Related
Hello all,
I need some help and guidance in fixing my Kindle Fire. Some background:
My Kindle Fire was on 6.3.1 when I rooted it, no custom roms, just root so I can get Google Framework on it since I use Google Docs and the Google Market. After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
I had FFF and TWRP on my Kindle Fire as well, running Windows 7 64bit Home Premium
After much searching, every unroot guide kept pointing me back to flashing the stock rom. So I downloaded the latest update.zip through KFU, booted into TWRP, wiped, installed the update.zip, and rebooted.
After that, I hit the Kindle Fire logo, static, and it hangs there. I power off and on, still hangs. I don't have the blue/white FFF recovery anymore so booting into recovery wasn't an option. I then connected the Kindle to my computer, opened KFU, and tried to change the boot option through option 1, and every time I change it, Fastboot, Normal boot, etc. it sends the command, Kindle reboots, but then hangs again on the static logo.
I tried reinstalling FFF and TWRP through KFU to try and reflash, but it shows as preparing, then waiting for device, and nothing. Again, just hanging.
I even tried the manual shell commands I've seen around the forums and in the Kindle Fire for Beginners Guide, but I keep hanging on "Waiting for device" in the cmd prompt.
I don't know what else to do and I'm becoming more confused with the different types of issues that everyone is reporting, with each one have one detail different from my situation. I had no custom roms, just a root, and it seems I may have flashed a bad stock rom.
Any help is greatly appreciated. I apologize if this was solved somewhere else, but I searched numerous threads and guides, but they all dealt with something going wrong with a custom rom or people getting to the animated Kindle Fire logo, where as mine is just static.
Again, thank you for your time.
Sounds like it's stuck in fastboot bootmode to this noob. I had the same problem at one point and used command line to fix with the simple bootmode switching commands - can't recall if I used fastboot or adb tools..but either should work. And if I'm reading your post right, you've tried these so this is likely above my meager skill level, heh. You are handling it better than I did, I might add.
If I may point out where you went wrong:
Mattamus Prime said:
After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
Click to expand...
Click to collapse
There are apps in the Google Play store that will temporarily remove your root status so you are able to use services that detect and shut down when root is detected. OTArootkeeper.apk is one that I've heard of.
And don't ever chose to lose fff once you have that as this is your lifeline to unbricking.
Hopefully someone with better chops than I on this will post up - continue with your patient reading and take a little comfort that this is most probably fixable.
First off, I applaud you for trying to figure out and fix the problem yourself using the guides available. Thank you. The information you provided will go a long way to getting the help you need.
So far it seems you've done everything right, but to be sure, you should check to make sure your drivers are in order (most likely the problem). The second post of the Beginners Guide will help you with that.
Once you have done that and you still can't change your bootmode, try using recovery to flash a custom rom. It's possible the stock boot image you have has been corrupted. You can use the "mount" function in recovery to push another rom to your sdcard. If that works you can stick with a custom rom like MoDaCo. It's the same stock stock interface with Google apps and services installed and you don't have to worry about OTA updates. OTA Rootkeeper will let you easily switch between "rooted" and "unrooted" so you can take advantage of Amazon's VOD.
And if you still want pure stock you can d/l a new copy of the update and try again.
Thanks for the suggestion. I did try OTA Rootkeeper, but when I went into my Instant VOD, it still had the buttons grayed out. I tried temp unroot, reboot Kindle, and still grayed out, so I assumed Rootkeeper wasn't working for me, thus, the looking for the unroot tutorials.
A little bit of extra information, when I hook up my Kindle Fire, my drivers says Android Composite ADB Interface. When I try to switch to Fastboot to have it switch to Android ADB Interface, it doesn't switch. It just stays as Composite.
Thanks again.
soupmagnet said:
So far it seems you've done everything right, but to be sure, you should check to make sure your drivers are in order (most likely the problem). The second post of the Beginners Guide will help you with that.
Click to expand...
Click to collapse
I followed the advice in the Beginners Guide, uninstalled whatever drivers I had, rebooted my comp, then installed the ones that came with the KFU download.
Are there any other drivers I should be looking for?
Also, a little bit of more information, I tried switching to Fastboot through KFU, received some messages to the effect of "system/some file name file not found (2)", (I apologize for not being specific, typing from memory), it then reboots my Kindle Fire, then I execute the commands:
fastboot getvar product
After that, it just says <waiting for device>
In fact, after any command I do in cmd, I get that message. So I believe it may be a driver issue, like was suggested, or my Kindle isn't far enough into the boot process to be found.
It definitely sounds like a driver issue. Keep working on your drivers.
If that doesn't work, you can try it on a different computer OR set up a Linux LiveUSB for issuing adb/fastboot commands.
FIX for Kindle stuck on logo
Finally I FIXED MY KINDLE FIRE!!!!
Issue : Kindle Fire stuck on 'Kindle Fire' logo and never moves after that.
Hello All,
Just like others in here, even I tried to upgrade to new version of Android on my kindle and I messed it up very bad.
I have read a post where, some-one just updated that it is because we have enabled fast boot on it and we need to move to regular boot.
However, none of the solutions suggest on this website worked for me (am not saying my friends are wrong in here).
Finally the work around that WORKED for me, and am sure this will be help you all.
When you are wiping/erasing the data/SD card, please do not wide the ROM. If you delete the ROM - Booom!!, you are cutting off the branch yo are
sitting ON )
Now if you have already done that.. please follow the steps.
You have intall/upgrade to a new version of Android.
Make sure you have the TWRP 2.1.x or 2.2.0 installed << which you will have, using that only you wiped off your kindle )
Now download the latest version of Andriod Jelly Bean and Google app on your computer from the following link
http://forum.xda-developers.com/showthread.php?t=1778010
1. Now, boot ur kindle into recovery.
2. Connect your kindle to your computer, if the computer recongnise your kindle paste both files onto kindle, and move to step 6
3. If your kindle is not recognized (like in my case), go to mount option in recovery
4. Choose mount USB
5. Kindle will be recognized in computer, and copy the files.
6. Disconnect Kindle from the computer
7. Wipe data/factory reset
8. Wipe cache
9. Wipe dalvik
10. Install ROM <install Andriod Jelly Bean> Do not install Google Apps
11. Reboot
Once you do a normal reboot, your system will boot into Andriod Jelly Bean edtion. Go to file manager and reach out to Google Apps and install the
application and reboot.
Yes!! you have the complete recoved Kindle
Only known issue - Your battery bar will not move when it is charging (but actually it is charging).
#####################################################################################################
MattamusPrime said:
Hello all,
I need some help and guidance in fixing my Kindle Fire. Some background:
My Kindle Fire was on 6.3.1 when I rooted it, no custom roms, just root so I can get Google Framework on it since I use Google Docs and the Google Market. After about a week or so, I decided I wanted to go back to an unrooted Fire so I can get access to my stock book reading app and Instant VOD.
I had FFF and TWRP on my Kindle Fire as well, running Windows 7 64bit Home Premium
After much searching, every unroot guide kept pointing me back to flashing the stock rom. So I downloaded the latest update.zip through KFU, booted into TWRP, wiped, installed the update.zip, and rebooted.
After that, I hit the Kindle Fire logo, static, and it hangs there. I power off and on, still hangs. I don't have the blue/white FFF recovery anymore so booting into recovery wasn't an option. I then connected the Kindle to my computer, opened KFU, and tried to change the boot option through option 1, and every time I change it, Fastboot, Normal boot, etc. it sends the command, Kindle reboots, but then hangs again on the static logo.
I tried reinstalling FFF and TWRP through KFU to try and reflash, but it shows as preparing, then waiting for device, and nothing. Again, just hanging.
I even tried the manual shell commands I've seen around the forums and in the Kindle Fire for Beginners Guide, but I keep hanging on "Waiting for device" in the cmd prompt.
I don't know what else to do and I'm becoming more confused with the different types of issues that everyone is reporting, with each one have one detail different from my situation. I had no custom roms, just a root, and it seems I may have flashed a bad stock rom.
Any help is greatly appreciated. I apologize if this was solved somewhere else, but I searched numerous threads and guides, but they all dealt with something going wrong with a custom rom or people getting to the animated Kindle Fire logo, where as mine is just static.
Again, thank you for your time.
Click to expand...
Click to collapse
K_Krish said:
Finally I FIXED MY KINDLE FIRE!!!!
Issue : Kindle Fire stuck on 'Kindle Fire' logo and never moves after that.
Hello All,
Just like others in here, even I tried to upgrade to new version of Android on my kindle and I messed it up very bad.
I have read a post where, some-one just updated that it is because we have enabled fast boot on it and we need to move to regular boot.
However, none of the solutions suggest on this website worked for me (am not saying my friends are wrong in here).
Finally the work around that WORKED for me, and am sure this will be help you all.
When you are wiping/erasing the data/SD card, please do not wide the ROM. If you delete the ROM - Booom!!, you are cutting off the branch yo are
sitting ON )
Now if you have already done that.. please follow the steps.
You have intall/upgrade to a new version of Android.
Make sure you have the TWRP 2.1.x or 2.2.0 installed << which you will have, using that only you wiped off your kindle )
Now download the latest version of Andriod Jelly Bean and Google app on your computer from the following link
http://forum.xda-developers.com/showthread.php?t=1778010
1. Now, boot ur kindle into recovery.
2. Connect your kindle to your computer, if the computer recongnise your kindle paste both files onto kindle, and move to step 6
3. If your kindle is not recognized (like in my case), go to mount option in recovery
4. Choose mount USB
5. Kindle will be recognized in computer, and copy the files.
6. Disconnect Kindle from the computer
7. Wipe data/factory reset
8. Wipe cache
9. Wipe dalvik
10. Install ROM <install Andriod Jelly Bean> Do not install Google Apps
11. Reboot
Once you do a normal reboot, your system will boot into Andriod Jelly Bean edtion. Go to file manager and reach out to Google Apps and install the
application and reboot.
Yes!! you have the complete recoved Kindle
Only known issue - Your battery bar will not move when it is charging (but actually it is charging).
#####################################################################################################
Click to expand...
Click to collapse
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
me too
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
I am stuck at the very same place you are. I was in an endless bootloop after trying to flas back to the Stock Amazon ROM using TWRP. Once i got the drivers sorted out and ADB could see my device i used KFU to "Install permanent Root with Superuser". The KF went to reboot into fastboot and the screen said "waiting for device" for about ten minutes. Now the KF is stuck at the white and orange "kindle Fire" boot logo. Windows will no longer see the KF as an android device. It only shows up as an "unknown device" in the device manager.
Try this
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
Ok, I dont know, how to fix this (as I was not in this situation). Try following the steps - Download update.zip through KFU. Connect your Kindle to PC and install the android driver. If your PC detects the kindle copy update.zip file to kindle and try to install that.
sounds like a job for this http://forum.xda-developers.com/showthread.php?t=1392693&highlight=info
dynomite16 said:
I think twrp got deleted when I reinstalled the kindle update. So I can't do what you said. When I turn my kindle on it gets stuck at that kindle fire logo. I can't go into recovery or anything. I can't re install twrp because it KFU says my kindle in online but when i click install twrp it says waiting for device.
Click to expand...
Click to collapse
Im in the same boat you are. I have tried everything stuck on same logo device is recognized in devices as android phone and adb interface but cannot connect to unbrick utility or KFU and doesnt show as a drive either. tried to search devices in cmd using fastboot commands and nothing shows either. I decided to purchase a factory cable today on ebay. Keeping my fingers crossed because after reading everything I could find I think it is my only option.
No, your problem is as "simple" as fixing your drivers so the computer can communicate with the device through adb and fastboot. KFU relies on those two tools to do pretty much anything. Unfortunately, Windows is stupid and is not very effective when dealing with certain USB devices.
In order to, say, install TWRP, you need adb to change the bootmode to accept fastboot commands, and use fastboot commands to overwrite the recovery partition. In the process of going between different boot modes, Windows had a hissy fit and decides not to communicate with the device at all. Hence the need to fix/reinstall the drivers. It doesn't always work out that way and you get stuck where you are right now. A factory cable will put you in fastboot, but it wont make Windows communicate with the device. You can continue to fight with Windows drivers and hope to get lucky, or you could try other, more effective options...
http://forum.xda-developers.com/showpost.php?p=30629067
omg .... I survived a bricking. Soupkit saved me!!!
Somewhere on the many tabs I have open, as I frantically search for ways to unbrick my Kindle fire... I run into " SoupKit" for Linux ... install it... mess around with the Bootloader .. change it to 4002 I believe the value was ... my Kindle that I've been working on for literally 6 hrs is back on! ... now on the figuring out how to root it / remove demo software. SOUPKIT!
E]
Hi guy,
I got this problem. When I plug my Kindle Fire into the laptop with the cable, of course I switched to USB debugging already, there is Android ADB Interface in my device management. However, when I start cmd and type adb devices --> there's no devices attached to my computers.
I re-plugged my Kindle Fire with the cable and click on turn on USB storage on the screen of KF, but it's still the same. There's no devices attached
I tried to re-run the install_drivers.bat (from KFU) but it has no results. It's still the same.
I think I have nothing wrong with the driver installation. It's kinda fine and I still can copy data in and out. However, I still tried to re-run the install_drivers in KFU and this is what I have (I rejected my Kindle Fire before re-running as your tutorial)
https://www.dropbox.com/s/sk84tqhtwba7jz7/KF_Noti.jpg
I tried to use some commands and this is the result
https://www.dropbox.com/s/u85xoupskedmaui/KF_cmd.jpg
I dunno what to do right now to install a new ROM when it's not connected. Previously, everything was fine.
What can I do now? I need to install a new custom ROM.
Also make sure your not using a 3.0 USB port they have fast boot communication issues but likely you need to uninstall you driver then plug your kindle in and let them reinstall
I tried to uninstall it and plug it to computer to reinstall it manually. However, when I plugged it to computer, it automatically receives the driver that I had just uninstalled.
I tried to make an overlapping driver, hence I continued to reinstall manually but it is said that it is working properly.
For your further information.
1. Whenever I plug in my Kindle Fire, this is the notification that I have. I think this is an error
https://www.dropbox.com/s/h0mhaiklthdfo01/KF_NoDisk.jpg
2. This is an overlook at my Kindle Fire driver on my computer when I plug it in and set up the debugging
https://www.dropbox.com/s/nym7n0ygo2sfqay/KF_General.jpg
The driver shown in your picture is the fastboot driver. Generally indicating your device in fastboot mode for kfu it needs to read android composite adb interface . So if your device is in normal bootmode then this driver is incorrect.
Yep! I have the same thought with you. I think there is a problem with my driver. But what am I supposed to do right now?
I did uninstall and re-install driver, both manually and automatically. ( Is there anything that I can try now?
P/S: I still can copy data between computer and Kindle Fire. So I don't know what the hell is going with my driver
Here is an excellent tutorial post #2 on drivers maybe it will be of some help to you http://forum.xda-developers.com/showthread.php?t=1552547
I did follow this tutorial, as the first step to start my Kindle Fire. I think I would try it again.
I would love to have your teamview. Thank you so much
Sorry for double-post, I posted in wrong section, it's hard to define whether this is really a quesiton, but here goes:
Ok, so I had TWRP including FFF installed, as well as all the other features that comes with kindle fire utility, when I decided that I wanted to restore to stock firmware.
I placed the update.bin in kindleupdates folder on the Kindle itself, and launched TWRP Recovery to install the rom/firmware.
When it was done installing, I was such a nutjob not thinking, that I decided to also delete everything (system, sdcard, cache, dalvik-cache), as well as to tell it to restore to factory settings, where I immediately after told it to reboot. Totally dumb, I know it, so now it's stuck at the "original"/orange Kindle Fire-logo, and just hanging there (i'm able to turn it on/off though), hence it can't restore stock firmware since I deleted everything off the kindle after I installed that stock firmware. It doesn't even have TWRP anymore (boot options doesn't appear when turning the kindle on.)
I also tried to connect it to the USB-port on my PC, (already have drivers installed), but it just gives me the "badom"-sound implying that a USB has been connected, nothing else. I can't even access the Kindle as an external storage device anymore now.
HELP!
PS: I'm running Windows 7 x64!
You need a factory cable...
http://forum.xda-developers.com/showthread.php?t=1668159
Jus check if our kindle is coming up under the USB devices as a composite USB device..if so uninstall the driver and reconnect the kindle..
It shd get detected under other devices..install the drivers manually by clicking dont install and use have disk and get it detected as a android phone or android composite interface..
If that works u can use adb commands and try..this might help u recover or kindle
Sent from my MB526 using Tapatalk 2
Hey I'm a brand new member so I apologize in advance if my problem has been solved already, however, I could not find anything on any of the threads. Okay so I am severely confused right now. I have had my Kindle Fire for almost a year now and this problem has never occurred. Ever since I got my Kindle I have been experimenting on it. I rooted it and have flashed many different custom roms. I had been using TWRP Recovery 2.0 for a long time and when I found out that it was outdated I updated it to the new 2.2.1.1 version...Everything seemed to be working perfectly until I tried mounting USB storage in the new TWRP...It did not work. My computer wouldn't recognize it. I kind of just let this slide since I figured I wouldn't need to mount USB storage in TWRP unless it was an emergency. A while later I switched back to the Kindle's stock rom. That's when I noticed that it would not mount...Not only was TWRP not mounting, but it was my Kindle altogether. I deleted all drivers that had any thing to do with Android from my computer. After restarting both my computer and my Kindle I tried mounting again...Nothing. The drivers weren't even reinstalling. To test wether this was a problem with my computer or my Kindle I got my brother's Kindle Fire (Never had any tweaking done to it) and mounted USB storage. It installed the drivers and mounted just fine. I then plugged my Kindle back in and it mounted just fine also. I thought I had solved the issue, but about an hour later I tried mounting my Kindle again and nothing happened. My brother's Kindle will mount (Actually there are a total of four Kindles in my house all of which have not been tweaked except for mine) but mine won't do anything. As a last resort I deleted EVERYTHING with TWRP and flashed the Kindle Fire 6.3.1 update.zip. My Kindle is now true factory default (no root, custom recovery, etc...). I thougt for sure this would work but IT STILL WON'T MOUNT USB STORAGE!!! When I plug my Kindle in and go to "Devices and Printers" it recognizes my device as a "Kindle" but I just cannot get it to mount! I am now stuck with a Kindle that cannot be re-rooted or anything due to the fact that it cannot be recognized with ADB. Sorry for the long post...I am just trying to give as much information as possible. By the way I am running Windows 7 and my Kindle is the only one that will not mount which makes this problem have nothing to do with drivers or my computer. Any help is appreciated. Thanks.
Wheww okay well try a factory reset this will wipe your sdcard as well. It should resolve most your problems. There are multiple things that can cause this to happen but one thing that really comes to mind. Are you ejecting your kindle before hitting the disconnect button? Just a wild guess but failing to do so can cause this disorder the very next time you plug it in. Something that could resolve minor sdcard issues is
Code:
fastboot oem format
don't let this make you to crazy yet RC soupmagnet should be releasing something very soon that will solve the majority of SD card mount problems hint hint . You will need to reroot and flash a custom ROM on it to have success though. So if nothing works hang tight and stay tuned.
This might help
http://forum.xda-developers.com/showthread.php?p=33109015#post33109015
Thepooch, no I had not been ejecting it before disconnecting. I'll do that from now on. Also commands do not work because my computer doesn't recognize my Kindle as either a storage device or an ADB device, and what does it mean what it says "fastboot not found"? I made sure I have the fastboot.exe in my ADB folder...Soupmagnet, I can't get those commands to work since I'm no longer rooted and my computer doesn't recognize me...
Nihilian said:
Thepooch, no I had not been ejecting it before disconnecting. I'll do that from now on. Also commands do not work because my computer doesn't recognize my Kindle as either a storage device or an ADB device, and what does it mean what it says "fastboot not found"? I made sure I have the fastboot.exe in my ADB folder...Soupmagnet, I can't get those commands to work since I'm no longer rooted and my computer doesn't recognize me...
Click to expand...
Click to collapse
Have you installed your adb drivers?
soupmagnet said:
Have you installed your adb drivers?
Click to expand...
Click to collapse
Yeah I downloaded the newest Kindle Fire Utility and installed thoose drivers. When I plug my Kindle in and go to "Device Manager" it lists it as an android phone with ADB Interface. If I plug any other Kindle in then it installs new drivers and doesn't list the ADB Interface. Is this normal?
Nihilian said:
Yeah I downloaded the newest Kindle Fire Utility and installed thoose drivers. When I plug my Kindle in and go to "Device Manager" it lists it as an android phone with ADB Interface. If I plug any other Kindle in then it installs new drivers and doesn't list the ADB Interface. Is this normal?
Click to expand...
Click to collapse
I don't use Windows so I couldn't tell what's normal for that OS.
Use the tutorial here to confirm your drivers are installed properly. Then Shift + right-click on your KFU "tools" folder with adb.exe and fastboot.exe, and select "Open command window here". Enter your adb or fastboot commands there and see how it goes. Start with "adb devices" to see if you are connected. If not, reinstall your drivers and try again.
Some ROMs have different product IDs than the stock OS so you may want to look into that if you are using a custom ROM, and edit your androidwinusb.inf accordingly. I know some JB roms have a PID of 0004 instead of 0006.
If for some reason Windows refuses to cooperate, you could always set up a Linux LiveUSB and get it done a lot easier.
Okay so I've been fiddling around with stuff. I completely uninstalled all Android drivers again then restarted my PC and Kindle. This time I plugged my Kindle in and it installed the correct drivers. It mounted USB just fine. When I tried reinstalling the ADB drivers that came with Kindle Fire Utility it erased the Kindle's normal drivers, so now it won't mount anymore...at least I know that it is a driver problem and that my Kindle doesn't need to be repartitioned. I'm really getting sick of Windows and its annoying drivers...Any ideas on how to get all the drivers to work? If not I think I might just install Ubuntu and screw the need for drivers.
Sent from my M886 using xda app-developers app
If you run the driver bat packaged with kfu with the device plugged in sometimes it will waste the mass storage drivers. It`s always best to run it then plug the device in and see what windows decides to install. Unplug, replug, unplug, replug as well as try this while in recovery because it will also attempt to install the drivers as well in recovery.
Thepooch said:
If you run the driver bat packaged with kfu with the device plugged in sometimes it will waste the mass storage drivers. It`s always best to run it then plug the device in and see what windows decides to install. Unplug, replug, unplug, replug as well as try this while in recovery because it will also attempt to install the drivers as well in recovery.
Click to expand...
Click to collapse
Sweet. I tried it and now everything is working perfectly. Thanks for your help guys.
Nihilian said:
Sweet. I tried it and now everything is working perfectly. Thanks for your help guys.
Click to expand...
Click to collapse
I downloaded the lates kindle fire utility and I enabled debugging, I can see my files but when I run the utility file the adb says offline. I cannot figure it out. : (
So, I tried searching for days on how to fix my problem.
A little while ago I rooted my Kindle Fire, and it was great. Then I did something. Not sure exactly what. But It ended up just doing nothing. When I boot up the Kindle it shows the blue and white Kindle Fire logo. Nothing else past that (unless I go to recovery.) Now, my computer doesnt recognize it anymore, even after doing most of the driver updates that people on here have said to do.
I need help, basically, getting it back to normal, so I can give rooting a try again. Now that I know what exactly I am dealing with, I can do this and not screw everything up.
First, the computer says the driver is installed, yet it doesnt recognize it.
Second, (before the driver mishap) KFU said it was connected but the adb was unknown.
Third, I have CWM and I tried to flash the normal Amazon update to bring it back, and it says"it cant open it (bad)".
Now, I would really like some help with this. I'm just at a complete lost.
Now should I put that into command prompt in the adb part? because it just says fastboot is not recognized.
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Now its just not connecting to the computer. I installed Android sdk and everything and its just not working. It says the driver is installed but there was an error because a problem had occurred. Any help? :crying:
As soon as you get tired messing with drivers you can move on to something that works http://forum.xda-developers.com/showthread.php?t=1850038
ManofFishFry said:
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Click to expand...
Click to collapse
I hope u r on windows PC..
first after u set up adb, make sure u install adb drivers that came with kindle fire utility with ur kindle fire unplugged..if u had plugged in kindle fire while doing that, go to device manager and uninstall that device and its driver software and start up from beginning..
keep kf unplugged and install driver..u dont get usb debugging option in stock kf rom..its enabled if u have installed the drivers properly..ur kindle fire appears as android phone in device manager if everything u hav done is correct..
then boot up ur kf..that blue and white kf logo is of firefirefire bootloader..i hope its v1.4a and u see it on right top of the screen..if its stuck there then open command prompt as administrator on ur pc..connect ur kf to pc..type in to cmd
Code:
fastboot devices
if u see something under list of devices attached that will be ur kindle fire(unless some other android device is connected in fastboot mode lol)
Because kindle fire, as far as i know, can only boot into 3 bootmodes(normal, recovery, fastboot) unless u have altered the partition table to install different roms and multiboot ur kindle fire..
if fastboot command is not recognized, try setting the path to where fastboot.exe is present in KFU folder
alternatively u can go to folder where fastboot.exe is located and right click while holding shift and selecting 'open command window here' and fastboot needs to firefirefire bootloader to be installed on ur kindle fire..
also u can try this..
JUST GO TO RECOVERY..twrp has always been a better recovery software than cwm based thing available for kindle fire at least for me..if u go to recovery, ur kf will definitely show up as an adb device..u can change the bootmode using this..just type in:
Code:
adb devices
if ur kf is seen as in recovery then type this in cmd
Code:
idme bootmode 4000
reboot
just report if this worked..
okay well, I deleted all the drivers and started from the beginning. Yet, after running the install_driver.bat I plugged my Kindle in and it still says device not recognized. Now, you how can get adb working? It is coming up as unknown device. Its just seeming like theres something wrong on the kindle part. But hey, what do I know. haha
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
But doesn't that require linux? I have windows 7. Is there something like that for windows?
Thepooch said:
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
This is what I get when I try to install the driver....
To run soupkit all you need is at least a 2 gig usb flash drive ubuntu 12.04 32 bit and universal usb creator. By the way your problem with the driver is you (or how you`re going about it), You would trip if I got on your computer and got it to work or could at least tell you why its not working. that`s why I suggested soupkit if you would of actually read the information I gave you, I wouldn`t have had to tell you twice and you would know that to use it it`s not required to be installed on your computer. But hey catch me online I can either help you fight through windows crappy drivers or help you set up soupkit I`m always game for a challenge When updating the driver you need to point it to the 32 bit version of the driver for instance on my computer it`s located here C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers. After it`s ran unplug and replug device if that doesn`t work power off and power on while connected this generally does the trick when windows finally catches on it will install android adb interface, this is the fastboot driver (if you`re stuck in fastboot). Then select option 1 in KFU for changing bootmodes, then option 1 for normal if it does nothing power off and power on while connected it should then detect the kindle and reset the bootmode to normal. Pm me later I will be online all evening and most every evening I will help you sort it out.
Josepho1997 said:
Whoops! Somehow my post was posted twice. I didn't even get to see your reply. Sorry!
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
this is what I get when I try this... (btw im working with firefirefire. its got the blue and white kindle fire.)
Why don't you let me take a look?
Dark__king said:
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
Click to expand...
Click to collapse
Yes soupkit can fix mounting problems.
This is a very interesting issue with this Kindle windows detects it as unknown usb device, drivers are installed properly from what I can see. Ubuntu with soupkit ran on it fails to detect it in recovery or fastboot. multiple cables tried, lsusb doesn`t show the device connected. I really think this one the computer is the problem, because it`s the only unchanged variable.
Firekit may be the only option if Linux won't detect the device. Before doing that, make sure a USB 3.0 port isn't being used and try a fresh install of Linux to be safe. Otherwise, it seems putting it in USBboot is the only option for getting Linux to detect.
I'm not exactly sure what causes the unknown device error, but it almost always means there is something wrong with the bootloader, and it seems as though Windows might be the main culprit. Not sure why exactly, but it may be similar to the problem soulweeper51 had. Possibly a hardware issue involving the computer's USB port or the motherboard itself.
@ManoFishFry has doomlords cwm recovery and he flashed JB at first I thought it was an issue with cwm not being detected but the fact that it`s not detected in fastboot raised my eyebrows. The bootloader appears to be functional but I cannot rule out any minor state of being broken in another fashion when lsusb returns null. The computer doing the work had never been used prior to the incident so driver install didn`t take place till after the fact. The usb ports are all either 1.0 or 2.0 no 3.0 ports are being used. An alternate computer would be nice to rule out the computer itself @ManoFishFry only has a dinosour of an xp machine as alternate use of is not possible yet, not that it would even be possible to install drivers because of the typical unsigned driver failure of xp and booting ubuntu isn`t happening at the moment on this machine.
I'm willing to bet it is the bootloader.
Just USBboot and get it over with.
We did try usb boot once but it didn`t work will keep trying.