CoreELEC 19.1-Matrix_rc3 Discussion

When you install to internal eMMC you should be able to recover the device…

Create a new clean uSD from rc3 and insert it into the device. Maybe you need to push and hold the reset button till CE logo shows up.

I removed the rc3 release from today until the reason is found of this issue.
All affected devices are S905X2?

What DTB is used?
Anyone able to make any log? Like by opening the device and attach UART?

Successful update on Odroid C4, no issues so far.

Upgrading to RC3 on N2 went smoothly.

Also reporting boot stuck on my 905x3 (x88pro x3 device) boot from sd card.
It was automatic update via system.

I tried to do a clean install from uSD with the reset button, but I either land in android recovery or am stuck in the x96 max boot logo.
currently trying to unbrick with this How To Recover a Bricked X96 Max using Linux

As you are mentioned in that post, can you assist and confirm that the mentioned dd command in the linked post is correct?
The instructions mention flashing the UBOOT and .ini file, but dd flashes UBOOT twice.

edit maybe @JohnBoyz can confirm this?

I failed to update my X96 max from nightly to rc3.
I did a fresh install on SD card of rc3 and it booted without incident.

I had not done an internal install on this device.

its probably the other way around, otherwise flashed uboot size is way off?

still I’m not able to reach the android logo screen. always back to the x96 max boot logo.

You just brick your device when flashing a ini to the bootloader!
No idea from where you got this information.

Create a recovery uSD by Burncardmaker by using a vendor Android image. Insert the uSD and press and hold the reset button and recovery should be started.

VIM3 installed to internal rc2 updated to rc3 yesterday, everything works fine

By confirming the request to update CoreElec I just updated from 19.1_rc2 and after the reboot and now I’m stuck at a boot screen (“A95X-F3 Slim” logo).

INFO: Release is currently on hold and update paused!
If the system request a update to rc3 do not update!!

Those who already updated need to take any action?
It seems to be working fine on my GT King (SD card install).

No, when updated and still booting there is nothing todo.

Please clarify what deangerous may happen, brick device or only CE stop booting on rc3? SD card installation, Vontar X3. Currently it looks like I need to remove sd card before power on my device and plug it to my PC to make sure I will remove update file, otherwise it will start update automatically after boot. Not sure if update is present or not, not checked before power off last time.

Or can I interrupt update process, is it safe?

You just have to check the contents of storage/.update. erase the file if it’s there. There won’t be anymore auto update until we figure out all the problems. You can check it by ssh into the device.

First need to boot it, if file is already present, update process will start and it won’t let me to check anything

Put you card in a linux environment. You’ll have access to storage and you can delete update.

Sometimes typing things out without knowing anything might lead to such a result :wink:

I reflashed Android with Burncardmaker and by now I am back on coreelec 19.1_rc2.

Thank you.

@DDuck , @thromin , @supperka , @jlazkano , are your boxes have 100Mbit ethernet?