I tried everything. I changed power adapter, use button for 20-50s, wait without power supply whole night 
my device is dead looks like, but i have no idea why just after update. As i said update went fine, but after coreelec logo first run all switched off and now is dead
Do you have enough space left on your storage partition?
It could also be a faulty download. What happens, if you manually download the tar file to your /storage/.update/ folder and reboot your box?
Sorry i just read post above the other one you posted.
Mine did not carry out the update.
It rebooted to black screen.
Different symptom.
My update proceeded after the black screen when it booted Android
then powered off and on after that.
You need Amlogic Burning Tool
Burn the Android image for your box.
Only thing you can try.
I have the same problem - t95q
TR99 X2 (S905X2 / 2G) here, also dead after the update… Was booting from SD, Android was on eMMC, but it’s not going there.
I have two 922 Boxes , everything is ok
But the other two 905 X2 Boxes are dead after update
Arm Burning tool dont work anymore
i think the problem is the bl 301 blob on X2 Boxes
If the bl 301 blob is activated the X2 Boxes crashes
Please be carefull
Yes i have bl301 activated 
so its update fault
bl301 injection brings always a risk. There is also a warning.
Sure, playing with not official software is always risk, that way i use sd card
Well, that didn’t help here did it? I also had my CoreELEC on SD and the box is dead after the update.
bl301 on s905x2 is fault looks like, anybody updating should disable bl301 just before? Or better wait for fix
I know the risc with bl301 blob
But it works on 9.2.3 and if you update on 9.2.4 the Box is realy dead
I try with amlogic burning tool to restore Android , no connection
I spend some hours at last night to prepare old device, cause my kids will be not happy today At least I have backup device wetek hub guys should hurry and take down update files
I see there was some commits to bl301 last days.
The CE settings and also the download helper on our main website are pointing to the 9.2.3 release again. Auto-updates are also disabled.
Therefore only users downloading directly from GitHub are able to access 9.2.4.
We will investigate this problem as soon as possible and leave everything pointed to 9.2.3 until a fix is available.
1 Like
Added SPI device for devices with GPIO headers (ODROID & VIM3(l))
This sounds really interesting. For some reason I thought the GPIO pins were not available in CoreELEC at all. I recently started playing with Arduino’s and it would be cool and useful if I can do some stuff with the GPIO header on my VIM3 as well. Can I find information somewhere on what pins are available in CoreELEC and some information on how to use them?
Also, would it also be possible to use gpio-ir-tx or pwm-ir-tx on my VIM3? If so how would I enable it and define a pin? Is this somehow possible by running fdtput on the dtb file with the right parameters perhaps?
Doesn’t matter if you use SD card. Bl301 injection manipulates U-boot on emmc/nand. So there is a big chance bricking something. Restore your uboot on Android box and it will work again.
@oastra tried the amlogic burning tool and that still failed for them, are you talking about something else?
The uboot cannot be restored
Usb Burning Tool has no connection
Then you need to shorten some pins to force using u-boot from SD card. You might find the uboot in the vendors android img.