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??
I have no option for usb data transfer. Just MTP and PTP. When trying to drag and drop I get "Calculating the time required to copy the files". It copies nothing.
Airdroid, wifi explorer, kies doesnt transfer a damn thing.
ANY HELP IS APPRECIATED!
Make sure that your drivers have been installed properly, first off (I think this is a big problem for a lot of ppl). And on the phone, in Settings > Storage > Menu > Computer Connection > "Media device (MTP)" is checked. (I also believe unchecking "USB Debugging" in Developer options can help, too).
If your drivers are set up, you should get a prompt (assuming you're on Windows 7) to "open folder and view files" and you'll get an Explorer window. Just drag/drop files on the device.
You can also use a WiFi FTP transfer app (I wanna say AirDroid is a popular one?). Some prefer it this way.
How can you tell if the drivers have been installed properly?
I can drag and drop one file at a time but nothing more
jgarozzo said:
How can you tell if the drivers have been installed properly?
Click to expand...
Click to collapse
If you plug your phone in and don't get an error. And in device manager it should show up as "Galaxy Nexus" or "Samsung Galaxy Nexus".
jgarozzo said:
I can drag and drop one file at a time but nothing more
Click to expand...
Click to collapse
Sounds like a possible issue with your setup. I just recently re-installed a fresh 32bit Windows 7 install on my MacBookPro, and without any driver tweaking or anything I was able to connect and drag/drop files back and forth.
I do have issues with my desktop and plan on wiping it.
jgarozzo said:
I do have issues with my desktop and plan on wiping it.
Click to expand...
Click to collapse
MTP can be finnicky but there's no technical reason why it can't work just fine (as I said it works perfectly for me and others here).
Have you tried something like AirDroid (linked above)? Or if you're just sitting on WiFi you can always just upload to DropBox (Google Drive) and download on the phone/PC.
airdroid hasnt worked for me. I'm not positive but I think there are certain files that won't transfer via cloud.
jgarozzo said:
airdroid hasnt worked for me. I'm not positive but I think there are certain files that won't transfer via cloud.
Click to expand...
Click to collapse
Should be able to transfer anything. Don't see any restrictions to it.
Is your Kies properly Installed?
Hi,
If your Samsung Kies was properly installed (means took quite time for installing Driver for Samsung devices). Your phone should be detected once connected via USB cable. Some devices may have different situations. Exp. file transfer in SamsungGalaxyTab10.1 will not display exact time for file transfer Window. Once device connected via USB cable, and Your device's Name Pops Up in your window, means it's successful. Transfer shd not be problem.
Sometimes, Phone may not the cause, perhaps ur Pc/laptop might limited capability for Kies Support.
If your case is different, perhaps you can uninstalled and reinstalled it in control panel. Uninstalling Kies will not remove ur Phone's Driver data. Hope this Helps.
Sincerely,
whitefang
**** takes forever to transfer via usb. is this a known issue on the nexus or just me? I have never had a phone with issues in transfering data. I'll give a clous service a try again. I appreciate your help
jgarozzo said:
**** takes forever to transfer via usb. is this a known issue on the nexus or just me? I have never had a phone with issues in transfering data. I'll give a clous service a try again. I appreciate your help
Click to expand...
Click to collapse
It's a known "issue" that people have really funky PC setups and have issues installing drivers. It's not inherently a technological problem with MTP or the Galaxy Nexus. As I said before, it's just a bit more finnicky than USB Mass Storage (UMS), which is used on most other phones.
I'll keep referring to the fact that on a bare Windows 7 install, with no previously installed drivers, I was able to plug in my Galaxy Nexus, auto-install drivers, and xfer files back/forth without a hiccup... that'll give you an idea for where the problem lies
http://forum.xda-developers.com/showthread.php?t=1523691 try this it has wifi sync using it all the time
ive got windows 7 ultimate, no issues, works as it should
whitefang3456 said:
Hi,
If your Samsung Kies was properly installed (means took quite time for installing Driver for Samsung devices). Your phone should be detected once connected via USB cable. Some devices may have different situations. Exp. file transfer in SamsungGalaxyTab10.1 will not display exact time for file transfer Window. Once device connected via USB cable, and Your device's Name Pops Up in your window, means it's successful. Transfer shd not be problem.
Sometimes, Phone may not the cause, perhaps ur Pc/laptop might limited capability for Kies Support.
If your case is different, perhaps you can uninstalled and reinstalled it in control panel. Uninstalling Kies will not remove ur Phone's Driver data. Hope this Helps.
Sincerely,
whitefang
Click to expand...
Click to collapse
Kies is NOT supported on the Galaxy Nexus.
jgarozzo said:
airdroid hasnt worked for me. I'm not positive but I think there are certain files that won't transfer via cloud.
Click to expand...
Click to collapse
Like martonikaj said, you should be able to transfer everything wirelessly. It's probably your fastest bet.
I either do that, or use ADB. While it's not as fast, I find it to be more stable than MTP (but that could be just me).
I assume download files as a zip and then open them on the pc? I assume all I would have to transfer would be titanium backup since it contains all app and system data. I know some of my questions might seem silly but i want to make sure i dont loose any data.
I've tried downloading the samsung drivers on 3 different pc with 3 different operating systems and cant get the drivers to properly load. I'm a little upset with Samsung at the moment. I never had a problem wit HTC or Moto phones.
you can use Alt Mounter app on mac & windows
go to goole & search it
then download AltMounter.apk & install it to your phone
then download altmounter for windows & install it to your pc
after that run altmounter in your pc & also run altmounter in your phone
after that plug the usb cable . the phone storage shows up in a window
this is verys simple & i like it
you can use it if you have problems with MTP
I'll give it a shot, thanks!
Hi, So I have the sg3 T999V with Wind and I updated to jelly bean via kies today.
So I did lose root and cmw
but I used the root66 way of rooting it after the upgrade and it worked.
However, after the upgrade I encounter the MTP device not working problem.
I first unchecked usb debugging mode and it worked for a brief moment but then proceeded to not being recognized by my computer again
I have windows 7 32bit
So this is what I tried:
1) regedit described on this forum - did not work, and there was no upperfilters under EEC5AD98-8080-425f-922A-DABF3DE3F69A
2) reinstall kies,driver under my computer-manager, and kies troubleshooting - always returned with MTP not installed correctly
3) factory reset one where I signed into google account right away when prompt and another left it till later, the instance where i signed in later worked until i restored system-app data with titanium backup
4) Tried all the ports on my laptop- non of which worked
5) made sure I used the usb cable that came with the phone
So I am out of ideas and having tried most of the methods suggested on the forum I don't have a next step
the reset worked well till I backed up with titanium so perhaps it is a system setting that is preventing the mtp?
Please help I use my sg3 as a music player for my long commutes and losing the MTP function would be major. :crying:
HolySafari said:
Hi, So I have the sg3 T999V with Wind and I updated to jelly bean via kies today.
So I did lose root and cmw
but I used the root66 way of rooting it after the upgrade and it worked.
However, after the upgrade I encounter the MTP device not working problem.
I first unchecked usb debugging mode and it worked for a brief moment but then proceeded to not being recognized by my computer again
I have windows 7 32bit
So this is what I tried:
1) regedit described on this forum - did not work, and there was no upperfilters under EEC5AD98-8080-425f-922A-DABF3DE3F69A
2) reinstall kies,driver under my computer-manager, and kies troubleshooting - always returned with MTP not installed correctly
3) factory reset one where I signed into google account right away when prompt and another left it till later, the instance where i signed in later worked until i restored system-app data with titanium backup
4) Tried all the ports on my laptop- non of which worked
5) made sure I used the usb cable that came with the phone
So I am out of ideas and having tried most of the methods suggested on the forum I don't have a next step
the reset worked well till I backed up with titanium so perhaps it is a system setting that is preventing the mtp?
Please help I use my sg3 as a music player for my long commutes and losing the MTP function would be major. :crying:
Click to expand...
Click to collapse
I have this issue on and off with my S3. It tells me my Device ID is missing. What I do is the following:
1. Download the S3 Toolkit software http://forum.xda-developers.com/showthread.php?t=1746682 and extract
2. Go to the directory you put the toolkit in and look for the drivers folder. There are two (maybe 3) files there. The USB drivers, and an application. Right click on the application, and run as administrator.
3. Make sure phone is NOT plugged in
4. Look for all Samsung related files. You may have USB component, USB modem, CAC Driver, MTP Driver, ADB driver, And a T999 Driver. highlight and click the recycle bin next to teh X on the menu bar.
5. Plug phone in, and let it recognize the components again.
6. After it is complete, it may work, or you may have to plug it in one more time for it to recognize T999 or MTP again.
7. If it doesn't work, start again, sometimes it takes a few times.
I do notice that with the Universal Naked drivers I don't have any issues, but then I can't connect to Kies. Also curious to see if your Device ID is also missing, this is the first column in the application you are running. Mine are, which I think is part of the problem, but not sure why they vanished, or how to get them back.
I don't have a solution for your windoze problem
but if I understand correctly, you need to transfer files from pc to phone
you have wifi?
both pc and phone using same wifi?
on pc.. open sharing to LAN
get ES File Explorer (or similar) from the play store
in ES, switch from Local to LAN shares
tap New.. then Scan ... your pc should show
tap it and hold, edit login parameters as necessary
tada ... now you can move files from pc to sdcard or ext sd card, no prob .. Local to LAN or vice versa
tip: I opened the 5GHz band on My dual band router and have My SGS3 connect on that band ... this achieves speeds up to 150Mbps between pc and phone instead of usual max of 65Mbps on 2.4GHz band
another file transfer method ... Dropbox
drop files on pc into Dropbox, pick them up in the Dropbox app.. or vice versa
however this will use your internet .. and whatever your monthly limit is ... twice!
once to transfer from pc/phone to Dropbox server... second time back from Dropbox server to phone/pc
the first method using wifi LAN doesn't use your internet, not limit, at all
A few weeks after rooting and installing CM10 on my GS3, it stopped recognizing any form of USB data connection. It still charges from both computer and wall adapter, but I cannot initiate a data transfer or recognize my device using ADB.
I have tried:
three different OEM Samsung cables (from SG3/SG4 phones)
all the ports on two different Win 7 laptops
all the ports on an Ubuntu desktop
enabling or disabling USB debugging
with different combinations each time. No "USB connection" dialog has shown up on the phone, and no "new device" dialog has shown up on any of the computers. I know that I can get ADB working with a different Android phone (HTC Inspire 4G) so I know that my main laptop has USB ports that work and the cables I've tried work as well, so I'm left to assume that the issue is with the GS3. External visual inspection does not suggest the USB port on the phone is damaged, and the phone is only a year old, so I don't believe that is the cause.
Is there a system setting that I may have modified on the GS3 that would disable all forms of USB communication?
(The end goal is to get at least ADB working so I can try and recover some deleted files from the internal memory; I haven't found a reliable method that does not require ADB so I'm trying to get that to work. I know that transferring files on or off can be accomplished with the external SD card or over Wifi but that is not what I'm looking for)
Any suggestions from anyone?
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
stelv said:
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
Click to expand...
Click to collapse
I don't think any OTG app like stickmount will help; I'm not trying to connect devices to my phone. I'm trying to get my computer to recognize my phone (and vice versa) in order to get ADB working.
If I can avoid flashing a RAM I'd like to, because I'm still interested in recovering those deleted files. If that is the only thing that would help, though, then I'll do it. Any other suggestions?
Install Kies and that should get the drivers for the pc in place. Odin should recognize the device when it is in the download mode. If that works, then the pc to phone connection is OK and I'd look to software instead of hardware.
Or, if you boot into your custom recovery, either CWM or TWRP, you should be able to get ADB to recognize the device and issue commands including pulling the files on Internal storage. TWRP also has a file browser built in that might be useful.
I have tried uninstalling any Samsung drivers then using the SGS3 toolkit to install the official drivers, but that didn't change anything on the PC end.
Additionally, I tried finding my device while it was in recovery using ADB and there was no connection indication either.
I currently have CWM installed, but I didn't see a mounting option like I've seen for TWRP. Can I flash TWRP without a computer?
Or try this out: Download mode>Connect via USB>Let Windows download and update all drivers until the notification in the bottom right says it's ready to use>Unplug>Battery Pull>Boot normally>connect again. Voila! It works every time when it's being wonky and its a simple way that doesn't require a bunch of downloads!
installing insecure adb might help
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
thanks
thanks
what next?
aEx155 said:
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
Click to expand...
Click to collapse
I have this same issue, in download mode, the device is still not connecting.
what is the next step? I have followed this thread and have the still have the same issues.
My rooted+bootloader unlocked LG Nexus 5x was not recognised by adb or fastboot in either Arch Linux or Windows (the latter with the proper drivers installed and the former with udev rules properly established). The device will also not show up in Windows' device manager or lsusb and the like in Arch. This was not too much of a problem until I accidentally deleted my SystemUI app from a new ROM.
The moment I realised what I had done I tried to reinstall from TitaniumBackup's restore function. That failed. I placed another copy of the apk within a folder in priv-app, assuming that I'd have no problems. I was very wrong.
On the next boot my SystemUI began crashing. My attempt to boot into TWRP required a password, which has never been the case before. I cancelled and tried to allow TWRP write access to /system. I then wiped data, cache, and dalvik during a factory reset. No luck.
Now it does not appear that my internal storage or system partitions are mounting properly, and I can't access the backup files on the sdcard. I can't sideload anything or adb push.
On a scale from one to screwed, how bad is my situation?
Not. If you have tried EVERYTHING else, download WugFresh tool kit, get into bootloader connect the USB and click the box under "unroot and return to stock" that states "device in bootloop" ,click on "unroot and return to stock" and follow the instructions. Make sure you manually select which device you are using first tho.
Edit: the tool kit has the option to install the ADB drivers, do that first (just in case). shouldnt have a problem pushing to ADB if you only messed with system files.
Boot up a live version of Linux Mint. You don't have to fart around with udev rules and adb and fastboot are packaged up and in the repos. You will have a functioning system in no time.
Sent from my SM-G930V using Tapatalk
Hehe, I was using a third party cable. Jiggled it around a bit and "adb devices" eventually returned the device's information. I just had to hold down the cable and I was able to start flashing. I'll buy a good cable soon (or wait and buy a laptop with Type C as I've been planning so that I can use the cable that came with the device).
PiArc said:
Hehe, I was using a third party cable. Jiggled it around a bit and "adb devices" eventually returned the device's information. I just had to hold down the cable and I was able to start flashing. I'll buy a good cable soon (or wait and buy a laptop with Type C as I've been planning so that I can use the cable that came with the device).
Click to expand...
Click to collapse
Glad you got it working. Test each side of the cables. Mine work better on one side than the other. The one side needs to be held in like you described but simply flipping the cable around it has a sold connection.