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??
EDIT:
So I got it rooted, but MTP still won't work on my laptop, but works on my friends laptop What drivers does the first method install? I thought about upgrading them to official drivers. But when I tried to do that, it says I'm already running the latest drivers... Should I uninstall them and try to manually re-install these?
dud3me said:
EDIT:
So I got it rooted, but MTP still won't work on my laptop, but works on my friends laptop What drivers does the first method install? I thought about upgrading them to official drivers. But when I tried to do that, it says I'm already running the latest drivers... Should I uninstall them and try to manually re-install these?
Mods feel free to delete as this doesn't require it's own thread!!
Click to expand...
Click to collapse
See if the following method fix your device, anyway it fixed mine, btw mine was running cm10.2
1) Go to system settings--->>storage
2) Choose USB computer connection on the upper-right corner
3) Have the MTP option checked.
4) Try connecting your device to the computer usb port again.
sontjer said:
See if the following method fix your device, anyway it fixed mine, btw mine was running cm10.2
1) Go to system settings--->>storage
2) Choose USB computer connection on the upper-right corner
3) Have the MTP option checked.
4) Try connecting your device to the computer usb port again.
Click to expand...
Click to collapse
Tried that on PA, no luck
Sent from my GT-I9100 using xda app-developers app
No one? Has anyone had any success with cm10.2 compared to stock based roms like PA?
me neither, can't even install the adb driver probably, although i've tried every way the nrt or nexus toolkit told me. T_T
with/without usb debugging, with/without mtp connection, using different usb ports, still no luck. Last thing i haven't tried is to connect n7 to another computer
This fixed it for me: http://forum.xda-developers.com/showthread.php?t=2390296
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
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
mdamaged said:
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
Click to expand...
Click to collapse
Didn't work, followed your steps in the other thread. I guess I'll just have to wait until a flashable zip for L :/
edit- And btw I tried it on both of my hard drives, one with windows 8 and one with windows 7, didn't work on either.
C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
wantabe said:
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
Click to expand...
Click to collapse
Thanks mate, didn't work though so I'm not sure what is going on. I'll just wait until zips get created but thanks for the help guys.
Dropped phone, broken screen/digitizer, doesn't respond to touch
Was able to see the screen a bit yesterday but now its almost all black. I mainly just need my photos off it. Tried an RMA to replace the screen but they said they had to wipe everything first
Is there any way I can pull the photos off it? I haven't tried an otg yet, but I also can't see the screen, so im not sure it would help
Is there a screen sharing program I could get w/o first installing it on my phone?
I think my phone may be rooted, i forget if i ever did, but i dont have TWRP installed on it? (i dont super know what that is but i see other people talking about it)
Any thoughts on how to pull photos off it? I tried the adb devices but the cmd prompt doesn't seem to recognize the phone
Im quite sure I have debugging enabled, just coudln't get the file transfer button hit
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Ok cool, how would i go about sorting the drivers? o.0
jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
side note.... wth is this image verification lol, ive tried like 30 of them, why is it so hard to post lol ><
Click to expand...
Click to collapse
Sorry, can't give definite answer, I know that I had an issue with drivers (device wasn't properly recognized) and tried pretty much everything that Google suggested ... Until it finally started working. I have no idea exactly what solved the issue, it was over a year and a half ago. The next time I clean installed Windows (10 in both cases) it was smart enough to automatically find right drivers.
So ... I'm guessing Googling something like "OnePlus 3 Windows # drivers" should find something useful?
About image verification: are you talking about anti-bot system that checks if you're human? Wouldn't know much about that, never personally had issues with it, but also very rarely see it on XDA as I'm nearly always checking this forum in Tapatalk app.
Sent from my OnePlus 3 using Tapatalk
jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
Click to expand...
Click to collapse
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
tnsmani said:
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
Click to expand...
Click to collapse
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Had the same issue with my Lenovo P2. Only i didn't have debugging enabled. If you have, screen mirroring should be an easy solution. You could just see ur phone screen on ur computer that way. What helped me was to forceboot the phone to recovery with the hardware buttons, then connect it to ur pc. TWRP will automatically launch MTP. When u backed up evrything, you can wipe ur device through adb
jsaden said:
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Click to expand...
Click to collapse
I don't know about Win 7. It will work on Win 10. Most likely, this should not be needed in Win 7 at all as the drivers should install whether signed or not.
Regarding copying data, a simple command of "adb pull /sdcard" will copy all the folders, files, data etc to your PC. You can also specify where you want the data copied to, simply add the path to the command above. This will work whether your screen works or not. Of course, there are other methods of copying data, you can search for it if you need it.