I ran this tool on my H96 Max X2 and it installed successfully. Then I followed the steps to update the config.ini. When I ran the “ir-keytable -u” command, the returns a “device not found” message. I am using the remote.conf specifically for this box that was mentioned in another thread by bazzle in this forum.
Any suggestions on how to address the “device not found” message? Thanks.
X96max 2g/16g - stuck in bootloop for CE but starts android if I pull the sd card.
I followed the Bl301 injection procedure and at first after rebooting nothing had changed and the remote did not power the box up.
It then became apparent that I needed to remove the # before the three relevant ir remote parameters in the /flash/config.ini file. (nowhere in the guide or config.ini file is this mentioned).
After doing so and rebooting I saw a warning about file corruption and giving 120 secs warning before an auto repair attempt. I powered it off then back up again and now with the sd card in the box just boot-loops.
How can I recover this? Is the /flash/config.ini file accessable from android?
Any help appreciated. Thanks
Move your SD card to an PC and edit the config.ini with an Unix compatible editor.
And yes, your right: you have to remove the # before the entry to activate it.
The bl301 injection does nothing change on boot process or on the SD card.
Only the part for wake-up is changed and you reach it only if you suspend or shut down the box from CE.
So if you got this warning with 120 seconds you modified something on the SD and it broke the file system. This can be happen like if you remove the SD card from the card reader without a sync of the card - as example.
Without any log we can not help anymore further - only that you may have to create a new CE SD card.
I was able to edit the config.ini back to default but it did not help.
I may have neglected the ‘sync && reboot’ after the editing the config.ini for the last time and corrupted the sd card.
Now starting again from scratch. Thanks
Update: All working now
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: 280b4000011a1400000f383052534b50
Using CPU type G12A (28): S905D2, S905X2
Using binary type because of CoreELEC DT-ID: Generic
Using /dev/bootloader as bootloader partition
Can’t not find TOC_HEADER!
does this mean that due to bl301 I can’t turn on the device with the remote control?
cannot be configured without using bl301?
I am referring to these commands
blgtmini:~ # 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: 280b40000xx71800000xx4354b48xxxx
Using CPU type G12A (28): S905D2, S905X2
Using binary type because of CoreELEC DT-ID: Generic
Using /dev/bootloader as bootloader partition
Found TOC_HEADER at: 0x00010210
Name: AA640001
Serial Number: 12345678
Flags: 0
TOC ENTRY #0
UUID: 9766FxxD89BEExx9AE5D78Axx0608xxx
Offset Address: 0x5C000 (absolute: 0x6C210)
Size: 0xE570
Flags: 0x0
Found BL30 blob image at: 0x0006C210
Amlogic magic: @AML
Old signature: EDCBF47E5F527D8AD93AE5962D8F01B615B7C02AE1498774
B41CA45056BE9A69
Using BL301.bin: Generic_28_29_bl301.bin
New signature: EDCBF47E5F527D8AD93AE5962D8F01B615B7C02AE1498774
B41CA45056BE9A69
Update of BL301.bin on eMMC is not needed, exit now...
But after a reboot and then shutting down using the Kodi GUI the box still won’t start by pressing the power button on the remote.
I’ve not read the whole thread, yet, but I also tried:
fw_setenv upgrade_step 3
reboot, shutdown, still no reaction.
Some more info (happy to provide more!):
blgtmini:~ # fw_printenv bootfromsd
bootfromsd=if mmcinfo; then run cfgloadsd; if fatload mmc 0 ${loadaddr} kernel.i
mg; then run sddtb; setenv bootargs ${bootargs} bootfromsd; bootm; fi; fi
Hi, I have an X96 Air P2 (S905x3, 4gb/32gb, dual band wifi, gigabit ethernet). If I shutdown the box from Android the remote can turn it back on fine, if I shutdown from coreelec the remote can’t turn it back on and I have to toggle the power, any ideas as it’s super inconvenient.
Can this sort it? I’ve noticed on the nightlies it’s built into the coreelec menu now although the “IR Remote Power Code” has limited options and not matched mine so I’ve not tried it. Assistance appreciated.
I haven’t run it yet as it doesn’t list it as the S905X3 as compatible so I was asking if it was safe, I’ve seen it in the coreelec menu but it only had limited options and you can’t see the code to check it matches mine, does it use the config.ini if I don’t select one of those? Also should the config.ini be totally empty other than just the wake up code?
Thanks