Thanks for your guidance, I successfully re-flashed the bricked SBC with the Android firmware using the method you introduced today.
I think this is wrong. You have:
BL2 time stamp: Built : 14:02:05, Nov 23 2020
And there are existing bl301 for:
221119 and 091020
So correct should be 091020 not 221119.
What Android image from Banana Pi you using? Download link?
Hi, I used the Android firmware provided by their website download site.
and the version is 2021-10-28-bpi-m5-m2pro-mbox-android9-emmc.zip
You can see here:
And may I ask the reason as to why an Android image different from the one recommended by BPI and CoreELEC is being used?
The latest is generally considered more stable, and I think the Chinese are tired of promoting software updates, like the page links to the June firmware, but when the October update is already available, the page has not been modified yet.
Please update CE with this image:
After update you can try inject_bl301 again.
Thank you very much. big brother.
Wake up and CEC features are work fine now.
CoreELEC (community): 19.5-Matrix_devel_20220309142558 (Amlogic-ng.arm)
CoreELEC-bpi:~ # 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: 2b0b010001321f0000103833334e3050
Using CPU type SM1 (2b): S905X3, S905D3
Using binary type because of CoreELEC DT-ID: Bananapi_M2Pro
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
Old signature bl2:F55564B11F1F4CDD921E70DFAB0FB26695646FA1DB4AE5C9F48875C446B3E919
BL2 time stamp:Built : 14:02:05, Nov 23 2020. g12a g966c864 - gongwei.chen@droid11-sz
TOC ENTRY #3
UUID:D6D0EEA7FCEAD54B97829934F234B6E4
Offset Address: 0xA7B70 (absolute: 0xB7D80)
Size:0xBBA00
Flags: 0x0
Found BL33 blob image at:0x000B7D80
Amlogic magic: @AML
BL33 time stamp:U-Boot 2015.01 (Oct 28 2021 - 10:27:45)
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: E85B1E9CA0AB7BA12C15ADA4ED9A43236DDFE610F70697F9B0549E4F56837CBC
Using bl301 blobs from: 091020
Using bl301 blob:Bananapi_M2Pro_2b_bl301.bin
Use config.ini value:
remotewakeup = 0xbf40fe01
Use config.ini value:
decode_type = 0x00
Use config.ini value:
remotewakeupmask = 0xffffffff
Use config.ini value: cec_osd_name = CoreELEC
New signature bl30:4ABB591EF32EEEF330F6D23B7B3503A758EE8B441250B166776DCCA292C7BE44
BL301.bin 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
Make backup of vendor bootloader to: /flash/2b0b010001321f0000103833334e3050_bl301.bin
Finished update of BL3* blobs on internal eMMC!
Please reboot device now and enjoy the new CoreELEC wake-up features!
Good to know it finally worked for you.
Could you figure out in detail what was the key point different to your attempts before?
e.g. pressing SW4, or connection to micro-usbâŚ
This would really help to improve our Wiki.
1 Like
Press and hold SW4 is the key, other steps are the same as before, only by pressing and holding SW4, USB_Burning_Tool can recognize the SBC that has been bricked, and can re-brush the Android firmware.
This is a very clever circuit design, it should be similar to a jumper, but unfortunately you didnât announce it earlier, otherwise I wouldnât have to return it to the factory for maintenance.
2 Likes
Thanks for letting us know.
When I wrote the documentation, the eMMC module on the SBC was blank. It appears there is no need to invoke the switch with a blank module. Itâs good to know that in case the module has data on it, the switch needs to be used.
The Wiki has been updated accordingly.
1 Like
Thanks for everything the CE team has done for us, itâs really not easy, to support so many strange hardware, especially when the development team doesnât have enough hardware samples, I am very satisfied with this SBC at present, thank you again.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.