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.
I am hoping that someone can help point me in the right direction. I've spent many hours on this forum trying various solutions and nothing seems to work. I have a Kindle Fire HD 8.9 (JEM-PVT-Prod-04). A year or so ago it was rooted and CyanogenMod 11 was installed. At some point a member of my family attempted a factory rest and the device ended up in the looping recovery screen (Teamwin flashing every 3 seconds). I resolved that issue and I am now able to successfully boot into twerp. However, whenever I attempt to push a new install to the SD card I received the unauthorized device error.
Fastboot commands seem to work and I was able to flash new bootloader, recovery, and bootloader files to the device, which is how I resolved the recovery boot loop. After initially resolving the bootloop issue ADB did not see the device. Reinstalling the drivers resolved that issue.
I'm unable to access the OS to enable USB debugging so I'm hoping there is another way.
Any help/guidance is greatly appreciated.
I think my 4th Gen Kindle Fire is bricked hard. I had rooted a while back and was running fine till one day it stayed stuck on the Fire logo during boot. I can get into recovery but when I try to sideload stock rom with adb I either get a message that says "Rom not compatible" or it transfers 0kb and nothing happens. I tried factory data reset but that doesn't work. I even tried the methods from here - http://forum.xda-developers.com/fire-hd/development/video-linux-iso-unbrick-fire-hd6-hd7-t3474999 using the Archlinux boot CD with AFT2 Tools, but when I issue the ./reader.sh command, it just hangs.
Are there any options for me?
nai1ed said:
I think my 4th Gen Kindle Fire is bricked hard. I had rooted a while back and was running fine till one day it stayed stuck on the Fire logo during boot. I can get into recovery but when I try to sideload stock rom with adb I either get a message that says "Rom not compatible" or it transfers 0kb and nothing happens. I tried factory data reset but that doesn't work. I even tried the methods from here - http://forum.xda-developers.com/fire-hd/development/video-linux-iso-unbrick-fire-hd6-hd7-t3474999 using the Archlinux boot CD with AFT2 Tools, but when I issue the ./reader.sh command, it just hangs.
Are there any options for me?
Click to expand...
Click to collapse
Also wanted to mention that I get Failed to mount /cache in the recovery screen. Is there anyway to fix this?
I have the exact same issue. Any help?
You ever got that issue fixed. I'm facing the same problem
I had such problems, when i had flashed twrp to cm recovery.
The only way to fix this in my case was to use fastboot flash.
And i managed to copy the rom through adb commands (if i remember right)
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.