The device is getting old, but let's infuse some energy into the otherwise lethargic community !!! :D
I am looking for a skillful volunteer in order to try to repeat the unbricking step from Fire 2015 :
http://ift.tt/29a97Iw
I've poked around, and found the Fire HD preloader sitting in /dev/block/mmcblk0boot0 (see the attached file). It does not seem to have any ANTI-ROLLBACK strings, but still bricks. It's definitely smaller than the version from Fire 2015, but the beginning of it looks similar. Regardless, the idea is to overwrite both UBOOT and TEE1 just like with Fire 2015. Please grab these from :
http://ift.tt/1qdUeGT ( 5.4.1_1133_stock_recovery_uboot.zip )
Please reply if you have a bricked Fire HD. The steps are very similar to Fire 2015, after figuring out the correct address, just write a recent version of UBOOT and TEE1 to the device using Python scripts, and in theory it should boot again.
@moroxoro, @notorious.dds, @CJD14, @DoLooper, @Gimzie, @kirito9, @sd_shadow, @Drevenu, @kyle12345109876, @Kramar111
I am looking for a skillful volunteer in order to try to repeat the unbricking step from Fire 2015 :
http://ift.tt/29a97Iw
I've poked around, and found the Fire HD preloader sitting in /dev/block/mmcblk0boot0 (see the attached file). It does not seem to have any ANTI-ROLLBACK strings, but still bricks. It's definitely smaller than the version from Fire 2015, but the beginning of it looks similar. Regardless, the idea is to overwrite both UBOOT and TEE1 just like with Fire 2015. Please grab these from :
http://ift.tt/1qdUeGT ( 5.4.1_1133_stock_recovery_uboot.zip )
Please reply if you have a bricked Fire HD. The steps are very similar to Fire 2015, after figuring out the correct address, just write a recent version of UBOOT and TEE1 to the device using Python scripts, and in theory it should boot again.
@moroxoro, @notorious.dds, @CJD14, @DoLooper, @Gimzie, @kirito9, @sd_shadow, @Drevenu, @kyle12345109876, @Kramar111
from xda-developers http://ift.tt/28USy4R
via IFTTT
No comments:
Post a Comment