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.
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 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.
Hi All，
I do believe here is the god place who will settle my problem~~ really need help.
my hdx7 is good and no any damages physically, but afte I tried many times for flashing CM13 and different root tools, finally the last time when I flash CM11 rom, the Startrap showing Sucessful, but when I click reboot device, my hdx7 there is no longer boot again, even there is a system already done.
now my hdx is bricked and also stuck by white Kindle Fire logo, I can use the combination key（vol+ and power） boot up Fire System Recovery, but only reboot and factory setting can be selected.
As described above, here is the key about my HDX7, if I want to apply any operations for my devices, this HDX7 cannot connect to computer no matter what kind of computer or different cable, all ADB, root tool, device manager.........there is no HDX7~~
tips: before last failed work I had 4 times flash CM11 system successed but the 4th time computer also cannot find device.
So god please help me~~ Thanks a lot
ydrz said:
Hi All，
I do believe here is the god place who will settle my problem~~ really need help.
my hdx7 is good and no any damages physically, but afte I tried many times for flashing CM13 and different root tools, finally the last time when I flash CM11 rom, the Startrap showing Sucessful, but when I click reboot device, my hdx7 there is no longer boot again, even there is a system already done.
now my hdx is bricked and also stuck by white Kindle Fire logo, I can use the combination key（vol+ and power） boot up Fire System Recovery, but only reboot and factory setting can be selected.
As described above, here is the key about my HDX7, if I want to apply any operations for my devices, this HDX7 cannot connect to computer no matter what kind of computer or different cable, all ADB, root tool, device manager.........there is no HDX7~~
tips: before last failed work I had 4 times flash CM11 system successed but the 4th time computer also cannot find device.
So god please help me~~ Thanks a lot
Click to expand...
Click to collapse
How were you trying to flash CM13? If you device does not have an unlocked bootloader (a CM13 prerequisite) there is no recovery. Given you are getting the factory recovery menu vs TWRP it sounds like Safestrap was installed.
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.
Hello my fire HD 6 is constantly looping at the fire logo and I don’t know what to do. I tried at fastboot mode but it gets stuck. Can anyone help me?
I had two devices with the same problem.
For the first device I did reset from recovery and it help.
For the second device the resetting did nothing and I tried
Code:
adb sideload
and has loaded *.bin file with firmware from my computer. After that, the second device also started working.