Cause it’s some proprietary code right ?
Yes, there should be two partition, but it might not show up on all devices.
If you boot up to android, it prevents CoreELEC from accessing some of its own files. This can happen if you Reboot to NAND/emmc.
Ok, but how to even reboot to Android intentionally once the setup is done ? 
Edit : with the reboot to Nand/EMMC option 
OK, so i can not for the life of me get CoreELEC installed on EMMC. i tried both the single boot and dual boot images for the AM6+, installed the 20.5 NG DV image to flash drive, copyied and renamed the dtb file to dtb.img and copied the divi module, the i booted from the flash drive ran ceemmc -x then continue Y then select 1 and i get this:
Please choose one option? [1/2/3/4/5/6/7]: 1
Free space of ‘partition CE_FLASH’: 512MB
Warning: Could not find ‘dto’ partition!
Could not find ‘CE_STORAGE’ partition!
Failed to read size of partition ‘CE_STORAGE’!
Failed to create new partition table!
what am i missing here?
If you have options 1-7 available means you already have ce installed to emmc. You need to choose the option to erase if you want to reinstall ce to emmc.
single boot or dual boot, i cannot install just coreelec to emmc
single boot not supported. If you unplug usb does ce boot or android?
You want to have the single boot image installed from Ugoos (the one with one Android on it). It’s available on their website if you want to start from scratch. Then you use the ceemmc tool to install CE in the dualboot option.
Don’t use the Ugoos dualboot image, nor try to install install CE in single boot. Both those avenues triggered the missing dto partition for me.
@n2plousse heh I went so far as to remove the boot from eMMC nand selection in the power menu to keep from accidentally selecting that 
.
1 Like
thats what i ended up doing, but would prefer single boot CoreELEC
It you want it to work and move on from there, you should just select the dual boot option for ceemmc 
I install CE on 64 GB SD card, run ceemmc tool, gives errors:
CoreELEC:~ # ceemmc -x
Starting CoreELEC eMMC installation tool...
System is not supported: g12b_s922x_ugoos_am6b!
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]: 1
Free space of 'partition CE_FLASH': 512MB
mount: /var/media/CE_STORAGE: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
Error running pclose on cmd: `mount -o rw,loop /dev/loop1 /media/CE_STORAGE`. Error: 32
Error executing cmd 'mount -o rw,loop /dev/loop1 /media/CE_STORAGE'
Failed to mount 'CE_STORAGE' partition!
Failed to read free space of partition 'CE_STORAGE'!
Failed to create new partition table!
CoreELEC:~ # df -h
Filesystem Size Used Available Use% Mounted on
devtmpfs 1.8G 4.0K 1.8G 0% /dev
tmpfs 759.9M 15.8M 744.2M 2% /run
/dev/mmcblk1p1 511.7M 247.0M 264.8M 48% /flash
/dev/loop0 224.5M 224.5M 0 100% /
/dev/mmcblk1p2 55.3G 360.2M 54.9G 1% /storage
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup
tmpfs 1.9G 3.2M 1.9G 0% /var
tmpfs 1.9G 0 1.9G 0% /tmp
/dev/vendor 248.0M 215.3M 27.6M 89% /android/vendor
/dev/sdc1 698.6G 696.2G 2.4G 100% /var/media/Expansion Drive
/dev/sda1 1.8T 1.8T 14.2G 99% /var/media/SP PHD U3
/dev/sdb1 4.5T 3.4T 1.2T 74% /var/media/My Passport
/dev/sdd2 10.9T 4.7T 6.2T 43% /var/media/SGEXOS
/dev/sde2 4.5T 3.8T 812.1G 83% /var/media/One Touch
What will i do now?
Thanks!
1 Like
Reinstall Ugoos pure Android (not dual boot) on device and try again.
Already used regular firmware!
Maybe sd card size is larger than internal memory? Ad in df -h, /storage partition has 55.3 GB, while the box has only 32 GB!
OK now, used 16 GB USB for CE then ceemmc works as intend!
That is an excellent idea !
Any of you randomly having no more signal sent after refresh rate switching ?
Fortunately I know the Kodi UI enough to stop the video and get display back…
Is there anyway to reset the CE like factory reset then do setup from scratch?
In CE settings addon.
https://wiki.coreelec.org/coreelec:ce_addon_system
1 Like
Hello, I am a new CoreElec and Ugoos AM6B plus user. I have read the installation guide on the forum but am having issues. Sorry for my basic questions but i got a message “File system corruption has been detected Coreelec” when i tried to boot using the reset pin method.
I wanted to just check the basic preparation settings first to diagnose the fault reason.
- Do i format the USB drive / SD card in Fat format or NTFS via windows (so far tried FAT)?
- Does the USB drive / SD card need to be smaller than 64gb ( i dont have anything smaller)
- Which of the USB ports should i use, the 2 on the back of the Ugoos or the 2 on the side ? (tried all the ports).
When using the Balenaetcher software to install the Armlogic generic img to the USB drive it installs and pauses at validating 98% and give a message “Flash failed”.
Thereafter i have take out usb and reinsert it to see the drive renamed to CoreElec, now with Device_trees folder and 7 other files on the USB drive.
Also i cant see two partions only the CoreElec partion !
Grateful for any advice you can give me to get this working
1 Like
new owner here of an AMB6B+. I’ve booted to Core ELEC via a USB stick (the micro SD card from an old Pi had a very loose fit in the card slot and I was unable to use it - are some micro SD cards a slightly different size?). Anyway, I have Kodi running fine, connection sorted to my shared database etc and the rebooting via the USB stick is solid. I’ve looked at various posts on use of the ceemmc tool and I’m not 100% sure how to proceed or what the result will be. I understand I need a dual boot option? But what’s the difference between [1] and [2]? Should I be running a backup within Kodi to save to the USB stick and then picking option [2] ? And if successful, when I reboot the device without the USB stick, can I expect a boot menu every time? Keen to understand what the outcome will be before committing. Thanks for any advice.
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