After many hours googling and searching here, I have finally successfully rooted my new Verizon Galaxy S4 (SGH-i545), and it had nothing to do with the root process itself, but it was the basic setup that was giving me fits.
Googling and searching has shown that this is actually a common enough problem with some Samsung devices, and there is a fix for it. Since I had to combine several different processes, I thought I would add a note here on how to get the device connected. I will leave the rooting and other discussions to the others. I am also going to give credit to arpruss, most of the steps here come from his work on the Epic. I have trimmed down to only what is necessary to get ADB working properly.
This assumes that you have already tried the various processes to install or update drivers, and that has not worked. Also assumes mid- to advanced user skills:
1. Install KIES. (Downloading the separate driver package didn't work--the driver package refused to install.)
2. Set device in USB Debug mode (Settings | Applications | Development | USB debugging(x)).
3. Plug device into computer.
4. Run Device Manager
5. Look for SAMSUNG_Android. You shoud see it in the Other devices section.
6. Right-click on "SAMSUNG_Android".
7. Choose "Update driver software" | "Browse my computer for driver software" | "Let me pick from a list".
8. Make sure "Show All Devices" is selected and click on "Next".
9. Click on "Have Disk" and type in "C:\Program Files (x86)\Samsung\USB Drivers\25_escape" (auto complete made it easier to type; if you have 32-bit windows, the " (x86)" should be omitted).
10. You will get a two-pane selection of the drivers. Selecting one of the two "SAMSUNG Electronics Co., Ltd." listings (you may need to look through both) in the left pane gives an option list on the right that includes two "SAMSUNG Android ADB Interface".
11. Choose the first "SAMSUNG Android ADB Interface" and click on "Next". You will get a warning that Windows cannot verify compatibility. Accept this. Windows will install the driver and once it's done you'll click on "Close".
12. Windows installed the driver and ADB started working. (If it didn't start working, I would now have gone back to the Device Manager, right clicked on "SAMSUNG Android ADB Interface", and then redid steps 7-11, but this time with the other "SAMSUNG Android ADB Interface" driver.)
This is enough to get adb working. But it's still probably worth fixing the CDC Serial device.
13. Repeat steps 7-11 in the Device Manager with the "CDC Serial" device now, except that instead of the ADB driver you will look for and install "Samsung Mobile USB CDC Composite Device" in the right pane in steps 10-11.
If all goes well, you will get more spinning stuff in the task bar, and eventually Device Manager doesn't show any devices in "Other devices" with yellow triangles. But if things go for you like they did for me, you'll have "CDC Abstract Control Model (ACM) in "Other devices".
14. Repeat steps 7-9 in the Device Manager with the "CDC Abstract Control Model (ACM)" device now. (You may have some USB Modem options showing up in some places, but I ignored those, and did the same "Have Disk" move as before.)
15. I got a single-pane display showing only "SAMSUNG Mobile USB Modem". (Maybe you'll have two-pane display and you'll have to find it as in steps 10-11.) Select it and click "Next". I didn't get any warnings. Windows will install the driver and once it's done you'll click on "Close".
At this point, Device Manager showed all devices correctly functioning. And "adb shell" worked fine.
16. If you don't want KIES, just uninstall it, but make sure not to uninstall the drivers (the KIES uninstaller will ask).
Related
Problem was solved by changing the xml file to the language code.
Original Problem:
Hi everyone, just got the kindle today and finished root, then I used the Kindle Utility tool to change to fastboot.
As I finished the fastboot, it ended up stuck on the boot screen. Try serverl methods, but did not work.
According to:
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
"Once rebooted, connect your Kindle again via USB. You'll probably hear 3 tones (which means it recognized a device, but didn't load any drivers). In device manager, you'll see a device just called "kindle" or "unknown" with an exclamation point by it. At this point, you'll need to install drivers for it again. Pick "Browse my computer for driver software" BUT don't browse, just click on "Let me pick from a list...", and select "Android Phone" and then pick the newest "Android Composite ADB Interface" from the list. I think you may have 4.0.0.0 or something similar (you may have only a 2.x version possibly depending on which drivers you loaded to root your phone)."
But the problem here is that it the Windows Manager recgnized the kindle as an "Unkown Device" , and also I did not find "Android Phone" from the list, and cannot install driver manually as well. Does anyone have any suggestions?
just right click the unknown device and update the drivers
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Excellent method! Thanks
Hello Everyone,
----------------------------
Nexus 7 Driver Fail
----------------------------
I was Unable to install drivers on Windows XP (ADB and Fastboot Drivers do not load). Every step has failed and multiple drivers fail to install with Code 18 and 28. I’ve tried just about EVERY Tool Kit available out there and searched fourms, still no positive results. If anyone out there may have an answer please feel free to drop it in here, I greatly appreciate all your help. Thank you.
Here is a list of what I have done thus far:
- Rebooted the computer after uninstalling devices with USB Deview before
continuing on to the other steps
- Uninstalling and manually deleting driver from the registry
- Unplugging and repluging the device while watching
the device manager (The device shows up as other devices, Example: nexus and MTP)
- I tried disabling auto driver configuration by Simply pressing the "Disable Auto Driver Config" button and then
changing the settings accordingly
- Registry cleaning
- Removing and manually adding to windows driver folder
- Trying on different User accounts from Admin to guest
- Used Android SDK manual driver installation
- Unplugged the device and Launched USBDevice
- Used USBDeview to uninstall any;
- Android ADB Interface device's
- Samsung USB devices
- Google USB drivers
- ANYTHING else you see that resembles your Nexus.
- Looked for devices with Vendor ID's:"18d1"or"04e8"
I then right clicked these devices, and selected the option to” Uninstall Selected Devices"
-Downloaded The official Asus USB driver off of Asus actual support base
And it said the following: an error occurred during the installation of this device The Parameter is incorrect.
Have I missed this action:
Download the drivers from Asus and unpack them to their own directory.
Connect the N7 with USB debugging enabled in "developer options"
Open Device Manager
Locate the N7
(from here my xp knowledge is rusty)
Right click on the N7 and select properties
Find the option to install/update drivers, Take the option to specify the driver directory where you unpacked the download, ensure that include sub directories is ticked and that should install
peterk-1 said:
Have I missed this action:
Download the drivers from Asus and unpack them to their own directory.
Connect the N7 with USB debugging enabled in "developer options"
Open Device Manager
Locate the N7
(from here my xp knowledge is rusty)
Right click on the N7 and select properties
Find the option to install/update drivers, Take the option to specify the driver directory where you unpacked the download, ensure that include sub directories is ticked and that should install
Click to expand...
Click to collapse
I tried the same steps.
I even tried using Android SDK, Universal Naked driver
Still no luck
N7 running 4.2.1 stock
Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Thanks to:MaxRabbit
Other solutions
Windows 8 Diagnosis
Originally Posted by Yorus
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
Hi All,
After seeming that I'm locked out of my own device for 72 hours, I managed to scour the net and use parts of other tutorials to successfully bypass the "you're device was reset, please log in" loop.
So I should point out I was running a Pure Nexus rom running 6.0 with a custom recovery, you're results may differ but you've got nothing to loose.
Pre Requisite
ADB and Fastboot - You don't need to spend an hour installing the whole kit, just visit http://developer.android.com/sdk/index.html and scroll right down to the section where it says "SDK Tools Only" and click on "installer_r24.4.1-windows.exe"
Once installed the SDK manager will open, now make sure the top 3 are checked which are:
Android SDK Tools
Android SDK Platform-tools
Android SDK Build-tools
And also scroll down in the list to find Google USB Driver
Once all of that is done download the latest Google USB drivers (although the SDK installs USB drivers it still shown an exclamation mark in device manager") http://developer.android.com/sdk/win-usb.html
To install those USB drivers just go into device manager and if you se Nexus 6 under "Other Devices" just right click and click update driver software and then click browse my computer and get it to scan the Google USB driver folder you downloaded.
restart your phone into recovery (Volume Down and Power button)
now again in device manager make sure the Nexus 6 doesn't have a yellow icon identifying there's a problem with drivers or that the nexus 6 is listed in other devices. If either of those are present right click and update drivers > browse from computer and select the Google USB drivers you downloaded previously.
Bypass FRP
With all that confirmed restart your Nexus and leave it on the Welcome screen.
Now, you need to get into platform tools which is located:
C:\Users\YOURUSERNAME\AppData\Local\Android\android-sdk\platform-tools
if you can't see AppData you need to enable hidden files and folders
once in platform tools hold SHIFT and right click any blank space and click "Open command window here"
then type "adb devices" and it should list your nexus under devices, if it doesn't open device manager and check your drivers.
If it does show your nexus execute this command which edited from another source:
"adb shell am start -n com.android.settings/.Settings"
Your nexus will now open the settings menu =] in settings go to "Backup & reset" then click "Factory data reset" (although it says it wipes user data, mine was untouched, I can't say the same for so you may lose some data if you proceed)
your phone will reboot and in my case it opened my custom recovery and executed a script, the phone will restart again and go to boot, hold the power button to force shut down the nexus and boot into recovery mode. In recovery mode flash a ROM, if you don't have a ROM download one on your PC and then connect your Nexus to your PC via USB and copy it over.
Once the ROM is installed you won't get the "you're device was reset" screen.
"
You left out some key details which are covered in the guide I wrote up a few days ago. Here's the link.
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
this does not work, because in order to adb devices to populate anything you would of had to enable usb debugging from within the phone, and if you're locked our from FRP, you cant access the settings to turn on the usb debugging
Bootloader LOCKED .. and asking for gmail ID ??
Please upload drivers for Elephone S7 4G 64GB/4GB . I need drivres for Windows XP SP3. Search in Google,but not find.
no drivers
I had the same problem on windows 10
What you need to do is change or update the driver that Windows is currently using whenever your plug your Android device into the computer via USB. To do this, open the Device Manager by clicking the Start menu and searching for “Device Manager.”
Look for a device that has the “ADB” designation. .” Expand the group by clicking the little arrow on the left, then right-click on the device and select “Update Driver Software” from the context menu.
right click on phone and pick ' let me pick from a list of device drivers on this computer
If you don’t see anything with “ADB” in the name, you may have to look elsewhere. I found it under “Portable Devices,” and it had the yellow exclamation mark that notes there’s a driver issue. Regardless of where you find the device, the required actions should be about the same.
The “Update Driver Software” window will ask you if you search or browse for driver software. You want to choose the browse option, which will advance you to the next step.
On the next screen, select “Let me pick from a list of device drivers on my computer” to advance to the next step.
This will present a long list of potential hardware types–select “Android Device” or “Android Phone.”
Finally, on the last screen you want to select the “MTP USB Device” NOT MTP device and then “Next.”
The device driver will then install over the old one, and your Android device will be recognized as a multimedia device as seen now in the File Manager.
It helped me to install the S7
i have same problem, windows 8.1, please send drivers to conect to pc
thank you
there are no drivers
What you need to do is change or update the driver that Windows is currently using whenever your plug your Android device into the computer via USB. To do this, open the Device Manager by clicking the Start menu and searching for “Device Manager.”
Look for a device that has the “ADB” designation. .” Expand the group by clicking the little arrow on the left, then right-click on the device and select “Update Driver Software” from the context menu.
right click on phone and pick ' let me pick from a list of device drivers on this computer
If you don’t see anything with “ADB” in the name, you may have to look elsewhere. I found it under “Portable Devices,” and it had the yellow exclamation mark that notes there’s a driver issue. Regardless of where you find the device, the required actions should be about the same.
The “Update Driver Software” window will ask you if you search or browse for driver software. You want to choose the browse option, which will advance you to the next step.
On the next screen, select “Let me pick from a list of device drivers on my computer” to advance to the next step.
This will present a long list of potential hardware types–select “Android Device” or “Android Phone.”
Finally, on the last screen you want to select the “MTP USB Device” NOT MTP device and then “Next.”
The device driver will then install over the old one, and your Android device will be recognized as a multimedia device as seen now in the File Manager.
It helped me to install the S7
jon feaver said:
What you need to do is change or update the driver that Windows is currently using whenever your plug your Android device into the computer via USB. To do this, open the Device Manager by clicking the Start menu and searching for “Device Manager.”
Look for a device that has the “ADB” designation. .” Expand the group by clicking the little arrow on the left, then right-click on the device and select “Update Driver Software” from the context menu.
right click on phone and pick ' let me pick from a list of device drivers on this computer
If you don’t see anything with “ADB” in the name, you may have to look elsewhere. I found it under “Portable Devices,” and it had the yellow exclamation mark that notes there’s a driver issue. Regardless of where you find the device, the required actions should be about the same.
The “Update Driver Software” window will ask you if you search or browse for driver software. You want to choose the browse option, which will advance you to the next step.
On the next screen, select “Let me pick from a list of device drivers on my computer” to advance to the next step.
This will present a long list of potential hardware types–select “Android Device” or “Android Phone.”
Finally, on the last screen you want to select the “MTP USB Device” NOT MTP device and then “Next.”
The device driver will then install over the old one, and your Android device will be recognized as a multimedia device as seen now in the File Manager.
It helped me to install the S7
Click to expand...
Click to collapse
Work Ok in Windows 7 Professional 64 Bits.
Thank. :good::good::good:
easy to find.. wind 8.1 and 10 have a very bad driver compatibility... i0ts an OS failure
http://www.drivethelife.com/windows-10/fix-mtp-usb-device-connection-problem-on-windows-10.html
I have the same problem with the drivers of elephone s7.after searching to the web I found a solution that works for me (I have an windows 10 laptop). After trying to update drivers I have an error message. Windows can't find INF folder. And that's the solution.
I hope I help..