Hey guys i had my kindle fire hd 7 running cm13 and was running fine. i had alot of apps and data so decided to perform a factory reset within the rom, now i am stuck on the twrp screen which just blinks occasionally. i have tried connecting to a computer and using adb but it comes back my device isnt authorised and i cant authorise as i cannot boot. i have also tried some fastboot commands but it comes back (waiting for device) im guessing this is when the screen pops up for you to authorise adb but i get nothing. any help please or is this just done for.
any help geting this fixed will be appreciated thanks!!! :fingers-crossed:
UPDATE.
I managed to get into fastboot mode with a diy fastboot cable but fastboot still comes back (waiting for device) when I run the command "fastboot devices" it comes back with an empty list can someone please help I have tried uninstalling and reinstalling drivers but nothing . Please help anyone?
Related
I swear I looked far and wide but this appears to be different from the usual "bootloop" questions. Apologies if not.
I flashed a bad ROM, and the device won't boot all the way into the OS. Just sits at the ROM logo for hours.
I previously installed FFF 1.4, so I do get the blue KindleFire logo momentarily, but any fastboot commands I try to send to it just come back with "waiting for device" and then "ERROR: Unable to create a plug-in (e00002be)". I've got TWRP installed and backups galore but I cant figure out how to get to it. I do have a fastboot cable.
Totally at a loss as to what to do. I feel like there's a really simple fix I'm missing, but I've poured through pages of Kindle Fire posts and everyone seems to be having a problem with the KindleFire logo screen and pre-getting all the way to recovery and ROMS installed.
Any help would be much appreciated dudes, you guys always get me sorted out. Thanks!
It sounds like you need the fastboot drivers loaded. Does it appear in device manager when it is plugged in and in fastboot mode?
It comes up under Other Devices: Kindle
Well, now I've got it coming up under Kindle Fire: Android ADB Composite Device. But at no point, apparently does it enter fastboot mode and I can't get any commands to work. Just scoots right through both KindleFire logos and then on to the ROM logo ad infinitum.
Hey there, I hope someone can help me find a solution. I have tried KFFirstAide and KFHD System.img Restore Tool but I am having no luck. I do not have a factory cord yet, but I am not sure that I need one. I have ordered one anyway and it should be here by the end of the week.
The FireHD 7 responds to KFHD System.img Restore Tool and KFFA both with reboot into FastBoot and reboot into normal mode, but as soon as it reboots, it will sort of flash and then displays FastBoot Kindle Fire.
Prior to this happening, The HD7 was stock, never rooted. I had only connected it to my Vista64 computer to transfer books. I was reading a book, plugged in the charger (not original, but have used for a long time), turned the HD7 off, put the HD7 down and then noticed I noticed the display came on. It had FastBoot Kindle Fire on the display. I tried restarting, but kept going back to FastBoot. I have tried holding the power button down for over 1 minute and then turning it back on. I have tried everything I can find to "reset" the HD7 normally.
I have tried to restore it with KFHD System.img Restore Tool. I have tried to restore it with KFFirstAide. Sometimes I get an error message about daemon not running when I try to use KFFirstAide. I would love it if someone could teamview with me to get it working again. This is my first experience with trying to do anything with the Android OS.
HappyTNMom said:
Hey there, I hope someone can help me find a solution. I have tried KFFirstAide and KFHD System.img Restore Tool but I am having no luck. I do not have a factory cord yet, but I am not sure that I need one. I have ordered one anyway and it should be here by the end of the week.
The FireHD 7 responds to KFHD System.img Restore Tool and KFFA both with reboot into FastBoot and reboot into normal mode, but as soon as it reboots, it will sort of flash and then displays FastBoot Kindle Fire.
Prior to this happening, The HD7 was stock, never rooted. I had only connected it to my Vista64 computer to transfer books. I was reading a book, plugged in the charger (not original, but have used for a long time), turned the HD7 off, put the HD7 down and then noticed I noticed the display came on. It had FastBoot Kindle Fire on the display. I tried restarting, but kept going back to FastBoot. I have tried holding the power button down for over 1 minute and then turning it back on. I have tried everything I can find to "reset" the HD7 normally.
I have tried to restore it with KFHD System.img Restore Tool. I have tried to restore it with KFFirstAide. Sometimes I get an error message about daemon not running when I try to use KFFirstAide. I would love it if someone could teamview with me to get it working again. This is my first experience with trying to do anything with the Android OS.
Click to expand...
Click to collapse
If you are using Windows,you'll need the android SDK installed. Google it and set up adb and fastboot. Once they are working, the following command should reboot it into the os:
fastboot -i 9x1949 reboot
If it stays on waiting for device,driver problem. Use stunts513's drivers.
The best way would be to boot into a linux live session,install fastboot only and use the command. The command to install fastboot is:
sudo apt-get install android-tools-fastboot
Thank You
SafinWasi said:
If you are using Windows,you'll need the android SDK installed. Google it and set up adb and fastboot. Once they are working, the following command should reboot it into the os:
fastboot -i 9x1949 reboot
If it stays on waiting for device,driver problem. Use stunts513's drivers.
The best way would be to boot into a linux live session,install fastboot only and use the command. The command to install fastboot is:
sudo apt-get install android-tools-fastboot
Click to expand...
Click to collapse
I will try to do that later today. Thank you for the help. I will be back to let you know if I can get it to work or with questions.
Sorry Didn't work
HappyTNMom said:
I will try to do that later today. Thank you for the help. I will be back to let you know if I can get it to work or with questions.
Click to expand...
Click to collapse
ok, so I now have SKD and tried the command you gave me with no luck
I also tried SRT again and it looks like it is working on my cmd screen
I did step 1, step 3, step 4, step 6 and they all said they finished but it still reboots then goes straight to the FastBoot screen
Got my Factory Cable Today still stuck on fastboot
SafinWasi said:
If you are using Windows,you'll need the android SDK installed. Google it and set up adb and fastboot. Once they are working, the following command should reboot it into the os:
fastboot -i 9x1949 reboot
If it stays on waiting for device,driver problem. Use stunts513's drivers.
The best way would be to boot into a linux live session,install fastboot only and use the command. The command to install fastboot is:
sudo apt-get install android-tools-fastboot
Click to expand...
Click to collapse
ok I have tried using this new cable and running SRT with no luck. I am still stuck on FastBoot. It seems to work, but as soon as I do the Reboot to Normal, it goes to the Kindle Fire homescreen, then immediately goes back into FastBoot. I am going to keep trying and hopefully you or someone will see this and respond with more suggestions. Thanks for the help, much appreciated...
Thank you for all the help in advance!
Current state of device:
Fire HD 7" factory cable plugged in stuck on fastboot screen not loop just stuck no access to ADB (device not found[debian gnome])
I was deleting my previous ROM to go back to stock. I wiped my cache, os and everything then went to go and install the stock ROM and my little one managed to power the kindle down. I turned it back on to find kindlefire logo on the screen but it doesn't go past that. I built a factory cable and now it displays the fastboot logo but nothing else, not looping just frozen on the fastboot screen. So the computer [debian gnome] can't find the device when using ADB. (ADB is working with my other devices) I tried to follow a post about using the fastboot cmd to install the system.img, recovery.img and boot.img but did not know exactly what I was doing at that point. Is it done for? or is there hope?
Any help would be greatly appreciated!
There is hope. You could try following the commands in the batch file from this post.
http://forum.xda-developers.com/showthread.php?t=1951254
I've never tried it from Linux but so long as fastboot is working you should be able to flash the 3 images and then wipe data.
Thank you sooo much! this worked like a charm. I downloaded the img files and loaded them to the kindle via fastboot then rebooted and wala back to a fully functioning kindle. Thanks for the link!!!!
Glad to hear it helped you out.
Help me please
I have bricked my device. I can no longer get it past the bootloader Amazon image and can only get it into fastboot. Had root on device and was attempting to flash twrp so that i could install some custom roms. When flashing twrp the device restarted and has been stuck in a silver amazon bootloop. With the help of root junky's supertool i can get into factory recovery. but cannot sidload origional system back. I was gonna go back origional and re root. But can not get it out of bootloop. Tried using the system recovery thread found in second post on this thread and recieved an unsuccessful. Am i done for.... Kindle just stuck on fastboot screen now
Does your device have the front facing camera and the mini hdmi port?
Hi everyone.
I rooted my kindle. Put CM 13 in it. Had some problems with SuperSu - couldn`t install. Download zip update and installed it from TWRP. After rebooting all I can see is orange Kindle logo which keep rebooting constantly every 2-3 seconds. Can`t get into recovery. PC doesn`t recognize it because it`s kind of off. Installed ABD - still nothing. No devices in the list. Installed utility - nothing - status off. It seems like it`s not getting to the point to be considering on for adb to pick up anything.
Can you please advise.
Thank you.
Gospelalex said:
Hi everyone.
I rooted my kindle. Put CM 13 in it. Had some problems with SuperSu - couldn`t install. Download zip update and installed it from TWRP. After rebooting all I can see is orange Kindle logo which keep rebooting constantly every 2-3 seconds. Can`t get into recovery. PC doesn`t recognize it because it`s kind of off. Installed ABD - still nothing. No devices in the list. Installed utility - nothing - status off. It seems like it`s not getting to the point to be considering on for adb to pick up anything.
Can you please advise.
Thank you.
Click to expand...
Click to collapse
I did the EXACT same thing, so don't feel bad. You will need a fastboot cable. If you don't have one, you can find them on eBay, or there are instructions on this site on how to make one, but you'll need to buy a breakout board. Here's how @r3t3ch helped me once I got the fastboot (or factory) cable:
"The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs."
vasolini said:
I did the EXACT same thing, so don't feel bad. You will need a fastboot cable. If you don't have one, you can find them on eBay, or there are instructions on this site on how to make one, but you'll need to buy a breakout board. Here's how @r3t3ch helped me once I got the fastboot (or factory) cable:
"The command "fastboot -i 0x1949 getvar product" will wait until fastboot sees your device; using "fastboot -i 0x1949 devices" will also tell you if it sees anything, but exits immediately without waiting. If windows shows the device as "Tate" under unrecognized devices in device manager and you know fastboot is already installed, do right click>update driver>browse computer>let me pick>android composite interface. Since you know you soft bricked by flashing supersu, once you get the cable and fastboot mode working, you just have to extract the boot.img file from the cm13 zip and flash it using "fastboot -i 0x1949 flash boot boot.img" then "fastboot -i 0x1949 reboot oem recovery" then power cycle the device. I recommend waiting for the cable since making one is a PITA especially if your donor cable is cheap and doesn't have easy to access pin outs."
Click to expand...
Click to collapse
Thanks a lot for reply.
Just got my cable today. Tried as you`ve said. But nothing responded. In com "Waiting for device". Kindle keeps rebooting. Nothing unidentified in Device manager...
Gospelalex said:
Thanks a lot for reply.
Just got my cable today. Tried as you`ve said. But nothing responded. In com "Waiting for device". Kindle keeps rebooting. Nothing unidentified in Device manager...
Click to expand...
Click to collapse
Do you have the kindle drivers installed on your PC? If you get the Kindle to boot to fastboot mode, the PC should show it in the device manager. I'll see if I can find the link to the drivers that I used. They're somewhere on this site!
I think these are the adb drivers I used... http://forum.xda-developers.com/showthread.php?t=1890413
vasolini said:
Do you have the kindle drivers installed on your PC? If you get the Kindle to boot to fastboot mode, the PC should show it in the device manager. I'll see if I can find the link to the drivers that I used. They're somewhere on this site!
I think these are the adb drivers I used... http://forum.xda-developers.com/showthread.php?t=1890413
Click to expand...
Click to collapse
Can`t install them - install failed.
Gospelalex said:
Can`t install them - install failed.
Click to expand...
Click to collapse
Got another cable. Was able to get to fastboot. But couldn`t get past it. Device was shown as tate unrecognized. Pushed to install driver and made it recognized by pc. Tried kindle fire utility v099 to run recovery. The kindle gone into reboot. So now it reboots into main loge, then changes into fastboot loge and then going into continuous reboot again. Windows in the same time stop recognize it. Shows it in usb unidentified for a second because it switches on and off again.
Update:
Managed to return it into fastboot. But in cmd when i run adb.exe devices there is nothing.
I know how to fix this problem. I ran into this 10 times before Android Studio suddenly went through my head.
In order to install the Kindle Fire ADB Drivers, you need to download and install the Android SDK Manager from Google Inc. Then when you install those drivers I mentioned earlier, you won't get errors. It's so weird.
You can try using the Ultimate Unbrick Tool, but I forgot the download link for it. There should be a thread about it here on XDA.
Lots of advanced technical stuff. I suck at explaining without making it a very long explanation because then people stop reading after 10 seconds.
SO I foolishly issued the fastboot command via ADB when it was working. I started to issue commands in order to install the 2nd bootloader and recovery. Since that point, the Kindle isn't recognized by Windows 10 Pro anymore and I've tried just about every utility, method and button combination there is.
I read that ADB only needs 4 seconds -/+ to initiate commands once the Kindle powers up. I've tried to issue the ADB to get it to boot back in normal mode and it always sits on <waiting for device>. I attached a screen shot showing what comes up in device manager. I've uninstalled the drivers, reinstalled but to no avail.
At this point, I'm willing to try anything. Stand on my head and shake the Kindle 5 times while rotating it clockwise....anything would help.
*UPDATE* I just more or less wiped my laptop which I have all the ADB drivers on as well as Android Studio. I'm going to run some tests to see if I can get that 4 second gap to initiate an ADB command to get the fastboot to go into normal boot more 4000.
*UPDATE 2* I managed to get generic ADB drivers as well as FASTBOOT drivers installed on my laptop. I can communicate with the Kindle a little. At this point, I've tried to issue ADB commands to restart with bootloader and other commands, but it only reboots back into FASTBOOT. The only thing I've been able to see is with KFFA, I can reboot to normal mode but it just comes back to FASTBOOT. I can also issue the test FASTBOOT and it gives me an ID and recognizes the Kindle. I've tried other options within KFFA but nothing seems to stick. I'm now officially stuck. Any help would be fantastic.
*UPDATE 3*
Thanks to this thread http://forum.xda-developers.com/kin...ment/unlock-kfsowi-bootloader-unlock-t3262770
I was able, or am in the process of loading a 2nd bootloader + TWRP and then on to CM13.
Any ideas?
Windows 10 Pro
Kindle Fire HD
Rooted with Kingroot
No Fastboot cable
Lots of frustration
Eh back to square one. It reverted and there is no TWRP recovery. It's stuck in FASTBOOT and will take most fastboot commands but I can't get ADB and the drivers loaded to issue any sideload commands.
This is weird.
Hello I have bricked my kindle fire and having similar driver issues I am able to get into fastboot mode with a diy factory cable boot any fastboot command comes back waiting for device . Can I ask where you got drivers please?
I used these:
http://forum.xda-developers.com/showthread.php?t=1890413
I also ran like every single recovery tool out there to help me fix this. After I did fix it, it updated to latest version and there is no root yet for it. I sold it.
If you need help, I think I might still have all the tools I used to get this back to stock and working.
Regards,
rast4man