yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] lekofraggle:
Whether your boot loader is unlocked or not, your computer will recognize the device in boot loader mode if you have the drivers.

I plugged my kindle in, deleted all my kindle drivers using device manager, unplugged it, put it in boot loader mode, plugged it back in and it installed the drivers. In doing so, I lost the map drivers, but adb still works as does WiFi sharing.

---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------

Here is the thread that made the unlock easy for me.

http://xdaforums.com/showthread.php?t=3050689

Good luck.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Here's another write-up (based on Draxie's work) that helped me: http://xdaforums.com/showpost.php?p=58897784&postcount=67. Additional thoughts can be found here and throughout the BL unlock thread. Use any/all of these resources including the link provided by [MENTION=3038165]lekofraggle[/MENTION]. Ultimately they all get you to the same place.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] SilverLynx:
Yeah, my head is spinning. There's too many pitfalls for some of us who haven't kept up with the scene over the years. No one wants (or can afford to) brick their tablets.

Is there any way one or some of you can collaborate and type up a step by step detailed tutorial to take a Kindle Fire HDX 7 &/or 8.9, from factory reset to installing cm12 or any rom?

I know it would be a lot of work, but you would be hailed as a hero :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
That has been discussed but the number of variations is simply to great. The guide itself would be a small novel and still wouldn't cover all the scenerios. Risks are also unacceptably high IMO as the slightest misstep can lead to an unrecoverable brick. All the information is in the forums but it takes a fair bit of dedication and certainly time to digest the material and separate chaff from wheat. Unless you're a geek/tinker at heart it's best to appreciate your stock Kindle for what it is.

Edit: I should clarify that the act of unlocking is not particularly risky and is actually pretty easy once you understand the process and get though maddeningly frustrating driver issues on some platforms (Windows is the worst offender). It is the steps required for most devices to get to the point of unlocking that poses the greatest risk. Many HDX owners are unfamiliar with rollbacks, flashing, OTA, ADB, etc. and ultimately make mistakes that are difficult/impossible to rectify. The pool of devices that can be unlocked is also decreasing as anything that started life above 3.2.6 can't be readily unlocked with the current set of exploits.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] PacoBell:
You got fastboot to work on your HDX in Windows? What version of Windows were you running? What version of the Android SDK did your fastboot binary come from? I installed android-studio-bundle-141.1903250-windows.exe on my Windows 7 SP1 box and set up all the appropriate toggles in the SDK Manager. And I can adb just fine and even reboot-bootloader, but fastboot just won't list the damn device. I even tried manually updating the driver with some added USB information in the installation script, but Windows doesn't recognize that installer file as the correct driver for the device. I mean, unless nobody actually tested this before reporting success, I have to imagine that it functioned correctly in at least one Windows environment at some point. I'd like to know how to recreate those conditions.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Hasney:
8.1.

I'm not at the laptop I did it with so I can't tell you the specific drivers I used, but I had to totally uninstall the driver I used ADB with, reboot and then it installed fastboot drivers. I found this pretty invaluable when I was going through it:

http://xdaforums.com/showpost.php?p=23747671
[Kindle Fire HDX 7" & 8.9" Original Android Develop] lekofraggle:
For me (also 8.1), it found the drivers itself.

I put the kindle in casebook mode and plugged it in.

When it was not recognized, I deleted all possible drivers from my machine and rebooted it.

Then, I plugged the device back in in casebook mode and it worked. It should be noted that my machine (and I have read reports of others') cannot mount the kindle in Windows explorer with the casebook driver installed. This is fine because adb still works as does various WiFi transfer tools (es file explorer has a nice one).

Good luck.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
You are working too hard :) .

Best practice is to connect your kindle and then delete all related components that show up in device manager. Then reboot and reconnect. In most cases Windows 8.1 (and below) will install the correct drivers assuming they have been downloaded in advance (not always required; Win 8.1 seems to come with compatible drivers). You will need to disable unsigned driver protection on Win 8.1 x64.

You don't need the full android SDK. Minimal Fastboot and ADB work just fine.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] tishotch:
Can you this method to work on locked bootloader on HDX Nexus v4.0.1 ROM ? I have stuck grey logo on bootloader after flashing and as I understood, I have to unlock it to start normally.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] lekofraggle:
No, this will not work. You need adb to unlock it. What you need to do is refresh the version of the kindle os you had (I assume it was <2.3.6), then rollback to 2.3.2. Finally, you can unlock it. I would recommend using Draxie's tool from the other dev. thread as you need to follow many more directions to unlock successfully this way. You have a long hard road ahead, and you need to read these threads carefully, but if you started with the right version, it can be done.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NeverSmile:
sorry about long quote, i do extractly, but at the step flash unlock 0xmmsssssss.unlock ( of course i have the code ) , at fastboot prompt say wait for the device and stuck, but in my kindle fire appear fastboot ready, and nothing here, no flash, no comand appear, so what's my problem here ? and how to fix it ..
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ceyo14:
Im guessing its not recognizing it. Try fastboot devices... Or reconnect it... Try the driver install again.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Agreed. Windows drivers are the likely culprit. Remove all related entries in Windows Device Manager (visible when device is tethered), detach device and reboot both devices. Then replug Kindle and allow Windows to reinstall drivers. That usually fixes it. If not you may need to download Kindle specific drivers and jump through some additional hoops if your are running Win 8.x 64-bit.

Also try a different usb cable. Amazing how many times that works.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NeverSmile:
i change hub of usb, reinstall window 7 ( my os previous is 8.1 ) reinstall sdk, driver HDX 7, but still stuck at '' Waiting for device ". I think that adb driver is missing, but the problem is i have installed driver. link is : https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing

https://developer.amazon.com/public...cs/01-setting-up-your-development-environment

still no luck. anyone have an idea ? pls help
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Tip-of-the-hat for the lengths you have gone to so far!! Try this (sorry for the prescription; trying to get to a known environment):

- if you are using a physical USB hub get that out of the equation. Try to use USB2 ports if you have the choice between USB2 and USB3

- install minimal ADB and Fastboot (here)

- grab drivers from this post; unzip and store in a familiar folder

- reboot windows. Open device manager

- power off HDX. Restart via power + vol-down; should go directly into fastboot and display 'Ready'

- connect HDX. Observe new ADB entry (should refresh within a few seconds). Uninstall driver

- replug device; likely the same driver will be reinstalled

- click through 'update driver software' -> 'browse my computer ...' and install driver from downloaded package

- unplug/replug device; validate same driver remains installed

- open a command prompt in the directory where Minimal ADB and Fastboot is installed. Issue following command: fastboot -i 0x1949 devices

What comes back?

FYI - I verified connectivity with Google ADB driver v2.0.10.2 (2009) and v8.0.x (2013) and version 7.0.x from CMCC on Win 8.1 x64. Should be fine on Win 7 (and likely Vista/XP) which handle unsigned drivers more gracefully. If you are still having connectivity issues then you should consider switching hosts ans there may be some type of hardware limitation coming into play. Another option is a Linux virtual machine but I have found Windows connects reliably with the correct drivers.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] NeverSmile:
thanks, it work like charm. :good::good::good:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Bear6009:
Hey guys,

Wondering if someone could point me in the right direction. I have my .unlock file created, but where do i put it? (IE. fastboot directory) ? is this on the device or on my pc?

thanks
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Cl4ncy:
Did you install Minimal ADB and Fastboot? It's the same directory then (usually c:\adb), fastboot.exe should be in there, too.

If you get the good ol' "wating for device" issue, install these drivers.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Bear6009:
I was having a hard time because i was trying to see if the devices was connected by adb devices, but that wont show up while in fast boot. DUH lol

[IMG="success"]http://s18.postimg.org/r9e93i3wp/20150911_102848.jpg[/IMG]

:) lovely! THANKS [MENTION=5488402]Davey126[/MENTION] and [MENTION=6815340]Cl4ncy[/MENTION]

Now on to roms!

Is there a way to run two roms? like dual boot?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Congrats - glad all is well. Only one rom at a time when using 'native' twrp as you flashing directly to the system partition. However, you can backup and restore different roms in twrp. Safestrap offers dual boot capability but you really don't need/want to use that if you can flash natively.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] tthaz777:
My firmware version is 4.5.5. How can I unlock the bootloader?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] EncryptedCurse:
You can't. You need to be on 3.2.3.2 or below, and there's no way to rollback firmwares past 3.2.8.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
New kid on the block

Forget about adb/fastboot, python, cuber, and driver agonies on Windows... ;)

Check out my '1-Click' bootloader unlock!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] adeba:
Hello from germany,

I am on cm11 rom with safestrap 4.01.

Whats my way to unlock?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] EncryptedCurse:
Not possible.

You need to be on FireOS 3.2.3.2 or below, but there's no way to downgrade past 3.2.8.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] rlkellyjr:
Big Question? If I do a rollback, and then manually update to 4.5.2, then root my kindle again, If a boot loader unlock is made available for the 4.5.2 to 4.5.5 firmware's, will I be able to update and preform that procedure? Or once you do this rollback, are you stuck at 4.5.2??
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Bootloader unlock is unlikely; better odds buying a lottery ticket. That said if an unlock were to become available you would have complete control over your device. Current OS would be irrelevant.

Better to be on 4.5.2 and rooted than 4.5.5 and locked into Amazon's upgrade/obsolescence path. Note rollback is only available on 3rd gen devices (all 7" and 8.9" manufactured before 3Q14; snapdragon 800 processor). There is no option to root or rollback a 4th gen device (snapdragon 805).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Jamesblond005:
Ok I get to the stage below please guide me . Im a total newbie on a customisable bootloader and nexus 2.05. Ive managed to create the img file unsure how to proceed with the instructions below.where is the fastboot directory

Please help thanks

copy that file to your fastboot directory.

on an ADB prompt type

adb reboot-bootloader

then on a fastboot prompt type

fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot

thats it.

Gathered all from this thread, just a little clearer I think...

thanks to [MENTION=438903]dpeddi[/MENTION], [MENTION=4450207]vortox[/MENTION], [MENTION=5828306]draxie[/MENTION], [MENTION=4107074]ApokrifX[/MENTION][/QUOTE]
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Have you tried 1-Click?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Jamesblond005:
'www.microsoft.com' appears unr

Please check your internet conn

Press any key to continue . . .

Downloading 'https://www.virtua

loads\1-Click(1)\1-Click\dwnlds

Download complete.

Downloading 'http://download.vi

105127-Win.exe' to 'C:\Users\Di

14-105127-Win.exe'

Download complete.

Launching the VirtualBox instal

Please complete the installatio

Installation complete.

VBoxManage.exe: error: Machine

lick\1-Click.vbox' already exis

VBoxManage.exe: error: Details:

achineWrap, interface IMachine,

VBoxManage.exe: error: Context:

raw(), ComSafeArrayAsInParam(gr

hine.asOutParam())" at line 272

VBoxManage.exe: error: Could no

VBoxManage.exe: error: Details:

nent VirtualBoxWrap, interface

VBoxManage.exe: error: Context:

utParam())" at line 1027 of fil

VBoxManage.exe: error: Could no

VBoxManage.exe: error: Details:

nent VirtualBoxWrap, interface

VBoxManage.exe: error: Context:

utParam())" at line 325 of file

VBoxManage.exe: error: Could no

VBoxManage.exe: error: Details:

nent VirtualBoxWrap, interface

VBoxManage.exe: error: Context:

utParam())" at line 486 of file

VBoxManage.exe: error: Could no

VBoxManage.exe: error: Details:

nent VirtualBoxWrap, interface

VBoxManage.exe: error: Context:

e.asOutParam())" at line 224 of

Oracle VM VirtualBox Headless I

(C) 2008-2016 Oracle Corporatio

All rights reserved.

Invalid machine name or UUID! unsure where i went wrong have tried this numerous times getting the previous error
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Cl4ncy:
Do you have Minimal ADB & Fastboot installed? Check this post then.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Jamesblond005:
Hi yes I have minimal adb installed think I may have a issue with the pc recognising my kindle now. I can only get it to display the files within the kindle in twrp currently it dosent seem to mount otherwise. The problem may have been it wasnt displaying a kindle as being connected it was showing a Nexus 2.0.5 , i may have deleted that and now it dosent display my kindle unless i mount it in twrp

Do you have Minimal ADB & Fastboot installed? Check this post then.[/QUOTE]
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Cl4ncy:
Did you install the drivers linked in the post I referred to above? They help to get the HDX getting recognized by fastboot during the unlock procedure, but lead to the problem that the HDX won't get recognized by Windows anymore. But that doesn't matter for unlocking, just proceed with the adb & fastboot commands, get the HDX unlocked, then re-install the original Amazon drivers, and everything will be fine. ;)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Jamesblond005:
Hi this is what I get when I try the unlock procedure

C:\adb>fastboot -i 0x1949 devices

D0FBA0A03451042E fastboot

C:\adb>fastboot -i 0x1949 flash unlock 0x115dd87787.unlock

error: cannot load '0x115dd87787.unlock'

On kindle hdx I get

getvar:partition-type:unlock...ok.

Ready.

Did you install the drivers linked in the post I referred to above? They help to get the HDX getting recognized by fastboot during the unlock procedure, but lead to the problem that the HDX won't get recognized by Windows anymore. But that doesn't matter for unlocking, just proceed with the adb & fastboot commands, get the HDX unlocked, then re-install the original Amazon drivers, and everything will be fine. ;)[/QUOTE]
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Cl4ncy:
Did you copy/move the .unlock file into the adb directory? Otherwise you have to enter the path to it as well. (That's why it's recommended to put it into the adb directory).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Jamesblond005:
yes the unlock file is in adb\0x115dd88787.unlock. Im getting rather concerned now I cant seem to get my kindle recognised on the pc, Id work around that but have been unable to unlock the bootloader either , have been at this for days on and of
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Reviewing post history it appears your device started at 3.2.4 w/Safestrap v3 and then attempted to auto update to an unknown version (you speculated 3.2.5) which was canceled before completion followed by a factory reset (typically yields brick w/Safestrap installed - got lucky) . Device then reported 13.3.0.0. It is possible your bootloader remain at a level (>3.2.3.2) that can not be unlocked.

You may want to consider flashing TWRP sooner vs later as it will: 1) confirm if bootloader is eligible for unlock/signature forging; and 2) offer additional recovery capability of something goes wrong with subsequent flash/upgrade/rollback attempts. Note you can install custom versions Nexus v2 (Jelly Bean) or CM11 (KitKat) from TWRP on devices with a locked bootloader. If you go this route you will still have the opportunity to unlock later (involves reinstalling FireOS; not for the faint of heart).

Thoughts from others (@CL4ncy; [MENTION=5828306]draxie[/MENTION])?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Jamesblond005:
Hi Davey no I have TWRP installed I dont have safestrap haven't had it installed for quite some time. Find the whole process difficult to be honest, with no programming knowledge. I may just leave as is with TWRP installed . How do I get the kindle recognized without mounting it in TWRP. Thanks for your help

JB
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Assume you can boot (any) OS:

- open Windows device manager; expand window so most/all device categories display (don't have to expand individual trees)

- attach Kindle via known good USB cable; observe what gets added

- delete all the recently added (only) devices from device manager; typically one device but occasionally two

- disconnect Kindle

- reboot both devices

- reattach Kindle; windows should find and install correct drivers

Be sure your USB cable is good and connects directly to host device (no hubs, extension cables, etc).

BTW - 1-click bootloader unlock is much easier...if it works. The path you have been taking is akin to fighting off a band of Orcs with a butter knife :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Jamesblond005:
Yeah I have tried 1 click a few times without sucess will hop over to that topic , thread, see if someone can assist me further with that method thanks got the kindle recognised by following your instructions ty
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Awesomeslayerg:
The trust zone exploit may help us unlock our bootloader

https://mobile.twitter.com/laginimaineb/status/737051964857561093
[Kindle Fire HDX 7" & 8.9" Original Android Develop] hammaad5:
Would this bootloader unlock work if I have FIre OS 4.5.5.1?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
No - unless you are an experienced Android developer and can develop and exploit that will work against this vulnerability (if it even applies to this device).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] hammaad5:
Would it be possible for me to downgrade this device or no?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
No
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Alright... so, this is what kept people from trying the obvious, but admittedly risky reflash before...
[MENTION=5594063]ONYXis[/MENTION] prevailed!!! (^;

---------- Post added at 21:50 ---------- Previous post was at 21:46 ----------

Not only arrogant, he was also dead wrong....
[Kindle Fire HDX 7" & 8.9" Original Android Develop] r3pwn:
I appreciate the unwarranted hatred, but I fail to see how reporting on a hypothesis based on a large amount of users bricking their devices while trying to roll back the software on their devices is "arrogant". I admitted I was wrong. I'm glad HDX users finally have a reliable way of unlocking from any version.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Whoa there! Dredging up dusty posts to blast past guidance based on the communities best understandings at the time seems a little out of bounds. During the ensuing 18 months any number of individuals could have tried the "obvious"; seems no one wanted to sacrifice their device. Not you, not me, not [MENTION=5594063]ONYXis[/MENTION] (as previously noted) nor dozens of other 'technical' contributors. Yet bricks kept happening to unwitting users who attempted flashbacks so we all seemed satisfied with the previously presented explanation. If [MENTION=4732871]r3pwn[/MENTION] displayed arrogance by trying to prevent bricks then I am a flaming example having posted similar warnings dozens of times.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
Frustration? Defnitely.

"Hatred"? NO WAY!!

And, I certainly don't appreciate you trying to spin it that way.

Here's the specific part that I find extremely arrogant:

Granted, it's not _that_ easy. You need to also __unlock__ the bootloader you've just flashed.

BTW, as I said on the other thread: I completely agree that the assumption is plausible,

but dismissing others' ideas the way you did (and with the weight your "Respected" status

carries) **based on an unverified assumption** does come across as arrogant, in my eyes.

I also recognize and respect that you simply admit that you were wrong. That's fine.

Now, if you could help in finding a way to figure out the EMMC serial from a fastboot

prompt alone, we could also unbrick at least _some_ of those rolled-back devices;

at least those that flashed a vulnerable aboot...

---------- Post added at 10:20 ---------- Previous post was at 10:17 ----------

First of all, I was looking for this post of mine,

when I happened to come across [MENTION=4732871]r3pwn[/MENTION]'s post, and I just couldn't hold back my frustration seeing not only *what* he said,

which is quite plausible, but also **how**.

Also, if you care to check back, those posts were instrumental in establishing that "best understanding".

I've been parroting that in trying to help others, just like you, but I don't seem to recall ever having encountered

that kind of tone from you (I'm less sure about myself ;-P).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] BeeWall:
Can someone do a comparison of the bootloader before and after unlock? If we can figure out the difference, it may also be applicable to other devices that don't have an unlock method yet.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] draxie:
The bootloader doesn't change. That state is kept elsewhere (idme?).
[Kindle Fire HDX 7" & 8.9" Original Android Develop] BeeWall:
Is there any idea of how we could figure out where? And if so, could we find the difference? Maybe comparing the important partitions (RPMB, idme, etc)? If nobody has a backup, we could use the stock recovery files, and if a partition is not in there, we could compare an unlocked device to a newer version that can't be unlocked yet.