Develop Bugs

[Q] Galaxy Nexus Bootloader Unlock [HELP]

Hi all, Purchased my Galaxy Nexus today - First thing on the list; Unlock and Root.
I have downloaded all of the necessary files but cmd is stuck on < waiting for device >
My phone is in fastboot mode but i cannot get this command to work to unlock the bootloader - I have installed the Samsung drivers... Is there anything I am missing here?
Any help or suggestions welcome, Thanks!

Try with a different USB cable if you can.
I had the same issue (device not being found) using the cable that came with it, so I swapped it for the one that came with my Desire and it worked fine.
Worth a shot.

Cheers! I'll give it a try!

Just tried my original Nexus One USB cable but no luck - I'm thinking it could be something to do with the drivers?

lexarjump said:
Hi all, Purchased my Galaxy Nexus today - First thing on the list; Unlock and Root.
I have downloaded all of the necessary files but cmd is stuck on < waiting for device >
My phone is in fastboot mode but i cannot get this command to work to unlock the bootloader - I have installed the Samsung drivers... Is there anything I am missing here?
Any help or suggestions welcome, Thanks!
Click to expand...
Click to collapse
If you run "fastboot devices" and there's nothing found, then you need to install the fastboot drivers (these are not the same as the USB debug drivers from the zip).
I've found the easiest way to get the drivers is to install pdanet - as part of the installation process you install all needed drivers. You can then uninstall pdanet (or in my case, have the installer crash), leaving just the fastboot driver for you to carry on your rooting

lexarjump said:
Just tried my original Nexus One USB cable but no luck - I'm thinking it could be something to do with the drivers?
Click to expand...
Click to collapse
mybe, you can try fastboot devices and check if the device is found.

Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers

braingravyuk said:
Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers
Click to expand...
Click to collapse
Honestly, not willing to check this one after spending today setting up my device, and no custom recovery available yet.
But given it's a Nexus device, and noting the ease with which we can unlock, then I'd say it's a pretty surefire bet that relocking will be just as easy.

Thanks alot! It worked

I'm looking to just unlock the bootloader of my Galaxy Nexus which will hopefully arrive tomorrow morning. I currently have AndroidSDK and samsung drivers both installed on my pc as well as a file called fastboot.exe. my question is do I need both the Samsung Drivers as well as AndoidSDK installed for this?

rock7632 said:
I'm looking to just unlock the bootloader of my Galaxy Nexus which will hopefully arrive tomorrow morning. I currently have AndroidSDK and samsung drivers both installed on my pc as well as a file called fastboot.exe. my question is do I need both the Samsung Drivers as well as AndoidSDK installed for this?
Click to expand...
Click to collapse
I think PDAnet should be sufficient

Proyoyo said:
I think PDAnet should be sufficient
Click to expand...
Click to collapse
okay thanks

I tried all day yesterday to unlock bootloader with no success. I installed the latest sasmsung usb drivers for mobile (released on 31/10/2011). This allowed the PC to recognise the phone installing the drivers properly. But then starting the phone in recovery mode (power+up+down bottons) I get the android 1 not recognised in device manager.
I then saw this thread and decided to install pdanet 3.02 client on the pc. I couldn't complete that step as pdanet cannot see the phone.
I gave up in the end. If you manage to do it successfully could you please tell me the step you did?
I am going to try tonight on my mac as apparently on mac you do not have this drivers issue. Will post with my results.
---------- Post added at 10:41 AM ---------- Previous post was at 10:34 AM ----------
By the way the latest samsung usb drivers can be found here:
http://forum.xda-developers.com/showthread.php?t=961956
---------- Post added at 11:39 AM ---------- Previous post was at 10:41 AM ----------
Forget my previous post.
Installing pdanet and saying no to install the usb drivers (as part of pdanet install) everything should be fine.
Done mine and working fine.
Thanks.

braingravyuk said:
Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers
Click to expand...
Click to collapse
yes
fastboot oem lock will lock it

Hey I seem to be having some troubles as well,
windows 7 recognizes it as an ADB device and when I use - adb reboot bootloader
it takes me to the fastboot screen that it should.
but once I'm there it doesn't recognize any fastboot devices.
And yes I have reinstalled the SDK, Samsung drivers, and Android ADB driver
Would it matter that I had previously done a bunch of messing around with my ASUS transformer on this computer?
under device manager it says:
ASUS Android Devices - Android ADB Interface
I'm going to try it on another computer tomorrow but I'm curious if that should make a difference.

The driver failed to install on my phone...when I reboot into my bootloader it looks a bit different from in the video. Mine just has an android and it says start above it. The oem unlock command fails to do anything as well.
Why is nothing ever simple?
Does your phone need to be connected when you install the samsung drivers on it? Or does it install these drivers after booting into the bootloader?
When I install the samsung drivers on my computer with the phone connected, it says the following:
Android phone: No drivers found
Samsung Mobile USB Composite Device: Ready to use
Samsung Mobile MTP Device: Failed
Samsung Android ADB Interface: Ready to use
When I hold the volume buttons and power it on now, it just goes straight to the google logo...not even getting the android logo with the start option anymore. I think I might have accidentally uninstalled the ADB drivers in my device manager because I saw 2 copies and thought I installed it twice...

using adb with galaxy nexus

what does our phone have to be in to use adb? ive never used it before but want to to obtain root without unlocking the bootloader and losing my info. is it rebooted in adx mode? just turned on normally? off?
thanks!

You cannot root without unlocking the bootloader! To access adb you need to be in OS and have debugging enabled under Developer options in the settings.

RTContent said:
You cannot root without unlocking the bootloader! To access adb you need to be in OS and have debugging enabled under Developer options in the settings.
Click to expand...
Click to collapse
i was directed here
http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
for a workaround to rooting without unlocking the bootloader

Wow, I must have missed that news. Apologies! Have you tried replying in that thread then?

RTContent said:
Wow, I must have missed that news. Apologies! Have you tried replying in that thread then?
Click to expand...
Click to collapse
you already answered my question to be in the OS with debugging enabled! thanks!

You could re-lock the bootloader though if you ever wish to unroot your phone...

my computer wont allow me to recognize my gnexus using adb. im following these steps - http://droidmodderx.com/galaxynexus/how-to-set-up-the-sdk-for-galaxy-nexus
and i know i have already installed the dirvers previously, but when i use the cmd prompt, my computer does not find my device whatsovever. tried uninstalling it from device manager, but it just reinstalled it when i plugged it in with the MTP drivers already on my computer.
does anyone have any suggestions? i did remember to leave usb debugging on.
thanks!
after rebooting, i tried this in cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Josh Bucher>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
************** offline
C:\Users\Josh Bucher>adb devices
List of devices attached
C:\Users\Josh Bucher>
so it looks like it detected it as offline, then it doesnt. any thoughts? i **ed my phones serial #

ive managed to get the toolkit to install fastboot drivers, but ADB drivers still are not installed and adb does not recognize my phone. fastboot does see it but adb doesnt. ive uninstalled all the drivers and tried the nexus toolkit, pdanet and manual installation but for some reason, i cannot get it to install adb drivers or even recognize that it is an option. does anyone have any suggestions?

joshtb86 said:
ive managed to get the toolkit to install fastboot drivers, but ADB drivers still are not installed and adb does not recognize my phone. fastboot does see it but adb doesnt. ive uninstalled all the drivers and tried the nexus toolkit, pdanet and manual installation but for some reason, i cannot get it to install adb drivers or even recognize that it is an option. does anyone have any suggestions?
Click to expand...
Click to collapse
So there's nothing listed if you input :
adb devices
You are connected via usb with debugging enabled?
Edit: could you also open up device manager in windows and have a look if the device is listed
Sent from my Galaxy Nexus using Tapatalk

RTContent said:
So there's nothing listed if you input :
adb devices
You are connected via usb with debugging enabled?
Edit: could you also open up device manager in windows and have a look if the device is listed
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
usb is enabled.
nothing is listed under ADB, but there is my serial number listed under fastboot. I uninstalled all drivers the toolkit and the SDK. I am going to try the toolkit again now that everything is been uninstalled. The device will be listed in Windows but usually without the ADB driver listed, however the fastboot driver is listed.
now that I tried using the toolkit,
I still had the same problem with no ADB but fastboot was the listed. Then I went to uninstall the drivers through the toolkit and I got an error message saying that they remove failed three times and that no device was removed. However the device still exists under portable devices in the device manager. I am going to uninstall the toolkit after removing the drivers and remove all the drivers from the device manager and then try using just the SDK to route the phone.

after using the toolkit, I am now getting Samsung ADB interface driver installed on my computer. However the toolkit cannot access or realize that ADB is connecting to my phone. I do have USB debuggingenabled. I might try using the SDK to manuallyto connect to it.

fixed the problem. i plugged my phone in directly to the computer instead of through a usb splitter. got it rooted via this post
http://androidforums.com/verizon-ga...oot-un-root-without-unlocking-bootloader.html
thanks for everyoines help! everyone is tahnked!

joshtb86 said:
fixed the problem. i plugged my phone in directly to the computer instead of through a usb splitter. got it rooted via this post
http://androidforums.com/verizon-ga...oot-un-root-without-unlocking-bootloader.html
Glad you got it fixed. If I knew I could have told you the usb hub would have been the problem (they always are)
thanks for everyoines help! everyone is tahnked!
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using Tapatalk

[Q] Use computer to turn phone on?

So short story, my galaxy nexus's power button doesnt work anymore. It stopped working for no reason yesterday, yet when I plug it into the charger the charging screen comese on. I want to be able to power my phone on so that I can get all the information onto my computer so that I can easily transfer stuff to my new phone (replacement gnex coming tomorrow) Is there a way I can turn on my phone without using the power button? Any help would be much appreciated.

If you've got the SDK or just ADB available, you should be able to use the command of "adb reboot" to get the device to boot up. Could be wrong.

Can someone guide me in the direction I need so I can do this adb reboot?

chantheman525 said:
Can someone guide me in the direction I need so I can do this adb reboot?
Click to expand...
Click to collapse
Download the ADB file (usually bundled with Fastboot) from any one of these guides that requires it. Or just Google for it.
Unzip all of that, use command line to get into it's directory, hook your phone up over USB, and type:
Code:
adb reboot
Again, not sure if this will work when the phone is off. If it will work, I think you had to have USB debugging turned on. Its not working for me currently on OSX. So I don't think it will. Maybe there's a different ADB command that can help you.
Its a long shot. There are probably better options.

I'd agree with adb reboot if your computer will recognize it from this mode...
Use the guide linked in my sig to set up ADB if you need.

I'm a newbie to all this, but I don't think anyone here mentioned the necessary step of downloading and installing your phone's specific ADB drivers to your computer.
So, to recap:
Download your phone's ADB drivers on to your computer and install them.
Plug your phone in.
Go to your command prompt and type 'adb reboot'.
I think. I'm new, as you can see by my post count and thanks meter.

I tried to adb reboot. Unfortunately the galaxy nexus cant be recognized when the phone is off. Disappointing but not the end of the world. Thanks for everyones help.

If adb works in download mode you could make a jig to get you there.
Sent from my Galaxy Nexus using Tapatalk

[Q] ADB error device not found

Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance

JT-on said:
Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
Click to expand...
Click to collapse
To use ABD you need to be connected in recovery or a booted device.

nlooooo said:
To use ABD you need to be connected in recovery or a booted device.
Click to expand...
Click to collapse
Brilliant. Like you said, ADB recognized my device in both booted OS and recovery. However, I needed to be in recovery to push files to the system directory. Thanks.

You're welcome. You can push in booted device you just need to enable superuser rights in adb shell.
Sent from my HTC Desire using Flashes and Thunders

JT-on said:
Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance
Click to expand...
Click to collapse
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:

Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?

rmp5s said:
Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?
Click to expand...
Click to collapse
You can't. Both the n4 and the n7 have their memorys formatted as ext4, partition type that windows can't access normally. MTP was the only sollution google had.

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