My HDX 7 64GB is stuck in a boot loop after 4.5.5.3 update (I did not believe amazon would offer another update so i did not block OTA updates). It was fully Stock except for King root.
Now after the first boot loop it boots always the Fire System Recovery.
Is there any possibility to fix this?
MxUltra said:
My HDX 7 64GB is stuck in a boot loop after 4.5.5.3 update (I did not believe amazon would offer another update so i did not block OTA updates). It was fully Stock except for King root.
Now after the first boot loop it boots always the Fire System Recovery.
Is there any possibility to fix this?
Click to expand...
Click to collapse
Not likely short of placing the device in 'bulk' mode and taking a series of rather technical steps to erase and then rebuild your device. Entering bulk mode may be tricky if it is unstable during boot.
How would I place my HDX 7 into 'bulk' mode?
MxUltra said:
How would I place my HDX 7 into 'bulk' mode?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Ok. I tried to get my HDX 7 into bulk mode, by using a fastboot cable. But it only enters 9008 QDL mode, how do I get from there to the buk mode?
As I tired different things. My HDX 7 is now stuck with the grey kindle fire screen, but I can see the device in adb. The problem is that I can not execute any command, because it is shown as unauthorized. Is there a way to still boot fastboot?
MxUltra said:
Ok. I tried to get my HDX 7 into bulk mode, by using a fastboot cable. But it only enters 9008 QDL mode, how do I get from there to the buk mode?
Click to expand...
Click to collapse
MxUltra said:
As I tired different things. My HDX 7 is now stuck with the grey kindle fire screen, but I can see the device in adb. The problem is that I can not execute any command, because it is shown as unauthorized. Is there a way to still boot fastboot?
Click to expand...
Click to collapse
A fastboot (aka 'factory') cable is ineffective on this device. Being stuck at the bootloader logo with no connectivity is generally fatal. Details matter; how did the device and up in this state?
@draxie - thoughts?
I wanted to unlock the bootloader and rooted it via Kingroot, but had no time that day to get further. Some days later I discovered the HDX 7 was booted to the stock recovery.
I tried to reboot it, but it always tries to boot the rom and start over and boots the stock recovery.
Then I called amazon, and they told me that my HDX tried to update to 4.5.5.3 and that they can not help me.
Then I tried the factory reset, but it did not help either.
Through experimentation I noticed that if the tablet booted while connected to my linux notebook, it would sometimes stop at the grey kindle fire logo and offer a adb connection, that I sadly could not use because i don't have the necessary ADB_VENDOR_KEYS.
MxUltra said:
I wanted to unlock the bootloader and rooted it via Kingroot, but had no time that day to get further. Some days later I discovered the HDX 7 was booted to the stock recovery.
I tried to reboot it, but it always tries to boot the rom and start over and boots the stock recovery.
Then I called amazon, and they told me that my HDX tried to update to 4.5.5.3 and that they can not help me.
Then I tried the factory reset, but it did not help either.
Through experimentation I noticed that if the tablet booted while connected to my linux notebook, it would sometimes stop at the grey kindle fire logo and offer a adb connection, that I sadly could not use because i don't have the necessary ADB_VENDOR_KEYS.
Click to expand...
Click to collapse
I am not aware of any method to reliably force a device into 'bulk' mode via button pushes, etc. The member referenced in a previous post has the most experience in this area; see if he responds.
FWIW - accepting a FireOS 4.x OTA update on a rooted HDX device is almost always fatal.
Hopeless...
Davey126 said:
A fastboot (aka 'factory') cable is ineffective on this device. Being stuck at the bootloader logo with no connectivity is generally fatal. Details matter; how did the device and up in this state?
@draxie - thoughts?
Click to expand...
Click to collapse
Condolences, perhaps...
If the bootloader is unlocked, Power+VolDn won't enter fastboot
(although that doesn't hurt trying), and I don't know of any exploits
that would get adb executing commands on an unauthorized device.
(Of course, trying "adb reboot bootloader" won't do any harm, either.)
If adb used to work before, there _could_ be an absolutely minuscule
chance that whatever host was used still has adb keys in the .android
folder of the relevant user account's home directory, but given that factory
reset was performed, the corresponding public key(s) on the device are
probably gone... Still, if there are keys in .android (and, especially, if there
are different versions on different hosts and/or under different user accounts),
then testing them all may be worth a try. Just in case...
The steps involved are
Stop the current instance
Code:
adb kill-server
Copy the keys to try to .android
(on the test host in the test user's home directory)
See if "adb" manages to connect:
Code:
adb shell
(This needs to be run as the "test" user.)
And, the above steps should be repeated for each set of keys....
I would NOT hold my breath, but one might get lucky.
Related
Hello
I got my HDX rolled back today, rooted it using Towelroot, all worked fine
Installed FLASHR and there was an image I had for TWRP, I tried mounting it as recovery but failed, then there was a Kernel option which I did install it with (The same TWRP Image), when the device rebooted it was stuck in Grey Kindle Fire screen,
I read around for methods and found some, the problem is that my device is not seen by ADB and when connected to USB there is no response.
Can this device be unbricked? Do I need the fastboot cable?
I also have taken a backup using FLASHR and it stayed on the device, is this useful?
Thanks for your time
TWRP is not compatible with 3.2.8. Try powering up by holding the on/off and volume-up buttons together. It's possible Amazon's (crippled) recovery is still intact. From there you may be able to reset your device. If successful read through the forums to determine what is possible. Options with 3.2.8 are limited.
Davey126 said:
TWRP is not compatible with 3.2.8. Try powering up by holding the on/off and volume-up buttons together. It's possible Amazon's (crippled) recovery is still intact. From there you may be able to reset your device. If successful read through the forums to determine what is possible. Options with 3.2.8 are limited.
Click to expand...
Click to collapse
Thanks for your reply, I did try power + volume up still got the grey Kindle Fire logo, I did read a lot in this forum but didn't succeed in finding a good solution
I got the factory Cable
The device was recognised as USB, a black screen was showing.
I tried ADB it said device not found
also fastboot -i 0x1949 etc keeps waiting for a device
any hint? is the device dead?
mrewen said:
Hello
I got my HDX rolled back today, rooted it using Towelroot, all worked fine
Installed FLASHR and there was an image I had for TWRP, I tried mounting it as recovery but failed, then there was a Kernel option which I did install it with (The same TWRP Image), when the device rebooted it was stuck in Grey Kindle Fire screen,
I read around for methods and found some, the problem is that my device is not seen by ADB and when connected to USB there is no response.
Can this device be unbricked? Do I need the fastboot cable?
Click to expand...
Click to collapse
No, this device is bricked for good assuming that your device was on FW xx.3.2.8:
- you writed incompatible twrp image on recovery and also on boot partition, the second flash was deadly
The only option for custom rom for FW xx.3.2.8 is to use safestrap and nexus for safestrap 1.0.1.
Hello fellows!
I'm afraid, I bricked my kindle.
I wanted to check out the permissions for /app using ES-File Explorer. My screen went instantly black and stuck. I didn't change anything, I just clicked on "details". I killed the device (holding down power button) and afterwards it doesn't boot. The kindle logo stays gray and it reboots 1 time. This reboot ends in the Fire System Recovery, where I can reboot the device or do a factory reset.
Factory reset didn't help.
I have one problem fixing the device:
- The device is only recognized as MTP-Device while it tries to boot the first time. And this is not very long. It isn't named Kindle, but Android in "Devices and Printers". Unfortunately I can't uninstall or "update" the driver, while the kindle tries to boot.
---> ADB tells me: "error: device '(null)' not found" .
Do you have any idea how to save my kindle?
What I wanted to do before killing the device:
- Get the kindle to show Wallpapers (Totally worth to brick the device! -.-)
EDIT: I tried a second Factory Reset. Now it is fully stuck at the grey boot logo. But my system detects the kindle now correctly.
Next problem: adb shell command end in: "- exec '/system/bin/sh' failed: Permission denied (13) -"
EDIT EDIT: Getting the kindle into real bootloop is not always possible. It happened once and now I'm stuck in the System Recovery again and can't connect to the device :/
You might have to reroot the tablet. I think you can do it with ADB, or HDX toolkit might work. Or maybe you don't have to root at all, I recommend to reinstall ADB.
GodsMistake said:
Hello fellows!
I'm afraid, I bricked my kindle.
I wanted to check out the permissions for /app using ES-File Explorer. My screen went instantly black and stuck. I didn't change anything, I just clicked on "details". I killed the device (holding down power button) and afterwards it doesn't boot. The kindle logo stays gray and it reboots 1 time. This reboot ends in the Fire System Recovery, where I can reboot the device or do a factory reset.
Factory reset didn't help.
I have one problem fixing the device:
- The device is only recognized as MTP-Device while it tries to boot the first time. And this is not very long. It isn't named Kindle, but Android in "Devices and Printers". Unfortunately I can't uninstall or "update" the driver, while the kindle tries to boot.
---> ADB tells me: "error: device '(null)' not found" .
Do you have any idea how to save my kindle?
What I wanted to do before killing the device:
- Get the kindle to show Wallpapers (Totally worth to brick the device! -.-)
EDIT: I tried a second Factory Reset. Now it is fully stuck at the grey boot logo. But my system detects the kindle now correctly.
Next problem: adb shell command end in: "- exec '/system/bin/sh' failed: Permission denied (13) -"
EDIT EDIT: Getting the kindle into real bootloop is not always possible. It happened once and now I'm stuck in the System Recovery again and can't connect to the device :/
Click to expand...
Click to collapse
You didn't indicate if your device was rooted (assume yes), Safestrap installed, FireOS version, etc. But in the end it really doesn't matter. With a locked bootloader there is nothing you can do to recover from this type of failure. Even if the device is detected you will not have adb access. Nor will fastboot commands work (most are disabled). Native factory reset only clears the data partition; it does NOT fix errors in the system partition. If still under warranty contact Amazon about a replacement.
Davey126 said:
[/HIDE]
You didn't indicate if your device was rooted (assume yes), Safestrap installed, FireOS version, etc. But in the end it really doesn't matter. With a locked bootloader there is nothing you can do to recover from this type of failure. Even if the device is detected you will not have adb access. Nor will fastboot commands work (most are disabled). Native factory reset only clears the data partition; it does NOT fix errors in the system partition. If still under warranty contact Amazon about a replacement.
Click to expand...
Click to collapse
It was/is rooted.
So even a Fastboot cable won't work?
GodsMistake said:
It was/is rooted.
So even a Fastboot cable won't work?
Click to expand...
Click to collapse
Fastboot cables are useless on a HDX as 1) device interface does not support alternative pinout; and 2) fastboot environment is crippled.
Davey126 said:
Fastboot cables are useless on a HDX as 1) device interface does not support alternative pinout; and 2) fastboot environment is crippled.
Click to expand...
Click to collapse
Oh man! **** Amazons Bootloader!
I called them and they told me, that there are no Tablets to replace mine. They'd give me a kindle 8.9 for 303€ and that's all.
Thank you for answering. I'm going to throw my kindle away
GodsMistake said:
Oh man! **** Amazons Bootloader!
I called them and they told me, that there are no Tablets to replace mine. They'd give me a kindle 8.9 for 303€ and that's all.
Thank you for answering. I'm going to throw my kindle away
Click to expand...
Click to collapse
Well, I wouldn't toss it just yet. Stick it on a shelf and move on. Possible (albeit unlikely) a future unbrick method or bootloader exploit will become available.
Davey126 said:
Well, I wouldn't toss it just yet. Stick it on a shelf and move on. Possible (albeit unlikely) a future unbrick method or bootloader exploit will become available.
Click to expand...
Click to collapse
I hope so. Someone said they found how to get direct eMMC access.
After upgrading to CM 12.1 everything was just fine. Got my tablet to charger and left it there for a while. And then i saw that i was looping.
It's trying to enter recovery (TWRM) "or something like" and restarting.
I' sitting on forum for 3 days already. trying to get some information and did lot's of things. Nothing helps.
Can anyone help me with this somehow? I'm almost crying and losing it (not really, but that what i feel inside)
Please. Any help. I think I've read all forum about this thing.
Thank you.
Do you have the real TWRP (i.e. not Safestrap!) & an unlocked bootloader?
don't think so. or better say i'm not sure about it. how can i check?
Edit:
i can run adb and after command "adb devices" it shows serial number and status: recovery.
i can use the command adb reboot-bootloader which puts me in fastboot mode. but then i try adb devices and have nothing there.
also, any command like "fastboot...." gets me to "waiting for device" and nothing more.
I tried two different computers. all ports. all cables that i've found.
Edit 2:
also after command "adb shell" i ca see "~ # ←[6n" and i can put there only reboot command
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Cl4ncy said:
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Click to expand...
Click to collapse
Also verify you have a Kindle HDX ... not HD or generic Fire.
the fastboot command got me still only 1 message "waiting for device"
Tried to install drivers. While looping, in device manager, i can see "Fire devices: Android composite ADB Interface"
and "Portable devices: MTP USB Device"
If i enter fastboot mode, gets me to "Other devices: Unknown device" and i just cant figure out how to install the drivers. Tried to download some stuff. plugged, unplugged.
Edit:
After some work done with drivers, i input adb kill-server and adb devices and get "Serial Number Unauthorized"
So maybe i should change word "work" to "messing" with driver
what do i do from here... is there any live chat for it maybe? or i can call someone?
Well, do you have the real TWRP or Safestrap? Can you enter recovery?
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Still haven't answered Safestrap or native TWRP query (you should know). Do this:
- long press power until device shuts off
- restart device with power button (only)
- detail the 1st, 2nd and 3rd screens you see
If you do not have native TWRP (with unlocked bootloader) you likely borked your device with the installation of CM 12.1. Generally not repairable.
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Cl4ncy said:
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Click to expand...
Click to collapse
To check if your bootloader is unlocked (assumes you previously unlocked and still have the prerequisite software installed on host):
- power down device
- press vol-down + power; release both keys when "[fastboot]" prompt appears
- tether your device
- open a command prompt (assuming Windows)
- issue command: fastboot -i 0x1949 oem idme ?
- you will only get a response if bootloader is unlocked
If the (Windows) host displays "<waiting for device>":
- press <ctrl>-c to break wait
- start device manager (different window)
- located device with explanation mark (likely under "portable devices")
- right click -> update driver software -> browse my computer... -> Let me pick...
- select driver from list (ideally one that contains the words 'fastboot'); might have to try a few
- reissue above command
Bit of a PiTA ... might be easier to simply try the one click unlock tool as there is no additional risk to your device. It will either work or not.
I guess i'll check it only next week. Leaving all this things for the weekend.
I'll keep you updated guys.
Anyway, i really appreciate your help! Thank you so much for helping
same problem
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
stephio said:
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
Click to expand...
Click to collapse
I assume you have an unlocked bootloader and were running 'native' twrp (not Safestrap) when the problem occured. Unfortunately, there is no known 'quick fix' recovery from this failure scenario (boot looping on teamwin spash screen) as you have tried to reinstall twrp without success. Someone very talented with android might be able to unravel the problem. Best guess (and it is only a guess) is the recovery partition became damaged to such an extent it the contents can not be replaced without performing a low level format/reset of your device.
Some curiosities:
- Android 5.0.1 and CM11? (impossible combination)
- TWRP freedom? (not supported on HDX)
Are your certain your device is a HDX and not some other model?
same problem
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
stephio said:
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
Click to expand...
Click to collapse
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
same problem
EncryptedCurse said:
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
Click to expand...
Click to collapse
I searched the web and I have definitely amazon kindle fire HD 8.9 because even his appearance differs from the HDX 8.9.
no I do not really think the problem comes from the data flash HD 8.9 (wikicyanogenmod) because I flashed the data after doing a factory reset without actually knowing that this would pose a problem with amazon tablets.
the tablet was working well but I was unable to connect to the wifi. I thought it would be nice to change rom and install a suitable and stable rom for my tablet, but my operation I was surprised because I had never heard of this kind of problems caused by an factory reset
Hi there,
Can't find solution for my problem.
I have installed twrp. Then tried to click unlock.bat and tablet get in fastboot mode. From where i can't recover tablet.
While fastboot i see there is no driver in device manager as shown in attachment.
I can get in twrp with power + volume up.
But can't do something else.
What is solution to recover from this situation?
arshileus said:
Hi there,
Can't find solution for my problem.
I have installed twrp. Then tried to click unlock.bat and tablet get in fastboot mode. From where i can't recover tablet.
While fastboot i see there is no driver in device manager as shown in attachment.
I can get in twrp with power + volume up.
But can't do something else.
What is solution to recover from this situation?
Click to expand...
Click to collapse
- on Windows machine install Motorola Device Manager from here; you do NOT need to launch the device manager once installed
- from TWRP boot into fastboot via Reboot -> Bootloader; the word 'Fastboot' should be displayed on HDX
- on Windows change device driver to "Mot Composite"; the word 'Ready' should appear on the HDX
- turn off tablet (long press power button) then reboot to TWRP
- attempt to run unlock.bat
Davey126 said:
- on Windows machine install Motorola Device Manager from here; you do NOT need to launch the device manager once installed
- from TWRP boot into fastboot via Reboot -> Bootloader; the word 'Fastboot' should be displayed on HDX
- on Windows change device driver to "Mot Composite"; the word 'Ready' should appear on the HDX
- turn off tablet (long press power button) then reboot to TWRP
- attempt to run unlock.bat
Click to expand...
Click to collapse
I have tried these steps but no luck with Mot Composite. I just get an error that it FAILED.
I have TWRP Recovery 3.1 installed and I attempted to manually unlock the boot loader but that didn't work out. I want to try the 1-Click which I just got but heres the problem. When I turn on the kindle it goes directly to Kindle Fire [fastboot]. or if I hold down Power and Vol+ I can get to TWRP. What should I do? My ultimate goal is to unlock bootloader. Thank you for any assistance!
tekiro7 said:
I have tried these steps but no luck with Mot Composite. I just get an error that it FAILED.
I have TWRP Recovery 3.1 installed and I attempted to manually unlock the boot loader but that didn't work out. I want to try the 1-Click which I just got but heres the problem. When I turn on the kindle it goes directly to Kindle Fire [fastboot]. or if I hold down Power and Vol+ I can get to TWRP. What should I do? My ultimate goal is to unlock bootloader. Thank you for any assistance!
Click to expand...
Click to collapse
You're pretty much screwed without a ROM or tethered connection. If you can get adb working in TWRP then there's some hope. That should be your focus.
Davey126 said:
You're pretty much screwed without a ROM or tethered connection. If you can get adb working in TWRP then there's some hope. That should be your focus.
Click to expand...
Click to collapse
I downloaded the stock 4.5.5 ROM from another post. After that I booted into TWRP and opened the sideload ADB option. Then I plugged in the kindle and ran the write code to load it. Success! . I have it working again! I will try draxies One-Click-program next. Thanks!
Is it possible to brick the Kindle Fire HDX 7 Thor with "adb reboot bootloader"?
I put the command in and my tablet shut off and hasn't powered on since.
The Amazon version was very early, near it's release. I didn't update as suggested.
The battery was at 5% but I figured since I was keeping it plugged in and charging it'd be okay.
Is my HDX bricked?
zXiC said:
Is it possible to brick the Kindle Fire HDX 7 Thor with "adb reboot bootloader"?
I put the command in and my tablet shut off and hasn't powered on since.
The Amazon version was very early, near it's release. I didn't update as suggested.
The battery was at 5% but I figured since I was keeping it plugged in and charging it'd be okay.
Is my HDX bricked?
Click to expand...
Click to collapse
That command in isolation is completely benign. What happened just prior is the outcome determiner. Did you attempt to replace the bootloader, downgrade FireOS or install a custom recovery? Any of those actions done wrong will trash the device.
If none of these apply plug the device until fully charged (75+%). Unplug and long press power (10-30 sec) looking/listening for any signs of life. Repeat a few times for certainty. If no joy tether the device to the previously used host and repeat procedure. If nothing the device is not recoverable using any reasonable means.
Davey126 said:
That command in isolation is completely benign. What happened just prior is the outcome determiner. Did you attempt to replace the bootloader, downgrade FireOS or install a custom recovery? Any of those actions done wrong will trash the device.
If none of these apply plug the device until fully charged (75+%). Unplug and long press power (10-30 sec) looking/listening for any signs of life. Repeat a few times for certainty. If no joy tether the device to the previously used host and repeat procedure. If nothing the device is not recoverable using any reasonable means.
Click to expand...
Click to collapse
I was following steps from: https://forum.xda-developers.com/ki...r-firmware-t3463982/post75284993#post75284993
1. Install the adb-setup-1.4.3 into a folder (for example: C:/adb), extract dd-0.5.zip + unlock.zip + aboot-xxx.zip, put dd.exe + get_code.bat + unlock.bat + twrp image (for your device) + aboot_vuln.mbn (for your device) into that folder. After that install the kindle_fire_usb_driver.
2. Turn on ADB-Debuging Mode in Developer Mod by tapping 7 times the build numbers in settings and connect to your computer + trust your device.
3. Excecute "get_code.bat" in the folder above, you will get a new file: unlock.code in the folder.
4. Open CMD in the folder and run "adb reboot bootloader", the Kindle will reboot to bootloader with "[ fastboot ]" on the display
At step 4 I did the command and the tablet rebooted into a black screen and that was it.
I had already gone through the process once with a prior Kindle Fire HDX 7 tablet so I figured the same process would work out.
Unfortunately I believe the only difference is the firmware version on this HDX 7 being a lot earlier, 2014 build or something. That's about the only thing I can figure.
zXiC said:
I was following steps from: https://forum.xda-developers.com/ki...r-firmware-t3463982/post75284993#post75284993
1. Install the adb-setup-1.4.3 into a folder (for example: C:/adb), extract dd-0.5.zip + unlock.zip + aboot-xxx.zip, put dd.exe + get_code.bat + unlock.bat + twrp image (for your device) + aboot_vuln.mbn (for your device) into that folder. After that install the kindle_fire_usb_driver.
2. Turn on ADB-Debuging Mode in Developer Mod by tapping 7 times the build numbers in settings and connect to your computer + trust your device.
3. Excecute "get_code.bat" in the folder above, you will get a new file: unlock.code in the folder.
4. Open CMD in the folder and run "adb reboot bootloader", the Kindle will reboot to bootloader with "[ fastboot ]" on the display
At step 4 I did the command and the tablet rebooted into a black screen and that was it.
I had already gone through the process once with a prior Kindle Fire HDX 7 tablet so I figured the same process would work out.
Unfortunately I believe the only difference is the firmware version on this HDX 7 being a lot earlier, 2014 build or something. That's about the only thing I can figure.
Click to expand...
Click to collapse
Nothing in those first four steps could trigger the behavior you describe. The mystical "get_code.bat" in step #3 simply executes a series of queries and then writes out an intermediate work file named "unlock.code". Things get a whole lot more dangerous starting with step #6. Regardless, the age of the existing firmware is irrelevant to the entire unlock process provided you are working with a 3rd (not 4th) gen HDX and utilize the files appropriate for your device type (Thor/7" or Apollo/8.9").
I realize the above does not align with your recent experience. Suppose it is possible the device experienced a spontaneous hardware failure assuming nothing was done prior to the four steps noted.
Davey126 said:
Nothing in those first four steps could trigger the behavior you describe. The mystical "get_code.bat" in step #3 simply executes a series of queries and then writes out an intermediate work file named "unlock.code". Things get a whole lot more dangerous starting with step #6. Regardless, the age of the existing firmware is irrelevant to the entire unlock process provided you are working with a 3rd (not 4th) gen HDX and utilize the files appropriate for your device type (Thor/7" or Apollo/8.9").
I realize the above does not align with your recent experience. Suppose it is possible the device experienced a spontaneous hardware failure assuming nothing was done prior to the four steps noted.
Click to expand...
Click to collapse
Is there anything I can do?
It honestly feels so stupid to brick 2/3 Fire HDXs.
zXiC said:
Is there anything I can do?
It honestly feels so stupid to brick 2/3 Fire HDXs.
Click to expand...
Click to collapse
Nothing beyond steps previously listed. Sorry for your loss(es).
Curious - what type of host computer were you using? Any chance the HDX was connected to USB 3.1 port? Some are capable of much higher output than older USB standards and don't regulate voltage well. Anything significantly over 5V can (and will) damage older devices.