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
I just got my SNS yesterday and it's my first android phone (was previously using an LG cookie) First thing I did was try to root it, and I seemingly succeeded, or so I thought. It looks like it's rooted and the superuser apps there but I can't install apps using any of the guides I find or even update to 2.3.2 (keep getting and error 7 msg). When I try to install using APKInstaller it tells me it can't find the device, which I think is the problem.
I think the problem is that someway or another windows 7 64 bit stopped recognizing my phone as a Nexus S and now recognizes it as a portable device in device manager (There's also an Android Phone, with an Android Composite ADB interface) I used the SDK to install all the updates available including the google usb driver rev. 4. I tried updating the Portable device driver using the google usb driver but windows keeps it as a WPD Filesystem Volume Driver. Also I noticed when I checked to see if adb gave me a serial number for the phone using the cmd prompt commands in the rooting guides it comes up blank.
I used usbdeview to delete everything seemingly related to Android, but everytime I reconnect the phone it, installs the drivers for the portable device.
I need help to make windows recognize the phone as a nexus s again so I can update and install apps and games etc. If anybody out there can help i'll really appreciate it. Explain the steps to me as if you were talking to a child, leaving nothing out plz. Thanks for any assistance.
I live outside the US (no android market) and would hate to think I messed up and expense phone purchase in just one day
Not quite sure where to start. But my intuition tells me its the Windows 7 64-bit and drivers that's not playing along. You might want to google if other users are having trouble with W7 64-bit with Android drivers. Otherwise, find another computer and repeat the steps. If not, flash a custom ROM to see if that eliminates the problem. You haven't damaged your phone. Don't worry.
just install directly from android market website
Sent from my Nexus S using XDA App
I assume you mean instal the update from the market (which I can't do because I don't have wifi)?
I managed to get the adb to list a device number after I installed java x32 & x64 bit. I still can't install apps or get the update to work, but I'll try unrooting and then rerooting my phone as see how that goes.
Oh, I haven't done the initial sign into gmail thing yet in case that makes any difference
Edit: god I feel stupid. I didn't realize that I had to upgrade from 2.3 to 2.3.1 and then to 2.3.2. I did that an everything upgrade without any problems. Now just got to figure out how to install apk's and I'm golden
Edit 2: Ok, I figured everything out and now i'm up to date with updates and I can install apps and games. Oh Happy Day Thx for all the help
http://org.downloadcenter.samsung.c...113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe
22.8MB file installing slowly?
First off, I apologize for being paranoid. I downloaded this file and started installing it. It's a 22.8 MB .exe file. I started installing, and it *seems* to be working correctly. After clicking install MSS Installation Wizard is installing Samsung USB Driver for Mobile Phones V1.3.2200.0. Slightly after, desktop toolbar icon popped up Installing device driver software, opened it up showing:
USB Composite Device Ready to use
USB Mass Storage Ready to use
CDC Cerial Waiting for user input
Samsung LTE USB Device Ready to use
Samsung LTE Card USB Device Ready to use
It's been like 10-15 minutes and the MSS Installation Wizard is chugging along, at about 50%. Is this file legit? Is it just my slow ass computer that is making this install take forever? Have other successfully installed this for ADB usage?
Looks to just be the link to Samsung, which yes I have installed. It was a bit slow on my netbook.
Sent from my SGH-T769 using Tapatalk 2
Same here. I installed it yesterday while working on my wife's phone (Blaze also). The first time I tried to install it on my desktop it was slow and there was some sort of error. I had to reboot and redo it before I got it properly installed.
I've never needed the drivers, just downloaded kies.
Sent from my SGH-T769 using XDA
Kies I think installs the drivers for you. You can't properly use the device without the drivers and you definitely cannot use some of the tools without them.
No ADB
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Does anyone know how to get this device working with adb on Debian? I can't for the life of me get the device recognized by adb. I have a 51-android.rules set up and all that jazz. udev sees it and rules are applied properly. I just can't get it recognized. It seems references to accessing this device from Linux are very few and far between. What gives?
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
strungoutfan78 said:
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
Click to expand...
Click to collapse
Can you explain this a bit more, like where to input these commands. Im a bit green and having this issue.
---------- Post added at 01:25 AM ---------- Previous post was at 01:04 AM ----------
theshowman said:
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Click to expand...
Click to collapse
I tried the #7284# and #9090# and got "unable to process request"
any other suggestions?
Hi Guys,
I had a rooted 4.4.2 device, when I got the the 4.4.3 upgrade and I think that from then I cannot see my device on my laptop.
(I am not sure of that because I CAN see it on my work desktop...)
Anyway, whatever I do - I get the following results:
1. Device manager shows me under the "Portable Devices" the brance F:\
2. When I try to install new ADB drivers, it tells me that "WPD fileSystem volume driver" is the best for me...
Storage usb connection setting is set to be MTP.
Meanwhile, I cannot see my nexus 5 files on my laptop
Please assist, Thanks!!!
dushkin said:
Hi Guys,
I had a rooted 4.4.2 device, when I got the the 4.4.3 upgrade and I think that from then I cannot see my device on my laptop.
(I am not sure of that because I CAN see it on my work desktop...)
Anyway, whatever I do - I get the following results:
1. Device manager shows me under the "Portable Devices" the brance F:\
2. When I try to install new ADB drivers, it tells me that "WPD fileSystem volume driver" is the best for me...
Storage usb connection setting is set to be MTP.
Meanwhile, I cannot see my nexus 5 files on my laptop
Please assist, Thanks!!!
Click to expand...
Click to collapse
Delete the device in device manager and then let it find it again.
Sent from my Nexus 5 using XDA Free mobile app
Thanks
If you mean to uninstall it, then I did it couple of times, and now again when the device was disconnected. Then I reconnected the device to the USB port, and scanned the deice manager for changes.
I got the same result - see attachement.
Delete then reboot both devices. Connect phone again. If same, delete device and reboot phone whilst still connected
If that fails, delete and use "universal naked driver"
Sent from my Nexus 5 using Tapatalk
dushkin said:
If you mean to uninstall it, then I did it couple of times, and now again when the device was disconnected. Then I reconnected the device to the USB port, and scanned the deice manager for changes.
I got the same result - see attachement.
Click to expand...
Click to collapse
Never seen that before. Your drivers obviously aren't set up right. Google 15 second adb drivers xda and use that to install the drivers. It'll also set up adb/fastboot which you may or may not need. It gives you the option
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Never seen that before. Your drivers obviously aren't set up right. Google 15 second adb drivers xda and use that to install the drivers. It'll also set up adb/fastboot which you may or may not need. It gives you the option
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No need google.. Section 1b of the resources thread in my signature
Sent from my Nexus 5 using Tapatalk
Are you trying to use ADB mode? If so, and it's not recognizing the device, try using ADB Driver Installer. It worked for me.
dushkin said:
Hi Guys,
I had a rooted 4.4.2 device, when I got the the 4.4.3 upgrade and I think that from then I cannot see my device on my laptop.
(I am not sure of that because I CAN see it on my work desktop...)
Anyway, whatever I do - I get the following results:
1. Device manager shows me under the "Portable Devices" the brance F:\
2. When I try to install new ADB drivers, it tells me that "WPD fileSystem volume driver" is the best for me...
Storage usb connection setting is set to be MTP.
Meanwhile, I cannot see my nexus 5 files on my laptop
Please assist, Thanks!!!
Click to expand...
Click to collapse
I had a similar issue. In order to get my Windows 7 laptop to recognize my N5, I first turned off USB Degugging then connected my N5 to the laptop. Then it showed up.
Sent from my SPH-L720
optimummind said:
I had a similar issue. In order to get my Windows 7 laptop to recognize my N5, I first turned off USB Degugging then connected my N5 to the laptop. Then it showed up.
Sent from my SPH-L720
Click to expand...
Click to collapse
It's supposed to work fine even with it on, at least it did when I had it on. Tested on Win 7, 8, 8.1 and 8.1U1 lol. I never had any issues with USB ever.
Or use Linux, it'll work right away..
It's not set to Camera (PTP) instead of Media Device (MTP) ?
Case Status
Guys.
Thank you all for your kind help.
I tried at least most of your advises - but there were no joy...
I think that the best I should do now is somehow clean up my system from old drivers and related installations.
So, taking aside the option of reinstalling windows, can you share with me some procedures that will enable me to get rid of all old drivers and files and to reach a state of a clean system, so I can then start reinstalling the drivers again?
Thanks a lot!
Well... here is the solution!!!!
https://www.topnotchtablets.com/FixUSBproblems
dushkin said:
Guys.
Thank you all for your kind help.
I tried at least most of your advises - but there were no joy...
I think that the best I should do now is somehow clean up my system from old drivers and related installations.
So, taking aside the option of reinstalling windows, can you share with me some procedures that will enable me to get rid of all old drivers and files and to reach a state of a clean system, so I can then start reinstalling the drivers again?
Thanks a lot!
Click to expand...
Click to collapse
I have similar problems, and as many times as ive tried to uninstall and reinstall i cannot access it from my 1 laptop. However, another laptop connects fine to it- even though i used the same drivers on both laptops. thats the only way i was able to get it to work for me.
dushkin said:
Hi Guys,
I had a rooted 4.4.2 device, when I got the the 4.4.3 upgrade and I think that from then I cannot see my device on my laptop.
(I am not sure of that because I CAN see it on my work desktop...)
Anyway, whatever I do - I get the following results:
1. Device manager shows me under the "Portable Devices" the brance F:\
2. When I try to install new ADB drivers, it tells me that "WPD fileSystem volume driver" is the best for me...
Storage usb connection setting is set to be MTP.
Meanwhile, I cannot see my nexus 5 files on my laptop
Please assist, Thanks!!!
Click to expand...
Click to collapse
Hi,
I just bought a Nexus 5 and I'm having unbearable trouble getting it connected with my PC. I have spent the last 3 or 4 hours on Google and xda forums searching for a solution but nothing has worked so far.
My situation is as follows:
I'm using a laptop running Windows 8.1, I have tried both the original USB cable that came in the package as well as an older one and all the ports on my laptop.
I checked device manager and saw that it was connecting with ACER adb interface drivers. Some people had had the same problem, so I uninstalled the drivers. After that I installed Universal Naked Driver 0.73 (disabled checking for signatures first), my PC could not identify the Google package as a driver. Nexus still didn't show up in explorer although device manager now showed that it was connecting with the proper driver.
I downloaded the Nexus Root Toolkit and did the step-by-step driver setup. Toolkit itself connected perfectly well with my phone and stated that the drivers were successfully installed but my phone still doesn't show up anywhere in explorer.
I've really run out of ideas and cannot find anything online that's related to my problem that I haven't already tried. If anyone could help me, I'd really greatly appreciate it
Thanks,
Alselius
Alselius said:
Hi,
I just bought a Nexus 5 and I'm having unbearable trouble getting it connected with my PC. I have spent the last 3 or 4 hours on Google and xda forums searching for a solution but nothing has worked so far.
My situation is as follows:
I'm using a laptop running Windows 8.1, I have tried both the original USB cable that came in the package as well as an older one and all the ports on my laptop.
I checked device manager and saw that it was connecting with ACER adb interface drivers. Some people had had the same problem, so I uninstalled the drivers. After that I installed Universal Naked Driver 0.73 (disabled checking for signatures first), my PC could not identify the Google package as a driver. Nexus still didn't show up in explorer although device manager now showed that it was connecting with the proper driver.
I downloaded the Nexus Root Toolkit and did the step-by-step driver setup. Toolkit itself connected perfectly well with my phone and stated that the drivers were successfully installed but my phone still doesn't show up anywhere in explorer.
I've really run out of ideas and cannot find anything online that's related to my problem that I haven't already tried. If anyone could help me, I'd really greatly appreciate it
Thanks,
Alselius
Click to expand...
Click to collapse
Have you tried screwing with MTP and (the other) mode? Also is USB debugging on?
tevil said:
Have you tried screwing with MTP and (the other) mode? Also is USB debugging on?
Click to expand...
Click to collapse
Yeah, tried all the possible combinations, MTP, PTP, debug on and off. Responded the same, showed up in device manager and made the connected device sound effect but no folder.