Android 7.1.2 booting from eMMC after ceemmc

Hi!
I have two boxes KI Pro (S905D) with Android 7.1.1
CE 19.2 installed on internal eMMC in dual boot mode.
It worked.
I (re-) flashed Android firmware 7.1.2.
Then used ceemmc to install CE Matrix to internal.

CoreELEC (official): 19.2-Matrix_nightly_20210717 (Amlogic-ng.arm)
CoreELEC:~ # ceemmc -x
Starting CoreELEC eMMC installation tool...
System is not supported: gxl_p230_k1_pro!
There is NO official support by Team CoreELEC
if you continue to run this tool!
Continue? [y]: y
eMMC size: 0x0003a3e00000 [16GB]
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 not possible!
  No DT partition was found
Please choose one option? [1/2]: 1
Free space of 'partition CE_FLASH': 512MB
Free space of 'partition CE_STORAGE': 10886MB
Used space of '/flash': 230MB
Used space of '/storage': 110MB
There is enough free space on eMMC for installation!
Install CoreELEC on eMMC.
Continue? [y]: y
e2fsck 1.45.6 (20-Mar-2020)
resize2fs 1.45.6 (20-Mar-2020)
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'
        230.28M 100%   30.55MB/s    0:00:07 (xfr#68, to-chk=0/84)
Synchronize data on disk with memory, please wait...
Copy all data from '/storage' to '/media/CE_STORAGE/coreelec_storage'
        110.82M  99%   23.98MB/s    0:00:04 (xfr#278, to-chk=0/532)
Synchronize data on disk with memory, 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!
CoreELEC:~ #

But now booting from eMMC only Android!
Checked on two boxes.
Any ideas how to solve this problem?
Thanks!

Looks like your box installed CoreELEC to eMMC in dual boot mode but has retained the preference to boot to Android by default.

Give this thread a quick read and see if it solves your issue:

If that fails you can confirm that CE is in fact installed to eMMC by downloading and running the Android App: Reboot to LibreELEC.

I’ve encountered that even some Android 7.1.2 firmwares don’t allow for installing CE to eMMC in Single Boot mode.

CE installed to eMMC in dual boot mode!
This can be seen if you run again ceemmc -

CoreELEC:~ # ceemmc -vx
Starting CoreELEC eMMC installation tool...
System is not supported: gxl_p230_k1_pro!
There is NO official support by Team CoreELEC
if you continue to run this tool!
Continue? [y]: y
eMMC size: 0x0003a3e00000 [16GB]
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 0x000020000000 [512 MB], cache
[mmcblk0p04]                  env  offset 0x000027400000, size 0x000000800000 [8 MB], unkn
[mmcblk0p05]                 logo  offset 0x000028400000, size 0x000002000000 [32 MB], code
[mmcblk0p06]             recovery  offset 0x00002ac00000, size 0x000002000000 [32 MB], code
[mmcblk0p07]                  rsv  offset 0x00002d400000, size 0x000000800000 [8 MB], code
[mmcblk0p08]                  tee  offset 0x00002e400000, size 0x000000800000 [8 MB], code
[mmcblk0p09]                crypt  offset 0x00002f400000, size 0x000002000000 [32 MB], code
[mmcblk0p10]                 misc  offset 0x000031c00000, size 0x000002000000 [32 MB], code
[mmcblk0p11]                 boot  offset 0x000034400000, size 0x000002000000 [32 MB], code
[mmcblk0p12]               system  offset 0x000036c00000, size 0x000080000000 [2048 MB], code
[mmcblk0p13]                 data  offset 0x0000b7400000, size 0x0002cca00000 [11466 MB], data
[mmcblk0p14]           CE_STORAGE  offset 0x0000b7400000, size 0x0002cca00000 [11466 MB], data
[mmcblk0p15]             CE_FLASH  offset 0x000383e00000, size 0x000020000000 [512 MB], data
Existing **CoreELEC dual boot installation found on eMMC**
Migrate CoreELEC dual boot to single boot installation
  Use CoreELEC data from
    [1] current used SD or USB device
    [2] the existing data on eMMC
    [3] existing backup on current used SD or USB device
Renew current CoreELEC dual boot installation on eMMC
  Use CoreELEC data from
    [4] current used SD or USB device
    [5] existing backup on current used SD or USB device
[6] Make a backup of current CoreELEC dual boot installation on eMMC to current used SD or USB device
[7] Remove current CoreELEC dual boot installation on eMMC
Please choose one option? [1/2/3/4/5/6/7]:

But now booting from eMMC only Android!

I tried this option - reboot to Recovery Box!

Not to undermine your efforts but is it absolutely necessary to run your box from eMMC?

I have a distinct feeling that it’s an issue with your firmware as I’ve encountered the similar issues before. If it were an S905X I’d suggest you try one of the generic roms like ATVxperience or Aidan’s Rom. Being that you have an S905D you’re kind of in a tough spot as the development for that chipset with those two rom developers has been more or less abandoned. I couldn’t say if it would work as I’ve never had an S905D device and I’d caution against trying unless you’re confident in your unbricking skills for this particular device.

Were I in your situation, I’d probably be inclined to cut my losses, reinstall Android from the USB Burning rom and run CE from uSD.

It loads faster from emmc.
I’m so used with Android 7.1.1

You are talking about a S905D box.
If You want it fast buy Odroid N2+
It´s a modern fairy tale to speed up this old boxes running on internal.
I own two S905X an one S912
S912 running internal, S905X running SD
S912 boots a few seconds faster … thats it

So you’re able to run CE 19.2 successfully in dual boot mode with Android 7.1.1?

If you’re dead set on installing to eMMC, why not re-install Android 7.1.1 to the box and restore a setup that you know works? I personally have no use for Android beyond the bootloader on my older box so I can’t honestly say, but I don’t imagine there is much of a difference between 7.1.1 and 7.1.2.

Yes I wrote about it

How many times a day you boot your box to be so keen on loading time? It’s usually a 10 sec difference in boot time between these options.
Since I usually boot my boxes once a day, I never bothered with internal CE instalation…

“Practice makes perfect.”

UART Log while loading from emmc

UART Log

BL2 Built : 17:47:29, Jul 11 2017.
gxl gcb74862-dirty - jiaxing.ye@droid05

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 7
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
STICKY_REG0: 0x00000000
STICKY_REG1: 0x00000000
STICKY_REG9: 0x00000000
DDR3 chl: Rank0+1 @ 792MHz - FAIL
STICKY_REG0: 0x00000000
STICKY_REG1: 0x00000000
STICKY_REG9: 0x00000000
DDR4 chl: Rank0+1 @ 792MHz - PASS
Rank0: 1024MB(auto)-2T-18
Rank1: 1024MB(auto)-2T-18
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x0002c600
Load bl32 from eMMC, src: 0x00050200, des: 0x05300000, size: 0x00036200
Load bl33 from eMMC, src: 0x00088200, des: 0x01000000, size: 0x00066a00
NOTICE: BL3-1: v1.0(release):35dd647
NOTICE: BL3-1: Built : 15:20:30, Feb 7 2018
[BL31]: GXL CPU setup!
NOTICE: BL31: BL33 decompress pass
mpu_config_enable:ok
[Image: gxl_v1.1.3243-377db0f 2017-09-07 11:28:58 qiufang.dai@droid07]
OPS=0x02
f4 ec 7d 3 13 31 9e 7c db 3f 74 79 [0.490947 Inits done]
secure task start!
high task start!
low task start!
INFO: BL3-2: ATOS-V2.0.2-g7eeafe5 #4 Thu May 18 13:19:01 CST 2017 arm
INFO: BL3-2: Chip: GXL Rev: B (21:B - 0:2)
INFO: BL3-2: crypto engine DMA
INFO: BL3-2: secure time TEE
INFO: BL3-2: CONFIG_DEVICE_SECURE 0xb200000e

U-Boot 2015.01-g9331ff1-dirty (Mar 13 2018 - 21:09:40)

DRAM: 2 GiB
Relocation Offset is: 76eb2000
register usb cfg[0][1] = 0000000077f5b090
[CANVAS]canvas init
boot_device_flag : 1
Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc.
init bus_cycle=6, bus_timing=7, system=5.0ns
reset failed
get_chip_type and ret:fffffffe
get_chip_type and ret:fffffffe
chip detect failed and ret:fffffffe
nandphy_init failed and ret=0xfffffff1
MMC: aml_priv->desc_buf = 0x0000000073eb2790
aml_priv->desc_buf = 0x0000000073eb4ab0
SDIO Port B: 0, SDIO Port C: 1
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
init_part() 278: PART_TYPE_DOS
[mmc_init] mmc init success
dtb magic 5f4c4d41
Amlogic multi-dtb tool
Multi dtb detected
Multi dtb tool version: v2 .
Support 2 dtbs.
aml_dt soc: gxl platform: q20x variant: 2g
dtb 0 soc: gxl plat: q20x vari: 1g
dtb 1 soc: gxl plat: q20x vari: 2g
Find match dtb: 1
start dts,buffer=0000000073eb7300,dt_addr=0000000073ec2b00
Amlogic multi-dtb tool
Multi dtb detected
Multi dtb tool version: v2 .
Support 2 dtbs.
aml_dt soc: gxl platform: q20x variant: 2g
dtb 0 soc: gxl plat: q20x vari: 1g
dtb 1 soc: gxl plat: q20x vari: 2g
Find match dtb: 1
get_partition_from_dts: not find /partitions node FDT_ERR_NOTFOUND.
get_ptbl_from_dtb()-259: get partition table from dts faild
mmc_device_init()-1081: get partition table from dtb failed
init_part() 278: PART_TYPE_DOS
eMMC/TSD partition table have been checked OK!
check pattern success
mmc env offset: 0x27400000
In: serial
Out: serial
Err: serial
reboot_mode(0xc810023c)=0x8
reboot_mode=charging
[store]To run cmd[emmc dtb_read 0x1000000 0x40000]
_verify_dtb_checksum()-917: calc 259312c2, store 259312c2
_verify_dtb_checksum()-917: calc 259312c2, store 259312c2
dtb_read()-1039: total valid 2
dtb_read()-1106: do nothing
Amlogic multi-dtb tool
Multi dtb detected
Multi dtb tool version: v2 .
Support 2 dtbs.
aml_dt soc: gxl platform: q20x variant: 2g
dtb 0 soc: gxl plat: q20x vari: 1g
dtb 1 soc: gxl plat: q20x vari: 2g
Find match dtb: 1
vpu: clk_level in dts: 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
vpu: vpu_clk_gate_init_off
vpp: vpp_init
hpd_state=1
[1080p60hz] is invalid for cvbs.
set hdmitx VIC = 16
config HPLL = 2970000
HPLL: 0xc000027b
config HPLL done
j = 4 vid_clk_div = 1
hdmitx: set enc for VIC: 16
HDMITX-DWC addr=0x10004006 rd_data=0x40
Error: HDMITX-DWC exp_data=0xff mask=0x9f
rx version is 1.4 or below div=10
hdmtix: set audio
hdmitx phy setting done
vpp: vpp_pq_load pq val error !!!
Net: dwmac.c9410000amlkey_init() enter!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0

Start read misc partition datas!
info->attemp_times = 0
info->active_slot = 0
info->slot_info[0].bootable = 1
info->slot_info[0].online = 1
info->slot_info[1].bootable = 0
info->slot_info[1].online = 0
info->attemp_times = 0
attemp_times = 0
active slot = 0
wipe_data=successful
wipe_cache=successful
upgrade_step=2
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x7f851000
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x7f851000
[CANVAS]addr=0x7f851000 width=3840, height=2160
amlkey_init() enter!
amlkey_init() 71: already init!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0
[KM]Error:f[key_manage_query_size]L507:key[usid] not programed yet
[KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet
gpio: pin GPIOAO_2 (gpio 102) value is 1
saradc - saradc sub-system

Usage:
saradc saradc open - open a SARADC channel
saradc close - close the SARADC
saradc getval - get the value in current channel
saradc test - test the SARADC by channel-7
saradc get_in_range - return 0 if current value in the range of current channel

key1 = ba45ff00
key2 = ba4594ca
time_out = f4a10
vs_irkey - irkey key_value1 key_value2 time_value

Usage:
vs_irkey
reboot_mode(0xc810023c)=0x8
Hit Enter or space or Ctrl+C key to stop autoboot – : 0
card in
sdio debug board detected, sd card with 1bit mode
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
emmc/sd response timeout, cmd1, status=0x1ff2800
(Re)start USB…
USB0: USB3.0 XHCI init start
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices… 2 USB Device(s) found
scanning usb for storage devices… 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Invalid partition 4 **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Invalid partition 15 **
** Invalid partition 16 **
** Invalid partition 17 **
** Invalid partition 18 **
** Invalid partition 19 **
** Invalid partition 20 **
** Invalid partition 21 **
** Invalid partition 22 **
** Invalid partition 23 **
** Invalid partition 24 **
ee_gate_off …

Booting Android Image at 0x01080000 …

reloc_addr =73f373b0
copy done
Kernel command line: buildvariant=userdebug
load dtb from 0x1000000 …
Amlogic multi-dtb tool
Single dtb detected
Uncompressing Kernel Image … OK
kernel loaded at 0x01080000, end = 0x01fb9020
Loading Ramdisk to 73cbd000, end 73e9fbb7 … OK
Loading Device Tree to 000000001fff2000, end 000000001ffff519 … OK
fdt_instaboot: no instaboot image

Starting kernel …

uboot time: 6866059 us
[ 0.000000@0] Initializing cgroup subsys cpu
[ 0.000000@0] Initializing cgroup subsys cpuacct
[ 0.000000@0] Linux version 3.14.29-g7d57fff (weizhongyi@vstrong3) (gcc version 4.9.2 20140904 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.09 - Linaro GCC 4.9-2014.09) ) #11 SMP PREEMPT Fri Sep 14 11:19:07 CST 2018
[ 0.000000@0] CPU: AArch64 Processor [410fd034] revision 4

Remove your attached USB devices and try again.

Tried it ten times in different flavors

The log shows USB device is connected

Maybe this UART ADAPTER - SDIO Debug Board ? I’ll try again to make a new log

About | FAQ | Terms of Service | Privacy Policy | Legal Notice