Related
I seriously need some help. My normally fierce Google-fu has failed me. I have searched countless threads on here (and elsewhere) and tried just as many solutions, but I haven't had any luck. My Kindle Fire is stuck at the "Kindle Fire" boot logo. I was using the KF utility, and ADB status was online, everything looked good. I chose the option to root and install TWRP. However, it couldn't grab TWRP through my corporate firewall/proxy, so it skipped it, placed my KF in fastboot (I think), rebooted, now I'm bricked.
Depending on which PC I use, and in what order it's plugged in, I get different results in the Device Manager (both Windows 7):
Home PC -
Hardware Ids = USB\UNKNOWN
Yes, I've tried loading drivers six ways from Sunday, and none worked.
Absolutely no solution involving ADB in any way will work until I can at least get Windows to recognize it correctly and load the proper drivers.
Work PC -
If I have the KF turned on when I plug it into my PC, I get the same result as on my home PC (though I don't think I tried plugging it in on my home PC while my KF was powered off).
If I have it turned off when I plug it in, my PC sees it as an "Android ADB Interface", with the correct hardware ids.
Even when it sees my KF correctly in Device Manager, I still can't get ADB to communicate with it.
I've tried FireKit on my Ubunutu 12.04 laptop, but it never sees my device, and gets stuck at the <waiting for device> message. I've tried countless driver iterations and many utilities, and none seem able to communicate with it while it's stuck at the logo.
Any help would be immeasurably appreciated!!
[UPDATE]
While my device was detected correctly in Device Manager (but still not able to communicate via ADB), I reloaded the drivers using the KF Utility. It is still detected as "Android ADB Interface" but with an error in Device Manager. The error is "This device cannot start. (Code10)". I uninstalled it, including drivers, and let Windows autodetect. It was identified as "kindle", so I ran the same driver package and it still sees it as "Android ADB Interface", but still with the error.
[UPDATE 2] - Steps I took to (finally) get mine working
Note: If your device is recognized in Device Manager as something *other* than "Unknown Device* (such as "kindle" or "Android ADB Interface"), skip to step 3.
1. Turn off the device.
2. Plug the device into USB to your computer. This should turn the device on.
3. Delete the ".android" folder from your Windows profile. This is very important. If you just uninstall the device and driver, Windows will still use this to reinstall the device. You want to start as fresh as possible to eliminate complications from previous attempts.
4. Uninstall it from Device Manager. Make certain to check the box to uninstall the driver as well.
5. Start a new scan for hardware changes in the Device Manager.
6. As mine was stuck in fastboot mode, it recognized the device as "kindle" (lower-case "k")
7. Run the "install_driver.bat" from the Kindle Fire Utility.
8. After driver install, run the Kindle Fire Utility.
9. ADB status will say "offline", that's fine.
10. Choose option 1 to go into the Bootmode Menu.
11. Choose option 1 to boot into Normal Mode.
12. It will be stuck at <waiting for device>.
13. Turn off the device, keeping it plugged into the PC. *very important* This step was one among others that made THE difference for me.
14. Turn on the device. *Hopefully*, you should immediately see the utility spit out some text and your device should reboot.
15. Boots up!! (well, mine did, and I had almost give up hope were it not for my pride and stubbornness).
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on device drivers.
"Android ADB Device" typically means the device is in fastboot mode and you cannot use adb while in fastboot mode.... you must use fastboot.
With your KF off and disconnected from your work computer, run this command...
Code:
fastboot -i 0x1949 getvar product
and then connect it to the computer. The KF will turn on automatically. The computer will say "<waiting for device>" for a bit, but if the command works, it will eventually return "product: kindle" as output. If that works, you can actually flash TWRP from there, but if you are anxious for it to do something again...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
should get it booting normally again. If it doesn't, look at the link I gave you and focus on getting your drivers fixed. You won't be able to execute any commands (fastboot or adb) through Windows if the device drivers don't work. You might want to go back to Firekit if drivers remain problematic for you.
Everything you need to know to fix your KF is in that link at the beginning of my post, including the commands you need to run. At the bottom of post #3 is also another link to a how-to root/install ROMs page.
IT LIVES!!! While I was still getting the error code 10, I launched the KF utility one more time. ADB status was still offline. I went into the menu to modify boot mode, told it to boot in normal mode and it was stuck <waiting for device>. On a whim, I left it there and cycled power on my KF. It found the device, finished, rebooted, and it's good!!! The Device Manager is happy now too!!
The behavior was so odd between my work and home PC. I was seriously scared when it gave a bad device ids on my home PC. I think it was more a combination of several different things that helped, and I'll update my main post with all that I did to get it back (that I can remember). Hopefully it will help someone else.
This is an *amazing* community, and I can't thank everyone enough for the incredible work you all do and the true sense of selflessness exhibited here on the forums!
btw, How do I edit the subject to indicate it's solved?
^_^
OH ,MY GOSH I DO NOT NO HOW MUCH TO THANK U THNX FOR THE POST
jaetrix said:
OH ,MY GOSH I DO NOT NO HOW MUCH TO THANK U THNX FOR THE POST
Click to expand...
Click to collapse
Glad it could help someone! I was frustrated enough about it and couldn't find a single solution that fit my issue. I just had to combine some to get it to work for me.
Bump
Yes this saved two bricked kindles. Trial and error is sometimes the best means to solving a problem.
Sent from my GT-I900 using xda premium
This is happening alot here of recent thats why I bumped it to the top of the list
Thank you for this. Maybe a moderator will be kind enough to sticky this.
Sent from my Galaxy Nexus using Tapatalk 2
pugsley42 said:
I seriously need some help. My normally fierce Google-fu has failed me. I have searched countless threads on here (and elsewhere) and tried just as many solutions, but I haven't had any luck. My Kindle Fire is stuck at the "Kindle Fire" boot logo. I was using the KF utility, and ADB status was online, everything looked good. I chose the option to root and install TWRP. However, it couldn't grab TWRP through my corporate firewall/proxy, so it skipped it, placed my KF in fastboot (I think), rebooted, now I'm bricked.
[...]
15. Boots up!! (well, mine did, and I had almost give up hope were it not for my pride and stubbornness).
Click to expand...
Click to collapse
Pugsley42...you 'da man! I had the same story as you told above, including searching and following countless threads of instructions. Nothing worked until I found your instructions! Thank you, thank you, thank you!
Stuck at the KF logo
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Neely said:
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Click to expand...
Click to collapse
My first suggestion would be to read this:
http://forum.xda-developers.com/showpost.php?p=25884555
Neely said:
These steps still didn't work for me :-/ I'm still stuck with the KF logo and a "Waiting for device" prompt. I've read through these forums starting with the "KKFB" to this one and still haven't had any luck yet. It may be time to give up on her. I think I have royally messed her up.
If anyone else has any other suggestions I'm open i've tried everything else on here I can find.
Thanks
Neely
Click to expand...
Click to collapse
Agreed, you really need to be more specific. "Waiting for device" .... which part of the KF utility?. What *exactly* are you seeing, where? What does Device Manager show your KF identified as (keep in mind, there is a big difference between seeing it as "Kindle" and "kindle"). What *exactly* did you do that brought you to this point?
Symptoms. Symptoms. Symptoms. The more detail you provide, the more likelihood we can help.
Take heart. If there's anything I learned in my stubborn refusal to admit my KF was fully bricked, is that it can be brought back from a lot worse than we give it credit for. I also learned quite a bit that I never would have if I never failed. That's what I love about breaking things!
pugsley42 said:
Agreed, you really need to be more specific. "Waiting for device" .... which part of the KF utility?. What *exactly* are you seeing, where? What does Device Manager show your KF identified as (keep in mind, there is a big difference between seeing it as "Kindle" and "kindle"). What *exactly* did you do that brought you to this point?
Symptoms. Symptoms. Symptoms. The more detail you provide, the more likelihood we can help.
Take heart. If there's anything I learned in my stubborn refusal to admit my KF was fully bricked, is that it can be brought back from a lot worse than we give it credit for. I also learned quite a bit that I never would have if I never failed. That's what I love about breaking things!
Click to expand...
Click to collapse
Okay, I was attempting to load a ROM on it. It had been rooted already with no issues and then something happened during the installation of TWRP and spit out an error message of unable to load and then rebooted. That's where I am with the kindle fire boot screen.
As for the "Device Manager" It shows up as "Android Composite ADB Device" and with KFU it shows the following status:
ADB Status: Online
Boot Status: Unknown
At this point is when if I try to run Install Latest TWRP Recovery or FFFF or anything it just sits there and says "Waiting For Device"...
I've read though most of these posts and have tried several different suggestions with no luck so far. So I have actually read through here. :-/
Hope this helps at all.
I would try by trying to change the bootmode using the KF utility. If you're stuck at the KF logo on boot, then the other functions of the utility won't do anything. Your KF needs to be in a "usable" state before that can happen. Have you tried changing it to "Fastboot" or "Normal"?
Stuck at the KF logo
pugsley42 said:
I would try by trying to change the bootmode using the KF utility. If you're stuck at the KF logo on boot, then the other functions of the utility won't do anything. Your KF needs to be in a "usable" state before that can happen. Have you tried changing it to "Fastboot" or "Normal"?
Click to expand...
Click to collapse
Yeah, I've tried it using the KF Utility as well as using fastboot at the command line :-/
kinfauns said:
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on device drivers.
"Android ADB Device" typically means the device is in fastboot mode and you cannot use adb while in fastboot mode.... you must use fastboot.
With your KF off and disconnected from your work computer, run this command...
Code:
fastboot -i 0x1949 getvar product
and then connect it to the computer. The KF will turn on automatically. The computer will say "<waiting for device>" for a bit, but if the command works, it will eventually return "product: kindle" as output. If that works, you can actually flash TWRP from there, but if you are anxious for it to do something again...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
should get it booting normally again. If it doesn't, look at the link I gave you and focus on getting your drivers fixed. You won't be able to execute any commands (fastboot or adb) through Windows if the device drivers don't work. You might want to go back to Firekit if drivers remain problematic for you.
Everything you need to know to fix your KF is in that link at the beginning of my post, including the commands you need to run. At the bottom of post #3 is also another link to a how-to root/install ROMs page.
Click to expand...
Click to collapse
Your explanation and guidance cut right to the solution for me. Thank you so much!
Thank you!!
I've been searching forever for this same issue. This has not fixed it completely but has helped me! Thank you for taking the time to post this!!
cmgroden said:
I've been searching forever for this same issue. This has not fixed it completely but has helped me! Thank you for taking the time to post this!!
Click to expand...
Click to collapse
I presume if any of this helped, you were able to get further than you have been. What state is it in now? What error(s) if any?
I seem to be having this same issue but I cannot get my pc to recoginze the kindle fire as anything. perhaps i did something wrong but i was following a video on youtube and though i was doing it exactly as it showed. First thing i did after I finally got the drivers loaded was start KFU and then chose to load TWRP. It started the process but when it hit the part about rebooting my device that's where it stopped. Since then i've been stuck at the white and yellow kindle fire logo. No matter what i do to try to reinstall the ADB drivers I cannot get my computer (win xp) to recognize the kindle. It shows as "unknown device" in device manager and when it's plugged in the little pop up says that the usb device has malfunctioned and windows doesn't recognize it. So am I totally dead? I'm assuming before i can do anything to recover it I need to get windows to recognize it with the ADB drivers.
Hey Guys, weird problem. I bought my sister a Kindle Fire for her birthday and I wanted to root and flash MoDaCo before I gave it to her so she could use the Google Play store. I received it in the mail today and went to go flash TWRP and FFF and it said "offline" on the adb status. I thought it was particularly odd because I rooted my KF using KFU on this same computer. I checked out the drivers anyway though and it said ADB user interface or something to that effect, which was correct. I thought maybe KFU was just acting funky so I went for it and it downloaded TWRP (which I am glad is back up and running) and then just sat there <waiting for device>. Then I tried just running a few ADB commands to see what would happen and so I tried adb devices and it came back with the string of numbers and then at the end it said offline. I have never seen that before, of all of the android devices I have fiddled with and rooted, I have never seen where it was connected to adb but "offline". This is where I reached out for my only known alternative which was my factory cable so I could just flash via fastboot and call it a day, I turned off the kindle and plugged in the factory cable and ran my first command: fastboot devices. it just returned to the command prompt. So I then just tried going for it, again. "fastboot flash recovery twrp.img" and then I got <waiting for device>..... That's all I've got, I really have no idea what there could be left. It seems like a driver issue and I would just go get my linux box and hopefully that would get it done but I don't have it with me, as I am just home from college for the day to give this gift to my sister. Any help would be hugely appreciated!
nschiwy said:
Hey Guys, weird problem. I bought my sister a Kindle Fire for her birthday and I wanted to root and flash MoDaCo before I gave it to her so she could use the Google Play store. I received it in the mail today and went to go flash TWRP and FFF and it said "offline" on the adb status. I thought it was particularly odd because I rooted my KF using KFU on this same computer. I checked out the drivers anyway though and it said ADB user interface or something to that effect, which was correct. I thought maybe KFU was just acting funky so I went for it and it downloaded TWRP (which I am glad is back up and running) and then just sat there . Then I tried just running a few ADB commands to see what would happen and so I tried adb devices and it came back with the string of numbers and then at the end it said offline. I have never seen that before, of all of the android devices I have fiddled with and rooted, I have never seen where it was connected to adb but "offline". This is where I reached out for my only known alternative which was my factory cable so I could just flash via fastboot and call it a day, I turned off the kindle and plugged in the factory cable and ran my first command: fastboot devices. it just returned to the command prompt. So I then just tried going for it, again. "fastboot flash recovery twrp.img" and then I got ..... That's all I've got, I really have no idea what there could be left. It seems like a driver issue and I would just go get my linux box and hopefully that would get it done but I don't have it with me, as I am just home from college for the day to give this gift to my sister. Any help would be hugely appreciated!
Click to expand...
Click to collapse
First things, first...In Windows, if you are in fastboot and you get "waiting for device", it is a driver issue, plain and simple. In rare cases it could be a bad USB cable or port, but those are very unlikely considering what we see on a daily basis.
To understand the adb issue, you have to take a look at KFU's run.bat. To decide whether it is "connected" or not, it checks to see what state the device is in, i.e. in fastboot or booted normally or in recovery. To get the status (online/offline), it sends an "adb devices" command. If the command returns "List of devices attached -null-", the script will return a status of "offline". Either way, you are dealing with a driver issue.
I bought a couple of factory cables to test and share and found that if i just plugged it in an typed fastboot devices nothing would be returned no string nothing but if I powered it of and typed
Code:
fastboot -i 0x1949 getvar product
and then plugged it in it would power on and present product: kindle then fastboot devices would produce the string of numbers I was looking for. Dont know why it works this way but it does give it a shot...
nschiwy said:
Hey Guys, weird problem. I bought my sister a Kindle Fire for her birthday and I wanted to root and flash MoDaCo before I gave it to her so she could use the Google Play store. I received it in the mail today and went to go flash TWRP and FFF and it said "offline" on the adb status. I thought it was particularly odd because I rooted my KF using KFU on this same computer. I checked out the drivers anyway though and it said ADB user interface or something to that effect, which was correct. I thought maybe KFU was just acting funky so I went for it and it downloaded TWRP (which I am glad is back up and running) and then just sat there <waiting for device>. Then I tried just running a few ADB commands to see what would happen and so I tried adb devices and it came back with the string of numbers and then at the end it said offline. I have never seen that before, of all of the android devices I have fiddled with and rooted, I have never seen where it was connected to adb but "offline". This is where I reached out for my only known alternative which was my factory cable so I could just flash via fastboot and call it a day, I turned off the kindle and plugged in the factory cable and ran my first command: fastboot devices. it just returned to the command prompt. So I then just tried going for it, again. "fastboot flash recovery twrp.img" and then I got <waiting for device>..... That's all I've got, I really have no idea what there could be left. It seems like a driver issue and I would just go get my linux box and hopefully that would get it done but I don't have it with me, as I am just home from college for the day to give this gift to my sister. Any help would be hugely appreciated!
Click to expand...
Click to collapse
Try this it works fine for me so far. I'm facing the same problem as you ADB Offline,
1) Switch off your kindle.
2)start KFU (ensure it's the latest v. 0.9.6) on your desktop
3) Connect your factory cable to kindle first then to PC ( take note ADB status will still be Offline).
4) Kindle will boot by itself
5)when boot logo is on the kindle fire screen go to KFU press 5 (install latest firefirefire)
6)Installation firefirefire complete next press 3 install latest TWRP Recovery
7) Done. Now you can access to TWRP and flash your ROM
Thanks for all of the advice guys, in the end I wound up giving it to her with stock running so she can get used to it. Maybe sometime down the road I can help her with root and such. She is only 11, after all.
Rooting Problems
Lol I hope this doesn't affect me because I'm actually 12 With the same problem On My KF Ill try those BTW I jailbreaked a iTOUCH 4G With redsn0w and I un jailbreaked it Unsafe Way But GamePlayer Still Works
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
favaron88 said:
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
Click to expand...
Click to collapse
Do you have a bootloader installed? Can you boot into recovery?
Eaffon said:
Do you have a bootloader installed? Can you boot into recovery?
Click to expand...
Click to collapse
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
favaron88 said:
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
Click to expand...
Click to collapse
Hmm... Does it show up in device manager?
Dont throw it.. give it to me. Haha
After my sem I will have plenty of time to do all this stuff..
Sent from my SGH-T999 using xda premium
Eaffon said:
Hmm... Does it show up in device manager?
Click to expand...
Click to collapse
I've uploaded a screen shot of my device manager and in "devices and printers"
as you can see, it shows up as a kindle in devices and printers, and as an android phone in the device manager.
I also uploaded "My Computer" so you can see there is no access to it from there.
Okay.
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Eaffon said:
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Click to expand...
Click to collapse
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
favaron88 said:
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
Click to expand...
Click to collapse
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Eaffon said:
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Click to expand...
Click to collapse
alright, I found it and tried those commands and this is what I got.
favaron88 said:
alright, I found it and tried those commands and this is what I got.
Click to expand...
Click to collapse
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Eaffon said:
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Click to expand...
Click to collapse
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
You could try my prefab ISO soupkit is already ran on it and it has teamviewer installed for assistance measures you can find it here post 7 http://forum.xda-developers.com/showthread.php?t=1413358 but what I think you will need is a factory cable found here ultimately post 9 http://forum.xda-developers.com/showthread.php?t=1392693 . The system is trying to run that's why it comes up android composite adb interface, its busy trying to handle the data that you failed to wipe prior to flashing jelly bean and then stock. You could also see if if will allow you to send twrp and fff back to the device with kfu then enter recovery wipe and reflash another ROM.
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
It's totally fixable.
Thepooch is right. My brother had the same problem with his son's. Just get into fastboot and flash a bootloader and twrp and youre set
Sent from my Amazon Kindle Fire using xda app-developers app
Thepooch said:
It's totally fixable.
Click to expand...
Click to collapse
Awesome
Also I didn't want you to think I ignored your post. I just finished making the usb drive with ubuntu on it and was going to attempt your solution in the other thread if whatever we were trying here doesn't work.
I appreciate y'alls help very much.
Eaffon said:
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Ok I loaded KFU and told went and told it to boot in fastboot, it said that it told the device to do it, but it still says Boot Status: Unknown.
Is this a problem or do we know that it's booting in fastmode now? I'm just not sure how to tell if it was successful since it's not giving me the code.
(Ps - I originally posted this before my previous post thanking you guys, but then came back to this window to see that I had screwed up the Captcha, but it wouldn't let me post for 5 more minutes since I'm a new user. Sorry for the wait.)
Its very common for the boot mode to be unknown in fast boot. Try to send twrp with kfu if it says waiting for device for a long time simply power it off while connected then back on it should then pick up and send twrp. If need be do the same thing with the bootloader just wait longer a failed bootloader flash is far worse than the situation your in.
favaron88 said:
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
Click to expand...
Click to collapse
ADB is connected, therefore you are not in fastboot. The Kindle Fire logo you see is actually the stock boot animation. The difference is whether or not it changes in brightness at any point (obviously it does).
You need access to recovery to fix your problem and you need the ability to change bootmodes to get into recovery. Without a working shell you need access to fastboot to change bootmodes.
Unfortunately, in many situations like yours, there is no working shell to change the bootmode. To confirm this, try to launch the shell by entering "adb shell", respectively.
If you receive an error, your only options are to get a factory cable (recommended) or open the device so you can put it in USBboot via the shorting trick and the use of Firekit (not so recommended).
With access to fastboot, you can change your bootmode to recovery or reinstall a custom recovery if necessary. In recovery, the "fix" is as simple as reinstalling a ROM.
"That's a special kind of stupid. The kind that makes me laugh."
Hi all,
My Kindle Fire HD (model 001400) was semi-bricked when I tried to install a custom ROM instead of the Amazon native OS. I bought a factory cable and was able to get to fastboot (the screen showed a "Fastboot" logo with a little sign of traffic lights and a blinking green light animation).
I tried to follow some of the threads that showed how to recover (KFHD Restore Tool) but none worked. I think now that it was because after using the factory cable to fastboot I should have used a normal cable to adb/fastboot, but I'm not sure about this anymore.
Anyway, I used this thread
http://50.23.216.69-static.reverse.softlayer.com/showthread.php?t=2128848
And I tried to do the
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
After doing that (succesfully according to the KF screen) the Kindle Fire HD is no longer turning on. Tried to charge it for a day, connect it to my PCs and Macs with a fastboot (factory) cable and with a normal cable, without success. No signs of life.
I've seen on the question 34 (Q34) of the FAQ that it seems there's nothing to do, but I wanted to make sure that there is really nothing to do now. I think this is a 2nd generation KFHD, but I'm not sure either. On fastboot the devices was recognized as Otter 1400 or something similar.
So... Any chance to recover it?
javipas said:
Hi all,
My Kindle Fire HD (model 001400) was semi-bricked when I tried to install a custom ROM instead of the Amazon native OS. I bought a factory cable and was able to get to fastboot (the screen showed a "Fastboot" logo with a little sign of traffic lights and a blinking green light animation).
I tried to follow some of the threads that showed how to recover (KFHD Restore Tool) but none worked. I think now that it was because after using the factory cable to fastboot I should have used a normal cable to adb/fastboot, but I'm not sure about this anymore.
Anyway, I used this thread
http://50.23.216.69-static.reverse.softlayer.com/showthread.php?t=2128848
And I tried to do the
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
After doing that (succesfully according to the KF screen) the Kindle Fire HD is no longer turning on. Tried to charge it for a day, connect it to my PCs and Macs with a fastboot (factory) cable and with a normal cable, without success. No signs of life.
I've seen on the question 34 (Q34) of the FAQ that it seems there's nothing to do, but I wanted to make sure that there is really nothing to do now. I think this is a 2nd generation KFHD, but I'm not sure either. On fastboot the devices was recognized as Otter 1400 or something similar.
So... Any chance to recover it?
Click to expand...
Click to collapse
The fact that you don't know what device you have is a little disturbing. If your device said "otter" anything in fastboot, then you definitely do not have a Kindle Fire HD.
If that's the case, you flashed the wrong bootloader for your device and it is very unlikely that you will ever recover it.
The device IS a Kindle Fire, maybe not an HD. The only thing I'm not sure about is whether it's a first or a second generation. The only hint I've got is that "Otter 1400" (or something similar, again) string that the "fastboot devices" command gave as output. That makes sense, since the Model No. is D01400, which AFAIK is a Kindle Fire 7'' WiFi (2012).
Anyway, the fact is I probably tried to use the wrong bootloader, but I was expecting maybe the Firekit solution could be appropiate for my now not-turning-on device.
Can someone confirm the brick is a definitve brick?
javipas said:
The device IS a Kindle Fire HD. The only thing I'm not sure about is whether it's a first or a second generation. The only hint I've got is that "Otter 1400" (or something similar, again) string that the "fastboot devices" command gave as output. That makes sense, since the Model No. is D01400, which AFAIK is a Kindle Fire 7'' WiFi (2012).
Anyway, the fact is I probably tried to use the wrong bootloader, but I was expecting maybe the Firekit solution could be appropiate for my now not-turning-on device.
Can someone confirm the brick is a definitve brick?
Click to expand...
Click to collapse
Oh my...
Have a seat, my friend, because you're about to learn something...
In fastboot, if you were actually successful in sending the "fastboot devices" command (not possible on the HD), the output would be something similar to the following...
Code:
1234567890ABCDEF fastboot
...however, if you had a Kindle Fire HD7 and used the "fastboot getvar product" command, the output would be something like "TATE-XXXX-XXX". Respectively, the Kindle Fire HD8.9 would be "JEM-XXXX-XXX", the Kindle Fire 2 would be "OTTER-XXXX-XXX" and the original Kindle Fire would be "kindle".
Furthermore, only the original Kindle Fire and the Kindle Fire 2 (non-HD), have the model number D01400.
Now, whether you have an original Kindle Fire or a Kindle Fire 2 is still up for debate because you are clearly confused about what device you have in the first place. If you are lucky, and in fact have an original Kindle Fire, you will be able to restore it using Firekit. Unfortunately, considering the information available, I'm willing to bet that you have a Kindle Fire 2, and thus there is no way for you to restore your device.
Thanks for the clarification, that was perfect. I'm affraid I've got a Kindle Fire 2 then, so it seems there's nothing to do. Maybe in the future some method will appear to recover this second generation, who knows.
Greetings soupmagnet!
Easy Way to tell KF&KF2 from HDs: If it has a camera its a HD. Duh.
Sent from my Amazon Kindle Fire using xda app-developers app
Please help me!
I rooted my girlfriend's Kindle a few days ago in order to install the Google Play store. Managed that just fine and installed a few apps. I then decided it would be a good idea to change the launcher and get shot of the carousel. I tried the next Launcher 3D and followed an online guide to install it. On rebooting the Kindle I got a constant pop up advising Next Launcher 3D had stopped working. It popped up continually every 1/2 second or so and I couldn't get rid of it,
Again I had a look online and found a guide to removing it using command prompt script via ADB. I went through the instructions correctly but it kept telling me the app didn't exist. Using the dir command showed the app though. Confused I tried again a couple of times. I then got a pop up on the device telling me another app.....something relating to Swype had stopped working. The Kindle rebooted itself and presented a screen with a red triangle and 'Kindle Fire System Recovery' giving me the options to either reboot or reset to factory defaults. I tried both of these options (perhaps foolishly) and had no success.
I was given some further advice from a very helpful poster on here to get KFFAide v100 and enter some fastboot commands. On entering the command 'fastboot -i 0x1949 getvar product', the script shows 'waiting for device'. Powering on the device at that point does nothing more than booting to the same screen with the red triangle. Windows does not acknowledge that the device is connected at all.
It would seem I was hasty in rooting the device. Having rooted several other Android devices I was clearly overconfident in my ability and now find myself at a loss. Is there any way at all for me to recover the device at this point? Or should I now file this under 'very expensive experience and education'?
Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hi Stunts513. Thank you for your reply. Have tried what you said above and Windows (8) just doesn't detect that the device has been connected. No pop up from system tray, nothing in file explorer and nothing, not even for a second in device manager.
Am at a loss for the moment. Will have to get hold of an Ubuntu CD and try that way. Am just praying it detects the Kindle. Didn't on my girlfriends laptop nor my PC so am mildly panicked just now.
OK, so I went through Linux Mint and installed the SoupKit and tried it that way. Same result. The device just isn't detected at all. Really starting to fear the worst here. The fact it's still powering on should give me some faith but i've tried all I can think of and everything advised and cannot proceed past this point.
Does anyone have any last gasp possibilities for me? Borderline desperate here now.... will try anything at this point.
In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Did exactly that. Brought up the virtual terminal. Nothing.
Have tried everything now I think. Used different PCs. Different cables. Different OS. Tried bypassing getvar and just trying a manual command "fastboot -i 0x1949 flash recovery recovery.img". Nothing is getting any response from this device other than booting to the recovery screen.
Suspect I may be out of luck.
Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah it is most definitely an 8.9 model. Am not sure what I have done to it but it is not being detected by any OS whatsoever. Have bitten the bullet and bought the Mrs a replacement. Expensive error on my part.
Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Many apologies for the delay. i managed to get the Kindle up and running following your advice coupled with that on another thread. Although it wouldn't detect in either Windows 8 or Ubuntu, it did so on Windows XP. Don't imagine you can begin to explain that one any better than I can as it's entirely illogical......but there you go. From there it detected as a JEM device and I was able to run KFFA and do a complete restore.
I now have it the way I intended to have it in the first place. Changing the launcher was fruitless as I couldn't get the wallpaper fix to work but am fine with that. had a look at customising the icons on the carousel but boy does that look like more trouble than it's worth!! Lol.
I wont pretend I was going to send my Kindle off to you guys. In truth I would have sold it to recoup some of my losses and raise funds towards the replacement. I will however be making a donation to the team very shortly as a token of my appreciation.
Thank you very much for all your help. it is greatly appreciated.