yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" General] usman3206:
it just reboots into system, if i keep pressing it then kindle fire logo keeps coming again and again but when i release buttons it just boots system.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Alternatives/clarification:

- Option #1: press <power>+<vol-down> for 1-2 sec then release <power> button (device should NOT be tethered)

- Option #2: Boot into system (presumably Fire Nexus), tether and open a command prompt. Issue command 'adb reboot bootloader'. What happens?
[Kindle Fire HDX 7" & 8.9" General] usman3206:
option 1 did nothing and booted to normal system but option took me to fastboot with ready prompt. When execute command "fastboot -i 0x1949 devices" just gets me same prompt as if nothing has happened and when i run unlock.bat it says waiting for device.
[Kindle Fire HDX 7" & 8.9" General] DB126:
- please confirm attempts to access fastboot via power/vol buttons are being done while untethered (absolutely no cables attached to device)

- also confirm 'ready' does not appear if device is immediately untethered after ''adb reboot bootloader" command is issued/accepted

- but 'ready' does appear when device is re-tethered while in fastboot mode, correct?

- if all the above is true have you tried a different USB cable as previously suggested?

My concern here (as it has been for the past 24-36 hours) is device may have a flaky usb port and/or cable. Been trying to eliminate that possibility but keep getting distracted by random posts that fail to clearly distinguish between driver/software and possible hardware issues.
[Kindle Fire HDX 7" & 8.9" General] usman3206:
You could be right about a faulty usb cable/ flaky usb ports on my pc. But then why is it that adb commands are executed without any trouble? I think software issues are at their optimum since in windows it now shows ADB composite ADB interface, and executing adb reboot bootloader takes me to fastboot mode with "ready" prompt.

But key combinations do not take me to fastboot mode no matter how many times i have tried with pressing power plus volume down key for 1-2 seconds or longer or leaving power button in 1-2 seconds or longer (while completely untethered).

If adb reboot bootloader command is executed in normal system mode it immediately gets in fastboot mode with "ready" prompt but when i unplug cable the ready prompt remains there and when i reattach it with pc then it shows offline and plugging multiple times shows offline unless i change usb port on computer whence it would again show "ready".

Feels like flaky usb/cable, isn't it but why then adb works so well? i think i will try to buy a smaller length good quality cable tomorrow to see if that makes things better.

I am just a single step away from bootloader unlock and just can't do it?

feel so pissed off.:crying:
[Kindle Fire HDX 7" & 8.9" General] draxie:
That combination only works on *unlocked* bootloader.

I wish that wasn't the case, but -unfortunately- it is.

I just happened to test it yesterday. You can try yourself.

Once you manage to unlock power+volUp will get you

into fastboot. Then run

fastboot -i 0x1949 oem relock

poweroff, and try the same combo, unless your device differs

significantly from mine, it won't work, tethered or not.

That's really odd. Could be HW...

You _could_ also try the fastboot-only driver from Amazon.

(I don't recall the name, but thry have 3 drivers: adb-only,

fastboot-only, and composite.) You'll probably want to switch

back later, but it may be worth a try.

BTW, that "access denied" error was on a Linux box, wasn't it?

If so, that could just be a permission issue, which I've seen before

and can be easily resolved running 'fastboot' as root (e.g. via sudo).

I'm not intimately familiar with the low-level workings of the two

protocols, but they are -apparently- different enough that they warrant

separate drivers... Perhaps, fastboot depends on different, more sensitive

USB formafs/transactions that simply fail on flaky HW... (in which case,

switching drivers likely won't make a difference, unless there's some way

one can get "crosstalk" between the protocols in the composite case)
[Kindle Fire HDX 7" & 8.9" General] usman3206:
I am on windows 7 professional 64bit
[Kindle Fire HDX 7" & 8.9" General] DB126:
Going to respond to this and [MENTION=5828306]draxie[/MENTION]'s post separately but they are closely related.

Yes - that happens! I have a lovely USB cable here that works fine with adb (commands, file transfer, etc) and shows 'ready' when tethered to a device in fastboot mode. However, it will not pass any commands to the device. I have other cables that will pass adb commands but crap out on file transfers. I have assisted 3-4 (perhaps a half dozen) individuals who SOLVED their problems by changing USB cables. That's why I have asked (5 times) if you have changed cables! The USB port in this device is also known to be somewhat fragile. Possible one of the pins is loose.

Yes...and probably was early on. Downloading the massive Android SDK studio was likely a waste of time and bandwidth. The only components required are a minimal adb/fastboot package (several to choose from including these from Google) plus an appropriate driver for your device (a known working driver is linked in the thread OP). Less than 10 MB total.

Yes - this was an oversight on my part for which I apologize (kudos to [MENTION=5828306]draxie[/MENTION] for the reminder). Been a long time since I worked with an unlocked HDX. My gray matter isn't as resilient as it once was; completely forgot an unlocked device will not respond to <power>+<vol-> key combo. D'oh!

This is Windows being Windows regarding USB reattaches (especially prior to Win 8.1); don't sweat it; not your fault.

Well, what can I say. It may or may not be the cable but you/we won't know until tested. You don't necessarily need a high quality cable. I have seen good and bad $1 and $30 USD cables. Look around; you may have one hanging around from another device that will work fine.

Yep - been there.

---------- Post added at 05:58 PM ---------- Previous post was at 05:44 PM ----------

Yes, of course!! Been awhile since I worked with an unlocked HDX. Thanks for the reminder; I feel like an idiot (glad you can't publicly "+1" that).

As an aside, the "-i 0x1948" prefix is not always needed and sometime detrimental. The early build THOR I have on the bench now does not respond to any fastboot command with this prefix but does respond without it. I just relocked and unlocked it as a test. I haven't dug deeper to determine if this is a driver, host and/or device related issue.

See my previous post regarding USB cables and HDX ports.

- don't thing the problem is driver related ...

- [MENTION=569564]usman3206[/MENTION] is using a Win7 host

Nor am I...but there is a definite difference that sometimes manifests in the ability to communicate via ADB but not Fastboot as outlined in my previous post. This statement is not drawn from a single data point (like so many other "expert" contributors) but formed from multiple observations, direct and indirect, over the past several years. Then again...I have already admitted to various gray matter deficiencies so perhaps I am the one who is FUBAR ... :)
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
Using different cables and USB ports can make a big difference. Front or hub type USB ports can cause all sorts of issues, so using a port which is directly onto the motherboard is best. Also make absolutely certain that you are using a USB2.0 port rather than a USB3 port.

ADB just seems to work on most systems, but Fastboot is much more finicky.

Shoog
[Kindle Fire HDX 7" & 8.9" General] Mr McBoatface:
My post back in December and January, fastboot issue caused by faulty usb on the HDX :-

At least 1 other person reported the same issue since. All is not lost. it's possible to flash the NEXUS and CM11 KK roms without the unlocked code added to the device from fastboot. In fact I keep going back to them cause they just work 100%.

Try different PC, different USB cables and different usb ports. If you have electric contact cleaner or IPA try cleaning the usb port on the HDX. You might find a lucky combination that works .
[Kindle Fire HDX 7" & 8.9" General] hgthanh:
I have HDX 7, running room cook Nexus V2.0.5 on Safestrap 3.75

Pleas help me, unlock bootloader, exactly i must how to do..?

Thank all.
[Kindle Fire HDX 7" & 8.9" General] DB126:
This thread is filled with the information you need. See OP followed by this post which replaces steps #1 and #3.
[Kindle Fire HDX 7" & 8.9" General] draxie:
I see... I think I combined two pieces of info the wrong way.

I thought you said earlier that you could try on Linux.

And, then came a sentence after the 'access denied'

saying that it works on Windows, which made me think

you tried that on Linux. Wrong. Sorry!

---------- Post added at 19:57 ---------- Previous post was at 19:55 ----------

That _could_ also be due to the unfortunate fact that I mistyped the vendorID.... (-;

It's supposed to be 0x1949 **NOT** 0x1948...
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yep - 0x1949 did the trick. FWIW vendorID remains optional on my rig. Obviously YMMV is the operative phrase here. :)
[Kindle Fire HDX 7" & 8.9" General] atik03:
work this also with 4.5.5.2? my hdx7 didnt open the fastboot mode, when i start unlock.bat.
[Kindle Fire HDX 7" & 8.9" General] hgthanh:
Thanks Daveys

I wants ask sure befor I do it. My thor running Nexus rom v2.0.5 no need step 2?

Step 3: When i run the batch file "unlock.bat" , in case fastmode screen remains on < waiting for any device > in the Command window

I must re-install driver adb and fastboot for Thor?
[Kindle Fire HDX 7" & 8.9" General] DB126:
- step #2 is required if the LAST version of FireOS on the device was 3.2.4 or above; if unsure complete step #2

- fastboot waiting indicates the device can not communicate with the host PC. While in fastboot mode look for an 'Android' entry in Window device manager. Right click that entry and replace the driver with the one downloaded from the OP.
[Kindle Fire HDX 7" & 8.9" General] hgthanh:
After running "unlock.bat" My Thor " Fail: Unlock code is Not correct" the same image

Next step, how to do?

Thanks for help me.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Complete step #2 from the OP then try again.
[Kindle Fire HDX 7" & 8.9" General] Stickman89:
[MENTION=5488402]Davey126[/MENTION] - So from the information I have read, am I correct in thinking that those who have a firmware greater than or equal to 3.2.4 in step #2 are actually using dd to write the bootloader (aboot) taken from a 3.2.3 or lower build to expose the vulnerability again that devs have exploited to bypass signature verification?

Just if you go back enough into this thread you'll hear those informing how people who have used the rollback method to 3.2.8 cannot or must not flash TWRP or updated TWRP builds due to the aboot vulnerability being patched from 3.2.4 onwards... Should I (we) assume this is only applicable to those who haven't followed this bootloader unlock method; more specifically the boot partition overwrite via dd directed in step #2?

Since we are dd'ing the vulnerable bootloader afterwards, does this allow us to flash an up-to-date recovery. For example: TWRP v3.0.3-1?

I'll basically be performing a rollback from Fire OS 4.5.5.2 > 3.2.8 Rollback OTA then initiate this, the OP unlocking bootloader procedure on a Kindle Fire HDX 3rd Gen 7" Thor device - and finally afterwards updating TWRP to v3.0.3-1.

I'm more then at home with adb and fastboot. Hell, I'll even contribute to development for this device - cook us up some roms and what not - just I'd rather be absolutely certain I have understood I am making correct sense of the information provided by devs and the users in this thread.

Many Thanks.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Hi [MENTION=458344]Stickman89[/MENTION] - welcome to the HDX forums.

Being a legacy device there are numerous outdated (but largely accurate at the time) posts floating around various threads. Kinda messy. In Sept 2016 [MENTION=5594063]ONYXis[/MENTION] revealed that a vulnerable bootloader could be flashed without triggering anti-rollback protections which was the belief (backed by numerous unrecoverable bricks) dating back to early 2014. That was a game changer as I'm sure you can appreciate. Fast forward to today: any rooted 3rd gen (not 4th) HDX can be provisioned with an vulnerable bootloader that can be easily unlocked regardless of existing firmware revision. That opens the door to booting (or installing) any HDX compatible custom recovery including TWRP v2/v3 (v3.0.0-1 recommended; 3.0.2/3.0.3 have some issues; separate topic). And, of course, any HDX custom ROM. At present only LinOS 14.1 is being actively maintained due to developer resourcing (time). HDX is a very challenging device to support due to custom (often undocumented) Amazon binaries dating back to Android 4.2/4.4. You will want to touch base with [MENTION=5749760]ggow[/MENTION] and/or [MENTION=4243514]Hashcode[/MENTION] if interested in assisting w/ROM development. [MENTION=5594063]ONYXis[/MENTION] and [MENTION=5828306]draxie[/MENTION] are excellent resources as well.

Tip: see posts #550-560 (approximate range) for a streamline method for generating the bootloader unlock code. Full credit to [MENTION=5828306]draxie[/MENTION] for that nice piece of handy work!
[Kindle Fire HDX 7" & 8.9" General] hgthanh:
I working Step 2. Error " No such file or directory"
[Kindle Fire HDX 7" & 8.9" General] DB126:
Appears you did not download 'twrp_cubed.img' or move it to the c:\windows\system32 folder. If you don't understand find someone local to help before you brick the device.
[Kindle Fire HDX 7" & 8.9" General] hgthanh:
Thank a lot!

I unlock success.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Well done. Enjoy your liberated HDX!
[Kindle Fire HDX 7" & 8.9" General] usman3206:
[MENTION=297200]Davey[/MENTION]; but I am still stuck. I am unlucky. I have tried multiple usb cables and multiple port but situation is same "waiting for device". Today i tried it with a brand new Lenovo laptop with windows 10 but this time executing fastboot command took my kindle hdx 7 to fastboot mode but without the "ready" prompt, i tried with the that win10 laptop thru all usb ports and multiple cables but never "ready" prompt appeared and windows10 was "waiting for device". any ideas, i am reading threads associated with fastboot.
[Kindle Fire HDX 7" & 8.9" General] Mr McBoatface:
Power off your tablet. When powered down press the volume + button and then the power button keep holding them until you see the Kindle logo at boot. When you see that release the power button the the volume up button. If you successfully flashed twrp recovery it should load.

Post back your results
[Kindle Fire HDX 7" & 8.9" General] DB126:
Procedure is correct (of course!) but not sure which member you are responding to. Last poster [MENTION=569564]usman3206[/MENTION] is looking to unlock the bootloader and can not establish host/device communication. There's a long history in this thread. I believe he is close now (different host; new USB cable) as not getting a 'faux' fastboot ready prompt. Just need to get the Win 10 drivers straighted.

On the road today so can't provide further guidance - sorry!
[Kindle Fire HDX 7" & 8.9" General] Mr McBoatface:
Yeah just noticed that. Saw usman3206 quoting your previous post and assumed it was hgthanh.

Must get the eyes tested ?

Usman3206 what is the HDX in fastboot mode showing as in device manager when connected to your PC ?
[Kindle Fire HDX 7" & 8.9" General] atik03:
Unlocking 4.5.5.2 possible?
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yes. Any rooted 3rd gen HDX can be unlocked. Root is the only prerequisite.
[Kindle Fire HDX 7" & 8.9" General] usman3206:
I think i unlocked the device! See the screenshots
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
Yes looks like you have.

Shoog
[Kindle Fire HDX 7" & 8.9" General] draxie:
AND, soon even that prerequisite will vanish... (-;

---------- Post added at 11:09 ---------- Previous post was at 11:08 ----------

Given the *loooong* struggle, would you care to share what made the difference?

Others might find that helpful...
[Kindle Fire HDX 7" & 8.9" General] usman3206:
I finally could fix it, Special thanks to [MENTION=297200]Davey[/MENTION], [MENTION=5828306]draxie[/MENTION] and [MENTION=7218819]Shoog03[/MENTION] for their patience and persistent guidance.

Your guys are amazing, i mean you give your valuable time to people like me for nothing in return literally.

The issue that was haunting me was the "drivers" cause when i used pdanet drivers they instantly worked.

I have installed LineageOS ROM. It's a wonderful ROM but i have some strange issues, my device has issues like sliding not working in recovery sometimes and at times roms works flawlessly but at other times the device would not work like when i unlock pattern lock it would partially show my tracings and i have to push power off and on buttons toggle screen and then try again. similarly sometimes, apps would launch automatically, is there an issue with screen, digitizer or with the rom itself. The camera app crashes without ever turning on camera.
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
In the end I loaded CM12 on mine and though it went straight into storage thereafter, I encountered no issues with it at all.

Quite often these ROM's are buggy and if the developer loses interest half way through they remain buggy. This is why the earlier ROM's such as CM11 and CM12 tend to be better than the later ones since the device was still fresh and had developer interest. At this stage it will be hard to find a committed developer who will have any interest in this device. Coupled to this is that it takes real skill to develop ROM's for the Kindles because the Fire OS has lots of propitiatory elements which need cracking before a ROM will be fully functional, camera support seems to be a real issue.

So I would recommend trying different Rom's until you find one without bugs, and as I said CM11 and CM12 are both very mature and stable and give up nothing on the functionality over the like of CM13 and CM14.

Shoog
[Kindle Fire HDX 7" & 8.9" General] usman3206:
I always respect your opinions and would definitely try those roms but why is touch so buggy in twrp?
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
Don't know much about TWRP but it has been said that one version is buggy in of itself on the Kindle. Your going to have to trawl back through the thread to see which version of TWRP is best, though I think it was mentioned in the last 5 pages.

There is of course the possibility that your Kindle is buggy.

Shoog
[Kindle Fire HDX 7" & 8.9" General] usman3206:
Can you suggest a ROM that had the best experience with your device, i want to try that (if possible give link since i am getting confused finding multiple roms with similar names). In previous pages [MENTION=297200]Davey[/MENTION] suggest that i go twrp version 3.0.0.1 and i downgraded to that version but some people are saying that 2.8.7 or something in that version list is better.

Update: is this better https://xdaforums.com/kindle-fire-hdx/development/rom-cm-11-safestrap-20150628-unofficial-t3145547 because this one has some issues https://xdaforums.com/kindle-fire-hdx/development/rom-cm-12-unofficial-apollo-thor-t3050199 but these are based on older versions specially cm11 is on kitkat
[Kindle Fire HDX 7" & 8.9" General] atik03:
i have problems with unlocking the bootloader! I habe 4.5.5.2 use kingroot.

what i do:

i go to adb directory; enter adb devices and see my hdx; enter get_code.bat; "unlock.code" is generated; copy "twrp_cubed.img" and "aboot_vuln.mbn" to root;

enter adb shell; su;

when i enter:

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

or

dd if=/storage/emulated/0/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

dd if=/storage/emulated/0/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot

i get the message "no such file or directory"

then i look with es explorer: in dev/block/platform/ there is no directory called "msm_sddc.1" i have a directory called "omap_hsmmc.1"

can someone help me?

thank you
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
Try the CM12 you linked to, I think thats the source I used.

However the CM11 you linked to is the version my wife has used for over a year without a single issue.

Shoog
[Kindle Fire HDX 7" & 8.9" General] DB126:
- TWRP 3.0.0.1 is fine

- no TWRP build has touch issues (unless using the wrong device build)

- TWRP touch and "glitches" across multiple ROMs suggest a hardware issue

- all custom of the ROMs for this device (based on Android 4.2-7.1) are highly stable; I have used them all

- radio (primarily BlueTooth) and camera support are the primary functional differentiators for unlocked devices

- my daily driver is CM 12.1...a choice based solely on Xposed dependencies which has nothing to do with HDX specific customizations or compatibility

---------- Post added at 04:10 PM ---------- Previous post was at 03:56 PM ----------

Fascinating interpretation that simply does not align with reality...especially comments regarding developer interest and ROM maturity. The last sentence outlines the real culprit combined with developer availability (life balance) which has nothing to do with waning interest.
[Kindle Fire HDX 7" & 8.9" General] Shoog03:
CM13 had buggy camera support on my Thor, so I would have to disagree with the comment that all ROM's are stable and usable. CM13 was fairly much abandoned when CM14 came along and it seems that it was never fully fixed. Thats a fair basis to make the statements I made.

Shoog
[Kindle Fire HDX 7" & 8.9" General] DB126:
CM13 is tagged 'Legacy' which is different than "abandoned". Other ROMs are flagged as 'Discontinued' when a suitable replacement exists. None of these actions were taken lightly by the development community or driven by a lack of interest. As you accurately noted development for this aging device is both time consuming and difficult. Kudos to the developers who STILL (unselfishly) invest their time and talents for the benefit of the XDA community.

Camera support has nothing to do with ROM stability. Usability is a personal assessment. I never use the camera on HDX devices so is irrelevant to me. I respect your choice to go with something else based on this requirement.
[Kindle Fire HDX 7" & 8.9" General] usman3206:
Camera is irrelevant for me too, no one buys this device to take selfies. Is there a way to check digitizer or asses screen touch objectively?
[Kindle Fire HDX 7" & 8.9" General] DB126:
HDX devices do not have onboard digitizer diagnostics. To be honest I typically use TWRP to informally assess basic panel performance. Crude but effective.

Looking at the big picture (several "glitchy" ROMs; partial paints; lock screen freezes, inconsistent touch response, etc) think you have a buggy/defective device. Kinda thought that from the start as evidenced by several posts to that effect. Why I focused on flashing Fire Nexus early (to further evaluate device stability) versus unlocking the bootloader. The latter has nothing to do with overall device stability.

Obviously you have learned a lot. Next device will be a lot easier.
[Kindle Fire HDX 7" & 8.9" General] usman3206:
I have noted that every ROM works really great until i start installing apps, after installation of a few apps it becomes glitchy, plenty of space is still present (more than 70%) but performance becomes glitchy!
[Kindle Fire HDX 7" & 8.9" General] usman3206:
Thanks, this CM-12.1 is much better and had the least glitch of all the ROMs that i used and i have again reinstalled it and for the last few hours it hasn't glitched at all and is going very smooth. But now certain apps say that the device is not rooted and are asking me to root it. I have flashed supersu but result is the same. How to approach it? I will again give cm 14.1 a try since nougat was much better polished but this one too is very good.