I installed Unified Toolkit V 7 on my windows 7 operating system. The installation went okay. I started Toolkit and downloaded and installed the drivers for my T-mobile Galaxy S 3. The drivers installed okay. When I looked at my devices in windows, it show my Samsung driver, an icon SGH-T999. However, when I use Unified Toolkit to root my phone, I noticed that the driver icons goes off and on only when I put the cell into the debugging mode. As a result, Toolkit fails to continue and root my phone. The Driver icon goes off and on, until I take it out of the debugging mode. I tried rebooting my computer and cell. I also tried reinstalling the drivers. Please help!
Ronnie
Related
Hi guys, hopefully someone can help.
I rooted the phone using unrevoked and now have clockworkmod recovery on the phone. Tonight I tried to connect the phone to the android SDK with no success.
Windows device manager only shows it as an Android Phone. Everytime I try to manually install the SDK usb drivers, it comes up with a message saying drivers aren't available. I have deleted and reinstalled the SDK usb drivers and have also deleted the android phone from the device manager as well as USBDView. Have had no success whatsoever.
How can I get ADB commands working again on the phone?
EDIT - SOLVED - Apparently I had to reinstall HTC Sync and it worked! strange how these things work!
[FIXED]
For some reason Toolkit didnt work for me and i used this method to unlock bootloaders and root it.
http://forum.xda-developers.com/showthread.php?t=1362957
Also installed CWM recovery
------------------------------------------------------------------------
I installed my drivers and 1st time when I connected my phone in adb toolkit recognised it and showed his id. Next time when I connected it in adb it didnt recognise it in toolkit but windows recognise my phone and i can access it.
I've rebooted my pc every time and reinstalled couple of drivers:
-Naked samsung drivers
-Pda drivers
-Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
Nothing worked.
1st time I used Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0 and i tried again and nothing.
I am on Windows 7 64bit version.
If anyone knows how to solve this please share the idea.
sukyman said:
I installed my drivers and 1st time when I connected my phone in adb toolkit recognised it and showed his id. Next time when I connected it in adb it didnt recognise it in toolkit but windows recognise my phone and i can access it.
I've rebooted my pc every time and reinstalled couple of drivers:
-Naked samsung drivers
-Pda drivers
-Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
Nothing worked.
1st time I used Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0 and i tried again and nothing.
I am on Windows 7 64bit version.
If anyone knows how to solve this please share the idea.
Click to expand...
Click to collapse
I was facing lot of driver issues when connecting my GNex for the first time to the laptop on WinXP. Installing the drivers through the GNex Toolkit also did not work for me.
Finally what worked for me was, installing the latest version of Android SDK with the additional package of Google USB drivers, and then manually selecting the drivers after connecting my phone instead of asking Windows to look for drivers automatically.
I had trouble when first connecting my GNex too. However, these drivers worked for me (plus work with many many other android devices):
http://forum.xda-developers.com/showthread.php?t=1379875
If you have several android devices you'll find that you don't have to install multiple drivers for adb, fastboot, etc. for each of the devices.
Taken from post#3 of the ToolKit thread:
Note 1: If the driver doesnt install automatically then double click on the Android 1.0 item, then click on the driver tab and select 'update driver'. Select 'browse my computer' and then 'Let me pick from a list'. If no items appear in the list then untick 'Show compatible hardware' and find the Android adb driver or Samsung adb driver.
Try that as they may be on your pc and just not installing.
Mark.
Got them working now but i have problem when rooting, using GNex toolkit 5.6
It boots into android, i set usb debugging but when the phone is suppose to boot back to fastboot it gives error device not connected.
I was able to install the ADB and fastboot drivers for my Galaxy Nexus no problem (using both manually installed INF files and device manager, an the wugfresh toolkit), but when I do the same thing with the N72013, it just never recognizes my device in CMD or with the wugfresh ADB/fastboot test
Any idea what's happening here? I've tried in both Windows 7 and Windows 8
I've used the Google USB driver from the Android SDK, open SDK Manager and scroll to the bottom, check it to install.
- Sent from my Galaxy S3
I have a completely stock, locked and unrooted Nexus 7 2013, and whenever I plug it into my computer, it will not recognize my device.
I've tried:
- checking/unchecking MTP
- switching to PTP
- turning on/off USB debugging
- uninstalling and reinstalling drivers
- Nexus 7 toolkit to install drivers, wouldn't work
- Wugfresh's toolkit, and followed the driver guide, still nothing.
After uninstalling the driver, Windows would allow me to choose a driver to install, but it would always end up saying "Windows has determined the best driver is currently installed" or something similar to that.
I am updated to the latest build, JSS15R. Before I updated, my computer was able to recognize my device just fine.
Is anyone else in the same situation as I am?
Hmmmm, are you using a USB extender cable or a long cable. Mine fails to pick mine up after the JSS15R update unless I use the given micro USB cable.
Sent from my Nexus 7 using XDA Premium HD app
I'm using the cable that came with Nexus 7 that says "ASUS" on it.
When I tried to root my device I had a lot of problems connecting it with my PCs/Notebook.
I tried WinXP, 7 and 8 and got crazy because I never reached a reliable state.
If I remember correctly WugFresh's toolkit has an utility integrated that lists all "Android USB devices". I had to remove them all before it finally worked - and in the end I had to repeat this twice before my Nexus was rooted and had a recovery. And even then I had to dis- and reenable MTP etc. a few times.
After this I had to reinstall different drivers so that it was recognized as MTP again.
Took me one day for a process I expected only an hour.
So try the Root Toolkit and the utility inside.
I tried that. I might have to give it a try again. I might have missed some devices.
Hi, I just flashed the 4.4 official image from google. Still on stock recovery.
I do plan to install custom recovery to flash some custom rom now.
However, when I try to plug my tablet in laptop (windows 7 64bit), all i hear is that ding sound, hover over the usb devices i would see nexus 7, but it is not showing in the Windows Explorer.
PTP would show, but MTP wouldnt, with or without usb debugging enabled.
I tried to update my usb driver from google via SDK, i uninstalled first before upgrading so its a clean install, however i am still stuck here.
Any other solution?
hhwong said:
Hi, I just flashed the 4.4 official image from google. Still on stock recovery.
I do plan to install custom recovery to flash some custom rom now.
However, when I try to plug my tablet in laptop (windows 7 64bit), all i hear is that ding sound, hover over the usb devices i would see nexus 7, but it is not showing in the Windows Explorer.
PTP would show, but MTP wouldnt, with or without usb debugging enabled.
I tried to update my usb driver from google via SDK, i uninstalled first before upgrading so its a clean install, however i am still stuck here.
Any other solution?
Click to expand...
Click to collapse
If you have Wugfrest Root Kit, in there Click Full Driver Installation Guide - Automatic + Manual and follow his instruction.
Or you can uninstall the driver and update the driver yourself to a specific location on your computer. (this method i used) I run Win 7, and it would detect Nexus 7 but fail, when it told me to update driver i went to the folder where i put the drivers. Eventually you will find the right driver. Its a pain in butt to get the drivers to work sometimes.
Duffmantp said:
If you have Wugfrest Root Kit, in there Click Full Driver Installation Guide - Automatic + Manual and follow his instruction.
Or you can uninstall the driver and update the driver yourself to a specific location on your computer. (this method i used) I run Win 7, and it would detect Nexus 7 but fail, when it told me to update driver i went to the folder where i put the drivers. Eventually you will find the right driver. Its a pain in butt to get the drivers to work sometimes.
Click to expand...
Click to collapse
I manually updated the driver from the SDK and it worked, not too ure why exactly......but oh well.....its working as MTP with usb debugging enabled now