Related
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
bump. i also need this. btw have you tried using a script to do it?
danboard said:
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
Click to expand...
Click to collapse
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=698059
and especially did you install this driver?
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
I do have read the thread and I have installed that driver. While in recovery mode using GOT's or OpenRecovery I notice that under device manager it says my phone is listed as "Android Phone" and if my phone is on and I connect it to my computer with USB debugging it lists it as "ADB interface". I can't get the phone to appear under adb devices while in recovery mode.
USB-Debugging active? (Settings-->Development)
It is when the phone is on, but what I am trying to do is push a file to the phone while its "off" in recovery mode so the usb debugging is irrelevant or so i believe.
Yes, sorry, you are right.
As I can remember, I have had a similar problem a year ago...
Try to copy adb into another directory and use it from there. Sounds stupid, but helped me in the past.
Sent from my Milestone using XDA App
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
danboard said:
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
Click to expand...
Click to collapse
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
micdim said:
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
Click to expand...
Click to collapse
Seems OK now. I just reinstalled official SDK.
dl.google.com/android/installer_r08-windows.exe
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
1st post here.
Seems like basic problem but I cannot get adb connected to my G1.
I started off on process of upgrading to CM 6.1 but when I was about to put recovery image on phone I discovered flash_image program was not found. Then set off on the adb route but am now stuck. Tried searching but not found answer. Here is what I have done/tried so far:-
PC is XP Pro SP3
G1 V1.6 rooted via Universal method (su works ok via Term)
Downloaded and installed latest SDK in c:\Android-sdk
USB debugging is enabled on phone
SD card is not mounted
When I run "adb devices" (from C:\android-sdk\platform-tools) it fails with
msg "error: protocol fault (no status)"
The basic usb connection to PC is known to be working ok (have copied files to phone sd card etc. no problem if I mount it)
The installation of usb drivers seemed to go ok although I had to do it manually from folder \android-sdk\google-usb_driver
When I look at usb devices with USBDeview there are 3 related to Android phone (all enabled).
1. HTC Android phone usb device (connected)
2. USB Mass storage device (not connected)
3. Android composite ADB interface (not connected)
Further info...
I see other people have had the same problem (with other phones as well) but cannot find any specific reason or fix that works.
I have reinstalled latest sdk rev08
Unintsalled and reinstalled latest google usb drivers (ver 4) endless times
Usb driver install appears to all go ok
In XP Device Manager I get Android Phone device which expanded shows single Android Composite Interface Device which has staus enabled and working ok
I have no "Other" usb devices etc. showing up in Device Manager
USBDeview shows 3 usb devices for Android phone. The connected one shows the htc serial no. The ADB composite interface is not connected and has no serial number.
I have tried different usb ports, cables, and another standard G1 phone - all gives same results
I noticed the adb_usb.ini file had no device id in it, I ran "update adb" as per comment note at top of adb_usb.ini but still got not entries in file.
Someone surely must have solution to this. I cannot believe a G1 phone does not work/been tested with sdk adb.
Maybe some source code guru can tell me under what conditions adb gives the "protocol error: no status" msg.
Or could someone with a working G1 adb usb connection post their adb_usb.ini etc.
Have spent 2 days on and off fiddling with this sdk now. :-(
Thanks
Shame you didn't spend some of that two days reading the site rules and the fact that not only is there Q&A section but also try posting in the ADB threads that are littered around these forums.
Catch me on irc, link in sig and I'll see what can be done.
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
dalek1999 said:
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
Click to expand...
Click to collapse
he offered help via irc, so you should think about accepting it.
anyway he ment that this has (almost) NOTHING to do with development and should have been posted in Q&A.
concerning your problem: i have no idea try if you can connect to fastboot.
dalek1999 said:
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
Click to expand...
Click to collapse
So what does helping you get adb setup help android G1 Developmet?
Sent from my HTC Dream using XDA App
lolmensch said:
he offered help via irc, so you should think about accepting it.
anyway he ment that this has (almost) NOTHING to do with development and should have been posted in Q&A.
concerning your problem: i have no idea try if you can connect to fastboot.
Click to expand...
Click to collapse
fastboot uses fastboot.exe, not adb.exe. Adb works while in recovery or while booted.
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,
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?