Related
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!
For some reason my nook won't show up in windows 7 device manager as anything but a storage device (both the nook and sdcard). It doesn't show up under "other hardware" like all the tutorials show. I am at a loss?
Should I reset my device (unroot, wipe clean, etc)? And try again or am I missing something.
I am looking to get ad hoc working and am stuck in the mud
Depending on what ROM you're running... you may need to go into nook color tools and toggle usb debugging mode... it is a known issue in some ROMs....
You may also need to edit %userprofile$\.android\adb_usb.ini so the only line in it is:
0x2080
anyone have problems in ubuntu 10.04 can't get it :'(
I figuered it might be that I had tried some different kerenels recently. I did eventually return to stock. I have toggled debugging mode to no avail.
I will follow the other instructions you provided and if all else fails wipe her clean and try that.
Thanks.
Sent from my rooted nook color using Tapatalk
I have the same problem and am using the stock kernal. I have even tried two different computers (one with Win 7 and the other with XP) and get the same result. The first time it I tried with XP it showed "NookColor" under Other Devices with a ? mark. In just a second, it reloaded Device Manager and would never showed up again. I have tried all suggestions including the USB Debugging toggle with no positive results. By the way, I rooted using auto-nooter 3.0 for Nook Version 1.1. Everything seems to work well and I am using ADW Laucher EX. I am familiar with ADB as I used it root my Motorola Droid. In that case, I had no problems with it seeing my Droid.
Any suggestions would be helpful. I also have Ubuntu on a test computer that I may try if no solutions are found.
[email protected] said:
anyone have problems in ubuntu 10.04 can't get it :'(
Click to expand...
Click to collapse
I had the same issue in Ubuntu 10.04. My Evo would show up fine. My NookColor I could not get to show up though. No matter what I tried (I tried all the walk throughs on forums, Nookdevs.com, etc).
I finally just gave up. I've just been moving APK's from my Evo to my Nook to install them. There are many other things I'd wish to do through ADB other then install apps though so I may give it another shot sometime soon.
If it worked in some ROM versions and not in others... you need to check the device ID in windows device manager... get the PID for the device listed.... then you will need to add the device PID to the .inf file for the drivers so it will know to use the drivers that work for the "new" device (not really new.. just HWID change in some new kernels/ROMs
I had a world of trouble getting getting my computer to recognize the nook so that ADB would recognize the device. I mean HOURS of debugging.
However.. good news!... The answer that can help you is...: screw it and just download adbwireless app. All you do is run the app while connected to your home network and then on your computer run the the command "adb connect 192.168.1.xxx:5555" and you are connected and can run adb just like you were USB'd up
I hope this helps
Recommend installing the easy ADB install for Windows from the developers forum.
On Win7, sometimes you need to force the driver to use "USB Composite device" or "Android composite USB device", even after doing the easy ADB installer above.
Managed to get ADB working after Autonooker 3.0, Nook 1.1
Hi, All,
I had similar problems. I managed after a bit of fuss on my mac to get ADB up and running.
The main problem seemed to be getting USB debugging working. I went into nook color tools, from ADW launcher. I went to All Settings : Development, and saw that USB debugging was checked, but I didn't believe it was running.
So, I unchecked both Auto Mount (to simplify what the heck was going on over USB) and USB debugging, and hit back, to save the settings. Then I went back into debugging, and re-checked USB debugging.
Then, I made sure that ~/.android/adb_usb.ini contained the line:
0x2080
I killed the adb server and restarted it, and voila, ADB.
Hope this helps some folks.
Dave
I am in the same boat, adb works fine on my other android device, but won't see my nook for anything.
I have tried every permutation I have seen of the rules file, still nothing.
Im running windows xp 32bit and having major difficulties getting adb to show my devices as online.
so far I have tried reinstalling the SDK, as well as removing/reinstalling the driver multiple times.
I'm kinda at a loss as to what could possibly be causing this issue. Initially when I rooted the device I followed Pete's page and used the driver supplied there.
what could I possibly be over looking?
-I installed 2 separate drivers one over the other accidentally, so I uninstalled each, and ran a registry cleaner and that resolved the conflict.
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
On one of my laptops, Windows 10 performed a significant update to a new major version. All completed well, except that now my Google Pixel 5 is no longer appearing as a USB device. I have 2 laptops. Below is a device manager capture of the two laptops with the Google Pixel 5 plugged in. It appears that Windows decided to reclassify how Android phones now appear (no longer under "Portal" and now under "Android Devices"). My Pixel 5 doesn't show up, instead there's a "Google Nexus ADB Interface." Well, I uninstalled it and it automatically installed again... a check for online updates says it's the latest. But in Windows Explorer I do not see my Google Pixel 5 when setting to File Transfer mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've ditched my days of being involved in firmware updates because the latest phones are so capable now, especially with customizations. I thought perhaps a driver update directly from Google would be in order, but I'm unable to find anything... only stuff for the SDK.
I posted about this on Reddit r/GooglePixel, and got no help. If anyone here has a useful idea, please share. Thanks!
I think a few things could be happening. First, if you do not have ADB tools (Android ADK) installed, it may default to the phone name because it isn't finding the ADB interface, but the other phone interfaces (PTP for example). Was the Android SDK installed on the old version too?
Also, do you happen to have it linked to your computer with "My Phone"? You may get a more accurate name if you have linked it.
But ultimately, what is your goal?
bitpushr said:
I think a few things could be happening. First, if you do not have ADB tools (Android ADK) installed, it may default to the phone name because it isn't finding the ADB interface, but the other phone interfaces (PTP for example). Was the Android SDK installed on the old version too?
Also, do you happen to have it linked to your computer with "My Phone"? You may get a more accurate name if you have linked it.
But ultimately, what is your goal?
Click to expand...
Click to collapse
Yes, I had the ADB tools, Android SDK installed on only one computer., my primary. (On the older one it didn't have ADB. <--- FALSE). ClockworkMod was installed. But I wiped that clean.
Interesting, on my other computer I rechecked--I do have Android SDK installed on it... I just didn't put ClockworkMod on it.
Not sure what you mean by linking it with "My Phone." I have a USB-C cable, which has worked before just fine. My device is simply named "Pixel 5."
Btw, after installing all ADB drivers, I'm finding that when I plug in my Pixel 5, the "Google Nexus ADB Interface" node appears again under "Android Devices." What's going on? Is Windows somehow retrieving the ADB drivers from somewhere in a CAB file or something?
My goal is simple--I want to connect my Google Pixel 5 to my laptop and have it available as a USB storage device so I can transfer files to and from the device. I've done this for years... and this latest Windows update somehow screwed things up for me.
EDIT: For what it's worth, I was able to connect to Microsoft Windows Support via chat, for free. The technician looked this up and said it's a known issue for some configurations. Apparently there will be an update in a few weeks and he suggested rolling back to the previous version if I can't wait.
cytherian said:
Yes, I had the ADB tools, Android SDK installed on only one computer., my primary. (On the older one it didn't have ADB. <--- FALSE). ClockworkMod was installed. But I wiped that clean.
Interesting, on my other computer I rechecked--I do have Android SDK installed on it... I just didn't put ClockworkMod on it.
Not sure what you mean by linking it with "My Phone." I have a USB-C cable, which has worked before just fine. My device is simply named "Pixel 5."
Btw, after installing all ADB drivers, I'm finding that when I plug in my Pixel 5, the "Google Nexus ADB Interface" node appears again under "Android Devices." What's going on? Is Windows somehow retrieving the ADB drivers from somewhere in a CAB file or something?
My goal is simple--I want to connect my Google Pixel 5 to my laptop and have it available as a USB storage device so I can transfer files to and from the device. I've done this for years... and this latest Windows update somehow screwed things up for me.
EDIT: For what it's worth, I was able to connect to Microsoft Windows Support via chat, for free. The technician looked this up and said it's a known issue for some configurations. Apparently there will be an update in a few weeks and he suggested rolling back to the previous version if I can't wait.
Click to expand...
Click to collapse
Nonsense. I have the same Win 10 version and everything connects the same. They are clueless and reverting might bring way more problems than you wish to deal with. It's a driver issue plain and simple. There is a .inf file that needs to be reinstalled but I'll be darned if I remember which and what exactly to do. I'll research it a little tomorrow and see if I can find the solution. Whatever you do don't follow Microsoft help forums, you'll be installing crap that won't help.
edit: Ok this is what I did way back and it worked. Good luck. https://forum.xda-developers.com/t/...allation-on-windows-10.3570625/#post-71364316
bobby janow said:
Nonsense. I have the same Win 10 version and everything connects the same. They are clueless and reverting might bring way more problems than you wish to deal with. It's a driver issue plain and simple. There is a .inf file that needs to be reinstalled but I'll be darned if I remember which and what exactly to do. I'll research it a little tomorrow and see if I can find the solution. Whatever you do don't follow Microsoft help forums, you'll be installing crap that won't help.
edit: Ok this is what I did way back and it worked. Good luck. https://forum.xda-developers.com/t/...allation-on-windows-10.3570625/#post-71364316
Click to expand...
Click to collapse
Thanks...
Yeah, I've been around the block enough times to know that Microsoft Windows O/S installations are often buggy and fragile. I never take a major upgrade with ease. I always expect there may be an issue. And rolling back is only a very last resort.
In my case, I do not get an unknown or MTP device listed in the Device Manager. I tried doing the INF install... both with the wpdmtp.inf file and the Google provided android_winusb.inf.... No change. Every single time I plug in my Google Pixel 5, I get an "Android Devices" node with "Google Nexus ADB Interface" showing. And, still no device listed in Windows Explorer when I switch to USB File Transfer mode.
@cytherian It was worth a shot. My laptop says something different although it's basically the same I think. Mine says, "LeMobile Android Device" and under it Android composite ADB Interface. So even though I know you know these things and probably have tried each and every one I'll list them as I'd do them.
Make sure you have the very latest Platform tools
Try a different USB port
Try an A to C adapter rather than C to C
Try a different cable.
I think since it reinstalls auto then your laptop's drivers are fine. Mine is dated 2016 so I'm sure yours is the latest. It's gonna be something simple, you'll figure it out. In the meantime can you use a different computer that recognizes it and do the file transfers there?
bobby janow said:
@cytherian It was worth a shot. My laptop says something different although it's basically the same I think. Mine says, "LeMobile Android Device" and under it Android composite ADB Interface. So even though I know you know these things and probably have tried each and every one I'll list them as I'd do them.
Make sure you have the very latest Platform tools
Try a different USB port
Try an A to C adapter rather than C to C
Try a different cable.
I think since it reinstalls auto then your laptop's drivers are fine. Mine is dated 2016 so I'm sure yours is the latest. It's gonna be something simple, you'll figure it out. In the meantime can you use a different computer that recognizes it and do the file transfers there?
Click to expand...
Click to collapse
Yep, tried USB port change... no dice. Cable is same I've been using, but tried another. Both work on my other laptop. I am really not planning to delve back into firmware flashing, but maybe I should just go install the latest Android SDK and all the drivers from that to see if that somehow fixes things.
cytherian said:
Yep, tried USB port change... no dice. Cable is same I've been using, but tried another. Both work on my other laptop. I am really not planning to delve back into firmware flashing, but maybe I should just go install the latest Android SDK and all the drivers from that to see if that somehow fixes things.
Click to expand...
Click to collapse
Yes try that for sure.
I uninstalled ClockworkMod, but this driver keeps appearing. I went to USBDeview, found 3 listings for the ClockworkMod, deleted them...
STILL... when I plug in my damned Pixel 5, this ClockworkMod driver keeps coming up! I searched the Registry. Found a few entries. Deleted them. Restarted my computer. Plugged in my Pixel 5... It's Baaaaaaaaaaaaaaaaack!
What in the world?
cytherian said:
View attachment 5258887
I uninstalled ClockworkMod, but this driver keeps appearing. I went to USBDeview, found 3 listings for the ClockworkMod, deleted them...
STILL... when I plug in my damned Pixel 5, this ClockworkMod driver keeps coming up! I searched the Registry. Found a few entries. Deleted them. Restarted my computer. Plugged in my Pixel 5... It's Baaaaaaaaaaaaaaaaack!
What in the world?
Click to expand...
Click to collapse
To remove the driver:
Open and admin command prompt
Type dism /online /get-drivers
Look through the list for the above driver. Provider Name, Date, and Version should all match. Use the Published Name in the command below
Type dism /online /remove-driver oemXXX.inf
Do be careful, there are no "are you sure" prompts with this method.
You should also be able to force it to the Google USB driver as well if you have it downloaded from the android SDK. Use the update driver button and browse to the extras\google\usb_driver folder.
l7777 said:
To remove the driver:
Open and admin command prompt
Type dism /online /get-drivers
Look through the list for the above driver. Provider Name, Date, and Version should all match. Use the Published Name in the command below
Type dism /online /remove-driver oemXXX.inf
Do be careful, there are no "are you sure" prompts with this method.
You should also be able to force it to the Google USB driver as well if you have it downloaded from the android SDK. Use the update driver button and browse to the extras\google\usb_driver folder.
Click to expand...
Click to collapse
I ran DISM and did not find ClockwordMod indicated anywhere in the driver list.
I went ahead an plugged in my Pixel 5... the "Android Devices" node appears. "Google Nexus ADB Interface" is there again. It shows that pesky ClockwordMod driver again. And when I run DISM, there's no indication of "ClockworkMod" anywhere. I do see the AndroidUsbDeviceClass, android_winusb.inf, dated 8/28/2014, version 11.
Still, can't get access to my Pixel 5 in Explorer...
cytherian said:
I ran DISM and did not find ClockwordMod indicated anywhere in the driver list.
I went ahead an plugged in my Pixel 5... the "Android Devices" node appears. "Google Nexus ADB Interface" is there again. It shows that pesky ClockwordMod driver again. And when I run DISM, there's no indication of "ClockworkMod" anywhere. I do see the AndroidUsbDeviceClass, android_winusb.inf, dated 8/28/2014, version 11.
Still, can't get access to my Pixel 5 in Explorer...
Click to expand...
Click to collapse
Did it have enough buffer to scroll all the way to the beginning of the driver list? DISM Should list all third party drivers. You might want to do:
dism /online /get-drivers > drivers.txt
notepad drivers.txt
Another alternative since it sounds like the correct driver is indeed installed
Update driver button
Browse for driver
Let me pick from a list
Select Android Composit ADB Interface
EDIT:
I re-read the thread and it seems you're trying to get usb storage to work. That should be a different driver all together. The one you're looking at should be for the android debug bridge and should disappear if you turn off USB debugging. To confirm, go to the details tab of the device properties and see what hardware ID it is.
USB\VID_18D1&PID_4EE1 = USB Storage
USB\VID_18D1&PID_4EE1&MI_01 = ADB
l7777 said:
Did it have enough buffer to scroll all the way to the beginning of the driver list? DISM Should list all third party drivers. You might want to do:
dism /online /get-drivers > drivers.txt
notepad drivers.txt
Another alternative since it sounds like the correct driver is indeed installed
Update driver button
Browse for driver
Let me pick from a list
Select Android Composit ADB Interface
EDIT:
I re-read the thread and it seems you're trying to get usb storage to work. That should be a different driver all together. The one you're looking at should be for the android debug bridge and should disappear if you turn off USB debugging. To confirm, go to the details tab of the device properties and see what hardware ID it is.
USB\VID_18D1&PID_4EE1 = USB Storage
USB\VID_18D1&PID_4EE1&MI_01 = ADB
Click to expand...
Click to collapse
Yes, I thought it was implied... wanting Windows Explorer access to files would mean USB storage. I did have sufficient buffer to scroll through the whole list. In fact, I copy/pasted it into a text editor for easy searching.
Devices showing up under "Google Nexus ADB Interface":
USB\VID_18D1&PID_4EE1&REV_0440
USB\VID_18D1&PID_4EE1
NOTE - In Events I see this:
Device install requested
Device not migrated
Driver service added (WinUSB)
I should also note that in the System Tray, for USB devices, I see "Pixel 5." I have the option to eject if I wish. So, Windows is seeing the device but perhaps somehow the wrong driver is being mapped?
What really bugs me is... WHY is this "ClockworkMod" driver even showing up? Is Windows dynamically picking it up somewhere?
cytherian said:
Yes, I thought it was implied... wanting Windows Explorer access to files would mean USB storage. I did have sufficient buffer to scroll through the whole list. In fact, I copy/pasted it into a text editor for easy searching.
Devices showing up under "Google Nexus ADB Interface":
USB\VID_18D1&PID_4EE1&REV_0440
USB\VID_18D1&PID_4EE1
NOTE - In Events I see this:
Device install requested
Device not migrated
Driver service added (WinUSB)
I should also note that in the System Tray, for USB devices, I see "Pixel 5." I have the option to eject if I wish. So, Windows is seeing the device but perhaps somehow the wrong driver is being mapped?
What really bugs me is... WHY is this "ClockworkMod" driver even showing up? Is Windows dynamically picking it up somewhere?
Click to expand...
Click to collapse
Windows loads drivers based on the hardware IDs. For some reason the ClockworkMod driver is claiming to be for one of those hardware ids. Now that I know it's supposed to be the storage driver try this:
Update Driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
See if "MTP USB Device" is listed
Another option to identify the clockworkmod driver
Details tab
Inf name
If it starts with oemXX.inf it should be safe to use dism to remove it
You know what's so bizarre?
Published Name : oem47.inf
Original File Name : android_winusb.inf
Inbox : No
Class Name : AndroidUsbDeviceClass
Provider Name : ClockworkMod
Date : 8/27/2012
Version : 7.0.0.4
Notice it's indicating the original filename as "android_winusb.inf."
Well, sure enough oem47.inf is in the Windows/INF directory, and it has "ClockworkMod" info in it.
I tried removing it with dism /online /remove-driver /driver: oem47.inf
Failed. Error: 50, "This command can only be used with an offline image."
I discovered that I could rename the files (oem47.infx, oem47.pnfx), then move them off to a TEMP folder. I rebooted... and oddly, "oem47.inf" is still showing in the DISM driver list. I ran USBDeview, noticed it was still there, so I deleted it. Ran the DISM get-drivers cmd again... STILL showing up. It did NOT mysteriously reappear in Windows/INF. So I figured it must be in the registry. The only registry entries I could find is "oem47.inf" among others in "Owners" of various DLL files.
cytherian said:
You know what's so bizarre?
Published Name : oem47.inf
Original File Name : android_winusb.inf
Inbox : No
Class Name : AndroidUsbDeviceClass
Provider Name : ClockworkMod
Date : 8/27/2012
Version : 7.0.0.4
Notice it's indicating the original filename as "android_winusb.inf."
Well, sure enough oem47.inf is in the Windows/INF directory, and it has "ClockworkMod" info in it.
I tried removing it with dism /online /remove-driver /driver: oem47.inf
Failed. Error: 50, "This command can only be used with an offline image."
I discovered that I could rename the files (oem47.infx, oem47.pnfx), then move them off to a TEMP folder. I rebooted... and oddly, "oem47.inf" is still showing in the DISM driver list. I ran USBDeview, noticed it was still there, so I deleted it. Ran the DISM get-drivers cmd again... STILL showing up. It did NOT mysteriously reappear in Windows/INF. So I figured it must be in the registry. The only registry entries I could find is "oem47.inf" among others in "Owners" of various DLL files.
Click to expand...
Click to collapse
see if pnputil will do the job. I could've sworn I've used DISM to remove online drivers before.
pnputil -d oem47.inf
or
pnputil -f -d oem47.inf
Thanks! That did the trick --> pnputil -d oem47.inf
And... I plugged in my Pixel 5... low & behold, Windows tells me it discovered a new device, setting it up... and...
YES!
I see it now in Windows Explorer!
So this was the problem. A LEGACY issue, with a leftover INF file. Somehow this was taking priority, because in the OEM list, the proper one is oem87.inf.
What an ordeal. Can you imagine if a novice had to face this?
cytherian said:
Thanks! That did the trick --> pnputil -d oem47.inf
And... I plugged in my Pixel 5... low & behold, Windows tells me it discovered a new device, setting it up... and...
YES!
I see it now in Windows Explorer!
So this was the problem. A LEGACY issue, with a leftover INF file. Somehow this was taking priority, because in the OEM list, the proper one is oem87.inf.
What an ordeal. Can you imagine if a novice had to face this?
Click to expand...
Click to collapse
Glad you got it worked out. It is a bit of driver hell. Side effect of supporting nearly every piece of hardware that one could plug into a computer. They should make it easier to manage them though. I'm actually surprised that it's still using a third party driver (oemXX.inf). My 20H2 system is using a built in driver, wpdmtp.inf.
l7777 said:
Glad you got it worked out. It is a bit of driver hell. Side effect of supporting nearly every piece of hardware that one could plug into a computer. They should make it easier to manage them though. I'm actually surprised that it's still using a third party driver (oemXX.inf). My 20H2 system is using a built in driver, wpdmtp.inf.
Click to expand...
Click to collapse
Thanks. Yes, at this late stage of the game, Windows Device Management should be revised. It's the same old interface we've had for almost 2 decades. Such a PITA to update drivers. The thing is, the Google Pixel 5 is from... GOOGLE. A software giant. Wouldn't Microsoft ensure that those drivers will be picked up and not allow an obsolete driver to override? Just boggles my mind.
Well, on my system now, the Pixel 5 is being supported by the same driver as yours, wpdmtp.inf. It seems to have been mapped when Windows 10 recognized the Pixel 5 as a new device. It was the old driver that was blocking the installation, somehow.
cytherian said:
Thanks. Yes, at this late stage of the game, Windows Device Management should be revised. It's the same old interface we've had for almost 2 decades. Such a PITA to update drivers. The thing is, the Google Pixel 5 is from... GOOGLE. A software giant. Wouldn't Microsoft ensure that those drivers will be picked up and not allow an obsolete driver to override? Just boggles my mind.
Well, on my system now, the Pixel 5 is being supported by the same driver as yours, wpdmtp.inf. It seems to have been mapped when Windows 10 recognized the Pixel 5 as a new device. It was the old driver that was blocking the installation, somehow.
Click to expand...
Click to collapse
Right, and that driver is dated 6/21/2006. The clockworkmod driver is dated 2012. I suspect that Window's logic matches the device id first and then looks for the latest driver available. In this case the question is why was the clockworkmod driver claiming to be for the storage device id rather than the ADB device id. I'd have been curious to know if you could have manually chosen the older (and correct) driver.