Bl301 injection, problems, help,

Then just grep the kodi.log and upload it somehow

i couldn’t work out how to manually post to xi.io so i used the below alternative, hope it is suitable…

not that i completely understand the log, it looks like no response from TV (works fine with same cable on other boxes) suspecting some HW issue - miss soldered pin or something on HDMI port on the box…hope i am wrong tho!

thanks for you help so far!

As I thought, there is no response from your TV:

	Zeile 22246: 2021-02-21 11:53:16.795 T:5383    DEBUG <general>: CecLogMessage - << Broadcast (F) -> TV (0): POLL
	Zeile 22247: 2021-02-21 11:53:16.795 T:5383    DEBUG <general>: CecLogMessage - processor thread started
	Zeile 22248: 2021-02-21 11:53:16.796 T:5383    DEBUG <general>: CecLogMessage - << f0
	Zeile 22260: 2021-02-21 11:53:16.825 T:5383  WARNING <general>: CecLogMessage - Write: write failed
	Zeile 22261: 2021-02-21 11:53:16.827 T:5383    DEBUG <general>: CecLogMessage - << f0
	Zeile 22299: 2021-02-21 11:53:16.864 T:5383  WARNING <general>: CecLogMessage - Write: write failed

Maybe CEC is turned of on the TV or you have a hardware issue.

The message f0 does mean a broadcast “ping” of node 0 what is the TV and there is no answer.

OK Thanks for looking.

i think HW issue on the H96 Max as all my other boxes work on this TV with the same cable, suspect the ‘ping’ is not even getting to the HDMI cable. I also tested the box on another TV where my other boxes also work in case there was something specific between the Max and just that TV, but CEC not working on the second TV with that box also…

What is the status of WOL for the Odroid N2+ on CoreElec?
I tried running the inject_bl301 script but got:

System is not supported by BL301.bin injection: g12b_s922x_odroid_n2plus

@Menion maybe you are able to try last nightly with inject_bl301?

Doesn’t matter if 9.2 or v19. I fixed something about G12A devices as it needs another blob for a specified time range as Amlogic changed something in source.

So maybe it is working again with your device and firmware. But be aware that you may need to recover your device again if it doesn’t work.

Thank you.

@Portisch maybe you missed my post. I recover the box with a new firmware but this one has an older, already supported, bootloader so I am not able to test it with the newer uboot I had that caused the problem in injection

Aha, I missed this part, yes. Maybe it’s possible for you to flash the non working firmware and try if injection works now? Would just be nice to have confirmation before we doing the next stable release, thank you!

I don’t have the BL301 options on my Odroid N2+ running CoreElec 19 (matrix). It is supposed to be available?

I do have the Wake-on-lan option, and it is activated, but it is working half the time.

Please read forum more carefully!

WOL is working 100%

Yes I read the part where it says that Odroid are already supported, but again, with mine sometime it just does not start.
It seems to work flawlessly if the device is suspended. If I shut it down, sometimes WOL does not start the device and I have to unplug and replug. (I can see the WOL packets on the network)

Never mind, the TV is not powering on or prevent Odroid to power on, that’s all. (f**k CEC as always)

How do I find out if my TX3 is capable of using the the injection or not? I got mine via geekbuying, not AliExpress.

Hi, I have a broken M9C Max (S905x_2 / 16) (gxl_p212_2g.dtb) box after having followed the bl301-injection tutorial to the letter.

Process details

*CoreELEC:~ # inject_bl301 *
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: 210a8200e920b23dc5d3eeaaf7d6e0bf
Using CPU type GXL (21): S805X, S805Y, S905X, S905D, S905W, S905L, S905M2
Using binary type because of CoreELEC DT-ID: Generic
Using /dev/bootloader as bootloader partition

Found a valid Amlogic v2 ToC header (0xC200)
Amlogic magic: AMLC
Old signature ToC: C1575C02C371DCE3981BF3B0020687C0D2588353E21A6B63C8A0DEF06FD7A3F2
Name: AA640001
Serial Number: 12345678
Flags: 0
Found BL30 blob image at: 0x10200 (0xD600)
Found BL31 blob image at: 0x20200 (0x15400)
Amlogic magic: AMLC
Old signature bl30: 562069D80B05CBEA266A6AF91E71EF944BC7C054B1CB1AD39EF58120090074FD
Using bl301 blob: Generic_21_bl301.bin
Using bl30 blob: /gxl/bl30.bin
Use config.ini value: remotewakeup = 0x10015
Use config.ini value: decode_type = 0x00
Use config.ini value: remotewakeupmask = 0x10015
Use config.ini value: cec_osd_name = CoreELEC
New signature bl30: D5BAEF23DC26E1A99F9CE6C19A21EF1763A8724F7C2803FAA7E797885FE254FA
BL301.bin needs to be updated on eMMC
Old signature bl31: B96B87A7707937F374D294A07ACAF4CC8D1B3A290A5E2B14BEDC49A28589C3C2
BL31 time stamp: Built : 18:30:11, Nov 1 2016
Using bl31 blob: /gxl/bl31.img
New signature bl31: FCAE077E75CB84170D8D3E9F731CFDC1F173BC020082F3A5D65A68EFE2F2C30E
BL31.img needs to be updated on eMMC

Please confirm to write the bootloader blob BL301 to
the internal eMMC! Please ensure to update first the device
to the last vendor firmware! And remember if the vendor
firmware get updated you have to do this step again as the
bootloader blob will be overwritten!

Continue? [y/n] y

Warning! GXL support is still experimental!
It is possible that the injection brick your device and it will not boot anymore!
It will be needed to short out the eMMC to recover the Amlogic device.
So there is no warranty by team CoreELEC if the injection will be successful or not!
Please confirm again to write the bootloader blob BL301 to
the internal eMMC on your GXL device!

Continue? [y/n] y

Make backup of vendor bootloader to: /flash/210a8200e920b23dc5d3eeaaf7d6e0bf_bl301.bin

New signature ToC header: EFD4D6371A2AE04DA1DFA5F4BECC7F99390E4D08817478B65DA70D4530FB97D0
ToC header needs to be updated on eMMC

Finished update of BL3 blobs on internal eMMC!*
Please reboot device now and enjoy the new CoreELEC wake-up features!

End

After the process, the box remained with the indicator in intense red and does not respond to anything.
After seeing the output through the serial port, I realized that the problem is a faulty bootloader

I attach the backup of the bootloader210a8200e920b23dc5d3eeaaf7d6e0bf_bl301.bin (4 MB)

Is there any way that bl301-injection works for this box?
Sorry for my English

Did you use latest nightly before injection?

nop, the estable version. https://github.com/CoreELEC/CoreELEC/releases/download/19.0-Matrix/CoreELEC-Amlogic-ng.arm-19.0-Matrix-Generic.img.gz

Your bootloader is from 2016.
Please search a image with Android 7.

For M9C Max there is only Android 6.0.1
A custom ROM would serve as atvx?

Yes, I use ATV Experience v4 so you can dual boot (I only preserved the bootloader and installed CE 19 on nand with ceemmc -x). It’s a ATV Pie iteration. Also, “universal Aidan’s custom ROM”, 7.1.2 worked for this box.

Great. Could you share the bootloader you are using …?

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