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
Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!
Linch89 said:
Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!
Click to expand...
Click to collapse
Ace Hack Kit
That will walk you through the root/s-off/unlock process. It's been VERY much simplified over time, now it's just a 1 step process. Read the effen manual a few times before you start - but like I said, at this point it's very straight-forward.
Once installed hit up the MIUI thread. Basically you'll download the ROM to your SD, boot to recovery, perform a wipe, and flash the ROM
And thank you for your service and dedication to this wonderful country of ours!
He said the adb drivers won't connect
Any specific error messages? At what point is this happening? Is he trying to run the hack kit or just trying to access an ADB shell?
The hack kit contains all necessary adb files/drivers
Make sure he's done all of this:
Make sure HTC USB Drivers for Android are installed (included in the Hack Kit @ tools/windrivers)
Disable all malware detection, including Windows Defender
Uninstall HTC Sync
Uninstall Droid Explorer
Uninstall iTunes or stop service
Uninstall Other phone pda or tablet software
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
trouble rooting my phone
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol
did u ever find out y adb wont connect im having d same problem
Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Did you install the drivers that came with the kit just to be safe?? I just did this like 2 days ago and it worked perfect..
Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Has he by any chance tried a different USB port? And is the phone in charge only mode, it's not mounting itself as a disk drive automatically? I don't know how feasible it might be, but if he has another computer available try running it there and see if you get any different results. At least then we might be able to narrow down better whether it's the software, the computer, or the phone.
jonathanj942 said:
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol
Click to expand...
Click to collapse
Another simple thing that I have to ask about...you guys did extract all the contents of the hack kit somewhere on your computer, correct? You're not trying to run it from the .zip?
If it is extracted,
go to the tools\win\ directory.
Hold Shift and Right-Click in an empty spot, select "open command window here"
type "adb devices" and hit Enter
You should see 12 alpha-numerics listed under "List of devices attached"
If you don't see anything under this, then for some reason adb isn't recognizing your phone is plugged in. In which case I'd try a different USB port or computer
Hi All,
I was trying to enable the ADB with PAC ROM when my evita is switched on as we do on sense roms.
But my Windows 7 PC is unable to detect the phone as android and It was searching for drivers online and at last failing to find the drivers.
I have HTC Android drivers installed on my PC and android debugging enabled on my evita.
Is this is the known behaviour of KK 4.4.2 AOSP ROM's ??
Not that I know of, I've had no problems using adb on any of the KitKat ROMs I've tried. How have you installed the drivers?
Sent from my Evita
Scozzar said:
I've had this issue quite a lot as well. ADB won't ever work when booted into the ROM, but if you boot into fastboot, no problems at all. What happens is that it searched for drivers, then can't find them.
Click to expand...
Click to collapse
Are you talking about adb commands working in fastboot? Or fastboot commands working in fastboot?
Sent from my Evita
Ok. It can be a huge hassle, I had the opposite problem. My adb was working beautifully on my new laptop but I couldn't get fastboot working with official HTC drivers. Ended up using the drivers from pdanet to get it to work, but they ended up not being compatible with RUUs. So tried with the official HTC drivers again, plugged in my fiance's Evita instead of mine, and bam! Perfect driver setup. Go figure. The amount of times I've helped people on XDA get their drivers working and it took me like three friggin days.
Sent from my Evita
No, only one set of drivers. When the official HTC drivers didn't work with fastboot I uninstalled them and used the pdanet drivers. When the pdanet drivers didn't work with the RUU I uninstalled them and installed the HTC drivers again.
Sent from my Evita
timmaaa said:
No, only one set of drivers. When the official HTC drivers didn't work with fastboot I uninstalled them and used the pdanet drivers. When the pdanet drivers didn't work with the RUU I uninstalled them and installed the HTC drivers again.
Sent from my Evita
Click to expand...
Click to collapse
PDANet drivers worked for me as well. But my device is showing as Offline, what could be the reason for this?
sathish804 said:
PDANet drivers worked for me as well. But my device is showing as Offline, what could be the reason for this?
Click to expand...
Click to collapse
You need to have your screen on and accept the prompt that pops up.
Sent from my Evita
I have experience similar problem after flash to KK4.2.2: adb never connect and no authorization confirmation pop up will show. I found that in my device manager there is a device called "One X" without driver. I get all my htc driver from http://forum.xda-developers.com/showthread.php?t=2217396 never installed htc sync. I searched around, everyone was talking about disable and re-enablle adb debug and "allow" its access from the popup and no one was having the "no driver" problem. I solved this problem by editing one inf file in the installed driver.
SOLUTION
If you have installed the driver from the link above, under:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64
there will be a file named androidusb.inf. Depending on your windows installation path and bitness, this path may be slightly different. Edit it with notepad, find a line
%MyHTC%=HTCAND64.Dev, USB\VID_0BB4&PID_0FF2&MI_01
insert the following line just below that line
%MyHTC%=HTCAND64.Dev, USB\VID_0BB4&PID_0FF9&MI_01
save the file and use "update driver" in device manager to install driver. manually select the search directory and windows should find the driver. After the driver is installed, adb works like a charm.
sippey said:
I have experience similar problem after flash to KK4.2.2: adb never connect and no authorization confirmation pop up will show. I found that in my device manager there is a device called "One X" without driver. I get all my htc driver from http://forum.xda-developers.com/showthread.php?t=2217396 never installed htc sync. I searched around, everyone was talking about disable and re-enablle adb debug and "allow" its access from the popup and no one was having the "no driver" problem. I solved this problem by editing one inf file in the installed driver.
SOLUTION
If you have installed the driver from the link above, under:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64
there will be a file named androidusb.inf. Depending on your windows installation path and bitness, this path may be slightly different. Edit it with notepad, find a line
%MyHTC%=HTCAND64.Dev, USB\VID_0BB4&PID_0FF2&MI_01
insert the following line just below that line
%MyHTC%=HTCAND64.Dev, USB\VID_0BB4&PID_0FF9&MI_01
save the file and use "update driver" in device manager to install driver. manually select the search directory and windows should find the driver. After the driver is installed, adb works like a charm.
Click to expand...
Click to collapse
Thank You.. This is worked for me!!
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
iainwith2is said:
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
Click to expand...
Click to collapse
Install the adb/fastboot drivers. Google is your friend
Firstly thank you for your reply.
I have tried your install but it hasn't worked. I can tell I have been following a smilar update route looking at the pictures you uploaded also, although these screen snaps were obviously from a new OS (windows 7 perhaps).
Whats interesting to note however, is that in my device manager the phone is clearly shown twice, at the top as "Android Device", with "Google Nexus ADB Interface" below it and then again further down as "Other Devices" with MTP below with the familiar yellow exclamation mark.
Significant?
You actually don't need debugging mode if you're intending to manually flash the ROM. Debugging mode is only an android setting and you flash the ROM using fastboot which is outside of android.
Also you don't need the SDK.
I would say go to general > sticky roll-up then read my adb and fastboot thread to start
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
If you used the adb and fastboot installer in my thread, did you use the "install system wide" option?
If not, do.
If you did and it did not work, read more of that section as the manual steps are also mentioned, which you'll need to follow.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
He should already have it from my thread. Its just a question whether he used it correctly or whether it doesn't set up the environment variables on xp properly
Yes installed the 15 second install, Y,Y,N, then installed the Clockmod driver.
I'll go back and read it again, guess I must've missed something.
Have you rebooted? Try that. Is still no, you'll need to manually populate the environment variables.
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
iainwith2is said:
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
Click to expand...
Click to collapse
Don't copy and paste it. The text is generic. You must put your text there....then reboot.
this is what I pasted:
;c:\adb_fastboot
?
iainwith2is said:
this is what I pasted:
;c:\adb_fastboot
?
Click to expand...
Click to collapse
Which is generic. Is the folder your adb and fastboot executables are in called c:\adb_fastboot? If you used the installer, it is not.
Where would the installer put them? I've searched my computer for "fastboot" and its found the exe that I put in a folder on my desktop. This looks a similar address to what I changed the path to previously...
Oy vey
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Oy vey
Pardon?
Click to expand...
Click to collapse
OK so my path is broken so I won't be able to run adb commands?
Did you look at the root of c:? C:\adb perhaps? Its all covered in my thread isn't it? Are you reading it or skimming it? You don't even *need* to put it in the path. Its just easier. Please read to the end of the thread
Also, you don't need to run any adb commands
Yes I've scanned c: drive.
I've read and understood what I can, I'm not an expert so I can only compute what I understand.
I have reinstalled the adb setup a few times and I have noticed that it clearly says "0 files copied" after I select the exe files and system wide options.
I have also tried to run the adb and fastboot devices commands in the command window which gives me the aforementioned error messages.
For some reason, these programs are not being installed onto my machine?
For years, I struggled to get ADB/FASTBOOT installed and working. I've succeeded fairly often but usually have a success/failure ratio of one hundred to one. I'm currently trying it again, so thought I'd make a request for info from someone more experienced than myself.
First of course, is USB Debugging enabled. Done.
Then install OEM USB drivers; in my case Samsung.
Finally install the "short" version of Android SDK Development tools (just adb and fastboot but nothing else).
Am I missing something? I usually have to keep "hacking and whacking" at the damn thing until I finally stumble upon the correct combination of components.
And of course different cables, different computers, different Windows versions, etc, etc, etc ad nauseum.
I even reinstalled Windows 7 for a "fresh" PC and EVEN that did not help.
SO.......... Anyone have any ideas what works "first time, every time". I'm desperate.
Boowho??
boowho said:
For years, I struggled to get ADB/FASTBOOT installed and working. I've succeeded fairly often but usually have a success/failure ratio of one hundred to one. I'm currently trying it again, so thought I'd make a request for info from someone more experienced than myself.
First of course, is USB Debugging enabled. Done.
Then install OEM USB drivers; in my case Samsung.
Finally install the "short" version of Android SDK Development tools (just adb and fastboot but nothing else).
Am I missing something? I usually have to keep "hacking and whacking" at the damn thing until I finally stumble upon the correct combination of components.
And of course different cables, different computers, different Windows versions, etc, etc, etc ad nauseum.
I even reinstalled Windows 7 for a "fresh" PC and EVEN that did not help.
SO.......... Anyone have any ideas what works "first time, every time". I'm desperate.
Boowho??
Click to expand...
Click to collapse
What are you trying to do with ADB
([emoji3590]09-09-18[emoji3590])
boowho said:
For years, I struggled to get ADB/FASTBOOT installed and working. I've succeeded fairly often but usually have a success/failure ratio of one hundred to one. I'm currently trying it again, so thought I'd make a request for info from someone more experienced than myself.
First of course, is USB Debugging enabled. Done.
Then install OEM USB drivers; in my case Samsung.
Finally install the "short" version of Android SDK Development tools (just adb and fastboot but nothing else).
Am I missing something? I usually have to keep "hacking and whacking" at the damn thing until I finally stumble upon the correct combination of components.
And of course different cables, different computers, different Windows versions, etc, etc, etc ad nauseum.
I even reinstalled Windows 7 for a "fresh" PC and EVEN that did not help.
SO.......... Anyone have any ideas what works "first time, every time". I'm desperate.
Boowho??
Click to expand...
Click to collapse
As long as you have the complete USB drivers for your device, USB debugging enabled and the adb 15 second installer installed on PC, it should work. When you connect your device to adb, you "should" get a prompt or notification on your device to allow adb access, if you do, grant it permission.
If you're trying to use fastboot on a Samsung device, you can give up on that notion, Samsung devices can't use fastboot for anything, it isn't compatible at all, you will never get it to work.
But...
ADB works just fine on Samsung.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
As long as you have the complete USB drivers for your device, USB debugging enabled and the adb 15 second installer installed on PC, it should work. When you connect your device to adb, you "should" get a prompt or notification on your device to allow adb access, if you do, grant it permission.
If you're trying to use fastboot on a Samsung device, you can give up on that notion, Samsung devices can't use fastboot for anything, it isn't compatible at all, you will never get it to work.
But...
ADB works just fine on Samsung.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks so much for your thoughts/reply. I found last night that stripping ALL previously installed USB drivers and re-installing the Samsung USB drivers got it working. I plugged the device in BEFORE installing Sammy's drivers and it showed in device manager (without a driver, of course). I then installed the drivers and it connected. At that point ODIN worked just fine. Then I did an "adb devices" and it responded as it should.
For me, all these "packages" (Like 15 second installer or something) with .bat files, etc are not needed at all for ADB and just make things more confusing.
Just the two executables and three .DLL files make ADB and fastboot work in windows; IF you have previously installed Sammy's drivers as mentioned above.
Finally, not to disagree with you (after all it was ME who came here looking for help), but FASTBOOT works just fine on my Samsung device (a Gear Live Watch). I have to use the command "adb reboot bootloader". The watch reboots and from there all fastboot commands seem to work just fine. I flashed several .img files that way.
It's possible (I suppose) that no other Sammy device will accept fastboot, because supposedly Sammy wasn't even involved in creating the firmware for that watch. Google did it ALL.
Oh, and one last thing..... Yes I HAD it all working, but now ADB devices shows the device as "unauthorized". It did not when I first did the ADB devices, but instead put up the popup asking for permission. Now it just says unauthorized and fails to popup the little message
I've gone thru all the "fixes" for this that I can find for this particular problem, but so far no joy.
Maybe it's just me, but setting up ADB/fastoot as ALWAYS been a pain is the ass.
Boowho??
boowho said:
Thanks so much for your thoughts/reply. I found last night that stripping ALL previously installed USB drivers and re-installing the Samsung USB drivers got it working. I plugged the device in BEFORE installing Sammy's drivers and it showed in device manager (without a driver, of course). I then installed the drivers and it connected. At that point ODIN worked just fine. Then I did an "adb devices" and it responded as it should.
For me, all these "packages" (Like 15 second installer or something) with .bat files, etc are not needed at all for ADB and just make things more confusing.
Just the two executables and three .DLL files make ADB and fastboot work in windows; IF you have previously installed Sammy's drivers as mentioned above.
Finally, not to disagree with you (after all it was ME who came here looking for help), but FASTBOOT works just fine on my Samsung device (a Gear Live Watch). I have to use the command "adb reboot bootloader". The watch reboots and from there all fastboot commands seem to work just fine. I flashed several .img files that way.
It's possible (I suppose) that no other Sammy device will accept fastboot, because supposedly Sammy wasn't even involved in creating the firmware for that watch. Google did it ALL.
Oh, and one last thing..... Yes I HAD it all working, but now ADB devices shows the device as "unauthorized". It did not when I first did the ADB devices, but instead put up the popup asking for permission. Now it just says unauthorized and fails to popup the little message
I've gone thru all the "fixes" for this that I can find for this particular problem, but so far no joy.
Maybe it's just me, but setting up ADB/fastoot as ALWAYS been a pain is the ass.
Boowho??
Click to expand...
Click to collapse
Samsung gear doesn't count, as you said, Samsung doesn't have anything to do with creating the firmware. I would think that any android device that Samsung had it's part in making firmware for, doesn't work with fastboot. But, devices that are Samsung "in name" only, may be compatible with fastboot. The question is, is it really a Samsung or is it just wearing the Samsung name?
Sent from my SM-S767VL using Tapatalk