yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" General] impact79:
[MENTION=5488402]Davey126[/MENTION]:

After flashing CM11 i was able to boot into android. Thanks Davey!

Afterwards i reflashed aboot and twrp and bingo, the device booted into flashboot mode, stating "ready" in an additional line. That was missing before. From here everything went smoothly.

Probably something went wrong flashing aboot, during my first try...
[Kindle Fire HDX 7" & 8.9" General] DB126:
Revisit step #2 and try again, perhaps using a different host and with some assistance from a friend. Amazing how a second set of eyeballs can surface simple mistakes blocking the path to joy. BTW - you don't have to do step #3 immediately. Several custom ROMs can be installed even with a locked bootloader. See recent posts from another contributor who was in a similar situation. Good luck!
[Kindle Fire HDX 7" & 8.9" General] woomdawg:
Ok I got TWRP and aboot flashed but I am unsure of where to put the unlock code and do I unzip it? Do I put the unlock file unzipped in the root of internal storage?
[Kindle Fire HDX 7" & 8.9" General] DB126:
- unzip/extract unlock file (must be personalized for your device)

- file goes in same folder where you are issue adb/fastboot commands

- if not obvious from above unlock file remains on host machine
[Kindle Fire HDX 7" & 8.9" General] woomdawg:
I am not sure of the location of that folder is, I have adb set up to run globally in my cmd window. I used an ADB tool from XDA to install the ADB drivers. i am assuming the folder is going to be on my PC correct?
[Kindle Fire HDX 7" & 8.9" General] DB126:
Gotta figure that out - can't see into your machine from here. :)
[Kindle Fire HDX 7" & 8.9" General] :
Restore factory state

Can this method also be used/altered in order to flash an original bootloader / locked bootloader and flash original stock rom? I want to put my device back to factory state with locked bootloader and FireOS, because I want to send it back to Amazon. Currently, I have unlocked bootloader with TWRP and CM 12.1 on it.
[Kindle Fire HDX 7" & 8.9" General] woomdawg:
I extracted to unlock file to the ADB folder located in C:\ and ran the unlock code and it said that fastboot is not found.

c:\>adb -s D0FBA0A0348604A5 shell

7[r[999;999H[6nshell@thor:/ $ su

=/dev/block/platform/msm_sdcc.1/by-name/recovery <

/dev/block/platform/msm_sdcc.1/by-name/recovery: cannot open for write: Permission denied

1|shell@thor:/ $ su

root@thor:/ # tform/msm_sdcc.1/b

/dev/block/platform/msm_sdcc.1/by-name/recovery <

/sdcard/twrp_cubed.img: cannot open for read: No such file or directory

=/dev/block/platform/msm_sdcc.1/by-name/recovery <

/sdcard/twrp_cubed.img: cannot open for read: No such file or directory

cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery <

20112+0 records in

20112+0 records out

10297344 bytes transferred in 1.451 secs (7096722 bytes/sec)

vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot <

678+1 records in

678+1 records out

347456 bytes transferred in 0.096 secs (3619333 bytes/sec)

root@thor:/ # fastboot -i 0x1949 flash unlock 0x450992e4e7.unlock

tmp-mksh: fastboot: not found
[Kindle Fire HDX 7" & 8.9" General] DB126:
Amazon won't care if the device is modified for returns within warranty. However, if you wish to restore FireOS flash v4.5.5 from here. There is no easy path for restoring stock recovery. While I see no purpose in relocking the bootloader the following command should do it: "fastboot -i 0x1949 oem lock"

---------- Post added at 07:52 PM ---------- Previous post was at 07:35 PM ----------

No idea what's going on here. Some of the commands are concerning; glad they failed.

Recommend stepping away from whatever method you are using and go with generic/standard tools:

- download "Minimal ADB and Fastboot" from here

- run the installer; take note of the install folder

- use Windows file explorer to copy/move the extracted HDX unlock file to that folder

- locate "Minimal ADB and Fastboot" under "All Programs" (note: installer may put an icon on your desktop; use that if available)

- when you click on icon you will be placed in a Windows command window (scary...)

- place device in fastboot mode and tether to PC

- issue command "fastboot devices"; you should get a response. No response indicates driver issues.

- assuming success in previous step issue bootloader unlock command as shown in OP
[Kindle Fire HDX 7" & 8.9" General] woomdawg:
Ok I did that and I think it worked it says on my device unlock code correct. Now how do I flash it? Thank you so much for your help. I am not stuck in the fastboot screen no matter what I do.

---------- Post added at 08:50 PM ---------- Previous post was at 08:35 PM ----------

EDIT: I got it to boot into TWRP so now I feel alot better.
[Kindle Fire HDX 7" & 8.9" General] DB126:
All set? Assuming you know what to do in TWRP. Tips:

- clear following partition before flashing first rom: System, Data, Dalvik, Cache

- suggest starting with CM 12.1 (Lollipop) or Fire Nexus 6 (Marshmallow)

- CM 13 nightlies are broken; however previous builds are fine (here)

- other ROMs are fine too ... just trying to give you a starting point

- suggest holding on CM 14.1 for now ... still in early beta
[Kindle Fire HDX 7" & 8.9" General] woomdawg:
I have used TWRP in the past but not in awhile. So I just need to push the rom to my downloads folder and flash it in TWRP correct?
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yes. Don't forget the previously mentioned wipes (very important). Given your situation I strongly suggest going with Fire Nexus as it's all inclusive (ROM + GAaps + SuperSU).
[Kindle Fire HDX 7" & 8.9" General] :
Thank you for this information. So I will simply send it back. The screen has a hardware problem, an area where it shows lots of blurry/damaged pixels which is only visible on black background. That's why I didn't notice at first, and then I already had done the modifications. I got it from Warehouse Deals and it was advertised as used condition. So I hope this won't defy my warranty claim, because of buying it knowing that it's used.
[Kindle Fire HDX 7" & 8.9" General] DB126:
I would reach out to Amazon via chat/phone to insure your claim will be honored. Devices sold through Warehouse Deals typically do not carry a warranty as stated in the description. If Amazon does accept it for exchange/return they may want to power on the unit for inspection. In that case having FireOS pop up will not raise any red flags. My previous statement assumed a new unit under warranty. Your situation is a little different. Good luck.
[Kindle Fire HDX 7" & 8.9" General] woomdawg:
Flashed the nexus ROM. Thank you.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Enjoy your liberated device! A few more tid-bits:

- no hardware GPS; static locations only

- powerful backlight highlights beautiful screen but also sucks juice; disabling auto-brightness and setting manually helps

- orientation (rotation) issues in some apps are a common problem on Amazon devices; there are fixes if needed

- suggest Nova launcher for best experience

- when you are ready Xposed modules further extend the utility of this lovely device/rom combination
[Kindle Fire HDX 7" & 8.9" General] tvd0405:
Try to boot into recovery by holding vol+ and power buttons together then release the power button while keep holding the vol+ button when the screen display kindle fire. Keep holding vol+ until boot into recovery. When in recovery, you can copy the ROM image from PC to kindle then you can flash that image.
[Kindle Fire HDX 7" & 8.9" General] :
Do I need to put the original recovery on it then? Are there any instructions available how to do that? Or maybe flashing a TWRP compatible (modified) stock rom is enough?
[Kindle Fire HDX 7" & 8.9" General] Grtschnk:
Yeeeeees! Finally the tablet is useful! Flashed CM and now I'm a happy camper.

Fastboot driver issues: if someone's is struggling to connect Windows to fastboot maybe try a different cable. Worked for me (adb worked but fastboot surprisingly not)
[Kindle Fire HDX 7" & 8.9" General] DB126:
Restoring FireOS should be sufficient IMO. There is no standard procedure for restoring stock recovery; you don't want to mess with that.

---------- Post added at 02:25 PM ---------- Previous post was at 02:15 PM ----------

Yep - on more than rare occasions this has proven to be the culprit. USB cable quality is highly variable including the stock cable provided by Amazon. Poor charging, random corruption during data transfer and/or inability to connect in various modes is bellwether of problems that defy easy explanation.

---------- Post added at 02:30 PM ---------- Previous post was at 02:25 PM ----------

Although normally a good suggestion I doubt this will help the OP. Symptoms described elsewhere suggest a borked aboot flash.
[Kindle Fire HDX 7" & 8.9" General] woomdawg:
I was noticing that stuff last night. I am going to try cm12 tonight when I get back from training.

What exactly is xposed and what can I do with it? I want to get rid of the branding.
[Kindle Fire HDX 7" & 8.9" General] twocrows:
I think that I used the correct aboot.bin file but the wrong mmssssss address. My 6 yr old was up in my space and I think I miskeyed, my own boneheaded fault. If you pay attention you should be fine. My focus was broken and I wanted to see what my kid wanted but should've double checked before I hit enter. But most feedback I have seen has been positive and non destructive. Hope you find the knowledge to give you the confidence to make your device the way you want it.

---------- Post added at 12:25 PM ---------- Previous post was at 12:18 PM ----------

Any links to these "hacks"? My kindle in similar state, add shows that device is "unauthorized". Windows File Explorer can see internal storage l, but can't turn USB debugging off/on or access "handshake" ("trust this device") from Kindle screen. MiPhone either times out with waiting for "hello packet" or gives me above error or a "catastrophic failure" error.
[Kindle Fire HDX 7" & 8.9" General] DB126:
For awareness an incorrect unlock code ("mmssssss address") would not brick the device. Response would simply state unlock code was incorrect and both devices (host and table) would return to a 'ready' state. A more likely scenario IMHO is a corrupt/invalid aboot.bin was flashed followed by an immediate attempt to unlock. The presence of a 'bad' aboot would not become apparent until the device was subsequently rebooted. Corruption can occur in a number of ways as noted in previous posts (when initially downloaded to host, during transmission to device, etc.). Again - an incorrect unlock code/file would not brick the device.

I'm responding not to 'correct' but reassure other readers that a bad unlock file itself is not dangerous.
[Kindle Fire HDX 7" & 8.9" General] Manuelhu:
hello

i dont know why but Phyton is not running well

so can someone get me an unlock code please.

thank you very much

manfid

0x000011

serial

0x070facc2
[Kindle Fire HDX 7" & 8.9" General] DB126:
I have no direct experience with overcoming 'unauthorized' issues on a non-bootable device so never retained links. Same with "MiPhone". Google is your friend; you'll need to do some digging.

As an aside, 5th Gen Fires are on sale this week in the US (20% reduction). A 'like new' refurb from Amazon Warehouse is nearly 50% off list. Might be a reasonable alternative depending on intended use. Bad for text and web browsing; not too shabby for video. Several custom ROMs to choose from.
[Kindle Fire HDX 7" & 8.9" General] stangri:
Enjoy!
[Kindle Fire HDX 7" & 8.9" General] jmanteau:
Hello,

I'm stuck in a boot loop with Amazon Logo. I'm able to go into Fastboot but the following command don't work. Do you have any clues for me to solve this ?

shell@ford:/ $ cat /sys/block/mmcblk0/device/manfid

0x000015

shell@ford:/ $ cat /sys/block/mmcblk0/device/serial

0x0e4049be

# python cuberHDX.py 0x150e4049be

Your unlock code is in '0x150e4049be.unlock'.

# fastboot -i 0x1949 flash unlock 0x150e4049be.unlock

target reported max download size of 134217728 bytes

sending 'unlock' (0 KB)...

OKAY [ 0.012s]

writing 'unlock'...

FAILED (remote: unlock code error)

finished. total time: 0.022s
[Kindle Fire HDX 7" & 8.9" General] DB126:
Clue is in this line: "sending 'unlock' (0 KB)...". Nothing got sent. Check file location and permissions.
[Kindle Fire HDX 7" & 8.9" General] OiOlli:
I tried but i even cannot installed the drivers. It failed with Lab 126 (WinUSB) AndroidUSBDeviceClass Status Installation failed.

Second question, have i got to the Donload or Recovery with my Kindle HDX 7 and how did i get there?
[Kindle Fire HDX 7" & 8.9" General] DB126:
Be candid - you probably don't want to unlock this pup without local assistance from someone knowledgeable in electronics. Seen too many bad outcomes from folks trying to wing it ...

To exit stock recovery long press power button until device shuts off. Then power up as normal.
[Kindle Fire HDX 7" & 8.9" General] OiOlli:
Or a step by step intruction. Maybe i am wrong but i think there is something missing.

And now, i dind´t want to leave the recovery mode, i want to get there.
[Kindle Fire HDX 7" & 8.9" General] jmanteau:
Thank for the tip, that's my idea as well but unfortunately it is not the case:

# ls -lah 0x150e4049be.unlock

-rwxrwxrwx 1 ABC ABC 256 Dec 18 15:50 0x150e4049be.unlock

# fastboot -i 0x1949 flash unlock 0x150e4049be.unlock

target reported max download size of 134217728 bytes

sending 'unlock' (0 KB)...

OKAY [ 0.012s]

writing 'unlock'...

FAILED (remote: unlock code error)

finished. total time: 0.021s
[Kindle Fire HDX 7" & 8.9" General] DB126:
Thoughts:

- try a different cable; not a common failure point but not rare either

- ditto for USB port (yeah I know, grasping for straws)

- later tonight I will spin up an unlock file using your data; try that one (also compare file signatures)

- Apollo, correct?
[Kindle Fire HDX 7" & 8.9" General] DB126:
Edit: ran out of time (sorry); will address tomorrow.
[Kindle Fire HDX 7" & 8.9" General] stangri:
Given the user/group of the file -- are you running this inside a Linux VM on Windows?
[Kindle Fire HDX 7" & 8.9" General] jmanteau:
I started it on a MAC but fastboot -i 0x1949 was giving me "waiting for any devices". So I spinned up a linux VM and direct attach the kindle to it.

On MAC

$ fastboot -l devices

0123456789ABCDEF fastboot usb:338886656X

$ fastboot -l devices -i 0x1949

$

On Linux VM

# fastboot -l devices

0123456789ABCDEF fastboot usb:1-1

# fastboot -l devices -i 0x1949

0123456789ABCDEF fastboot usb:1-1

---------- Post added at 09:52 AM ---------- Previous post was at 09:46 AM ----------

It's OK. You're already very helpful by helping me on your spare time.

Thor and here is the manfid and serial. I will retry another usb port and cable with your file (already changed to a spare USB 2.0 port in back of the motherboard but will try again!)

FYI I tried the cuberHDX in python but also compile another one in C to test. Same result.

shell@ford:/ $ cat /sys/block/mmcblk0/device/manfid

0x000015

shell@ford:/ $ cat /sys/block/mmcblk0/device/serial

0x0e4049be

To arrive at this state (stuck at fastboot with wrong unlock code), I did follow the tutorial. However I was already on Safestrap with Nexus Fire Rom. Can this have an impact ? I didn't think so as the bootloader was independant and I did arrive in Fastboot mode. But at this stage I can only think of this to explain the current status.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Attached is the unlock file I spun up from your data. Curious if it works and (if not) do signatures match? The presence of SafeStrap or anything else in the system partition is irrelevant to the bootloader unlock procedure.

Curious if you validated the outcome from step #2 by attempted to boot into native TWRP (not the Safestrap emulator)? That should confirm a vulnerable aboot was properly installed.
[Kindle Fire HDX 7" & 8.9" General] stangri:
Weird, everything worked on mac here. Maybe it's an indication of the underlying issue (unless you have a very outdated fastboot binary). Does any fastboot -i 0x1949 action actually work from Linux VM? Can you try:

fastboot -i 0x1949 reboot
fastboot -i 0x1949 reboot-bootloader
[Kindle Fire HDX 7" & 8.9" General] jmanteau:
Both commands work but the Kindle is still stuck in the boot loop.

---------- Post added at 09:04 AM ---------- Previous post was at 09:02 AM ----------

Same checksum.

MD5 (0x150e4049be.unlock) = 1c94c0493f77537be8530aecd6c2348e

MD5 (0x150e4049be.unlock-mine) = 1c94c0493f77537be8530aecd6c2348e

I've tried to be sure but it still doesn't work.

No, I didn't do that, unfortunately.
[Kindle Fire HDX 7" & 8.9" General] DB126:
You can still test TWRP availability as follows:

- untether

- long press power (20+ sec) to insure device is off

- press <vol-up>+<power> to enter recovery mode

If the above yields Amazon's stock recovery step #2 in unlock procedure was unsuccessful. If TWRP then there are steps that can be taken to recover the device. Post back findings; go from there.
[Kindle Fire HDX 7" & 8.9" General] Paladin@1976:
I need help, because I can not flash the unlock-file. I had no errors until step 3, but I restartet the fire hdx after the two dd-commands (I think that was my mistake). Now the device starts directly in fastboot-mode and shows a "Ready."-statement. But I can not see it with adb devices. If I run the fastboot-command with unlock-file it shows "waiting for any devices". I can start in TWRP Recovery but does not know what I should do there. If I run adb shell I get this prompt: "~ # <- [6n" (only in TWRP).

Edit: Is there a way to go back to original bootloader with twrp? I can copy files to device if I start TWRP.
[Kindle Fire HDX 7" & 8.9" General] lilsancho:
Doh! I'm in the same boat, my own stupid fault for messing up the .unlock stage - I got the serial wrong.

I did make a note of it but I reset my machine trying when trying to install a driver.. that notepad entry is lost forever!

Is there a way I can re-grab the serial from the terminal? I can boot into TWRP - but thats about it..
[Kindle Fire HDX 7" & 8.9" General] DB126:
No need to restore original bootloader. Your issue is driver related on the host side; adb and fastboot typically need different drivers installed. Has nothing to do with restarting device after issuing DD commands. Read through the thread for guidance from others caught in this situation. Links to drivers can be found in OP.

As TWRP is available (meaning step #2 was successful) you can flash several KitKat based ROMs that do not require an unlocked bootloader including CM11 and Fire Nexus. Suggest the latter as it has everything you need in a single zip (link below). Be sure to wipe system, data, cache and dalvik partitions first.

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

---------- Post added at 08:38 PM ---------- Previous post was at 08:32 PM ----------

Since TWRP is available install the following ROM which will permit you to requery the serial number. See previous post for related notes.

http://xdaforums.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
[Kindle Fire HDX 7" & 8.9" General] stangri:
Can they not boot to twrp, mount system partition (if required) and run adb commands (to get serial number)? For some reason I have an impression that adb is enabled in twrp.
[Kindle Fire HDX 7" & 8.9" General] testomat:
Can someone create me an unlock file. Python will not work.. :(

cat /sys/block/mmcblk0/device/manfid

0x000015

shell@thor:/ $ cat /sys/block/mmcblk0/device/serial

cat /sys/block/mmcblk0/device/serial

0x873565c2
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yes, but it can be fussy. Fire Nexus installs quickly, is self contained (GAaps; SuperSU) and allows device to remain fully operational while gathering info, unlocking bootloader, etc. For some that may be good enough for immediate needs. Also a potential solution when adb has been explicitly disabled.
[Kindle Fire HDX 7" & 8.9" General] Paladin@1976:
You were right. It was a driver problem. I installed google drivers from android sdk and these were working with adb-commands. Now I installed the pdanet drivers and I could run the fastboot-command. Problem is I get an error when I tried to flash the unlock-file: "Unlock code is not correct". My target is to flash CM13 or CM14 and not CM11 or Nexus-ROM.

Edit: Now the unlocking was working without error. My mistake was that I only used the serial number and forgot the last 2 digits of manfid.

---------- Post added 22nd December 2016 at 12:00 AM ---------- Previous post was 21st December 2016 at 11:40 PM ----------

I tried the adb-command to get serial number when fire hdx was booted into TWRP. I got the same serial number which I had written before.
[Kindle Fire HDX 7" & 8.9" General] lilsancho:
Thanks Davey!

I can boot up now :)

But sadly another issue has developed, when reboot into fastboot I get "Unknown USB Device (Device Descriptor request failed)"

Can't seem to get around this..
[Kindle Fire HDX 7" & 8.9" General] DB126:
Thoughts:

- try changing USB ports; avoid hubs and USB3 ports if possible

- try a different cable (you'd be surprised how often this works)

- verify drivers are correct; see previous post from another user

- if none of the above works try a different host
[Kindle Fire HDX 7" & 8.9" General] lilsancho:
Yeah I figured I'd wait until I got back to my work machine this morning as everything was working on it yesterday.

Thankfully It worked without issue! Am now unlocked :)

Thanks again for your guidance Davey
[Kindle Fire HDX 7" & 8.9" General] Thanatus1985:
fail at the last step

Well guys, I followed the tutorial, and everything was fine. I also created my own unlock file. But at the last step, I just couldn't flash the file in fastboot, and it kept reminding me cannot load .unlock. Anyone could help me in this issue? I tried also do it through antother computer, but the result was the same.
[Kindle Fire HDX 7" & 8.9" General] RambaaZambaa:
This means that i cant run the command because while in "SU" it cant find the sdcard folder (which is the root directory, right?).

(i only used the cd command to check if the folder is existing because the "dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery" command gave me this Error.)
[Kindle Fire HDX 7" & 8.9" General] ONYXis:
Ou..Forget. Just copy two files through mtp protocol, with My computer - Fire.

After that enter commands that I wrote at OP.
[Kindle Fire HDX 7" & 8.9" General] RambaaZambaa:
My HDX only shows up in picture-mode so i pushed the two files via adb which worked fine. I can see the two files in /SDCARD and on the device itself with my file explorer. Problem is: your command needs SU and i cant access the sdcard folder while being SU.
[Kindle Fire HDX 7" & 8.9" General] ONYXis:
Because you try access sdcard/sdcard with second cd I guess. After su (in your screen)U Already in sdcard.

Pls provide pic where only my commands.
[Kindle Fire HDX 7" & 8.9" General] RambaaZambaa:
So first i try the command _without_ su which obviously is not working BUT we clearly see that the file is there. Just not the permissions.

So then i try it with SU which gives the "cannot open for read: No such file or directory" Error.
[Kindle Fire HDX 7" & 8.9" General] ONYXis:
cd /sdcard

ls

Without su
[Kindle Fire HDX 7" & 8.9" General] ONYXis:
Really dont understand what is you problem.

Okey.

Su

Cd /sdcard

Ls

Do you see files?

Try to reboot pc and tablet at least)
[Kindle Fire HDX 7" & 8.9" General] draxie:
That looks really odd.

Can you post the output of these commands?

su
ls -lZ /
ls -lZ /storage/emulated/legacy/
[Kindle Fire HDX 7" & 8.9" General] dutuka:
HDX 8.9 Apollo?

Does it work with HDX 8.9 Apollo? Thanks.