Develop Bugs

[Q] Verizon Galaxy Nexus cannot connect via fastboot

Hi All,
I just received a used Galaxy Nexus from a buddy and wanted to root and flash it up to 4.2. It is currently at 4.1.1 JRO030.
Everything seems to work fine (phone is not activated yet - no SIM - still need to transfer number), but other than that all is a go. I can see the phone via ADB in Linux and Windows. When I boot in to the bootloader though fastboot will not see the device. The volume keys do not change the menu (stays on START) and I have to pull the battery to reboot. The bootloader does show as being unlocked.
I have tried factory Reset (multiple times)
Linux and Windows - SDK
Wug's Nexus Root ToolKit - followed all the instructions from multiple sources.
Again - ADB works and sees the device and I can use "adb reboot bootloader" with no problem. When the bootloader comes up (either via ADB or 3-button power up) I am stuck.
Any help is appreciated.
Pax,
Arklazak

Make sure u are in USB debugging and make sure the drivers are installed right on your computer.
Sent from my Galaxy Nexus using xda premium

Esteway.619 said:
Make sure u are in USB debugging and make sure the drivers are installed right on your computer.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply.
The USB Debugging is enabled (first thing I did as I have unlocked and rooted other devices) and USB drivers are correct and working since ADB sees the device correctly. Also, it is my understanding that USB Debugging does not apply when the bootloader is up.
One thing I just noticed in Windows (XP) is that when the phone reboots into the bootloader, the ADB devices go away in device manager.
Any idea why the bootloader is unresponsive - seems locked. It seems as if the bootloader is not loading completely - since the volume buttons do not work and a battery pull is necessary.
Pax,
Arklazak

This worked for me:
rootzwiki -> Google/Nexus Devices -> Galaxy Nexus -> "Galaxy Nexus Root Procedure - (broken) ADB Method Dont USE" -> page 3, second to last post on the page (by litso):
"EDIT: Scratch that, was able to use the PDANet drivers. Install PDA Net, reboot into bootloader, open device manager, manually select the directory "C:\Program Files (x86)\PdaNet for Android\usbwin". Fastboot will then recognize the device and allow you to unlock."
I can't post a link because I am a 'new user' due to low number of posts, but that is the path to your solution. I literally just went through this yesterday.

g_what said:
This worked for me:
rootzwiki -> Google/Nexus Devices -> Galaxy Nexus -> "Galaxy Nexus Root Procedure - (broken) ADB Method Dont USE" -> page 3, second to last post on the page (by litso):
"EDIT: Scratch that, was able to use the PDANet drivers. Install PDA Net, reboot into bootloader, open device manager, manually select the directory "C:\Program Files (x86)\PdaNet for Android\usbwin". Fastboot will then recognize the device and allow you to unlock."
I can't post a link because I am a 'new user' due to low number of posts, but that is the path to your solution. I literally just went through this yesterday.
Click to expand...
Click to collapse
Thanks g_what. I will look at it and try it out this weekend - on the road for work right now - and report back. On the plus side, I have been able to get the phone rooted (from Linux) without the bootloader - thanks to efrant's thread here: http://forum.xda-developers.com/showthread.php?t=1894717
I still want to get the everything up to snuff.
Pax,
Arklazkak

You can unlock the bootloader without fastboot when the phone is off using OMAP: http://forum.xda-developers.com/showthread.php?p=41612401#post41612401

im experiencing the same issue
wug fresh cant detect fastboot ... drivers are installs correctly and adb is recognized and i can access fastboot through command prompt .. any suggestions?

[Q] Can Not get ADB and Fastboot drivers to install

Windows 7 x64
Galaxy Nexus i515, BROKEN SCREEN, USB DEBUGGING WAS NOT TURNED ON. The phone is completely stock I just turned it on and used it until I broke my screen. Screen lock is on.
I have been trying to access my phone, using Fastboot, to wipe it before I send it in for warranty. I can not seem to do this at all. It seems that I can not install the drivers because I have not enabled USB debugging. Is this true? I have been following this guide : http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/ When i go to manually install the drivers, from SDK, I get, "The folder you specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure that it is designed to work with Windows for x6-based systems." I then tried the driver from Samsung and got the same response.
So then I hold VOL+ _ VOL- and Power and tried to install the drivers for Fastboot with the same outcome as above. Also when I boot in Fastboot mode the drivers that are installed make my phone a modem. The driver is called, "SAMSUNG Mobile USB Modem." I can not get this to change.
So to summarize I can not get the ADB Drivers to install, because I do not have USB Debugging enabled, that in return will not allow me to install Fastboot Drivers because when I plug the phone in the computer sees it as a Modem.
Any suggestions? I am just trying to erase the info on my phone I have given up all hope of recovering any data.
Thanks,
qualm

USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.

beekay201 said:
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
Click to expand...
Click to collapse
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.

_qualm_ said:
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
Click to expand...
Click to collapse
I know what a screen pattern lock is.
Uninstall all drivers, reboot pc.
Assuming device is off: press power+vol up+vol down, until you feel the vibration. Wait 2 secs or so. Device will be in fastboot mode.
Read this thread, i say again, READ this thread, obviously start with the first post! - http://forum.xda-developers.com/showthread.php?t=1812959

Thanks for the link. I read it and followed instructions for installing the drivers. Here is what I did:
1.Uninstalled all drivers
2.Rebooted my PC
3.Downloaded these Drivers, as suggested: http://forum.xda-developers.com/showthread.php?t=1379875
4.Followed these instructions, on how to install the driver without windows trying to find one automatically: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Everything seemed to go well under the Device Manager, when I plug my phone in in fastboot mode, it shows Android Phone -> Samsung Android Interface. This is way better than what I had before, when it was showing up as a Modem. Now when I try to use fastboot.exe and I type "fastboot devices" nothing shows up. I reset the computer and replugged in my device, in fastboot, and the same thing nothing shows up in fastboot.
Thanks for you help.

Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.

beekay201 said:
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
Click to expand...
Click to collapse
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.

Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus

W8 a sec, do you even have your bootloader unlocked???
You said you're running stock, so that should have been my first question, because to unlock your bootloader through the usual way, you need to confirm a dialog on the device... which in your case, doesn't have a working screen.
_qualm_ said:
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Click to expand...
Click to collapse
....
Lets see:
That post shows how it's done, correctly. (I think, from what i've read)
pay attention to part 3)
3)
NOTE:
- The method described here can be used to install the "Samsung Galaxy Nexus ADB Interface" driver as well as the "Samsung Galaxy Nexus Bootloader Interface" driver.
- Differences between the two procedures. One is done with the phone booted up normally and "USB Debugging" is enabled, and the other is done when the phone is in fastboot. I will cover the "USB Debugging" part here.
Click to expand...
Click to collapse
then...
We will now install the two drivers that efrant talked about in his post.
A) (FOR ADB - WHEN RUNNING ANDROID OS):
Enable USB debugging on your device
- Goto Settings > Developer Options > Check "USB Debugging"
- Connect device, manually update driver to Naked driver by 1wayjohny, done. On 4.2 and above, you'll need to confirm that you accept the host's (your pc) RSA key.
B) (FOR FASTBOOT - WHEN RUNNING FASTBOOT MODE)
boot into fastboot mode - power off phone and hold vol up + vol down + power
Click to expand...
Click to collapse
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.

Pirateghost said:
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I am learning this ^. I am having trouble getting my computer to see my phone, in fastboot mode. All of the instructions that I have read start with installing drivers for ADB, which requires the phone to be USB debugging mode, and then the drivers for fastboot. So I thought my trouble was, since I can not install the drivers for ADB, and that I was having trouble with all of my drivers, that it was probably the fact that my phone can not be put into USB debugging mode. I now realize that USB debugging has nothing to do with fastboot, as fastboot is before the OS is booted. I am still just having trouble with my fastboot driver and seeing my phone with fastboot.exe.

beekay201 said:
W8 a sec, do you even have your bootloader unlocked???
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Click to expand...
Click to collapse
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.

_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus

Pirateghost said:
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you used odin to flash something, that will unlock the bootloader. Flashing a section of edited param using OMAP flash will also unlock the bootloader.
Beamed from my Maguro.

I also have the same problem with my galaxy C5.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
My galaxy C5 is also not recognized as a bootloader interface while in fastboot mode, after installing all the drivers correctly. Samsung usb driver v1.5.63.0 makes the changes i think, and it makes it as a modem instead of bootloader. maybe the solution is i have to manually update the driver of that modem into bootloader, right click on the modem in device manager and change it's driver into bootloader of your phone, maybe it works. I will try it this way.
Let me know if this solution has worked for someone.
Thanks

HELP!!! Why Can't I unlock my device {Fixed}

I have spent 2 days trying to unlock my new Nexus 7 HD. I'm not a noob, my last 7 phones I have rooted, flashed, unlocked and messed around with, my last 3 tablets I've unlocked and rooted including my 2012 Nexus 7.
Everytime I try to unlock it says fastboot not found. I'm using Nexus Root Toolkit 1.7.1. I can boot into the bootloader using the toolkit, and when it's in bootloader mode, I can also reboot the bootloader using the toolkit. When I click unlock, i get the fastboot device no found. When the Nexus 7 is turned on, my device manager shows "Android Composite ADB device" when the Nexus is in bootloader mode my devices show "Android bootload interface" USB debugging is enabled which don't effect fastboot anyways.
I've tried all 4 of my USB ports, I've followed the driver instructions to a "T", I've uninstalled all the
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- or ANYTHING else you see that resembles your Nexus.

budco2000 said:
I have spent 2 days trying to unlock my new Nexus 7 HD. I'm not a noob, my last 7 phones I have rooted, flashed, unlocked and messed around with, my last 3 tablets I've unlocked and rooted including my 2012 Nexus 7.
Everytime I try to unlock it says fastboot not found. I'm using Nexus Root Toolkit 1.7.1. I can boot into the bootloader using the toolkit, and when it's in bootloader mode, I can also reboot the bootloader using the toolkit. When I click unlock, i get the fastboot device no found. When the Nexus 7 is turned on, my device manager shows "Android Composite ADB device" when the Nexus is in bootloader mode my devices show "Android bootload interface" USB debugging is enabled which don't effect fastboot anyways.
I've tried all 4 of my USB ports, I've followed the driver instructions to a "T", I've uninstalled all the
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- or ANYTHING else you see that resembles your Nexus.
Click to expand...
Click to collapse
Is the fastboot command not found or the device is the one not found? Unlocking the bootloader is very easy using fastboot. I've never run any of the toolkits.
Once the device is connected to your computer and in bootloader mode (vol+down and power), you should get the device id returned if you run "fastboot devices". Then it is a simply matter of just running "fastboot oem unlock", use the vol to scroll to yes, and press the power to select. That is pretty much there is to it.

cowabunga said:
Is the fastboot command not found or the device is the one not found? Unlocking the bootloader is very easy using fastboot. I've never run any of the toolkits.
Once the device is connected to your computer and in bootloader mode (vol+down and power), you should get the device id returned if you run "fastboot devices". Then it is a simply matter of just running "fastboot oem unlock", use the vol to scroll to yes, and press the power to select. That is pretty much there is to it.
Click to expand...
Click to collapse
It says fastboot device not found. I know this is a driver issue, and I've tried different drivers. I unlocked my 2012 nexus 7 in under 3 minutes, but this is not going to smoothy lol

budco2000 said:
It says fastboot device not found. I know this is a driver issue, and I've tried different drivers. I unlocked my 2012 nexus 7 in under 3 minutes, but this is not going to smoothy lol
Click to expand...
Click to collapse
And you are booted to the bootloader, right?
I use a mac. No crazy drivers to deal with. Just plug and go.

cowabunga said:
And you are booted to the bootloader, right?
I use a mac. No crazy drivers to deal with. Just plug and go.
Click to expand...
Click to collapse
I got my bootloader unlocked. Now I can't root it. I downloaded like 3 toolkits, all of them are failing. I've never had so many problems with one device as this one. Wug's toolkit didn't see the device in bootloader, but N-cry toolkit had no problem seeing the device in bootloader mode, which unlocked bootloader, but it wont flash recovery or root. Wug's tool kit will push the files for recovery and root, but then when the Nexus goes into bootloader wug's toolkit fails because it don't see the device in bootloader mode. The quick root tool doesn't do anything at all. The problem here is I'm using windows 8 and I just read that android SDK drivers have to be manually installed, but even that is giving me problems. I have a bad ass laptop, A dell alienware that's never gave me a problem. It came with windows 7, and i put windows 8 on it about 8 months ago, thinking about running the restore CD's and downgrading back to windows 7. ADB commands aren't responding from a command promt. I just want root, and its being a real pain in the ass.

budco2000 said:
I got my bootloader unlocked. Now I can't root it. I downloaded like 3 toolkits, all of them are failing. I've never had so many problems with one device as this one. Wug's toolkit didn't see the device in bootloader, but N-cry toolkit had no problem seeing the device in bootloader mode, which unlocked bootloader, but it wont flash recovery or root. Wug's tool kit will push the files for recovery and root, but then when the Nexus goes into bootloader wug's toolkit fails because it don't see the device in bootloader mode. The quick root tool doesn't do anything at all. The problem here is I'm using windows 8 and I just read that android SDK drivers have to be manually installed, but even that is giving me problems. I have a bad ass laptop, A dell alienware that's never gave me a problem. It came with windows 7, and i put windows 8 on it about 8 months ago, thinking about running the restore CD's and downgrading back to windows 7. ADB commands aren't responding from a command promt. I just want root, and its being a real pain in the ass.
Click to expand...
Click to collapse
Now that I think about it, I don't think I had to even deal with installing a root. I installed twrp2 for recovery and it automatically detected that I did not have root as I was rebooting and it prompted me if I wanted to install root. I remember select yes and after it rebooted, I had root.
Make sure you enable root access for "Apps and ADB" in developer options. You may find you already have root.

cowabunga said:
Now that I think about it, I don't think I had to even deal with installing a root. I installed twrp2 for recovery and it automatically detected that I did not have root as I was rebooting and it prompted me if I wanted to install root. I remember select yes and after it rebooted, I had root.
Make sure you enable root access for "Apps and ADB" in developer options. You may find you already have root.
Click to expand...
Click to collapse
I got it. I ended up using the rootkit for the 2012 nexus 7, i remembered it had an option to push image files, I push the recovery file, then flashed super user. all is good

Can't get windows 10 to detect my Fastboot device

hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.

Put in fastboot mode, connect to computer and manually select fastboot interface from the device manager "install device/update driver manually" box. That worked for me.

JusTeN_ said:
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Click to expand...
Click to collapse
Its fine just search for fastboot devices and see if your device comes up. Mine was showing the same thing and i continued and it worked

Bootloader un-detected.

I am trying for the first time to root my 7t pro McLaren, and I ran into a problem. When the boot loader is turned on, and I use fastboot devices, nothing happens. When I do adb devices with it powered on, it shows that its connected. I tried to use the oneplus usb driver update, and nothing happened. does anyone have any solutions? I have OEM unlocking turned on and SIM permantly unlocked. If it helps I'm running on windows 10.

KH-Squisshy said:
I am trying for the first time to root my 7t pro McLaren, and I ran into a problem. When the boot loader is turned on, and I use fastboot devices, nothing happens. When I do adb devices with it powered on, it shows that its connected. I tried to use the oneplus usb driver update, and nothing happened. does anyone have any solutions? I have OEM unlocking turned on and SIM permantly unlocked. If it helps I'm running on windows 10.
Click to expand...
Click to collapse
Hi.
What you want to do exactly?
To Root open bootloader as first.
Developer options /Default usb configuration/ file transfer. Then check if pc "see" your device. fastboot fastboot devices. If visible then u are at home let's say

Make sure your USB port on the phone is clean using compressed air. Though if it works with ADB it should also work in bootloader

Riski3Run said:
Hi.
What you want to do exactly?
To Root open bootloader as first.
Developer options /Default usb configuration/ file transfer. Then check if pc "see" your device. fastboot fastboot devices. If visible then u are at home let's say
Click to expand...
Click to collapse
I was trying to just root it, but I found out what it was. someone sent me the drivers to update my device in manage devices.