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] Problem when rooting, help me out?

Heres where i got from following a video tutorial, I installed the KFU drivers, and then ran the utility, and it stopped at this area "fastboot uses a different device thn ADB you should check your device manager for kindle, amazon." Above that is saying that they are unable to locate my kindle fire. The Kindle itself is stuck at the Kindle fire logo, with no animation to it, and i've tried just about everything to get it back to normal, but until the computer will recognize my kindle again. I can do nothing. Let me know if you have a solution for me, thanks.

Bongripper said:
Heres where i got from following a video tutorial, I installed the KFU drivers, and then ran the utility, and it stopped at this area "fastboot uses a different device thn ADB you should check your device manager for kindle, amazon." Above that is saying that they are unable to locate my kindle fire. The Kindle itself is stuck at the Kindle fire logo, with no animation to it, and i've tried just about everything to get it back to normal, but until the computer will recognize my kindle again. I can do nothing. Let me know if you have a solution for me, thanks.
Click to expand...
Click to collapse
If you have drivers installed corectly then you could try turning kf off. Go to kfu then bootmode then 4000(normal) It should say waiting for device. then plug kf in while it is off and let it boot from connecting it. If it works then it should boot up.
Sent from my Amazon Kindle Fire using xda app-developers app

powerpoint45 said:
If you have drivers installed corectly then you could try turning kf off. Go to kfu then bootmode then 4000(normal) It should say waiting for device. then plug kf in while it is off and let it boot from connecting it. If it works then it should boot up.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I tried that, but when i plugged in the kf it said it was an unrecognized device, so it doesn't show up as a usb mass storage, I need a way to make this computer to recognize it as a kindle again. And then i can get into ADB, i just don't know how to do it.

Bongripper said:
I tried that, but when i plugged in the kf it said it was an unrecognized device, so it doesn't show up as a usb mass storage, I need a way to make this computer to recognize it as a kindle again. And then i can get into ADB, i just don't know how to do it.
Click to expand...
Click to collapse
Cant help you with that unless you were using Linux.

Here try this iso http://db.tt/KDNzyCTP
Instructions:
1. Download this http://www.pendrivelinux.com/univers...easy-as-1-2-3/
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of dropdown in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
then powerpoint45 can help you via teamviewer on linux to launch teamviewer type teamviewer7 in aterminal and hit enter give him your partner id and passcode in a pm if hes willing to help of course I cant speak for him you need a 2gig usb flash drive or larger

Alright, i've spent hours trying to get it back to normal, still no luck, can someone just tell me the easiest way for me to get my computer to recognize my Kindle fire as what it is, and then set it back to normal mode? I really don't want to end up not able to fix it.

Try this
http://forum.xda-developers.com/showpost.php?p=30629067

Thanks for the help guys but i still haven't made any progress, is it really just about impossible just to get windows to recognize a device? I really think at this point that i'm not going to be able to get it fixed, and the problem is so simple, why the solution isn't, i'm not sure yet.

Bongripper said:
Thanks for the help guys but i still haven't made any progress, is it really just about impossible just to get windows to recognize a device? I really think at this point that i'm not going to be able to get it fixed, and the problem is so simple, why the solution isn't, i'm not sure yet.
Click to expand...
Click to collapse
Then forget about Windows and use Linux. You can install it and run SoupKit, or you can try out this instead:
http://forum.xda-developers.com/showthread.php?p=31449443

Kindle Fire Stuck Logo

Hello all, please forgive me as I know there are a ton of threads with a similar title but I'm completely new at this and I'm frankly at a loss.
My Kindle Fire is stuck on the Kindle Fire logo screen after trying to unroot it. I know I messed up by trying to wipe everything off of it and rebooting it. I'm hoping someone can walk me through a step by step guide on how to unbrick it (I am completely dumb with this and probably shouldn't have attempted to unroot it in the first place).
I recieve the following error when trying to do anything in the KFU or the Unbrick Utility:
exec '/system/bin/sh' failed: No such file or directory (2)
Unable to access the internal portion of the Kindle Fire, when I try to "Browse Files" it's grayed out with no option of looking into it. When looking at the device itself, it's on the dimmed light Kindle Fire logo with the power button showing green.

well unfortunately you will need twrp and fff back on your device to do it... if you cannot get it into fastboot very likely you will need a factory cable to do so found here http://forum.xda-developers.com/showthread.php?t=1392693 after you get twrp and fff back on simply wipe everything except your sdcard or external storage and flash this rom http://forum.xda-developers.com/showthread.php?t=1439916 then you will be all refreshed and can decide where to go from there...
Edit:looks like at this point he has 5 cables maybe less left best jump on that as soon as you can... in the meantime keep it on the stock wall charger as not to compound the situation with a depleted battery...

Thepooch said:
well unfortunately you will need twrp and fff back on your device to do it... if you cannot get it into fastboot very likely you will need a factory cable to do so found here http://forum.xda-developers.com/showthread.php?t=1392693 after you get twrp and fff back on simply wipe everything except your sdcard or external storage and flash this rom http://forum.xda-developers.com/showthread.php?t=1439916 then you will be all refreshed and can decide where to go from there...
Edit:looks like at this point he has 5 cables maybe less left best jump on that as soon as you can... in the meantime keep it on the stock wall charger as not to compound the situation with a depleted battery...
Click to expand...
Click to collapse
Thank you for the response.
How does the cable work though? Does it work just by plugging it into the device? By using it and the Kindle Fire Utility I would be able to install the TWRP at that point? Also how do I flash a rom onto it when it is in TWRP? Kinda confused what flash means sadly..

Dont feel bad.. this is what I had to do to get the cable to work for me when I tested it: shift + right click on the tools folder in kindle fire utility.. select open command window here...hold down the power button on the kindle for 30 seconds to power it off , dont plug it in yet type
Code:
fastboot -i 0x1949 getvar product
in the terminal hit enter.... then plug the kindle in ... it will then power on in fastboot and return product:kindle in the terminal... this is if all your drivers are installed correctly if this is the very first time you have tried anything with your kindle I suggest you get at least a 2 gig usb flash drive and go this route....
Originally Posted by Thepooch
its all set up
Here try this iso http://db.tt/KDNzyCTP
Instructions:
1. Download this http://www.pendrivelinux.com/ universal usb installer is the program
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of dropdown in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
different build but thread found here http://forum.xda-developers.com/showthread.php?t=1882565
just pm me when you get to this point and I will help you do the rest factory cable in hand and running live usb...this live usb will allow you to boot linux on your machine if your on windows all the up front configuring is all ready done.. in your spare time while you wait I suggest some learning first here http://forum.xda-developers.com/showthread.php?t=1552547 and here http://forum.xda-developers.com/showthread.php?t=1638452 there is alot of content here but these are the best guides on the net bar none...

foxdieabetes said:
Thank you for the response.
How does the cable work though? Does it work just by plugging it into the device? By using it and the Kindle Fire Utility I would be able to install the TWRP at that point? Also how do I flash a rom onto it when it is in TWRP? Kinda confused what flash means sadly..
Click to expand...
Click to collapse
to better answer this question the cable forces the devices into fastboot so that things like bootloaders and recoveries can be easily replaced when there doesnt appear to be another way to do it. As far as flashing goes it pertains to flashing a rom flashing a recovery ect. In most instances it just means replace without a better term for it...

[Q] Failed ROM Flash - Kindle can't connect via usb

I apologize ahead but I have not been able to find a thread that addresses my problem.
Kindle Fire (1st gen)
Rooted with KFU, installed FFF, TWRP, Go Launcher and Gaaps. Worked perfectly.
Attempted to flash hashcode's JB ROM with Goo manager and made a mistake.
Attempted to boot to system and all that will show is the Rolling Triangles splash screen
continuously.
I can boot to TWRP.. I want to start over and flash the Amazon update 6.3.1 but my
Windows 7 PC cannot connect to the Kindle over usb. Fastboot seems to connect
(returns "Kindle" on fastboot getvar product) ADB does not show any devices attached.
I have deleted and reinstalled drivers - Windows does not recognize the Kindle.
Will a factory cable allow my PC to recognize my stuck Kindle?

Which version of twrp are you using?
Sent from my Amazon Kindle Fire using xda app-developers app

A factory cable will only put your device in fastboot. If you plug the kindle in while in recovery it should install the correct drivers. Try connecting to your computer and selecting mount and hit the big button to access your sdcard contents, where you can transfer a new rom zip to it. I wouldn`t attempt to flash stock unless you research prior many brick their devices and then a factory cable is needed. Did you wipe before flashing? If so how and what?

Also, do you have FireFireFire installed?

Thank you for your replies!
I have FFF installed
TWRP is 2.3
I did do a cache wipe and factory reset within TWRP
I did see this morning manofFishfry posting "[Q] I need help bad"
and it seems he was having a nearly identical problem with USB
connection.
I will attempt thepooch's recommendation:
http://forum.xda-developers.com/show....php?t=1850038
I will post any progress I make.
Many thanks
M

TWRP 2.3 is your issue if you do get ubuntu setup with Soupkit simply replace 2.3 with 2.2.2.1 and rewipe and reflash another rom.

Thepooch said:
TWRP 2.3 is your issue if you do get ubuntu setup with Soupkit simply replace 2.3 with 2.2.2.1 and rewipe and reflash another rom.
Click to expand...
Click to collapse
Looks like I'm still stuck then - I've only got Win7 on my PC - unbuntu is WAY out of my league.
I'll try Zombiepiratez unbrick utility
M

It`s not that far out of your league. Use universal usb creator to make a live usb with persistent run soupkit on it reboot the usb Your in like flin If you want help I can help you at some point to get this done.

Thepooch said:
It`s not that far out of your league. Use universal usb creator to make a live usb with persistent run soupkit on it reboot the usb Your in like flin If you want help I can help you at some point to get this done.
Click to expand...
Click to collapse
I removed the Kindle drivers from my Laptop PC and then connected my son's unrooted stock KF1. It was recognized, the drivers loaded, and I loaded the KFU drivers and updated them no problem. I ran KFU and got 4000 on the code.
I then plugged in my "stuck in TWRP/FFF/JB Splash Screen" rooted KF1 and the PC sees it as a removable memory device. It prompts me to load it with media when I double click on it. KFU can't find it. ADB can't find it. Fastboot can get "Kindle" from getvar product, but nothing else.
What can I do next?
Thanks!

Update
Micah461 said:
I removed the Kindle drivers from my Laptop PC and then connected my son's unrooted stock KF1. It was recognized, the drivers loaded, and I loaded the KFU drivers and updated them no problem. I ran KFU and got 4000 on the code.
I then plugged in my "stuck in TWRP/FFF/JB Splash Screen" rooted KF1 and the PC sees it as a removable memory device. It prompts me to load it with media when I double click on it. KFU can't find it. ADB can't find it. Fastboot can get "Kindle" from getvar product, but nothing else.
What can I do next?
Thanks!
Click to expand...
Click to collapse
One new thing: I mounted the SD card using TWRP, then my Win 7 Laptop could connect to my Kindle via usb as an external drive. Win 7
then siad the drive needed reformatting. KFU still would not connect.

would the soupkit help in this situation? I had the same problem but figured out the whole mounting from TWRP and it worked for me

Micah461 said:
One new thing: I mounted the SD card using TWRP, then my Win 7 Laptop could connect to my Kindle via usb as an external drive. Win 7
then siad the drive needed reformatting. KFU still would not connect.
Click to expand...
Click to collapse
Your sdcard issue and ADB issue are two completely unrelated things. The ADB issue is due to the way Windows handles drivers. Fix the driver problem or use SoupKit/Linux.
The sdcard issue is due to your sdcard losing its formatting somehow. You'll have to reformat (quick format, block size 4096) in order to use it again. You will lose all data on the sdcard BTW.
"That's a special kind of stupid. The kind that makes me laugh"

Huzzah! Success in spite of myself!
Many thanks to each of the experts that each gave me nuggets of info that eventually
unbricked my KF1.
I last posted that Win 7 would see my Kindle when I used TWRP to mount the SD card.
It prompted for me to "format the device" and feeling I had nothing to lose - selected
default settings and quick format.
This then opened a File Manager window giving me access to the SDcard folder on the KF1.
I had downloaded the Stock update from Amazon update-kindle-6.3.1_D01E_4107720.bin
On another thread - Soupmagnet had said to rename this BIN file to a ZIP - which I did.
I shortened the file name to update-kindle-6.3.1.zip.
I de-mounted the SDcard folder in TWRP.
I wiped the Dalvic and did a factory reset.
I navigated to the Install screen and it found the update file and installed it.
UNBRICKED!
Thanks again for the tireless help you guys give.
Micah461

[Q] Another nOOb got his Kindle Fire stuck in fastboot mode.

Good evening all. Here I am, another nOOb who ended up getting his Kindle Fire stuck in fastboot mode. I've read through the forums for about a week and a half and tried to apply some of the suggestions with no luck. I'm using a 32bit Windows 7 Home Premium desk top computer and am using the KFU 0.9.6. The Kindle fire is in stock mode stuck at the white and yellow boot logo. My computer recognizes the Kindle Fire as an Andriod Phone>Android ADB Interface but I have the yellow exclamation and in the properties it reports a code 10 error. (see attachment 1.) I tried uninstalling and re-installing the driver's by the cut and paste below. post #2 again with no luck.
If the Kindle Fire comes up as a different device or you get a "Code 10" error, you'll have to explicitly tell Windows what driver you expect to see for the device. The steps below are for Windows 7, but they should be very similar for earlier versions of Windows as well. The following may have to be performed twice, once for normal mode and again for fastboot mode. The steps below are listed for normal mode (and the fastboot equivalent in parentheses). Be sure to have tried installing the drivers using the batch file at least once or you will not be able to complete the process.
*Connect the Kindle Fire in normal mode (fastboot mode) to the computer
*In the Device Manager, right click on the device and select "Uninstall"
*Check the "Delete the driver software for this device." box and press "OK"
*Disconnect the Kindle Fire, reconnect and reboot in normal mode (fastboot mode)
*The Device Manager should show "Other devices -> Kindle" ("Other devices -> kindle")
*Right click on "Kindle" ("kindle") and select "Update Driver Software..."
*Select "Browse my computer for driver software"
*Do not click the "Next" button, but select "Let me pick from a list of device drivers on my computer"
*Select "Android Phone" and then press the "Next" button
*Press the "Have Disk..." button
*Click the "Browse..." button, point it to the "C:\kfu\drivers\kindle" directory and press "Open"
*Press the "OK" button
*Uncheck the "Show compatible hardware" checkbox
*Select "Android Composite ADB Interface" ("Android ADB Interface") and press the "Next" button
*Select "Install this driver software anyway"
*Press the "Close" button
The device should now appear in the Device Manager.
I tried this suggestion post #4 thinking it was the closest to my current situation again with no luck. The command prompt window hangs up at the waiting for device.. forever. I tried the suggestion with a regular USB cable and a factory cable (Thank you SkOrPn) with same results. KFU shows the device ADB Status as offline and Boot status as unknown (see attachment 2.)
If anyone has any suggestions I'm all ears. If any further information is needed just ask and I'll do my best to supply it.
Thank you in advance for any and all help
Mike Shipman
sabres032

Okay try this method. Plug your kindle in, use kfu to set the bootmode to normal, when it hangs <waiting for device> hold the power button down while connected till it powers off, then simply power it back on and wait bootmode change doesn't happen immediately. Rinse and repeat till you're successful. If your trouble persists due to driver issues consider trying soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .

Thepooch said:
Okay try this method. Plug your kindle in, use kfu to set the bootmode to normal, when it hangs <waiting for device> hold the power button down while connected till it powers off, then simply power it back on and wait bootmode change doesn't happen immediately. Rinse and repeat till you're successful. If your trouble persists due to driver issues consider trying soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .
Click to expand...
Click to collapse
Thank you for the suggestion. Should I use a normal USB cable or the Factory Cable?

A normal one. A factory cable is intended to stick you in fastboot you're already there

Thepooch said:
Okay try this method. Plug your kindle in, use kfu to set the bootmode to normal, when it hangs <waiting for device> hold the power button down while connected till it powers off, then simply power it back on and wait bootmode change doesn't happen immediately. Rinse and repeat till you're successful. If your trouble persists due to driver issues consider trying soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .
Click to expand...
Click to collapse
OK So I've tried your suggestion of using KFU to set boot mode to normal, and rebooting the Kindle (after sufficient time, like 30 minutes) and still nothing. I've also tried to uninstall and re-install the drivers as noted in the OP, and every time the driver's install I still get the code 10 error. Would a broke bootloader or not being in fastboot be the cause of this? I'm sure there is an easy way to get the driver's to install properly but, so far it's escaping me. YEs I have spent more than two weeks searching the forums and trying others suggestions.
I know Window's can be very temperamental but I'd like to avoid using soup kit since it's Linux based and I know nothing of Linux. I only have one computer and if I screw it up I will have to waste even more time reloading windows and configuring.
I'm open to just about any other suggestion right now.
**EDIT** Also not sure if this means anything the C:\User\.android folder is empty. ISn't there supposed to be an .inf or configuration file in there?

**EDIT** Also not sure if this means anything the C:\User\.android folder is empty. ISn't there supposed to be an .inf or configuration file in there?
Click to expand...
Click to collapse
yep you can get it from the drivers folder in kfu and put it in there it`ts the adb_usb.ini if you open it with notepad it has this inside 0x1949. When your having driver issues soupkit is the way to go unless adding that file does it for you.

Thepooch said:
yep you can get it from the drivers folder in kfu and put it in there it`ts the adb_usb.ini if you open it with notepad it has this inside 0x1949. When your having driver issues soupkit is the way to go unless adding that file does it for you.
Click to expand...
Click to collapse
I would definitely need some major hand holding if I have to use soupkit as I have zero knowledge of Linux. Let me see if adding the .ini file works.

You could try the iso I made post 7 http://forum.xda-developers.com/showthread.php?t=1413358 . I`ll hold your hand if you need it.

I know it's been a while (a looooong while) since I have posted here but life sort of got in the way. I would like to share an update on my predicament. After months of leaving the Kindle Fire sitting on my bookshelf collecting dust I tried again to unbrick it. I spent a great deal of time studying up on Linux and reading and re-reading soupmagnets soupkit and decided to give it a try. I mean why not I'm not going to make things worse, right? . Well let me tell you it worked like a charm. I was able to restore my Kindle Fire to factory settings and to take it a step further I was able to install CROT recovery, the latest FFF bootloader and install CM10.1 and it's like a have a new device. I would like to give a huge thank you to everyone who tried to help me fix my device, you rock.
Mike