I don’t understand what is going on here 
On RC1 can you dump whole flash partition and upload file flash.gz to somewhere online? This would help very much!
dd if=/dev/disk/by-label/COREELEC | gzip -c >flash.gz
This flash partition is fine and I can mount it on rc2 on my device.
Could you make one fresh SD card or USB stick with RC2 and see if it boots or not on your device? If it doesn’t then boot with RC1 and update to RC2. When it doesn’t boot you get the message you wrote and then you get into shell. Attach USB keyboard and type dmesg. Make a picture what you get and post it.
I have an issue with RC2 playing interlace content (1080i) at X2 Boxes
When I play the content and skip forward or back it is a 2 sec fullscreen clear Picture with random colors
I made a clean install on a SD Card and its the same
I test it on 3 X2 Boxes:
Vosen V1 X2
Bqeel y5 X2
H96 Max X2
Whith a X3 (X96 Max+) and a 922X (Orbsmart S86) Box there is no problem
So I have only problems on X2 Boxes with Interlace content on RC2
With RC1 everything is fine
is it possible, there is a problem with the Kernel update on X2 boxes ?
Did you manage to get 19.3 to work on Beelink King GT Pro and does it load from AN SD Card . Is there a straight copy to flash. I am new to this and would welcome some help. Thanks
Fresh install of RC2 on SD Card–Same exact result(no boot) with message. I ran the Dmesg and don’t know how to save the whole long result, but here is the end with the error mount messages. Will this be what you are looking for?
Yes, this is perfect!
You boot from USB or SD card? And do you have any other USB sticks attached on booting?
If I’m correct you are using Realtek Wifi stick? Can you try to boot without it?
SD Card. Yes I saw the USB messages and removed it, (it is the Wifi module that initially gets identified as a storage device). Made no difference other than the dmesg messages were gone for the realtek device.
Did you tried to boot RC2 from USB stick?
Also which Android version is on device?
I just tried a new install on USB stick and burned the image the exact same way as the SD card and it does, in fact, work!
Internal android is 7.1.2 and I haven’t booted to internal for a couple years, and have never tried USB(I have both ports used by Wifi and keyboard) as I have never had a problem, ever, with SD card.
It is possible that there was some small change between kernel and now you see this issue.
Could you boot RC2 from USB stick without SD card. When system comes up attach SD card and in ssh console type this command and post url.
dmesg | pastei think that it is a slight kernel change and as a guess see that it might be with fsck tool change?
Anyway I did ssh command and copied it into a text file (not sure if this is correct) and it doesn’t make sense to me but hope this is what you mean?
just try command again, it should give you a normal link
It is the kernel change but I doubt it has something to to with fsck. I checked the flash partition file you send on my device and it was fine (no errors). This time looks like there is no device visible (message Device not found, continuing…).
Could you run this command again on RC1 version which works fine? And please reboot before.
dmesg | paste
I made one test image and would be interesting to know if it updates to RC2 or not.
Also could you repeat the step booting RC2, attaching SD card and then run this commands and copy/paste text you get?
umount /media/COREELEC/ /media/STORAGE/ /dev/mmcblk1p1 /dev/mmcblk1p2
fsck -T -M -p -a LABEL=COREELEC
fsck -T -M -p -a /dev/mmcblk1p1
fatlabel /dev/mmcblk1p1
find /dev/disk/ | xargs ls -l
RC2 booted from USB and SD card inserted
CoreELEC (official): 19.4-Matrix_rc2 (Amlogic-ng.arm)
CoreELEC:~ # umount /media/COREELEC/ /media/STORAGE/ /dev/mmcblk1p1 /dev/mmcblk1
p2
umount: can't unmount /var/media/COREELEC: Invalid argument
umount: can't unmount /var/media/STORAGE: Invalid argument
CoreELEC:~ # fsck -T -M -p -a LABEL=COREELEC
fsck.fat 4.2 (2021-01-31)
/dev/mmcblk1p1: 70 files, 28152/65501 clusters
CoreELEC:~ # fsck -T -M -p -a /dev/mmcblk1p1
fsck.fat 4.2 (2021-01-31)
/dev/mmcblk1p1: 70 files, 28152/65501 clusters
CoreELEC:~ # fatlabel /dev/mmcblk1p1
COREELEC
CoreELEC:~ # find /dev/disk/ | xargs ls -l
lrwxrwxrwx 1 root root 13 Jan 23 14:57 /dev/disk/by-id/mmc-016G94_0xd6e84557 -> ../../mmcblk0
lrwxrwxrwx 1 root root 13 Jan 23 14:57 /dev/disk/by-id/mmc-SC32G_0xccb10498 -> ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 23 14:59 /dev/disk/by-id/mmc-SC32G_0xccb10498-part1 -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 Jan 23 14:57 /dev/disk/by-id/mmc-SC32G_0xccb10498-part2 -> ../../mmcblk1p2
lrwxrwxrwx 1 root root 9 Jan 23 14:57 /dev/disk/by-id/usb-PNY_USB_2.0_FD_AAC3160000000282-0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 23 14:57 /dev/disk/by-id/usb-PNY_USB_2.0_FD_AAC3160000000282-0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 23 14:57 /dev/disk/by-id/usb-PNY_USB_2.0_FD_AAC3160000000282-0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 15 Jan 23 14:59 /dev/disk/by-label/COREELEC -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 Jan 23 14:57 /dev/disk/by-label/STORAGE -> ../../mmcblk1p2
lrwxrwxrwx 1 root root 15 Jan 23 14:59 /dev/disk/by-partuuid/1073c556-01 -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 Jan 23 14:57 /dev/disk/by-partuuid/1073c556-02 -> ../../mmcblk1p2
lrwxrwxrwx 1 root root 13 Jan 23 14:57 /dev/disk/by-path/platform-d0072000.sd -> ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 23 14:59 /dev/disk/by-path/platform-d0072000.sd-part1 -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 Jan 23 14:57 /dev/disk/by-path/platform-d0072000.sd-part2 -> ../../mmcblk1p2
lrwxrwxrwx 1 root root 13 Jan 23 14:57 /dev/disk/by-path/platform-d0074000.emmc -> ../../mmcblk0
lrwxrwxrwx 1 root root 18 Jan 23 14:57 /dev/disk/by-path/platform-d0074000.emmc-boot0 -> ../../mmcblk0boot0
lrwxrwxrwx 1 root root 18 Jan 23 14:57 /dev/disk/by-path/platform-d0074000.emmc-boot1 -> ../../mmcblk0boot1
lrwxrwxrwx 1 root root 9 Jan 23 14:57 /dev/disk/by-path/platform-xhci-hcd.0.auto-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 23 14:57 /dev/disk/by-path/platform-xhci-hcd.0.auto-usb-0:1:1.0-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 23 14:57 /dev/disk/by-path/platform-xhci-hcd.0.auto-usb-0:1:1.0-scsi-0:0:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 15 Jan 23 14:59 /dev/disk/by-uuid/2001-3319 -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 Jan 23 14:57 /dev/disk/by-uuid/5bf50cb0-0114-4996-adbf-47b275f7f4a8 -> ../../mmcblk1p2
/dev/disk/:
total 0
drwxr-xr-x 2 root root 180 Jan 23 14:57 by-id
drwxr-xr-x 2 root root 80 Jan 23 14:57 by-label
drwxr-xr-x 2 root root 80 Jan 23 14:57 by-partuuid
drwxr-xr-x 2 root root 220 Jan 23 14:57 by-path
drwxr-xr-x 2 root root 80 Jan 23 14:57 by-uuid
/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root 13 Jan 23 14:57 mmc-016G94_0xd6e84557 -> ../../mmcblk0
lrwxrwxrwx 1 root root 13 Jan 23 14:57 mmc-SC32G_0xccb10498 -> ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 23 14:59 mmc-SC32G_0xccb10498-part1 -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 Jan 23 14:57 mmc-SC32G_0xccb10498-part2 -> ../../mmcblk1p2
lrwxrwxrwx 1 root root 9 Jan 23 14:57 usb-PNY_USB_2.0_FD_AAC3160000000282-0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 23 14:57 usb-PNY_USB_2.0_FD_AAC3160000000282-0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 23 14:57 usb-PNY_USB_2.0_FD_AAC3160000000282-0:0-part2 -> ../../sda2
/dev/disk/by-label:
total 0
lrwxrwxrwx 1 root root 15 Jan 23 14:59 COREELEC -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 Jan 23 14:57 STORAGE -> ../../mmcblk1p2
/dev/disk/by-partuuid:
total 0
lrwxrwxrwx 1 root root 15 Jan 23 14:59 1073c556-01 -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 Jan 23 14:57 1073c556-02 -> ../../mmcblk1p2
/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root 13 Jan 23 14:57 platform-d0072000.sd -> ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 23 14:59 platform-d0072000.sd-part1 -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 Jan 23 14:57 platform-d0072000.sd-part2 -> ../../mmcblk1p2
lrwxrwxrwx 1 root root 13 Jan 23 14:57 platform-d0074000.emmc -> ../../mmcblk0
lrwxrwxrwx 1 root root 18 Jan 23 14:57 platform-d0074000.emmc-boot0 -> ../../mmcblk0boot0
lrwxrwxrwx 1 root root 18 Jan 23 14:57 platform-d0074000.emmc-boot1 -> ../../mmcblk0boot1
lrwxrwxrwx 1 root root 9 Jan 23 14:57 platform-xhci-hcd.0.auto-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 23 14:57 platform-xhci-hcd.0.auto-usb-0:1:1.0-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 23 14:57 platform-xhci-hcd.0.auto-usb-0:1:1.0-scsi-0:0:0:0-part2 -> ../../sda2
/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 15 Jan 23 14:59 2001-3319 -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 Jan 23 14:57 5bf50cb0-0114-4996-adbf-47b275f7f4a8 -> ../../mmcblk1p2
CoreELEC:~ #
Sadly till not clear what the cause is. This would be final test - I hope you are still on it 
Boot RC1 from SD card and then update with RC2. When RC2 doesn’t boot you get into shell. Wait 3 minutes and run this commands. After dmesg and sync check that you really have file with some size and not 0. Power off device, copy file dmesg_user from SD card and upload it somewhere or attach to post. At the same time replace kernel/system to get back working device.
mkdir m
mount /dev/mmcblk1p1 m
dmesg >m/dmesg_user
sync
# check that you really have something in the file
# if not repeat dmesg and sync
ls -l m/dmesg_user
umount m
# power off device
I am getting “mount: mounting /dev/mmcblk1p1 on m failed: no such file or directory”
is that expected or a problem with getting what you need?
That’s the main issue: SD card is just not visible for some reason.
And if you wait some time and try again I assume it still fails?
What about this command gives you
ls -l /dev/mmc*
Btw: Did you tried some other SD card? Different brand?
