I missed out something i think.
I have my sdk, with those files.
I went to cmd and type the commant
bla bla bla
fastboot devices >>> no error, means connected
fastboot oem unlock
>>>> it is connected but why it still waiting for my device?
I added the path to the system too, but still cant get rid of
I search the net and I cant get the solution.
Any idea anyone?
What drivers did you install? And yes, I read the "fastboot devices"
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Phone has to be in bootloader mode?
Sent from my Nexus S using XDA App
yup.. it is in volume up + on mode.
If you plug your NS in and look in the Device Manager, do you see an unknown device with the question mark? If so, you should try to manually install the driver located in android-sdk-windows\extras\google\usb_driver
And when you issue the command
Code:
fastboot devices
It should display your NS device id, not just a blank line.
melvinchng said:
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Click to expand...
Click to collapse
"samsung" driver... no
you use the drivers obtained from the Android SDK or PDAnet
Pretty much what suksit said.
Try pdanet! Last place i go y find drivers
Sent from my Nexus S using XDA Premium App
I tried sdk driver, pdanet driver. I can't unknown driver, it is listed as android. Means my phone is found by computer
I have android 2. 3. 4. Does it effect?
Sent from my Nexus S using XDA Premium App
Just curious, did you enabled the option in Settings > Applications > Development > USB debugging?
In Device Manger it should say something like "Android Composite ADB Interface"
I enabled it too... maybe I will try to reinstall and root it via my XP in VM.
I rooted my wildfire with this pc last time, maybe the drive mixed up.
Sent from my Nexus S using XDA Premium App
Just noticed that your location is in Malaysia. Could it happen that you have the i9023 (SLCD) model? If that's the case then I think you should try this.
Ya, I bought slcd set.
I will try it tomorrow at night and report back to you guys.
--------------------------------
It is really strange. Tried everything and won't work.
Pdanet detected my device that it is connected to computer, but it just show wait for device.
----------------------------------------
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
melvinchng said:
Ya, I bought slcd set.
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yeah thats normal, Samsung did some weird battery calibration thing!
However people here have found to get 100% or close to it.
When charging just leave screen on for 1 hour and have tethered wifi On, so far im charging full up to 98%, just waiting to squeeze in the last 2%.....could take awhile.
and yeah the 95% charge is normal. heres a explanation in further detail
Your battery gauge is lying to you (and it's not such a bad thing)
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
j0l6 said:
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
Click to expand...
Click to collapse
i have these in tools. and still waiting for device.
anyone any idea?
I forgot to tell you guys that my windows is 64-bit
Sent from my Nexus S using XDA Premium App
Try this or this then (the latter is quite hard to read anyway, I think they messed up the code formatting)
Unlocked bootloader!
thanks!
Sent from my Nexus S using XDA Premium App
melvinchng said:
I haven't root yet.
After I root, my storage and Rom will be wipe? So I need to install new Rom?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Rooting will add su binary and Superuser app to your NS. But your data will be wiped (both on phone and SD card) when you unlock the bootloader -- it's the same as doing a factory reset. However, your system partition will not be affected so no need to install new ROM if you prefer using stock.
Related
I was trying to root my Nexus S
I got to bootloader, flashed rootboot.img and clockwork. Now I'm stuck on the unlocked google reboot.
When I try mounting the sdcard via usb in clockwork I can't get it to show on my comp, so I can't drop the zip files in there to update the phone. I believe that's the last step I need to get my baby working again.
If this is the case do you have any suggestions on how I can get files in there? I thought there might be a fastboot command to move the files there but I can't seem to figure it out.
If not can you please point me in the right direction
I tried searching the forums for a solution but everything I come across does not seem to help my particular needs, I apologize if I missed the solution elsewhere but I'm at wit's end right now
All suggestions are greatly appreciated
Thanks!
I am almost having the same issue. I unlocked the bootloader and flashed recoverymod but was unable to locate the superuser zip file so I rebooted my nexus. When I tried to start over again and fastboot I'm getting an error with CMD saying its waiting for device. On the nexus when in fastboot mode at the very bottom it says fastboot failsomething or another.
Any suggestions as to how I can get fast boot working again?!
Sent from my Nexus S 4G using XDA Premium App
I'm obviously no pro! but from what I gather it sounds like your phone's not being recognized. I had that problem and this guide seemed to solve it so you might find it of some help
nexusshacks.com/nexus-s-hacks/how-to-install-nexus-s-windows-usb-drivers
Thanks, it can't be a driver issue though since I was able to use fastboot to unlock the bootloader. Although it sure does seem like its not connecting properly.
Sent from my Nexus S 4G using XDA Premium App
blahhhh you jinxed me. I just realized how to use ADP, figured it was the way to push the files I needed to SD card and now I'm getting your error. I'll reply with a solution if I find one, hope you do the same! two noobs are better than one after all!!
Yikes! Please do, it's driving me insane!
Sent from my Nexus S 4G using XDA Premium App
Fixed it, a simple battery pull fixed my problem. Rooted it this morning!
Sent from my Nexus S 4G using XDA Premium App
Think you can tell me what driver you're using? When I plug my phone in I see the following in the device manager
ADB Interface
SAMSUNG Android Composite ADB Interface
I tried your battery trick to no avail, I even had ADB running and tried the battery trick and it won't work
Also, fastboot is recognizing my device.
Any help would really be appreicated. it's day 3 with no phone now
I'm at work now till 9 and I'm in CA. Ill look it up when I get home. U have to DL the Google something or another driver in sdk. I remember 4 was at the end of it. Ill post when I get home.
Your phones not working at all?!
Sent from my Nexus S 4G using XDA Premium App
vintagetonez said:
I am almost having the same issue. I unlocked the bootloader and flashed recoverymod but was unable to locate the superuser zip file so I rebooted my nexus. When I tried to start over again and fastboot I'm getting an error with CMD saying its waiting for device. On the nexus when in fastboot mode at the very bottom it says fastboot failsomething or another.
Any suggestions as to how I can get fast boot working again?!
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
hi there
i'm trying to root my xperia x8 using superoneclick, ADB start OK.... waiting.... and i'm waiting more than 5 min i think.... but nothing happen...
-i've extracted/copied xrecovery into sd, phone browser but nothing happen.
- boot the phone and press "back <--" key multiple time.... but phone start as usual ...
can somebody teach me how or give link to show how to root step by step please...
i'm new here..... TT
-- sorry for english.... not my language..
yeah I just switched to the google android service 4 "something or other" not in the mindset to find it. My phone's working it's just in super retardo mode right now. All that's working is the bootloader screen and the clockwork orange screen. I've kind of abandoned all hopes of getting adb to work on it because I've tried EVERTHING (except for what will work). I'm trying to figure out how to get clockwork to work with my pc that way I can get files into the sdcard which is what I was trying to use adb for in the first place.
ps... can you send a pic of your homescreen? I miss mine
U don't need adb to transfer files to your nexus s. Make sure debugging is turned on and mount your SD. You should get a promt to transfer files to and from your device via comp. You can use cmd to transfer with fastboot. I just got home and haven't even downloaded anything for root other than free tethering so I'm not sure which app will allow screen shot capture.
Sent from my Nexus S 4G using XDA Premium App
I'm relatively sure debug is still on otherwise I would not have been able to do what I already did. what's the command to transfer files to sd via fastboot? I tried "push" but that did not seem to work.
Once you plug the phone in.and mount SD.windows will automatically recognize it and prompt what woulf you like to do. Just choose transfer files. Go to the file you want yo transfer and right click. Choose send to E. At least on my comp the nexus shows up as e drive so choose which one it shows up as.
Sent from my Nexus S 4G using XDA Premium App
Thanks for all your help, I really appreciate it. It seems the phone's not being recognized by the computer when I mount it. The drivers show up in device manager when I boot to bootloader but then disappear when I go into clockwork. So I never get a chance to see it in "computer" when I try mounting the sdcard. Any thoughts?
Im using the revolutionary method i get my beta key.
when i run the program it type in my beta key, and it accepts it and the comes up with ''zerging root. . . this might take a minute or so. . .'' but nothing happens and it stays like this. is it supposed to boot into bootloader or something? i have usb debugging enabled. and im on htc sync mode.
Did you install USB driver on rev site? Happenned to me when I try rooting it.
Sent from my HTC Sensation 4G using XDA Premium App
Shouldn't be in Sync mode, just connect it in charging mode
Ive tried what both of you have suggested but its still the same? is usb debugging supposed to be on or off?
USB Debugging = ON
Seriously, read the guide - http://forum.xda-developers.com/showthread.php?t=1192300
EddyOS said:
USB Debugging = ON
Seriously, read the guide - http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
Thats the guide im following and its not working. My galaxy s2 was a piece of cake to install a custom rom on
it works perfectly up to the point when i type in the beta key? which i know im doing it correctly.
it just hangs there? also when i boot into fastboot it has ***LOCKED*** at the top in pink, so does this mean i need to unlock my bootloader first?
No, it gets replaced with 'Revolutionary' once done.
Try a different USB port/PC
Just calm down and take a break, then re read the instruction. You must miss something
Sent from my HTC Sensation 4G using XDA Premium App
still no luck, and i have no idea why accept this sort of thing always happens to me ive managed to root a desire z in the past so this shouldnt be a problem on my laptop because it worked fine before?
This what comes up
We know what's coming up, that's normal. Have you tried a different USB port/PC at all?
I take it you're using Windows 7. If so, run your DOS prompt as an Administrator
dav08094194 said:
This what comes up
Click to expand...
Click to collapse
Your phone gonna reboot into HBoot a few time to get root. Are you seeing your phone reboots?
Sent from my HTC Sensation 4G using XDA Premium App
EddyOS said:
We know what's coming up, that's normal. Have you tried a different USB port/PC at all?
I take it you're using Windows 7. If so, run your DOS prompt as an Administrator
Click to expand...
Click to collapse
Yeah windows 7 and ive tried all 3 usb ports. not sure what DOS Prompt is but im running the program as administrator anyway.
Then I suggest trying a different PC. Although, have you always tried it as Admin? Funnily enough it worked for me once I STOPPED using Administrator rights
EddyOS said:
Then I suggest trying a different PC. Although, have you always tried it as Admin? Funnily enough it worked for me once I STOPPED using Administrator rights
Click to expand...
Click to collapse
got it to work in the end. i had to install windows 7 on my linux ubuntu pc
Hi there,
I was trying to change the splashscreen with use of adb, when i tried to reboot into bootloader the error devices not found poped up, i thought well no worries ill do it myself then. When in fastboot usb mode it still doesn't find it. things u tried:
usb mode by recovery
usb mode by fastboot
normal usb at homescreen
charging mode
htc sync mode
i did check usb debugging and it was checked
i run OrDriod 2.0.1(2.0.2 in a couple of min) FW 3.32 bricked 0.65 kernel
------------------------------------------------------------------------------------------------
i can only check this question again later tonight.. (gst 1+) so ni about 4 to 5 hours.
use this instead. Much easier and friendly
http://forum.xda-developers.com/showthread.php?t=794638
azzledazzle said:
use this instead. Much easier and friendly
http://forum.xda-developers.com/showthread.php?t=794638
Click to expand...
Click to collapse
+1 on you but i need it for other things to like superCID/making superCID undone...
i did try adb that comes with sdk stuff...
Arrrr i see.
Well dowload ADB again, make sure drivers are upto date, Make sure ADB is in the correct location. And always make sure the commands are correct.
azzledazzle said:
Arrrr i see.
Well dowload ADB again, make sure drivers are upto date, Make sure ADB is in the correct location. And always make sure the commands are correct.
Click to expand...
Click to collapse
check,check,check
if adb devices gives nothing and adb reboot bootloader neither then i guess it doesnt lie down to my adb drivers, since i used them before my laptop just randomly blanked itsself and i needed to get everthing up and running again
You got USB Debugging checked ??
azzledazzle said:
You got USB Debugging checked ??
Click to expand...
Click to collapse
myself said:
Hi ...
htc sync mode
i did check usb debugging and it was checked
i run OrDriod 2.0.1(2.0.2 in a couple of min) FW 3.32 bricked 0.65 kernel
Click to expand...
Click to collapse
that must say it?
haha sorry i didnt read that bit lol....
azzledazzle said:
haha sorry i didnt read that bit lol....
Click to expand...
Click to collapse
np i just need it working again since that flash tool for splash screen doesnt work ether
android flasher works perfect , I was using it less than 10 mins ago....
ADB not working - Android flasher not working ... Seems like some issue with your PC / Drivers
azzledazzle said:
android flasher works perfect , I was using it less than 10 mins ago....
ADB not working - Android flasher not working ... Seems like some issue with your PC / Drivers
Click to expand...
Click to collapse
i thought more of the phone
Possibly,, But providing USB debugging is checked, And there seem to be no other faults / problems with the phone, I cant figure out what could be causing this ?? On the phones part i mean.
Damn i really need adb fixed got a kinda ride splash screen and every watches my screen...
Sent from my Sensation using xda premium
ADB is in the right location yeah ?
what error does android flasher give (if any)
Non just cant go further then starting the daemon srrver because there is no phone connected in fastboot usb mode xD
Sent from my Sensation using xda premium
did you uncheck the 'im already in fastboot' box on android flasher ?
Yes as well as check if devices are connected by adb was non
Sent from my Sensation using xda premium
Hmmmmm. Very strange.
What OS do you have on your PC ?
Btw updated to 2.0.2 with 0.7 bricked kernel
Sent from my Sensation using xda premium
Windows 7 64 bit
Sent from my Sensation using xda premium
Okay, so this is a new one to me, I installed TWRP Recovery after formatting System, Boot, Recovery, and Modem. I successfully reinstalled everything using a combo of fastboot and TWRP, but now my device is acting, well, weird. My system loads, but only after I open the bootloader and choose the "Normal Startup" option. Everytime I power down, it shuts off and loads into fastboot. I then need to open the bootloader and choose the above stated option to load my OS. What the heck, all I want to do is be able to UPDATE so I can participate in the JB Soak Test...has anyone come across this issue? Need some Dev Love right about now, I'm relatively new to this.
Reflash stock FXZ.
mrvek said:
Reflash stock FXZ.
Click to expand...
Click to collapse
Can I do that from TWRP?
Sent from my XT897 using xda app-developers app
galacticservant said:
Can I do that from TWRP?
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
No. You need RSDLite. FXZ from Skrilax_CZ's thread here.
But I've seen in other threads you have issues with rsd. You should fix drivers issue first, ie. get your device recognized first. Remove all drivers, reinstall, use device manager to see if some drivers are missing... IIRC, windows needs to install different drivers for running system (mtp, mass storage mode...) and different for bootloader mode, it should notify you of the process happening.
mrvek said:
No. You need RSDLite. FXZ from Skrilax_CZ's thread here.
But I've seen in other threads you have issues with rsd. You should fix drivers issue first, ie. get your device recognized first. Remove all drivers, reinstall, use device manager to see if some drivers are missing... IIRC, windows needs to install different drivers for running system (mtp, mass storage mode...) and different for bootloader mode, it should notify you of the process happening.
Click to expand...
Click to collapse
Yeah, I just installed a driver cleaner. Then I disabled the auto driver updater that windows has. Next I'll reinstall Moto device Manager and RSD Lite. The one driver that does not install is the Moto Networking Interface, which I believe is the culprit here if I'm not mistaken.
Sent from my XT897 using xda app-developers app
mrvek said:
No. You need RSDLite. FXZ from Skrilax_CZ's thread here.
But I've seen in other threads you have issues with rsd. You should fix drivers issue first, ie. get your device recognized first. Remove all drivers, reinstall, use device manager to see if some drivers are missing... IIRC, windows needs to install different drivers for running system (mtp, mass storage mode...) and different for bootloader mode, it should notify you of the process happening.
Click to expand...
Click to collapse
Yes, went into My Computer right click Properties, then chose Environmental Variables, and entered a user variable to allow showing of unused and hidden device drivers. Cleared all the ones that were outdated or possible conflicts (usb and adb drivers from samsung, htc, etc.), then reinstalled RSD Lite 6.1.5 and Moto Device Manager. Booted into Android system, ADB loaded. USB Mass Storage loaded. Booted into AP fastboot, NOTHING. Booted into Tools and a bunch of drivers were not found. Strange, I thought Moto Device Manager would cover those, isn't that what it's for??? I somehow am not getting the needed drivers, probably the Motorola Networking Interface. Any ideas?
Sent from my XT897 using xda app-developers app
galacticservant said:
Yes, went into My Computer right click Properties, then chose Environmental Variables, and entered a user variable to allow showing of unused and hidden device drivers. Cleared all the ones that were outdated or possible conflicts (usb and adb drivers from samsung, htc, etc.), then reinstalled RSD Lite 6.1.5 and Moto Device Manager. Booted into Android system, ADB loaded. USB Mass Storage loaded. Booted into AP fastboot, NOTHING. Booted into Tools and a bunch of drivers were not found. Strange, I thought Moto Device Manager would cover those, isn't that what it's for??? I somehow am not getting the needed drivers, probably the Motorola Networking Interface. Any ideas? I even progressively went through and installed every version of RSD all the way back to version 5.7.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Sorry for the double post
Sent from my XT897 using xda app-developers app
I really do not know. I'd try to reinstall drivers while in bootloader. But seems like a long shot.
Why did you format system, boot, recovery, modem?
Is your system functional? Try to connect it as MTP instead of mass storage (if not already).
On my XP machine for the additional BP Tools devices, I had to use the pre-release v5.9.1 drivers (developer version, 32bit only) that have been posted here:
http://forum.xda-developers.com/showthread.php?t=1891582
kabaldan said:
On my XP machine for the additional BP Tools devices, I had to use the pre-release v5.9.1 drivers (developer version, 32bit only) that have been posted here:
http://forum.xda-developers.com/showthread.php?t=1891582
Click to expand...
Click to collapse
I will definitely try that...thanks
Sent from my XT897 using xda app-developers app
mrvek said:
I really do not know. I'd try to reinstall drivers while in bootloader. But seems like a long shot.
Why did you format system, boot, recovery, modem?
Is your system functional? Try to connect it as MTP instead of mass storage (if not already).
Click to expand...
Click to collapse
Well, I was being stupid. Trying to bring back to stock, didn't have RSD, and had 8 hours till Moto pushed JB to my phone. So, I formatted and wiped the whole thing, oops.
Sent from my XT897 using xda app-developers app
galacticservant said:
Well, I was being stupid. Trying to bring back to stock, didn't have RSD, and had 8 hours till Moto pushed JB to my phone. So, I formatted and wiped the whole thing, oops.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
I could easily be wrong but I doubt formatting recovery, modem, kernel and ramdisk (boot) is a wise thing to do if you're only trying to get clean stock. Simply re-flashing stock image should take care of everything.
mrvek said:
I could easily be wrong but I doubt formatting recovery, modem, kernel and ramdisk (boot) is a wise thing to do if you're only trying to get clean stock. Simply re-flashing stock image should take care of everything.
Click to expand...
Click to collapse
Hind sight.....
Sent from my XT897 using xda app-developers app
So it turns out that I didn't run the command "moto-fastboot oem fb_mode_clear" after manually reinstalling my OS through fastboot utility. My phone now boots up normal. Still no end in sight for getting RSD Lite to recognize my phone...
Sent from my XT897 using xda premium
galacticservant said:
So it turns out that I didn't run the command "moto-fastboot oem fb_mode_clear" after manually reinstalling my OS through fastboot utility. My phone now boots up normal. Still no end in sight for getting RSD Lite to recognize my phone...
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
(I followed the .xml script contained in the SBF and manually erased and flashed my entire system. Forgot the above referenced line though and my system was locked going to sticky-bit factory fastboot. There is a command line "moto-fastboot oem fb_mode_set" which I believe RSD uses to make the device reboot into fastboot after partitioning and such (.mbn?). Anyway, I'm still learning so cut me some slack. Everybody has to start somewhere, right?
Sent from my XT897 using xda premium
Okay so I did read up on another post about the same issue but it didn't really explain what fixed it. I only have a windows xp or vista or something computer. Its a 32 bit. I have installed and uninstalled drivers from SDK manager, manually installed Google drivers, universal drivers. All of it. I originally tried rooting using cf auto. Than tried to do it manually. That is when I realized it was a fastboot issue. I'm in fastboot mode during my attempts. Should it say fastboot USB when plugged in?
Sent from my Nexus 5 using xda app-developers app
whozilla said:
Okay so I did read up on another post about the same issue but it didn't really explain what fixed it. I only have a windows xp or vista or something computer. Its a 32 bit. I have installed and uninstalled drivers from SDK manager, manually installed Google drivers, universal drivers. All of it. I originally tried rooting using cf auto. Than trues to do it manually. That is when I realized it was a fastboot issue. I'm in fastboot mode during my attempts. Should it say fastboot USB when plugged in?
Click to expand...
Click to collapse
Have you endabled USB debugging under Developer options in your Settings?
Yep. More details
I have uninstalled and re installed all drivers from
lgs driver .exe
From the universal. Driver.
And google drivers
via sdk manager.exe.
I did that after i re set up android SDK in the c drive,s root. and ran the commands from directly in the platforms folder. Still my device is only seen under adb devices. Not fastboot devices. I just type in fastboot in the promt and it shows all the commands listed so I assume it has been set up.
Now it seems SDK manager won't open. A promt pops up and closes with no program open thereafter. I wanted to retry googles drivers because I uninstalled and re set up android SDK. I wanted to re download the packages and start fresh.
Sent from my Nexus 5 using xda app-developers app
whozilla said:
Yep. More details
I have uninstalled and re installed all drivers from
lgs driver .exe
From the universal. Driver.
And google drivers
via sdk manager.exe.
I did that after i re set up android SDK in the c drive,s root. and ran the commands from directly in the platforms folder. Still my device is only seen under adb devices. Not fastboot devices. I just type in fastboot in the promt and it shows all the commands listed so I assume it has been set up.
Now it seems SDK manager won't open. A promt pops up and closes with no program open thereafter. I wanted to retry googles drivers because I uninstalled and re set up android SDK. I wanted to re download the packages and start fresh.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Google tool adb fastboot drivers xda. That should get them working
Nice. gonna try as soon as I get home from work. I'll report back with result :thumbup:
Sent from my Nexus 5 using xda app-developers app
You're still thinking of HTC phones...
When in fastboot it will no change on the phone itself, you check by running 'fastboot devices' in the command prompt. If you see your serial number, it's fine. If you don't, go into Device Manager and manually update the driver
If you run 'adb devices' when connected in fastboot nothing will happen as adb is ONLY FOR WHEN ANDROID IS RUNNING (how many more times does this need to be said??).
whozilla said:
Nice. gonna try as soon as I get home from work. I'll report back with result :thumbup:
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I'm sorry eddy. It seems you misread my posts. Im not having an issue understanding the difference between adb and fastboot. Allow me to clarify. While phone is on. With USB debugging enabled. I type
adb devices
in the command prompt under platform tools.. My device shows up and I have authorized it
When my phone is in the bootloader in fastboot mode. I type
fastboot devices
Nothing. That is my issue. Feel free to scroll back up and read the details. Any help is good help :beer:
Sent from my Nexus 5 using xda app-developers app
EddyOS said:
You're still thinking of HTC phones...
When in fastboot it will no change on the phone itself, you check by running 'fastboot devices' in the command prompt. If you see your serial number, it's fine. If you don't, go into Device Manager and manually update the driver
If you run 'adb devices' when connected in fastboot nothing will happen as adb is ONLY FOR WHEN ANDROID IS RUNNING (how many more times does this need to be said??).
Click to expand...
Click to collapse
I quoted myself by mistake haha. PS
I have manually updated drivers. After uninstalling them to be clear. That's what I meant when I said I tried the universal drivers. For the record. All attempts I have made to get fastboot to recognize my device have been done using forums with detailed instructions.
Sent from my Nexus 5 using xda app-developers app
Sounds like Windows isn't wanting to use the driver. Manually update the driver and point it to the *.inf file in the SDK. It should then work fine
Solved. Such a small detail. Eddy you were right. Before I could see your post I realized. Vuala! I needed to update the drivers manually with the phone plugged in in fastboot mode!. That was my mistake. Cf root did the rest.
In device manager you will see a yellow triangle under other devices when the nexus is plugged in on fastboot mode. I installed drivers from the .exe found in this thread.tool adb fastboot drivers. I let the computer search on its own for updates. Done. Rooted
Sent from my Nexus 5 using xda app-developers app
jd1639 said:
Google tool adb fastboot drivers xda. That should get them working
Click to expand...
Click to collapse
Thank you sir. You lead me in the right path
Sent from my Nexus 5 using xda app-developers app