Thank you so much for your interest in my issue I tried using the dtb file you attached, but it was not bootable.
@adam,
I will attach the entire log that ran the ceemmc through S905X3_2g_1gbit.dtb. I’d appreciate it if you could check if there’s a problem.
CoreELEC (official): 9.2.2 (Amlogic-ng.arm)
CoreELEC:~ # ceemmc -vx
Starting CoreELEC eMMC installation tool...
System is not supported: sm1_s905x3_2g_1gbit!
There is NO official support by Team CoreELEC
if you continue to run this tool!
Continue? [y]: y
eMMC size: 0x001d1ec00000 [128GB]
Original partition table:
[mmcblk0p01] bootloader offset 0x000000000000, size 0x000000400000 [4 MB], unkn
[mmcblk0p02] reserved offset 0x000002400000, size 0x000004000000 [64 MB], unkn
[mmcblk0p03] cache offset 0x000006c00000, size 0x000046000000 [1120 MB], cache
[mmcblk0p04] env offset 0x00004d400000, size 0x000000800000 [8 MB], unkn
[mmcblk0p05] logo offset 0x00004e400000, size 0x000000800000 [8 MB], code
[mmcblk0p06] recovery offset 0x00004f400000, size 0x000001800000 [24 MB], code
[mmcblk0p07] misc offset 0x000051400000, size 0x000000800000 [8 MB], code
[mmcblk0p08] dtbo offset 0x000052400000, size 0x000000800000 [8 MB], code
[mmcblk0p09] cri_data offset 0x000053400000, size 0x000000800000 [8 MB], cache
[mmcblk0p10] param offset 0x000054400000, size 0x000001000000 [16 MB], cache
[mmcblk0p11] boot offset 0x000055c00000, size 0x000001000000 [16 MB], code
[mmcblk0p12] rsv offset 0x000057400000, size 0x000001000000 [16 MB], code
[mmcblk0p13] metadata offset 0x000058c00000, size 0x000001000000 [16 MB], code
[mmcblk0p14] vbmeta offset 0x00005a400000, size 0x000000200000 [2 MB], code
[mmcblk0p15] tee offset 0x00005ae00000, size 0x000002000000 [32 MB], code
[mmcblk0p16] vendor offset 0x00005d600000, size 0x000014000000 [320 MB], code
[mmcblk0p17] odm offset 0x000071e00000, size 0x000008000000 [128 MB], code
[mmcblk0p18] system offset 0x00007a600000, size 0x000080000000 [2048 MB], code
[mmcblk0p19] product offset 0x0000fae00000, size 0x000008000000 [128 MB], code
[mmcblk0p20] data offset 0x000103600000, size 0x001c1b600000 [115126 MB], data
No CoreELEC installation found on eMMC
Install in dual boot mode, CoreELEC and Android on eMMC
Use CoreELEC data from
[1] current used SD or USB device
[2] existing backup on current used SD or USB device
Install in single boot mode, only CoreELEC on eMMC
Use CoreELEC data from
[3] current used SD or USB device
[4] existing backup on current used SD or USB device
Please choose one option? [1/2/3/4]: 3
Free space of 'partition CE_FLASH': 512MB
Warning: Could not find 'dto' partition!
Free space of 'partition CE_STORAGE': 118664MB
New partition table:
[mmcblk0p01] bootloader offset 0x000000000000, size 0x000000400000 [4 MB], unkn
[mmcblk0p02] env offset 0x000000400000, size 0x000000800000 [8 MB], unkn
[mmcblk0p03] misc offset 0x000000c00000, size 0x000000800000 [8 MB], code
[mmcblk0p04] logo offset 0x000001400000, size 0x000000800000 [8 MB], code
[mmcblk0p05] dtbo offset 0x000001c00000, size 0x000000800000 [8 MB], code
[mmcblk0p06] reserved offset 0x000002400000, size 0x000004000000 [64 MB], unkn
[mmcblk0p07] CE_FLASH offset 0x000006400000, size 0x000020000000 [512 MB], data
[mmcblk0p08] CE_STORAGE offset 0x000026400000, size 0x001cf8800000 [118664 MB], data
Used space of '/flash': 212MB
Used space of '/storage': 3MB
There is enough free space on eMMC for installation!
Install CoreELEC on eMMC.
Continue? [y]: y
Moved 'env' from offset 0x00004d400000, size 0x000000800000 to offset 0x000000400000
Moved 'misc' from offset 0x000051400000, size 0x000000800000 to offset 0x000000c00000
Moved 'logo' from offset 0x00004e400000, size 0x000000800000 to offset 0x000001400000
Moved 'dtbo' from offset 0x000052400000, size 0x000000800000 to offset 0x000001c00000
Starting to format the new 'CE_STORAGE' partition...
mke2fs 1.45.3 (14-Jul-2019)
Discarding device blocks: done
Creating filesystem with 30377984 4k blocks and 7602176 inodes
Filesystem UUID: ea494a38-7690-4929-9fc8-f9f4d5df473e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Starting to format the new 'CE_FLASH' partition...
mkfs.fat 4.1 (2017-01-24)
Stopping Kodi before start of copy process!
Starting copying of data to the eMMC!
Please do NOT interrupt this progress till it's finished!
Copy all data from '/flash' to '/media/CE_FLASH'
212.83M 100% 36.42MB/s 0:00:05 (xfr#33, to-chk=0/36)
Syncthing, please wait...
Copy all data from '/storage' to '/media/CE_STORAGE/coreelec_storage'
3.63M 99% 9.17MB/s 0:00:00 (xfr#328, to-chk=0/651)
Syncthing, please wait...
Start Kodi again to have a user interface!
Success!
You can now power off the device, remove the used boot media (SD or USB) and
power on again to boot the device from eMMC!hongtonik, installation went fine. But why it doesn’t boot is different story and have no idea. Using log from UART would tell more.
Just got this box today and tried all the generic s905x3 DTB from image and the ones uploaded but no luck booting to CE (booting from USB). Good box at first glance but too bad it’s unusable for CE (at this point)
hi hongtonik, it seems you have a x88 pro x3 4/128gb protected box. I was wondering if you could share your firmware so I could bring mine back to life. thanks.
I have a 4/32 which works ok with generic 2g_1gbit dtb. The box should be 4Gb, but I am afraid it may be a fake 4Gb…
I have the same box (4/32) and it also fails with the 4g DTB, but loads up fine with sm1_s905x3_2g_1gbit DTB. This is all booting off the MicroSD with 9.2.5
I cracked it open, and it definitely has 4GB of RAM on the board. Is there anything I can provide that might help get it working with all 4GB?
i am in the same boat, can only get my 4/32 X88 to boot with sm1_s905x3_2g_1gbit. it works well like that to be fair, but obviously would like to utilize the full 4gb
What can you load/run on CE that actually makes use of the extra memory? I know you can increase buffer size, but you don’t need 2GB for that.
Andrew
All what will need to use a 2g dtb for a 4g device please dump your device dtb by:
dd if=/dev/dtb | gzip > /storage/downloads/dtb.img.gz
Then please attach it here and tell us what device it is, thx.
This is from my X88 Pro X3 (S905X3, 4GB RAM, 32GB Storage), with RTL8211F 1000M Ethernet and an SP6255 Wi-Fi module (Seems to be a clone of AP6255?). Pulled running sm1_s905x3_2g_1gbit off CoreELEC 9.2.5 from the SD slot
dtb.img.gz (206.7 KB)
your Android /dev/dtb is encrypted. you have any chance to boot into Android and open a SSH or UART connection?
After some quick Googling, apparently the box itself is encrypted. I was able to get into a terminal session under its stock Android install and pulled the DTB again, but it’s still encrypted (same hash as the one I posted). Or would you like me to run some other commands?
Boot into Android and try to read this value by the xxd cmd:
console:/ $ xxd /proc/device-tree/memory@00000000/reg
00000000: 0000 0000 d800 0000 ........
or
console:/ $ hexdump -C /proc/device-tree/memory@00000000/reg <
00000000 00 00 00 00 d8 00 00 00 |........|
00000008
2 Likes
Ran them both:
console:/ $ xxd /proc/device-tree/memory@00000000/reg
00000000: 0000 0000 7800 0000 ....x...
console:/ $ hexdump -C /proc/device-tree/memory@00000000/reg
00000000 00 00 00 00 78 00 00 00 |....x...|
00000008
It boots fine when I use the toothpick method, but after fresh install and a reboot, it just gets stuck bootlooping at the AMLogic logo. I can still boot it up using the toothpick method again though, and it reports 1860MB of memory in System Information
Alternatively, the normal sm1_s905x3_2g_1gbit.dtb I was using boots fine each time (no boot loops) and reports a slightly different amount of RAM, 1986MB
Don’t understand.
You need to be able to boot CE with the 2g dtb.
If this is working just replace the dtb.img with the new one I attached. Then try to boot again and if it boots check memory.
The dtb.img will be overwritten by an update!
I did use the new dtb. I created a fresh MicroSD with your new dtb posted, but it made my device bootloop after the initial install and when powering up. I have to use the toothpick method each time I turn on the device to avoid the bootloop. When I finally get into CoreELEC, it displays 1860MB of memory
I then replaced the dtb with a sm1_s905x3_2g_1gbit.dtb, and it no longer bootloops, but displays slightly more memory (1986MB)
Then I am sorry, not supported and bootloader is encrypted anyway.