Related
This about as short as I could make it:
I haven't tried to use ADB with my G1 for about a month, so I'm not exactly sure when the problem started, but it's become a royal headache now. For whatever reason when I launched ADB shell today, I got an error saying 'device not found'. The first thing I did was check device manager where I noticed the phone showed as a 'USB composite device' with a yellow exclamation mark over it. I thought to myself "drivers." So I tried pointing it to the driver in the Android SDK folder. That just popped an error saying that Windows couldn't find a better driver match than the one I was already using.
From there I got the googling and came across this insanely long Google Groups thread. Following the advice listed, I started pulling some USB .sys files. I tried using an older copy of the USB driver from a previous SDK. I tried using Haruyko's modified USB driver. None would install.
Same error.
Reading down some more I saw that some people had success with with usinfg HTC Sync. It was worth a shot, right? Well it certainly made things different, but doesn't resolve the issue. Now in device manager I have an 'HTC Remote NDIS' listing under Network Connections. The old 'USB Composite Device' item is now gone. But still, I can't use ADB. "Device not found."
It's driving me nuts.
At this point I figured that it'd be best to try this on a different PC. Maybe my primary one is wonking out. These things happen. Well, that hope was quickly crushed when I discovered that NOT EVEN on a VANILLA XP SP3 setup, will Windows detect the G1. I downloaded a fresh copy of the SDK, plugged it in, pointed it to the USB driver....and nothing. Same error as PC number one:
"Windows can't find a better version of the driver than you're currently using."
Tried switching the USB cable. Same thing.
Back to PC number one, I removed all HTC software from 'Add/Remove Programs, then ran USBDeview. There, I removed the HTC NDIS device, unplugged the G1, and plugged it back in.
The HTC NDIS Remote device returned. **** my life.
SO.....before I throw this phone into traffic, does anyone have any clue as to what's going on here? All I want to be able to do is regain ADB access to my phone. I don't care about USB tethering (and toggling that option does nothing btw) or none of that. Just looking to regain ADB access. The only thing that's changed since the last time I used ADB is the version of Cyanogen's mod. I'm currently using v4.2.3.1. Maybe this broke shell access?
Thoughts?
**EDIT***
-Toggling USB debugging does nothing either.
-Ditto that for Fastboot
device not found has to do with the phone....make sure your cable is not messed up.
B-man007 said:
device not found has to do with the phone....make sure your cable is not messed up.
Click to expand...
Click to collapse
Tried switching the USB cable. Same thing.
Click to expand...
Click to collapse
Tried that already.
the.snks said:
Tried that already.
Click to expand...
Click to collapse
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again
B-man007 said:
is the phones usb port ok? can you transfer files over it? if your about to throw the phone away....at least try flashing the RC29 image again
Click to expand...
Click to collapse
As far as I know the USB port is ok. It charges fine. And to update everyone on where I am, I tried the following today:
-Removed all HTC software (Sync and Drivers).
-Used USBDeview to remove all instances of HTC, and Android devices.
-Tried downgrading my test machine (PC #2) to Service Pack 2.
-Tried a third USB cable.
And I'm still getting the same problem. So there's no doubt in my mind that it has to be the phone. Like I said, the only thing I've done lately is update the version of Cyanogen's ROM.
I know it definitely worked before I updated to v4.2.3.1. Also I noticed that I am no longer able to mount the sdcard as storage in Windows. I do not get a prompt on the G1 asking if I wish to mount it. However, the USB debugging notice still pops up (weird).
....and here I'm stuck once again.
Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.
rp1783 said:
Have you tried actually uninstalling the usb devices in device manager?
I was having a similar problem, I just unistalled all the usb instances in the device manager, and when I rebooted my computer, everything seemed to work fine.
Click to expand...
Click to collapse
Yes. Multiple times in fact. It can't be the computer if the same issue is happening across two different PC's, with three different USB cables.
At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stuck in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues
goldenarmZ said:
At first I thought this was a definite driver issue with xp, I've had similar problems in the past that just won't go away.. xp is a c*nt when it gets a driver stick in its head that it just doesn't want to part with... but if its persisting across several machines it could well be the phone..
Have you tried adb with the phone in recovery? Boot into recovery and leave it about 30 seconds, then plug in the usb and try to get an adb shell.. this should rule out any rom config issues
Click to expand...
Click to collapse
PROGRESS! I booted into recovery mode and plugged the G1 into the computer. I got the 'new hardware' prompt and was asked to install the driver. I did so using the one from the SDK. Now I have ADB access, and Windows tried to mount the sdcard but that failed. I'm guessing because there's no way for me to 'ok' that in the recovery console.
So what does this tell us? I'm not sure if I understand what's wrong here.
(Sidenote: Man I'm so tempted to try to install the new Google Maps now....)
the.snks said:
So what does this tell us? I'm not sure if I understand what's wrong here.
Click to expand...
Click to collapse
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd for windows when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
goldenarmZ said:
It tells us that something's cocked up with the usb support in your rom, but the phone itself is fine. wipe/reflash and you should be good to go.
There is a command you can type to mount the sd as storage when you're in recovery.. just type this in the console:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
Ah....that blows but you do what you gotta. I'll try wiping and report back in case this thread helps anyone else.
Thanks man.
Alright, here's what I did to get working again:
Doing a wipe did NOT resolve the issue. However, updating to v4.2.4 did (remember I was using v4.2.3.1 originally). For clarity, I wiped both before and after the update. And I had to use a sdcard reader to get v4.2.4 onto the phone. I can now ADB and mount the sdcard in Windows without issue. I'm not sure if this was a one off, or possibly a bug in v4.2.3.
Somebody may want to bounce that Cyanogen.
B-man007 and goldenarmZ, the help was much appreciated.
This probably is related to USB tethering Cyan put in his rom.
Also for future reference, if you want to mount your SD card in recovery and you have Cyan 1.3 or greater or RA recovery, you can just type
ums_enable
to mount and
ums_disable
to dismount
saves you from typing that hideously long line lol
Hey, i have had this problem for a bit now, but it is really starting to bug me.
I have a dual boot computer, one is fedora, the other windows 7. When i decided to root my nexus one, i did it through windows, so i got the SDK, installed the drivers and rooted the phone.
Some time later (after flashing and restoring from desire rom back to CM 5) my computer can no longer recognise the device properly Windows will say it fails to recognise the device (code 43), and will not let me re-install the drivers. Saying they are up to date even after i uninstall the drivers then re-install them.
I have given up on fedora too, since no command ever seems to work on fedora beyond yum install xxx. Trying to get "fastboot devices" in fedora brings up "command not found" or something to that effect.
I wouldn't be too worried, but not everything comes as an update.zip, and i would like to try out the undervolted kernel some time.
Note: i can still mount the SD card fine.
EDIT: i can Mount the SD on Fedora, but not windows.
Things you can try out:
1. Completely uninstall and remove the driver from the system and connect the phone and install the drive when prompted. (try in safe mode as well)
2. Try other USB ports.
3. Try turning off USB debug, connect the phone and then turn on USB debug.
4. Try on another PC and rule out any problem with ur phone.
5. Reinstall Windows!!!
Thanks for the suggestions, i tried everything there short of re-installing windows.
As soon as i plug in the device windows will bring up the error message, it will not call it a nexus one, an unknown device. Any attempt to install the new drivers and windows will say that better drivers are already installed.
I also figured out that it will not work on fedora because it is not configured, but the only guide to fastboot and linux i have found is for ubuntu, and some of the commands wont work on fedora.
I tried it on another computer, an XP, it would not install on there either, i tried to use my mums N1 afterwards to see if it would install, it didn't but there are a number of reasons why it may not.
Any other suggestions? or could someone point me to a fedora guide for fastboot?
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Uninstall the usb drivers. Not sure what there called when kies installs it
fivebraids said:
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Click to expand...
Click to collapse
I had a similar problem and it turn out that Kies hosed up all my drivers...The only way I got it fix was by totally removing any trace of Kies and then uninstalled all my samsung drivers and usb drivers and then rebooted my pc. Then I reinstalled the samsung drivers and win 7 did the rest...
Well, I haven't uninstalled Kies yet. Although I have uninstalled and reinstalled the drivers from the ODIN thread. No difference.
I even uninstalled the ODIN referred drivers and tried the drivers directly from the Samsung site. Still no difference.
I'll go ahead and try uninstalling Kies and then the ODIN drivers, reinstall the ODIN drivers and see if that helps.
I've also ordered a new cable, since I've read a few threads on other forums where the problem was bad cables. I was going to go to AT&T and get a new cable, but they want $24.99. I just ordered a pair from Amazon at $3.99 each, with free shipping!!
Thanks...off to try ridding myself of Kies...
Well, deleting Kies (and associated drivers) didn't help!
After deleting Kies, I tried both the ODIN referenced drivers, as well as those from the Samsung site. Still not working!
I guess I'll wait on a new cable and see if that helps...
Okay, I think I'm in BIG TROUBLE here!!!
New cables arrived today, but they made no difference at all! Still getting the USB Device Not Recognized message. Doesn't matter if I plug the cable in while the phone is on and select any of the connection options (Kies, Mass Storage, etc.). It gives me the same message when I have Odin running and plug the phone in while holding the volume keys.
To further add to the problem, I tried installing the Odin referenced USB drivers on my wife's laptop which has never seen this phone or Kies. SAME PROBLEM!
I'm thinking there might actually be something wrong with the physical port on the phone. But this highlights my actual problem...
How can I return the phone (for the second time) when this phone has been rooted and is running SRE 1.2.1a ?!?!?
Apparently, there's no way for me to restore this thing to stock without USB.
Any ideas/suggestions?
Relax dude--I just got a captivate a few weeks ago, and have it working on tmobile.
For the drivers, when you plug your phone in, you're getting some errors. I know you uninstalled the drivers, but to double-check, open up device manager and see if there are any ! marks for the phone. Right-click and uninstall the entries. Also, you might try using a different USB port. I can only get my phone to connect using one of the 6 usb ports i've tried. Finally, and I don't know if these are the drivers for Odin, but I downloaded these drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
When the phone connects, you might want to go to device manager, find the device(s), righ-click and and select 'update driver'. then, in the driver update window, pick 'manual' or 'let me specify location' and navigate to the unzipped SGH-i897_Captivate_USB_Drivers_5_02_0_2 file. Then, it should work.
Like I said, I have no idea if those are the drivers for odin...but I'm about to find out
I'd like to relax, but I think I'm dealing with a phone with a bad usb port...and since I've rooted, SRE'ed, etc., I won't be able to return it.
Anyway...
The driver you're using is the 'direct from Samsung' version, not the one for Odin.
Regardless, I've been through the exercise you propose...both with the Samsung and Odin drivers. When you attempt to manually install drivers, you need to point the installer to the ".inf" setup information file to use. The Samsung driver has three: SSADADB2.inf, SSADBUS.inf, and SSADMDM2.inf.
I get the following message when trying to use any of these three setup files:
The specified location does not contain information about your hardware.
Oh, and I've tried several different USB ports on the computer...both on my external hub and directly into the back of the machine.
Thanks for the suggestions, but still not working...
I'm really thinking I have a bad port on the phone...especially since trying the connection on my wife's laptop produces the exact same error.
Dam...
Still trying to find a way to restore the phone to stock without a USB connection...
i also have this "DEVICE NOT RECOGNIZED" on my sony x1.
Drivers
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
superdog404 said:
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
Click to expand...
Click to collapse
Not sure different USB drivers would help, but I went to the thread you show and tried to download the 32bit drivers. This is what I get:
{"error": "Invalid access attempt for this token"}
Oh well, thanks anyway.
I'm still thinking that the problem is hardware on the phone. I've tried four different cables, and three different computers. All show same problem of DEVICE NOT RECOGNIZED.
Still trying to figure out how to restore to stock without USB connection for ODIN so I can exchange for a new phone...
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
No modifications, same error
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
mukherji said:
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
Click to expand...
Click to collapse
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Rhiannon224 said:
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
JayPhill89 said:
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
Click to expand...
Click to collapse
USB is set to Ask on connection
Debug off or on makes no difference
All tests have been done on XP machines (3 different ones)
I'm all but positive this is hardware...
Thanks for trying to help!
Rhiannon224 said:
<snip>
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
I haven't tried ADB, but I'm not understanding how ADB would be able to connect when the connection to the computer is failing at the driver level. I guess I can give it a try tomorrow.
Thanks for trying to help!
What would REALLY help me is for someone to post a backup taken of a completely stock (ODIN'ed) phone using ROM manager. I'm thinking I could load that on the phone and then be able to return it for a new phone!
Any volunteers...please?
techmik67 said:
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
Click to expand...
Click to collapse
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
jaxf250 said:
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
Click to expand...
Click to collapse
Great!! Glad it all worked for you. My next advice is, before adding anything READ A LOT!!! =) Decide what you want from the descriptions and issues you will see in the threads....
Happy modding!!
I didn't see, I just skimmed through bit did you try to put the phone in download mode and see if windows sees that (different drivers come in to play in download mode and none of the touch wiz stuff is running)? it would test the idea of a bad port.
then you can still always install linux and use adw from there, linux and macs don't need drivers. if that doesn't work, put insurance on the phone if you haven't already then drop it in the sink and get another one.
also I think although I don't know but I think adw may have something to do with it. and incorrectly uninstalling it. first put the phone in download mode then you can work from there on ways to fix that.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Ok, I've given up trying to get this to work. I'm 100% convinced this is a hardware problem with the phone!
I had another thread going, looking for a way to restore this phone (remove SRE, SU, etc.) without usb/ODIN so I could return it to AT&T. I've figured out how to restore it to stock and will be heading to AT&T in the morning.
Thanks to everyone for their patience and assistance!
I've added a few apps to my S3 and altered a few things on my PC and now I can't connect via mtp or ptp. It goes through the usual "installing drivers" and then fails. I've tried pulling the battery and removing the sim and micro sd card then putting everything back. Tried it without the card (currently having to transfer files via a card reader so - at least the card's fine) but to no avail.
I've had a go at uninstalling the drivers through the device manager, rebooting and scanning for hardware changes. I've tried downloading the drivers without kies but it didnt work out (I cant remember the site or the url, but ended up with the following file SAMSUNG_USB_Driver_for_Mobile_Phones) It didn't auto install but even when I tried to point Windows to the folder on my C drive, nothing.
I've spent a couple of hours trawling the net including on here and tried all sorts.
I'm rooted, using the stock 4.1.2 ROM with Windows 7.
I can't use Kies as when it was installed the first time it wrecked all my Synctoy sync's so I really could do with another option please guys.
Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom.
Now select 'MTP + ADB' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now back to default USB operation.
Raistlin1158 said:
Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom.
Now select 'MTP + ADB' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now back to default USB operation.
Click to expand...
Click to collapse
Thanks for the quick reply.I did that and it was set to mtp + adb...
When I then connected it it tried installing the driver and I got..
Driver device software was not installed.
Please consult with your device manufacturer for assistance getting this device installed
MTP USB Device X Failed
I tried updating the MTP drivers again from device manager but this time got
Windows encountered a problem installing the driver software for your device
Windows found driver software for your device but encountered an error while attempting to install it.
SAMSUNG Mobile MPT Device
This device cannot start (code 10)
From what I'm reading it's a computer error not the phone. Can anyone suggest a new set of drivers to download (that doesnt involve Kies) as I've had issues with picking up harmful software from random sites when I've been struggling to find drivers.
I tried using the suggestion at the bottom of here r.e.Portable Devices and deleting the Upperfilters string Link but also to no avail.
Oh, and yes I've tried different ports and cables.
Well that's me done for the evening! I've tried everything mentioned in this thread including updating java and windows media player and all the afformentioned stuff but still no dice.
Could it be the actual drivers or a random windows 7 setting that I haven't yet tweaked since my clean install of windows??
http://d-h.st/YpV
Here are the correct drivers, install then reboot your pc.
Raistlin1158 said:
Go here for drivers.
---------- Post added at 01:00 AM ---------- Previous post was at 12:57 AM ----------
http://d-h.st/YpV
Here sre the correct drivers, install then reboot your pc.
Click to expand...
Click to collapse
Sorry,I know I'm tired but I can't see a link on your post...
Highlighted in red
The newer drivers don't really wwork with the 9305 so find some older drivers. That works for me
Sent from my GT-I9305 using xda app-developers app
Thanks for the tip.any suggestions as to where I can download these older drivers? I'll try the previously mentioned ones first, but I'm starting to think it might be the drivers themselves
woldranger said:
Thanks for the tip.any suggestions as to where I can download these older drivers? I'll try the previously mentioned ones first, but I'm starting to think it might be the drivers themselves
Click to expand...
Click to collapse
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Raistlin1158 said:
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Click to expand...
Click to collapse
Cheers, yeah, I was going to try them but I wasn't at my pc at the time I wrote that. I've downloaded the exe package but now it seems there are still drivers to uninstall - I uninstalled the drivers through device manager and went into my C drive and removed the SAMSUNG folder with the USB drivers in it. I'll restart the pc and hope that helps with the removal....
woldranger said:
I've added a few apps to my S3 and altered a few things on my PC and now I can't connect via mtp or ptp. It goes through the usual "installing drivers" and then fails. I've tried pulling the battery and removing the sim and micro sd card then putting everything back. Tried it without the card (currently having to transfer files via a card reader so - at least the card's fine) but to no avail.
I've had a go at uninstalling the drivers through the device manager, rebooting and scanning for hardware changes. I've tried downloading the drivers without kies but it didnt work out (I cant remember the site or the url, but ended up with the following file SAMSUNG_USB_Driver_for_Mobile_Phones) It didn't auto install but even when I tried to point Windows to the folder on my C drive, nothing.
I've spent a couple of hours trawling the net including on here and tried all sorts.
I'm rooted, using the stock 4.1.2 ROM with Windows 7.
I can't use Kies as when it was installed the first time it wrecked all my Synctoy sync's so I really could do with another option please guys.
Click to expand...
Click to collapse
Having the same problem. but I am on 4.3 rom using carbon rom a few days then transferred to pac man rom. My cellphone is not detected in my computer but it is being detected in the safely remove usb options. I tried to use a usb otg cable and a flash disk. No notification is seen on my phone but I can access the files on the flash disk (using usb otg cable) in the file manager. Tried the *#7284# but error occurs and says connection problem or invalid MMI code. I found that MTP udb device says failed
Raistlin1158 said:
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Click to expand...
Click to collapse
It made no difference whatsoever. I used a utility to check for an remove the samsung drivers (USBDeview) as well as uninstalling through device manager and removing with windows "products and features" but even then, when I tried installing the new drivers it mentioned previous drivers. I restarted after each stage of the process.
I've even tried connecting it in download mode and it shows in device manager.
Could there be some remnant of the software I used to root that phone that might be causing the issue??
I'm due to leave the country in 5 days and have loads of things to sort (also have a family member going into hospital for major surgery tomorrow) so I can't just devote all my time to this - but I need to at least know that it's not the phone (I dont have another win 7 computer to try it on).
woldranger said:
It made no difference whatsoever. I used a utility to check for an remove the samsung drivers (USBDeview) as well as uninstalling through device manager and removing with windows "products and features" but even then, when I tried installing the new drivers it mentioned previous drivers. I restarted after each stage of the process.
I've even tried connecting it in download mode and it shows in device manager.
Could there be some remnant of the software I used to root that phone that might be causing the issue??
I'm due to leave the country in 5 days and have loads of things to sort (also have a family member going into hospital for major surgery tomorrow) so I can't just devote all my time to this - but I need to at least know that it's not the phone (I dont have another win 7 computer to try it on).
Click to expand...
Click to collapse
Just got the same problem. But my problem is already solved. Just flash a new rom. In my instance, I flash ripper rom
I've had my L90 for about two months now, and I'm happy to have it after owning an S2 which has had a faulty USB port and crashed almost daily. The only problem with the L90 was the small internal memory. To remedy this, I bought a SanDisk 32 GB MicroSD, which arrived yesterday. It worked well, the first thing I did was put the first 5 seasons of Adventure Time onto the SD card (~13 GB of .mp4 video) in about an hour and the files played fine in MX Player. However, some problems began to arise after this.
The phone would say that it's in MTP mode, and my computer would show that it was connected, but opening it in Explorer showed me a blank window. Keep in mind that these problems began after mounting the SD card. In addition to this, any attempt to move music would end in the middle of the process because the phone would "disconnect", and any attempt to move an .mp4 file would come up with an error saying the device "didn't support" that file, despite being able to play them previously.
I have tried multiple USB ports on my computer, rebooted my phone, installed the LG drivers (which I feel haven't done anything, as they don't show up anywhere), and nothing seems to work. If anyone could help me out with this, it'd be greatly appreciated.
Update on situation:
The phone's problem now is that it will show up in My Computer, but then disappears after a few seconds, as though it has been disconnected, yet it's still plugged in and charging.
folieadeux said:
Update on situation:
The phone's problem now is that it will show up in My Computer, but then disappears after a few seconds, as though it has been disconnected, yet it's still plugged in and charging.
Click to expand...
Click to collapse
that my friend i fixed pretty easily.... all though the worst way... if you have cutom recovery wipe the cache and dalvik-cache if not then factory reset
demonslayer12349 said:
that my friend i fixed pretty easily.... all though the worst way... if you have cutom recovery wipe the cache and dalvik-cache if not then factory reset
Click to expand...
Click to collapse
So I should just format the SD card and that should work?
folieadeux said:
So I should just format the SD card and that should work?
Click to expand...
Click to collapse
if you have custom recovery factory reset
demonslayer12349 said:
if you have custom recovery factory reset
Click to expand...
Click to collapse
I don't have a custom recovery installed.
I'd suggest uninstalling all LG drivers. Reboot your PC and then run the driver installation program again. DO NOT connect your device to the PC just yet. Reboot PC once more. After PC starts, connect your device in "Charge phone" mode. Let the drivers install. From the "PC connection -> Select USB connection method" screen on the device, select "Media sync ( MTP )" and let the drivers install. Do the same for the remaining two connection methods. Once all drivers are installed, just for sanity, reboot PC one last time.
If that method doesn't work, then a factory reset may need to be done. This can be done in one of two ways.
1) With device booted :: Settings -> Backup & reset :: select Factory data reset
2) See this post for instructions on how to perform a factory reset with key combos.
shinobisoft said:
I'd suggest uninstalling all LG drivers. Reboot your PC and then run the driver installation program again. DO NOT connect your device to the PC just yet. Reboot PC once more. After PC starts, connect your device in "Charge phone" mode. Let the drivers install. From the "PC connection -> Select USB connection method" screen on the device, select "Media sync ( MTP )" and let the drivers install. Do the same for the remaining two connection methods. Once all drivers are installed, just for sanity, reboot PC one last time.
Click to expand...
Click to collapse
I've done everything up until installing the drivers from the phone. When it's first plugged in in "Charge Phone" mode, should I hit the button in the top right to install the PC software? Or should I go straight to the other drivers? I'm asking because when I plugged it in with "Charge Phone" mode on, nothing installed.
folieadeux said:
I've done everything up until installing the drivers from the phone. When it's first plugged in in "Charge Phone" mode, should I hit the button in the top right to install the PC software? Or should I go straight to the other drivers? I'm asking because when I plugged it in with "Charge Phone" mode on, nothing installed.
Click to expand...
Click to collapse
Yes, if you don't have another LG driver installer package.
shinobisoft said:
Yes, if you don't have another LG driver installer package.
Click to expand...
Click to collapse
I did everything you said, installed drivers, reset my computer and phone, and the problem persisted, it showed up, and then the window closed and nothing showed up. Will I have to factory reset it or is there anything else I could do?
folieadeux said:
I did everything you said, installed drivers, reset my computer and phone, and the problem persisted, it showed up, and then the window closed and nothing showed up. Will I have to factory reset it or is there anything else I could do?
Click to expand...
Click to collapse
With fresh drivers and you're still having issues then I'd say it can be one of 3 things:
1) Bad MTP driver on Windows. Hard disk fragmentation can cause issues like this. Try running Defrag on the Windows installation drive. Usually ( C: )
2) #1 didn't fix it? Try uninstalling and reinstalling Windows Media Player. MTP only works with Windows XP 32 bit and Windows Media Player 11, and newer 32 and 64 bit Windows versions with Windows Media Player installed.
3) #1 and #2 didn't work??? Possibly a hardware issue on the device.
shinobisoft said:
With fresh drivers and you're still having issues then I'd say it can be one of 3 things:
1) Bad MTP driver on Windows. Hard disk fragmentation can cause issues like this. Try running Defrag on the Windows installation drive. Usually ( C: )
2) #1 didn't fix it? Try uninstalling and reinstalling Windows Media Player. MTP only works with Windows XP 32 bit and Windows Media Player 11, and newer 32 and 64 bit Windows versions with Windows Media Player installed.
3) #1 and #2 didn't work??? Possibly a hardware issue on the device.
Click to expand...
Click to collapse
Should I install the MTP toolkit? Also, I'm running a defrag on my C: drive, and I have Windows 7 64-bit, and I'm not totally sure on how to uninstall and reinstall WMP. If none of this works, I'll just factory reset it and hope it solves it.
you are using lockscreen lock or something????
sometimes lockscreen lock can make device disappear like you said...
k2wl said:
you are using lockscreen lock or something????
sometimes lockscreen lock can make device disappear like you said...
Click to expand...
Click to collapse
I have a lockscreen with a pattern, if that's what you're asking.