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...
Related
I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....
I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....
adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.
The title says it all, well most of it. heres the problem:
I want to unlock the bootloader on my Xperia Play, I've tried many different ways to actually get fastboot to detect my phone I installed various drivers for S1 Semcboot but no luck, I also tried installing seus, uninstalling the drivers and letting seus re-install the s1 semcboot drivers but still no luck Ive been at it for a whole day... How can I get fastboot on windows 7 to detect my xperia play which is 100% bootloader unlockable...?
NOTE: The blue power led turns on when I hold search and connect the phone, the computer detects the phone but fastboot doesn't.
I have also tried lollylosts thread for drivers and stuff...
Any help would be appreciated please...
The usb driver file is here
its direct link, should work.
Thankyou but how am I supposed to use that driver?, windows 7 doesnt let me install drivers it only lets me update drivers when i try to update it doesnt install ...
Manny- said:
Thankyou but how am I supposed to use that driver?, windows 7 doesnt let me install drivers it only lets me update drivers when i try to update it doesnt install ...
Click to expand...
Click to collapse
Haven't really used Windows for a while but I think you can uninstall then reinstall drivers through device manager
I know you can, I've tried selecting many drivers by browsing and locating the folders but it just wont install...
Which fastboot command are you using?
Manny- said:
Thankyou but how am I supposed to use that driver?, windows 7 doesnt let me install drivers it only lets me update drivers when i try to update it doesnt install ...
Click to expand...
Click to collapse
I tried it, my device was detected but fastboot didnt pick the device up its driving my nuts I have no idea what I'm doing wrong
@Michealtbh
I tried this: fastboot.exe -i 0x0fce getvar version and also this: fastboot.exe devices, they dont work
http://forum.xda-developers.com/showthread.php?p=23692459
Maybe the files linked in this thread will help you, worth a shot.
Sent from my R800i using XDA
Thanks but made no difference, windows 7 detects the device but fastboot doesn't. :/
ch3mn3y said:
The usb driver file is here
its direct link, should work.
Click to expand...
Click to collapse
I still dont get how to install this driver...
Correct me if I'm wrong but I think you manually point to the drivers when your computer says that it doesn't recognise the device. Can't really remember how I installed them lol.
Sent from my R800i using XDA
Manny- said:
Thanks but made no difference, windows 7 detects the device but fastboot doesn't. :/
Click to expand...
Click to collapse
maybe you are using an outdated version of fastboot.exe? Have you tried pressing back key on boot or the volume down key? Have you seen your LED indicator turn or blink blue? Have you used tools or apps that can boot you into fastboot mode? are you rooted already? Have you tried following the Sony Ericsson guide on unlocking bootloader? If you followed this correctly especially downloading the right JAVA and latest Android SDK which includes the ADB drivers, then there will be no problems. Rooting and unlocking bootloader is the easiest part in my opinion when modding your Xplay. The hardest part for me was recovering from an almost bricked phone
http://unlockbootloader.sonymobile.com/
anbu187 said:
maybe you are using an outdated version of fastboot.exe? Have you tried pressing back key on boot or the volume down key? Have you seen your LED indicator turn or blink blue? Have you used tools or apps that can boot you into fastboot mode? are you rooted already? Have you tried following the Sony Ericsson guide on unlocking bootloader? If you followed this correctly especially downloading the right JAVA and latest Android SDK which includes the ADB drivers, then there will be no problems. Rooting and unlocking bootloader is the easiest part in my opinion when modding your Xplay. The hardest part for me was recovering from an almost bricked phone
http://unlockbootloader.sonymobile.com/
Click to expand...
Click to collapse
I tried the latest version and others...[1] Yes, I have tried pressing them everythings works as normal.. [2] Yes the LED turns blue doesnt blink though [3] No I havent tried any maybe you could point me in the right direction? [4] The device is rooted, yes [5] Yes I have followed the guide.. [6] and I have installed java and adb and drivers but its on another drive..
Manny- said:
I tried the latest version and others...[1] Yes, I have tried pressing them everythings works as normal.. [2] Yes the LED turns blue doesnt blink though [3] No I havent tried any maybe you could point me in the right direction? [4] The device is rooted, yes [5] Yes I have followed the guide.. [6] and I have installed java and adb and drivers but its on another drive..
Click to expand...
Click to collapse
check device manager in control panel and check if ADB driver is showing if not, try reinstalling those java and adroid sdk packages again in C:\
btw latest version puts fastboot.exe in android-platform tools folder
If you are still having trouble installing the fastboot drivers and you are using Windows 7 64bit, try the following link: http://forum.xda-developers.com/showthread.php?t=1554805
I had the same problem, but I could fix it by simply adding some lines into the .inf-file.
yesterday i had the same problem hen i tried to boot doomkernel v11. I use this drivers:
http://www.mediafire.com/?1jqvtofgc13figr
and it works (for me)
Thankyou everyone for your help, I will give what you all said a go and will report back here if it worked or not
oh btw @janitory Im using x32 (x86)
EDIT: also I get this error when Im installing the SDK on C:/ "Stopping ADB server failed (code -1)." does that make a difference?
hey guys having the same problem here i have xperia play screen stopped responding on sunday
i tried repairing via the sony tool got modified software error spent most of yesterday dismantling the phone putting back together reinstalling stock firmware turned out i needed to delete the bootloader key to repair done that via blagus and flash tool repaired phone but no joy
turn on phone today and its working again but now i need to unlock the bootloader again ive done all the steps on the sony site but at the getver part it just shows waiting for phone so im stuck at the moment unless one of you guys can help im on win7 32bit also but was able to use fast boot to flash custom kernels etc before today
---------- Post added at 06:57 PM ---------- Previous post was at 06:35 PM ----------
i uninstalled the phone in device manager it gave me the option to delete the driver file too i did this reconected the phone it installed and worked first time
Still no luck guys, anyone got a link to a full step by step guide to unlock the bootloader on xperia play using windows 7 x32 (x86) because I'm almost fed up of this
EDIT: Ive deleted the drivers installed loads of other drivers i.e. .inf or whatever files lol still nothing ... I mean what on earth could I be doing wrong
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
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...
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?