Develop Bugs

[Q] Waiting for device...

So I rooted my KF a day or so ago and didn't follow the directions entirely. I ended up bricking my KF. Eventually I was able to unbrick it and got it back to stock.
I would like to try rooting it again using the KFU (which is what I used the first time), but the KFU won't find my KF.
I installed the drivers and after I plug in my KF, it shows up in my Device Manager under 'Disk Drives' and it is named 'Amazon Kindle USB Device.' Is this correct?
I have removed the drivers and reboot both my computer and KF, re-installed the drivers and the same thing happens.
Something to note... when I uninstall the drivers and plug the KF back into my computer, the drivers install by themselves. I remember the first time I plugged my KF in, the drivers were not found and would obviously not install. I had to manually install the drivers included in this utility in order for my computer to 'find' my KF.

car_lost said:
So I rooted my KF a day or so ago and didn't follow the directions entirely. I ended up bricking my KF. Eventually I was able to unbrick it and got it back to stock.
I would like to try rooting it again using the KFU (which is what I used the first time), but the KFU won't find my KF.
I installed the drivers and after I plug in my KF, it shows up in my Device Manager under 'Disk Drives' and it is named 'Amazon Kindle USB Device.' Is this correct?
I have removed the drivers and reboot both my computer and KF, re-installed the drivers and the same thing happens.
Something to note... when I uninstall the drivers and plug the KF back into my computer, the drivers install by themselves. I remember the first time I plugged my KF in, the drivers were not found and would obviously not install. I had to manually install the drivers included in this utility in order for my computer to 'find' my KF.
Click to expand...
Click to collapse
I'm having the same problem.
In the device manager, you should see Android phone or some such near the top, as well as the drive you mentioned.
I tried to root my KF yesterday on 4 different Windows machines using 4 different OS's: Windows 7 Professional, XP Professional, XP and Vista. (Yes, I stil have a Vista machine)
No joy. <Waiting For Device> _
Matt

This might help both of you...
http://forum.xda-developers.com/showthread.php?t=1552547
Post #2 deals with driver installation, but it might not hurt to read #1 before you get to that.
Good luck.

kinfauns said:
This might help both of you...
http://forum.xda-developers.com/showthread.php?t=1552547
Post #2 deals with driver installation, but it might not hurt to read #1 before you get to that.
Good luck.
Click to expand...
Click to collapse
Yup, I've done all that.
One thing that doesn't happen for me anymore is this step when I remove/uninstall the drivers:
Check the "Delete the driver software for this device." box and press "OK"

car_lost said:
Yup, I've done all that.
One thing that doesn't happen for me anymore is this step when I remove/uninstall the drivers:
Check the "Delete the driver software for this device." box and press "OK"
Click to expand...
Click to collapse
Is this on Windows XP?
"Disk drives - Amazon Kindle USB Device" is not what you should be worried about. That just lets you mount the sdcard on Windows.
You should be seeing something under "Android Phone" or "Other devices" in the Device Manager. That's the device that needs the ADB drivers.

kinfauns said:
Is this on Windows XP?
"Disk drives - Amazon Kindle USB Device" is not what you should be worried about. That just lets you mount the sdcard on Windows.
You should be seeing something under "Android Phone" or "Other devices" in the Device Manager. That's the device that needs the ADB drivers.
Click to expand...
Click to collapse
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'

car_lost said:
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'
Click to expand...
Click to collapse
On a stock device, booted up to the OS... some device in a category other than Disk drives or Portable Devices should come up when you connect it to your computer. I've never seen a situation where that did not happen. If you have another computer, I would suggest trying that.

car_lost said:
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'
Click to expand...
Click to collapse
is there a device named "kindle" ? - if yes delete it and try to unplug/replug
if this don't help try to use this method to show devices that are not connected atm:
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
disconnect the kf and remove everything with adb or kindle
take care that you uninstall the driver too where you get the option to do this
now reconnect the kf - it should ask for the drivers like at the first connection

I'm formatting my computer and starting from fresh. Fresh copy of Windows 7 and a stock KF.
I'll report back.

regrouping
I'm going to regroup and try again as well and try again this evening. I've tried all of the above with no success.

Mattb4rd said:
I'm going to regroup and try again as well and try again this evening. I've tried all of the above with no success.
Click to expand...
Click to collapse
maybe this one can help:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

b63 said:
maybe this one can help:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
Already had tried that but did again for good measure. The driver installs as before but the KFU still hangs on "oops, something went wrong" and <waiting for device>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
Out of time right now and have to leave for a meeting. Will give it one more shot later.

you need two drivers:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
according to your screenshot the kf is not recognized by adb
what are the status lines if you start kfu ?
should look like:
ADB Status: Online
Boot Status: 4000

So I did a fresh install of Windows 7, plugged in the KF and the same damn thing is happening. I'm gonna throw this thing against the wall.

This is what I get...

previous pic doesnt seem to be working..

car_lost said:
So I did a fresh install of Windows 7, plugged in the KF and the same damn thing is happening. I'm gonna throw this thing against the wall.
Click to expand...
Click to collapse
You're in an unusual spot... I figured a new Windows install would get it to work. In my opinion, if you can rule out Windows 7 as the problem, you're going to have to start looking at the KF as the possible cause. I haven't had stock on my device in a while, but if I was in your shoes... I would try a factory reset. Maybe even try to get it to reflash the stock software. I think you can download the KF software from Amazon, rename it update.zip and put it at the root of /sdcard or /sdcard/kindleupdates and reboot to initiate a flash.
If none of that works, you might want to build/buy/borrow a factory cable. Then you can flash a new bootloader/recovery and try a ROM to see if you can get adb working with that.

kinfauns said:
you're in an unusual spot... I figured a new windows install would get it to work. In my opinion, if you can rule out windows 7 as the problem, you're going to have to start looking at the kf as the possible cause. I haven't had stock on my device in a while, but if i was in your shoes... I would try a factory reset. Maybe even try to get it to reflash the stock software. I think you can download the kf software from amazon, rename it update.zip and put it at the root of /sdcard or /sdcard/kindleupdates and reboot to initiate a flash.
If none of that works, you might want to build/buy/borrow a factory cable. Then you can flash a new bootloader/recovery and try a rom to see if you can get adb working with that.
Click to expand...
Click to collapse
this worked! This worked! This worked! This worked! Thank you a million times!!

b63 said:
you need two drivers:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
according to your screenshot the kf is not recognized by adb
what are the status lines if you start kfu ?
should look like:
ADB Status: Online
Boot Status: 4000
Click to expand...
Click to collapse
ok .. I'm taking it with me to the office. That's a Win7 Pro machine, but I'm thinking about trying a restoration to factory defaults like Carlos.

Mattb4rd said:
ok .. I'm taking it with me to the office. That's a Win7 Pro machine, but I'm thinking about trying a restoration to factory defaults like Carlos.
Click to expand...
Click to collapse
A factory reset isn't going to hurt, but you are in a different boat than Carlos. Based on your screenshot of the Device Manager, it looks to me like your computer is recognizing the device correctly and loading the right drivers since it says "Android Phone -> Android Composite ADB Interface" when it's hooked up. For whatever reason, KFU is not able to push the required files onto your device and get it into fastboot mode. I suggest taking KFU the middleman out of the picture and seeing what adb tells you when you try to use it directly. Try something simple like "adb devices" on the command line and see what you get. You'll have to use the command line to run the adb program located in the tools directory of KFU.

[Q] KF drivers work but still cant get ADB working?

I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks

xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1552547
The second post will help you to get your device drivers in order.

xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
Which version of KFU did you try running.. suggest you try the KFU 0.9.6

my drivers are working. when i plug my KF in i see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
im also using 0.9.6
i plug my kf into my pc, that above screenshot is what i see so i dunno whats going on?

Did u run the first option to reset the boot mode to normal or fast..
If u run this option u can set ur boot mode appropriately and then root it using option 2 which is burrito root installation
Sent from my MB526 using Tapatalk 2

kinfauns said:
http://forum.xda-developers.com/showthread.php?t=1552547
The second post will help you to get your device drivers in order.
Click to expand...
Click to collapse
kishorev said:
Did u run the first option to reset the boot mode to normal or fast..
If u run this option u can set ur boot mode appropriately and then root it using option 2 which is burrito root installation
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
no i never did that...how do i got about that? im horrible at this, apologies.

xXezmacXx said:
I'm trying to use KFU to root, I'm on 6.3.1. I went into device manager on windows and it says "android phone > android adb interface" every time I plug my KF in. So I'm guessing my PC is recognizing it? When I try to open KFU to root it doesn't show up, it still says "adb status: offline". Anyone know what I'm missing? - Thanks
Click to expand...
Click to collapse
I'll see if I can help. The description of what you are seeing in the device manager "android adb interface" matches the picture in the upper right box in the table you posted. That is the fastboot driver, look at the description in the left column of the table. ADB doesn't work with the fastboot driver. You need to keep playing with drivers until you get the "normal" ADB driver working, see the listing in the lower right box of the table. The word "composite" must appear in the driver description for your computer to recognize your KF as an ADB device. KFU includes and installs both drivers but windows is easily confused and frequently uses the wrong one. Personally I think it is because the KF goes through different modes as it boots up and windows isn't accustomed to a device changing modes, but that is just my guess.
Sent from my Amazon Kindle Fire using xda premium

xXezmacXx said:
no i never did that...how do i got about that? im horrible at this, apologies.
Click to expand...
Click to collapse
Have uploaded some screenshots for you on checking your driver and also how to run ur KFU
Let me know if u were able to succeed

i try adding the drivers again and it says its up to date already. i have no idea what im doing wrong but im sure is something easily fixable. should i press "disconnect" when i plug the kf in or should i leave usb cable screen up?

xXezmacXx said:
i try adding the drivers again and it says its up to date already. i have no idea what im doing wrong but im sure is something easily fixable. should i press "disconnect" when i plug the kf in or should i leave usb cable screen up?
Click to expand...
Click to collapse
Yes, you have to disconnect mass storage to enable debugging.

soupmagnet said:
Yes, you have to disconnect mass storage to enable debugging.
Click to expand...
Click to collapse
sorry for the stupid ? but how do i do that?

edit: i got rooted following this guide: http://forum.xda-developers.com/showthread.php?t=1638452
for some reason KFU doesnt work for me.

Fastboot USB does not work

Hello
i have a problem. When i connect my phone to my computer with Fastboot. My phone says "FASTBOOT USB" and 15 sec later I get this error and my phone says "FASTBOOT"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone is on Fastboot mode. Adb and Fastboot driver are installed. Please HELP me!

evildog1 said:
Hello
i have a problem. When i connect my phone to my computer with Fastboot. My phone says "FASTBOOT USB" and 15 sec later I get this error and my phone says "FASTBOOT"
My phone is on Fastboot mode. Adb and Fastboot driver are installed. Please HELP me!
Click to expand...
Click to collapse
Windows 8/8.1 has had issues with using devices in Fastboot mode. Luckily, a fix is already available. Follow the instructions in the thread linked below and make sure you have the drivers installed and HTC sync removed
http://forum.xda-developers.com/htc-wildfire-s/general/driver-finally-how-to-fastboot-to-t2857536
Click to expand...
Click to collapse

This method does not work

evildog1 said:
Hello
i have a problem. When i connect my phone to my computer with Fastboot. My phone says "FASTBOOT USB" and 15 sec later I get this error and my phone says "FASTBOOT"
My phone is on Fastboot mode. Adb and Fastboot driver are installed. Please HELP me!
Click to expand...
Click to collapse
Here is your solution: http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx

evildog1 said:
This method does not work
Click to expand...
Click to collapse
Have you installed the drivers for the phone? Because the only reason for it to not work is the unavailability of the drivers

csoulr666 said:
Have you installed the drivers for the phone? Because the only reason for it to not work is the unavailability of the drivers
Click to expand...
Click to collapse
I have installed the HTC drivers and enter FASTBOOT again but the word "FASTBOOT USB" disappear without any errors on Windows 8.

evildog1 said:
I have installed the HTC drivers and enter FASTBOOT again but the word "FASTBOOT USB" disappear without any errors on Windows 8.
Click to expand...
Click to collapse
And what about HTC sync, is it installed as well? Also try to use a newer version of fastboot just in case(if you haven't updated it in some time)

csoulr666 said:
And what about HTC sync, is it installed as well? Also try to use a newer version of fastboot just in case(if you haven't updated it in some time)
Click to expand...
Click to collapse
@evildog1: If you have usb connection in recovery mode your drivers are ok. Please read my previous link on this page for solving the problem in windows 8.1.

Marcel1962 said:
@evildog1: If you have usb connection in recovery mode your drivers are ok. Please read my previous link on this page for solving the problem in windows 8.1.
Click to expand...
Click to collapse
i successfully flashed custom recovery with my old computer running Windows 7.
when i connect my device to my computer running Windows 7 without any HTC drivers, the word "USB" did not disappear from Fastboot and it always says "FASTBOOT USB". i installed HTC Drivers and run Fastboot flash and it worked perfectly.
On Windows 8. without any HTC Drivers, it tells me that there was something wrong with the USB. After i installed HTC Drivers and run Fastboot again, the word "USB" disappear from Fastboot screen without any errors.

SW3 not recognized by ADB while in fastboot mode

EDIT: Solved
Before you ask, yes, I do have USB debugging on, and I do have ADB and fastboot drivers installed. I'm running Windows 10.
The ADB shell is working well while the watch is in "normal" system mode, but after I boot it into fastboot with the "adb reboot bootloader" command, it's no longer recognized by my PC. "adb devices" brings up an empty list, and entering any command at all gets ADB stuck at < waiting for any device >.
What do?

Instead of adb use
Code:
fastboot devices -l

ranf said:
Instead of adb use
Code:
fastboot devices -l
Click to expand...
Click to collapse
I mean I did that, sorry for being unclear.
Anyway, it was a Windows 10 driver issue. Apparently you have to manually specify via Device Manager that the watch uses Android ADB while it's in fastboot mode.

[NUMINIT] said:
I mean I did that, sorry for being unclear.
Anyway, it was a Windows 10 driver issue. Apparently you have to manually specify via Device Manager that the watch uses Android ADB while it's in fastboot mode.
Click to expand...
Click to collapse
Hi,
I have the same problem, how did you solve it in WIN 10 ?
Ferdinand

fmcheetah said:
Hi,
I have the same problem, how did you solve it in WIN 10 ?
Ferdinand
Click to expand...
Click to collapse
If I recall correctly, the watch showed up as an unknown device while plugged in in fastboot mode. It's just a matter of identifying it (unplug & plug in and see which one reacts) and manually pick "ADB device" or some such from the manual update settings.

I am having a problem with this also. After having many android devices and other OS's......this is the first time I have been unable to get the correct drivers to be able to see my watch file system on my Win7 PC....and Win10 laptop.
Here is what I get when trying to update the driver with ADB debugging enabled in on watch as well..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here are my choices available:
I get stuck selecting the right choices and all lead to the same "code 10" cant find/install driver.

RR215 said:
I am having a problem with this also. After having many android devices and other OS's......this is the first time I have been unable to get the correct drivers to be able to see my watch file system on my Win7 PC....and Win10 laptop.
Here is what I get when trying to update the driver with ADB debugging enabled in on watch as well..
Here are my choices available:
I get stuck selecting the right choices and all lead to the same "code 10" cant find/install driver.
Click to expand...
Click to collapse
This is probably a dumb question, but it never hurts to make sure: you do have the drivers installed, right?

That is my problem....I dont see it in the available list. I have several other android devices in use with no problems, also have the Sony PC Companion 2.1 on my PC and use that.
I am actually not in OP's situation actually now that I re-read the thread over. This is in normal boot mode. How do i get the correct driver for the watch from here.
Thanks for your help.

Otter 1st gen bricked

So I'm wondering anyone can help Ive got a 1st gen and it's bricked it was rooted with custom firmware and had twrp installed i was flashing new firmware and was on twrp I wiped something can't remember what as it was months ago and since then device won't turn I've tried using a fast boot cable but my pc keeps saying its an unrecognised device I've tried using Linux aswell but no such look any ideas any help is appreciated thanks in advance

What does the tab say?
Can you access twrp?

Kenora_I said:
What does the tab say?
Can you access twrp?
Click to expand...
Click to collapse
Can't access anything just get a black screen nothing loads atm might aswell be a wedge to keep the door open I'm trying on a diffrent pc no but installing adb drivers I'm getting an error fail to write 0x1949 hoping if I fix that maybe I'll be a step in the right direction

Does fastboot commands work?
Can you try booting to fastboot

sd_shadow said:
Sounds like a driver issue
Sent from my Moto E (4) using Tapatalk
---------- Post added at 08:54 AM ---------- Previous post was at 08:51 AM ----------
See
https://forum.xda-developers.com/showpost.php?p=54123148&postcount=1
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse

Nothing at all work I connect it to the pc try turning it on and it goes be bop bop be over and over again so it's connecting disconnecting connecting disconnecting etc I've drived downloading the drivers off amazon directly it installs then says at the end something like it's installed but incorrectly or may need rebooting

lsngregg said:
Howdy all, I have an old KF here that I have bricked. I'm stuck at the logo. I'm trying to issue shell commands and I get the "- exec '/system/bin/sh' failed: No such file or directory (2)" error. So far I've found that this means I screwed up my /system when I tried getting this thing back to stock. I cannot remember what I was running on it earlier today.
I do know that I downloaded a factory update.zip and installed that from TWRP. I wiped everything before hand. I'm afraid wiping the SD card after installing the update.zip may have caused me to be stuck at the logo without being able to issue shell commands? I've tried the KindleFireUtility and KindleUnbrickUtility and a few things with soupkit. Nothing is working.
I seem to have found a few hints that there are indeed workarounds to this problem without having to make or buy a factory cable. I'm terrible at soldering.. much better at typing in terminals.
If there is any help out there, I would massively appreciate it.
All I want to do is read a d*** book.
-Ellison
UPDATE:
I bought a fastboot cable.
It appears that I can boot in to fastboot mode (Kindle Fire logo, green light, and screen never dims) but I think at some point, the device gets lost. I installed the android bootloader ADB drivers for the fastboot mode. If I start the kindle without the factory cable and it boots normally and sits at the logo screen forever, it gets listed as an ADB device. While the kindle is still attached, I can reboot it in to what I am assuming is fastboot mode. My Windows10 rig sees it as a composite ADB bootloader interface. But I can't get unBrickUtility to do anything... the only thing I saw it do to the kindle was wipe the userdata. Other than that, UnBrickUtility cannot see my kindle in fastboot mode.
Unplugging my factory cable and plugging it back in causes the kindle to be completely unrecognized ( unknown usb device set address failed) on Windows 10.
I have soupkit running on a netbook... it tells me that my shell is damaged, which I know is the problem. But now I'm not sure what to do next as I can't get linux (mint) to recognize my kindle in fastboot mode either.
I really hope someone out there has been here before and can help. I'd love to see this thing running back to normal again.
related image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE: I FIXED IT.
What ultimately saved this device was being able to get in to fastboot mode. I bough the cable, flashed FFF and TWRP from fastboot mode. I then found I could not run shell commands. I fixed this by running
Code:
fastboot oem format
from fastboot mode. Then going back in to TWRP, I was able to mount /System and was then able to use Soupkit's kindle fire utility to fix the /sdcard. The version of TWPR I was using would not flash the stock update, so I downloaded and flashed that. Afet that installed, I was able to flash the stock update and now I'm up and running again! WOO! Thank you so much for the developers here!!!
Admin: can I get the thread title so reflect the fact that I have fixed this for future users? Thank you!
Click to expand...
Click to collapse

It's driving me nuts been trying to fix it on and off for ages still get no where the pc has the drivers installed but just connects and disconnects every tool I've tried says it either waiting for device or can't find device

Try the tools mentioned in above post