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.
hello, i have successful installation with emuelec on x88 pro x3. mine is 4gb/64gb. i know this forum is for coreelec. but i see same problem with dtb files. this file work for me: sm1_s905x3_2g.dtb. but i think it happened because my unit is using custom rom vortex. the stock rom bricked when i try to install supersu. it is encrypted unit so only way to flash it is using vortex rom. believe me its way better than the stock rom.
hope this help.
Hi, Did you got you back? I have mine stuck on logo, trie install other linux OS but it detecteds only 2gb of ram.
It’s confirmed the X88 Pro is a fake box with only 2g assembled:
Be warned: buy cheap, buy twice!
Hello, yesterday i install on my x88 x3 pro Ce 19.1 rc2 to emmc working , booting fine but if I want to boot to android i can’t , i click on context menu "boot to android " box is trying to restart and show 2x manufactur logo then boot back to CE.
If I deleted CE from emmc and boot from SD card, context menu working great and box boot to android. I want to have CE in emmc with possiblity to boot to android.
Can someone help me please?