Database Info

[Q] Fastboot problem

hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!

I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk

Did you try a fastboot command like fastboot devices?

Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.

Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz

Fastboot issues - Can't Get it to Work

I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.
I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
0315c2d60935c160 device
Then I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
ADB sees the phone; Fastboot does not.
The solution is well documented on the web: Install new drivers. I have been installing drivers from just about everywhere for the last week without success. With the phone connected, I get this from Device Manager:
Computer
Android Device
Android Composite ADB Interface
The driver information is as follows:
Driver Provider: Google, Inc.
Driver Date: 7/9/2013
Driver Version: 8.0.0.0
Driver Signer: Google, Inc.
Driver Details:
Driver Files:
C:\Windows\System32\Drivers\Winsub.sys (File Version 6.2.9200.16384(Win8_rtm.120725-1247))
C:\Windows\System32\WdfcoInstaller01009.dll(File Version 1.9.7600.16385 (Win7_rtm.090713-1255)
C:\Windows\System32\WinUSBCoInstaller2.dll (File Version 6.1.7600.16385 (win7_rtm.090713-1255))
I am running a Dell XPS-17 I7 laptop with Windows 8 (not 8.1) 64 bit
If I could find a way to unlock without using Fastboot, that would probably be a good solution, but I can’t. And I have absolutely no success at getting Fastboot to work.
I do notice that the Device Manager lists Android Composite ADB interface (ADB works) but noting about a Fastboot interface. Does that mean anything?
Please help I am at my wit’s end.
For what it is worth, I did read all the tutorials here, and the only thing I could figure out was if I have the right drivers everything works fine. I also reviewed the posts here, including "Diagnosing USB Driver and ADB issues in Windows," which discusses ADB (which I have no problem with)

this article helped me out a bunch. http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
you'll have to edit the "android_winusb.inf" with the correct hardware id.
in Device Manager make sure you go to "Android Device" > "Android Composite ADB Interface" go to Properties. on the Details tab and then click on the drop down box and select "hardware ids" you might see 2 ids there. i believe the one you'll need is the bottom one. if you only have one. thats fine too.
so, read the article. grab your hardware id and edit your driver. see if it works. you may have to reboot after you edit the driver. hope this works for you.

krdu said:
I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.
I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
0315c2d60935c160 device
Then I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
ADB sees the phone; Fastboot does not.
Click to expand...
Click to collapse
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.

Sounds like you need to boot your phone into fastboot mode. Power off the phone and hold volume down and hit the power button.
Then the fastboot devices command should work and you should be able to unlock the boot-loader then. Unlocking the boot-loader will wipe your phone just so you know.

erikivy said:
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.
Click to expand...
Click to collapse
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.
I then went and tried it in the bootloader, to copy listings to post, and here's what I got!
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)
List of devices attached
0315c2d60935c160 device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
0315c2d60935c160 fastboot
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 41.215s]
finished. total time: 41.215s
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.
Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)

You realize that the two command line interfaces (ADB and fastboot) don't work in the same state, right? ADB is for use in recovery and while booted, whereas fastboot only works in bootloader. It sounds to me like everything is working exactly as it should.
I'm no expert or anything, but I always assumed that they were two different ways to interact with your device while it is in different states. If I'm mistaken, someone please correct me.

krdu said:
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.
I then went and tried it in the bootloader, to copy listings to post, and here's what I got!
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)
List of devices attached
0315c2d60935c160 device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
0315c2d60935c160 fastboot
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 41.215s]
finished. total time: 41.215s
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.
Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)
Click to expand...
Click to collapse
ADB is used in android and the recovery.
Fastboot is used only in the bootloader.

[SOLVED] Nexus 5 shows up in adb but not fastboot.

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

[Q] Softbricked after 4.3.3

Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.

haloux said:
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
Click to expand...
Click to collapse
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app

Vivek_Neel said:
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Thanks for the quick response.
Win7 doesn't even detect the N5. Device manager doesn't even show that it exists (as android device or anything else). I've unplugged and replugged, no sound, multiple different ports.

Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.

habitformer said:
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
Click to expand...
Click to collapse
Will do (or won't do?). Thank you for the advice. Any tips on how to get my system to recognize the device?

So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.

haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.

haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.

habitformer said:
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
Click to expand...
Click to collapse
Yea, USB debugging was on. The recovery mode just yields the dead android.
adrman said:
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
Click to expand...
Click to collapse
How would I verify that? I assumed that fastboot drivers were installed bc I used them in the past.
Code:
fastboot devices
(yields)
No devices found.

I would do a search here for "windows fastboot drivers". I can't be of much help to you as I haven't used windows for several years now. Also, if you have a working Android device, see if it shows up when connected in bootloader mode as a test.
Sent from my Nexus 5 using Tapatalk

Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.

haloux said:
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
Click to expand...
Click to collapse
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Wow. It worked! The device showed up! Thank you guys.

haloux said:
Wow. It worked! The device showed up! Thank you guys.
Click to expand...
Click to collapse
Not sound like a turd but I mentioned using a nexus USB cable in post #7 after mentioning my issue.

[Q] Bootloader Unlocking Issue

So this is a bit weird but here goes. I already knew it was damned easy to unlock the bootloaders for Nexus 5s( usually), so I figured why not give it a go. Downloaded the sdk, enabled usb debugging, opened cmd, typed adb devices and yada yada. I get to the point where I reboot the device into fastboot via the cmd, type in fastboot oem unlock andddd........nada. Literally nothing happens, it just says waiting for devices in the cmd, but changes nothing on the Nexus 5. Anyone keen on what the problem might be?

boomvausstat said:
So this is a bit weird but here goes. I already knew it was damned easy to unlock the bootloaders for Nexus 5s( usually), so I figured why not give it a go. Downloaded the sdk, enabled usb debugging, opened cmd, typed adb devices and yada yada. I get to the point where I reboot the device into fastboot via the cmd, type in fastboot oem unlock andddd........nada. Literally nothing happens, it just says waiting for devices in the cmd, but changes nothing on the Nexus 5. Anyone keen on what the problem might be?
Click to expand...
Click to collapse
If it says "waiting for devices", it means it cant see the device. When you boot into bootloader, the first command you trype should be "fastboot devices".
I would recommend ditching the SDK and uninstalling the drivers then setting your computer up the way I satet in my "Adb and fastboot. What is it?" thread, which you can get to via my signature link

rootSU said:
If it says "waiting for devices", it means it cant see the device. When you boot into bootloader, the first command you trype should be "fastboot devices".
I would recommend ditching the SDK and uninstalling the drivers then setting your computer up the way I satet in my "Adb and fastboot. What is it?" thread, which you can get to via my signature link
Click to expand...
Click to collapse
I'll try your method and see what happens
Update: It worked, thanks!!!