yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] gr8fuldee:
Factory Fastboot Cable to Unbrick KF HDX 7

Hi. I was looking to root my KF HDX 7, but was unable to figure it out by myself, so my ex-husband tried doing it (as he considers himself techy). He ended up bricking the device & it won't turn on at all. Amazon sent a factory fastboot cable, but I'm unsure how to use it correctly. I followed some steps I read on here, which were simply to plug into a computer, hold the power button for a couple minutes, let it sit & then power it on. This didn't work, but my computer did go from seeing it as just a USB device to recognizing it as QHSUSB_BULK. I'm using my Windows 7 partition to try this, but normally use Zorin. Not sure what other pertinent info there is to include, but will answer any questions you have...I have AML & my Kindle is the only thing that helps me get through the hours of chemo. PLEASE help!! :(
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] sd_shadow:
I'm not sure a fastboot cable is compatible with the HDX 7", if it is be sure the Kindle is off, and just not showing anything on the screen.

connect fastboot cable to kindle, then to pc, kindle should boot directly to fastboot mode, but pressing power maybe needed. If screen doesn't say Fastboot Mode, it's not good.

also could connect the fastboot cable to kindle and pc, then hold the power button for 20 secs.

If you bough this kindle new direct from amazon, you likely can return it

[MENTION=6815340]Cl4ncy[/MENTION] and [MENTION=5488402]Davey126[/MENTION] will know more.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] EncryptedCurse:
fastboot mode is useless without an unlocked bootloader.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Sorry for your situation. As others noted a Fastboot cable is of no use. The Amazon agent made an error. Your only option is to seek an in-warranty exchange if your device qualifies.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] gr8fuldee:
This is too bad. The warranty expired in Dec of last year, so there's no hope of replacement. I've tried 3 different reps at Amazon. I read in another thread here that if your device is recognized as QHSUSB_BULK that you were not hard bricked though & can still recover the device. I went through the steps listed on that discussion, although they didn't work for me. Just hoping there was another method...
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] ^Apo^:
Hi everyone, I want to upgrade my Fire HDX 7 to CM12.1, but I get stuck at the very first step.

I have 13.3.1.0 installed, so I have to upgrade to get TWRP running.

So I tried putting update-kindle-13.3.2.4_user_324002120.bin (and after that update-kindle-13.3.2.5_user_325001120 and after that update-kindle-13.4.5.2_user_452004120) via USB to the Internal Storage. Always just one file, not all at the same time.

After it was copied to the internal storage I rebooted tapped on "check now" at the system updates, but I only get a message that a network connection is nessassary.

What can I do to upgrade my 13.3.1.0? Is there maybe a full tutorial to get from 13.3.1.0 to cm12.1?

Best regards,

Apo
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
If you have 13.3.1.0 you do not need to upgrade. Suggest path:

- if necessary root and block OTA using HDX toolkit (here). Network connection not required

- flash twrp (here) using adb commands in OP. If you aren't comfortable with adb you can slide load flashify (here) to install twrp

- update bootloader to v13.3.2.3 (here)

- access twrp recovery (power + vol-up) and immediately make a backup of your device. When complete restart FireOS and copy/move the backup to another device via usb tether. Don't skip this step; if things go wrong later you'll be glad for the backup.

- follow [MENTION=6815340]Cl4ncy[/MENTION]'s guidance to unlock the bootloader (here). This will likely be a frustrating experience but necessary to run many roms including CM12.

- once the bootloader is unlocked you can flash either CM12 or SlimLP

Note this is a high level overview. Details can be found in the linked threads. Plan on spending time reading before diving in. Kindles in general and HDX models in particular are sensitive devices that are easy to brick and nearly impossible to recover. Make sure you clearly understand each step before proceeding. Post questions before taking a chance; never guess. As you probably surmised there are no step-by-step guides or helpful videos. However, with patience and perseverance you'll score big as a HDX is beautiful and power device once freed of its FireOS shackles.

Good luck.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] ^Apo^:
Thank you very much Davey for your fast and extensively response!

At your linked twrp thread there is the sentence: "Ensure you are running stock firmware .3.2.3.2"

Can I safely ignore that? Because that's the cause I wanted to upgrade :)

At the step with the bootloader, you linked Cl4ncy's Profile twice instead of the unlock thread.

I'm not too lazy to search the thread by myself, but I don't want to brick my HDX and at the android development section he is only the thread starter of the "flash twrp" thread.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Cl4ncy:
Yes you can ignore that, TWRP is safe to install below 3.2.4, at least proven from 3.1.0 to 3.2.3.2, thus rooting and installing TWRP are the way to go.

The correct links to the unlock procedure are here and here, probably needed Windows drivers here.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Sorry about that. I see [MENTION=6815340]Cl4ncy[/MENTION] has responded (thanks!). Keep plugging away and don't hesitate to ask questions if unsure.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
Sorry, is there anyway to check? What can I do if the boot loader lock? Or unlocked?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Ask your friend what he was doing when the device borked. Highly unlikely it can be recovered; really don't wan't to run the fish bone on an unknown device.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
I been asking my friend what did he do/guide he has followed to did on this device, but he is a non-tech person so that's all I got right now.

Would appreciate if you can give me some tips to work on to recover this HDX 8.9, I have some days off to spend working on this.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
If your friend is not technical it is highly unlikely he/she got to the point of unlocking the bootloader. Unfortunately, locked HDX devices are almost always unrecoverable when a ROM or custom recovery can not be booted. If the device had a very old version of FireOS (typically 3.26 or lower) there is an outside chance it can be recovered using the methods outlined in this thread.

Another option is to replace the motherboard and possibly daughter board. How successful this will be depends on your skill/experience with disassembling small electronics and how well the seller reconditioned the board(s).
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Ufdah:
10yr member with a Noob-like question... I have a HDX 7 "Thor" with Safestrap 4 and the HDX Nexus rom v4.0.5 installed. Everything works fine but I've been wondering if there's anything better out there. Would you be able to recommend a relatively stable new ROM that I could install to breath some new life into this aging tablet? I'm willing to unlock the bootloader if there are non KitKat ROM's that are better. Thanks!
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Give consideration to unlocking the bootloader opening the door to CM 14.1 (Android 7/Nougat) which is the only ROM for this device still under active development. If that feels out of reach suggest installing Fire Nexus HDX which is the immediate succesor to Nexus 4.0.5 and the newest Safestrap v4 compatible ROM. No advantage going with CM 11 which is the only other Safestrap v4 compatible ROM.

https://xdaforums.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Run this command to see if your bootloader is locked or unlocked:

fastboot -i 0x1949 oem idme \?

If you get something other than

FAILED (remote: oem idme not allowed for locked hw)

you're in luck.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
It's seem that the adb didn't recognize my HDX, its just so the line <waiting for device> whe I enter the command.

Command adb device does not so any device connected.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Need to update drivers on host machine. See OP in this thread for link.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
That sounds like a good idea (although the

fact that 'Ready' pops up when a cable is

connected indicates _some_ exchange

between the host and the device).

In any case, use

fastboot -i 0x1949 devices

instead of 'adb devices'.

I thought you guys have already established

a few posts back that on a device that boots

directly to the 'fastboot' prompt there's no use

trying 'adb' commands.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
yes, I did get this message:

FAILED (remote: oem idme not allowed for locked hw)

I'm so excite, what should I do next :D
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
I'm not sure why you're excited seeing that your HDX is **locked**.

AFAIK, you cannot flash anything on locked HW (not even properly

signed images from Amazon). I used to have a theory that

fastboot -i 0x1949 update update.zip

_MIGHT_ work based on the fact that 'fastboot' doesn't reject

the command right away with a similar "not allowed for locked hw"

message, but chances are that even the 'update' command will be

denied later on, since the actual implementation might use the

same 'flash' commands that are rejected immediately.

I'd be happy to verify (or falsify) the above theory by assembling

an 'update.zip' for you [this needs to be in a special format, which is

*different* from Amazon's OTA updates], if you're interested in testing.

I don't suppose you have much to lose at this point, but I wouldn't

get my hopes up too high either, if I were you.

---------- Post added at 20:03 ---------- Previous post was at 19:24 ----------

I've just experimented some more with potentially interesting 'fastboot' commands,

and it seems that 'erase' is also accepted, although I'm not convinced it has any effect.

For obvious reasons, I've only tried to erase 'cache' and 'recovery' and didn't notice

any changes (booting into recovery still worked afterwards). You _could_ try

fastboot -i 0x1949 erase recovery

and see if it makes any difference on your device. While you're at it, you might as well

test replacing 'recovery' by 'boot' also. If you had a working 'boot' or 'recovery' partition,

your HDX wouldn't get stuck at the 'fastboot' prompt; so, there's little harm in trying...

If you are REALLY adventurous, you could also try 'erase aboot', but keep in mind that

-if successful- that would nuke the very bootloader that still gives you that 'fastboot'

prompt; so, think **twice** --NO: 3 times!-- before testing that one.

On the other hand, there's an outside chance that wiping the bootloader would cause

the device to "fail open" and expose it's internal flash as a USB drive as we had seen

in a recent case, BUT -and read this a few times to let it sink in- there are NO GUARANTEES,

as you'd likely be the first one to try (the other case was a re-flash gone wrong, and who

knows, it might matter what data is flashed to 'aboot' [it was the initial part of a proper

ANDROID! boot image in that case]).
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
Well, I'm excited because you said at the previous post if I got that message, I'm in luck! So I thought that my device is now recoverable.

And yes, I would do anything as your instruct at this rate. So, should I enter those command as your last post to see how my device react to it, or waiting for your update.zip?

Thanks
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
In fact, I said the exact opposite.

I suggest you reread that message

with special attention to the words

"something **other** than". (-;

I'm not quite sure when I'll find the time to prepare that 'update.zip',

but I'll try my best to get it to you this week. (No promises, though.)

In the meantime, you could test the first 2 variants; that is, erasing

first 'recovery' and then if that didn't have any effect also 'boot', but

don't touch 'aboot' yet if you want to have a chance to try the 'zip'.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
Sorry for misread your post, I see it now :(

After enter the 2 commanf "erase" and "boot", I get the messages as the picture attached, then restart the device and it goes to fastboot as nothing change, is this good?

http://cloud.tapatalk.com/s/5892713d2c859/DSC_1130.JPG
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Well... that supports the theory that these 'erase' commands have no effect.

Good or bad, you decide... They certainly didn't seem to help, in any case...

I've put together an update.zip for you to try. I also tried it on my test-HDX,

and got the usual "not allowed on locked hw" message *after* the upload,

when flashing was supposed to take place... In other words, this looks a lot

like a dead-end, but I sent you a PM with a link, in case you want to give it

a try (although you should expect to see the same result as I did).

In the extremely likely case that 'fastboot -i 0x1949 update update.zip'

doesn't work for you either, you could try to erase the 'aboot' partition.

Based on your prior experience with 'boot' and 'recovery', my current

expectation is that this will have no effect either, but that one I've not

tried; so, I'm not 100% sure. **BEFORE** you decide, however, I'd like you

to understand that if the erase does work, even that fastboot prompt

that you still have at the moment will disappear, and your chances of

ever recovering the tablet (without swapping HW) will drop from very

close to zero to even closer to zero (unless you happen to experience

the same failure mode I had referenced before, which may or may not

happen). I certainly won't take responsibility if things don't work out.

This is a call you need to make. What I'm trying to do is provide you

with as much info as I can to help you make an informed decision.

Apropos, informed decision: there's another faint possibility for recovery

from your current fastboot-only state *IF* you're friend did actually flash

the vulnerable bootloader, only "forgot" to unlock it. If I were you, I would

definitely ask if they saved the EMMC-id (manfid + serial) for that tablet.

In fact, just the serial number (from /sys/block/mmcblk0/device/serial)

would be sufficient, since the manufacturer's id can be retrieved via

'fastboot -i 0x1949 getvar emmc_mid'. I've been looking through 'aboot'

to see if an 'emmc_sn' or similar might turn up, but to no avail.

BUT, there _may_ be a way to get the info even in 'fastboot' mode,

except we don't yet know how..
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
I did get the messages as below:

so I'll try aboot next for your expirement :)

---------- Post added at 02:12 AM ---------- Previous post was at 02:06 AM ----------

well, after enter erase aboot, then reboot the tablet, my computer show 8 local disk, and the tablet does not seem to boot in to fastboot anymore. I guess that's it then :)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
JackPot!?!

Are you kidding me? Or is this for real?

That sounds a lot like a JACKPOT,

but let's not get carried away... (-;

Have you tried to identify your aboot & TWRP partitions,

and flash the vulnerable aboot and a recent TWRP image?

I've just checked both my primary and my test Apollo and

both have 'aboot' as partition #6 and 'recovery' as #18.

You can try dd for Windows to flash those partitions.

First identify the disk corresponding to your tablet

(you should see 20+ partitions), using

dd --list

You may have to 'Run as Administrator' for this (and the next!) command to work.

Once you got your disk number, replace the RED X below accordingly:

dd of=\\?\Device\Harddisk[COLOR="Red"]X[/COLOR]\Partition6 if=aboot_vuln.mbn

If you don't already have a copy of the vulnerable aboot, you'll find a Google Drive link here.

Make sure to use the right version for your device! (It was an Apollo, wasn't it?)

And, while you're at it, you might as well flash TWRP also.

You'll need that to figure out your unlock code, anyways.

dd of=\\?\Device\Harddisk[COLOR="Red"]X[/COLOR]\Partition18 if=twrp_cubed.img

[Sorry for having fallen of an edge here. I saw your first post,

but never got a notification about the next (probably because

the system auto-merged them). Darn...]
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
can you attached the program or upload it somewhere? I cant get the webpage to load to download dd for windows :crying:
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Can you try again?

Somehow I managed to insert a LIST in that link....

Here it is in plain, in case your Google-fu is not sufficient:

http://www.chrysocome.net/dd
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
I managed to get the ddrelease64 and dd-0.5, but both version does not appear to have the result as wanted, nothing happen when I enter the command dd --list, also Run as Adminstrator :(

rawwrite dd for windows version 1.0beta1 WIN64.
Written by John Newbigin <jnewbigin@chrysocome.net>
This program is covered by terms of the GPL Version 2.

dd --list
dd --list
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
That's really odd. Does the output you're showing come from ddrelease64.exe?

That "version 1.0beta1 WIN64" is not even listed in the table closer to the bottom

of the page I linked to... I've just tested dd from dd-0.5.zip and --list worked as

expected on Windows 8.1 (32-bit), just running straight from an ordinary cmd

window (no admin privileges required). What version of Windows do you run?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
Im using windows 10 64bit, both version have the same result. So, just to clarify, I run the exe of dd fpr windows and enter the command straight from the new window open after run dd right?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
I wouldn't think so.

You need to open a command window,

navigate to the directory with the dd executable,

type 'dd --list', and hit enter/return.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
Thanks for keep patient with me :)

anw, after running the dd the correct way, I got this result:

C:\Minimal ADB and Fastboot>dd --list
rawwrite dd for windows version 0.5.
Written by John Newbigin <jn@it.swin.edu.au>
This program is covered by the GPL. See copying.txt for details
Win32 Available Volume Information
\\.\Volume{6ebddaa1-d05f-4b81-bbb1-dda0f515c66a}\
link to \\?\Device\HarddiskVolume1
fixed media
Mounted on \\.\d:

\\.\Volume{11475ea8-6dac-4d6b-8a56-1cce8e15b8aa}\
link to \\?\Device\HarddiskVolume3
fixed media
Mounted on \\.\c:

\\.\Volume{9b856e37-30fe-50b0-e6e5-e4d4413f8704}\
link to \\?\Device\HarddiskVolume4
fixed media
Mounted on \\.\f:

\\.\Volume{dba8f1d3-c55d-9c38-613d-f11d9ea4d936}\
link to \\?\Device\HarddiskVolume8
fixed media
Mounted on \\.\i:

\\.\Volume{303d725a-d01d-5119-8b39-782b2cd4a60f}\
link to \\?\Device\HarddiskVolume13
fixed media
Mounted on \\.\j:

\\.\Volume{9cbef8a9-7c2b-6b2b-a7b8-62e5c8fa0fc5}\
link to \\?\Device\HarddiskVolume20
fixed media
Mounted on \\.\k:

\\.\Volume{5fbf1111-8ab7-a097-31d7-71a01b1f60fe}\
link to \\?\Device\HarddiskVolume22
fixed media
Mounted on \\.\l:

\\.\Volume{e2f58113-b94a-557e-142e-8b01f1e2ed0f}\
link to \\?\Device\HarddiskVolume23
fixed media
Mounted on \\.\m:

\\.\Volume{2036dea8-183b-8faf-4a53-dbf6fcd777eb}\
link to \\?\Device\HarddiskVolume24
fixed media
Mounted on \\.\n:

\\.\Volume{c5a1f09b-1ee9-95ec-fb68-135d458472e7}\
link to \\?\Device\HarddiskVolume25
fixed media
Mounted on \\.\o:

\\.\Volume{cfa77e34-a23a-b1ec-6f21-d927a2eb8580}\
link to \\?\Device\HarddiskVolume26
fixed media
Mounted on \\.\p:

NT Block Device Objects

Virtual input devices
/dev/zero (null data)
/dev/random (pseudo-random data)
- (standard input)

Virtual output devices
- (standard output)

C:\Minimal ADB and Fastboot>

HardiskVolume 1 & 3 are my PC's drive, and other are from my Apollo, so could you help me for the next step, I'm not quite understand your previous post about finding my X disk number, does that mean I have to run each command for the HarddiskVloume 4,8,13 20, 22, 23, 24, 25, 26?

Thanks
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Is this the complete output of 'dd --list' on your system?

The "NT Block Device Objects" section near the end,

which normally lists the links in the format given in

my earlier post, is empty in what you posted.

Without that information, I won't be able to help you.

Of course, 'dd' is not the only tool that can list disks,

volumes, partitions, etc.; but we do need to figure out

which disk number corresponds to your Kindle.

You could try the built-in Disk Management tool...

http://www.disk-partition.com/windo...gement/extend-volume-with-disk-management.gif
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
Yes, that is the complete output

My Diskmanagement screenshot as below:
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
According to your screenshot, X=3.

Before you proceed with flashing, you may want to verify

that your 64MB drive F: with a FAT filesystem corresponds

to a partition (in fact, partition #1) on Disk3, and contains

a single folder 'image' with a bunch of .bIJ and .mdt files.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
I got an error for the aboot-vunerable but success with TWRP as the code show below:

/the disk and file show exactly how you discribed (the F partitions have an image folder with a bunch of *.bxx and mdt files.

C:\Minimal ADB and Fastboot>dd of=\\?\Device\Harddisk3\Partition6 if=aboot_vuln.mbn
rawwrite dd for windows version 0.5.
Written by John Newbigin <jn@it.swin.edu.au>
This program is covered by the GPL. See copying.txt for details
Error reading file: 87 The parameter is incorrect
677+1 records in
677+1 records out

C:\Minimal ADB and Fastboot>dd of=\\?\Device\Harddisk3\Partition18 if=twrp_cubed.img
rawwrite dd for windows version 0.5.
Written by John Newbigin <jn@it.swin.edu.au>
This program is covered by the GPL. See copying.txt for details
20100+0 records in
20100+0 records out
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Check my answer to a question on the exact same error.

It's probably inconsequential. BTW, unless you manage to flash

a proper bootloader (signed by Amazon), like the vulnerable

version, the HDX will likely remain in "download mode".

Have you tried to power off and boot into recovery (Power + VolUp)?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
Wow, I can boot into recovery now :) what should I do next?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Antonntminh:
Ok, so I have read the guide on how to unlock bootloader https://xdaforums.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982

I boot my HDX to TWRP -> Advance -> ADB Sideload, connect my HDX to my PC.

When I run the file get_code.bat I got this error messages as below:

adb: error: connect failed: closed
error: closed
error: closed
adb: error: connect failed: closed
error: closed
Press any key to continue . . .

although adb devices recorgnize my HDX as normal