Hi all. This is my first post and I want to thank all the devs for the great job.
As for my question. I have a kindle fire 7" HDX Model X43Z60 that was stuck in a boot loop. We ordered a factory cable and was able to get it into fastboot, I also was able to install the drivers properly. It comes up as android adb interface. No errors or yellow signs.
adb and fastboot are not seeing the device when I try to list them. I've tried uninstalling and reinstalling the drivers. Reboots. I'm not sure what else to do here after much fiddling around with it. I can't get nothing to work even though the kindle is showing up in device manager and showing no conflicts.
I would like to at least get this kindle to factory reset.
Any information you can give me would be very much appreciated.
AShadowedWizard said:
As for my question. I have a kindle fire 7" HDX Model X43Z60 that was stuck in a boot loop. We ordered a factory cable and was able to get it into fastboot
Click to expand...
Click to collapse
You have Kindle Fire HD, not HDX. So I think you better ask in proper section.:good:
Related
Hi guys, had everything working swimmingly after getting a replacement HDX from Amazon (due to screen flicker) and the replacement came with Rootable software! yay!
Anyway, even though I was running on Rom Slot 1 and not the Stock Rom, when I used the Wipe function it wiped everything - stock and slot... I hadn't created a recovery of Stock Rom (yes, I didn't RTFM... but I imagined I could ADB push the amazon update file and go from there... ADB was too intermittent to do this and when the HDX booted again I stupidly accepted the Kindle Fire System Recovery and tried to "recover" when there was nothing there...
So now I have the silver Kindle Fire logo... I do get MTP USB Device showing up on my PC (but can't get ADB to connect etc) and can also boot into Kindle Fire System Recovery (but the device doesn't then get detected on the PC)...
Any thoughts???
Any update on this? I am wondering if you got it working or not.
i did the same thing :crying::crying:
kudoz83 said:
Hi guys, had everything working swimmingly after getting a replacement HDX from Amazon (due to screen flicker) and the replacement came with Rootable software! yay!
Anyway, even though I was running on Rom Slot 1 and not the Stock Rom, when I used the Wipe function it wiped everything - stock and slot... I hadn't created a recovery of Stock Rom (yes, I didn't RTFM... but I imagined I could ADB push the amazon update file and go from there... ADB was too intermittent to do this and when the HDX booted again I stupidly accepted the Kindle Fire System Recovery and tried to "recover" when there was nothing there...
So now I have the silver Kindle Fire logo... I do get MTP USB Device showing up on my PC (but can't get ADB to connect etc) and can also boot into Kindle Fire System Recovery (but the device doesn't then get detected on the PC)...
Any thoughts???
Click to expand...
Click to collapse
No it won't wipe the stock slot. What you did was wiped the working rom slot & then rebooted into it, where no OS is, because, well, because you had just wiped it. Try Unbuntu for adb access. You *MAY be able to set it to boot to stock, or push the system files to it via adb, but I am not in a position to recreate this issue.
Hello I'm looking help with my kindlefire 8.9 hd. I attempted to root and install twrp on my tablet and then rebooted. I know am only seein the tablet boot up and then power off and boot up again. Only thing showing on the screen is the kindlefire logo. When it's connected to my windows pc I hear chimes for when it powers on and then down again.
I have attempted to run the setup script again on my desktop and the fastboot getvar devices command. When I do this It just says waiting for device. Again it keeps rebooting itself so it isn't really up in a state that would allow it to be viewable/usable from the pc. Basicly it powers off/reboots before I'm able to do much with it.
I'm not really sure what to try next or if there are any options at this point.
I was following this tutorial to root/install android on my kindlefire 8.9 hd.
Well I'm unable to post with a url in it until I the 10 post requirement. Any help would be greatly appreciated.
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.
I was restoring to factory settings through Cyanegon 13 and now it's been on a boot loop at the TWRP screen. I've done extensive google searches and a lot of the "solutions" require for my PC to recognize the Kindle when connected but it doesn't. Weird thing is though I go to device managers and it "recognizes" it there but not when I use command prompt etc. IS THERE ANY SOLUTION WITHOUT ME HAVING TO BUY A ****ING FACTORY/FASTBOOT CABLE?!
P.S. don't give me solutions that imply me having to use TWRP home screen because, again, boot loops at the "teamwin" part
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.