Develop Bugs

Device not recognized on ADB?

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.

[Q] Kindle Fire Root Help, URGENT!

I am having a serious problem with my Kindle Fire, I am worried that it has bricked. For the past month ive been trying to fix it and nothing ever worked out. What happened was I tried to root my kindle using Kindle Fire Utility, and everything seemed fine at first. I turned my Kindle on and everything was normal, then I turned it on again and all it does is flash on and off at the screen with a yellow triangle with a flame in the middle of the triangle and it says "press power button for recovery." The kindle does not respond to anything and it will not turn on unless connected to the computer and it will not turn off until i disconnect it. My computer also does not recognize my Kindle.
Kindle Fire Utility says to just switch it to normal mode by going the "fastboot menu" and simply switching it. But when i do the program just sits at the screen saying "waiting for device" and I think its because my computer simply will not recognize it.
Others have said to go in the command prompt and type "adb shell" but that wont work either. It says something like "adb is not recognizable as an internal or external command, operable program or batch file. So i have no idea what to do there.
I never installed TWRP so i tried tonight, and I downloaded the image and i did what it tells me to do in the command prompt, but once again it would not me recognizable as an internal or external command.
Im all out of ideas and have not found a single person with the same problem as me and I need any help I can get from anyone. I GREATLY APPRECIATE ANYTHING!

http://forum.xda-developers.com/showthread.php?t=1623244
http://forum.xda-developers.com/showthread.php?t=1552547

Charged
Well I charged my Kindle overnight and it is staying on and i can turn it on and off whenever, i connected it to my computer and the computer found it but it couldnt find any drivers for the Kindle and it sort of ignores the Kindle. The Kindle fire utility still says "waiting for device" and when i try to install drivers from the Kindle fire Utility folder it tells me "There was no driver found for this machine" What should i do now?

Read this first...
http://forum.xda-developers.com/showpost.php?p=23747567

Have you tryed holding the power button down for like 20 seconds to power it completely off then powering it back on?

Read it
I read the page and they said I can reverse it with SDK, or KFU. Ive tried with Kindle Fire Utility but how do i do it with SDK??

Thepooch said:
Have you tryed holding the power button down for like 20 seconds to power it completely off then powering it back on?
Click to expand...
Click to collapse
Yes ive tried and it continues to do the same thing

I'm a little confused about the reverse it idea but the drivers were there before why aren't they now? If your referring to going through the process to set a the proper environment you need Java development kit then open the sdk manager and download tools and 2.3 platform and the Google driver this is a lot of excess bulk that may not be needed try using system restore to roll your computer back to a date before you messed with the driver's. Download a fresh copy of kfu rerun the driver without your kindle plugged in then see what you get.

SDK will let you do the same thing KFU does, only manually. If you can't get KFU to work, the SDK probably won't help.
In order for either to work, you need to make sure your drivers are in order.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

The yellow triangle your looking at is the bootloader which isn't bad but the fact that you don't have twrp installed and can't get past it and your computer either doesn't recognize or will not communicate with the device is bad. Your driver's must be functioning to make it past this via adb.

Thepooch said:
The yellow triangle your looking at is the bootloader which isn't bad but the fact that you don't have twrp installed and can't get past it and your computer either doesn't recognize or will not communicate with the device is bad. Your driver's must be functioning to make it past this via adb.
Click to expand...
Click to collapse
Could I do it on a different computer then?

Many people have had success with that, yes.

Unsigned drivers
Well i tried on the new computer and it wouldnt let me download the drivers but i found out about changing the unsigned driver settings on my original computer but i have windows vista on the original one and windows XP on the other, the Windows XP computer was easy to see the unsigned driver setting(which didnt work out) but i cnat find it on the vista. Where is it located?

I also tried the code: bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
The cmd told me that my access was denied

soccerman9 said:
Well i tried on the new computer and it wouldnt let me download the drivers but i found out about changing the unsigned driver settings on my original computer but i have windows vista on the original one and windows XP on the other, the Windows XP computer was easy to see the unsigned driver setting(which didnt work out) but i cnat find it on the vista. Where is it located?
Click to expand...
Click to collapse
http://www.google.com/search?mmns=0...action=devloc&q=disable+unsigned+driver+vista

soupmagnet said:
http://www.google.com/search?mmns=0...action=devloc&q=disable+unsigned+driver+vista
Click to expand...
Click to collapse
It says i gotta choose a device/file, what file would it be? would it be the "install_drivers" in the kfu?

There should be two files:
android_winusb.inf & adb_usb.ini
...both are somewhere in the KFU/drivers folder

soupmagnet said:
There should be two files:
android_winusb.inf & adb_usb.ini
...both are somewhere in the KFU/drivers folder
Click to expand...
Click to collapse
I found the adb_usb but there two of the other, they are called
androidwinusb86
&
androidwinusba64
Does it matter which one i choose?

Well i got the Google Usb driver installed, but the problem still remains where my kindle is connected and my computer says its finding a driver for it, but then my Kindle disconnects too fast and the computer cannot find any drivers because "the device was unplugged." I noticed that when i start the kindle while its connected the power button light is green, and thats when my computer sees the Kindle, but then the light turns orange and then the computer loses it. What should i do now?

That seems to be a typical problem with Vista. I'm not sure what causes it, but it would probably be beneficial for you to try a different computer, if you have one available.

[Q] Kindle Fire Stuck on Boot Image

I was attempting to root my Kindle using the tools in this thread: http://forum.xda-developers.com/showthread.php?t=1399889
It failed at "Installing FFF... Waiting on Device". It seems like this is an issue with TWRP. Since that failed the kindle gets stuck on the Kindle Fire logo and can only be powered off with the 20 second button press.
I am not sure where to go from here, any help would be great, thanks

This same thing has happened to me SO many times. What's happening is your Kindle is stuck in fastboot mode. This is usually caused by a driver related issue. You probably didn't have installed all the correct drivers. Try doing this to get it back to normal bootmode:
First make sure the right drivers are installed. Run "install_drivers.bat"
Then before plugging in or turning on your Kindle run "run.bat" and choose "1 Bootmode Menu" and select "1 Normal <4000>"
It should now say "waiting for device". Make sure your Kindle is still off then plug it in. It should boot up on it's own. Then KFU will recognize it and switch it to normal bootmode.

Nihilian said:
This same thing has happened to me SO many times. What's happening is your Kindle is stuck in fastboot mode. This is usually caused by a driver related issue. You probably didn't have installed all the correct drivers. Try doing this to get it back to normal bootmode:
First make sure the right drivers are installed. Run "install_drivers.bat"
Then before plugging in or turning on your Kindle run "run.bat" and choose "1 Bootmode Menu" and select "1 Normal <4000>"
It should now say "waiting for device". Make sure your Kindle is still off then plug it in. It should boot up on it's own. Then KFU will recognize it and switch it to normal bootmode.
Click to expand...
Click to collapse
I did all of that and it still does not get past the splash screen. The kindle booted up on it's own, but KFU never went past <waiting for device> and the kindle never went past the splash screen.

Try researching into the Factory reset cable that Skorpion sells, that can help boot your kindle into fastboot mode and help unbrick it.

A factory cable would be no help here seeing as it's already in fastboot mode. You need to somehow get your Fire back to normal boot mode. To me it sounds like this is a driver related problem since KFU cannot find your device. Try looking into this. It has helped me in the past. You need to be running Ubuntu for this, but then you won't to deal with drivers.

Nihilian said:
A factory cable would be no help here seeing as it's already in fastboot mode. You need to somehow get your Fire back to normal boot mode. To me it sounds like this is a driver related problem since KFU cannot find your device. Try looking into this. It has helped me in the past. You need to be running Ubuntu for this, but then you won't to deal with drivers.
Click to expand...
Click to collapse
I have tried using that with Ubuntu as well, but the computer still never recognizes the Kindle. I ordered the cable in case it helps, it should be here after Christmas. I will try out some more options in Ubuntu in the time being.

The stock bootloader has (presumably) been modified from it's original state and packaged with the 6.3.1 update. I stumbled across this anomaly during my work on the SoupKit.
Typically, with working drivers, the stock bootloader would report that a device is connected when it receives the "fastboot devices" command. Now, it doesn't...even on Linux. Another thing I noticed, is that when a fastboot command is sent, it sits at "waiting for device", indefinitely, or until the device is restarted by use of the hard shutdown. When the device starts up again, fastboot will detect it and send the command. Unfortunately, this only works for one command at a time and the device needs to be restarted again.
This all depends on whether the drivers are in working order, of course.
Windows can be very finicky when it comes to Android drivers so the best bet is to use Linux so as to eliminate as many variables as possible. Try sending the command and restarting the device. If it doesn't work, you know it's a driver issue. You can keep trying to fix your drivers in Windows or bite the bullet and go the Linux route. If you do decide to go the Linux route, SoupKit can make your life considerably easier (just choose an option and follow the instructions).
"That's a special kind of stupid. The kind that makes me laugh."

I think its been once again modified a little more as of recent there was a tiny update that I believe will have some affect.

I have tried a few of the options in FireKit on a Ubuntu LiveUSB Stick.
Same problem as ever though. Nothing ever gets past < waiting for device >.
My process is: enter the prompt in Terminal and get to the < waiting for device > step. Plug in the powered off Kindle Fire. The KF boots up into the splash logo.
After a few minutes the screen and power LED starts to turn on and off but nothing else ever happens.

I got a factory reset cable, but it does not seem to do anything.
I have also tried soupkit and firekit, both on a Ubuntu live USB.
Is there anything else I should try?

[Q] Purchased a "Bricked" Kindle Fire...

After toying with jailbreaking/modifying iPhones, taking a Unix/Linux course at a local community college, experimenting with different linux operating systems, and stalking these forums for about the last month, I figured I would purchase myself a "Bricked" Kindle Fire and have at it for funsies. Well, I bit off more than I could chew. I'm stuck as much as the Kindle Fire is at what I think is the boot screeen for the FireFireFire Bootloader. It powers on and loads the Kindle Fire blue logo with a v1.4a in the top corner. Then, selects and deselects "normal boot" "recovery" "reset boot mode" on it's own without ever picking one! I'm not sure what the prior owner did to this thing but I'm assuming they at least attempted to root it. I've tried SoupKit, KFU, Kindle Fire Unbrick Utility, and tried adding the google USB driver for the thing in Windows 8. The worst part of it is that it's not recognized in either Ubuntu (terminal - tried lsusb) or Windows 8. Any help, suggestions, or even comments telling me that I'm dumb for doing this would be much appreciated. Thank you!

Your saying it runs through the bootmenu selections on its own? That`s a new one for me. Have you tried to select one? To get the Driver installed on windows 8 you must disable driver signature verification then install the driver.

It doesn't respond to me trying to select any of the options. It just cycles through each one from top to bottom. Last night I went through the steps to disable driver signatures (posted here: http://forum.xda-developers.com/showthread.php?p=34626361) I was successful in installing the drivers but the computer still does not recognize the device. I was also able to download/extract the Android SDK to my computer. I ran ADB and it showed the driver was installed. I believe ADB should recognize the device?

There are two methods on that page which one did you use? The one in post #8 will work but I just simply hold shift then click restart then follow the rest of the instructions to disable it. If its in fastboot adb will not recognize it but I bet your shell is corrupted as well when you select recovery it should go there unless your recovery is broken.

I followed the instructions on #8. Additionally, the LED on the power button does not power on. I don't know if that's any indication of anything or not.

When you plug it to the pc or the wall charger? To the pc isn't that strange could be the cable itself, to the wall might raise an eyebrow to early to tell. Im gonna send you a pm.

CH1215 said:
I followed the instructions on #8. Additionally, the LED on the power button does not power on. I don't know if that's any indication of anything or not.
Click to expand...
Click to collapse
It looks like you need to replace the bootloader...probably via usbboot.

Arrrgh The dreaded broken bootloader time to work a little firekit.

I did try a few of pokey9000's firekit options in SoupKit but to no avail. I am a bit confused as to where I need to place my metal object to "short the point" as I couldn't find any threads with pictures. I will continue to reasearch/apply usbboot and return to you with my findings. I really appreciate the help both of you have given me.

http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51 this is the test point there is a small metal frame surrounding it . Start the script when it says waiting for omap44xx contact the test point and just as you lean whatever you are using to short against the small metal frame and plug in the usb at the same moment. Keep it shorted till the script runs through 4 stages. The script you need to run is the usb fix parts install fff and twrp. It is best to brace the kindle against something so it does not slip as your trying to perform this maneuver. Caution not to contact anything but the test point and the metal frame to prevent permanent hardware damage.

I used a modified safety pin, used the correct option in firekit, and followed your directions, but it didn't seem to do anything. I can tell that the prior owner(s) had tried this before as the area I am to place the pin looks a bit scratched. On another note, I had to boot my windows partition to get something off of there late last night and I left the device plugged in. Surprisingly, this morning the device was showing up in the system tray as "kindle." I was curious and looked at the properties and it's showing the drivers are working and that it's an "Android phone." I don't know if this is a good indication of anything or not.

When you exspand android phone in device manager what does it say? Shift+right click on the tools folder select open command window here
Code:
adb shell
see what you get.

Thepooch said:
When you exspand android phone in device manager what does it say? Shift+right click on the tools folder select open command window here
Code:
adb shell
see what you get.
Click to expand...
Click to collapse
"Android Phone" expanded in Device Manager shows "Android Phone ADB Interface." When I try the command you suggested it says, "error: device not found."

kindle stuck... need help

Hey guys... Only second kindle I've ever attempted (have a butyload of other android devices I've rooted... But this bigger with no other buttons has me stumped )
Anyway... Went to root today, plugged in kindle, battery was dead... No problem... Let it charge.
When it booted, ran KFU to tell it to install TWRP. Here's where it gets....odd.
I had twrp in the KFU folder but it decided it wasn't there and wanted to download it... Mind you, this is... I believe... After it sent a command to fastboot ... Well, I didn't have internet, so KFU just sort of stopped when it couldn't download twrp...
Since then, the kindle is just stuck on KindleFire screen... Doesn't go any further... If I let the battery run out for about an hour, it will start rebooting every 5 seconds even if I plug it in. In the "bootloop" I can't turn it off, it just keeps rebooting...
If I let it die, I can plug it in, let it charge and turn it on... Sticks at KindleFire screen... I have tried holding in power for 30 seconds... It just turns the kindle off, doesn't help.
Windows sees it as an unrecognized device (tried rebooting, unplugging, uninstalling the drivers, looking at the KFU folder to manually select drivers (windows says they're not the correct drivers for the device) adv can't see it (cms... Adb devices shows no devices connected)
Any help is appreciated... If I missed needed info, please ask and ill supply...
I'm happy to try anything and report the findings...

RBThompsonV said:
Hey guys... Only second kindle I've ever attempted (have a butyload of other android devices I've rooted... But this bigger with no other buttons has me stumped )
Anyway... Went to root today, plugged in kindle, battery was dead... No problem... Let it charge.
When it booted, ran KFU to tell it to install TWRP. Here's where it gets....odd.
I had twrp in the KFU folder but it decided it wasn't there and wanted to download it... Mind you, this is... I believe... After it sent a command to fastboot ... Well, I didn't have internet, so KFU just sort of stopped when it couldn't download twrp...
Since then, the kindle is just stuck on KindleFire screen... Doesn't go any further... If I let the battery run out for about an hour, it will start rebooting every 5 seconds even if I plug it in. In the "bootloop" I can't turn it off, it just keeps rebooting...
If I let it die, I can plug it in, let it charge and turn it on... Sticks at KindleFire screen... I have tried holding in power for 30 seconds... It just turns the kindle off, doesn't help.
Windows sees it as an unrecognized device (tried rebooting, unplugging, uninstalling the drivers, looking at the KFU folder to manually select drivers (windows says they're not the correct drivers for the device) adv can't see it (cms... Adb devices shows no devices connected)
Any help is appreciated... If I missed needed info, please ask and ill supply...
I'm happy to try anything and report the findings...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2166668
#30 & #31

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2166668
#30 & #31
Click to expand...
Click to collapse
OK... but why does it stick on the KindleFire logo? (It does that without rebooting, it just hangs there).. And the battery drain was not intentional... It's ff now... charging (I assume... no logo, no led )

RBThompsonV said:
OK... but why does it stick on the KindleFire logo?
Click to expand...
Click to collapse
#16
It's ff now... charging (I assume... no logo, no led )
Click to expand...
Click to collapse
I would have to agree...it does appear to be charging.

soupmagnet said:
#16
I would have to agree...it does appear to be charging.
Click to expand...
Click to collapse
Sorry if im being super-noobish... I prefer my nook over this kindle
The logo is bright and unchanging (Seems to be stuck in fastboot?) But adb doesnt recognize it... windows sees it as an unknown device... and KFU shows... well, nothong Even when I try to normal boot in KFU (or adb..) it hangs on waiting for device.
Also, thanks a billion for even responding Soup... Its nice to know there's someone out there

RBThompsonV said:
Sorry if im being super-noobish... I prefer my nook over this kindle
The logo is bright and unchanging (Seems to be stuck in fastboot?) But adb doesnt recognize it... windows sees it as an unknown device... and KFU shows... well, nothong Even when I try to normal boot in KFU (or adb..) it hangs on waiting for device.
Also, thanks a billion for even responding Soup... Its nice to know there's someone out there
Click to expand...
Click to collapse
Okay,
Yes, it is in fastboot. ADB won't recognize the device in fastboot because ADB commands don't work in fastboot, only fastboot commands will. The KFU won't detect the device in fastboot because of the bootloader itself. It used to, but not anymore...likely due to an update on Amazon's part. There can be a couple of reasons why it just hangs at "waiting for device". When you see "waiting for device", you can reboot the KF and see if it detects upon rebooting. If not, you'll have to completely uninstall your drivers and try again. Even then, there's still a good chance it won't work. If not, you can reference the following thread for clues to get it working properly:
http://forum.xda-developers.com/showthread.php?t=2179748

soupmagnet said:
Okay,
Yes, it is in fastboot. ADB won't recognize the device in fastboot because ADB commands don't work in fastboot, only fastboot commands will. The KFU won't detect the device in fastboot because of the bootloader itself. It used to, but not anymore...likely due to an update on Amazon's part. There can be a couple of reasons why it just hangs at "waiting for device". When you see "waiting for device", you can reboot the KF and see if it detects upon rebooting. If not, you'll have to completely uninstall your drivers and try again. Even then, there's still a good chance it won't work. If not, you can reference the following thread for clues to get it working properly:
http://forum.xda-developers.com/showthread.php?t=2179748
Click to expand...
Click to collapse
OK.. Ive tried everything in the thread... Only thing I cant find is the android_winusb folder (Im running Win7 x64).
Also, when I look up the UNKNOWN DEVICE Hardware ID, I get USB\UNKNOWN) in device manager

RBThompsonV said:
OK.. Ive tried everything in the thread... Only thing I cant find is the android_winusb folder (Im running Win7 x64).
Also, when I look up the UNKNOWN DEVICE Hardware ID, I get USB\UNKNOWN) in device manager
Click to expand...
Click to collapse
Make sure you have the hardware IDs that I posted in that thread, in your KFU's 'android_winusb.inf' file.
You also have to find and delete the folder that gets created by KFU's install_drivers.bat. It will be in the WINDOWS directory somewhere, most likely in a hidden folder. Make sure "Show hidden folders" is enabled.
You may have to search your hard drive for any directory containing the string "android" OR for the filename 'android_winusb.inf',making sure to search hidden files and folders.
Once you have found and deleted it, reboot your computer and run KFU's newly edited 'install_drivers.bat'

Still Stuck...
OK, so, I did a CLEAN install of windows XP, installed the complete Android SDK package, then installed the modified KFU package (Added the lines of Device IDs supplied in your post on how to get it to work) and edited the install bat to install in legacy mode.
I still get an error in windows about the Kindle Fire.
I installed everything, then plugged in the kindle after turning it on. Kindle is still stuck on Kindle Fire logo (doesnt flicker or sparkle or dim or anything)... and windows says:
(In FOUND NEW HARDWARE WIZARD):
Cannot start this hardware
There was a problem installing this hardware:
Android Composite ADB Interface
This device cannot start (Code 10)
...

Thats a USB error code , maybe trying to use a different cable or use the usb ports on the back of the pc instead of the front

OMFG!!!!
I want to thank all of you for your help...
But, get this...
Apparently the kindle was waiting for me to send the TWRP package... THATS ALL!!!
I built the factory cable... proved useless for me
I went through all of my USB cables... NONE worked...
So, as a last ditch effort I thought... screw it, lets see what happens if I... (Fill in the blank)...
Tried sending the TWRP package and BAM!!!! Blue kindle...
Go figure