Related
Well, I've been having some issue with signal on my desire so I won't to prove it wasn't the rom I was using. I downloaded the offical htc rom and started flashing it. It got so far then hung waiting on the bootloader... after an hour it was still waiting.
I pulled the battery and now it won't boot. It vibrates but nothing else.
If I remove the battery and put it in again, when I connect the charger the led comes on. If I turn it on with usb connect the pc seems to see it but I con't do anything with it.
ANY IDEAS????
can you connect with adb ?
Never used adb... only ever used fastboot but It won't enter bootloader to get there. If you can let me know what to try i'll give it a go.
googled it,
adb kill-server --> OK
adb wait-for-device --> nothing
adb reboot-bootloader --> nothing
Do a search for SLCD brick. There is a extensive tutorial on how to fix that.
Sent from my HTC Desire using XDA App
Hello Everyone,
I will try to provide as much details as I can from what I remember.
Basically, I tried to ROOT my device and install TWRP. However, I messed it up the first time. I tinkered with it for hours but it still couldn't work until finally, after hard resetting for the unlimited time, it booted up.
The problem though, is that it wasn't rooted and TWRP wasn't installed when it came up so I tried it again. Second try, second time it was messed up. Annoyingly, I don't know what I did earlier to make it work. The second instance it happened is just like the first.
Just to be clear, this isn't the boot screen where the kindle fire logo is animated (has reflections). In my case, its the logo as is, stuck on the screen just like that. Tried hard resetting, doesn't work.
What do I know?
1) From my earlier experience, it has lesser to do with the system (PC, Mac) and drivers since I managed to get it boot up again without being connected the first time
2) If I do connect it to the PC, it says Cannot Start Device/Unable to Start Device. Code:10. That's it. Even if I reboot the device, its still the same.
3) If you connect it to the Mac, it is detected in system preferences. Problem though is that I tried using adb and just like its windows counterpart, there are no devices detected.
THOUHGTS:
1) I know I just have to get it to be recognized and I can change the bootmode. Something's telling me that its a boot mode problem only. In my earlier V3X phone, I used to TP (testpoint) if anyone's familiar with that, or shortcircuit the board to get it out of the 'loop'. Do we have that with the kindle fire?
2) What operating system would it be easiest to get the device detected. I'm hoping that if there's lesser complications with the device being detected by the computer, be it mac, linux or windows, I can change the bootmode. my technical instinct tells me it has something to do with boot mode.
What have I done already?
1. Let me see, I believe I tried hard resetting it for ALOT of times already
2. Reinstalled drivers on PC. Used both Android and Kindle Fire Utility drivers. Even checked the /android folder
3. I'm using a Nokia Micro-USB cable. I'm not sure if that has any impact on the device or its effectiveness but I will try to pick-up another cable today and post later.
I would really appreciate if anyone can help. It sucks that I tried this just after unboxing the unit. I haven't even tried doing anything on it yet.
If you can help, ANY help would be appreciated.
Thanks mate!
had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
the entry for 18D1 in adb_usb.ini is missing - had to add it
the other entries are allready in version .6 android_winusb.inf
if you have troubles to remove old drivers use this:
http://support.microsoft.com/kb/315539/en-us
unplug/replug and install the drivers from .6 from scratch
it's not needed to reboot the computer - works immediately
waiting to get your status ...
b63 said:
had the same
1. use computer (windows - in my case windows xp)
2. nokia cable is fine (i use it too)
3. use kf utility .6
is your kf recognized by the computer ? (adb device or composite adm device)
have you tried to shutdown and startup your computer ? (not restart)
waiting to get your status ...
Click to expand...
Click to collapse
Did you solve your problem?
My kindle is recognized by my computer but it as either ADB device or Composite ADB device (depending on what drivers I use to install it). Problem is that it says Cannot start device. Code Error: 10. Tried shutting down/restarting PC, still the same.
updated my initial post again ... (ms-link)
yes solved it in minutes
make the additional entry in adb_usb.ini
use only the drivers from .6
i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
whats your status ?
i think best way is to disconnect the kf - uninstall all old drivers regarding adb device - connect kf - use only drivers from .6 utility - start utility - change bootmode - up again !
Click to expand...
Click to collapse
I did this but it still says device cannot be started.
make the additional entry in adb_usb.ini
Click to expand...
Click to collapse
0x18D1 -- is that what I'm supposed to add to adb_usb.ini?
yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually
b63 said:
yes exactly - the device changes between the two id's regarding the bootmode
and don't let the computer select the driver - select manually
Click to expand...
Click to collapse
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.
kaswistry said:
Okay, so I followed the instructions to a T.
I followed the MS Link to remove all drivers and then plugged-in the kindle and installed it back again by specifically telling windows that 'I have a disk'. It still says Code 10.
If it would mean anything, I'm doing this on a virtual machine since the computers around me are all Windows 7s.
Click to expand...
Click to collapse
all this works using windows 7
dustyjerran said:
all this works using windows 7
Click to expand...
Click to collapse
I did try this yesterday on Windows 7 but most guides I see do it on older versions. I will try again a little later. Thank you.
I tried it on Windows 7. Still the same error. Kindle is frozen and on Device Manager it says "This device cannot start. (Code 10)"
I ran into the exact problem yesterday. I thought I bricked my kindle. That was scary. Anyway, the problem is that you're stuck on fastboot, mode 4002 instead of a normal mode 4000.
Following rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/
You'll need to add a new vendor id (0x18d1). However, even with that the device still will not be recognized right away. Following another user's suggestion on that same thread, I let the battery drained out. Once that's done, reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Then do the adb commands (even if it doesn't show any device attached)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Your device will reboot out of the stuck "kindle fire" logo screen. If your device goes dark after, it just means that the battery need to recharged first. Another scary moment for me. You can unplug and use the wall charger, much faster than charging by PC. After 5 - 10 minutes, you should get back to your normal screen. Then, just use the Kindle Utility to install TWRP.
You'll need to add a new vendor id (0x18d1).
Click to expand...
Click to collapse
I added this already
reconnecting the Kindle will show up as simply "kindle" on the device manager instead of the normal "unrecognized device".
Click to expand...
Click to collapse
Actually, the problem with mine is that it's detected. However, it shows up as Code:10, The device is unable to start.
Still, I'll try to drain it first, tinker with it next and see what happens. That or I'll wait for tomorrow and open the whole device already and see if I can OMAP it.
Mine also did show up as code 10, and sometimes code 43 ... I tried uninstalled the driver and reinstall it manually each time and eventually showed up as unrecognized ... so I tried the battery drain ... I even tried putting it in the freezer to quicken the drain but not sure if it actually help ..
I tried the battery draining. Nope, still didn't work
UPDATE: I take this back. After draining the battery, I would like to confirm that the issue has been fixed. Thank you, THANK YOU Everyone! )
I REALLY APPRECIATE THE EFFORT. HAPPY HOLIDAYS! )
A family member recently got a Kindle Fire, I tried to flash recovery but it got stuck in fastboot mode. Windows will recognize it as uknown device but Linux won't detect anything in fastboot or adb.
I will try battery drain out since kaswistry said it worked
If all else fails, I will try this.. http://forum.xda-developers.com/showthread.php?t=1405052
EDIT: nevermind lol, this worked.. http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11 even though i tried it several times already..
I have the same problem too, the kindle fire stuck at the boot logo
kf utility show that when i try to restore or other option!
Changing bootmode doesent work at all
*imageshack/photo/my-images/10/60506677.png/[/url] (imageshack link)
KF utility status fastboot... offline
*imageshack/photo/my-images/834/kfustatus.png/
My computer have the right driver!
can anybody help me?
*sorry for my bad english*
Could it be that something destroyed my FireFireFire boot? My KF always gets stuck in fastboot when I try to flash ... obviously quite annoying.
u guys need to talk to vashypool in irc and he can fix it!! he fixed mine and mine was a complete brick
If it gets stuck in fastboot you need to run the command fastboot idme bootmode 4000 from the Android SDK.
Sent from my Kindle Fire using Tapatalk
In my case, i have tried to install the original 6.2 kindle firmware with TWRP. After that, the kindle staying stuck on the boot logo... This is me story... I think my kindle is stuck on fastboot! I tried to change bootmod with FK utility v.6
This is what kf utility gave me, when i try to reinstall twrp
imageshack.us/photo/my-images/10/60506677.png/
And this is the kf utility status
imageshack.us/photo/my-images/834/kfustatus.png/
Is anybody can say me, if my kindle is bricked for ever? Or have a solution
Happy holiday btw
#sorry for my poor english#
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
Hey guys... Only second kindle I've ever attempted (have a butyload of other android devices I've rooted... But this bigger with no other buttons has me stumped )
Anyway... Went to root today, plugged in kindle, battery was dead... No problem... Let it charge.
When it booted, ran KFU to tell it to install TWRP. Here's where it gets....odd.
I had twrp in the KFU folder but it decided it wasn't there and wanted to download it... Mind you, this is... I believe... After it sent a command to fastboot ... Well, I didn't have internet, so KFU just sort of stopped when it couldn't download twrp...
Since then, the kindle is just stuck on KindleFire screen... Doesn't go any further... If I let the battery run out for about an hour, it will start rebooting every 5 seconds even if I plug it in. In the "bootloop" I can't turn it off, it just keeps rebooting...
If I let it die, I can plug it in, let it charge and turn it on... Sticks at KindleFire screen... I have tried holding in power for 30 seconds... It just turns the kindle off, doesn't help.
Windows sees it as an unrecognized device (tried rebooting, unplugging, uninstalling the drivers, looking at the KFU folder to manually select drivers (windows says they're not the correct drivers for the device) adv can't see it (cms... Adb devices shows no devices connected)
Any help is appreciated... If I missed needed info, please ask and ill supply...
I'm happy to try anything and report the findings...
RBThompsonV said:
Hey guys... Only second kindle I've ever attempted (have a butyload of other android devices I've rooted... But this bigger with no other buttons has me stumped )
Anyway... Went to root today, plugged in kindle, battery was dead... No problem... Let it charge.
When it booted, ran KFU to tell it to install TWRP. Here's where it gets....odd.
I had twrp in the KFU folder but it decided it wasn't there and wanted to download it... Mind you, this is... I believe... After it sent a command to fastboot ... Well, I didn't have internet, so KFU just sort of stopped when it couldn't download twrp...
Since then, the kindle is just stuck on KindleFire screen... Doesn't go any further... If I let the battery run out for about an hour, it will start rebooting every 5 seconds even if I plug it in. In the "bootloop" I can't turn it off, it just keeps rebooting...
If I let it die, I can plug it in, let it charge and turn it on... Sticks at KindleFire screen... I have tried holding in power for 30 seconds... It just turns the kindle off, doesn't help.
Windows sees it as an unrecognized device (tried rebooting, unplugging, uninstalling the drivers, looking at the KFU folder to manually select drivers (windows says they're not the correct drivers for the device) adv can't see it (cms... Adb devices shows no devices connected)
Any help is appreciated... If I missed needed info, please ask and ill supply...
I'm happy to try anything and report the findings...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2166668
#30 & #31
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2166668
#30 & #31
Click to expand...
Click to collapse
OK... but why does it stick on the KindleFire logo? (It does that without rebooting, it just hangs there).. And the battery drain was not intentional... It's ff now... charging (I assume... no logo, no led )
RBThompsonV said:
OK... but why does it stick on the KindleFire logo?
Click to expand...
Click to collapse
#16
It's ff now... charging (I assume... no logo, no led )
Click to expand...
Click to collapse
I would have to agree...it does appear to be charging.
soupmagnet said:
#16
I would have to agree...it does appear to be charging.
Click to expand...
Click to collapse
Sorry if im being super-noobish... I prefer my nook over this kindle
The logo is bright and unchanging (Seems to be stuck in fastboot?) But adb doesnt recognize it... windows sees it as an unknown device... and KFU shows... well, nothong Even when I try to normal boot in KFU (or adb..) it hangs on waiting for device.
Also, thanks a billion for even responding Soup... Its nice to know there's someone out there
RBThompsonV said:
Sorry if im being super-noobish... I prefer my nook over this kindle
The logo is bright and unchanging (Seems to be stuck in fastboot?) But adb doesnt recognize it... windows sees it as an unknown device... and KFU shows... well, nothong Even when I try to normal boot in KFU (or adb..) it hangs on waiting for device.
Also, thanks a billion for even responding Soup... Its nice to know there's someone out there
Click to expand...
Click to collapse
Okay,
Yes, it is in fastboot. ADB won't recognize the device in fastboot because ADB commands don't work in fastboot, only fastboot commands will. The KFU won't detect the device in fastboot because of the bootloader itself. It used to, but not anymore...likely due to an update on Amazon's part. There can be a couple of reasons why it just hangs at "waiting for device". When you see "waiting for device", you can reboot the KF and see if it detects upon rebooting. If not, you'll have to completely uninstall your drivers and try again. Even then, there's still a good chance it won't work. If not, you can reference the following thread for clues to get it working properly:
http://forum.xda-developers.com/showthread.php?t=2179748
soupmagnet said:
Okay,
Yes, it is in fastboot. ADB won't recognize the device in fastboot because ADB commands don't work in fastboot, only fastboot commands will. The KFU won't detect the device in fastboot because of the bootloader itself. It used to, but not anymore...likely due to an update on Amazon's part. There can be a couple of reasons why it just hangs at "waiting for device". When you see "waiting for device", you can reboot the KF and see if it detects upon rebooting. If not, you'll have to completely uninstall your drivers and try again. Even then, there's still a good chance it won't work. If not, you can reference the following thread for clues to get it working properly:
http://forum.xda-developers.com/showthread.php?t=2179748
Click to expand...
Click to collapse
OK.. Ive tried everything in the thread... Only thing I cant find is the android_winusb folder (Im running Win7 x64).
Also, when I look up the UNKNOWN DEVICE Hardware ID, I get USB\UNKNOWN) in device manager
RBThompsonV said:
OK.. Ive tried everything in the thread... Only thing I cant find is the android_winusb folder (Im running Win7 x64).
Also, when I look up the UNKNOWN DEVICE Hardware ID, I get USB\UNKNOWN) in device manager
Click to expand...
Click to collapse
Make sure you have the hardware IDs that I posted in that thread, in your KFU's 'android_winusb.inf' file.
You also have to find and delete the folder that gets created by KFU's install_drivers.bat. It will be in the WINDOWS directory somewhere, most likely in a hidden folder. Make sure "Show hidden folders" is enabled.
You may have to search your hard drive for any directory containing the string "android" OR for the filename 'android_winusb.inf',making sure to search hidden files and folders.
Once you have found and deleted it, reboot your computer and run KFU's newly edited 'install_drivers.bat'
Still Stuck...
OK, so, I did a CLEAN install of windows XP, installed the complete Android SDK package, then installed the modified KFU package (Added the lines of Device IDs supplied in your post on how to get it to work) and edited the install bat to install in legacy mode.
I still get an error in windows about the Kindle Fire.
I installed everything, then plugged in the kindle after turning it on. Kindle is still stuck on Kindle Fire logo (doesnt flicker or sparkle or dim or anything)... and windows says:
(In FOUND NEW HARDWARE WIZARD):
Cannot start this hardware
There was a problem installing this hardware:
Android Composite ADB Interface
This device cannot start (Code 10)
...
Thats a USB error code , maybe trying to use a different cable or use the usb ports on the back of the pc instead of the front
OMFG!!!!
I want to thank all of you for your help...
But, get this...
Apparently the kindle was waiting for me to send the TWRP package... THATS ALL!!!
I built the factory cable... proved useless for me
I went through all of my USB cables... NONE worked...
So, as a last ditch effort I thought... screw it, lets see what happens if I... (Fill in the blank)...
Tried sending the TWRP package and BAM!!!! Blue kindle...
Go figure