[Thor][Apollo] Unlocking bootloader with any firmware

DB126 · Jan 16, 2018

draxie said:
Well... I'm not a mind reader... (-;
The person said they didn't know how to use TWRP flash a ROM,
and wanted to do more 'research'; so, it sounded counter-productive
to tell them to do just that. BUT: apparently, they were happy to do
that in any case... ODD... how people say one thing and mean another. :^)

Chalk it up to a bit of experience navigating choppy waters

draxie said:
Based on what was reported, the bootloader unlock worked.
The more likely scenario is that the aboot and TWRP images
got swapped on the first flashing attempt (hence the failed
boot attempt, with the device still in bulk mode), and only
aboot got reflashed to the correct partition, meaning that
the recovery partition of that device likely holds aboot and
NOT TWRP. Depeding on how much gets screwed up and
where later on, this _can_ prove to be a fatal mistake. I'd say
it would be wise to make sure the recovery partition has TWRP
on it; especially, since this is trivially achieved from fastboot on
unlocked HW...

Code:

fastboot flash recovery twrp_cubed.img

@webby2018 - heed @draxie's guidance on this item which clearly trumps my casual speculations. Trivial to implement (especially given your growing familiarity working with fastboot) and a wise precaution to avoid a potential unpleasant visit to the poop-pit.

webby2018 · Jan 16, 2018

Davey126 said:
Chalk it up to a bit of experience navigating choppy waters

@webby2018 - heed @draxie's guidance on this item which clearly trumps my casual speculations. Trivial to implement (especially given your growing familiarity working with fastboot) and a wise precaution to avoid a potential unpleasant visit to the poop-pit.

OK. I've done this and now can power+volup into TWRP (thanks @draxie).

I'm downloading the Nexus rom now but I would like to restore the original FireOS, I like to always have a rollback point when doing kind of things, and I'm still unclear how to do this.

I haven't touched the boot partition so I now assume that if I flash the original aboot (emmc_aboot.mbn) then this will boot into FireOS but @draxie said there may be issues if recovery contains TWRP so where do I get the original recovery partition to flash (restore)?

DB126 · Jan 17, 2018

webby2018 said:
OK. I've done this and now can power+volup into TWRP (thanks @draxie).

I'm downloading the Nexus rom now but I would like to restore the original FireOS, I like to always have a rollback point when doing kind of things, and I'm still unclear how to do this.

I haven't touched the boot partition so I now assume that if I flash the original aboot (emmc_aboot.mbn) then this will boot into FireOS but @draxie said there may be issues if recovery contains TWRP so where do I get the original recovery partition to flash (restore)?

You can preserve your current FireOS config via the backup function in TWRP. Tap Backup then select System, Data and Boot partitions. On HDX devices the output file must be written on device so you must have sufficient free space. If not you'll need to backup one partition at a time. Data will likely be the largest. When complete tether your device and copy the dated folder under TWRP->{serial} to the host. Copy the folder, not the individual files contained in the folder. Then delete the dated folder. Do not delete the parent {serial} folder.

Note you will not be able to restore and execute the FireOS backup(s) without making the accommodations outlined by @draxie. I am not a fan of replacing the original aboot at this stage of the game. A borked aboot flash will ruin your day and possibly yield an unrecoverable device. Recommend installing Nexus and moving forward. The fewer brain surgeries the better.

webby2018 · Jan 17, 2018

Davey126 said:
You can preserve your current FireOS config via the backup function in TWRP. Tap Backup then select System, Data and Boot partitions. On HDX devices the output file must be written on device so you must have sufficient free space. If not you'll need to backup one partition at a time. Data will likely be the largest. When complete tether your device and copy the dated folder under TWRP->{serial} to the host. Copy the folder, not the individual files contained in the folder. Then delete the dated folder. Do not delete the parent {serial} folder.

Note you will not be able to restore and execute the FireOS backup(s) without making the accommodations outlined by @draxie. I am not a fan of replacing the original aboot at this stage of the game. A borked aboot flash will ruin your day and possibly yield an unrecoverable device. Recommend installing Nexus and moving forward. The fewer brain surgeries the better.

---------- Post added at 02:32 AM ---------- Previous post was at 02:30 AM ----------

You can preserve your current FireOS config via the backup function in TWRP. Tap Backup then select System, Data and Boot partitions. On HDX devices the output file must be written on device so you must have sufficient free space. If not you'll need to backup one partition at a time. Data will likely be the largest. When complete tether your device and copy the dated folder under TWRP->{serial} to the host. Copy the folder, not the individual files contained in the folder. Then delete the dated folder. Do not delete the parent {serial} folder.

Note you will not be able to restore and execute the FireOS backup(s) without making the accommodations outlined by @draxie. I am not a fan of replacing the original aboot at this stage of the game. A borked aboot flash will ruin your day and possibly yield an unrecoverable device. Recommend installing Nexus and moving forward. The fewer brain surgeries the better.

Yep. Have since gone onto Nexus as you suggested earlier. Had a problem with TWRP 3.1.1-0 where I kept getting a error 7: "Can't install this package . . . over newer build" even after a full wipe. Found a reference to reverting back to version 3.0.0-1 which worked for me so Nexus will be my rollback point until I eventually go to a 7.x OS which is my current goal.

Thanks for your help and @draxie

DB126 · Jan 17, 2018

webby2018 said:
Yep. Have since gone onto Nexus as you suggested earlier. Had a problem with TWRP 3.1.1-0 where I kept getting a error 7: "Can't install this package . . . over newer build" even after a full wipe. Found a reference to reverting back to version 3.0.0-1 which worked for me so Nexus will be my rollback point until I eventually go to a 7.x OS which is my current goal.

Thanks for your help and @draxie

Great! All of the custom Android 7 builds for this device are stable and feature complete with a couple caveats. My current preference is AospExtended as it closely mirrors AOSP/Nexus which is effectively 'pure Android'. The previously mentioned caveats involve display, audio, WiFi and Bluetooth support. All work but are not always seamless due to a wonky Amazon kernel dating to Android 4.x that does not always play nicely with modern roms. There are workarounds for most issues and not everyone runs into problems. Just a heads-up.

ReichMann · Jan 21, 2018

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:

Code:
Code:

fastboot -i 0x1949 erase aboot fastboot -i 0x1949 reboot

NB: this will be scary as you'll lose 'fastboot' and only see a black screen.
Your device should reboot into "bulk mode" resulting in a number of pop-up
windows asking to format all the partitions that get exposed (at least, on Windows 10).
DO NOT format anything! Follow the above instructions instead.

Code:
Open a command window (cmd) and run the following commands:

Code:

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

All three of the above commands should return the same DiskIndex. Let's call that index X.

In the command window, run the following two commands with the right aboot&twrp files for your device
(you will need to substitute the DiskIndex X from above in place of the X):

Code:

dd of=\\?\Device\HarddiskX\Partition6 if=aboot_vuln.mbn dd of=\\?\Device\HarddiskX\Partition18 if=twrp_cubed.img

This error message on the first command seems normal: "Error reading file: 87 The parameter is incorrect"
NB: make sure you run both commands! Without TWRP, you'll get a brick.

Wait a few minutes for good measure; then, keep holding Power + VolUp until your device enters TWRP.

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

mrw187 · Jan 22, 2018

ReichMann said:
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

Will this work for 4.5.5.3?

ReichMann · Jan 22, 2018

mrw187 said:
Will this work for 4.5.5.3?

I tried with 4.5.5.2 but this should work with *ANY* firmware like mentioned in the OP.

Good luck!

mrw187 · Jan 22, 2018

ReichMann said:
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

ReichMann said:
I tried with 4.5.5.2 but this should work with *ANY* firmware like mentioned in the OP.

Good luck!

Worked all good. Now on aosp 7.1.2

mydanuyen · Feb 1, 2018

link die . please reload link download

DB126 · Feb 1, 2018

mydanuyen said:
link die . please reload link download

A thread search would have yielded this: https://xdaforums.com/kindle-fire-h...ing-bootloader-firmware-t3463982/post75284993

mancoh51 · Feb 2, 2018

I have hit a dead end

ONYXis said:
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 manual are not necessary but they are present for maximum safety. So I highly recommend do anything exactly in this way. Sorry my English as always =)

Update: now you can use updated draxie's utility - http://xdaforums.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014

Prerequisites for Installation
- Root
- Installed adb and fastboot drivers - official - https://drive.google.com/open?id=0B2twXJIOgv-UWWdwRl9TQS11b0k (if your system language not English, after fail navigate to "Program Files (x86)\Lab126\drivers" and run dpinst.exe /EL or switch to English =) for x64 need to disable driver signature verification before install ) also you can use pdanet drivers - http://xdaforums.com/showpost.php?p=59268023&postcount=8

Manual:
1. Create unlock file following this instruction - https://xdaforums.com/kindle-fire-h...r-firmware-t3463982/post70881555#post70881555

2. Flash old vulnarable aboot and cubed twrp (just in case). Check that all these commands executed without errors. If you'll get one - read second post below. If your firmware <=13(14)3.2.3.2 skip this step.
Download aboot and twrp for Thor (Kindle Fire HDX 7) https://drive.google.com/open?id=0B2twXJIOgv-UMGxXMUZPZTlZTUk or for Apollo (Kindle Fire HDX 8.9) - https://drive.google.com/open?id=0B2twXJIOgv-URzJDQkczNzRLaHM - and put this two files (twrp_cubed.img and aboot_vuln.mbn) into root of your kindle internal storage.
Run:

Code:

adb shell su dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot

Now you have working twrp recovery. It already works even without unlocked bootloader. You could boot into it by holding volUP during grey kindle logo. But no need to flash anything until unlock. At this point this is just emergency tool if something goes wrong =)

3. Flash unlock file.
Now, if you reboot, you will go straight into fastboot because of old aboot - newest boot.img can't load with it. If your firmware <13(14).4.1.1 you need run "adb reboot bootloader" to boot into fastboot.
Time to flash your unlock file.

Code:

fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock

You must obtain "unlock code is correct".
Grats. You are perfect =)
You can flash:
CM13 - http://xdaforums.com/kindle-fire-hdx/orig-development/rom-cm-13-kindle-hdx-2015-11-29-t3259732
CM 12.1 - http://xdaforums.com/kindle-fire-hdx/development/rom-cm-12-unofficial-apollo-thor-t3050199
Or stock repacked latest 4.5.5.2 rom - https://drive.google.com/open?id=0B2twXJIOgv-UVFFtN2RYNXNUZ0k (13.x - thor, 14.x - apollo)
Do not flash original stock firmwares.

Regards and thank to all - @dpeddi, @vortox, @draxie, @ggow, @Ralekdev, @jcase, @Hashcode
And greatest thanks for motherboard for my experiments to @MahmudS !

Hi all. I followed all the steps. When I get to step three (https://xdaforums.com/kindle-fire-h...firmware-t3463982/post70881555#post70881555)- I just get FAIL: Unlock Code is NOT correct. Here is what I get in Terminal after running unlock.bat

"/Users/MannyCohen/Downloads/unlock/unlock.bat: line 2: /Users/MannyCohen/Downloads/unlock: is a directory
error: no devices found
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.087s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.144s
/Users/MannyCohen/Downloads/unlock/unlock.bat: line 7: pause: command not found
"
Can someone help?
I can't go into my device to fix anything, because I can only boot into fastboot, and also TWRP.

DB126 · Feb 2, 2018

mancoh51 said:
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 manual are not necessary but they are present for maximum safety. So I highly recommend do anything exactly in this way. Sorry my English as always =)

Update: now you can use updated draxie's utility - http://xdaforums.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014

Prerequisites for Installation
- Root
- Installed adb and fastboot drivers - official - https://drive.google.com/open?id=0B2twXJIOgv-UWWdwRl9TQS11b0k (if your system language not English, after fail navigate to "Program Files (x86)\Lab126\drivers" and run dpinst.exe /EL or switch to English =) for x64 need to disable driver signature verification before install ) also you can use pdanet drivers - http://xdaforums.com/showpost.php?p=59268023&postcount=8

Manual:
1. Create unlock file following this instruction - https://xdaforums.com/kindle-fire-h...r-firmware-t3463982/post70881555#post70881555

2. Flash old vulnarable aboot and cubed twrp (just in case). Check that all these commands executed without errors. If you'll get one - read second post below. If your firmware <=13(14)3.2.3.2 skip this step.
Download aboot and twrp for Thor (Kindle Fire HDX 7) https://drive.google.com/open?id=0B2twXJIOgv-UMGxXMUZPZTlZTUk or for Apollo (Kindle Fire HDX 8.9) - https://drive.google.com/open?id=0B2twXJIOgv-URzJDQkczNzRLaHM - and put this two files (twrp_cubed.img and aboot_vuln.mbn) into root of your kindle internal storage.
Run:

Now you have working twrp recovery. It already works even without unlocked bootloader. You could boot into it by holding volUP during grey kindle logo. But no need to flash anything until unlock. At this point this is just emergency tool if something goes wrong =)

3. Flash unlock file.
Now, if you reboot, you will go straight into fastboot because of old aboot - newest boot.img can't load with it. If your firmware <13(14).4.1.1 you need run "adb reboot bootloader" to boot into fastboot.
Time to flash your unlock file.

Hi all. I followed all the steps. When I get to step three (https://xdaforums.com/kindle-fire-h...firmware-t3463982/post70881555#post70881555)- I just get FAIL: Unlock Code is NOT correct. Here is what I get in Terminal after running unlock.bat

"/Users/MannyCohen/Downloads/unlock/unlock.bat: line 2: /Users/MannyCohen/Downloads/unlock: is a directory
error: no devices found
target reported max download size of 536870912 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.087s]
writing 'unlock'...
FAILED (remote: Unlock code is NOT correct)
finished. total time: 0.144s
/Users/MannyCohen/Downloads/unlock/unlock.bat: line 7: pause: command not found
"
Can someone help?
I can't go into my device to fix anything, because I can only boot into fastboot, and also TWRP.

First - please don't cross post similar information in multiple threads; patience is a virtue.

Appears files are located in the downloads folder on the 'host' which I assume is a Windows machine. I doubt that is where the adb and fastboot executables are located.

There appears to be a conflict with a file/folder named 'unlock'. Might check to see if that exists and rename it. Also note the batch file is designed to run in a Windows command window (not terminal) and assumes your device tethered and accessible via adb. You might get the batch command to run while booted into TWRP; doubt it.

While there are ways around the latter obstacle the best path IMHO is to install and older ROM via TWRP that does not require and unlocked bootloader. Then start over with the procedure to generate an unlock code. You also want to be certain that a vulnerable aboot has indeed been installed (step #2) and that is a firm prerequisite to unlocking the bootloader. Finally, installing an older ROM will verify the device doesn't have other issues.

In short, install the ROM linked below, verify device stability and post back for further guidance if needed.

https://xdaforums.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931

fosterreichert · Feb 4, 2018

Help Please:

< waiting for device >
target reported max download size of 114294784 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.019s]
writing 'unlock'...
FAILED (remote: unlock code error)
finished. total time: 0.031s
Press any key to continue . . .

DB126 · Feb 4, 2018

fosterreichert said:
Help Please:

< waiting for device >
target reported max download size of 114294784 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.019s]
writing 'unlock'...
FAILED (remote: unlock code error)
finished. total time: 0.031s
Press any key to continue . . .

Did you install a vulnerable aboot (step #2 in OP) prior to attempting to unlock the bootloader?

draxie · Feb 6, 2018

Davey126 said:
First - please don't cross post similar information in multiple threads; patience is a virtue.

Appears files are located in the downloads folder on the 'host' which I assume is a Windows machine. I doubt that is where the adb and fastboot executables are located.

There appears to be a conflict with a file/folder named 'unlock'. Might check to see if that exists and rename it. Also note the batch file is designed to run in a Windows command window (not terminal) and assumes your device tethered and accessible via adb. You might get the batch command to run while booted into TWRP; doubt it.

While there are ways around the latter obstacle the best path IMHO is to install and older ROM via TWRP that does not require and unlocked bootloader. Then start over with the procedure to generate an unlock code. You also want to be certain that a vulnerable aboot has indeed been installed (step #2) and that is a firm prerequisite to unlocking the bootloader. Finally, installing an older ROM will verify the device doesn't have other issues.

In short, install the ROM linked below, verify device stability and post back for further guidance if needed.

https://xdaforums.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931

Actually, based on the paths and the reference to Terminal, my guess is that someone's
trying to run a batch file intended for Windows on a Mac. They should be using the similarly
name shell script instead...

mancoh51 · Feb 6, 2018

Davey126 said:
First - please don't cross post similar information in multiple threads; patience is a virtue.

Appears files are located in the downloads folder on the 'host' which I assume is a Windows machine. I doubt that is where the adb and fastboot executables are located.

There appears to be a conflict with a file/folder named 'unlock'. Might check to see if that exists and rename it. Also note the batch file is designed to run in a Windows command window (not terminal) and assumes your device tethered and accessible via adb. You might get the batch command to run while booted into TWRP; doubt it.

While there are ways around the latter obstacle the best path IMHO is to install and older ROM via TWRP that does not require and unlocked bootloader. Then start over with the procedure to generate an unlock code. You also want to be certain that a vulnerable aboot has indeed been installed (step #2) and that is a firm prerequisite to unlocking the bootloader. Finally, installing an older ROM will verify the device doesn't have other issues.

In short, install the ROM linked below, verify device stability and post back for further guidance if needed.

https://xdaforums.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931

Will try soon, thanks for the help!

nikobaldt · Feb 14, 2018

Works perfectly

ReichMann said:
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

This guide works perfectly. The only difference: the commands

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

have an error message but the first command

wmic partition where index=22 get diskindex

returned the right index.

Thank you for that. After that I installed CM14.1.

My device: Kindle Fire HDX 8.9 (Apollo), FireOS 4.5.5.3

ubergeek71 · Feb 16, 2018

Cubed TWRP?

Greetings,

Thor and I have been happy users of the Fire Nexus ROM for a couple of years, so a big thanks to all who were involved in that!

I feel that it's time to update to something like AospExtended because why not?

I've taken some time to familiarize myself with the instructions in this and other threads, and I believe I have assembled almost all of the necessary pieces (I'm able to run get_code.bat, for example). But there's one puzzle remaining: the continued reference to the "cubed" TWRP, for which there don't appear to be any working links.

The most recent instructions from @ReichMann imply that one can just use TWRP 3.1.1-1, although the details still refer to twrp_cubed.img. So I just wanted to be sure that I can use 3.1.1-1, or if I still need to find this elusive "cubed" version somewhere.

Thanks for the help!

draxie · Feb 17, 2018

Good to go!

ubergeek71 said:
Greetings,

Thor and I have been happy users of the Fire Nexus ROM for a couple of years, so a big thanks to all who were involved in that!

I feel that it's time to update to something like AospExtended because why not?

I've taken some time to familiarize myself with the instructions in this and other threads, and I believe I have assembled almost all of the necessary pieces (I'm able to run get_code.bat, for example). But there's one puzzle remaining: the continued reference to the "cubed" TWRP, for which there don't appear to be any working links.

The most recent instructions from @ReichMann imply that one can just use TWRP 3.1.1-1, although the details still refer to twrp_cubed.img. So I just wanted to be sure that I can use 3.1.1-1, or if I still need to find this elusive "cubed" version somewhere.

Thanks for the help!

All *RECENT* TWRP images(3.0.2 and beyond) released by @ggow appear to be fake-signed (i.e. "cubed'").
You can either rename the file or change the reference in the command to the actual filename you have...

[Thor][Apollo] Unlocking bootloader with any firmware

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

New member

Senior Member

Senior Member

Member

New member

Member

Senior Member

Similar threads

Top Liked Posts