[Thor][Apollo] Unlocking bootloader with any firmware

[hdmodding]

Would anyone know what is casuing
"Error opening input file: 2 The system cannot find the file specified"
When running dd of=\\?\Device\Harddiskx\Partition6 if=aboot_vuln.mb and
dd of=\\?\Device\Harddiskx\Partition18 if=twrp_cubed.img (on windows 10)

 

[The-Frog]

Hi HDModding,

Yes, you cannot use 'harddiskx' in the line, the x should be the partition index value such as 'harddisk3' or 'harddisk1' or whatever the index value is from the previous steps ...

Hope this helps
The Frog

 

[aaa_plshelp]

Steps unlock bootloader and needed files

this is the details step for unlocking bootloader for the 2013 Kindle HDX 7 (Thor) and HDX 8.9 (Apollo). Becarefull the 2014 HDX 8.9 (Saturn) doesn't work! These steps are done in Windows 10, successfully checked by myselft!
i don't take any credits, just collect all the steps in one post of the whole process.

Download the needed files are in the attachment, just download them all + the TWRP for your device from this thread: TWRP 3.1.1-1
You do NOT need root for these steps!

1. Install the adb-setup-1.4.3 into a folder (for example: C:/adb), extract dd-0.5.zip + unlock.zip + aboot-xxx.zip, put dd.exe + get_code.bat + unlock.bat + twrp image (for your device) + aboot_vuln.mbn (for your device) into that folder. After that install the kindle_fire_usb_driver.
2. Turn on ADB-Debuging Mode in Developer Mod by tapping 7 times the build numbers in settings and connect to your computer + trust your device.
3. Excecute "get_code.bat" in the folder above, you will get a new file: unlock.code in the folder.
4. Open CMD in the folder and run "adb reboot bootloader", the Kindle will reboot to bootloader with "[ fastboot ]" on the display
5. On the Computer go to Device-Manager and change driver in "Other Android" to "Fire Devices - Android Adb Composite Driver" . It should say "Ready" on the Kindle.
6. Now we need to enter Bulk-Mode like the instruction in this thread: Bulk Mode
Type:






7. When done, hold down the power button until it reboots. Now you will be at Bootloader with [Fastboot] sign on the screen. Change the drive in Device-Manager again if needed.
8. Run the "unlock.bat" in the folder and you should get a green line: "unlock code is correct". Congrats your Kindle now has an unlocked bootloader.
9. Now hold power button again to shut down the device, then hold both "power button + Volume UP" and keep them for 3-5 seconds after you see the "kindle fire" logo. Then you will get into the TWRP and flash your desire things.

i hope this post will help others new member to free our beautifull devices!

Cheers and happy flashing

Hi, great post but I seem to have encountered a major problem... I followed all the steps till 6 and typed in the given into cmd but it did not return the same error but

C:\Users\DELL>dd of=\\?\Device\Harddisk1\Partition6 if=aboot_vuln.mbn​

rawwrite dd for windows version 0.5.​

Written by John Newbigin <[email protected]>​

This program is covered by the GPL. See copying.txt for details​

Error opening input file: 2 The system cannot find the file specified​

​

C:\Users\DELL>dd of=\\?\Device\Harddisk1\Partition18 if=twrp_cubed.img​

rawwrite dd for windows version 0.5.​

Written by John Newbigin <[email protected]>​

This program is covered by the GPL. See copying.txt for details​

Error opening input file: 2 The system cannot find the file specified​

Now the device will not power on or go into twrp... I suspect that I've made a rookie mistake somewhere and could have possibly hard bricked my device.

Additionally, every time I plug in the kindle to my pc it'll open multiple dialog boxes saying, "you need to format the disk before using it". Moreover, when connected the device is displayed as QHSUSB_BULK (which is supposed to be the kindle in bulk mode..?)

I would deeply appreciate any insight to complete the unlocking bootloader or recovering the fire os.
Thank you for your time.

 

[thomscon]

Worked for me on Apollo 4.5.5.3, thank you all.

[Thor][Apollo] Unlocking bootloader with any firmware

Hello. At first, I did not invent anything new, just checked some my guess on a other motherboard. All thanks and credits to our great developers. As always, all at your own risk. It does not work on the Fire HDX 8.9 (Saturn)! All steps in this...

forum.xda-developers.com

 

[hiitsrudd]

Why even bother to run an outdated version of android on this amazon crap?

 

[MMTalk]

Hi, great post but I seem to have encountered a major problem... I followed all the steps till 6 and typed in the given into cmd but it did not return the same error but

C:\Users\DELL>dd of=\\?\Device\Harddisk1\Partition6 if=aboot_vuln.mbn​

rawwrite dd for windows version 0.5.​

Written by John Newbigin <[email protected]>​

This program is covered by the GPL. See copying.txt for details​

Error opening input file: 2 The system cannot find the file specified​

​

C:\Users\DELL>dd of=\\?\Device\Harddisk1\Partition18 if=twrp_cubed.img​

rawwrite dd for windows version 0.5.​

Written by John Newbigin <[email protected]>​

This program is covered by the GPL. See copying.txt for details​

Error opening input file: 2 The system cannot find the file specified​

Now the device will not power on or go into twrp... I suspect that I've made a rookie mistake somewhere and could have possibly hard bricked my device.

Additionally, every time I plug in the kindle to my pc it'll open multiple dialog boxes saying, "you need to format the disk before using it". Moreover, when connected the device is displayed as QHSUSB_BULK (which is supposed to be the kindle in bulk mode..?)

I would deeply appreciate any insight to complete the unlocking bootloader or recovering the fire os.
Thank you for your time.

Trivial question, did you change the name of the downloaded aboot file "emmc_appsboot-13.3.2.3.2_user_323001720.mbn" to aboot_vuln.mbn? Same with the twrp file "thor-twrp-3.5.0_9.1.img" to twrp_cubed.img? And do you placed these two files in the same folder with the other files?

Even weeks after trying this you can resume trying again. I for myself had problems after the "wmic partition where index=22 get diskindex". I even unplugged fire hdx 7. Tried to turn it on without success. After 10 Min. I found the problem. I used PowerShell instead of a simple CMD Window. I plugged the fire hdx in and those several PC Window frames popped up again. I even played around with the power button of the fire hdx to see whats happens with those PC windows pooping up. Device was discovered and I changed the driver. The screen still was black and adb and fastboot didn't work. But 'wmic partition where index=22 get diskindex' worked and all those other following commands too.

 

[MMTalk]

Thx, i didnt wrote the result of wmic partition where index=22 get diskindex
wmic partition where (index=17 and numberofblocks=20480) get diskindex
wmic partition where (index=5 and numberofblocks

NOW i ve no acces... Hmm other ideas?

Try it again. See my previous post.

 

[aaa_plshelp]

Trivial question, did you change the name of the downloaded aboot file "emmc_appsboot-13.3.2.3.2_user_323001720.mbn" to aboot_vuln.mbn? Same with the twrp file "thor-twrp-3.5.0_9.1.img" to twrp_cubed.img? And do you placed these two files in the same folder with the other files?

Even weeks after trying this you can resume trying again. I for myself had problems after the "wmic partition where index=22 get diskindex". I even unplugged fire hdx 7. Tried to turn it on without success. After 10 Min. I found the problem. I used PowerShell instead of a simple CMD Window. I plugged the fire hdx in and those several PC Window frames popped up again. I even played around with the power button of the fire hdx to see whats happens with those PC windows pooping up. Device was discovered and I changed the driver. The screen still was black and adb and fastboot didn't work. But 'wmic partition where index=22 get diskindex' worked and all those other following commands too.

I didn't change the names of the files, I only downloaded the files attached to the original post and placed them in the abd folder.

Could you give more insight as to how exactly you revived your hdx and what commands you wrote in PowerShell? Moreover how did you get the device discovered again? I'm stuck with the fire in bulk mode while it's recognized as a drive instead of an android device... If I could undo the partition, I could possibly get the device working again though, I only know of theory of what to do, not the actual code.

I'm sorry if I'm asking too many questions but I'm quite desperate to fix the fire...

Thank you for your hopeful response.

 

[MMTalk]

I didn't change the names of the files, I only downloaded the files attached to the original post and placed them in the abd folder.

Could you give more insight as to how exactly you revived your hdx and what commands you wrote in PowerShell? Moreover how did you get the device discovered again? I'm stuck with the fire in bulk mode while it's recognized as a drive instead of an android device... If I could undo the partition, I could possibly get the device working again though, I only know of theory of what to do, not the actual code.

I'm sorry if I'm asking too many questions but I'm quite desperate to fix the fire...

Thank you for your hopeful response.

Are you trolling my? The command lines must refer to the downloaded files. Either you change the names of the downloaded files to the names in the command line or the other way around.

No I didn't change anything to revive the hdx. It can be that the battery of your fire hdx is completely down after weeks Connect it with the PC at least for 2 hours and try to charge it. Then unplug and replug it with the PC (Win10) and look if it it is discoverd in the device manager (second pic in #1206 here in the forum thread)? In the pic in #1206 it is discovered but you must set the driver renewed. If it can't be find press the start button of the fire hdx and hold it some moment so turn turn it on as usual. As the screen stays black the only way to see that the device is turned on is seeing it discoverd under the device manager on the PC (Win10). Is it discovered and the driver set renewed continue with the following command lines in cmd (NOT PowerShell, PowerShell caused the problem!!!):

wmic partition where index=22 get diskindex
wmic partition where (index=17 and numberofblocks=20480) get diskindex
wmic partition where (index=5 and numberofblocks=4096) get diskindex

dd of=\\?\Device\HarddiskX\Partition6 if=XXXX.mbn
dd of=\\?\Device\HarddiskX\Partition18 if=YYYY.img

with XXXX the name of the downloaded aboot file with the mbn extension
with YYYY the name of the downloaded twrp e.g. the recovery file with the img extension

 

[aaa_plshelp]

Are you trolling my? The command lines must refer to the downloaded files. Either you change the names of the downloaded files to the names in the command line or the other way around.

No I didn't change anything to revive the hdx. It can be that the battery of your fire hdx is completely down after weeks Connect it with the PC at least for 2 hours and try to charge it. Then unplug and replug it with the PC (Win10) and look if it it is discoverd in the device manager (second pic in #1206 here in the forum thread)? In the pic in #1206 it is discovered but you must set the driver renewed. If it can't be find press the start button of the fire hdx and hold it some moment so turn turn it on as usual. As the screen stays black the only way to see that the device is turned on is seeing it discoverd under the device manager on the PC (Win10). Is it discovered and the driver set renewed continue with the following command lines in cmd (NOT PowerShell, PowerShell caused the problem!!!):

wmic partition where index=22 get diskindex
wmic partition where (index=17 and numberofblocks=20480) get diskindex
wmic partition where (index=5 and numberofblocks=4096) get diskindex

dd of=\\?\Device\HarddiskX\Partition6 if=XXXX.mbn
dd of=\\?\Device\HarddiskX\Partition18 if=YYYY.img

with XXXX the name of the downloaded aboot file with the mbn extension
with YYYY the name of the downloaded twrp e.g. the recovery file with the img extension

i did complete the steps provided above and this time it was successful as in

C:\adb>dd of=\\?\Device\HarddiskX\Partition6 if=emmc_appsboot-13.3.2.3.2_user_323001720.mbn
rawwrite dd for windows version 0.5.
Written by John Newbigin <[email protected]>
This program is covered by the GPL.  See copying.txt for details
Error native opening file: 0 The operation completed successfully

C:\adb>dd of=\\?\Device\HarddiskX\Partition18 if=recovery.img
rawwrite dd for windows version 0.5.
Written by John Newbigin <[email protected]>
This program is covered by the GPL.  See copying.txt for details
Error native opening file: 0 The operation completed successfully

but now how to advance further?
i input fastboot -i 0x1949 erase aboot but it says waiting for devices (in device manager its given as android composite abd interface) and it cannot boot into twrp either. If i try to run the file manually through my computer, it says disc image file is corrupted?
For context, when i hold power + volume up it just displays all the drives and their format boxes....

 

[azazeldev]

Hey, I kinda messed up with the "get_code.bat". I got an empty key file and didn't notice, so I just continued to do everything until step 8, which is when I realized I couldn't continue. Now I'm stuck in either TWRP or [fastboot]. How do I get out or get my code?

Edit: I also started a thread here.