Related
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!
haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!
bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.
I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid
I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!
Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!
Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work
matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!
thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!
I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box
Hey everyone,
I've read through the All-In-One guide about how to root the TF700T, downloaded the driver pack, put it into developer mode and enabled unknown sources. When I plugged the device into my computer it was immediately recognized and automatically installed the drivers and I can see it through Windows Explorer and browse the file system.
Unfortunately the device doesn't show in adb and I read through this quote in the guide, "if not, install the ADB drivers from Windows Device Manager (if you don't know how to do it then you better stay off from rooting your device)" so I went to the Device Driver and and tried to update the driver with the ADB driver, however, it says it's not compatible.
On the Android device I see the USB mode as Media Device (MTP) and that USB Debugging Connected
In Windows Device manager I see under "Portable Devices" the "ASUS Transformer Pad TF700T" is there and installed without error.
There aren't any device drivers that have a yellow icon indicating they aren't configured correctly.
I had purchased the tablet a few days back and it prompted me for a system update which I did.
I've tried rebooting both my computer and the tablet but it didn't appear to assist.
I'm assuming I'm doing something silly and simple but I cannot for the life of me figure it out.
Does anyone have any suggestions on what I may be doing wrong?
Thanks in advance everyone,
Septurious
Search for universal adb drivers in Google. It should lead you to a thread on XDA in the TF101 section.
Sent from my Galaxy Nexus using xda premium
Thanks!
Nebucatnetzer said:
Search for universal adb drivers in Google. It should lead you to a thread on XDA in the TF101 section.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the info! I searched for "universal adb driver xda" in good ol Google and got to this post.
Downloaded the drivers and started to do the install process described in the post but when I did the "uninstall and delete" drivers deal and then replugged in the TF700T I quickly clicked on the "driver install" dialog in windows and told it NOT to search Windows Update which seemed to cause it to grab the adb drivers that I grabbed from the original post and voila it worked.
After running through the debugfs script and running the SuperUser program once I was rooted and finally got smartdimmer and remote management disabled.
Thanks so much for your reply, most appreciated!
Septurious
Glad I could help.
Excuse me that I didn't post the link directly it's a pain on the phone.
I had a similar problem. The TF700 was automatically found, and no ADB drivers were installed. I kept trying to uninstall the driver, but it wouldnt let me. I don't have an option to "delete drivers" on uninstall.
When I tried installing "legacy hardware" to force the drivers, it would come up listed under "Samsung" and not Asus. I think I have my drivers all screwed up from previous phones i've had. I took the driver set, and went to another PC (same os, Win 7 ult x64), and had no problem installing all the drivers and rooting.
Anyone have an idea for me? Not sure if I should start going through my sys32 and manually deleting all driver files associated with my tablet.
Fixed.
I had to do this.
http://www.thewindowsclub.com/how-to-remove-old-unused-device-drivers-in-windows-7
Went through and cleaned up all the old drivers, between the old Samsung Drivers, Motorola Drivers, previous Android ADB drivers. I now plugged in my TF700, and while the ADB shows up as a Samsung device, it shows up on "adb devices", which it didnt before.
Another solution
I tried all listed tips but failed.
ADB driver was installed automaticaly after enabling USB-modem on my TF700.
Now android device chooser showing device
for hours i tried it! no i know why it didnt work!
turn off windows firewall!!! DD maaaaaan
Septurious said:
Thanks for the info! I searched for "universal adb driver xda" in good ol Google and got to this post.
Downloaded the drivers and started to do the install process described in the post but when I did the "uninstall and delete" drivers deal and then replugged in the TF700T I quickly clicked on the "driver install" dialog in windows and told it NOT to search Windows Update which seemed to cause it to grab the adb drivers that I grabbed from the original post and voila it worked.
After running through the debugfs script and running the SuperUser program once I was rooted and finally got smartdimmer and remote management disabled.
Thanks so much for your reply, most appreciated!
Septurious
Click to expand...
Click to collapse
>> I have the same problem and do the same thing, but windows didn't install drivers: its show a message indicating a problem with the hash of catalogue.
Anyone can help?
GBDias said:
>> I have the same problem and do the same thing, but windows didn't install drivers: its show a message indicating a problem with the hash of catalogue.
Anyone can help?
Click to expand...
Click to collapse
Windows 8?
Try disabling driver signature verification.
Sent from my DROID4 using Tapatalk
I can not figure out what the hell I am doing wrong here.
I downloaded the naked driver pack on the guide page labeled 'Drivers TF700: Windows (Patched Universal Naked Driver)'. I unzipped the folder and plugged my TF700 into my computer. I then opened up the Device Manager and clicked on 'Asus Android Devices', then right clicked on 'Asus Android Composite ADB Interface' and pressed uninstall. I checked the 'delete the driver software for this device' and pressed OK.
The drivers uninstalled successfully and I turned off my WiFi card. I then unplugged and re-plugged my TF700 and navigated to 'Other Devices' in the Device Manager. I right clicked on 'Asus Android Composite ADB Interface' and clicked 'update driver software...' and then on 'browse my computer for driver software'.
I then navigated to the folder that I unzipped the driver pack to and tried to install them (clicking the 'include sub-folders' option). No go, I got the error message 'Windows was unable to find the driver software for your device' or something very similar. I then tried specifically pointing to both the i386 and amd64 sub-folders just to see if that wouldn't work somehow but I got the same error message.
What am I doing wrong? I am using a Lenovo G550 (I think) 32-bit laptop running Windows 7. My TF700 is rooted and unlocked but not much else has been done to it.
If anyone can help me get these installed I would really appreciate it. I assume I can probably set up NvFlash with the standard Asus drivers but I would rather set it up exactly the way it is recommended to ensure success.
Massive thanks in advance!
Blake
Put the device in apx mode then try that process. It should show up as an APX device and that's what you apply the nvflash drivers to.
diablodow said:
Put the device in apx mode then try that process. It should show up as an APX device and that's what you apply the nvflash drivers to.
Click to expand...
Click to collapse
That step isn't till later
@OP - let it update the drivers form Windows. That should be fine. As long as you can see the device and it has no errors or warnings around it. you only need the specific drivers when you get to the APX mode, then it will find them.
I had pretty much the same problem, but it turned out it went a lot smoother with reboot in between. Try that, and disable Windows' desperate searching for drivers on Windows Update -- I got some funky drivers and device designations from the WHQL drivers... Please report back in with any progress or lack thereof, and we'll try and get you back on track.
MartyHulskemper said:
I had pretty much the same problem, but it turned out it went a lot smoother with reboot in between. Try that, and disable Windows' desperate searching for drivers on Windows Update -- I got some funky drivers and device designations from the WHQL drivers... Please report back in with any progress or lack thereof, and we'll try and get you back on track.
Click to expand...
Click to collapse
This.
I had big time problems as well with installing these correctly. You need to reboot after uninstalling all old drivers. 1) Hook up Infinity in Android Debug mode 2) uninstall/delete old drivers like you did 3) reboot PC 4) Plug in Infinity again in Android Debug mode 5) install drivers manually through hardware wizard (use have disk option)
Repeat this process for fastboot mode. Note: you will get a warning that you are installing drivers that have not passed WHQL. Disregard. Install anyways.
Its a pain in the butt process but you have to reboot after uninstalling each old driver. You should probably reboot and remove Infinity USB connection after each successful install of new drivers. This is how I got everything to work. I also tried a different USB port.
Sent from my SCH-I535 using Tapatalk 2
SOTK said:
Repeat this process for fastboot mode. Note: you will get a warning that you are installing drivers that have not passed WHQL. Disregard. Install anyways.
Its a pain in the butt process but you have to reboot after uninstalling each old driver. You should probably reboot and remove Infinity USB connection after each successful install of new drivers. This is how I got everything to work. I also tried a different USB port.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you clarify this? What do you mean by 'repeat this for fastboot mode'?
Sent from my unlocked Transformer Infinity
Still no luck. I uninstalled 'ASUS ABD Interface', unplugged the TF700, restarted the computer, plugged the tablet back in, and tried to uninstall. Told me the same thing, that Windows could not find the driver software.
Any other ideas? I have no clue what to do now...
Sent from my unlocked Transformer Infinity
I_EAT_BABIES said:
If anyone can help me get these installed I would really appreciate it. I assume I can probably set up NvFlash with the standard Asus drivers but I would rather set it up exactly the way it is recommended to ensure success.
Massive thanks in advance!
Blake
Click to expand...
Click to collapse
I am having the same exact issue. And strangely I get the same results on both my laptop and desk top systems. I search the forums for solutions and found the same answers that were suggested here but nothing works for me. I just can't figure out what I am doing wrong since so many others seem to be able to install the drivers without problems. Did you ever resolve your driver issue? Are you certain that the standard ASUS drivers will work?
Eddie Hicks said:
I am having the same exact issue. And strangely I get the same results on both my laptop and desk top systems. I search the forums for solutions and found the same answers that were suggested here but nothing works for me. I just can't figure out what I am doing wrong since so many others seem to be able to install the drivers without problems. Did you ever resolve your driver issue? Are you certain that the standard ASUS drivers will work?
Click to expand...
Click to collapse
Guys you need to install those drivers manually,it's not that hard.Here's how you should do it:
1) Put your device in Fastboot or APX mode (depend on the driver you want to install) and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
Also you should disable UAC if it's enabled.
Pretoriano80 said:
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
Click to expand...
Click to collapse
Thank you very, very much but I just figured that out and came back to this thread to tell it. I wasn't doing the "Have Disk" thing. I was just browsing to the driver's folder. I just successfully installed NVflash. I installed the ADB drivers at first but during the Nvflash installation process I had to go back and install the APX drivers. Thanks again. Now time for Jelly Bean.
Eddie Hicks said:
Thank you very, very much but I just figured that out and came back to this thread to tell it. I wasn't doing the "Have Disk" thing. I was just browsing to the driver's folder. I just successfully installed NVflash. I installed the ADB drivers at first but during the Nvflash installation process I had to go back and install the APX drivers. Thanks again. Now time for Jelly Bean.
Click to expand...
Click to collapse
Haha, nice! but still be very careful, 98% of the brick situation on tf700, NVflash didn't help at all.
buhohitr said:
Haha, nice! but still be very careful, 98% of the brick situation on tf700, NVflash didn't help at all.
Click to expand...
Click to collapse
Is the other way around, NvFlash will help you in 98% of bricks situation, if you don't believe try to investigate more, you can even try to wipe your bootloader if you want to check that percentage.
Pretoriano80 said:
Guys you need to install those drivers manually,it's not that hard.Here's how you should do it:
1) Put your device in Fastboot or APX mode (depend on the driver you want to install) and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
Also you should disable UAC if it's enabled.
Click to expand...
Click to collapse
I'm still not getting it I guess. I am assuming when doing it this way you do not uninstall the original drivers first or else the computer would not recognize the device correctly, please correct me if I am wrong.
I keep seeing this supposed "have disk" option talked about but I don't see it anywhere. Could someone please screenshot it for me?
Thanks for all the help guys, I (hope) I am close to getting it.
Sent from my unlocked Transformer Infinity
Pretoriano80 said:
Is the other way around, NvFlash will help you in 98% of bricks situation, if you don't believe try to investigate more, you can even try to wipe your bootloader if you want to check that percentage.
Click to expand...
Click to collapse
I'm talking about nvflash for the tf700 only. 98% of ppl in the tf700 experienced this type of issue where nvflash is uselessmost I believe cause by install custom recovery), where your pc failed to see your device. Below is another sample.
http://forum.xda-developers.com/showthread.php?t=1778353
buhohitr said:
I'm talking about nvflash for the tf700 only. 98% of ppl in the tf700 experienced this type of issue where nvflash is uselessmost I believe cause by install custom recovery), where your pc failed to see your device. Below is another sample.
http://forum.xda-developers.com/showthread.php?t=1778353
Click to expand...
Click to collapse
So I see you are trolling this thread too... 98%??? Really??? Can you give a source for that or is that a number you just made up?
NVFlash is useless if you have not already made the backups. But you are completely incorrect if you are suggesting that it is useless even if you have made the backups.
Best not to troll when you clearly do not understand what you are talking about
I_EAT_BABIES said:
I'm still not getting it I guess. I am assuming when doing it this way you do not uninstall the original drivers first or else the computer would not recognize the device correctly, please correct me if I am wrong.
I keep seeing this supposed "have disk" option talked about but I don't see it anywhere. Could someone please screenshot it for me?
Thanks for all the help guys, I (hope) I am close to getting it.
Sent from my unlocked Transformer Infinity
Click to expand...
Click to collapse
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
I_EAT_BABIES said:
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Damn,i can't believe this....When you get to this step " 4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK ... " look on the right bottom of that menu,do you see a "Have Disk" button?.
I_EAT_BABIES said:
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Here is a screen capture from my system. Look in the lower right for the HAVE DISK button. Following the directions giving earlier should get you to this point. Just click HAVE DISK and guide to where you have the drivers on your system. You may not see the list of drivers as on the screen capture the first time you do it. Since I have already installed the drivers the system remembered where to look so the drivers are visible. Also make sure to connect your tablet to your computer in order for the device to be visible in device manager. The device in device manager should say android ABD Interface or something of that sort. It took me awhile to get it too
****edit***
Apparently the link opens another page.Once on that page click the little box for the image.
https://www.dropbox.com/s/ykuv2ac6zxdln7i/driver_update.JPG
As of the time of this reply I have got the Fasboot drivers installed, but I still saw now "have disk" option. After turning UAC off (don't know how that got back on) I was still just selecting a folder as shown in my previous screenshot.
About to try APX, will post results.
Got it! Thank you guys so much, I really appreciate it. This was seriously driving me crazy, but I still don't understand how we are looking at different menus.
***ONLY FOR RELAYS RUNNING ICS 4.0.4***
Samsung had just released the official Jelly Bean 4.1 update for this phone on April 22 or so and this root method only works for Ice Cream Sandwich devices.
I know there's already a thread of how to root the ICS Samsung Galaxy S Relay 4G which is right here: http://forum.xda-developers.com/showthread.php?p=34515281 but I thought that it may be hard for some people to do it without a visual tutorial. Here's my helpful tutorial video of how to root the Samsung Galaxy S Relay 4G: https://plus.google.com/u/0/108388305247615258469/videos <-- You can easily find the video because it's the only video on that album.
Files Needed:
Winrar: http://www.win-rar.com/download.html?&L=0
Odin v3.07: http://www.4shared.com/zip/CGo6TP1O/Odin307.html? or for the latest and updated versions: http://forum.xda-developers.com/showthread.php?t=1738841
Rooted System IMG: http://www.4shared.com/rar/nhGK59WR/SGHT699_rootedtar.html?
CWM File: http://www.4shared.com/zip/wLHTlktW/cwmtar.html?
If none of the links above work, message me at [email protected] or reply to this topic and I will reupload the files.
Steps:
1) On your phone, go to Settings-->Developer Options and turn on USB Debugging.
2) Turn off your phone and put it in Download Mode/Odin mode.
3) Download the odin307, sght699_rooted.tar, and that cwm.tar files from the links given above.
4) Extract all the files with WinRAR or other file extracting programs.
5) Open Odin v3.07
6) Make sure that it says "Added!" on the bottom left box. If it doesn't say Added, unplug and plug your phone from the computer.
7) Deselect/Uncheck "Auto Reboot" and "F. Reset Time"
8) Click on Phone and a pop up should come up.
9) Find the SGHT699_rooted folder that you extracted in Step 4 and open the file inside it.
10) Click Start. This will take a while but it should not take more than 14 minutes.
11) Once it's done, click Reset.
12) Unplug and plug your phone again. It should say "Removed!" when unplugged and "Added!" when plugged on the bottom left box.
13) Deselect/Uncheck "F. Reset Time" but this time, keep the "Auto Reboot" marked/checked.
14) Click on PDA and a popup should come up.
15) Find the cwm folder that you extracted in Step 4 and open the cwm.tar.md5 file.
16) Click Start.
Once it finishes, your phone should reboot and be rooted. To check if it is actually rooted, go on Applications and find Superuser. If it is there, then you are rooted. Enjoy!!
Very nice. You are missing information, need to add the original posts/threads for the files that you mirrored so we can get version numbers and dates associated with the downloads. Feel free to edit the wiki in my sig if you want to help!
Ok. Thanks, but there's a problem. The files I mirrored other than Odin v3.07 are gone. The original link where the original tutorial was is gone. I had the link in my bookmarks but when I click on it, the webpage is unavailable. Ive tried viewing it from other computers and devices and it still wont work. So I decided to make a new one. Thanks again! The links should be updated in a few.
Sent from my SGH-T699 using xda app-developers app
Thanks.
Version is UVAMA2?
Sent from my SGH-T699 using xda premium
XIAOSpider said:
Thanks.
Version is UVAMA2?
Sent from my SGH-T699 using xda premium
Click to expand...
Click to collapse
What's UVAMA2?
USB won't connect properly; want to un-root
You're rooting video was very helpful.
However, now that the phone is rooted, when I try to connect to my computer with USB cable, I get error message to the effect that the computer can't recognize the hardware ID of the device, so can't back-up the files on the phone or the SD card. I have all the latest Samsung USB drivers, and the computer recognizes that a Samsung device is connected, but the USB connection fails anyway.
How do I un-root the phone - do I have to boot up in download mode and use ODIN? Will this wipe my data, or just go back to the unrooted ROM and keep my data intact?
-----------
Chrizuki said:
I know there's already a thread of how to root the Samsung Galaxy S Relay 4G which is right here: http://forum.xda-developers.com/showthread.php?p=34515281 but I thought that it may be hard for some people to do it without a visual tutorial. Here's my helpful tutorial video of how to root the Samsung Galaxy S Relay 4G: http://www.youtube.com/watch?v=GKgemJTeRWo
Files Needed:
Winrar: http://www.win-rar.com/download.html?&L=0
Odin v3.07: http://www.4shared.com/zip/CGo6TP1O/Odin307.html? or for the latest and updated versions: http://forum.xda-developers.com/showthread.php?t=1738841
Rooted System IMG: http://www.4shared.com/rar/nhGK59WR/SGHT699_rootedtar.html?
CWM File: http://www.4shared.com/zip/wLHTlktW/cwmtar.html?
If none of the links above work, message me at [email protected] or reply to this topic and I will reupload the files.
Steps:
1) On your phone, go to Settings-->Developer Options and turn on USB Debugging.
2) Turn off your phone and put it in Download Mode/Odin mode.
3) Download the odin307, sght699_rooted.tar, and that cwm.tar files from the links given above.
4) Extract all the files with WinRAR or other file extracting programs.
5) Open Odin v3.07
6) Make sure that it says "Added!" on the bottom left box. If it doesn't say Added, unplug and plug your phone from the computer.
7) Deselect/Uncheck "Auto Reboot" and "F. Reset Time"
8) Click on Phone and a pop up should come up.
9) Find the SGHT699_rooted folder that you extracted in Step 4 and open the file inside it.
10) Click Start. This will take a while but it should not take more than 14 minutes.
11) Once it's done, click Reset.
12) Unplug and plug your phone again. It should say "Removed!" when unplugged and "Added!" when plugged on the bottom left box.
13) Deselect/Uncheck "F. Reset Time" but this time, keep the "Auto Reboot" marked/checked.
14) Click on PDA and a popup should come up.
15) Find the cwm folder that you extracted in Step 4 and open the cwm.tar.md5 file.
16) Click Start.
Once it finishes, your phone should reboot and be rooted. To check if it is actually rooted, go on Applications and find Superuser. If it is there, then you are rooted. Enjoy!!
Click to expand...
Click to collapse
nosch454 said:
You're rooting video was very helpful.
However, now that the phone is rooted, when I try to connect to my computer with USB cable, I get error message to the effect that the computer can't recognize the hardware ID of the device, so can't back-up the files on the phone or the SD card. I have all the latest Samsung USB drivers, and the computer recognizes that a Samsung device is connected, but the USB connection fails anyway.
How do I un-root the phone - do I have to boot up in download mode and use ODIN? Will this wipe my data, or just go back to the unrooted ROM and keep my data intact?
-----------
Click to expand...
Click to collapse
Oops, sorry. Forgot the part of your reply that said you've installed all the drivers. What do you mean by it can't recognize it? Does the SGH-T699 still show up on your My Computer?
If you want to unroot, go here: http://forum.xda-developers.com/showthread.php?t=2166242
Just follow the steps and no, it won't wipe out all your data (Well, it didn't wipe mine, but I'm sure it won't.)
Sent from my SGH-T699 using xda app-developers app
Problems connecting with USB (MTP driver install failure)
Chrizuki said:
Oops, sorry. Forgot the part of your reply that said you've installed all the drivers. What do you mean by it can't recognize it? Does the SGH-T699 still show up on your My Computer?
If you want to unroot, go here: http://forum.xda-developers.com/showthread.php?t=2166242
Just follow the steps and no, it won't wipe out all your data (Well, it didn't wipe mine, but I'm sure it won't.)
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
When I connect the USB cable, Windows has a popup message that says:
" Hardware ID missing
Windows cannot identify the device plugged into the Samsung Mobile USB Composite Device.
For assistance, contact the hardware manufacturer"
Sometimes it tries - and fails - to install the MTP device driver.
However, when I go into Windows Device Manage, it does list SAMSUNG Android Phone | SAMSUNG Android ADB Interface, and when trying to update its drivers, it says I have the most up to date ones installed.
- What does "Hardware ID missing" mean? How do I get the phone to communicate with the computer using USB?
I thought it might have to do with Android Ice Cream Sandwich and the media device (MTP) protocol for USB, but, I had no problems getting the computer to recognize my son's (unrooted) Galaxy S 3, which also has ICS and is pretty similar to the Galaxy S Relay 4G. That's why I suspect the problem is with my rooted version.
Is there anything else I should try before un-rooting the phone?
nosch454 said:
When I connect the USB cable, Windows has a popup message that says:
" Hardware ID missing
Windows cannot identify the device plugged into the Samsung Mobile USB Composite Device.
For assistance, contact the hardware manufacturer"
Sometimes it tries - and fails - to install the MTP device driver.
However, when I go into Windows Device Manage, it does list SAMSUNG Android Phone | SAMSUNG Android ADB Interface, and when trying to update its drivers, it says I have the most up to date ones installed.
- What does "Hardware ID missing" mean? How do I get the phone to communicate with the computer using USB?
I thought it might have to do with Android Ice Cream Sandwich and the media device (MTP) protocol for USB, but, I had no problems getting the computer to recognize my son's (unrooted) Galaxy S 3, which also has ICS and is pretty similar to the Galaxy S Relay 4G. That's why I suspect the problem is with my rooted version.
Is there anything else I should try before un-rooting the phone?
Click to expand...
Click to collapse
Install kies or the USB driver directly from samsung.com. Try the USB driver first, then kies if it doesn't work.
Nocturin said:
Install kies or the USB driver directly from samsung.com. Try the USB driver first, then kies if it doesn't work.
Click to expand...
Click to collapse
Already tried both. USB driver is OK, the problem is with MTP. Kies only works via WiFi; does not recognize device with USB. I also tried Samsung tech support's suggestions, none of which changed the situation
nosch454 said:
Already tried both. USB driver is OK, the problem is with MTP. Kies only works via WiFi; does not recognize device with USB. I also tried Samsung tech support's suggestions, none of which changed the situation
Click to expand...
Click to collapse
Have you tried downloading the SDK Manager from "http://developer.android.com/sdk/index.html"? Open the big file that you just downloaded and open up SDK Manager. Install the Google USB Driver and as well as the Android SDK Tools and Android SDK Platform-tools. Once downloaded, go back to the android-sdk-windows folder and go to the "platform-tools" folder inside and hold Shift and right click on "adb" and select "Open Command Window Here" of something like that. The command prompt will open. Type in "adb devices" and tell me what comes up. If you see your device(It should be a bunch on numbers and letters) on there, it means it is recognizable. This might not solve your problem as I do not know what "Hardware ID missing" exactly is. But I will do some research.
I did as you suggested, and was able to see my phone when I ran "adb devices" from the command prompt. And, Windows, recognizes it too, because when I click on the button to remove attached USB devices, it lists SAMSUNG_Android_SGH-T699. But, I still get the hardware ID missing message whenever I connect the USB cable. Frustrating! But, thanks for trying to help me - you seem very knowledgeable.
What you can try and do to fix the USB hardware error is go to control panel then go to "uninstall a program" and uninstall the samsung driver once you uninstalled it reconnect your phone and let it reinstal the files and i believe it should fix your problem
Samsung Noob here with a question.
Ok, I know this is gonna sound kinda noobish, but I come from HTC phones, and this is my first Samsung. Do I need to flash ClockworkMod Recovery on this, or do I flash a rom to the 4G Relay using Odin? If I use Odin, can someone give a quick overview on how?
Gh0sTly said:
Ok, I know this is gonna sound kinda noobish, but I come from HTC phones, and this is my first Samsung. Do I need to flash ClockworkMod Recovery on this, or do I flash a rom to the 4G Relay using Odin? If I use Odin, can someone give a quick overview on how?
Click to expand...
Click to collapse
you'll need to install a recovery as you did on HTC as ROMs usually come as recovery-flashable zips.
there's a cwm recovery available here which can flashed using Odin. If you don't like the cwm on the relay you can flash TWRP from cwm over it. TWRP comes with more options and the touchscreen-control you might be used to.
from (any) recovery you can just install update zip-files just as you used to on your HTC.
I had used the "howto root the Galaxy S Relay" thread, and then realized, I should just SU and reboot recovery. :victory:
nosch454 said:
I did as you suggested, and was able to see my phone when I ran "adb devices" from the command prompt. And, Windows, recognizes it too, because when I click on the button to remove attached USB devices, it lists SAMSUNG_Android_SGH-T699. But, I still get the hardware ID missing message whenever I connect the USB cable. Frustrating! But, thanks for trying to help me - you seem very knowledgeable.
Click to expand...
Click to collapse
If anybody else got this error do the following:
- uninstall all samsung drivers / software
- connect your phone to the pc
- the driver installation should 'fail', but you can access the storage
- install the samsung drivers now while phone is plugged in
After the installation the phone will be recognized and everything is fine - this worked twice for me now, so I guess it should do it.
My phone is still a stock phone, all I have used was only official OTA updates in the past 2 years. All I wanted to do are just flash recovery and try some 3rd party ROMs on this phone. To get everything started I have to unlock bootloader via HTCdev, or maybe do some backup using Helium. Either way I will have to connect my phone to my pc via USB cable. But the USB just not detected. I think there's a problem caused by the 4.2.2 update? Before that everything was fine. See what I've tried already below.
Model of my phone
>One XL Asia (international?)
Bootloader details
>In the attachments
Current ROM/kernel
>Stock
Current recovery
>Not flashed yet
All events that lead to your current situation
>I haven't done anything to it
What you've tried already
✓unplug and replug (over 9000 times)
✓uncheck and check USB debug (over 9000 times)
✓reboot my phone and try again (a few times)
✓uninstall USB driver on my PC, then reboot PC, re-install (a few times)
✓switch cable
✓switch PC
✓switch USB port
✓switch phone:
magically, when I switch phone, which is a HTC desire, everything works fine, USB detected, adb works well, fastboot command works well
under same condition, everything works fine on the desire, but only when I plug my One XL in, everything don't work, so I bet the problem is on the phone?
Anything else that's relevant
>Phone running Android 4.2.2
>My PC runs 64-bit Win 7
>Maybe what I included in attachment will be useful?
I have the basic knowledge on flashing ROMs and stuffs, but I'm a noob in front of all you gods, please help.
Go to the device manager and try deleting the One XL entry
Sent from my HTC One XL using Tapatalk
pandasa123 said:
Go to the device manager and try deleting the One XL entry
Sent from my HTC One XL using Tapatalk
Click to expand...
Click to collapse
"One XL" not found in device manager, it shows "unknown device" removing that does nothing
Can you get Harware ID for that Unknown device from Device manager??
If you can add that Hardware Id to your Drivers .ini file and update the driver manually pointing to that driver folder.
Edit: I tried the drivers from this post and they worked for me
http://forum.xda-developers.com/showthread.php?t=2061435
sathish804 said:
Can you get Harware ID for that Unknown device from Device manager??
If you can add that Hardware Id to your Drivers .ini file and update the driver manually pointing to that driver folder.
Edit: I tried the drivers from this post and they worked for me
http://forum.xda-developers.com/showthread.php?t=2061435
Click to expand...
Click to collapse
Where are the drivers .ini files? And how to do it?
Sad;y the link doesn't work for me
joetong2006 said:
Where are the drivers .ini files? And how to do it?
Sad;y the link doesn't work for me
Click to expand...
Click to collapse
In the link I posted you will find a link to download the Win 7 64 bit drivers for HTC.
http://d-h.st/OYI
Unzip the archive downloaded from the link. In the extracted folder you will find a file named "androidusb.ini" open it with Notepad and Add your device hardware id found from the device manager to the file like below and save it.
%MyHTC%=HTCAND64.Dev, USB\XXHARDWARE_IDXXXXX
Follow the steps from this link to update your drivers once above modification is done.
http://pcsupport.about.com/od/fixtheproblem/ht/update-drivers-windows-7.htm
sathish804 said:
In the link I posted you will find a link to download the Win 7 64 bit drivers for HTC.
http://d-h.st/OYI
Unzip the archive downloaded from the link. In the extracted folder you will find a file named "androidusb.ini" open it with Notepad and Add your device hardware id found from the device manager to the file like below and save it.
%MyHTC%=HTCAND64.Dev, USB\XXHARDWARE_IDXXXXX
Follow the steps from this link to update your drivers once above modification is done.
http://pcsupport.about.com/od/fixtheproblem/ht/update-drivers-windows-7.htm
Click to expand...
Click to collapse
sorry i have been busy round these days, no time to deal with my phone
look at the attachments and you'll know why i included some Chinese words, in case my roughly translation is not accurate, you can still copy them and see what google translate says
i right clicked on the "unknown device" in device manager, and clicked into Properties(內容)
and in the 3rd tab(詳細資料), i can't find any similar Hardware Id, but however i found some id-like thing and tried
then when i came to the 10th step of this page: http://pcsupport.about.com/od/fixtheproblem/ht/update-drivers-windows-7.htm
something pops out and says
您指定的資料夾沒有包含裝置可使用的相容軟體驅動程式
如果資料夾中含有驅動程式,請確認它已設計為搭配 適用於 x64 型系統的 Windows 使用
it's roughly says there is not usable driver for win 7 64 bit in that path file i selected, then it did nothing i have to close it
and i just found out, when my phone is in fastboot and USB connected, ADB command works fine, if you know what i mean
that means, i can unlock the bootloader, but still, i need to backup my apps and data, is there an alt solution for me to do backup rather than fixing the driver and use Helium?
joetong2006 said:
that means, i can unlock the bootloader, but still, i need to backup my apps and data, is there an alt solution for me to do backup rather than fixing the driver and use Helium?
Click to expand...
Click to collapse
Why not use the methods on XDA? I don't recommend anything from outside of XDA
pandasa123 said:
Why not use the methods on XDA? I don't recommend anything from outside of XDA
Click to expand...
Click to collapse
Do you mean unlocking the phone or the backup?
joetong2006 said:
sorry i have been busy round these days, no time to deal with my phone
look at the attachments and you'll know why i included some Chinese words, in case my roughly translation is not accurate, you can still copy them and see what google translate says
i right clicked on the "unknown device" in device manager, and clicked into Properties(內容)
and in the 3rd tab(詳細資料), i can't find any similar Hardware Id, but however i found some id-like thing and tried
then when i came to the 10th step of this page: http://pcsupport.about.com/od/fixtheproblem/ht/update-drivers-windows-7.htm
something pops out and says
您指定的資料夾沒有包含裝置可使用的相容軟體驅動程式
如果資料夾中含有驅動程式,請確認它已設計為搭配 適用於 x64 型系統的 Windows 使用
it's roughly says there is not usable driver for win 7 64 bit in that path file i selected, then it did nothing i have to close it
and i just found out, when my phone is in fastboot and USB connected, ADB command works fine, if you know what i mean
that means, i can unlock the bootloader, but still, i need to backup my apps and data, is there an alt solution for me to do backup rather than fixing the driver and use Helium?
Click to expand...
Click to collapse
Please change the "Properties" to "Hardware ID's" as in attached screen shot.
sathish804 said:
Please change the "Properties" to "Hardware ID's" as in attached screen shot.
Click to expand...
Click to collapse
Glad I put up screenshot so that you know I was at the wrong place
Pretty sure I'm at the right place this time as the other 2 devices shows the right thing (same cable same port), but it shows "UNKNOWN" :crying:
screenshot in attachment
joetong2006 said:
Glad I put up screenshot so that you know I was at the wrong place
Pretty sure I'm at the right place this time as the other 2 devices shows the right thing (same cable same port), but it shows "UNKNOWN" :crying:
screenshot in attachment
Click to expand...
Click to collapse
Can you see any other devices without drivers in your device manager??
I think it is recognising your phone as USB device.