[Q] KF drivers work but still cant get ADB working? - Kindle Fire Q&A, Help & Troubleshooting

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.

Related

[Q][SOLVED] G2 Drivers

I am trying to install the ADB for my G2 and it won't install. I have downloaded the USB drivers, pointed the installation to my android sdk folder and it still comes back and says
Cannot Install this Hardware
I gotta be missing something here. Last time I did this was on my G1, worked fine it seemed, I followed the instructions from way back then. But it seems to be much different now.
Can someone help me with this? I Googled around, but found nothing that helped.
SOLUTION:
I modified and uploaded the usb drivers to work for the G2, these will work fine.
http://www.corylulu.com/usb_driver.zip
Click to expand...
Click to collapse
http://forums.t-mobile.com/t5/Opera...OW-TO-Get-ADB-to-recognize-your-G2/m-p/487554
You can do that or in my case I just forced the driver with Have Disk.
The above solution is more elegant.
This thread was up a few days ago and I wrote out a how to on manually choosing the drivers for mass storage and adb but it vanished somewhere and I haven't been able to find it since I pposted it. I even subscribed to the thread cause that's what I do with threads I've made posts in...
Sent from my HTC Vision
Thanks, got that working perfectly.
I can't get Windows to recognize the new driver. I updated the file as per the thread above, updated the SDK and all, but Windows keeps seeing the phone as USB only. There is an entry under Disks in device manager as HTC Android Phone USB Device, but won't update the driver because it says it's up to date already. Any thoughts?
Make sure you have USB Debugging enabled under Applications. Then select the driver manually using Have Disk.
Sent from my T-Mobile G2 using XDA App
hendusoone said:
Make sure you have USB Debugging enabled under Applications. Then select the driver manually using Have Disk.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Wow do I feel retarded ...I've been so used to my G1 that I completely forgot about the USB debugging option...lol Thanks.
On that note...
philosophics said:
This thread was up a few days ago and I wrote out a how to on manually choosing the drivers for mass storage and adb but it vanished somewhere and I haven't been able to find it since I pposted it. I even subscribed to the thread cause that's what I do with threads I've made posts in...
Sent from my HTC Vision
Click to expand...
Click to collapse
Is this the thread post you were referring to? I couldn't find it either but Google Cache found it:
http://webcache.googleusercontent.c...dating+g2+adb+driver&cd=4&hl=en&ct=clnk&gl=us
philosophics said:
Haven't been able to auto mount a portable device for some time now. Here's what you do, and this is assuming you have the android sdk complete with tools on your system as well.
-Usbdeview (find it, use it, love it)
-Uninstall all htc and android labeled devices (disconnect device/s first)
-Connect device
-Start/right-click on computer
-Device manager
-You'll see android phone with the unknown image next to it.
-Right-click it, update driver
-Let me choose/browse the preconfigured ones.
-You'll see android phone and adb something something in the list, click adb something something
-Select the qualcomm ADB composite ... one and select ok and your good to go.
If you're having problems mounting sd to pc do the same thing EXCEPT
-You'll see android phone and adb something something in the list, scroll all the way down and select universal serial bus controllers
-left column, select compatible usb device
-right column, select mass storage device and select ok
-mount sd card as usual...
When I get to my pc, I'll clean up the how to (remove the something something's along with the ...'s and replace with correct ... directories)
Sent from my HTC Vision
Click to expand...
Click to collapse
NOOB ALERT: Anyone know the correct steps to get adb working with linux(ubuntu)?
What I'ved is to follow other steps for the Vibrant replacing the vid and pid with the one from that thread but its not sticking. Any ideas?
man for the life of me i cant get this thing working at all.
does anyone have a link for the g2 adb driver? i think im going to have to use usbdeview
and now my g2 is being recognized as a usb mass storage device...
any help?
You turned debugging on right?
Sent from my T-Mobile G2 using XDA App
schwiz said:
You turned debugging on right?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I used the pdanet method. So easy even a caveman could do it lol
You don't need the G2 driver. Just force the ADB driver and it'll work just fine.
What are you talking about ? You need to go in the phone settings under applications and enable USB debugging.
sheek360 said:
I used the pdanet method. So easy even a caveman could do it lol
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
schwiz said:
What are you talking about ? You need to go in the phone settings under applications and enable USB debugging.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
i already had that checked on, but by using the pdanet app i was able to force adb to recognize the phone. if u install it on your pc, and connect your phone it will make sure u get adb. works with every phone so far. adb worked for the vibrant, slide 3g, a g1 and a n1 too. every android phone i throw at pdanet is being recognized by adb so far.
Thanks the new driver worked.
xyrcncp said:
Is this the thread post you were referring to? I couldn't find it either but Google Cache found it:
http://webcache.googleusercontent.c...dating+g2+adb+driver&cd=4&hl=en&ct=clnk&gl=us
philosophics said:
Haven't been able to auto mount a portable device for some time now. Here's what you do, and this is assuming you have the android sdk complete with tools on your system as well.
-Usbdeview (find it, use it, love it)
-Uninstall all htc and android labeled devices (disconnect device/s first)
-Connect device
-Start/right-click on computer
-Device manager
-You'll see android phone with the unknown image next to it.
-Right-click it, update driver
-Let me choose/browse the preconfigured ones.
-You'll see android phone and adb something something in the list, click adb something something
-Select the qualcomm ADB composite ... one and select ok and your good to go.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This method worked pretty well, except I chose "Google, Inc." as the category, then specifically chose "ADB Testing Interface" as the driver. Works like a charm!
USB mounting works fine automatically on Windows 7 64-bit.
{
"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"
}
Link is dead, just brings you to godaddy.

[Q] Stuck at boot!

My Kindle is unable to be detected on Kindle Unbrick and I reinstalled the drivers 9999 times and Kindle is stuck at bootlogo ! , Any Ideas how to flash the original firmware or at least bootup ?
I messed with the libandroid_runtime.so file
Can you see it in device manager?
Probably easiest to use this:
http://forum.xda-developers.com/showthread.php?t=1430038
But please, this thread should not be in the Dev forum.
Have you tried using "fastboot -i 0x1949 oem idme bootmode 4002" to enter fastboot mode when KF boots ? when it boots,there is a short time when you can use fastboot.
After entering fastboot mode,everything is so easy to save.
Gang_Jordan said:
My Kindle is unable to be detected on Kindle Unbrick and I reinstalled the drivers 9999 times and Kindle is stuck at bootlogo ! , Any Ideas how to flash the original firmware or at least bootup ?
I messed with the libandroid_runtime.so file
Click to expand...
Click to collapse
If it's a driver problem, use different drivers.
yumcax said:
Can you see it in device manager?
Probably easiest to use this:
http://forum.xda-developers.com/showthread.php?t=1430038
But please, this thread should not be in the Dev forum.
Click to expand...
Click to collapse
Thanks alooot for your response, & Sorry about the Dev forum
about the link you gave me , it needs Ubuntu and unfortunately I got Windows 7
adam900710 said:
Have you tried using "fastboot -i 0x1949 oem idme bootmode 4002" to enter fastboot mode when KF boots ? when it boots,there is a short time when you can use fastboot.
After entering fastboot mode,everything is so easy to save.
Click to expand...
Click to collapse
The adb pauses at "waiting for device" & it never pass
Disconnected it & reconnected many times but the same ;\
Zombiepiratez said:
If it's a driver problem, use different drivers.
Click to expand...
Click to collapse
3 different copies and still the same ;\
-----------------------------------------
Ugh I really feel very bad I didn't use this device only for 1 day and that happened
I have been rooting and installing custom roms on my X10 & SGSII for along time but never happened such
Please if anyone got another suggestions help ;(
Thanks everyone!
Gang_Jordan said:
Thanks alooot for your response, & Sorry about the Dev forum
about the link you gave me , it needs Ubuntu and unfortunately I got Windows 7
The adb pauses at "waiting for device" & it never pass
Disconnected it & reconnected many times but the same ;\
3 different copies and still the same ;\
-----------------------------------------
Ugh I really feel very bad I didn't use this device only for 1 day and that happened
I have been rooting and installing custom roms on my X10 & SGSII for along time but never happened such
Please if anyone got another suggestions help ;(
Thanks everyone!
Click to expand...
Click to collapse
Same happened to me. I was freaking out when it did. All you have to do is select ADB Device as the driver instead of ADB Composite Device.
Sent from my myTouch_4G_Slide using XDA App
jmcoffey said:
All you have to do is select ADB Device as the driver instead of ADB Composite Device.
Click to expand...
Click to collapse
and how can I do that ?
(I am a noob)
I found the ADB Composite Device but I don't know how to select ADB Device only ;\
I will donate if it worked
Gang_Jordan said:
and how can I do that ?
(I am a noob)
I found the ADB Composite Device but I don't know how to select ADB Device only ;\
I will donate if it worked
Click to expand...
Click to collapse
Does your computer see your kindle in device manager? If so what does it say?
Sent from my Kindle Fire using xda premium
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
pete_kowalski83 said:
Does your computer see your kindle in device manager? If so what does it say?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I did same as this
b63 said:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
Click to expand...
Click to collapse
I did it and still can't detect my device!
Sorry for being late to replay but I have exams these days :\
Any help ? ;(
that's only a loose description that you see how it is done:
if you' asked for a driver:
-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
if you'r not asked and want to update the driver:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
i to am stuck at boot, adb worked before this, fastboot never has.
i even deleted android sdk and re-installed it, still same thing. adb works, fastboot does not.
Devices and printers in normal power on: (adb working)
{
"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"
}
Devices and printers in fastboot mode: (fastboot not working)
[Update] I ran the "Tweaked KFU", option 1 and it got me out
http://forum.xda-developers.com/showthread.php?t=1454913

[Q] Cannot install clockwork mod

Used the one click el29 root and then used e4gauto, but option c, L just gets me an error:
failed to copy 'copy2sd/000root/superuser.apk -> /sdcard/000root/superuser.apk'
not a directory.
Flashed back to stock el29 and started over, same result. Any idea on how to get clockwork mod flashed onto this phone?
I'd suggest using the Odin method from sfhub (again). Download the file then use something like 7zip or Winzip to extract the actual OneClick.exe file to a folder of your choice. Then run if run it from there. Make sure you are able to boot a few times and all works (I usually use the no data file to preserve my settings). Then head over to the e4gauto etc. One thing I have found (and MANY others too!) is to make sure you use a very good USB cable. I have had SO many problems with roots/etc. because of ****ty cables! It is incredible the amount of time I've wasted when all I needed was to just get a new good USB cable! For printers, phones, cameras and other devices. Good luck
Cannot install clockworkmod
I have tried the odin method several times, both nodata and the one that cleared my settings. I have no problem with rooting. I even urooted back to stock with a factory reset and started over.
I have been using the Samsung usb cable that came with the phone. It has never failed me in the past.
It seems as though eg4auto is trying to access a directory that doesn't exist. On my phone superuser.apk is located in the system\apps directory. I think Eg4auto is looking for 000root\superuser.apk.
bgbuffalo said:
Used the one click el29 root and then used e4gauto, but option c, L just gets me an error:
failed to copy 'copy2sd/000root/superuser.apk -> /sdcard/000root/superuser.apk'
not a directory.
Flashed back to stock el29 and started over, same result. Any idea on how to get clockwork mod flashed onto this phone?
Click to expand...
Click to collapse
It appears you may have missed the pre-requisite that usb storage mode should be disable (ie the android guy should be green)
Cannot install clockworkmod
I thought of that, but you cannot get into usb storage mode when you have USB Debugging ticked. Or am I missing something here?
bgbuffalo said:
I thought of that, but you cannot get into usb storage mode when you have USB Debugging ticked. Or am I missing something here?
Click to expand...
Click to collapse
You can in fact connect to USB storage with debugging enabled.
You must have debugging enabled and USB storage must not be enabled.
Then I must be a complete idiot. if I turn on debugging mode and go to usb storage, it tells me to turn off debugging mode. If I go to usb storage first and get the green man, then go back to tick debugging mode it will not allow it until I disconnect cable.
WoW just WoW. think hard, you can do it, I have faith in ya.
How about a hint?
Well, I was messing around and hit "stop adb". Now I get a "more than one device or emulator". Reflashed el29 with odin one click, but still get the error message.
Hint, you're in the wrong mode (USB). You might want to reread the directions.
cannot install clockworldmod
Ok. Here's what I do. First make sure debugging mode is on. Then connect usb cable. I slide down the notification bar and click on connected to usb which brings me to the screen with the green guy.
At that point I run the program and get an error. What am I missing?
bgbuffalo said:
Ok. Here's what I do. First make sure debugging mode is on. Then connect usb cable. I slide down the notification bar and click on connected to usb which brings me to the screen with the green guy.
At that point I run the program and get an error. What am I missing?
Click to expand...
Click to collapse
Sounds like a bad download. Redownload try it over. report back. I actually have not used this method. I rooted with bubbys **** a long time ago and have never had to go back to stock. But I will try to help ya out.
bgbuffalo said:
Ok. Here's what I do. First make sure debugging mode is on. Then connect usb cable. I slide down the notification bar and click on connected to usb which brings me to the screen with the green guy.
At that point I run the program and get an error. What am I missing?
Click to expand...
Click to collapse
What error are you getting now? Is it the same as before or a different error?
All that part of the script is doing is using adb to push some files to your phone in the /sdcard/000root directory.
If you do "adb shell" and "cd /scard", then type "ls -l", what do you see?
If it has no files or subdirectories, then your /sdcard partition is not visible for some reason.
sfhub said:
What error are you getting now? Is it the same as before or a different error?
All that part of the script is doing is using adb to push some files to your phone in the /sdcard/000root directory.
If you do "adb shell" and "cd /scard", then type "ls -l", what do you see?
If it has no files or subdirectories, then your /sdcard partition is not visible for some reason.
Click to expand...
Click to collapse
Listen to Sfhub. He will not steer ya wrong.
Bear with me here. Do I do those commands on the phone using connectbot in local mode? If so, the adb shell command returns "adb: not found". Or do I need the developer toolkit?
When you plug in the phone as long as usb debugging is on, you shouldn't be clicking on the green android, that would enable usb mode. The files will be pushed thru adb you should not have be clicking anywhere on the green android guy.
bgbuffalo said:
Bear with me here. Do I do those commands on the phone using connectbot in local mode? If so, the adb shell command returns "adb: not found". Or do I need the developer toolkit?
Click to expand...
Click to collapse
Does your USB storage mode look like 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"
}
It should NOT be orange. It should look exactly like the picture above.
If you need to run "adb shell", use Option D, then choose adb shell. If your auto root package doesn't have "adb shell" as an option, get the latest one.
Then type:
Code:
cd /sdcard
ls -l
Yes it looks exactly as pictured. That's why I was sure it wasn't that i had the usb mode wrong. I will try your other suggestion and get back to you.
I got what looks like a directory of the sd card.
Now when I run eg4tauto I am getting daemon not running, adb server didn't ack

[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.

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

Categories

Resources