I have recreated this method based on this post to make it much easier for everyone to get this setup on their devices with complete details.
Confirmed Working With
1. Windows 7
2. Mac OS X 10.6 (Snow Leopard)
3. Mac OS X 10.7 (Lion)
4. Other OS versions possible just not yet confirmed/tested (only thing stopping is driver support)
How to Enable UMS Mode on your Verizon Galaxy S III
1. Make sure you are currently rooted ***VERY IMPORTANT***
2. Download and install the Samsung Official Verizon Galaxy S III USB Drivers - Link Here
3. Download and install GScript Lite from the Play Store onto your device - Link Here
4. Download the Verizon Galaxy S III UMS-MTP Switcher Scripts to your computer - Link Here (or attachment at bottom of OP)
5. Create a folder called "gscript" on the root of your internal storage (/sdcard partition)
6. Extract the two scripts from the zip file (from step #4) into that folder on your device - Screenshot Here
7. Open GScript Lite on your device
8. Press the Menu key on your device and select "Add script"
9. Press the "Load file" button and select "UMS Mode.sh", then press the "Save" button and the UMS Mode script will be added to the list
10. Press the Menu key on your device and select "Add script" again
11. Press the "Load file" button and select "MTP Mode.sh", then press the "Save" button and the MTP Mode script will be added to the list
12. Select the "UMS Mode" script from the list and allow Superuser for root access
13. The script will now run and do not worry if GScript Lite force closes at the end as this is perfectly normal
14. On your Windows 7 computer you will see it will try to install "SAMSUNG Mobile MTP Device" as one of the drivers and fail *this is normal*
15. Go into Device Manager on your computer, right click "SAMSUNG Mobile MTP Device" and select "Properties"
16. Click on the "Driver" tab and click the "Update Driver" button, a prompt will then come up
17. Select "Browse my computer for driver software", then select "Let me pick from a list of device drivers on my computer" on the next screen
18. Select "USB Mass Storage Device" as the new driver from that list and finish up that install
19. At the end you will see something like this on your computer - Screenshot Here
20. Windows will install final drivers automatically and a new "Disk drive" will show up on your computer, this is your external SD card on your device
21. If you want to return to MTP Mode, just select "MTP Mode" script from GScript Lite on your device and after it force closes you will be back to normal
Click to expand...
Click to collapse
Benefits of UMS Mode
USB Mass Storage (UMS) Mode used the old way of managing USB storage (like Galaxy S II and so on) before that changed to Media Transfer Protocol (MTP) Mode (aka. Device mode) with the Samsung Galaxy Nexus. The benefit of UMS Mode is that it will work with special devices that try to read your phone like a car radio head unit will now be able to read the songs, pictures, videos, etc through the USB port properly, as well as your TV (if it has USB support of course), among many other devices. Also it's a much more reliable method of transferring files on your computer since it's basically direct access to the SD Card as opposed working through a special protocol with MTP or PTP Mode. This mod will enable your SD Card to show up as a regular disk drive instead of a device on whatever you plug into with a USB port. Hope that helps explain it a bit without being too technical. For details on why Google decided to switch to MTP Mode see this article.
Click to expand...
Click to collapse
Awesome, sweet write up. :good:
I may have to try this. The MTP doesn't work on my Mac for some reason. Android file transfer just crashes whenever I try it.
Do you have to enable the script at boot?
Explanation in OP very summary.
Plug the phone where? In the computer or the AC adapter?
If in the computer then why is necessary that to run the script.
If you don't use the GScript Lite then what do you use to run the scripts (Terminal?).
If you copy the script to the phone then the files should have which extension? I mention that because there is nothing attached.
Do not forget that you're dealing here with a lot of noobs.
Please be so kind and review the OP.
If the script works correct then this is a big deal and I congratulate you but do it like a pro.
Cheers.
jb_alphamale said:
Do you have to enable the script at boot?
Explanation in OP very summary.
Plug the phone where? In the computer or the AC adapter?
If in the computer then why is necessary that to run the script.
If you don't use the GScript Lite then what do you use to run the scripts (Terminal?).
If you copy the script to the phone then the files should have which extension? I mention that because there is nothing attached.
Do not forget that you're dealing here with a lot of noobs.
Please be so kind and review the OP.
If the script works correct then this is a big deal and I congratulate you but do it like a pro.
Cheers.
Click to expand...
Click to collapse
OP only copied and pasted someone else's thread/work.
http://forum.xda-developers.com/showthread.php?p=28670285#post28670285
Yeah I figured that out.
Now we have the link.
Thanks Beknatok.
Edit: Well it does not work on Verizon SIII.
jb_alphamale said:
Yeah I figured that out.
Now we have the link.
Thanks Beknatok.
Edit: Well it does not work on Verizon SIII.
Click to expand...
Click to collapse
Well lets try and get it to work. Some dev must want this too.:fingers-crossed:
jb_alphamale said:
Yeah I figured that out.
Now we have the link.
Thanks Beknatok.
Edit: Well it does not work on Verizon SIII.
Click to expand...
Click to collapse
I just tried it and it works perfectly.
This part is very important:
If Windows fails to find the correct driver, go to the Device Manager and manually set it to use the driver, "USB Mass Storage Device". It seemed to try to stick with the MTP driver in my case.
Click to expand...
Click to collapse
OK here is what I did.
Installed Script Manager free from the market.
Copied both scripts into sdcard\scripts folder.scripts folder created by myslef.
Opened the mass storages.sh script and run it.
I've got bunch of error messages that it cannot find this and that.
The phone was connected to the computer.
If necessary I can screenshot the errors.
open1your1eyes0 said:
I just tried it and it works perfectly.
This part is very important:
Click to expand...
Click to collapse
jb_alphamale said:
OK here is what I did.
Installed Script Manager free from the market.
Copied both scripts into sdcard\scripts folder.scripts folder created by myslef.
Opened the mass storages.sh script and run it.
I've got bunch of error messages that it cannot find this and that.
The phone was connected to the computer.
If necessary I can screenshot the errors.
Click to expand...
Click to collapse
Don't use those scripts, I have issues with them as well. Just copy/paste the OP text into your own script using GScript Lite.
OK let's try. I'll report back.
Edit: OK I did what you proposed. Created the script in GSript Lite and saved then ran. Nothing happens. After I run it GScript FCs. I'm giving up.
This is so simple that I don't think that I'm messing up something.
open1your1eyes0 said:
Don't use those scripts, I have issues with them as well. Just copy/paste the OP text into your own script using GScript Lite.
Click to expand...
Click to collapse
jb_alphamale said:
OK let's try. I'll report back.
Edit: OK I did what you proposed. Created the script in GSript Lite and saved then ran. Nothing happens. After I run it GScript FCs. I'm giving up.
This is so simple that I don't think that I'm messing up something.
Click to expand...
Click to collapse
GScript does have force close issues but don't worry, it still runs as long as you don't see any errors when it's done.
I have just extracted the working GScripts I created and added them to OP for anyone who wants to import them into their GScript Lite. Just create a folder called "gscript" on your internal memory "/sdcard" partition and put those two .sh files into that folder. Then just use the app to add each of them as a new script (load file).
If Windows fails to find the correct driver, go to the Device Manager and manually set it to use the driver, "USB Mass Storage Device". It seemed to try to stick with the MTP driver in my case.
Click to expand...
Click to collapse
Can someone help me with this part? I have no idea how to do this. I feel so dumb.
Please be informed that I have completely updated and rewrote my own guide for the OP. You will see all details and screenshots necessary to get this setup. If something is not clear please feel free to let me know and I will try to answer as best as I can. Please be advised that this has only been tested and guaranteed to work 100% on Windows 7 based computers so far. I cannot confirm for Windows XP, Mac OS X, Linux, or other devices. If someone can test this elsewhere would be greatly appreciated. Hope this helps you guys.
works perfect/
Great!
Worked great for me. :good:
nice
So what does this enable you to do? Browse the entire internal memory when connected to USB, opposed to just the microSD?
This will enable your SD Card to show up as a regular disk drive instead of a device on whatever you plug into with a USB port. This was the old way of managing USB storage before that changed to MTP Mode (device mode) with the Samsung Galaxy Nexus. The benefit of UMS is that it will work with special devices that try to read your phone like a car radio will now be able to read the songs through the USB port, also your TV (if it has USB support of course). Also it's a much more reliable method of transferring files on your computer since it's basically direct access as opposed working through a special protocol with MTP Mode. Hope that helps explain it a bit without being too technical.
Found this today: http://forum.xda-developers.com/showthread.php?t=1711009
Related
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Update driver
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
ShreddinPB said:
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Click to expand...
Click to collapse
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Emul8or said:
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
Click to expand...
Click to collapse
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
it2steve said:
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Click to expand...
Click to collapse
There is a fix posted for the slowdown issue after resume from sleep, and you ADB to fix it
ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Here's what dev mgr looks like on XP...
Jim
ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
davinci07 said:
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
Click to expand...
Click to collapse
Found it.. it was under "Universal Serial Bus Controllers" and called "USB storage device" i believe.
I tried updating the driver with the andoid one, but it errored out and wouldnt load it. After that however, 2 new devices popped up.. both the Nvidia harmony drive, and another nvidia tegra one. The harmony drivers failed to load.. so I pointed at the directory in the SDK and bam it works!!
Thanks guys!
But also btw.. before I got this working, I did use ADBWireless to run the adb shell and run that camand mentioned in the main thread that is supposed to stop the slow downs.. and I think its working.
enjoy, can you point me to the post that you needed this for? Also, now that ADB works you can start making your own apps. With either Eclipse and Android SDK (more advance route, but there is alot of good books that could help you alot) or with app invnetor that just got released to the public.
I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.
Hi guys,
I just have received a i9023 from a friend to repair. I put fastboot on and the device is unlocked, then I copied over Matr1x kernel via USB to the SD card and flashed CMW to recovery.
From here things went bad.
When trying to update the kernel to Matr1x, it showed that the file wasn't on the SD card anymore, so I tried to mount the SD card to copy it back, but it my computer wouldn't see it. Since then I tried many things to get the USB working - updating drivers etc... after awhile I decided to format SD card, which didn't help, so I formatted all the partitions on the phone.
Now, every time the phone comes on, it boots straight to fastboot, but also the PC will still not recognise the phone via USB.
I've tried getting into Download mode and using ODIN to flash a new kernel & ROM, but this wont work without USB working.
Can anyone help?
PS. I have read many other guides and posts, but nothing has helped.
Many thanks.
*Bump*
Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?
I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.
bedalus said:
Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?
Click to expand...
Click to collapse
Yes, I tried to mount as USB Storage in the Recovery Menu - didn't work, but now, I've only got fastboot - Booting up the phone normally jumps straight to fastboot, trying to boot into recovery doesn't work (just the fallen over Android pic with the red "!" on his chest).
I'm using Windows 7 and computer will not recognise the phone at all (it was working before this & the MicroUSB port is not damaged).
My GT-i9100 works perfectly via USB.
Piemo said:
I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.
Click to expand...
Click to collapse
If I can get it to connect to my PC so I can throw a stock ROM on there via ODIN I should be right (Pretty sure SAMFIRMWARE has some).
I've found often that the sdcard only gets mounted when you "choose zip from sdcard" in recovery. I panicked once with a galaxy s when I had forgot to put any rom on the sdcard and couldn't mount it subsequently. Ended up using heimdall with success. Also make sure you have latest version of fastboot, from platform tools 4.0.3.
Yeah, try Odin
If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!
twadda218 said:
If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!
Click to expand...
Click to collapse
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.
Can you try Ubuntu? Any luck with Odin?
KLoNe1 said:
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.
Click to expand...
Click to collapse
Does it say unknown device in device manager?
Sent from my ice cream powered Nexus S
I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file
KLoNe1 said:
I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file
Click to expand...
Click to collapse
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S
DarkhShadow said:
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Yes, I did - it said that this inf (driver) doesn't contain information about the device in question.
I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.
Many thanks for all your help everyone; unfortunately I still have yet to figure out how to get this working. Please keep throwing out your ideas
bedalus said:
I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.
Click to expand...
Click to collapse
I gave this a go as it sounded like a great idea, but unfortunately it still isn't working.
I ended up deleting the drivers it was installing which wouldn't work & now it will only show up as 2x Unknown device under 'Portable Devices' heading.
I think you should try installing ubuntu, and the android sdk so you have access to fastboot again.
When I plug my phone in I have no way to transfer files to and from the Nexus 5. Nothing comes up. Tried updating the drivers, but nothing works. Please help.
I haven't been able to do this either, anyone wanna help?
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Sent from my Nexus 5 using xda app-developers app
n7of9 said:
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Click to expand...
Click to collapse
Nope, still nothing. My Razr HD comes up fine, but not the Nexus 5. Think it's a conflict in drivers?
Tweaken said:
Think it's a conflict in drivers?
Click to expand...
Click to collapse
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Tweaken said:
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Click to expand...
Click to collapse
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thank you n7of9 the link you provided worked for me.
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
This worked and also fixed another popular issue
Not only does this fix the MTP connection issue to move folders to root folder. But it also now allows me to see the preview thumbnails of my media! This was a huge problem on my other phones and many many people including me were never able to fix that. All the ideas to get around or create USB Mass Storage instead of MTP after 4.1 were fails.
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Worked perfect, thanks
what worked for me
In windows 8.1
I plugged in my nexus and browsed to device manager in control panel
I uninstalled the device (and deleted the driver)
I unplugged the nexus 5
I plugged it back in
Windows recognized it as a proper MTP device
I think the problem was something to do with windows recognizing it as an ADB device (I had installed the toolkit before etc)
This fixed it for me
openlatedotorg said:
Worked perfect, thanks
Click to expand...
Click to collapse
Hi,
I did all the steps mentioned, and ran the driver test - everything works fine, success.
However, I still cant see my device in "This PC"...
What is even more weird, that it only disappeared couple of days ago, and I didnt do anything to my computer at all....
Any other way to get devices to show? (Nexus 10 or Nexus 4 stopped showing too).....
Maybe problem is that it is being shows as ACER ADB Interface? But i cant change that to MTP anyway..
Hello everyone and thanks in advance for anyone replying to my dumb question.
Today I was preparing to use the Aroma Toolkit to restore my phone to a basic stock. I placed it in a folder called ".rom" on the internal sdcard so it would appear at the top. (can you believe it?) I have CWM Red and it doesn't see ".rom" as it is now hidden. (I guess) Unfortunately, I already wiped AND formatted "system" so I can't boot the phone up to change the folder to something more sensible. I cannot restore from Odin OR Heimdall because my phone won't show up on ANY PC and it only shows "Unknown USB Device." I've been up and down with that one too. Also, I tried to put the toolkit on the external sdcard both as is and as update.zip but it says there are no files. I think my only way(s) out of this would be to Odin or Heimdall, if I can get either working again, or if there is a way to get the CWM Red to see that hidden ".rom" folder.
ANY help at all would be greatly appreciated.
Thanks for reading this.
folders and files that begin with a dot are hidden in linux systems like android. you are seeing an unknown device because you dont have samsung drivers installed. you should be able to go into mounts and storage and select usb mass storage or something like that and it will mount as a mass storage device where you can rename the file in windows where that doesnt show as a hidden file.
if you wiped system, if you turn off your device, you might not be able to get back into recovery and youll have to use odin or heimdall. you can download the samsung drivers from http://d-h.st/xEG and when you are in recovery mode, go to device manager and select from the list of device and choose samsung composite device or something like that i dont remember.
next time you want a folder to show at the top of the list, i think you can start it with an underscore. i could be wrong about that though. you can try it out and see.
I don't recall if red CWM has the mount as usb storage option. If not...
Next step is getting the drivers on your PC. Easiest option from there is Odin or Heimdall - unless you want to download the android SDK and use adb shell to rename the directory.
Underscore should work for sorting...
fwiw I use exclamation points.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks for the reply! Although I did have the Samsung drivers installed with Kies mini, I removed Kies and installed the drivers in the link you gave me but no luck. USB used to work fine in Win as well as Lin but it stopped suddenly. I am able to get into both recovery and download mode fine but I can't go anywhere from there. I tried to "mount sd_ext" under mounts and storage in recovery, hoping to access the aroma toolkit file from there, but I get a can't mount error that says /dev/block/mmcblklb1p2 (file exists). "mount USB" doesn't help either. I really did it this time....
Thanks again for the input
well, if youre not going to download mode to run odin, and you cant do usb mass storage in red cwm, and you want to do it from recovery, you need to choose samsung adb device in device manager. then you need adb and can do adb shell and run "mv /sdcard/.rom /sdcard/_rom"
mrpectate said:
Thanks for the reply! Although I did have the Samsung drivers installed with Kies mini, I removed Kies and installed the drivers in the link you gave me but no luck. USB used to work fine in Win as well as Lin but it stopped suddenly. I am able to get into both recovery and download mode fine but I can't go anywhere from there. I tried to "mount sd_ext" under mounts and storage in recovery, hoping to access the aroma toolkit file from there, but I get a can't mount error that says /dev/block/mmcblklb1p2 (file exists). "mount USB" doesn't help either. I really did it this time....
Thanks again for the input
Click to expand...
Click to collapse
sd_ext in red recovery does not refer to the external sd card (even though you would think it does from the name)
For compatible drivers, remove all Samsung phone related drivers from your system and install the first driver package located here (not the mini-kies one):
http://www.samsung.com/us/support/owners/product/SGH-I997ZKAATT
Some things that may help:
http://forum.xda-developers.com/showthread.php?t=1982306&page=2
Also, turn off auto driver install in Windows 7 - could be your PC is deciding what is best for you before you can install working drivers:
Go to Control Panel > System > Advanced System Settings > Hardware > Device Installation Settings > "No / Never"
Then install the driver, then connect your phone. Once the driver and devices are fully installed you can change the above setting back to what it was or to "No / Install" (that's where I usually leave it)
Good luck
Well I sincerely appreciate all the help from you guys, and Zen Arcade, thanks for the toolkit that brought me back from disaster quite a few times. I tried all of your suggestions, but it seems like I might have a hardware failure which occured before all this. I was able to connect to USB fine and out of nowhere it just wouldn't anymore. That was OK. I still rom-hopped along with straight to phone rom aquisition, but then I made a mistake. One I have learned from. I'm not able to get the phone to show up AT ALL. I even tried a clean install of WinXP then the drivers from Zen's post, and Nicky's Win7 laptop. I also tried several versions of Linux. Only Mint's Gparted could see it as /sdb/ with a corrupted partition. I even gave Haiku's Drive Probe a shot. Jack of Clubs, I tried the SDK shell but it just scans and sees nothing. I just think that the USB thing is roadblocking any hope of saving this heap. Recovery is there, download mode is there, but the connection required to utilize either of those is gone.
Again, I truly appreciate the help.
Well I've been trying to get CWM to see the Infuse Toolkit (and various roms) on external_sd but it keeps saying:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount /sdcard
I've tried 4 different microSD's formatted as FAT, FAT32, and I used SDFormatter (I saw someone recommend that somewhere). I really see this as the very last ember of hope for this phone before I let it go.
Any ideas?
BTW, my CWM is v2.5.1.3 - Voodoo lagfix
Thanks again and in advance.
Infuse GB recovery menu will not see external SD card.
If you can get adb working - connection to your PC - you have some options. From adb there are commands that will allow copying files from PC to phone ... also from external to internal sd card depending on which kernel you are running. You could also rename your hidden folder too.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks again for your continued help Zen. I just can't get it recognized (in a constructive way) by anything. I tried Santoku linux today and nothing. I've just been beating my head with this thing. Well here it is: CWM is accessible, as is download mode, and it charges fine, but no PC connection. When it was given to me, the glass was cracked, but it always worked fine for me. It's in a Ballistic case. If your interested in it, I'll be happy to send it to you, even if it's just for parts. I loved this phone, and had a lot of fun with it. (thanks to this community and all of its' contributors) I think it's time to move on.
I'm gonna start looking at a phone with a good selection of custom roms cuz I just love flashin' 'em
Let me know if your interested in this phone Zen.