Related
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App
EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...
perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes
Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.
Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.
Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...
What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.
try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.
Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever
It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.
buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip
No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.
**BUMP**
Anyone care to take a shot??
Hi all...bare with me here, I posted this earlier, but in the wrong forum section so I am going to start over here.....thanks for your patience....
Hi everyone...I have a problem..I tried to use the Firerat zips to increase my internal storage, and during the flash of the zip file the phone hung and I had to pull the battery out.....since then the usb wont mount.
I am using a Tmobile mytouch slide 3g.
I tried using the sdk and running the fastboot commands etc to get the sd card to mount...no go.
I have tried the fastboot oem enableqxdm 0 command and no go....
Note:..My sd card works fine in a card reader on my computer, I can drag and drop anything to it etc. etc.
Finally i downloaded the stock rom, and i was able to put it on the card, and rename it ESPRIMG.zip and installed it through recovery...My phone was rooted and S-off running ginger, but now back to stock...S-on, and hating the phone now...lol.....
I have been all over the web and I am so confused...everywhere you search there is something different, I just dont know what to do, Windows doesnt recognize the phone when plugged in so I cant load custom rom etc back on....AARGH!!!..I am so frustrated, and have a migraine messing with this damn thing.....lol...
Someone here suggested the MISC is bad and that a binary flash_img would fix it, but honestly, I have no idea what any of that means...all that means to me is confusion, and I have that already.....lol
Can someone please suggest what I may try doing?I am pretty savvy with computers but some of the adb/shell stuff is very confusing to me, I dont like cmd prompts...so maybe a detailed explanation?..
Thank you so much for taking your time to read my problem, I really appreciate it very much.....Dirtylarry
"Kharma...It's a good thing"
ok man im gonna try to understand the problem... you say your usb mount doesnt work but the sdcard works with the adapter, then you went back to stock and un-rooted and the pc doesnt recognize your phone? right?
So it looks to me (just an idea) that the problem is your cable or the port on your pc... just beacuse your sdcard IS working in your phone as well since you used the ESPRIMG.zip(wich was really unnecessary) and you flashed it using the sdcard obviously.
Now you need to find a way to root it again just like you did the first time... dont mess with the drivers since you havent changed them in your pc (i guess) and try this guide....
http://richard.gluga.com/2010/08/complete-guide-to-rooting-and-hacking.html
Now all i can say is ALWAYS DO A NANDROID BACKUP BEFORE MESSING WITH YOUR PHONE. And check the cable/ports... thats the only problem i can think of...
well the fact that I have 3 computers that all used to recoginize the phone just fine is what's weird....none of them do, nor does my usb connection on my car stereo...the computers all say "USb not recognized" etc. etc. and the car stereo says USB N/A .......So i'm just at a loss as to what is going on here....Any ideas????? Thanks much ....Dirtylarry
Try installing PDA Net. It installs USB Drivers and resets the registry. One day it would work, then the next day it didn't work, reinstalling PDA Net worked every time.
Thanks Wave_Sailor, I tried the pda net install but it wont work....Everytime I try it says that it can't handshake to the phone, and then gives me an error code 103, I have tried many many times....also, in the device manager for computer it shows a yellow Exclamation mark everytime I plug the phone in listed at "Other Devices", and says Qualcomm CDMA Technologies MSM....So I googled, and found another thread saying Install Windows mobile 6 center, so I did, and nothing changed.......ARGH....DIrtylarry
Do part III, but while the phone is unplugged, download and install HTC Sync, and then plug the phone back in.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Ok...I did EXACTLY what you have suggested, and in the driver information box this is what I got after the install....
USB Composite device installed successfully
USB Mass Storage Device Failed
Mytouch slide tmobil installed successful
Still a no go on the Mass storage device......hmmm.....so weird of a problem to have....I would have thought that clearing everything on the phone and going back to stock would have done the trick......any more ideas?...Thanks so much for your help.....Dirty
Have you checked in device manager on your computer to see if the mass storage device has a yellow triangle? I just went through the same thing but in reverse. My pc would see the sd card while in my phone but not through the reader. I still haven't gotten it straightened out either, just learned to live with it.
dirtylarry10 said:
Ok...I did EXACTLY what you have suggested, and in the driver information box this is what I got after the install....
USB Composite device installed successfully
USB Mass Storage Device Failed
Mytouch slide tmobil installed successful
Still a no go on the Mass storage device......hmmm.....so weird of a problem to have....I would have thought that clearing everything on the phone and going back to stock would have done the trick......any more ideas?...Thanks so much for your help.....Dirty
Click to expand...
Click to collapse
Make sure you don't have any drivers disabled. Ran into that problem with a different phone. I had one driver disabled so it wouldn't install some of the other drivers.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Ok...just checked,...no drivers disabled in device manager...has to be something wrong with phone...its a/most like the driver is missing from within the phone or something...isn't there some way to get this back to where I could root it and install a custom rom again without the USB to phone connectivity and use my card reader to get some sort of files back onto phone that way?
ok....well I re-did the whole flash process over, and I am now rooted again once more.....I dont know how or why or what...but I am now going strong again.....lol thanks for the help everyone,
A few of you know me already from my thread where I asked a million questions before attempting to install a custom ROM on my new KF. Well, it still went completely south somehow, so here I am.
So, I'm stuck with the stock Kindle Fire logo on the screen, and and can't get it to go anywhere.
Here's what I did:
Downloaded KFU, installed the drivers, plugged in the Kindle,and ran KFU. ADB status online, boot status 4000.....so everything seemed good, from what I've learned. Also looked in Device manager, and it showed up as Android phone, or whatever it's supposed to say. I figure I'm good to go.
My plan is to install TWRP,FFF, and root it, then boot into TWRP, and flash the ROM. The first thing I did(and it seems wrong now) was try to install FFF, instead of TWRP. I think that's the wrong order, but not totally sure if it matters, but it's my assumption that it does.
So, as soon as I sent the command, for some reason, my computer got this blue screen with some message that I didn't have time to read, because it restarted right after. It still said everything looked good, so I tried again to install FFF. I think the "crash" was just coincidental, because it didn't act like that the second time, but whatever.
Anyway.......said it was installing FFF, and then it went to <waiting for device>
I figured ...ok...need to wait.
After about 10 minutes of waiting, I held the power button down until it turned off, then turned it back on, because someone said that's what you should do if this happens. Well, essentially.....since then, I've not seen anything but the Kindle Fire logo on the screen, and it feels like I've tried everything. A forum member spent some time on the phone with me, and we tried everything he knew.....no luck.
At one point, someone told me to uninstall the drivers and reinstall them, which I did, but upon reinstalling them, nothing changed, and the computer no longer even recognizes it being plugged in as a USB device, the drivers don't show now in device manager, even though I told KFU to reinstall them. To me that's weird, and seems like a major problem, because the computer isn't "seeing" the device, but that's mu humble opinion. I'm at a total loss, and would sure appreciate some help bringing this thing back.
Thanks....immensely, in advance!
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
If nothing you do results in any change, it's time to give up on Windows and create a Linux LiveUSB. Linux is extremely stable and pretty easy to set up and send adb/fastboot commands with. If you do decide to take that route, Ubuntu is pretty much the standard and version10.4 generally works better than later versions.
soupmagnet said:
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
Click to expand...
Click to collapse
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
soulweeper51 said:
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
Click to expand...
Click to collapse
Use the KFU on the laptop to install the drivers and see if that makes a difference.
soupmagnet said:
Use the KFU on the laptop to install the drivers and see if that makes a difference.
Click to expand...
Click to collapse
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
soulweeper51 said:
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
Click to expand...
Click to collapse
Yeah, that's what I meant.
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
kinfauns said:
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
Click to expand...
Click to collapse
I just did exactly what you said......plugged it in, turned it off. Turned volume all the way up, turned it on....no sound of any kind.
The weird part is when I first installed the drivers, I checked it by plugging the device in, and had adb status online, staus 4000, plus I went to the device manager, and I remember two things that said android phone. One said android phone, and the other said android something or other. And, it was seeing the device and everything seemed hunky dory, and I guess at that time it was???
I did uninstall and reinstall the drivers via KFU, and it says it's installing them, but never again have I seen anything in device manger that says Android anything. That is just wrong to me.
Personally I think you're spinning your wheels with Windows and causing yourself more headache than needed.
Create a bootable Linux LiveUSB on a thumb drive with Ubuntu 10.4 and get Android-SDK installed on it.
[Edit:]fixed spell check fail
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first.
Click to expand...
Click to collapse
Trust me.....I realized not too long after that I had done the wrong order. I even had a note to myself right here that said:
TWRP
FFF
Root
For the life of me, I don't know why I did FFF first.
All the questions I asked, and as anal retentive as I am, I totally screwed that part up, which may be the entire problem. Trust me.......I'm pissed.
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
Click to expand...
Click to collapse
Can I ask what Firekit is?
Firekit is a tool used to fix major problems easily. I would use it as a last resort because there isn't a command for just installing TWRP without the bootloader.. Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
soupmagnet said:
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
Click to expand...
Click to collapse
I'll just be honest and tell you that I have no idea what you're talking about. I don't mean that in a bad way.......I'm not some computer whiz that speaks the same language as a lot of you. Right now I wish I had left the freakin thing alone with Go Launcher Ex and called it a day. I'm really pissed off right now....that's not your fault.
I don't suppose that Factory Cable will do anything for this situation, correct? The guy said he will send it ASAP FWIW.
Had to ask.
soupmagnet said:
Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
Click to expand...
Click to collapse
Can you kindly tell me how I get to the point you're speaking of?
Sorry....this stuff is foreign language to me.
Do I have to install ubuntu on my computer?
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
soupmagnet said:
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
Click to expand...
Click to collapse
Should I trust this method?
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
I know NOTHING about this.
EDIT: Never mind.......that's another OS......damnit!
Can't I just play dumb, and send it back? I hate to say that, but.....
I guess this is it
http://www.linuxliveusb.com/en/download
^See.......trying as hard as I can to keep a good attitude.
That will work. Download Ubuntu 10.4
Hello,
I successfully rooted my Kindle Fire last year and a few months ago I decided to flash ICS on it. It worked perfectly and I've had no issues so far on it except for one thing that is driving me nuts.
I had downloaded a couple albums and a few magazines on my Kindle and I wanted to get them on my PC. So I proceeded to plug my Kindle as usual and I heard the USB sound on the PC. I checked My PC and my device did not appear there. I checked Device Manager and the ADB Composite thing did not appear either, it now says Amazon Kindle Fire with the yellow exclammation mark.
I suppose somehow the drivers got uninstalled or something, so I tried installing the drivers again... Which is another nightmare because first of all, I'm on Win XP and my computer is in Spanish. So when I double click on the drivers thing it doesn't work. And now when I try to manually install the drivers it won't let me.
I have no idea what to do now, maybe someone can help me with this. I'll be so grateful for any help you guys can give me! :crying::crying:
KindleTrish said:
Hello,
I successfully rooted my Kindle Fire last year and a few months ago I decided to flash ICS on it. It worked perfectly and I've had no issues so far on it except for one thing that is driving me nuts.
I had downloaded a couple albums and a few magazines on my Kindle and I wanted to get them on my PC. So I proceeded to plug my Kindle as usual and I heard the USB sound on the PC. I checked My PC and my device did not appear there. I checked Device Manager and the ADB Composite thing did not appear either, it now says Amazon Kindle Fire with the yellow exclammation mark.
I suppose somehow the drivers got uninstalled or something, so I tried installing the drivers again... Which is another nightmare because first of all, I'm on Win XP and my computer is in Spanish. So when I double click on the drivers thing it doesn't work. And now when I try to manually install the drivers it won't let me.
I have no idea what to do now, maybe someone can help me with this. I'll be so grateful for any help you guys can give me! :crying::crying:
Click to expand...
Click to collapse
When I flashed CM10.1 I needed to download "google android usb drivers" or something...
sghsmorgan said:
When I flashed CM10.1 I needed to download "google android usb drivers" or something...
Click to expand...
Click to collapse
Yup, I've tried every possible solution out there and nothing has helped.
kindle fire not found after cm10
KindleTrish said:
Yup, I've tried every possible solution out there and nothing has helped.
Click to expand...
Click to collapse
Trish: First, I am presuming you are working with a first gen Kindle fire?
I am pretty sure the problem is that the cm10 build is not using the 0x1949 kindle vendor ID and your drivers do not know what to do.
I am not entirely sure how to modify your USB driver ini files but, if you were to install something like USBDview, which lists usb attachments to your PC or, if you were in LINUX for certain and listed the syslog (which prints out all activity on ports basically), you would see a USB connection each time the tablet is connected but, the VID is no 0x1949 but, 18D1. 1949 is the VID for Kindle and I was told that 18D1 is the VID for google devices.
If your PC was set up and configured to work with google devices, I think you would be OK.
I had one person indicate their machine was configured to recognize either Kindle on Google Vendor IDs.
C:\Users\"your user name"\.android\adb_usb.ini
The file normally has 0x1949 listed in it which is the VID for Kindle.
Once cm10 is loaded the VID may no longer 0x1949.
I once tried to add 0x18D1 to the .android/ adb_usb.ini file located in the users base folder but, I did not have any better luck.
This issue happens quite a bit and there are lots of posts indicating that the PC will not recognize the tablet after loading one rom or another or just getting the tablet into one boot mode or another.
galearned said:
Trish: First, I am presuming you are working with a first gen Kindle fire?
I am pretty sure the problem is that the cm10 build is not using the 0x1949 kindle vendor ID and your drivers do not know what to do.
I am not entirely sure how to modify your USB driver ini files but, if you were to install something like USBDview, which lists usb attachments to your PC or, if you were in LINUX for certain and listed the syslog (which prints out all activity on ports basically), you would see a USB connection each time the tablet is connected but, the VID is no 0x1949 but, 18D1. 1949 is the VID for Kindle and I was told that 18D1 is the VID for google devices.
If your PC was set up and configured to work with google devices, I think you would be OK.
I had one person indicate their machine was configured to recognize either Kindle on Google Vendor IDs.
C:\Users\"your user name"\.android\adb_usb.ini
The file normally has 0x1949 listed in it which is the VID for Kindle.
Once cm10 is loaded the VID may no longer 0x1949.
I once tried to add 0x18D1 to the .android/ adb_usb.ini file located in the users base folder but, I did not have any better luck.
This issue happens quite a bit and there are lots of posts indicating that the PC will not recognize the tablet after loading one rom or another or just getting the tablet into one boot mode or another.
Click to expand...
Click to collapse
Thank for your response. I wasn't running CM10 on my KF 1st gen when I had this USB problem. To be honest, I don't even remember what's the name of the ROM I was running. All I have to say is that it was a very poor ROM, very unstable and it was missing a lot of features. For instance, when I went to Settings > Storage I would have no option to turn on the Mass Storage option.
I was so frustrated with this USB issue since I couldn't find a solution or help anywhere, so I decided to flash CM10.1 on my KF and now I have a very stable tablet. When I first tried to connect it to the pc after flashing, the PC didn't recognize it either. But at least I have the mass storage option in Settings > Storage.
Either way, the PC still doesn't recognize my tablet as an Android Phone. But I can get files from my KF to PC and vice versa.
KindleTrish said:
Hello,
I successfully rooted my Kindle Fire last year and a few months ago I decided to flash ICS on it. It worked perfectly and I've had no issues so far on it except for one thing that is driving me nuts.
I had downloaded a couple albums and a few magazines on my Kindle and I wanted to get them on my PC. So I proceeded to plug my Kindle as usual and I heard the USB sound on the PC. I checked My PC and my device did not appear there. I checked Device Manager and the ADB Composite thing did not appear either, it now says Amazon Kindle Fire with the yellow exclammation mark.
I suppose somehow the drivers got uninstalled or something, so I tried installing the drivers again... Which is another nightmare because first of all, I'm on Win XP and my computer is in Spanish. So when I double click on the drivers thing it doesn't work. And now when I try to manually install the drivers it won't let me.
I have no idea what to do now, maybe someone can help me with this. I'll be so grateful for any help you guys can give me! :crying::crying:
Click to expand...
Click to collapse
Some ROMs just don't seem to work with Windows PCs. The latest CM/SG7 one works fine (early versions did not, the ones from around May going forward do). If all else fails, I've never had an issue getting USB to connect when using TWRP's option. A minor inconvenience, but there it is.
KindleTrish said:
Thank for your response. I wasn't running CM10 on my KF 1st gen when I had this USB problem. To be honest, I don't even remember what's the name of the ROM I was running. All I have to say is that it was a very poor ROM, very unstable and it was missing a lot of features. For instance, when I went to Settings > Storage I would have no option to turn on the Mass Storage option.
I was so frustrated with this USB issue since I couldn't find a solution or help anywhere, so I decided to flash CM10.1 on my KF and now I have a very stable tablet. When I first tried to connect it to the pc after flashing, the PC didn't recognize it either. But at least I have the mass storage option in Settings > Storage.
Either way, the PC still doesn't recognize my tablet as an Android Phone. But I can get files from my KF to PC and vice versa.
Click to expand...
Click to collapse
zerbey said:
Some ROMs just don't seem to work with Windows PCs. The latest CM/SG7 one works fine (early versions did not, the ones from around May going forward do). If all else fails, I've never had an issue getting USB to connect when using TWRP's option. A minor inconvenience, but there it is.
Click to expand...
Click to collapse
This has been talked about several times, but for some reason no one ever seems to catch on.
You have to check the hardware IDs reported by your device in the Device Manager for every ROM you install, and make sure the information matches whatever is listed in your 'adb_usb.inf'.
My kindle fire 2 rooted was working fine until I launched this program called GOLauncher. I didn't like it and tried to uninstall it, but the darn thing wouldn't remove and the the next time I turned on my kindle, all I would get was a flashing loading screen. Nothing else. I soon thereafter discovered (when the 1-step program I had previous successfully used about 10 times before) would go no further that daemon starting. I noticed that instead of a Kindle in my device manager, there was now only a Portable Device with E: showing as active.
I've tried every solution I could find from here, but 90% of them assume you have the whole driver .exe to install or some other such stuff. Every driver that doesn't, doesn't work for my computer, and won't put the kindle device back on my computer. So now, I have no way to communicate between my kindle and my computer, which I need to do frequently.
I've uninstalled each adb between installs, I've tried all the drivers I can find, I've deleted hidden devices (there were no kindles there either)
Plus, I can't get these apps I installed on the third party sites (which I miss) to uninstall. All they say is "move to favorites" in both my app folder and in the cloud. I am assuming it's because I no longer am able to access those sites.
Could someone please help me? I'm pretty computer literate, except where it comes to DOS commands. Sigh, the one thing I didn't learn in high school.
I promise I've been spent the last 5 days and nights (and even restored my device to factory settings just to get it to work) searching through so many pages of this site that I'm starting to get confused. Will someone please help me?
OK lemme get this straight, you are stuck in a boot loop at the kindle logo and want adb access but nothing is showing up( except maybe a portable device)? If its showing up as a portable device during a boot loop that strikes me as odd, usually you don't have adb access during a bootloop , much less and mtp connection. If it's stuck in a boot loop you will typically need a fastboot cable to get out of it. Also what os are you running? I might be of more assistance after I get a better idea of what your kindle is doing exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK lemme get this straight, you are stuck in a boot loop at the kindle logo and want adb access but nothing is showing up( except maybe a portable device)? If its showing up as a portable device during a boot loop that strikes me as odd, usually you don't have adb access during a bootloop , much less and mtp connection. If it's stuck in a boot loop you will typically need a fastboot cable to get out of it. Also what os are you running? I might be of more assistance after I get a better idea of what your kindle is doing exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
This is what happened. I installed a program from the Google Play store, wasn't happy with it, and botched the uninstallation. I was messing around on my computer to see how I could fix the problem (after just rooting hubby's kindle fire 2nd generation and discovering I had not ADB drivers and my device manager wasn't recognizing my requests). I notice that once again the kindle is missing on device manager when plugged in to the computer. What is showing up is a Portable Device labeled E:. So I go looking for answers here.
One of the things I noticed I could do with the broken kindle was that about 1 out of 5 times it was on, I could swipe the top of the screen and have the settings menu come up. And out 1 out of those 5 times, I could actually get a setting to appear by pressing on it. So I literally spent 17 hours trying to time the swipe, press, press to get the restore to factory settings program to work. And when it finished, I had a useable device, but all the kindle programs were gone (they were still on my cloud) and I could run all the programs installed from other android stores (but I can't uninstall them). And, of course, I can't get my computer to recognize the device. But I do have program called file manager that allows me access to shared files on my family's three computers so I can transfer files over the LAN if I need to.
I hope that helps. Thanks for taking the time to help me.
I am running an Intel i5 with 64-bit Windows 7 Home Premium Service Pack 1. It has all Microsoft updates and it is my pristine baby that I bought 18 months ago (my last computer was 9 years old that I built with an AMD processor and an 17 and 20 GB hard drives that were donated to me. It was a real POS, but it's still running to this day as a backup.
I know the feeling, before i got my new laptop from a friend a few weeks ago i had a pc with a pentium 4 and 2gb of ram, and like 3 hard drives. Anyways I'm assuming at this point you want to try restoring the system partition? Have you tried the drivers in my signature for adb access? If you can reboot into fastboot you could restore the system image from kindle fire first aid, should fix any problems with the os. It all depends on if USB debugging is turned on on your kindle, and if you can get the PC to detect it as such, usually I would just uninstall the MTP device and try searching for drivers on the new device detected and point it to my drivers.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Have you tried a factory reset?
--》Sent from my mind to your screen
mindmajick said:
Have you tried a factory reset?
--》Sent from my mind to your screen
Click to expand...
Click to collapse
Thanks for both of your information. I did get the ADB drivers to show up - in the most stupid of ways. I changed from by brand new monster gold plated cable to a Wal-Mart special. Suddenly, everything worked perfectly! I use KFFirstAide to restore the device to the #1 setting, and then rooted it using the #23 setting. I also installed the Google Play store (though I installed the wrong, more complicated, version of if the first time.
Now I have a problem I can't see to fix. Ever since I got everything set up, there are certain programs on my kindle (cloud and device) that I can't get rid of. They are No Lock, Talk, News & Weather, Majic Locker, Google Voice, and Gl Launcher HD. I've tried downloading both ES Task and File Manager and deleting or startup disabling these apps, and while they say they are deleted, they reappear back on the active list as soon as I turn on my device (yes, I've rebooted), but I can't get them off my kindle Apps pages. And Go Launcher starts up every single time I turn on my device, and I hate this program, because it is not what I was looking for. Now I always have to look at it.
These .apk's are all in the system/apps folder. That's why I've tried to use the above file apps to get rid of them.
Also, my Silk browser doesn't work (I can open it and it immediately closes), and while I know I can download dolphin browser or firefox, I want the browser built for tablet speed and efficiency. Plus, when I had multiple browsers before, I always got the popup asking me which app I wanted to use to perform that function. But I can't find an apk for silk anywhere, and my device won't uninstall Silk.
Can anyone help? I feel so stupid about the cable issue. You wouldn't think a 3 day old cable would not properly transfer data.
OK to fix your launcher, go into the setting>apps and find go launcher and clear its defaults. That's kinda unspecific but I haven't been on amazon os for a while. To get rid of system apps, use es file explorer, enable root access, if on the older version, mount the system, if you have a panel on the left its the new version. Anyways from there you can simply hold down on the app and hit delete. Not too sure why silk isn't on the list. Though I though I might say consider this, you have no way of using flash with silk, so other browsers are kinda useful because you can. Then again I like flash. Kinda sounds like silk got deleted.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Not entirely true
stunts513 said:
OK lemme get this straight, you are stuck in a boot loop at the kindle logo and want adb access but nothing is showing up( except maybe a portable device)? If its showing up as a portable device during a boot loop that strikes me as odd, usually you don't have adb access during a bootloop , much less and mtp connection. If it's stuck in a boot loop you will typically need a fastboot cable to get out of it. Also what os are you running? I might be of more assistance after I get a better idea of what your kindle is doing exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have gotten several tablets to respond to ABD commands while soft bricked or not booting all the way. This is actually how I became an authorized MID repair facility. I have repaired a few kindle's that would only boot the to logo. If the device is loading as portable device, go to device manager, update driver for portable device, manually update the driver to whatever ADB driver you have extracted and it should at least respond to adb wipe command. once done you should be able to use the KFU to restore the tablet to factory state.
At least this is the process that has worked for me several times.