Develop Bugs

[Q] Phone not being recognized by computer in bootloader?

So I've been trying to root/unlock my CDMA nexus and I'm having a very frustrating problem that's preventing me from doing it with any of the toolkits available OR the manual method. I have the android SDK installed, samsung's USB drivers, and everything else I've been told to get. I can detect my phone when it's connected (and USB debugging is on) using adb commands but ONLY when the phone is booted as normal. If I reboot into the bootloader, my computer no longer detects it, and I can no longer act upon it via adb. This, of course, is preventing me from getting anywhere on the unlocking/root front. Anyone have any ideas? I'm fresh out.

ADB doesn't work in boot loader/fastboot. Adb only works in recovery or when Android is fully running.
You need to use fastboot commands in bootloader/fastboot.
"Fastboot devices" to see if it's detected.
Sent from my Galaxy Nexus

have you installed the hboot drivers?

As above, you have to use fastboot commands when the phone is in bootloader. Try "Fastboot devices" to see if your computer sees the phone.

Fastboot commands don't detect the phone either. Fastboot is installed, as I can get it via command prompt to show available commands and whatnot, it just does not detect a device to work on.

I am also having this exact problem when i try to install the new touch cwm beta that was just released. Its not detecting the device while in the bootloader, and when i try to fastboot flash recovery it just says <waiting for device> and does nothing.

I know this is a little late, but I figured I’d post here to help anyone else out that is having this problem. I was trying to update my Galaxy Nexus from 4.0.2 to 4.0.4 using fastboot when I ran into the problem you’re having. I did this from a Windows 7 machine, and the fix for me was as follows:
1. After booting into the bootloader and having your phone plugged into your computer, open Computer Management.
2. Under Device Manager, in Computer Management, you should see a listing for a device called “Android 1.0” and it’ll have the little yellow triangle with the exclamation point on it.
3. Right click on the Android 1.0 device and select “Update Driver Software…”
4. Click “Browse my computer for driver software”
5. Click “Let me pick from a list of device drivers on my computer”
6. If you installed the Samsung drivers for the phone, scroll down until you see a device listed as “SAMSUNG Android Phone”
7. Select it and click next
8. It should auto populate the driver information. Click next and it will install the device
9. Go back to your CMD prompt and fastboot devices should now list the phone.
Hope this helps!

Quicks man your the best!

...or use Linux #trolling
Sent from my Galaxy Nexus using xda app-developers app

[Q] Fastboot Adb drivers not installing, please help[SOLVED]

I've been trying since last night to root my Nexus, because I want to install Jelly Bean. When I used the Galaxy Nexus Toolkit to install my drivers it did fine for adb. When I go into device manager it shows up as Android Phone like its supposed to. However, when I boot into fastboot mode, my computer no longer recognizes my Nexus and when I got into device manager, nothing shows up for it...not even Android 1.0.
Can someone please give me some tips as how to fix this issue.
P.S. I also installed the Google SDK along with the Google USB drivers afterwards, hoping that would fix the issue...but no luck...and I tried PDAnet...still no luck
The issue I was having was due to the fact that I wasnt pressing Volume Up+Volume Down+Power, so I wasnt even in fastbook, but a screen similar to it

schwartzman93 said:
I've been trying since last night to root my Nexus, because I want to install Jelly Bean. When I used the Galaxy Nexus Toolkit to install my drivers it did fine for adb. When I go into device manager it shows up as Android Phone like its supposed to. However, when I boot into fastboot mode, my computer no longer recognizes my Nexus and when I got into device manager, nothing shows up for it...not even Android 1.0.
Can someone please give me some tips as how to fix this issue.
P.S. I also installed the Google SDK along with the Google USB drivers afterwards, hoping that would fix the issue...but no luck...and I tried PDAnet...still no luck
Click to expand...
Click to collapse
The driver needs to be installed TWICE: once when you are booted normally, and once when booted in fastboot. http://forum.xda-developers.com/showpost.php?p=28060885&postcount=3

efrant said:
The driver needs to be installed TWICE: once when you are booted normally, and once when booted in fastboot. http://forum.xda-developers.com/showpost.php?p=28060885&postcount=3
Click to expand...
Click to collapse
My problem is that when I plug in my phone...while its in fastboot its not recognized as an Android phone or Android 1.0...its recognized as a "SAMSUNG Mobile USB CDC Composite Device"

schwartzman93 said:
My problem is that when I plug in my phone...while its in fastboot its not recognized as an Android phone or Android 1.0...its recognized as a "SAMSUNG Mobile USB CDC Composite Device"
Click to expand...
Click to collapse
That's because you need to uninstall all the old drivers and install the ones I link to...
Sent from my Galaxy Nexus using Tapatalk 2

FastBoot Driver- Xperia Neo
efrant said:
That's because you need to uninstall all the old drivers and install the ones I link to...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi,
I am using sony sricsson neo .587. I tried to connect my phone in fastboot mode. I connected in fastboot mode. I am not able to install drivers for that.
Steps I Followed
1. I updated google usb driver
2. Replaced "android_winusb.inf" file which is provided by Sony official
3. Connected phone in fastboot mode
4. It asked for drivers
5. I selected usb driver folder to install drivers
But It fails...
I am doing these all things on Windows 7 64 bit
Please help...

[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

No OS- ADB wont work, and no recovery- Stuck :(

Hello everyone, been a while since I have been on this site.
I am in a dilemma which I hope you guys can help me with.
I have a samsung galaxy nexus, and I just wiped the phone. But there is no recovery, so I have no OS atm.I have tried the Android Toolkit, however, everytime I try using it I get problems. It says , " waiting for adb mode" . I downloaded SDK and have runned the adb.exe file, but a command prompt pops up, and a bunch of stuff pops up and scrolls down, and then it closes. It does nothing.
I have read that my drivers for ADB are not installed properly or whatever. So I tried uninstalling them from " device manager" and I tried reinstalling them. That didnt work. I tried uninstalling again and than downloaded a samsung galaxy nexus usb adb driver, which also did not work.
I just want to be able to place a ROM on my phone from the computer. If I can get that far, I can install it from recovery mode. But I cant even get it fully detected on my computer. Whenever I plug in the USB, it detects it, but drivers fail.
Also, in device manager, the universal serial bus controller, SM bus controller, and ethernet controller all have a yellow triangle over them. They always fail to install..
I have tried updating them from the device manager. But that has failed aswell..
Please someone help me. I am at a dead end and unsure what to do.
-Andrew

Try a different cable or different drivers. And please learn to use adb yourself and stop using toolkits.
Sent from my Galaxy Nexus using XDA Premium HD app

Can you enter in bootloader?
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

I can go into bootloader and recovery mode. I also tried a different computer and usb. It looks like its a bit better now because it actually says Galaxy nexus, instead of android device. However, I still cant go into ADB mode.
Everywhere I go, people say you need to enable debugging....but I dont have an OS. I am stuck in recovery or fast bootmode.
In the meanwhile, I tried installing zip file via sideload using Android Toolkit by skipsoft.( option 16) ....it looked like it was going to actually work...but it didnt. It says i dont have a recovery for TWRP or any of the other options.

You need to install fastboot drivers, and download 4.3 (or any you like) Google factory image for maguro. Flash that image, and install prefered custom recovery
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

I downloaded the fastboot usb drivers, however, I am not sure what to do with them.
Here's a pic of the files. I also download the adb files, and installed them, even though it said I had existing files.

andrewb71 said:
I downloaded the fastboot usb drivers, however, I am not sure what to do with them.
Here's a pic of the files. I also download the adb files, and installed them, even though it said I had existing files.
Click to expand...
Click to collapse
Enter bootloader on phone and connect it to PC. Phone probably wont be recognized. After that go to Device manager and find your phone ( as I remember it will say Android 1.0 or something similar), right click on it and press Update driver. In new dialog it will ask you whether you want to automaticly find drivers or manually. Press manually and select that usb_driver folder.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

Not detected in boot loader.

So I'm trying to flash the L preview. I plug my n7 in and do adb devices and it shows up, I adb reboot bootloader and it boots into the boot loader, but while in it if I do adb devices nothing comes up and if I do the flash-all.bat it just stays stuck on waiting on device. And yes I have USB debugging, and just updated drivers and installed SDK fresh. This just seems odd.
Sent from my LG-D801 using xda premium

C-4Nati said:
So I'm trying to flash the L preview. I plug my n7 in and do adb devices and it shows up, I adb reboot bootloader and it boots into the boot loader, but while in it if I do adb devices nothing comes up and if I do the flash-all.bat it just stays stuck on waiting on device. And yes I have USB debugging, and just updated drivers and installed SDK fresh. This just seems odd.
Sent from my LG-D801 using xda premium
Click to expand...
Click to collapse
When you are in bootloader mode, the correct command to list devices is: fastboot devices
Let me know if that command gives you a device id.
If it does not, then you must get your drivers situated.

mdamaged said:
When you are in bootloader mode, the correct command to list devices is: fastboot devices
Let me know if that command gives you a device id.
If it does not, then you must get your drivers situated.
Click to expand...
Click to collapse
Well not working while using the flash-all.bat would still indicate it's not recognized in boot loader mode. Which is weird when it is while its on.
Sent from my LG-D801 using xda premium

Any ideas?
Sent from my LG-D801 using xda premium

C-4Nati said:
Any ideas?
Sent from my LG-D801 using xda premium
Click to expand...
Click to collapse
I already suggested what needs to be done, you need to get your drivers working correctly. There are different drivers for the different modes.
Here is what I did to get my N7 2013 recognized in every possible mode: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887

Do you have a syncing program for your handset/tab installed?
If so I'd uninstall it as they tend to take over the USB when you plug your device in, changes the USB port com ID and only meant for an up and running system and not in bootloader/recovery/etc
As for an actual response as in an ID/model/etc using adb or fastboot I've never seen it shown when I've tried it even with official and unofficial drivers others have had responses with!! ..but not had any problems flashing except with a sync program on pc
(personally never use sync progs since then )
Bashing away at my HTC Desire C