X96 Air kernel panic

Hello All. I have a strange issue with a brand new X96 Air P3 rev C. I have the same box, but P2 working great for over an year now and I am surprised I am having a problem with almost the same S905X3 box. First, I had problems booting from SD card. I bought a new SD card and was able to boot instantly. I setuped Coreelec as usual for the first time, then i injected Bl-301 and rebooted. I got my first Kernel panic (I am using MX3 airmouse). I did a brand new image on my SD card and tried again - kernel panic immediately. Strange thing is that after the first install BL-301 is injected by default on both nightly and stable 9.2.5 builds. Here is some info:

http://ix.io/2Kke

Here is the output of the update-bl301.log file:

> CoreELEC:~ # cat update-bl301.log

Starting bootloader blob BL301 injection tool…

This tool can be used to update the bootloader
blob BL301 of the vendor bootloader on the internal
eMMC. This bootloader blob BL301 is customized by
Team CoreELEC to support all wake-up features like
CEC, Wake-On-LAN, IR, and GPIO wake-up from
suspend or power off state!

Device serial number: 2b0c1000011b1a000007373156525250
Using CPU type SM1 (2b): S905X3, S905D3
Using binary type because of CoreELEC DT-ID: Generic
Using /dev/bootloader as bootloader partition

Did not find Amlogic image v2 header magic!
Found a valid Amlogic v3 ToC header (0x10210)
Amlogic magic: AA640001
Serial Number: 12345678
Flags: 0

TOC ENTRY #0
UUID: 9766FD3D89BEE849AE5D78A140608213
Offset Address: 0x68000 (absolute: 0x78210)
Size: 0xE570
Flags: 0x0
Found BL30 blob image at: 0x00078210
Amlogic magic: @AML
Old signature bl30: B98EE840E59249701B51F8A28A2F3723A91A7B6A3A5DD4E4500298776613B116
Using bl301 blob: Generic_2b_bl301.bin
New signature bl30: B98EE840E59249701B51F8A28A2F3723A91A7B6A3A5DD4E4500298776613B116
Update of BL301.bin on eMMC is not needed

It’s not strange. The same bootloader is used, doesn’t matter where you boot from.
No idea what could cause this issue. Normally if bl301 fails you would not reach the logo at all.
You can make a SSH connection or you have UART? Then you can restore manually the bootloader to recover the device.
If not and because your device is still booting recover Android by a uSD card prepared by Burncardmaker and a vendor image.

Please report if the error is gone after recovery and reinstall CE, thx. Then I will add the device as not compatible for bl301!

1 Like

I saw entropy error on some S922x boxes with wrong cpu frequencies (wrong dtb)
But in SM1 case don’t know…
You could also test nightly build

1 Like

Did a fresh install, but this time i have set the remotewakeup to “0x00078210” in the config.ini before first boot. Remote doesn’t power up the box, but for some reason everything seems to be stable now. I assume Coreelec expects some value in config.ini for the “remotewakeup” parameter, since bl-301 is enabled by default.

1 Like

ok, i got a brand new box, this time bl301 did not get injected automatically. I made a copy of the new x96 air bootloader with ADB tools (just in case). Everything works fine now. I think the previous time the bootloader got messed up and the inject_bl301 script did not make a backup of the original device bootloader. Thank you for your help and Happy New year !

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.