I am stuck with this headache and have stressed my self for hours trying to fix this so now I turn to you guys for help.
My Situation:
I had kindle to 6.2.1 then I rooted it, installed CM7.
after using it for 7+ days there is an update of CM7 by another dev. which had sound in the CM7 so I tried to flash it.
I put it in the SD card and renamed it CM7.zip from Update.zip so I flashed on Custom Recovery to flash the Update.zip later finding out that I renamed it to CM7.zip so I was stuck at Customer recovery bootloop so I enter the command to flash stock recovery to boot as the CM7 required.
so after stock recovery flash on Kindle the Kindle got stuck on the "kindle fire logo"
I think it was stuck in Fastboot.
I tried with KFU and Kindle Fire Unbrick software but the thing is NONE of them detect my kindle
I have tried soo many ways to Get my kindle detected to unbrick it but still no luck
Any help would be greatly appreciated.
Thanks
BUMP!
Still need help with a bricked kindle
BUMP!
Any1?
Kindle Still Bricked and not working >.<
Have you tried Kindle Fire Utility 0.9 to install the latest drivers? After that install Kindle Fire Unbricking Utility 0.1 to unbrick. If that doesn't work, reply with a detailed explanation of what you're seeing and what you have already tried.
This post has links to both and a good alternative option: http://forum.xda-developers.com/showthread.php?p=21232193
Good luck.
Sent from my rough sketch of a Vibrant on a brick.
Hey,
My kindle got stuck in fastboot too. It wasnt recognized by KFU and unbricking tool. Here is how I managed to recover to normal boot:
Remove the drivers in device manager and reboot your stuck kindle fire, but do not unplug it (just hold power button for pretty long time till it shuts down, then just turn it on). Windows should recognize some device. now install adb drivers and launch KFU. If it sees your fire you are good to go, if not just try changing bootmode to 4000 as if it was recognized.
BUT this worked for me. I do not know if it will work for you! I takeno responsibility or whatsoever.
Good luck sir. Do not give up
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
umarsl said:
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
Click to expand...
Click to collapse
it looks like you have a driver issue - primarily
this is what has to be corrected first
then we could see what to do
therefor some info about your os would be helpful (os/bit)
what drivers are you using ?
do you have the newest kfu available ?
if yes - moved and renamed to c:\kfu ?
umarsl said:
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
Click to expand...
Click to collapse
In my case, KFU also stated
status: offline
bootmode: unknown
adb root: No
but it still worked when I tried to change bootmode to 4000.
Also, are you sure your KF is charged enough to start? Try plugging it for a while, then recheck in windows.
b63 said:
it looks like you have a driver issue - primarily
this is what has to be corrected first
then we could see what to do
therefor some info about your os would be helpful (os/bit)
what drivers are you using ?
do you have the newest kfu available ?
if yes - moved and renamed to c:\kfu ?
Click to expand...
Click to collapse
I am running Windows 7 64bit on two of my laptops and windows 7 32 bit on my desktop.
the Kindle logo is not glimmering or flashing so it is in fastboot, I know that much.
I have tried the drivers that came with the KFU 0.9.2 (Newest, I believe)
and Yes the Kindle Fire is fully (if not mostly) charged as I had it on the charger for 6 hours last night.
and No I have not placed it or renamed to c:\kfu
I will let you know in a minute about the results
If it keeps saying Waiting for Device then it's not really in fastboot. I had a similar issue and got it solved through this thread:
http://forum.xda-developers.com/showthread.php?t=1430515
It was stuck in a boot loop and appeared like it was in fastboot, but it would hang up and not respond. You may need to install the fastboot package manually and force it into the right mode. Then you can load TWRP and put it all back together.
If ADB isn't working though, you will need to start by getting that to work. It sounds like a driver issue even though you said you worked on that. You should try the Ubuntu boot method and Firekit to install the fastboot package through ADB. Those are outlined in the link above.
got it ?
if you have a 32 bit machine available that is the better choice cause you don't have to hassle with the 64 bit drivers too
here some information that should clarify the driver things:
in normal boot the device is "android composite adb interface"
in fastboot the device is "android adb interface"
here again all the possible commands to change bootmode:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Still no results
I connected my brother's kindle and the computer immediately recognized it and when I connect mine, it doesnt work! :'(
apparently still having the driver issues :'(
any help?
I have tried the KFU driver and that didnt work
I had a similar problem while trying to install TWRP the first time via KFU except I was stuck at the yellow triangle and not the Kindle Fire screen.
First I replaced run.bat in the KFU folder with the one from this post because my Kindle was 6.2.2. Next I installed the drivers for my uknown device in device manager both by pointing the unknown device to where I saved android_winusb.inf and also ran the install_drivers.bat. I got an error saying they could not install.
Next, I followed the steps here
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
Click to expand...
Click to collapse
and when I rebooted my Kindle, it booted normally and appeared as Kindle in Device Manager. So despite KFU not detecting my device, and the drivers giving me problems, I was still able to issue the command in KFU for normal boot mode and held the power button for 30 seconds and it was back to normal. This is on a Windows7 64bit machine. I hope this helps.
Make me the third. Here is my story.
I have lots of rooted and rom'd devices so I'm agreeing that this might be device related and not the drivers? Or maybe specifically the Kindle driver? Since all my other devices work fine.
I bought my kindle and rooted it on day one 6 weeks ago using TWRP. things have been perfect on my KF. I decided to install CM7.1 yesterday morning and it was working great. I just realized I never rebooted it so what Im going to say shortly may have been bound to happen.
So last night I decided to add a google Market update per a link on XDA that stated this can be updated to my current CM7 install. After this my KF just kept going into TWRP automatically. I then decided to load my backup rooted stock room and still my KF just boots into TWRP.
Next I decided to use rootkindlefire's unroot/stock rom to 6.2.1 (drop the bin renamed to update.zip to the SD) and got a TWRP logo screen. I powered off a couple times and now I get a KF logo screen. I tried the 20 second reset and it flashes (Windows XP see the request for a USB device also), but no KF OS loads. Windows is showing Android Phone > Android Composite ADB Interface but the SDcard does not mount files.
I tried:
Kindle Fire utility and it says: Oops... something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on. Press any key to continue . . .
SuperOneClick 2.1 says device isn not found
SuperOneClick 2.3.3 just sits at * daemon not running. starting it now on port 5037 * * daemon started successfully *
Stuck on logo option for Kindle Fire unbrick says: Kindle unbrick in progress... adb server is out of date. killing... * daemon started successfully * error: device not found error: device not found Congratulations, your Kindle should be unbricked!
My Sonxy Xperia, Eris, Vibrant and LG470 all work fine when connected.
At a loss here..
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
scrols said:
Hey,
My kindle got stuck in fastboot too. It wasnt recognized by KFU and unbricking tool. Here is how I managed to recover to normal boot:
Remove the drivers in device manager and reboot your stuck kindle fire, but do not unplug it (just hold power button for pretty long time till it shuts down, then just turn it on). Windows should recognize some device. now install adb drivers and launch KFU. If it sees your fire you are good to go, if not just try changing bootmode to 4000 as if it was recognized.
BUT this worked for me. I do not know if it will work for you! I takeno responsibility or whatsoever.
Good luck sir. Do not give up
Click to expand...
Click to collapse
I went to another site and was able to get my kindle recognized by my PC (manually edited the drivers and reinstalled) and now Kindle Fire utility sees my device but KFU keeps saying these two lines when attempting to recover and root
adbd cannot run as root in production builds and
- exec '/system/bin/sh' failed: No such file or directory (2) -
So after reading and trying how others on here fixed that very same problem I deiced its time to make a post and ask for help because those other methods did not work.
Ok I did something stupid and I went ahead and did a factory reset to my kindle. Yes I know it was a complete noob thing to do and I should have known better seeing that I have rooted and flashed ROMs on all my other android devices and never once did something that dumb but I did it this time. Now I do have a back up made and had it safely stored on my PC.
Problem is that I can't get into recovery it stuck on the FFF logo and holding down the button only brings it back up. When the device restarts windows recognizes it as an unknown usb device and won't connect and Adb also wont recognize the device or show that it is connected. So now I need to ask someone who is more knowledgeable then me on what to do next. Any help will be appreciated
Ok update: Was able to solve my own problem using the Kindle fire utility and by uninstalling the drive for the kindle through the device manager, then using the drive install_drivers.bat in the KFU folder to reinstall the drivers. I next unplugged my kindle from the pc, turned it off by holding the button on the kindle in and then restarted it with the usb plugged into the pc. My Pc recognized my kindle and I was then able to use KFUs Bootmode menu and once in there used option 1. to boot it in normal mode. Hope this helps anyone who was stuck like I was. My memory of which adb commands to use was a bit rusty but using the KFU helped with that part.
I had it working about a hour ago and rooted with burritoroot, but now ADB can no longer see the tablet. Any ideas? So far I factory reset the tablet and I'm stuck. USB drivers installed, win.ini and no connection. Mass storage works but ADB is at a loss...
When I hook my phone up, ADB sees it no problem, when I hook up the Kindle, nothing.....
I'm pulling my hair out here..........
edit...........ok I'm a dumbass I fixed it by mistake.
you should try manually installing the drivers again sometimes it doesnt work all the time but if that doesnt work you should also try installing kindle fire utility and installing drivers from there
lol didnt see you awnser it yourself
I just got my KF tonight and decided what the hell to go ahead and root it. I read the information in the development thread on the Kindle Fire Utility (ver 0.9.3).
I installed the driver files on Windows 7, no problems, device manager shows my device as a Kindle and not ADB composite.
Once that was done, I started the KFU and got my command prompt stating that it was resetting ADB and waited and waited.
I then got the messages after about 5 minutes stating that the daemon had been started successfully.
I then kept waiting and waiting and waiting for around 15 minutes.
I am not a complete noob to rooting, I rooted an OG Droid and my Samsung Fassy. My question is how long is it suppose to take to get the number prompts in KFU or am I totally missing something here
Please any assistance is greatly appreciated.
It should take few seconds. Apparently, your PC configuration for USB driver is not correct.
I recommend before using KFU that you test the interface using adb. Start with adb devices command. If you get a response from KF with its s/n then you go a he'd and use KFU to root, install bootloader fff, and recovery such as cmw or twrp and finally select a ROM to install.
Sent from my Amazon Kindle Fire using Tapatalk
Well I rechecked through ADB, got this as the feedback. I uninstalled and reinstalled the drivers, device mgr still showing as Kindle USB device.
C:\Users\Ninja\Desktop\ADB>adb devices
List of devices attached
2CBC002600000001 device
Am I suppose to be seeing this output or the name of Kindle on the output?
Yes, you do have ad working.
Now you can root your KF.
Sent from my Amazon Kindle Fire using Tapatalk
the last version of kfu (0.9.3) has a small bug in run.bat
would try to use the run.bat from here:
http://forum.xda-developers.com/showpost.php?p=23536888&postcount=1007
My Kindle Fire is stuck in the TWRP boot loop with the blue and white kindle fire logo. So far I haven't been able to mount or wipe the SD card, and there is not zip file loaded onto the Kindle that I can use to restore it. I haven't been able to try adb because the Kindle does not show up under the devices when I go through the command prompt steps. I can wipe everything else and get it to boot into the Fastboot? screen (the kindle fire logo is orange and white), but my computer doesn't recognize it from that screen. Both of my computers will only recognize it as Android ADB Interface when I hit the power button to enter the boot screen. Once it leaves the boot screen it disappears from the device manager.
The kindle fire utility reads:
ADB status: Offline
Boot Status: Unknown.
When using the twrp, anything that involves writing to or wiping the sd card receives this error E:failed to mount /sdcard (invalid argument)
I am about to order the factory cable, but first... does anyone know if the cable will even help if the SD card is inacessable? Any other suggestions? Or should I begin using my Kindle as a coaster?
Kamakookie said:
My Kindle Fire is stuck in the TWRP boot loop with the blue and white kindle fire logo. So far I haven't been able to mount or wipe the SD card, and there is not zip file loaded onto the Kindle that I can use to restore it. I haven't been able to try adb because the Kindle does not show up under the devices when I go through the command prompt steps. I can wipe everything else and get it to boot into the Fastboot? screen (the kindle fire logo is orange and white), but my computer doesn't recognize it from that screen. Both of my computers will only recognize it as Android ADB Interface when I hit the power button to enter the boot screen. Once it leaves the boot screen it disappears from the device manager.
The kindle fire utility reads:
ADB status: Offline
Boot Status: Unknown.
When using the twrp, anything that involves writing to or wiping the sd card receives this error E:failed to mount /sdcard (invalid argument)
I am about to order the factory cable, but first... does anyone know if the cable will even help if the SD card is inacessable? Any other suggestions? Or should I begin using my Kindle as a coaster?
Click to expand...
Click to collapse
If you have the newest 1.4a I think you shouldn't need the factory cable. That said, I use it most of the time because it makes it so easy.
Sounds like your USB drivers are messed up.
Sent from my MB855 using xda premium
rbeavers said:
If you have the newest 1.4a I think you shouldn't need the factory cable. That said, I use it most of the time because it makes it so easy.
Sounds like your USB drivers are messed up.
I bought the Fire used thinking it would be an easy fix. I didn't have any drivers installed before using the drivers from the Kindle Fire utility. I've tried it on 3 computers using Windows 7 64 bit and Windows Vista. Same results all around. They will only recognize the Fire after I enter the boot screen, and I have to keep hitting the button to change selections from normal boot, Recovery, and Reset Boot mode. If I ever stop scrolling and let it reboot, it will disappear from my device manager until I enter the boot screen again. I get an unidentified drive under My Computer ( Q: ) but access is denied. So far I've been unable to get it to show up under devices when I try using adb through the command prompt. Could that still be a driver issue? Any other ideas? I'm about ready to use it for skeet practice!
Click to expand...
Click to collapse
Kamakookie said:
rbeavers said:
If you have the newest 1.4a I think you shouldn't need the factory cable. That said, I use it most of the time because it makes it so easy.
Sounds like your USB drivers are messed up.
I bought the Fire used thinking it would be an easy fix. I didn't have any drivers installed before using the drivers from the Kindle Fire utility. I've tried it on 3 computers using Windows 7 64 bit and Windows Vista. Same results all around. They will only recognize the Fire after I enter the boot screen, and I have to keep hitting the button to change selections from normal boot, Recovery, and Reset Boot mode. If I ever stop scrolling and let it reboot, it will disappear from my device manager until I enter the boot screen again. I get an unidentified drive under My Computer ( Q: ) but access is denied. So far I've been unable to get it to show up under devices when I try using adb through the command prompt. Could that still be a driver issue? Any other ideas? I'm about ready to use it for skeet practice!
Click to expand...
Click to collapse
Are you using Kindle Fire Utility v0.9.6? http://forum.xda-developers.com/showthread.php?t=1399889
there is an option number 6 extras, to install latest stock update zip number 7.
That should get you to Stock.
Click to expand...
Click to collapse
rbeavers said:
Kamakookie said:
Are you using Kindle Fire Utility v0.9.6? http://forum.xda-developers.com/showthread.php?t=1399889
there is an option number 6 extras, to install latest stock update zip number 7.
That should get you to Stock.
Click to expand...
Click to collapse
That's the version I'm using. I tried that option but it failed because it couldn't access the sd card. Ive tried every option in the Kindle Fire Utility and the Kindle Fire Unbrick. I've ordered the factory cable to try that. I don't know of anything else to try.
Click to expand...
Click to collapse
Kamakookie said:
rbeavers said:
That's the version I'm using. I tried that option but it failed because it couldn't access the sd card. Ive tried every option in the Kindle Fire Utility and the Kindle Fire Unbrick. I've ordered the factory cable to try that. I don't know of anything else to try.
Click to expand...
Click to collapse
Hopefully your not in the right mode to flash if not....
Doesn't sound good check out this thread http://forum.xda-developers.com/showthread.php?t=1651413
about half way in.
Click to expand...
Click to collapse
Did you get your cable?
Any Luck with your Fire?