Develop Bugs

Trying to unlock the bootloader

I get through all the steps, adb setup recognizes my device is connected. When i try to unlock the bootloader <fastboot oem unlock> command line locks up at <waiting for device>.
can someone advise?
Verizon if that matters

What happens when you type in "fastboot devices"

Nothing happens. Tried it both before and after typing in adb reboot bootloader

You sure your pc is detecting the phone when it is in fastboot mode? To me it seems like your computer isn't detecting the phone or the drivers didn't get installed properly.

<deleted>
answered my own question

I had the same issue. Assuming you're using Windows, you need to find where the latest Samsung drivers for the GN were copied to when you installed them (you have installed them, right?) The next time you plug in your phone, it will probably ask you to setup a new device. Tell it you will install the drivers from a location you choose, navigate to the folder where the drivers are, let it install them, restart if it asks, and then try the process over.
FWIW, I used the directions and links from this tutorial and eventually got it working. They include alternate drivers here in case the one from samsung.com doesn't work.

im having the SAME PROBLEM AND HAVE TRIED TWO DIFFERENT COMPUTERS.TRING ADB METHOD

What's the ADB method? Why don't you just just hold the volume up, volume down and power to get into fastboot mode? When you plug it in, windows should see a new device that needs drivers. You need to make sure the drivers are installed before fastboot will work.

i am in fastboot "little android with chest opened". and i do have the driver installed but in fastboot windows thinks its a different device

robitron929 said:
i am in fastboot "little android with chest opened". and i do have the driver installed but in fastboot windows thinks its a different device
Click to expand...
Click to collapse
Is it saying that it couldn't install the drivers for Android 1.0 or something like that? What step are you at? Which tutorial are you using?
Read the driver installation part of this tutorial.
http://forum.xda-developers.com/showthread.php?t=1392310

i got it. it was this
TO GET DRIVER WORKING IN BOOTLOADER YOU MIGHT HAVE TO DO THIS, THIS TOOK ME FOREVER TO FIND!!!!!!!!!!!
I TAKE NO CREDIT!
READ CAREFULLY
THANKS TO KELLEX FROM DROIDLIFE
Tips:
-We know that many of you are running into a “waiting for device” issue when apply the fastboot oem unlock command. This is a driver issue and one that a reader has a suggestion for:
1. Open device manager on your PC.
2. Right click on Android 1.0 with the yellow ! mark on it.
3. Choose update driver.
4. Choose browse my computer.
5. Choose Let me pick from a list.
6. Scroll down and find the Samsung driver with newest date. Should be the driver you downloaded above. (Possibly dated 11/25/2011 ).
7. It will give you a warning about installing the driver, just click yes.

[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

fastboot mode not working

hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers

WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.

Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie

WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/

Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse

[Q] adb driver not working

I've been trying to access my GNex in fastboot mode, but my computer doesn't recognize it when it is in fastboot. I have tried to install the samsung adb drivers, but not matter what I try, I cannot get my computer to connect using the adb when the device is in fastboot. Any help would be appreciated.
I am running window 7 x64 btw.
EDIT: When my device is connected and I am not in fastboot mode, i am getting the "SAMSUNG Android ADB Interface" listed in device manager. So I am assuming I have the driver installed correctly.
EDIT 2: When I use
Code:
adb reboot bootloader
the device goes from recognized to Android 1.0, and if I try to
Code:
fastboot oem unlock
I get
Code:
<waiting for device>

rbmako69 said:
I've been trying to access my GNex in fastboot mode, but my computer doesn't recognize it when it is in fastboot. I have tried to install the samsung adb drivers, but not matter what I try, I cannot get my computer to connect using the adb when the device is in fastboot. Any help would be appreciated.
I am running window 7 x64 btw.
EDIT: When my device is connected and I am not in fastboot mode, i am getting the "SAMSUNG Android ADB Interface" listed in device manager. So I am assuming I have the driver installed correctly.
EDIT 2: When I use
Code:
adb reboot bootloader
the device goes from recognized to Android 1.0, and if I try to
Code:
fastboot oem unlock
I get
Code:
<waiting for device>
Click to expand...
Click to collapse
After 'adb reboot bootloader', and device being recognized as "Android 1.0", just manually update the driver: its the same driver that you used for adb. Windows is dumb.
Use search or browse the forums, read the stickies, this has been covered over and over again.
Sent from my i9250

If all else fails get mskips galaxy nexus toolkit v10.x, see xda thread or google skipsoft, and let it sort out drivers and adb, it has easy options and a good help section, should get the job done.
Btw if you are having driver issues you should try the driver download pack from samsung official website's manuals and downloads, its a tad under 30mb, run it then reboot computer then plug in gnex and any missing drivers should auto install, be patient, windows is a retard so it may take a coupla minutes
sent via xda premium from starkissed noozxoide maguro gnex paranoid beta9.5

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.
It's basically what bk201doesntexist said in the above post. I used the pdanet driver, but I'm sure the normal Samsung driver should work.

[Q] Nexus 7 2013 ADB sideload problem

Ok guys here is my problem :
I install Nexus 7 on my laptop. Download latest SDK, install tools and everything. After that I download USB drivers from XDA tutorials for ADB. Also, download OTA update from 4.3 to 4.4 (283mb) and prepare everything for adb sideload.
After debagging, entering the Recovery I select "update from adb" and then my problem starts. Until that point I could see my nexus in cmd (adb devices) after entering in "update from adb" I just hear 2-3 bip-bip sounds on my laptop (like when you put external hdd that has broken cable and dont recive power). When I try to see device entering "adb devices" i get no devices. After restarting Nexus everything is OK and I see nexus in adb devices (cmd)
What's wrong? Where I do wrong?
Tnx

Nemesis_GNex said:
Ok guys here is my problem :
I install Nexus 7 on my laptop. Download latest SDK, install tools and everything. After that I download USB drivers from XDA tutorials for ADB. Also, download OTA update from 4.3 to 4.4 (283mb) and prepare everything for adb sideload.
After debagging, entering the Recovery I select "update from adb" and then my problem starts. Until that point I could see my nexus in cmd (adb devices) after entering in "update from adb" I just hear 2-3 bip-bip sounds on my laptop (like when you put external hdd that has broken cable and dont recive power). When I try to see device entering "adb devices" i get no devices. After restarting Nexus everything is OK and I see nexus in adb devices (cmd)
What's wrong? Where I do wrong?
Tnx
Click to expand...
Click to collapse
You need different drivers for adb to work in recovery. Search for universal adb drivers.

How you mean "universal"? Is there some link or...?
Sent from my Nexus 4 using Tapatalk 2

Nemesis_GNex said:
How you mean "universal"? Is there some link or...?
Click to expand...
Click to collapse
To make a long story short, the USB IDs that the tablet presents when in Recovery mode are different than Android. The standard drivers from Google only recognize the device when in Android.
Universal driver (and also naked driver) add the missing USB IDs so your device gets recognized.
http://forum.xda-developers.com/showthread.php?t=1161769