yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" General] DB126:
- long press <power> for 15 sec to ensure device is fully OFF

- press and hold <power>+<vol-up> to boot into TWRP

- also try <power>+<vol-down> to boot into bootloader

- if no response device is likely not salvageable without expert assistance
[Kindle Fire HDX 7" & 8.9" General] Apfelman123:
Nothing happens :(
[Kindle Fire HDX 7" & 8.9" General] aedahh:
getting error Catastrophic failure(0x8000ffff): Send configure command)

Hello I am getting error

getting error Catastrophic failure(0x8000ffff): Send configure command)

Any idea how to review my FireHDX?

My HDX was stuck in "Fire OS is Upgrading" boot loop, so I was hoping your guide can help revive it.

Thanks
[Kindle Fire HDX 7" & 8.9" General] DB126:
See if it will boot into stock recovery:

- untether device

- long press power untill fully off

- press <power>+<vol-up> to bring up stock recovery menu

- repeat above a few times if not initially successful

If stock recovery is available/stable FireOS can be reloaded (don't attempt to downgrade; device will brick). Post back if you need further assistance.
[Kindle Fire HDX 7" & 8.9" General] 包海军:
Now，do you have the newest version of emmcbld.mbn for the 3.2.8 rom？
[Kindle Fire HDX 7" & 8.9" General] å¡«ä»€ä¹ˆ:
what's wrong with this?

I am not good at English

when i use the miflash,it works,but it says "missed hello packet,try to recover",what should i do ,thank you!

I am a Chinese,this is my QQnumber 1450736295

I hope you can help me

Thank you!
[Kindle Fire HDX 7" & 8.9" General] yachxc:
Thank you for providing this method, recently I got a 8.9 3rd with brick at kindle fire logo, and it had no response when connecting to the computer. It was working with cm11 and cm12, and was bricked after flashing 4.5.5 by last owner. After searching, I follow this thread to try unbrick, now hdx can enter into system, but the screen has no response to touching operation, and can't enter recovery, no matter press vol+ or vol-, hdx directlyload stock system. It seems like volume button not working, just like touch screen, but I'm not sure is this physical or not. BTW, system can not save time after forcing shutdown and restarting, time is reseted to "TUE, JUL 30 12:00" every time on lock screen. Is this a valuable information?

Now I find one solution to get touch screen rework: https://xdaforums.com/showpost.php?p=56986107&postcount=22, but I can't get access of adb, and can't enter into recovery of fastboot. By using fastboot cable first, then replace with normal data cable, computer has an unkown usb device, but it doesn't show in device manager, is there has a way to active adb, recovery or fastboot?

Wating for anyone could help, thanks anyway.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Please don't cross/double post in multiple threads (https://xdaforums.com/kindle-fire-hdx/help/help-half-brick-hdx-8-9-3rd-t3650575)
[Kindle Fire HDX 7" & 8.9" General] yachxc:
Sorry for this, should I delete one of posts?
[Kindle Fire HDX 7" & 8.9" General] DB126:
No - it's fine. I have your post queued up for a second look; believe an alternate set of drivers (not the one's normally recommended) may permit adb/fastboot access. Not certain that will help given the state of the device but you're pretty much stuck without it. Stay tuned.
[Kindle Fire HDX 7" & 8.9" General] DB126:
Try installing drivers from this post on a Windows host. Hopefully this will enable tethered access via adb or fastboot. Also try/verify the obviously stuff: USB ports on host (avoid external hubs and USB3 ports), cables, pins on HDX (bent or missing), etc.
[Kindle Fire HDX 7" & 8.9" General] yachxc:
Thanks for your replay, I have installed drivers from this thread，it helps hdx works in 9008 mode by using fastboot cable. There is no full system file can flash into device with miflash software besides two files in this thread. Because of unworking touch screen, although hdx can load system into lock screen, but I can't get adb access. Same reason with vol buttons, hdx can not enter into recovery or fastboot mode. So it seems like there is no way to get screen works, or flashing other system. I find one solution that useing fastboot cable first then replace with data cable, it can let hdx into fastboot mode. This solution leads "USB Device Not Recognized", and nothing shows in Device Manager. Does the method really work? If there is no way to get my hdx back, don't waste time on me. Thanks again.
[Kindle Fire HDX 7" & 8.9" General] DB126:
HDX is not like most other Android devices. There are no magic files you can flash to restore functionality. However, some devices can be recovered using extraordinary measures. Really depends on the underlying problem and your skill set.

You can try 'bulk mode' which is outlined in this post and those that it links to. Not sure how far you will get with a non-responsive touch screen. Really your best (and last) option.

[MENTION=5828306]draxie[/MENTION] - for awareness/comment

https://xdaforums.com/kindle-fire-h...ing-bootloader-firmware-t3463982/post71430759
[Kindle Fire HDX 7" & 8.9" General] yachxc:
Thanks a lot, but now I can do nothing because of the electricity failure, I will try it later or tomorrow, depends on electricity supply.
[Kindle Fire HDX 7" & 8.9" General] draxie:
See how far we can get ...

You can install your choice of ROM even without touchscreen or volume buttons,

but that won't be much use if the reason for those not working is the hardware.

Let's give it a try, anyway...

For starters, please grab the attached archive, follow the instructions below,

and let's hope that you get an ADB shell prompt at the end.

(The old flash programmer from this thread doesn't work on any of my devices,

which means I could not fully test the procedure, but this _should_ work.)

Flash my remastered recovery image to your boot partition

Extract the files 'rawprogram0.xml' and 'remastered.img' from the attached archive

to the 'fw' directory (from the OP) and follow the original instructions (from the OP)

except that you don't have to hold any of the volume buttons when you reboot.

Connect to ADB

Extract the file 'adbkey' from the attached archive, set the environment variable

ADB_VENDOR_KEYS to the full path of the just extracted file, kill your ADB daemon

(you probably have one running already) and connect.

set ADB_VENDOR_KEYS=/full/path/adbkey
adb kill-server
adb shell
[Kindle Fire HDX 7" & 8.9" General] yachxc:
Thx for your reply, I have already get adb authorization and root, by flashing modified boot.img from the rom cm-12.1-20160922-UNOFFICIAL-apollo through miflash(edit "ro.adb.secure=0", "ro.secure=0", "ro.debuggable=1", "persist.service.adb.enable=1", "persist.sys.usb.config=adb" in default.prop by android kitchen). After that, I followed this to getting touchscreen rework, but the new-flash recovery is not available for adb without touchscreen. Then I tried same progress as modifing boot.img on several suitable recovery.imgs, but the repacked imgs lead hdx boot into fastboot while using "adb reboot recovery". I'm waiting for get one recovery.img can get adb and root after flashing for now, what are the next steps you suggest? Also I'd appreciate it if you introduce the procedure of flash ROM via adb. "fastboot update filename.zip" does not adapt normal rom.zip, and as far as I know, there is no method can get system.img without recovery or official providing, so we can't use "fastboot flash system system.img" too, I'm curious how can install rom by adb.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Cut the crap

Ah, OK... Good job with those miflash 'skillz'! (-; ;-P

I would've preferred if you were up front with that info.

That could've saved my time trying to help you get there...

I have a distinct recollection that you were complaining

about NOT having ADB access. Oh, well...

Hopefully, the time spent won't be wasted. That archive

may turn out to be useful for someone else.

Now, let's get on with those instructions!

Assuming that you do have ADB shell access *and* a recent

version of TWRP installed (I'd put it in both boot and recovery

for good measure, but the latter should suffice; just make sure

that you don't forget 'recovery' in the 'reboot to TWRP' step).

fetch your unlock code (use get_code from unlock.zip)

This works with stock boot.img and my remastered.img.

I'm not sure about other images. YMMV

push your choice of ROM (lineage is just an example)

adb push lineage-14.1-20170710-UNOFFICIAL-apollo.zip /cache/rom.zip

instruct TWRP to perform an unattended update

(Depending on ROM, 'wipe system' and/or 'wipe data' may be useful;

just make sure you understand what the latter entails: take a backup!)

adb shell 'cat > /cache/recovery/openrecoveryscript << EOF
install /cache/rom.zip
wipe dalvik
wipe cache
reboot bootloader
EOF
'

reboot to TWRP (to perform the update)

adb reboot recovery

unlock and reboot

fastboot -i 0x1949 flash unlock unlock.code
fastboot -i 0x1949 reboot

Hold your breath and see if your touchscreen is still toast.

If it is and you need ADB access to fix it, consider installing

your ADB public key to your device (before you reboot to

TWRP for the unattended update above).

On Windows:

adb push %USERPOFILE%\.android\adbkey.pub /data/misc/adb/adb_keys

On Linux or Mac OS:

adb push $HOME/.android/adbkey.pub /data/misc/adb/adb_keys

Of course, if you need to wipe data, the above won't help.

Then, you should push your ADB public key to /cache instead,

and sneak in the following snippet in your openrecoveryscript

(after 'wipe data' and before 'wipe cache', of course!):

mount data
mkdir /data/misc/adb
cmd mv /cache/adbkey.pub /data/misc/adb/adb_keys
umount data

Good luck!
[Kindle Fire HDX 7" & 8.9" General] yachxc:
Sorry for not posting the latest progress on this thread, I just kept trying solve the problem one after one :D

Thanks for your patience on my issue, and the editing of long and detailed reply, this is a really good tutorial! Follow the instructions, I successfully installed the rom, but still get no response of both the touchscreen and vol button, so I started to wonder if it is hardware. Finally, it was found that the ribbon cable was not connected. After reconnecting two cable, it works!

Last owner said that hdx worked fine with cm12 before flash 4.5.5, so I always thought it was a software problem cased by flashing, it wasted too much time.

Thanks again!
[Kindle Fire HDX 7" & 8.9" General] draxie:
LOL... :good::crying:
[Kindle Fire HDX 7" & 8.9" General] mydanuyen:
link die , plese uplooad new link , thank all
[Kindle Fire HDX 7" & 8.9" General] fufu508:
Oops. Since I have a question, and this thread is largely inactive, I'm moving my post here. As you'll see in that post the process worked; my tablet is alive! :cool:
[Kindle Fire HDX 7" & 8.9" General] z7ua:
hdx 7

Hi. Anybody can update archive link with fw and tool

I want to try unbrick my kindle.

Thank`s
[Kindle Fire HDX 7" & 8.9" General] DB126:
So did you look at the post prior to yours?
[Kindle Fire HDX 7" & 8.9" General] z7ua:
I was read all posts and found files in another topic. Now i have new problem my pc displays my kindle hdx as usb flash 11Gb + unauthorized adb device. Kindle displaying nothing. Which next step for recovery, how change unauthorized adb device for connecting with adb?
[Kindle Fire HDX 7" & 8.9" General] DB126:
You might be done. Search the HDX forums using various keywords to find potentially helpful posts. They're often buried in threads with varying topics.
[Kindle Fire HDX 7" & 8.9" General] z7ua:
nothing turns out.

C:\Windows\system32>adb devices
List of devices attached
D0FBA0A034840ENU unauthorized

HELP ME! Say me what should I do.

I flashed mtk devices it was much more easier
[Kindle Fire HDX 7" & 8.9" General] alireza21:
need to files for unbrick thor

hi dear

the link of the files is incorrect

please give me the correct link

i need so much to this files

thanks alot
[Kindle Fire HDX 7" & 8.9" General] mydanuyen:
link die please upload link
[Kindle Fire HDX 7" & 8.9" General] fufu508:
I sent you a link via p.m.
[Kindle Fire HDX 7" & 8.9" General] mrstimpy:
Can you [MENTION=8790220]fufu508[/MENTION] or anybody else send me new links too? Thanks in advance!
[Kindle Fire HDX 7" & 8.9" General] tuanshungf:
Hello all, my friend HDX 7 have bricked to day by flashing this https://xdaforums.com/kindle-fire-hdx/development/twrp-flashable-3-2-3-bootloader-upgrade-t3025504, his device was unlocked bootloader , TWRP and running LineageOS 14.1. I don't know why he flash the upgrade bootloader upgrade package from that topic, now the hdx was bricked, and I can see QHUSB_BULK on my laptop. So someone here have a backup emmc image, plz send me to unbrick. Thank you so much..

PS: My friend HDX 7 is a 32 GB.
[Kindle Fire HDX 7" & 8.9" General] draxie:
Which QHUSB_BULK?

The HDX (and likely most other Qualcom-based devices) have several "bulk modes".

The one described in this thread with idVendor=05c6 and idProduct=9008 only allows

serial communication and needs a flash programmer. Unfortunately for most of us, the

only leaked flash programmer we are aware of only works if the device has never been

updated to a firmware newer than 1x.3.2.6 ...

The other, more useful, bulk mode with with idVendor=1949 & idProduct=9006 exposes

the internal storage directly. This should be fairly obvious to spot in Windows, since it

normally pops up a bunch of dialog boxes about unformatted partitions. If you see this,

you're in luck. Check out my post for instructions.
[Kindle Fire HDX 7" & 8.9" General] droiduzr2:
I have the fw files and the oddball files.

I also have aboot13 and aboot14 files.

I did flash with the fw files (meant for Thor) and device showed up in Windows 10 as Kindle FIre HDX 8.9 .....BUT after reboot it went to blank screen and Windows reported unknown Android device. I now have it back sitting at Qloader WinFlash screen ready to flash the proper files.

Can someone please provide the files needed for Apollo to use in MiFlash.

Thanks!

---------- Post added at 07:05 AM ---------- Previous post was at 06:11 AM ----------

UPDATE: Got TWRP 3.x loaded and boot into TWRP but my touchscreen is off...where I press does not line up to button.

I took the FW.zip files and added the Apollo14.zip info renamed the file and also renamed twrp to recovery.img.

How do I fix the touchscreen issue now?

In TWRP the buttons and where I press do not align. Using twrp 3.1.1-1

So now I try to unlock bootloader now?

Thanks!
[Kindle Fire HDX 7" & 8.9" General] iksel:
I think you used wrong Recovery...
[Kindle Fire HDX 7" & 8.9" General] DB126:
Yes, he did. Sufficiently annoyed at the reckless behavior to not want to deal with this now. Probably come back to it later.

Short answer: erase erase aboot and recovery then rebuild device.
[Kindle Fire HDX 7" & 8.9" General] droiduzr2:
I used the recovery from here, it was in post from GGNow

https://androidfilehost.com/?w=files&flid=49738

what recovery should I use?

Can someone just provide me the files I need, please.

I am checking about 5 threads with numerous pages trying to gather what I need.

Thanks

---------- Post added at 04:12 PM ---------- Previous post was at 04:03 PM ----------

What should I use? link please
[Kindle Fire HDX 7" & 8.9" General] droiduzr2:
What files do I rebuild with then?

broken links don't help people either...lol

Trying to fix this tablet for my son, appreciate some help.
[Kindle Fire HDX 7" & 8.9" General] BuffetMonster:
Unbrick kindle fire HDX 8.9?

Hi, I have a kindle fire HDX 8.9 [3rd generation,maybe!]

The device is in ‘bootloop’ state, the device is not rooted.

I tried the reset to factory boot option but it doesn’t help.

If I do a factory reset I have about 5 seconds to do as below before it reboots.

mint@mint ~ $ adb devices

List of devices attached

B0180706346707B5	device

mint@mint ~ $ adb shell

shell@apollo:/ $

Is there any hope or am I out of luck? I’m using ubuntu [mint] host btw, if it’s relevant. Many thanks for any suggestions.
[Kindle Fire HDX 7" & 8.9" General] DB126:
The files and procedure can be found in this post. Obviously some of the steps are not relevant give the device state. You need to get aboot and recovery aligned (ie: both for the proper device type) to progress normally. It will likely be a rugged journey given the state of your device. Goal at this point is to get a working, stable recovery from which you can build upon.

---------- Post added at 05:01 PM ---------- Previous post was at 04:57 PM ----------

You can unlock the bootloader using guidance/files from this post or found elsewhere in this forum. Once unlocked you can flash the ROM of your choosing including several variants built on Android 7.1 (Nougat). This is an advanced procedure that assumes familiarity with adb and fastboot. Good luck.
[Kindle Fire HDX 7" & 8.9" General] droiduzr2:
Thx.

Just to be clear...I can get into TWRP 3.x...my touchscreen is just not working right.

Also- my Kindle is on the original maybe the 2nd version of FireOS...I flashed it when it first came out with safestrap and messed up. It's been in the drawer sitting there until now. I am on OLD system.

Why can't I use WiFlash to do all of this?

---------- Post added at 11:16 PM ---------- Previous post was at 10:54 PM ----------

@Davey

I am following directions in your link.

I get this when I try to run get_code.bat

adb devices show this:

List of devices attached

B0180706347600X3 unauthorized

run get_code.bat shows this

D:\kindlefix>get_code.bat

error: device unauthorized. Please check the confirmation dialog on your device.

now what to try?

still reading all the threads also

I have spent 15+ hours trying to fix this.:eek:
[Kindle Fire HDX 7" & 8.9" General] DB126:
Likely due to having a Thor build of TWRP installed in the recovery partition. Have you tried booting an Apollo build from fastboot ready? Syntax: "fastboot boot <ApolloFileID.img>", where "ApolloFileID.img" is the name of a valid Apollo TWRP image (see below for link).

Thanks for sharing but irrelevant to the current solution. :)

Because it's an Amazon device - not a generic Android tablet.

No need to run that now; not trying to unlock the bootloader at this point. Just execute steps #6 and #7 from previously linked procedure. Notes:

- rename the file extracted from aboot-14-apollo.zip to 'aboot_vuln.mbn'

- rename the Apollo TWRP image secured from here to 'twrp_cubed.img'

- the above names should match those used in step #6

Post back once you get through step #7 and can successfully boot into TWRP ... hopefully with buttons aligned/working correctly. I'll walk you through the next series of steps to unlock the bootloader. Plan on another 48-72 hours elapsed time before you are able to boot a ROM depending on mutual availability.
[Kindle Fire HDX 7" & 8.9" General] droiduzr2:
Ok, thanks this is helpful.

I can't seem to get into bulk mode that shows all the partitions. I can get into Qloader.

How do I get into bulk mode? Remember I can't seem to launch adb or fastboot actions.

Let me ask you this. What if I edit the rawprogram.xml file? I opened it in notepad++ and I can see where it refers to the files it will use.

I am thinking if I edit the lines for the files that I do not need and insert the info to the files I need.

Then I can use MiFlash and problem solved.

Do you think it is doable?
[Kindle Fire HDX 7" & 8.9" General] DB126:
- in 5 yrs I have never seen report of MiFlash yielding success on this device

- procedure to enter 'bulk' mode is described in step #6 in linked procedure

- need fastboot working or it's game over

Can you put the device into fastboot mode and receive a positive response to the command "fastboot devices"? If using Windows are you confident drivers are correct/working?
[Kindle Fire HDX 7" & 8.9" General] droiduzr2:
I managed to use MiFlash to bring it to this far. Before it was just a black screen with Kindle logo.

I can almost use TWRP, just can't get the slide part to work all the time to execute the command.

Just asking...if I tried to flash a custom rom would the unit brick or would it work and in the process fix the touchscreen issue.

Ok, I will try the fastboot part later.

I can do adb devices in Windows 10 and it will show what I posted before with {unauthorized}.

I tried to do fastboot devices also but nothing happens. I did those when I was in "bulk mode" Qloader to use MiFlash.

It would be nice to get a win here but damn, this is a touch process.

Would you mind linking to the fastboot drivers just so at least I know I am using the right tools.

thanks again!
[Kindle Fire HDX 7" & 8.9" General] DB126:
Drivers were among the files in previously linked post. My preference is Moto drivers which can be obtained by simply installing Moto Manager (no need to launch). Either should work.

https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
[Kindle Fire HDX 7" & 8.9" General] droiduzr2:
Ok, maybe I am missing something not understanding something.

Can you simply tell me how to but into BULK mode.

thanks for the drivers, will try them now.

btw- I did install the drivers from the link.

fingers crossed, let's hope this works...

thanks!

---------- Post added at 07:38 PM ---------- Previous post was at 07:16 PM ----------

I reread this post....Yes I flashed the Thor files in MiFlash BUT I have since reflashed newer and proper TWRP which boots up into that.

I even flashed the reimage file from Draxie as it comes up with orange color TWRP.

That's what I do not understand is with new TWRP then touchscreen should be fixed unless Thor files flashed drivers for the touchscreen also.

Just as fyi...I flashed some files with Miflash and I got error (missing or improper file when I first tried with reimage files). It did not flash and finish in green...BUT when I rebooted and plugged back in I got about 6 drives showing up in Windows (asking to format them, I did not format).

I saw some folders and they had files in them. What if I was able to delete the folders from Windows...wold the system be blank then I can try MiFlash with proper files....just a thought...I could be way off, just asking.
[Kindle Fire HDX 7" & 8.9" General] DB126:
I really have no interest in veering into the weeds with MiFlash. That tool is not used with this device.

Erasing aboot followed by a reboot drops the device into 'bulk mode'. Screen will be blank and unresponsive; everything must be done via tether.

I seem to recall some difficulty with touch screen 'realignment' after flashing the wrong aboot and/or recovery. You mission, should choose to accept it, is to overwrite the existing aboot and recovery partition with known 'good' images for your device type using tools and methods outlined in linked posts. Which does not include MiFlash or deleting miscellaneous files/folders. That may fix the alignment problem and establish the foundation needed to unlock the bootloader and install a custom ROM (via TWRP - not MiFlash).
[Kindle Fire HDX 7" & 8.9" General] droiduzr2:
Ok got it. I will focus on trying to get fadstboot to work.

Just to be clear, I have a regular USB and a fastboot cable. I am guessing you did all of this with regular usb cable???

I can do adb devices - it will show up BUt if I type fastboot device(s) then nothing happens.

can you check your PM thanks

---------- Post added at 08:29 PM ---------- Previous post was at 08:17 PM ----------

I have a blank screen on Kindle.

It is in Qloader mode (shows up in MiFlash as Qualcom...with comport)

Is Qloader mode = Bulk mode????

I got this result

D:\Downloads\Firefox\kindle-tool-fw>fastboot boot aboot_vuln.mbn

< waiting for device >

*** If I use regular usb cable Windows will say does not recognize USB device...if I use fastboot cable then tablet shows up as Qualcom device.

That is when it is in the blank screen NO kindle logo showing. Actually when the tablet is off and you plug in the fastboot cable it goes into the Qboot mode but it does not do that with regular usb cable...just an observation.