Hey guys, I'm trying to root my girlfreind's verizon galaxy nexus and I can't even get past the first step of unlocking the bootloader! I've tried using the Nexus all in one tool kit without much success. The script reboots the phone into the bootloader screen but then the script hangs at "waiting for device". And nothing happens after that. Any ideas or suggestions would be greatly appreciated!
Here's some additional info on the phone:
Android version 4.1.1
Build number JRO030O
Sounds like you need to install the proper drivers.
Try doing it the real way.
Setup adb/fastboot then
fastboot oem unlock
Approve and it's done.
Hmm...tried doing manually and didn't have any luck. I'm guessing I'm leaving something out. I ran "adb devices" and it shows the phone. Then I type "fastboot oem unlock" and it stalls. The screen sits at "waiting for device". Any suggestions?
Also, can anyone post a link to the most recent drivers for this phone using a windows XP computer?
Any help is greatly appreciated!!
Thanks,
Eric
follow this: http://forum.xda-developers.com/showthread.php?t=1529058
start at the top and do not skip any steps.
scheirere said:
Hmm...tried doing manually and didn't have any luck. I'm guessing I'm leaving something out. I ran "adb devices" and it shows the phone. Then I type "fastboot oem unlock" and it stalls. The screen sits at "waiting for device". Any suggestions?
Also, can anyone post a link to the most recent drivers for this phone using a windows XP computer?
Any help is greatly appreciated!!
Thanks,
Eric
Click to expand...
Click to collapse
ADB is only used in custom recovery or booted into OS
Fastboot is used in fastboot/bootloader only
you dont interchange them. fastboot oem unlock only works when the device is in fastboot/sitting in bootloader
Thanks a bunch guys. I really appreciate the help.
I went thru the steps in the link Zepius suggested again and discovered the problem. As suggested in the directions, I had to go into device manager and update/install drivers for the USB interface manually. Took me a bit to figure this out as I'm pretty new to this stuff, but I found the drivers and got that fixed. After that the "fastboot oem unlock" command worked and I unlocked the bootloader. Now on to the next roadblock....
Again, many thanks. That was really frustrating.
Eric
Related
Hello friends,
How to get into fastboot to relock the bootloader, if my volume button is dead? By dead, I mean the ribbon has been ripped off of the mobo (it was soldered onto mobo).
Since I'm a brand-new noob, the only way I know of and have done is to get into fastboot mode and lock it back up like what I did when I unlocked it. Any other way to lock it, ideally within the Android OS? Since my volume buttons are completely dead, I doubt that I can get into any "mode" other than OS right now..
TIA!
adb reboot bootloader.
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
I would say doing whatever ripped the volume button cable out was what you shouldn't have been doing If you unlocked the phone you have the software you used to unlock, right? What software/guide did you use/follow? Are you using Windows/Linux/Mac? The only way to get to the bootloader w/o the volume buttons (afaik) is to use adb via usb. If you provide more details I can try to help you.
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure?
Click to expand...
Click to collapse
Once you're in adb reboot bootloader, do fastboot oem lock. Opposite of how you unlocked it in the first place
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
Click to expand...
Click to collapse
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
Click to expand...
Click to collapse
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Thanks for your help guys!
btw, anyone found xdadevelopers to load extremely slower in Firefox when compared to Chrome? (just offtopic)
Anyway, I unlocked the bootloader when I was switching to yakju cmd and this folder called "fastboot-and-adb" in which there is both adb.exe and fastboot.exe. I used command "fastboot unlock bootloader" or something alike.
I'll do some more search and learn. Don't want you guys to think of me as a lazy bone who unlocked their bootloader using 1-click toolkit
p.s. edit: in my other thread, someone suggested using quickboot app.
Thanks for your replies guys!
martonikaj said:
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Click to expand...
Click to collapse
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Try adb remount
The ad devices
This should list the serial number
Then all commands should work
Sent from my Galaxy Nexus using xda premium
cswithxda said:
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Click to expand...
Click to collapse
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Thanks for the help at late night guys. I finally got into the bootloader, thru a mac tho Kinda ironic that I am a supporter of Windows, well, at least a firm user of Windows.
Tried adb remount, it still says device not found
synaesthetic said:
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Click to expand...
Click to collapse
I believe that you quoted my "I have turned USB debug on" ;p
Gave up on trying Windows drivers. When I was flashing the Yakju, I tried Samsung full driver, and it didn't work on my machine, i.e., the phone can't be detected in bootloader mode, while the beta 0.5 driver worked. So I decided not to mess with it anymore.
It looks like when the phone is not under bootloader, windows recognize it fine as MTP devices and install proper samsung driver from the internet directly. This allows me to open it up in explorer to browse files and such, but the phone won't show up under adb devices somehow.
Looks like MTP device (when the phone is in Android OS) and the fastboot mode use two kinds of drivers. This is just my assumption, though.
Anyway, finally got into bootloader now with Mac, and it's pretty funny I have to do everything thru command as the volume rockers are dead
And most importantly, thank you guys for your help!
Just another update
It's real funny now that the bootloader is locked, I can't unlock it again cuz I don't have the volume button working, so I couldn't choose YES on the phone.
I'm not trying to unlock it again, but just to confirm if there's really no work around, in case I encounter this situation again in the future
Lucky that locking the bootloader won't erase everything, or I won't be able to flash a ROM with it locked... :cold sweating:
Hey guys,
I followed this thread to unlock boot loader (http://forum.xda-developers.com/showthread.php?t=2694600), used the automated way to install adb drivers and did everything like the post says, but when I boot into bootloader and connect to my pc, when I type an adb command to get the code, it just stays at waiting for device for ages...
What I'm doing wrong? I even updated to the last api of adb, which are on the automated post (http://forum.xda-developers.com/showthread.php?t=2588979), posted by an user.
Can anyone help me please?
Thanks in advance!
You don't use ADB at the bootloader, you use fastboot. ADB is only when Android is running
Hgneto said:
Hey guys,
I followed this thread to unlock boot loader (http://forum.xda-developers.com/showthread.php?t=2694600), used the automated way to install adb drivers and did everything like the post says, but when I boot into bootloader and connect to my pc, when I type an adb command to get the code, it just stays at waiting for device for ages...
What I'm doing wrong? I even updated to the last api of adb, which are on the automated post (http://forum.xda-developers.com/showthread.php?t=2588979), posted by an user.
Can anyone help me please?
Thanks in advance!
Click to expand...
Click to collapse
This method does not require you to boot into bootloader. It does require S-off, however. Notice the instructions only tell you to boot into bootloader as the last step, simply to verify the unlock was successful.
Confused...
What? I don't know what to next then... I installed the automated way drivers, installed HTC connect program and allowed the connection via usb in developer options... What shall I do next to unlock boot loader?
For what I see on the VomerGuide it says after:
"Enter Fastboot (bootloader) Mode" ... now you are telling me that I do not need to...
When I enter in this Fastboot Mode, I connect the device to pc and then say the command to get the code, but it says waiting for device for ages and doesn't give me the code... Can you explain me what I'm doing wrong/what shall I do next?
Thanks in advance!
Hgneto said:
What? I don't know what to next then... I installed the automated way drivers, installed HTC connect program and allowed the connection via usb in developer options... What shall I do next to unlock boot loader?
For what I see on the VomerGuide it says after:
"Enter Fastboot (bootloader) Mode" ... now you are telling me that I do not need to...
When I enter in this Fastboot Mode, I connect the device to pc and then say the command to get the code, but it says waiting for device for ages and doesn't give me the code... Can you explain me what I'm doing wrong/what shall I do next?
Thanks in advance!
Click to expand...
Click to collapse
Make sure "usb debugging is enabled" on your phone, then cmd "adb devices" on PC and it should return your phonr serial number.
Will try that.
BTW, shall I enter in bootloader and then connect to PC, or do the other way around?
Thanks!
Sent from my G3
Hgneto said:
What? I don't know what to next then... I installed the automated way drivers, installed HTC connect program and allowed the connection via usb in developer options... What shall I do next to unlock boot loader?
For what I see on the VomerGuide it says after:
"Enter Fastboot (bootloader) Mode" ... now you are telling me that I do not need to...
When I enter in this Fastboot Mode, I connect the device to pc and then say the command to get the code, but it says waiting for device for ages and doesn't give me the code... Can you explain me what I'm doing wrong/what shall I do next?
Thanks in advance!
Click to expand...
Click to collapse
My apologies. I was looking under a different page from the link you provided. If you are following VomerGide, yes you do start in fastboot.
Try this first, though. Make sure USB debugging is enabled, leave phone on (not fastboot), plug it into your computer, and cmd "adb devices". If a message comes up on phone screen to allow computer connection, choose to always allow. Once you have gotten adb to recognize device, you can cmd "adb reboot bootloader" and phone should reboot into bootloader. In bootloader screen on phone, you might have to select fastboot mode. Then try to cmd "fastboot devices" and see if it brings up you device info. If so, you are good to go!
Trying to unlock my bootloader and I'm having the dreaded problem of adb, fastboot and google usb drivers not working.
Tried the idiotic Sony documented way of installing Android SDK and development tools, tried 15 Second ADB, Flashtool and Minimal ADB installers - after doing all three of these and then running Flashtool it informs me that drivers need to be installed for the device.
Running "fastboot devices" results in no message at all, running "fastboot device" results in a "waiting for device" message.
Any ideas please?
diji1 said:
Trying to unlock my bootloader and I'm having the dreaded problem of adb, fastboot and google usb drivers not working.
Tried the idiotic Sony documented way of installing Android SDK and development tools, tried 15 Second ADB, Flashtool and Minimal ADB installers - after doing all three of these and then running Flashtool it informs me that drivers need to be installed for the device.
Running "fastboot devices" results in no message at all, running "fastboot device" results in a "waiting for device" message.
Any ideas please?
Click to expand...
Click to collapse
Do a search on how to install unsigned drivers on windows 10, that should fix your problem
Cheers that fixed it although using BCEDIT didn't I had to use the restart method.
diji1 said:
Cheers that fixed it although using BCEDIT didn't I had to use the restart method.
Click to expand...
Click to collapse
Cool
Now don't forget to backup your TA partition before unlocking your bootloader...
Happy rooting
I need a little help. I tried to unlock and root my phone. I was on build NDE63X. I was able to unlock the device no problem, but then ran into some issue with the root. I'm not sure what happened. Now I am stuck in bootloop.
I am trying to sideload the OTA NDE63X through ADB. However, adb isn't recognizing my device. If I type "fastboot devices" then it pulls up my device. I have tried to uninstall my drivers and reinstall the drivers and every time the driver says "Android Bootloader Interface". I don't know if that is the problem or not. Any help would be appreciated.
Thanks!
charr83 said:
I need a little help. I tried to unlock and root my phone. I was on build NDE63X. I was able to unlock the device no problem, but then ran into some issue with the root. I'm not sure what happened. Now I am stuck in bootloop.
I am trying to sideload the OTA NDE63X through ADB. However, adb isn't recognizing my device. If I type "fastboot devices" then it pulls up my device. I have tried to uninstall my drivers and reinstall the drivers and every time the driver says "Android Bootloader Interface". I don't know if that is the problem or not. Any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
unplug the phone
switch off the phone
press power + volume down
does it go in Fastboot mode ?
So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Make sure that the drivers are installed properly from the SDK. Installing the SDK is not enough. Look in device manager and look for a yellow symbol with exclamation mark next to any Android device. Right click and get to select driver and point to "Google usb driver" that you extracted from the SDK then select either bootloader or ADB driver depending on what mode your phone is in when doing the above. It should then work. Sorry if that is not clear I am doing it from memory and I am not at my computer. Good luck!
smartway4me said:
So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Click to expand...
Click to collapse
Try "fastboot devices" instead that will tell you of it's correct or not too
smartway4me said:
So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Click to expand...
Click to collapse
Did you enable ADB debugging in Developer Options yet?
That must be done when plugging phone into your computer while the phone is booted up.