me 2 i’m very confused does it matter dat it is een b grade brand ? chipset is al the same wright? on the bottum i see TT TV BOX android player model:X88PRO X3 RAM:4GB ROM:32GB
What is booting if you remove all USB and uSD?
Here is a technique I have found to help boot when my emmc gives me errors:
- Boot USB or SD card to CE
- Choose “reboot to nand/emmc” from power menu
- Once android starts, reboot.
It should then boot to emmc properly.
the tv lights up nothing on screen.
i’m not seeing reboot to nand or emmc or simmelar. Under Power Options i see: power off system, customshutdown timer, suspend, reboot, restart kodi.
CoreELEC:~ # df -h
Filesystem Size Used Available Use% Mounted on
devtmpfs 1.9G 4.0K 1.9G 0% /dev
/dev/mmcblk1p1 511.7M 203.1M 308.6M 40% /flash
/dev/loop0 187.0M 187.0M 0 100% /
/dev/mmcblk1p2 13.7G 5.5M 13.7G 0% /storage
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 1.9G 8.9M 1.9G 0% /run
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
tmpfs 1.9G 2.6M 1.9G 0% /var
tmpfs 1.9G 0 1.9G 0% /tmp
my X88 has 32G when android was working i saw 28GB something in the partioning went wrong ? or is this normal ?
I don’t know what is wrong on your box. The internal memory should still work as you still able to boot something. I guess best is to recover your box by a vendor Android image.
finaly it let me instal coreelec after i try to instal a rom with usb buring tool,
but it’s not booting after instaling en restarting tis is what i did :
CoreELEC:~ # ceemmc -x
Starting CoreELEC eMMC installation tool...
System is not supported: sm1_s905x3_4g_1gbit!
There is NO official support by Team CoreELEC
if you continue to run this tool!
Continue? [y]: y
eMMC size: 0x000747c00000 [32GB]
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': 29208MB
Used space of '/flash': 212MB
Used space of '/storage': 219MB
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 7477248 4k blocks and 1872304 inodes
Filesystem UUID: 99c1edd5-12e1-4371-b7a7-33c2ce65fc2c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 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.84M 100% 18.03MB/s 0:00:11 (xfr#32, to-chk=0/35)
Syncthing, please wait...
Copy all data from '/storage' to '/media/CE_STORAGE/coreelec_storage'
219.49M 99% 93.91MB/s 0:00:02 (xfr#330, to-chk=0/650)
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!So CE only on eMMC. Does it boot now? And when you run the ceemmc -vx now what is the output?
no it is not booting same as before, CoreELEC:~ # ceemmc -vx
Starting CoreELEC eMMC installation tool…
System is not supported: sm1_s905x3_4g_1gbit!
There is NO official support by Team CoreELEC
if you continue to run this tool!
Continue? [y]: y
Parameter for block device ‘mmcblk0’ not found: ‘/sys/block/mmcblk0/size’
Failed to read eMMC size! Exit!
Thank you, I will test it later here if something is broken on the tool.
Thank you, please let me know.
I just tested a single install on one of my devices with current 9.2.2 and it is working fine:
CoreELEC:~ # ceemmc -vx
Starting CoreELEC eMMC installation tool...
eMMC size: 0x0003a3e00000 [16GB]
Original 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 0x00037da00000 [14298 MB], data
Existing CoreELEC installation found on eMMC
[1] Make a copy of current CoreELEC installation on eMMC to current used SD or USB device
Please choose one option? [1]:
Also this is working here:
CoreELEC:~ # cat /sys/block/mmcblk0/size
30535680
I don’t know why it should not work on your device. What happening if installing in dual boot mode?
What does this mean? You install in single mode so only CE is on eMMC, Android get deleted.
How you where running ceemmc again? Botted from uSD/USB?
I wonder if it has something to do with the bootloader?
I was playing with my A95X Max trying to run from eMMC in single CE boot mode.
The process of installation seemed to go fine, apart from one warning message that read Warning: Could not find ‘dtbo’ partition!.
The 64Gb eMMC was seen and all the formatting and transfer of data looked good.
After the process was complete, I removed the original boot sourse and restarted but all that happened was that the vfd shows the word boot and stuck there with no further progress.
The one thing that I noticed that was different with the boot process was that the A95X Logo that normally appears as the first thing on screen when starting up was no longer being shown.
Putting the boot source back in the box enabled the original boot again.
When i ran the ceemmc process again it was interesting to see that it said ‘No CoreELEC installation found on eMMC’ which was unexpected.
So perhaps just a case of some boxes not capable of eMMC installation because of not having the necessary bootloader present?
This is warning only because some vendor name it different.
What happen if install in dual boot mode? Maybe there is something different in bootloader, yes. I don’t know because I have no such hardware → unsupported by CE.
In dual boot mode, android boots but when switching to CE just a blank screen unless the original boot media is inserted.
In my case I’m not surprised that it didn’t work because I know that it’s been a struggle for people to provide custom Android ROM’s for this box because of the bootloader, so perhaps Bubble’s box has a similar kind of issue.
I boot directly from an internal SSD in my box anyway, which works well for me, so the use of the ceemmc tool was more of a what if rather than a desire but might indicate the kind of direction that the issue may be coming from.
Any of you have a chance to get a bootloader log? It have to be a UART log, dmesg is not enough.
When you do not want to open the device this is may a alternative: CoreELEC Team SDIO Debug Board
i’m goning to try dual boot, yes i boot from usb, to use the ceemmc command.
How i get ceemmc get running again , is by try to install(alm buring tool )with rom version x96p3 air because it has identical specs so it is my best bed. i can’t find original rom for this box
aml usb buringtool ease flash & bootloader that helped so de ceemc tool could clean install CE.
A have a FTDI adaptor and soldering and open up tis box is no problem, but how do i create a log do you have a guide ?
Just use putty and record every print on booting. Maybe there is some information why it is not working. When you post pictures of your opened box we can search the 4-pin UART header. Sometimes there is also the mark with RX/TX.
I fond 3 holes named DBUG with labeling i connected the FTDI adaptor(ft2332rl) GND>GND TX>RX RX>TX . In putty tick serial com3 try diffrent bauterate en other serial settings, check drivers comports also linux and windows10 get no output, even if i boot from CE usb NO OUTPUT.
i ordered a new adaptor to rule out if its broken FTDI adaptor.