I've installed 2nd bootloader + TWRP + cyanogenmod for my kindle fire 8.9 hd, but now the device isn't showing up on my computer (windows 7 64bit.) It starts to install drivers but says "unidentified device" and fails. I looked around in settings on the actual tablet and couldnt find anything relevant. Is it possible I need to turn on adb debugging on the tablet again, and if so, where is it located in CM10.1?
I've tried rebooting and reinstalling adb drivers on my computer, but no dice.
It detects as a PTP device, but doesn't show up when I change it to MTP. adb devices doesn't list anything.
Any help would be greatly appreciated.
konasus said:
I've installed 2nd bootloader + TWRP + cyanogenmod for my kindle fire 8.9 hd, but now the device isn't showing up on my computer (windows 7 64bit.) It starts to install drivers but says "unidentified device" and fails. I looked around in settings on the actual tablet and couldnt find anything relevant. Is it possible I need to turn on adb debugging on the tablet again, and if so, where is it located in CM10.1?
I've tried rebooting and reinstalling adb drivers on my computer, but no dice.
It detects as a PTP device, but doesn't show up when I change it to MTP. adb devices doesn't list anything.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Yeah I had that problem just a few days ago. Turns out you just go to the setting and about section and tap the build number a few times to enable the developers options in setting. Then you will be able to select adb debugging.
AlexAquarium said:
Yeah I had that problem just a few days ago. Turns out you just go to the setting and about section and tap the build number a few times to enable the developers options in setting. Then you will be able to select adb debugging.
Click to expand...
Click to collapse
Sweet, that was really helpful. Now the device shows up in adb devices, but not in windows. I can't send or receive files.
This is really frustrating. You'd something something as simple as "how to connect cm10.1 kindle to computer" would be documented somewhere, but I cant seem to find it.
konasus said:
Sweet, that was really helpful. Now the device shows up in adb devices, but not in windows. I can't send or receive files.
Click to expand...
Click to collapse
Never had an issue not showing up in windows especially if the "adb devices" cmd now works in your windows. That seems odd. Maybe you should connect your kindle to pc and enter windows device manager under portable drivers and uninstall the kindle driver. Window will reinstall the driver once you disconnect and reconnect the kindle.
I have the exact same problem with my KFHD8.9 since I rooted and installed CM10 two days ago.
I also have Win 7 64, and I also can use it as PTP but not as an MTP (USB debugging is on).
I've tried installing and re-installing both ADB drivers provided here. Countless times I've tried to: reboot Kindle, restart my PC, removing unrecognized drivers in device manager and then reinstalling them when the Kidnle connects via USB.
I've even tried installing the Android SDK files with no success.
So far, I've spent more than 7 hours trying to fix this.
The closest I've gotton, was to manually direct the broken Kindle Fire HD driver in device manager to update via the ADB driver located in Program files (x86) folder- then it showed the kindle as being connected under the "safely remove hardware" icon in the notification area and showed as a working driver in device manager, but even then, the MTP won't work and won't show the Kidnle in my computer.
One of the most frustrating things about it is that I connected the Kindle to a 7 year old laptop we have and it was
recognized immediately in "my computer". So I know this means something is wrong with my laptop that
prevents it from being recognized.
Anyone have a suggestions? A solution?
After more than 7 hours trying to figure this out, I would really appreciate your help!
did you solve this?
I just flashed CM10.1 and have the same problem
Try this:
Disconnect kindle
Go to device manager
look for kindle
uninstall
connect kindle
I see that a1745 has tried something like this, but these USB drivers are really flaky. Worth a try.
You can also try toggling MTP mode.
Settings -> storage -> the 3 cube icon on the upper right -> USB computer connection -> and try toggling MTP.
Cronoss said:
Try this:
Disconnect kindle
Go to device manager
look for kindle
uninstall
connect kindle
I see that a1745 has tried something like this, but these USB drivers are really flaky. Worth a try.
You can also try toggling MTP mode.
Settings -> storage -> the 3 cube icon on the upper right -> USB computer connection -> and try toggling MTP.
Click to expand...
Click to collapse
thanks, it works now
Related
Hello, guys,
I recently rooted my Fire (6.2.2) with Kindle Fire Utility (0.9.3). Kindle is working but my PC (Win7 32) can't recognize it when i'm connecting kindle to PC. And Kindle Fire Utility can't connect to device since then (statusffline).
Maybe I forgotten to switch to normal mode?
How can I fix this?
Thanks.
talcegie [616
With your Kindle plugged in and with KFU (even if it says it is offline), press 1 for Bootmode Menu and select Normal.
meturne2 said:
With your Kindle plugged in and with KFU (even if it says it is offline), press 1 for Bootmode Menu and select Normal.
Click to expand...
Click to collapse
I tried to do this. Got the message "kindle told to reload in normal mode". Kindle reloaded but the problem left.
Sounds like you may have to reload your drivers. Is the computer recognizing the Kindle at all. I had the problem when trying to load files to the SD card that it would not show up as a storage device. I unchecked USB debugging and it showed up. If you are trying to establish an ADB connection you may want to check your ADB setup.
Try cd C:\kindleadb
adb devices
This will tell you if your ADB connection is working.
Maybe this video will help.
http://www.youtube.com/watch?v=_C-H3epEHjo
meturne2 said:
Sounds like you may have to reload your drivers.
Click to expand...
Click to collapse
I tried to reinstall drivers from Kindle Fire utility few times. No result. Is there any way to wipe them from system?
meturne2 said:
Is the computer recognizing the Kindle at all
Click to expand...
Click to collapse
Unknown Device in device manager
meturne2 said:
Try cd C:\kindleadb
adb devices
Click to expand...
Click to collapse
Gives empty output. I'm using adb bundled with Kindle Fire Utility
The same thing happened to me and I just deleted all the files that were associated with the ADB and KFU and reloaded everything. Before you do that you can go into device manager and pull up the properties for unknown device(kindle) go into update drivers and point to the file you downloaded when installing KFU.
I used this video to root mine and the part on installing the drivers works. Make sure you download the driver files attached to the video. Look under "show more" --Links in the video description.
Hope this is helping and not making you more confused.
http://www.youtube.com/watch?v=KapnjR89ICA
The problem solved. It was Windows drivers problem. I've got a USB-stick in another slot during all operations. When I removed it everything worked normally. My motherboard is Asus P5G41T-M.
Thanks to everybody who tried to help.
Kindle not recognized by PC
meturne2 said:
The same thing happened to me and I just deleted all the files that were associated with the ADB and KFU and reloaded everything. Before you do that you can go into device manager and pull up the properties for unknown device(kindle) go into update drivers and point to the file you downloaded when installing KFU.
I used this video to root mine and the part on installing the drivers works. Make sure you download the driver files attached to the video. Look under "show more" --Links in the video description.
Hope this is helping and not making you more confused.
/QUOTE]
-------------------------------------------------------------------------------------------------------------------------
I have attempted several different fixes to get my rooted KF recognized by PCs running VISTA and XP to no avail. My KF is looping TWRP v2.0.0, so I have concluded. Yet if not PC can recognize it as a device...well, please give me your thoughts and suggestions.
Thx,
R
Click to expand...
Click to collapse
Did you try again with the latest utility?? Coz it shd work..
Sent from my MB526 using Tapatalk 2
Here`s my suggestion http://forum.xda-developers.com/showthread.php?t=1882565
Hello,
I've been able to use ADB to install and test apps that I'm writing under the stock ROM for my Epic, as well as under CM9 (and I think an early CM10, not sure about that though). After installing the 20130101 build of CM10.1 (keeping the included kernel), I am having issues trying to deploy and debug apps from my any of my computer to the phone (all of which previously worked). I've verified that Android Debugging is still enabled on my phone.
In the device manager on my computer, "SAMSUNG Android USB Modem" and "Unknown Device" are both showing the "problem" icon. I've tried uninstalling and reinstalling various versions of the Samsung USB drivers, I've tried a few versions of Kies, and even a few third-party tweaked USB drivers. It doesn't seem like anything wants to recognize my phone now that is running CM10.1 (or CM10.1 in addition to something peculiar with my installation).
Additionally, if I have USB debugging enabled on my phone, even if I enable USB mounting, the computer won't recognize the mount until I disable debugging mode on the phone. Once I do that, then the volume will appear on my computer. Previously, when ADB debugging in general worked, I wouldn't have to disable debugging to get the USB mass storage mounting to work.
These problems happened at once on all three of my computers that I've been using for Android development, so I'm fairly convinced these issues are directly related to the ROM I'm running. I've attempted to search the forum and Google for others that may have had this issue and what the resolution/work-around might be, but so far I've not found anything. Surely other people are using CM10.1 and developing apps, which makes be believe it could be something unusual with my installations, but I've tried full wipe without a data restore and it didn't seem to have any impact. I've also tried searching to see if there were special drivers needed for CM10.1, and didn't find anything with that either. I know reverting back to an earlier ROM is an option to get ADB working, but I'm really hoping to get ADB working with CM10.1.
Does anyone have any suggestions on what I can check/do to get USB debugging working on CM10.1 (epicmtd)?
Thank you very much for your time
--James
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
I had the same problem, tried absolutely everything I could to get it to work and couldn't... had to roll back to a tw rom to get it to work (not a fan of the HUGE battery drain on cm9)
Edit- I know this doesn't help you, just wanted to point out you're not the only one with this problem....
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
jeffreyjicha said:
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...
flastnoles11 said:
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...
Click to expand...
Click to collapse
I've tried this with my previous uninstall/reinstall driver attempts, but tried it again anyway.
Unfortunately, it didn't' seem to have a positive impact. It looks like it reinstalled the mass USB storage driver, but it did not reinstall any other drivers (like the modem driver) so I'm still not able to do anything with ADB.
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Have you tried manually installing the drivers?
Here is the .exe that I used to install the drivers for my phone.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Have you tried manually installing the drivers?
Click to expand...
Click to collapse
Hello again. Yes. I've tried installing various versions of USB drivers floating around the net as well as Kies (after uninstalling and deleting current drivers to try to avoid conflicts). Other versions of Epic ROMs (Stock, CM9, etc.) worked with ADB using my installed drivers until I installed CM10.1 (maybe starting with CM10) on my Epic.
As an aside, using ADB requires some additional (special) drivers beyond the drivers required for mass storage support.
I'm hoping one of the CM10.1 developers will chime in with what they did and/or installed to have ADB working with CM10.1 on Windows 7.
Thanks!
--James
I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.
jeffreyjicha said:
I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.
Click to expand...
Click to collapse
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
No problem.
samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
Activating through developer options doesnt help? just go to about phone --> tap build number 7 times
I just went to device manager, uninstalled the failed USB device, and then plugged the phone back to the computer via USB.
Boom, just like that, all was well.
i tried everything and could not connect to my htc rezound (w/ CM10.1) thru adb. then i tried the following:
1. download the android adk from google (i can't post links)
2. connect phone thru usb
3. on your computer's adk download folder, navigate to sdk\platform-tools\
4. press shift + right click on the window, open command window here
5. type "adb devices" in the command window w/o the quotes
6. there should be a window pop up on ur phone asking for USB debugging permission. say OK.
7. type "adb devices" again and you should see ur phone connected thru adb.
I've never had a problem with android file transfer up till I rooted today. My wife has a stock Nexus 7 and I can plug her Nexus into my computer and the file transfer app will start. I have usb debugging turned on and the usb connection on my tablet is set to Media device.
Now as I'm typing this my Nexus has been connect to my mac for about an hour. I just went to the USB settings to make sure I had Media device selected and the file transfer window popped up out of nowhere. I killed it and tried again and it won't come up. Maybe in an hour or so if it does the same thing.
Any ideas as to what's going on? Very strange behavior.
Disable USB debugging.
Unplug/plug in your nexus.
The USB IDs change for some reason when you have USB debugging turned on and the MTP device isn't recognized as such. PTP (camera) mode continues to work for both cases though.
Thanks for the suggestion but It still fails. I disabled debugging and still can't connect. Switching USB modes didn't help either.
If that doesn't work uninstall the adb driver & then plug your tablet back in so it will reinstall
My next suggestion would to reboot the tablet with USB debugging turned off.
If that doesn't work, my next suggestion would be to delete the existing drivers and force reinstall.
All with USB debugging turned off.
johnnyninja said:
I've never had a problem with android file transfer up till I rooted today. My wife has a stock Nexus 7 and I can plug her Nexus into my computer and the file transfer app will start. I have usb debugging turned on and the usb connection on my tablet is set to Media device.
Now as I'm typing this my Nexus has been connect to my mac for about an hour. I just went to the USB settings to make sure I had Media device selected and the file transfer window popped up out of nowhere. I killed it and tried again and it won't come up. Maybe in an hour or so if it does the same thing.
Any ideas as to what's going on? Very strange behavior.
Click to expand...
Click to collapse
Make sure after you plug in your device you're looking at your tab and click OK on the pop up........
Sent from my Nexus 7
Thanks for all the suggestions. It's working now. I was just about ready to delete the driver and the tablet started to be recognized consistently. I was in the settings screen and toggled debugging on and off while plugging in the tablet. I noticed the info bar at the top alternating between showing "debugging" and "media device" and I selected each one a couple of times when they came up. I think that it finally worked through the ID confusion that was mentions. I'll follow the the rest of the instructions if the problem comes back.
Thanks again.
It's acting up again so I'm going to try deleting the drivers. I thought I knew what to do but I can't find any information. What's the procedure to delete the driver? I'm running os x lion
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
I'm not sure how I finally resolved the problem on my mac. I toggled debugging on and off and rebooted a couple of times. That may have done it. I also ran the adb script in the SDK platform-tools folder. I don't know what that script does exactly but possibly it reinitialized the driver and ID.
Anyway, hopefully these workflows will work for others.
johnnyninja said:
I'm not sure how I finally resolved the problem on my mac. I toggled debugging on and off and rebooted a couple of times. That may have done it. I also ran the adb script in the SDK platform-tools folder. I don't know what that script does exactly but possibly it reinitialized the driver and ID.
Anyway, hopefully these workflows will work for others.
Click to expand...
Click to collapse
Rooted my nexus 7 (2012) last night and struggling with my laptop not recognizing it. This thread solved it!
Delete the ADB on my window, toggle off debugging and restart the nexus 7 with usb connected to laptop. works like a charm.
Thank you!
Guys, my N4 got this problem too.. until just a few minute ago
I read somewhere ini goge groups (i think N5 group), and found explanation that we can change ADB or MTP "mode" on device manager. On "Androoid ADB Device" right click and select "Update Driver Software". Click "Browse My Computer for Driver Software" and then "Let me pick from blablabla...." And then select MTP USB Device, "next" and my N4 detected on Windows Explorer.
Hope it will be usefull for you guys.
Hey guys. I been here for like 4 hours just dabbling with everything. And cannot seem to find any solution to this...
I have uninstall all drivers and restarted like ten times now doing the same process over and over, cleaning up each file carefully of the nexus or any android device.
My problem is when i plug in my nexus 7 2nd gen, it seems to not even detect squat.
I have usb debug enabled
my MTP is on
( if i switch to PTP i can access the folder)
Ive done fresh start on everything i even look through device and try changing the option to MTP and STILL DOES not work
I don't even see my nexus 7 in my HDD external or anything, nothing pops up but an ADB success driver, and when i changed it to MTP a MTP success driver with STILL no luck....
I just bought it today and it worked fine earlier, now when i root it and stuff it seems to be glitchy with my MTP
I even factory reset everything i couldn't access my ADB
any help would be appreciated
Someone said that manually updating the adb usb driver in devices should show you a choice, choose mtp. It should then sort itself out properly.
n9900229 said:
Hey guys. I been here for like 4 hours just dabbling with everything. And cannot seem to find any solution to this...
I have uninstall all drivers and restarted like ten times now doing the same process over and over, cleaning up each file carefully of the nexus or any android device.
My problem is when i plug in my nexus 7 2nd gen, it seems to not even detect squat.
I have usb debug enabled
my MTP is on
( if i switch to PTP i can access the folder)
Ive done fresh start on everything i even look through device and try changing the option to MTP and STILL DOES not work
I don't even see my nexus 7 in my HDD external or anything, nothing pops up but an ADB success driver, and when i changed it to MTP a MTP success driver with STILL no luck....
I just bought it today and it worked fine earlier, now when i root it and stuff it seems to be glitchy with my MTP
I even factory reset everything i couldn't access my ADB
any help would be appreciated
Click to expand...
Click to collapse
On your Nexus, open "settings", click on "Storage", click on options(3 vertical dots on the top right corner), click on "USB PC Connection", now check MTP option.
Try connecting to your PC (or Mac) now. I didn't have to do that on a stock build, but for some reason I had to do it on a couple of custom roms. Hope it helps ya out...
Try enabling USB debugging. I know it sounds odd but its helped me with my devices.
Sent from my Nexus 7 using Tapatalk 4
do this only if you can see PTP on PC
On PC check device manger, on Android if there is ADB driver - uninstall it
On N7 set to MTP, debug off and reboot with N7 USB cable connected to PC
It should re-install the ABD drivers on PC before N7 fully boots up
You will be back in action.
n9900229 said:
I have usb debug enabled
my MTP is on
Click to expand...
Click to collapse
Actually for me, it's the opposite. If usb debugging is on I can't access the device to view files. Try disabling it?
yea thanks though everyone I got it to work. I had my old nexus and new drivers mixing up my ports for some reason not being able to access it at all
Hi all,
I've got a Kindle Fire, which was rooted quite a while ago. More recently, I had the 5 second bootloop, so I took the kindle apart and charged the battery directly by cutting apart a micro usb cable. This worked and now the device powers on, but is stuck on the logo. I previously had all my drivers set up for kindle, and ADB was working properly, but now it shows up as an unknown device. I have tried reinstalling my entire Android SDK, with Amazon's repositroy added, and have uninstalled the drivers on the Kindle, so that only the Amazon ADB drivers remain. Still, I am unable to connect with ADB, and the device still shows up as "Unknown Device" and fails to be noticed by Windows7, or ADB.
Can anyone point me in the right direction please? Thanks!
P.S. I've tried the KFU.
lobwege said:
Hi all,
I've got a Kindle Fire, which was rooted quite a while ago. More recently, I had the 5 second bootloop, so I took the kindle apart and charged the battery directly by cutting apart a micro usb cable. This worked and now the device powers on, but is stuck on the logo. I previously had all my drivers set up for kindle, and ADB was working properly, but now it shows up as an unknown device. I have tried reinstalling my entire Android SDK, with Amazon's repositroy added, and have uninstalled the drivers on the Kindle, so that only the Amazon ADB drivers remain. Still, I am unable to connect with ADB, and the device still shows up as "Unknown Device" and fails to be noticed by Windows7, or ADB.
Can anyone point me in the right direction please? Thanks!
P.S. I've tried the KFU.
Click to expand...
Click to collapse
install drivers that are included with KFU
then
In Device manager>select unknown device>Update driver software>
browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>
show all(uncheck show only compatible)>look for ADB interface or android phone
select yes to Ignore warning
may need to reboot both.
Sent from my XT907 using Tapatalk
+1 to above response. Tell windows to look for similar installed drivers and choose the ADB interface drivers.
Thank for the quick response. I tried what you told me, and I notcied that when I plugged the Kindle in, and listing of "Android phone" popped up in device manager. It then immediately disappeared. After a little dinking around with the cable, I found that the micro usb port on my Kindle in loose on the inside. It wasn't making a proper connection. So I'm charging it right now with the cable slightly angled in the device. Thank you for the help anyways!
Any ideas what I could do to fix the loose port? Solder?
soldering should fix it, several YouTube videos on it.
Sent from my XT907 using Tapatalk