yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" General] DB126:
Glad you got it sorted. A bootable ROM isn't strictly necessary but it does facilitate following the bootloader unlock guidance as written. Enjoy your device and Slim7.
[Kindle Fire HDX 7" & 8.9" General] av99315:
Stuck in fastboot with NO UNLOCK CODE

So I booted into fastboot mode, it appears my code wasn´t done correctly and now I don´t know if there is a way to generate it again without the IDs (Genious, I know). If not, what ROM does not require unlocked bootloader?

Edit: I flashed NEXUS ROM and got the unlock code, but when I run the "fastboot -i 0x1949 flash unlock 0x45251872a5.unlock"

I get "error: cannot load 0x45251872a5.unlock: no such file or directory" even tho I have the unlock.code file in "plataform-tools"
[Kindle Fire HDX 7" & 8.9" General] DB126:
- verify unlock file is not empty (0 bytes)

- verify the fastboot command being executed actually lives in the "platform-tools" directory (many hosts have multiple fastboot.exe files)

- verify file identifier is correct (obvious)

- try including an explicit path reference to the fastboot command, eg: fastboot -i 0x1949 flash unlock c:\<directory>\<directory>\....\platform-tools\0x45251872a5.unlock
[Kindle Fire HDX 7" & 8.9" General] av99315:
Thank you for taking the time to answer!

1. File is 1kb.

2. How do I know that? I have never used the adb before so I have no idea, but it could be a problem, I assumed it was "living" in the plataform-tools just because that is where I was in my cmd when I executed adb.exe and the fastboot command

3. I get 0x000045 and 0x251870a5, I have tried this many times and get the same.

4. Did it, did not work unfortunatelly. :(

Appreciate your help! :)

Edit: in my previous comment I wrote 0x251872a5 as a typo, but belive me, I have verified what I put on the console many times with the correct code. :)

Edit 2: SOVED! Insted of executing "fastboot -i 0x1949 flash unlock c:\<directory>\<directory>\....\platform-tools\0x45251872a5.unlock", I just executed unlock.bat as pointed here: https://xdaforums.com/kin...5#post70881555. I feel bad for wasting your time, have a nice day :D
[Kindle Fire HDX 7" & 8.9" General] DB126:
Glad you got it sorted. To be honest I wasn't sure why you were not executing unlock.bat but assumed there was a valid reason and didn't question it. Never dawned on me that you had overlooked the option.
[Kindle Fire HDX 7" & 8.9" General] st0wz:
on the stock rom (has unlocked bootloader and installed stock with a zip file)

my Serial number is 0000 0000 0000 0000 and I can't register device. Plz help
[Kindle Fire HDX 7" & 8.9" General] brycesub:
When running unlock.bat I receive the message "Partition does not exist." Any thoughts here?
[Kindle Fire HDX 7" & 8.9" General] bluecoyote:
After dropping this project since last Feb or so, I was able to rescue my strangely broken device (HDX 8.9) and install a current ROM/GAPPS. It does take a certain amount of reading thru and getting the right files/drivers, but it does work and works well!!

Thanks a million!

:D
[Kindle Fire HDX 7" & 8.9" General] aerosmesh:
Something wrong

I think i did the steps well.

1. Get root through Kingroot

2. Get unlock code

3. Install TWRP and other file

4. Flash unlock

After flash unlock file, i tried to reboot my tablet to access TWRP, instead the sreen goes black, all black, no text or logos, nothing, but if i plug on PC it detects and even accept commands via fastboot, besides i cannot flash TWRP once again, it appears as a no such file directory in fastboot interface.

Can anyone help me with some commands i can use?

I guess this is a minor issue but i don't know.

My device is an apollo with 4.5.5.2 installed originally.

Thanks in advance.

P.D. I think maybe occurs some kind of error on unlock bootloader, how can i check this?
[Kindle Fire HDX 7" & 8.9" General] DB126:
Thinking you may have flashed the wrong aboot or file was corrupt. You *might* be able to recover from 'bulk mode'. I am travelling the next few days and can not help with the details.

[MENTION=5828306]draxie[/MENTION]?
[Kindle Fire HDX 7" & 8.9" General] rommel19540:
Step 2??

hey where is the original post or what is step 2?

---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------

Hey can you let me know where the original post is or what is step 2 after clicking on get-code.bat file?

---------- Post added at 10:06 PM ---------- Previous post was at 09:59 PM ----------

Hey whats up folks. I'm new too this so please bare with me and my newbie questions but the other night I successfully rooted my kindle3rd gen 4.5.5.2. I guess thats a thor LOL. My question is what should be my next step? Do I need to unlock the bootloader and install recovery program? I want to get the google store on my device but not sure what the next step should be.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Take it easy

The "original post" is the first post in the thread where you copied from.

You seem to have a minor attitude problem. That's what's up.

If all you want is Google Play, you do NOT need to unlock

the bootloader and install a custom ROM. By exercising

some search-fu, you'll find separate instructions for that.

If you want to liberate your Kindle from FireOS (anno 2013)

and use something more modern instead, you will have to

unlock, and you seem to have found the right instructions

already; so, just go ahead...

---------- Post added at 08:54 ---------- Previous post was at 08:45 ----------

OK. So, my posts got merged (I _really_ hate this feature).

The above is for [MENTION=7855273]rommel19540[/MENTION], but starting from this point

I'm answering to [MENTION=5488402]Davey126[/MENTION] and ultimately [MENTION=6184880]aerosmesh[/MENTION]

All black screen, but fastboot still works? That's _strange_...

BUT, if you have fastboot, you should be able to recover

following these instructions.

NOTE: since you're starting from fastboot mode,

you'll need to execute the two fastboot commands

shown _below_ steps 1-4 *first* to get into bulk mode,

and *then* perform the numbered steps.

Let us know how it went!
[Kindle Fire HDX 7" & 8.9" General] tismond:
I used twrp to flash LOS14 and open nano gapps on Kindle fire Thor. Everything went well until i started to adjust the settings of the the device then trebuchet started force closing. I decided to reboot the devicewould help, it did not. I then rebooted to twrp to see i could reflash the OS but when the OS was being flashed it gets stuck at "patching system image unconditionally". I tried slim rom and go the same result. I tried flashing Supersu 2.82 just to see if twrp was still working and i was able to flash it. I kept retrying the flashing of the OS but got the same problem again and again. at one point when i was holding down power + vol up to get to twrp i ended up putting the kindle into bulk mode. I followed the instructions in the last post but i am unable to get out of the bulk mode. I am assuming it is because I was not able to erase aboot.

Give all that i have stated above any assistance would be welcomed. Please note that while i await a response i would still be researching a way out of this predicament.

I am able to get back into twrp and fastboot i just had to wait a little longer after trying the commands from last post. However i am still stuck at "patching system image unconditionally
[Kindle Fire HDX 7" & 8.9" General] cantrelly69247:
getting unlock code incorrect

Iv'e been at this forever, I rooted with kingroot and verified root success with cpu-z.. I have installed and updated drivers manually from pdanet and amazon...get code.bat succeeds and says code generated. then i run unlock.bat and it fails.. I have hdx 8.9 3rd gen apollo with os 4.5.5.2. can someone please tell me what im doing wrong here? thanks
[Kindle Fire HDX 7" & 8.9" General] DB126:
Did you follow step #2 in the OP?

---------- Post added at 05:16 AM ---------- Previous post was at 05:10 AM ----------

No place are wipes mentioned; assume they are being performed prior to each flash attempt (especially when switching ROMs). Also make sure you have the latest TWRP build installed. Some previous builds were problematic.

Given the unusual behavior on Lineage 14 and subsequent issues your device could be facing HW issues w/NAND storage.
[Kindle Fire HDX 7" & 8.9" General] cantrelly69247:
unlock code incorrect

yes I flashed twrp and it was a success and now it boots into fastboot when i try to reboot..but it keeps saying incorrect unlock code and i cant go any further
[Kindle Fire HDX 7" & 8.9" General] cantrelly69247:
I finally got it.. i wiped with twrp to clear wifi data to stop it from updating ota, flashed repacked stock 4.5.5.2 then rebooted and retried unlock.bat process and it succeeded.. I then flashed cm 12.1.....works great....thanks for your input
[Kindle Fire HDX 7" & 8.9" General] DB126:
Great! Enjoy your liberated device!

FWIW - CM 12.1 is a fine ROM for this device and has been my daily driver for well over a year. That said, Lineage 14 is probably a better choice unless you need to remain on a lower Android build. In my case a messaging app and Xposed dependencies are the culprits. Older CM based ROMs also feature a suite of persistent wakelocks, which can not be disabled, triggering a zombie battery drain while the device sleeps. Typical loss (on Thor) is 0.5% per hour versus <0.2% with other ROMs.

Edit: Aside from Lineage there are several other Android 7.x (Nougat) based ROMs for this device including Slim 7 and Resurrection Remix.
[Kindle Fire HDX 7" & 8.9" General] tismond:
Yes I did do the necessary wipes before and after loading or attempting to load ROMS. I had feared it might be NAND storage issues. Thanks for your response.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Try flashing the repackaged FireOS 4.5.5.2 ROM linked in the OP which is less sensitive to TWRP build anomalies. If that fails your device is likely toast. If it works try reflashing the ROM of your choice following the usual wipes. Yes, it seems weird but has proven to be a successful path for others. Good luck.
[Kindle Fire HDX 7" & 8.9" General] tismond:
It seems i am getting an issue copying the larger roms and gapps from my pc to internal storage on the kindle. It seems that the files dont copy correctly or not in their entirety, or sometimes it just stops short.

I am able to load the older marshmallow or kitkat roms but i get lots of force closures. Right now i am running HDX_Nexus_ROM_Thor-v4.0.5. thanks for all your help
[Kindle Fire HDX 7" & 8.9" General] DB126:
Force closures are unrelated to the corrupted downloads. Given the reported symptoms it would appear your device has a hardware problem.
[Kindle Fire HDX 7" & 8.9" General] tismond:
most definitely a hardware problem. I cannot copy any file that is larger than 200MB from my PC to the kindle. I managed to laod a kitkat rom and it works but i get random reboots. i tried downloading a ROM that is 299MB and just when it reached the 200MB mark in the download the tablet rebooted.

Thanks for all your help.

Now i am not sure what to do with my brick.LOL
[Kindle Fire HDX 7" & 8.9" General] draxie:
KingRoot?

Do you get that odd data transfer behavior in TWRP?

If yes, that's bad, but if not, continue reading...

Just at the off-chance that this might make a difference,

did you by any chance root your device using KingRoot;

and, if so, did you make sure to also wipe *data* and

*internal storage*?
[Kindle Fire HDX 7" & 8.9" General] IErziI:
Ok guys! I hope u can help me. :)

i did all steps until step 3. But i cant use my fastboot. My kindle (Thor) just starting to fastboot, but there is no 'ready'. On windows i cant use fastboot because 'waiting for any device'. In my device manager on windows i cant transfer data from my PC to my kindle (and from my kindle to my PC).

If i press 'start' and VolUp i can go to TWRP. I dont know what to do now. Did i just brick my Kindle?

And sorry for my.. really bad english. feelsbadman

well ok. I think its brick now. I can see my Kindle Fire in my device manager on Windows, but i got just the 'kindle fire' text on my screen and nothing happen. I cant use TWRP too :(
[Kindle Fire HDX 7" & 8.9" General] draxie:
Your English is fine and your Kindle was OK in fastboot without the ready prompt

(it's a known driver issue, which should've been noted in the instructions).

Your last addition, on the other hand, doesn't sound good.

Could you let us know _in_detail_ what you did to end up there?

That might allow us to diagnose how bad the situation may be...

Since you can still see your Kindle in Device Manager, chances are

it's recoverable, but I'd rather not jump to unwarranted conclusions

without more data. Could you let us know what VendorID / ProductID

Device Manager shows for your Kindle?
[Kindle Fire HDX 7" & 8.9" General] IErziI:
Good 'morning'!

well, I decided to flash my kindle with CM13 because the bootloader was unlocked. I did it with this instruction: https://xdaforums.com/showthread.php?t=1414626 (flashing custom roms)

1) I copied the CM13 folder to my kindle fire

2) I did a backup with TWRP

3) I wiped my Kindle Fire with TWRP

4) 5) I installed the boot image in the 'boot' partition. I rebooted my Kindle Fire.. and nothing happened. I rebooted again into TWRP (everything was working there) and did the same steps again. But I did a huge dumb mistake - instead of installing the image into the boot partition again, I installed it accidentally into the 'recovery' partition (i think that is where TWRP is installed).

I rebooted again (mistake nr. 2) and now nothing happened again. But I couldn't boot into TWRP either.

https://imgur.com/a/1tdMp

This should be the Vendor ID/Product ID of my Kindle. I can see it in Windows, but I cant get into the folders to move some datas and cant use adb/fastboot.
[Kindle Fire HDX 7" & 8.9" General] tismond:
Unfortunately I am getting that odd data transfer in twrp.

Yes I used kingroot and I did wipe data and internal storage.

I was able to sidelaod a jelly Bean room that was less that 200MB and so far I am able to use it to read books and watch YouTube videos. But I get random reboots and lockups when the kindle gets too hot.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Still leaning towards a hardware issue, possibly a dislodged heatsink. HDX devices do not run 'hot' except under extreme loading. Reading books and viewing videos are normal operations.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Power + VolumeDown?

If as you state your bootloader is indeed unlocked,

you should be able to get into fastboot mode by

keeping the power and volume down buttons

pressed. With an unlocked bootloader, you can

also flash pretty much any partition from fastboot.
[Kindle Fire HDX 7" & 8.9" General] IErziI:
mhhhm. it seeems that this doesnt work. i just tried it out and nothing happened. How long should i press power and volume down together?

i did the instruction with the unlock.bat file and thought everything was alright so i flashed my kindle (.. or tried it ^^)
[Kindle Fire HDX 7" & 8.9" General] draxie:
unlocked?

First, you should power off your Kindle by holding the Power button

until the display goes dark. Then, you need to power on while holding

the VolumeDown button (i.e. the button with the "minus sign").

You can release the buttons as soon as the display lits up.

This should be almost instantaneous.

You really shouldn't have to "think".

The result of an unlock attempt is displayed

in a very obvious fashion on the device: either

Unlock code is correct

with a green OK, or

Unlock code is NOT correct

and some red status text (probably, FAILED,

but I don't quite remember).
[Kindle Fire HDX 7" & 8.9" General] IErziI:
Ok. None of these obvious Fashion was displayed on my Kindle Fire. After using unlock.bat i am really sure there was „fastboot“ and nothing else.

So well (or not), it is not unlocked

And the fastboot dient work
[Kindle Fire HDX 7" & 8.9" General] DB126:
- untether and fully power down device

- press and hold <power> and <power-down> buttons together

- as soon as the screen illuminates (1-3 sec) release both buttons

If the above sequence does not work then: 1) the bootloader is not unlocked; or 2) the bootloader is damaged. The latter can sometimes be repaired. I'll let [MENTION=5828306]draxie[/MENTION] comment further.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Won't be easy...

I'd vote for #1. Since the logo is displayed, the bootloader is

probably just fine, but definitely locked if the Power + VolDn

combo doesn't work.

The problem is that the recovery partition was accidentally

overwritten with the unsigned CM13 boot.img; so, now TWRP

is gone. (Sidenote: I _REALLY_ don't understand why our ROM

developers choose not to sign those bloody boot.img files, when

they easily could and that would both prevent these problems

*and* make unlocking the bootloader _completely_ unnecessary.)

What is a bit surprising to me is that the Kindle still registers

with it's normal vendor+product identifiers. I have a device in

a very similar state, and that one shows _no_ sign of life over

USB, unless I use a fastboot cable, in which case it enters serial

bulk mode. Unfortunately, this is only useful for a small portion

of not-very-up-to-date devices, since the flash programmer for

the newer versions has not been leaked. I plan to recover my

Kindle eventually, but it's not (yet) my top priority. I have been

looking at 2 approaches that might work:

decompiling the flash programmer, patching out

the likely fuse check, and attempting to re-sgin

glitching the eMMC during boot when aboot is read,

since a damaged bootloader puts the Kindle into

this other "direct disk access" bulk mode

Unfortunately, the free/open decompilers I've found

do a pretty lousy job and working from disassembly

takes a long time. Ida Pro is wonderful, but it's way

over the budget I consider reasonable for this project.

I've bought a Raspberry Pi and a level-shifter for the HW

hack, but I'm not at all experienced with soldering those

tiny contacts; so, I'm holding off on that for now and keep

looking at the flash programmer when I have some time... (-;
[Kindle Fire HDX 7" & 8.9" General] IErziI:
Ok. So there is no chance to repair my Kindle? For a normal person like me.. i need a specific step-by-step manual to repair my Kindle.

.. and this doesnt sound good.
[Kindle Fire HDX 7" & 8.9" General] draxie:
No easy way out

No, unfortunately, it doesn't sound very good. Or not yet, in any case...

I'll get back to you if I make any progress with the SW-only approach.

Here you find step by step instructions, but chances are they won't work

for your device (and, you'd probably need a fastboot cable to even start).

BUT, it doesn't hurt trying. The procedure is harmless. (And, you _can_

make your own fastboot cable by simply shorting 2 pins.)
[Kindle Fire HDX 7" & 8.9" General] mcasara:
I have a kindle with fire Nexus ROM running on safestrap. Do i have to roll back to stock firmware or am i good to go with these steps?
[Kindle Fire HDX 7" & 8.9" General] DB126:
You can begin immediately; no roll back or adjustments/removal of Safestrap needed. I strongly suggest you complete step #2 first and test whether TWRP is working before proceeding with steps #1 and #3. Ask questions as needed.
[Kindle Fire HDX 7" & 8.9" General] xuberantz:
links for thor aboot/twrp are dead, any alternatives?
[Kindle Fire HDX 7" & 8.9" General] draxie:
You'll find aboot in this post.

And, the latest TWRP builds in this thread.
[Kindle Fire HDX 7" & 8.9" General] xuberantz:
Downloaded aboot and twrp, renamed them to coincide with post one aboot_vuln and twrp_cubed.img was the originals somehow different? The device will only display a black screen. I'm pretty sure I bricked it as holding volume + and power does nothing but a plain black screen, and device is not displayed in command window with abd devices but will accept some fastboot commands but I'm not sure what I'm doing. Any advice is appreciated, is this a lost cause?
[Kindle Fire HDX 7" & 8.9" General] draxie:
What a mess

The aboot images should be identical, only named differently.

You can always check the MD5 hashes to be sure:

66b7df0db97c7c2905d1d61199c816a5 :: Thor
4a2be8e374c8d1fce8e6743ac2d09bb0 :: Apollo

The TWRP images are newer, but as long as they're fake-signed

that shouldn't matter.

I'm confused by your reporting. Black screen only and working fastboot

is an unusual combination. Normally, you'd see a gray logo if fastboot works.

In any case, if you have fastboot access for real you can recover.

NOTE: since you're starting from fastboot mode, you'll need to execute

the two fastboot commands shown _below_ steps 1-4 *first* to get into

bulk mode, and *then* perform the numbered steps.

Alternatively, if you really have a black screen only, you may be in bulk mode

already, but then fastboot commands shouldn't work, and you should see

a number of extra disks popping up when you connect your Kindle via USB.
[Kindle Fire HDX 7" & 8.9" General] xuberantz:
Great I now seem to have TWRP and the bulk mode method seemed to work. Is the bootloader unlocked now or do I still need to do the steps for that? Thanks for any insight
[Kindle Fire HDX 7" & 8.9" General] matt_heynes:
A few (too many) questions about the bulk mode method

[MENTION=5828306]draxie[/MENTION]:

I'm pretty new to this scene, so I was wondering if I could ask you a few questions about your bulk mode instructions posted here. (I do have some experience with installing CM on my old Moto G, but it has been a while since then, and hacking my Kindle seems like an entirely different beast).

FWIW, my device is a Kindle Fire HDX 7 running FW 4.5.5.3. My main motivation behind going with the bulk mode route are security concerns about KingRoot.

----------------------------------

A few opening questions about whether or not I'm going down the right route:

First of all: Since you're one of the most knowledgeable people in the scene, how would you weigh the security risks of using KingRoot vs. the chance of bricking my device in bulk mode against each other? I guess it's important to note that my tablet is factory-reset and doesn't contain any personal data that KingRoot could transmit. My only two concerns are about traces of KingRoot possibly somehow persisting in memory after a TWRP wipe, and copying my IMEI.

In your post you noted that you managed to perform the bulk mode method succesfully on a number of devices, but that one test device did get bricked. Was this just a fluke or simply a result of experimentation as you were still figuring this method out?

Also: I assume that my device is running a newer firmware at 4.5.5.3 compared to the devices you tested back then. Do you think that this could be an issue? Have you had any confirmed reports on the bulk mode method working well with 4.5.5.3? (I tried searching, but couldn't find any relevant posts)

In any case, about the procedure itself:

(FWIW, I have already generated the unlock code for the bootloader using your instructions).

Is there any way I can perform the bulk mode method entirely on Linux? You wouldn't have a bash script handy, would you? I do have a dual-boot system, but I haven't touched Windows in a while und would feel much more comfortable doing all of this in a Linux environment. adb and fastboot are both installed and running fine.

This might be a stupid question, but which of the two aboot versions you kindly posted here do I need to download for my device?

Let's say that everything worked out well and I managed to successfully install TWRP from bulk mode, how would I proceed next? Am I right in assuming that I would then continue with step 3 in your bootloader unlocking instructions? After that I would just continue wiping my device with TWRP and installing a custom ROM, right?

---------------

Thanks again for all you do for this community and thanks in particular for reading through this. Sorry for the barrage of questions. I'd just rather ask in advance instead of making a mistake.