Samsung S3 not showing up in adb with usb debuging on? Solved - Sprint Samsung Galaxy S III

Have You enabled USB Debuging?
(In Android 4.2.2 or later)
Don't see the option To have USB debugging enabled;
Go to -
Settings, More,
Scroll to the bottom,
About on your device
and click on
Build number at the bottom 7 times
until it says You are now a developer (may go by fast and you don't actually see it).
Now here is where the problem may start.
When you have enabled usb debugging, then unplug/replug the usb cable and still your device is not listed in ADB?
OK so you have set your device into USB mode ( hit the Build number in About device 7 times if necc.)
Windows popped up a little notice and said your device Samsung xyz is ready to use.
Your device shows up in list of items to explore and you can see your files in windows explorer.
Great. Now why doesn't it show up in adb? You try different adb installs and still no device.
What could be wrong?
What to do?
If the device is seen in Windows explorer but is not recognized in adb,
you may need to reconfigure the inf file in windows/ inf folder (usb.inf)
Do this after you make a backup of you usb.inf file first!
Use notepad and make sure the box to use this always is not checked.
I just copied the file to another location to edit it. Then rename the original file to usb1.inf.
Then I copied the edited file back to the windows inf folder.
In Windows 7 (The listed information is listed in devices, driver, driver ID.)
To get the needed information to edit your usb.inf file -
Go to Computer, System Properties (at the top) Device manager.
Here under Portable Devices you should see your device listed. Note the exact name.
Double click or right click and then properties, under driver details change the radio bar to Harware ID from Device description. The information should look like this;
USB\VID_04E8&PID_6860.
USB\VID_04E8&PID_6860&REV_0400.
Now you will need to use that information in the area of your usb.inf file after this item;
;Non-Localizable
Samsung.Mfg="Samsung"
USB\VID_0419&PID_8001.DeviceDesc="Samsung USB Hub"
USB\VID_055D&PID_8001.DeviceDesc="Samsung E.M. USB Hub"
so that after it will look like this (after the previously noted area)
;Non-Localizable
Samsung.Mfg="Samsung"
USB\VID_04E8&PID_6860.DeviceDesc="Samsung USB Hub"
USB\VID_04E8&PID_6860&REV_0400.DeviceDesc="Samsung E.M. USB Hub"
I have tested this on a Samsung S3 SPH-L710 and was able to get the phone to be recognized by adb.
Then I was able to install recovery and root thanks to the work of Chainfire via
Sprint variant – [SPH-L710] CF-Auto-Root v1.0

Related

Extract Galaxy S device drivers?

Does anyone know if the Galaxy S is supposed to transfer drivers when attached to a machine via usb? I've tried installing samsung usb drivers/multiple kies versions on both xp and windows 7 x86 machines however I've not once got the device installed. The first machine I tried it on did register the device Samsung_android had been attached however after factory resting it now appears as 'unkown. If it does install drivers, would it be possible to retrieve them from the galaxy s source? Would flashing the phone with a custom rom include the device drivers?
I would really appreciate any suggestions, I love the device but I've been trying to resolve this issue since I bought the phone
By default it uses Kies when you connect it via USB, go into options - About Phone - USB Settings and choose "ask me what to do" then you can choose MTP to mount it as a USB drive, choose it as a modem, etc. You need to go into the slide-down notifications menu and click on MTP mode then. For Mac's you need to enable USB debugging as well.
Thanks for your reply however I've tried connecting using each of the connection options. I am given the option to mount the internal SD card and lists 'MTP conneced' but the machine it's connected to still lists 'unkown device' within dev manager. I've also tried enabling USB debugging but even adb doesn't list the galaxy s.
Regardless of the device setting windows still displays 'device not recognized'. I've looked at the drivers within samsung\usb_driver but the folders are listed by development alias so its hard to determine which driver is for the i9000 I read on a forum that someone had this problem and Samsung replaced the drivers on the galaxy, I'm not sure if that's true or it was some other fix but if the galaxy does provide the machine with drivers maybe I can extract them and install directly to the machine
I don't have access to the NAND as I have not rooted it, but if you want I can do a directory listing of the internal SD and you can see what you are missing. I can then copy the files for you.
Tachikoma_kun said:
I don't have access to the NAND as I have not rooted it, but if you want I can do a directory listing of the internal SD and you can see what you are missing. I can then copy the files for you.
Click to expand...
Click to collapse
I like this community already, thanks mate but you don't have to go to the trouble. I returned the device to vodafone for a replacement. The replacement connected first time and I can now access the device without any problems
No doubt others will have this issues so...
Galaxy S "unknown Device" - If you have tried
Installing Samsung USB drivers for your operating system (There are both x86(32bit) and x64(64bit) versions of these drivers for windows.
Setting the Galaxy S to MTP on usb connect (Settings>About Phone>USB settings
Resetting your Galaxy S to factory settings (Settings>Privacy>Factory Reset)
Enabling usb debugging (Settings>Application>Development)
Formatting your internal SD card (Settings>SD Card..) Unmount before and re mount after formatting
Installing various versions of keis bloatware
and your Galaxy S is still listed as "unknown device" within windows device manager. Try taking it back to the store and asking for a replacement, this was the only step which worked for me and it worked first time Remember to explain all the steps you've taken and if you have to, ask for a demonstration of the device successfully connecting before you accept that there isn't an issue.
No worries, glad you are sorted now.

Can't get Nexus 7 to show up on computer

Shows up on my laptop but not on my desktop, have tried back and front USB ports
have uninstalled USB drivers, reinstalled USB drivers (universal adbdriversetup6 downloaded from xda sources)
downloaded android SDK manager and installed whatever USB stuff it had there
used USBdeview to remove any nexus 7 related things and then re-install USB drivers
Cannot for the life of me figure out what's going on... can anyone help me please
When I plug it in my desktop it makes the sound like something got connected... even has the safely remove hardware thing with nexus 7 there, but nothing in my computer
also have tried with/without USB debugging
tried removing my rom and flashing stock etc
Nothing has worked so far
and yes forgot to put in the title but this is for the Nexus 7FHD 2013
Is there a chance you are using usb3.0 port and can switch to usb2.0?
I would suggest you backup, flash stock, and redo your driver deinstall/install on stock. Try to get it working there first. Make sure USB debugging is disable on stock.
sfhub said:
Is there a chance you are using usb3.0 port and can switch to usb2.0?
I would suggest you backup, flash stock, and redo your driver deinstall/install on stock. Try to get it working there first. Make sure USB debugging is disable on stock.
Click to expand...
Click to collapse
tried USB 3.0 as well as 2.0 on desktop doesnt work, shows up as a device on safely remove hardware, and I can also see it under other devices in hardware manager or whatever but doesnt display in computer
USB debugging enabled or disabled on stock doesn't work.. tried going back to stock and doing driver installation etc as well
In device manager are there any unknown devices?
Did you remember to
Originally Posted by Geodude074 View Post
When you uninstall the driver, make sure you check the option to DELETE the driver as well. Otherwise when you try to reinstall it, it will just reinstall the old driver again
Driver instal with WinXP
I went around with this problem after both my Win7 laptop and WinXP desktop both recognized my N7 2013 the first time I connected to them. I had no problem dragging and dropping files.
I had then returned the tab back to BB for a exchange for another. This time after setting up the tab and setting the MTP file toggle and USB settings correctly......The Win7 laptop worked find and recognized the N7 just like it did on the first tab. But now the WinXP desktop did not work and only saw the N7 as a ABD device.
You may already have the correct drivers (if not those are available here in several posts). You just have to direct windows driver update to the correct place for the MTP driver. Here is how i did it.
1. Open up the Device Manager on your PC and locate the Android device it sees. Select the update driver option and you get to the "Welcome to the Hardware Update Wizard" screen.
2. In this window it asks "Can Windows connect to Windows Update to search for software?" Select the 3rd option ' No, not at this time"
3. In the next window "This wizard helps you install software for...." Select the 2nd option "Install from a list or specific location (Advanced)
4. In the "Please choose your search and installation options" window... go down to the bottom and select "Don't search, I will choose the driver to install" option.
5. Now finally the window we need..... "Select the device driver you want to install for this hardware" The "show compatible hardware" button should be selected...if not check that box. You should see 2 choices in the "Model" area..... Google Nexus ADB Interface" and what we need to select " MTP Device" click on the MTP Device and hit next......it should install and your Nexus 7 should then show up properly.
Hope this works for all that have had a hard time as I did....I just found it odd after getting a replacement N7 my XP desktop did not recognize it as it did to the original one I used the day prior.
un1bomber said:
Shows up on my laptop but not on my desktop, have tried back and front USB ports
have uninstalled USB drivers, reinstalled USB drivers (universal adbdriversetup6 downloaded from xda sources)
downloaded android SDK manager and installed whatever USB stuff it had there
used USBdeview to remove any nexus 7 related things and then re-install USB drivers
Cannot for the life of me figure out what's going on... can anyone help me please
When I plug it in my desktop it makes the sound like something got connected... even has the safely remove hardware thing with nexus 7 there, but nothing in my computer
also have tried with/without USB debugging
tried removing my rom and flashing stock etc
Nothing has worked so far
Click to expand...
Click to collapse
Just go in settings then storage and then computer usb connection by opening preferences in storage and then make sure mtp is checked.
Thank you guys SO MUCH for the help... I actually just returned my unit to staples because those POS wont give me a price adjustment vs google play
Will buy another one from google play and follow steps in the thread!
un1bomber said:
Thank you guys SO MUCH for the help... I actually just returned my unit to staples because those POS wont give me a price adjustment vs google play
Will buy another one from google play and follow steps in the thread!
Click to expand...
Click to collapse
We are always here to help.
I remember few years back I installed miui ROM on my xperia n couldn't connect to PC , only to realise USB wasn't turned to mtp by default. I thought it was a bug, tried everything even to fix it only to realise this.
Thanks a lot !!! This solution worked perfectly for me
You saved lots of time for me
Thanks a ton :good::good::good:
Best regards,
RR215 said:
I went around with this problem after both my Win7 laptop and WinXP desktop both recognized my N7 2013 the first time I connected to them. I had no problem dragging and dropping files.
I had then returned the tab back to BB for a exchange for another. This time after setting up the tab and setting the MTP file toggle and USB settings correctly......The Win7 laptop worked find and recognized the N7 just like it did on the first tab. But now the WinXP desktop did not work and only saw the N7 as a ABD device.
You may already have the correct drivers (if not those are available here in several posts). You just have to direct windows driver update to the correct place for the MTP driver. Here is how i did it.
1. Open up the Device Manager on your PC and locate the Android device it sees. Select the update driver option and you get to the "Welcome to the Hardware Update Wizard" screen.
2. In this window it asks "Can Windows connect to Windows Update to search for software?" Select the 3rd option ' No, not at this time"
3. In the next window "This wizard helps you install software for...." Select the 2nd option "Install from a list or specific location (Advanced)
4. In the "Please choose your search and installation options" window... go down to the bottom and select "Don't search, I will choose the driver to install" option.
5. Now finally the window we need..... "Select the device driver you want to install for this hardware" The "show compatible hardware" button should be selected...if not check that box. You should see 2 choices in the "Model" area..... Google Nexus ADB Interface" and what we need to select " MTP Device" click on the MTP Device and hit next......it should install and your Nexus 7 should then show up properly.
Hope this works for all that have had a hard time as I did....I just found it odd after getting a replacement N7 my XP desktop did not recognize it as it did to the original one I used the day prior.
Click to expand...
Click to collapse
If nothing else here has helped you solve this issue, check my thread, it should be of some help to you...
I'm having an issue where I can connect to my laptop in debug mode, but I'm not able to connect in the MTP mode with debug turned off. I expected to be able to mount the device storage in either mode.
Is that correct? If so, any ideas? I do notice I can't seem to get the MTP driver to stay in device manager.
Rick

[SOLVED] OmniROM phone won't mount.

Hi folks,
Running the latest OmniROM nightlies on my Find 7, non-unified.
The phone won't mount on my Windows 8.1 box for some unknown reason.
It happened I think after I installed drivers for a Samsung S3 which I rooted and flashed. I uninstalled those and cleaned up the registry, still no dice.
When I plug the phone in the machine makes the mount beep sound, but the device does not appear. Other USBs do. I don't have another computer to test the phone mount on, however.
USB debugging on/off with the same effect.
Any other ideas? The computer doesn't normally have any problems mounting things.
I'll update this if I find a fix, or if more details are needed.
Cheers!
d
Update: The phone mounts over PT (as a camera) but not MTP (media device). Can't access anything but DCIM and some other rubbish. :/
Update #2: Fixed. Uninstall the drivers per instructions here
http://android.stackexchange.com/qu...n-windows-in-mtp-mode-after-update-to-android
Copied:
Plug the Nexus 7 into your computer with the USB cable.
Open Device Manager: Start -> Run (or Win+R), type in: devmgmt.msc and hit enter. This opens up the device manager.
Find "Android Composite ADB Device" near the top and expand the node. Double click on the device. (Note: Sorry, I don't see it anymore so it might be named slightly differently.)
In the properties window that pops up, uninstall the driver. You should choose to delete the current driver as well.
Unplug the tablet and plug it back in.

Google drivers not working on Nexus 5X/Marshmallow on Win7 - Is the phone too new?

I have my new Nexus 5X with Android 6 on it. I am trying to unlock and root.
I have enabled USB debugging and OEM unlock.
I have downloaded and installed the SDK package with Platform-Tools and drivers in the 'Extras' folder.
When first plugging in the phone I install the drivers with the 'Have Disk' and browse method.
Every time, installing the driver returns an Error 'Code 10 - device cannot start. 'Android ADB interface' shows up in device manager when I plug in the phone but with an exclamation point.
I have uninstalled, downloaded fresh drivers from other sources, reinstalled, tried plugging the phone in while in 'recovery' mode (starting by pressing all 3 hardware buttons).
I uninstall every time and reboot both the computer and the phone. The drivers simply won't work.
What is going on here? Is the phone/Android 6 still too new to unlock and root?
P.S. I should also say that I go into Developer options and change the Select USB Configuration between PTP and MTP (between which, I have not seen mention of the correct choice. Does it not matter?) - I cannot chose the others RNDIS, Audio Source, or MIDI; it seems to want to default to 'Charging' when I try to change to these choices.
Having the same issues on Windows 8.1. Can't get my 5x to connect to transfer files or to show up in adb.
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
bsinc1962 said:
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
ahunter said:
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
Click to expand...
Click to collapse
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
rgerrans said:
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
Click to expand...
Click to collapse
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
ahunter said:
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
Click to expand...
Click to collapse
Sorry. I should have been more specific. Part of it is I did so many different approaches they've bled together in my head and I was on my way out the door yesterday when I fired off the reply.
To try to break it down from memory (going to throw in a couple of different options since I can’t seem to fully uninstall / reinstall so please provide any corrections once you get it to work or let me know if anything doesn’t match what you find and I’ll try to remember from there):
Phase I (phone on and connected to computer):
Open Device Manager. My phone shows as Android Device | Android Composite ADB Interface or Android ADB Interface.
If it is the Composite version, I believe I had to update it to the straight “Android ADB Interface to get Phase II to work)
If you don’t see that, look to see if you have any uninstalled devices by scanning for new. If so, then right click on that device, and choose “Update Driver”
Choose “Browse my computer for driver software”
Choose the “Have disk” option and browse to your USB Driver folder
From there, choose “Google | Android ADB Interface”
Phase II (phone in recovery connected to computer)
On phone, choose “Update device from ADB”
Open Device Manager and you should see the Nexus 5 under Other Devices with the yellow triangle.
Right click on it and “Update Drivers”
Choose “Browse my computer for driver software”
Choose “Let me pick from a list….”
Choose “Android Device”
Choose “Android ADB Interface”
Now you should be able to push the update over
Simple method: What I did was plug it in and wait for it to show up in device manager. Then I deleted the device (the one that shows adb) from device manager. Then I unplugged the device and plugged it back in... Then waited for drivers to install on it's own. Everything was good after that.
I have no trouble other than on Windows 10. Windows 10 doesn't even show the drivers from a list to install.
Sent from my Nexus 5X using Tapatalk
I followed this to get my Nexus 5X detected on my Windows 10: http://stackoverflow.com/questions/...ould-we-use-for-the-nexus-5/19839812#19839812
I have no trouble with Fastboot or adb. It only happens when I try and sideload. I end up have to use my Macbook Pro to sideload.
Sent from my Nexus 5X using Tapatalk
bsinc1962 said:
Just need the right drivers. Download the driver files from here:
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I wish it were that easy. But, no, this does not work. Nor do I believe my issue is the same as you others here, as I have Windows 7 and not the 8.1 and 10 issues that you are having.
No, no matter what driver I use, including any from your kind link, bsinc1962, they return an error, code 10 when trying just to install the drivers. I cannot go further.
What is this Code 10 error preventing drivers from installing?

USB Device Not Recognized - Win10

tl;dr: Boot your Moto in Fastboot mode with USB connected to PC for it to recognize the device, then reboot normally.
For those with issues with their PC recognizing the device, in my case Verizon's Droid variant. I racked my brain all weekend and tried multiple different cables and PCs in order to push some ADB commands and transfer files with nothing seeming to get the PCs to recognize the phone. I just now rebooted into Fastboot mode and the PC now recognizes the phone, both in Fastboot and under normal boot. Hope this helps anyone with a similar problem. Cheers!
I have tried this method and still the PC does not see the Phone in File Transfer mode but will see it in Photo transfer.
Help, I have the Moto 6.4 drivers installed, when I check device Manger on the PC i see "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)"
If I try to force a driver update I am told the "INF" is invalid. Any suggestions are welcome, this has me scratching me head and is driving me nuts.
Connect your phone first
and Choose Usb to File Transfer in Mobile
In PC
Go to the Device Manager
And you will see Portable Devices
and there your Device Name or Unknown Device
Open it By clicking Double
Click Driver
ThenUpdate Driver
then you have tow option to fix
1.Search automatically for update driver software
2.Browse my Computer for driver software
I recommendedd OPTION 2
then come up two option
1.Browse driver software
2.Let me pick from a list of device drivers on my computerr
I recommended OPTION 2
and computer will show you all Compatible driver
I recommended to select MTP USB Device
THen NEXT NEXT BOOM
mijing said:
Connect your phone first
and Choose Usb to File Transfer in Mobile
In PC
Go to the Device Manager
And you will see Portable Devices
and there your Device Name or Unknown Device
Open it By clicking Double
Click Driver
ThenUpdate Driver
then you have tow option to fix
1.Search automatically for update driver software
2.Browse my Computer for driver software
I recommendedd OPTION 2
then come up two option
1.Browse driver software
2.Let me pick from a list of device drivers on my computerr
I recommended OPTION 2
and computer will show you all Compatible driver
I recommended to select MTP USB Device
THen NEXT NEXT BOOM
Click to expand...
Click to collapse
BOOM, Thank you worked like a charm... after trying every other way I could think of was driving me nuts.
mijing said:
Connect your phone first
and Choose Usb to File Transfer in Mobile
-- snip --
THen NEXT NEXT BOOM
Click to expand...
Click to collapse
Thanks so much! Was having same issue as OP but with Win 7 and Moto Z2 Force. Even with the Motorola Device Manager app installed, I the device kept showing up as "unknown" in Windows Device Manager.
I've updated your steps to include one you left out (in bold):
Connect your phone first
and Choose Usb to File Transfer in Mobile
In PC
Go to the Device Manager
And you will see Portable Devices
and there your Device Name or Unknown Device
Open it By clicking Double
Click Driver
ThenUpdate Driver
then you have tow option to fix
1.Search automatically for update driver software
2.Browse my Computer for driver software
I recommendedd OPTION 2
then come up two option
1.Browse driver software
2.Let me pick from a list of device drivers on my computerr
I recommended OPTION 2
and computer will show you all Compatible driver
I recommended to select Mobile Device
Then select MTP USB Device
THen NEXT NEXT BOOM​

Categories

Resources