Related
I don't want to bother you with stupid threads and things like that, but I've used the search function on XDA and I'm still lost on this really small problem - my Kindle Fire is not being recognized anymore in ADB.
See, a long time ago (few weeks) I rooted my KF and installed Android Market, whatever. Never installed a recovery or custom ROM. Everything was ok until I tried to install TWRP using Kindle Fire Utility.
While trying to install, I got the famous "adbd cannot run as root in production builds". So I thought it was something with my drivers. Ok, then I installed the drivers that come with KFU - just to screw with everything. My Kindle Fire stopped being recognized by ADB.
I tried: (1) uninstall the drivers and install from KFU again. (2) uninstall the drivers and install the drivers I got from the video-tutorial (the famous one). (3) factory reset the kindle fire and do all the drivers install again. (4) hold the power button 900 seconds to reset the kindle fire and install the drivers again. (5) finally install the drivers on ANOTHER computer (running WinXP instead of Win7) and plug my factory reseted KF.
I gave up.
I don't know why my Kindle Fire isn't recognized by ADB on any computer at all. I thought it was my laptop, but then I tried the same steps I did at the first time using a Windows XP and no good. I don't know.
Can someone help me? Thanks a lot.
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
or you can try this solution:
http://forum.xda-developers.com/showthread.php?t=1430038
b63 said:
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
Click to expand...
Click to collapse
Tried that and didn't work.
I'm going to wait a little more before using Linux, I really wanted to do this using Windows only.
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
b63 said:
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
Click to expand...
Click to collapse
Right now my KF is normally booting into stock ROM and stock everything.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Thanks for your support.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
Click to expand...
Click to collapse
xp will be the better choice cause you don't have to hassle with 32/64 bit drivers and the uac (user access control)
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Click to expand...
Click to collapse
add it in another line
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Click to expand...
Click to collapse
seems that the patched version (the whole thread) is deleted - you will have to do it by yourself - take the original from the dev section and:
http://forum.xda-developers.com/showthread.php?t=1454913
The issue persists. I've seen that other people are having the same issue. The device got "unrooted" by unknown reasons and then it's invisible to any adb. As I'm writing to you right now, I'm trying the adb on my brother's Ubuntu. I've tried other solutions using linux but without success.
I'm running out of options here.
I'll admit that I haven't tested the last link you sent, but I can't see how that can change the way adb works on my device. Anyway I'll try that tomorrow.
in the meantime br3 is out - if you use kfu you will have to use an updated run.bat: http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
but you'r right - that will not change the communication
firekit http://forum.xda-developers.com/showthread.php?t=1430038
is worth a try cause linux don't use drivers to communicate
only needs some entries which are included in firekit
maybe try an other cable ?
really running out of ideas at this point ...
I got the same problem.
If you can fix it, please show me how, thank you.
c:\KindleADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
c:\KindleADB>
Just a quick idea. Have you tried the attach the kindle to a different USB port? I had the same issue until I used a different port. The front ports on my desktop are totally fubar, but the port where my mouse was worked when 4 out of 6 ports did not. This for me is probably a hardware problem, but it may help someone.
Sent from my Kindle Fire using Tapatalk
I am having the same exact problem as the OP and I truer everyway to root it and install the drivers but its still not recognized by adb
Its seems i should give up
Similar problem with cm9, and fixed
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Push push push it
tried all the steps. and still nothing. dont know what im doing wrong. starting to get pissed. any help would be great, thanks
Save my KF
sudogeek said:
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Click to expand...
Click to collapse
Could you help me to fix same problem with window. My PC alway, automatic recognize my KF as normal disk driver. I try to make a factory cab but not success .
Thanks.
Edit android-path.sh
1. On my Mac I opened System Profiler, then checked Hardware > USB > and 'MyDeviceName' (for me its: LePan Tablet PC)
2. Opened this file with a text editor: /Users/MyName/.android/android-path.sh
3. Added a new line in this file with the tablet Vendor Id, for example:
0x22a4
4. Executed: adb kill-server
5. Executed: adb start-server
6. Finally adb devices is showing:
List of devices attached
0163AE9D0801F02C0C280002 device
Bricked?
I think I'm having the same problem, or at least a very similar one.
Using windows XP. I got the drivers working, plugged my kindle into the Kindle Fire Utility, and ran option 2, which seemed like it was the option to create a backup in case you bricked your kindle. It ran, showed up on the Kindle screen, and did it's thing without a problem.
Then, when the kindle rebooted, I got the yellow-triangle-fire symbol. It says 'press power button for recovery', but pressing the power button does nothing. Holding it down for a long time shuts the kindle down, but pressing it again brings it right back to the yellow-triangle-fire symbol.
So I uninstalled the drivers from Windows XP (as another thread mentioned). I now have two ways that I can think of to install the drivers. Using the KFU, I get the "unsigned drivers" shutdown even after I went into the Driver Signing menu and chose "ignore and install regardless".
The other option I have is to install the drivers that I downloaded manually -- the same ones that worked in the first place. Problem with that is that I go through the entire process, selecting the directory the drivers are in and whatnot, and the only thing that happens is I get an error that says "These drivers aren't the drivers for your hardware" or something similar to that.
So neither of my options allow me to actually install drivers for my Kindle Fire, and my Fire itself is in a recovery loop. All of the tools that are supposed to address the recovery loop require drivers, so I seem to be up a creek without a Fire.
Any ideas?
Okay, to enter recovery...When you see the yellow triangle, hold the power button until it turns orange then release. It shouldn't take more than 10-15 seconds. If you still can't get into recovery, reinstall it.
For your drivers...uninstall completely and delete them if you're using Win7. Then reinstall using one of the previous methods.
The power button doesn't do anything when I push it. It stays bright green until the kindle fire shuts down. I'm not sure what "reinstall it" means, sorry, n00biness.
The drivers (winXP as mentioned) I've uninstalled, but I can't reinstall. One option says "unsigned drivers" and the other doesn't recognize the device as a Kindle and thus quits the install with a "this is not an appropriate driver for your device" message.
Thanks for trying, though! I appreciate your time and effort.
My girl got a Kindle Fire and wants Jelly Bean on it. I plug it into the laptop, Windows start to look for drivers, can't find them. So, thru KFU I install the drivers, open KFU, device is not showing. I open adb, run adb devices, blank. Run adb usb devices,, device not found.
The kindle will say that its connected to the computer and I can transfer files. But windows will not show an external device is attached. So, I go to Device Manager, its an "unknown device". So I looked through post after post, finding out that I need to edit the adb_usb.ini file. Problem is, I can't get to it......
I'm not a noob when it comes to computers or android, but this has me lost......
Your GF wants too much!!!
I had same problem. Errore was plug first kindle then install kfu with drivers. Remove all drivers you installed. Now install drivers provided with kfu. Make sure SDK and java is ok. Then plug kindle.
Sent from my Amazon Kindle Fire using xda app-developers app
smsrat84 - when you plug KF into USB and Windows starts to scream about new unrecognized device, choose an option to install drivers manually from a specified location, and choose {KFU_HOME}/drivers/kindle - KFU will see it after that. Then install FFF, TWRP with KFU and so forth.
Try using Linux (yes I said the dreaded 'L' word ) because apparently it's not as fiddly with drivers as Windows is.
Personally, I used Mac and it was plain sailing all the way. No drivers, everything just worked first time [Just make sure you're careful, nothing is foolproof ]
jji7skyline said:
[Just make sure you're careful, nothing is foolproof ]
Click to expand...
Click to collapse
touché
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. : (
I have here Kindle Fire rev. 2.
I want to root it.
I downloaded Kindle Fire ADB drivers.exe , and installet it.
Run cmd.exe goto adb Folder type "adb devices" and adb server cant finy my kindle...
My Smartphone is Visable in ADB.
i have here 3 Win 7 PC´s and Win8 Notebook (all x64 OS) . I Try´d it on other PC, dnot work. I installed extra win 7 32 bit, but still dnot work.
ADB ist 100% enable in Kindle Settings Menu.
Can anyone Help me ?
avathor said:
I have here Kindle Fire rev. 2.
I want to root it.
I downloaded Kindle Fire ADB drivers.exe , and installet it.
Run cmd.exe goto adb Folder type "adb devices" and adb server cant finy my kindle...
My Smartphone is Visable in ADB.
i have here 3 Win 7 PC´s and Win8 Notebook (all x64 OS) . I Try´d it on other PC, dnot work. I installed extra win 7 32 bit, but still dnot work.
ADB ist 100% enable in Kindle Settings Menu.
Can anyone Help me ?
Click to expand...
Click to collapse
Really needs to be in Q+A not dev.....
Try this;
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
from here
bryanchapman9999 said:
Really needs to be in Q+A not dev.....
Try this;
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
from here
Click to expand...
Click to collapse
I downloaded the SDK and it didn't have a 'adt bundle' in the contents but i ran sdk manager and I had already added the link you mentioned and I also had already added the extras you mentioned earlier from a article I read and Nothing so I stumbled across this article and it had a few extra steps so I thought to give it a try only problem is, When I go to my device manager to uninstall the kindle drivers i don't have that option to uninstall a 'kindle' driver rite below it there's a android adb interface and i have the option there to uninstall but before I did so I wanted to post here what's going on with me. I wonder if it worked for the person who started the post?
bryanchapman9999 said:
Really needs to be in Q+A not dev.....
Try this;
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
from here
Click to expand...
Click to collapse
Worked perfectly and allowed me to root using the other guide in the forum.
Posted using my Kindle Fire 2.
Are you using the adb from the latest sdk?
I couldn't get adb to recognise my kf2 until I used the latest adb.exe
I rooted my both kindle´s before a week.
no idea why the other driver did not work.
The Driver from http://kindle-sdk.s3.amazonaws.com/addon.xml work perfectly.
I had this same issue until I updated the driver with the latest. I don't have it in front of me, but when I looked at it, it's dated approx Dec 8th 2012 in Device Manager. Update the driver to the latest and you should be good to go.
know that if you install the drivers after connect your kindle it can mess it up, if you go into device manager and uninstall the drivers after you've disconnected you're kindle and install them then reconnect it, it should work.
I think I know what's wrong...Your using windowzzzzzzzzzzzzzzzzzzzzzzzz...
powerpoint45 said:
I think I know what's wrong...Your using windowzzzzzzzzzzzzzzzzzzzzzzzz...
Click to expand...
Click to collapse
Powerpoint is so right here, If you use any linux distribution, it's going to be much easier to get your kindle connected to adb.
Do we even have a q&a or general section for this device? Bought, rooted and turned into a tablet today
Sent from my KFOT using Tapatalk 2
new adb files
cupidstunt said:
Are you using the adb from the latest sdk?
I couldn't get adb to recognise my kf2 until I used the latest adb.exe
Click to expand...
Click to collapse
That must have been my problem. I ended up moving to my Xubuntu machine to get it to work. I think my adb was from November,
Joe
rooting kindle fire 2 (10.3.1)
bryanchapman9999 said:
Really needs to be in Q+A not dev.....
Try this;
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
from here
Click to expand...
Click to collapse
Thanks for the steps to install adb drivers worked prefectly
can you also kind me how to install custom recovery on kindle fire 2 (10.3.1) and cm10.1
@indus76:
You may want to look at these threads:
http://forum.xda-developers.com/showthread.php?t=2100963
for flashing the second bootloader and TWRP recovery
and
http://forum.xda-developers.com/showthread.php?t=2209995
for flashing CyanogenMod
Good luck!
This probly isnt the right place for this but I have been to so many areas and so many websites that I am crosseyed now. I managed to root my kindle the other day and was attempting to install a mod on it. At this point I cant even remember which site I was on to share the steps I took. Needless to say, I messed up and now the kindle boots to to the logo for a few seconds, shuts off and boots back to the logo, over and over. I'm not very good at all this but not completely stupid either. I'm simply ready to pull my hair out. I have installed Android SDK and am having trouble getting the correct drivers for my kindle apparently. Its a kindle fire hd 2012. I went through all the trouble of installing the sdk and got to the part with the addons and manually putting in the amazon site, only to read on and discover its no longer supported so I can not get the different kindle fire definitions. In my device manager, it shows kindle fire and expanded shows Android ADB Interface (no composite.. does it matter?). I have verified that abd is installed and working, but doing a devices command, doesnt show any devices. It executes without errors, just doesnt list anything. I have a fastboot cable and it does currently say Fastboot on the kindle when I plug it in.. thats all it says tho, is it supposed to go any further then those words?
I have tried so many suggestions on here to get it to see my kindle to no avail. I follow tutorials, that seem to link to other tutorials because the previous ones had prerequisites and THOSE have links for downloads that no longer work and so I do a side load of a webpage trying to find the missing download I need and THOSE pages end up leading me somewhere else or going a different route then the previous tutorial took me and I just CAN'T get anywhere with this! It shouldnt be this hard (and I'm venting at this point so I apologize). Does anyone have an UPDATED (2018) tutorial for getting my kindle back to where it will boot up... assuming my computer will ever see it (windows 7 btw). Thanks in advance.
I'm new to the Kindle Fire flashing scene, and trying to get Jelly Bean on to my stock Kindle Fire. I've spent several hours on it so far, and haven't been able to get past the first step of getting KFU to see my Kindle Fire, so I can root it or do anything else. To be clear, this is a 1st gen Kindle Fire, running 6.3.1. I've never rooted or flashed it before, and it boots and works perfectly.
The main problem I seem to be having is that Device Manager (on my Win7 PC) shows the device as 'Android ADB Device.' It seems the expected description should be 'Android Composite ADB Device' but I can't get it there. Most of the posts and pages I've seen related to having trouble getting KFU to see a Kindle Fire focus on the drivers not being installed at all, which I don't think is my problem. And I've uninstalled/re-installed them at least 1/2 a dozen times with no effect.
The documentation would seem to suggest that seeing 'Android ADB Device' in the Device Manager implies my device is in Fastboot mode. However, when I uninstall the drivers I see 'Kindle' not 'kindle' in my device manager which suggests normal mode according to the 'Windows Device Drivers and the Device Manager' tutorial. This seems consistent with the fact that my device behaves perfectly normally, so I don't think it's actually in FB mode. Further, the FB tool can't see it.
I've tried connecting to the device from the command line using both the ADB (adb devices) and Fastboot (fastboot -i 0x1949 getvar product) tools. Neither one seems capable of connecting to the device. I also tried connecting the device on a second PC and there too I got 'Android ADB Device', suggesting the problem is device side. I don't have a factory cable to force FB mode that way.
I suspect I'm missing something obvious, but can't figure out what. Can anyone help me out?
It`s probably something strange I`m pretty good at working it out contact me tomorrow via Pm I would be happy to look at it for you. Check your user/.android folder for adb_usb.ini see if it has 0x1949 in it.
Thanks, the adb_usb.ini has the 0x1949 line in it, so that's not the issue. My %userprofile% directory name has a space in it, which initially caused the install_drivers.bat that comes with KFU to have some issues (because it assumes it doesn't.) But everything is where it should be now. Look for my PM.
Re: [Q] Can't get Stock Kindle Fire to show "Android Composite ADB Interface"
I had to used the drivers in superoneclick 2.3.3.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
This problem is solved he was running kfu from a temp directory.
Actually, I don't think the problem was the location of KFU. Thepooch gave me a new android_winusb.inf to use along with the KF drivers. The new .inf file had additional Kindle Fire entries for USB\VID_1949&PID_0004 and USB\VID_1949&PID_0007 which the original version I got with KFU did not include. If I pull up the Hardware IDs from the details tab of the device in Device Manager, it showed the PID_0007 version. So I suspect the fact that was missing from the inf file was the cause of my issues (and it's inclusion the solution.) I've attached the updated inf file (with added .txt extension) to this reply.
Beyond that, Thepooch did an amazing job helping me through the whole process. Really went above and beyond. Thanks!