Related
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
I have spent 2 days trying to unlock my new Nexus 7 HD. I'm not a noob, my last 7 phones I have rooted, flashed, unlocked and messed around with, my last 3 tablets I've unlocked and rooted including my 2012 Nexus 7.
Everytime I try to unlock it says fastboot not found. I'm using Nexus Root Toolkit 1.7.1. I can boot into the bootloader using the toolkit, and when it's in bootloader mode, I can also reboot the bootloader using the toolkit. When I click unlock, i get the fastboot device no found. When the Nexus 7 is turned on, my device manager shows "Android Composite ADB device" when the Nexus is in bootloader mode my devices show "Android bootload interface" USB debugging is enabled which don't effect fastboot anyways.
I've tried all 4 of my USB ports, I've followed the driver instructions to a "T", I've uninstalled all the
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- or ANYTHING else you see that resembles your Nexus.
budco2000 said:
I have spent 2 days trying to unlock my new Nexus 7 HD. I'm not a noob, my last 7 phones I have rooted, flashed, unlocked and messed around with, my last 3 tablets I've unlocked and rooted including my 2012 Nexus 7.
Everytime I try to unlock it says fastboot not found. I'm using Nexus Root Toolkit 1.7.1. I can boot into the bootloader using the toolkit, and when it's in bootloader mode, I can also reboot the bootloader using the toolkit. When I click unlock, i get the fastboot device no found. When the Nexus 7 is turned on, my device manager shows "Android Composite ADB device" when the Nexus is in bootloader mode my devices show "Android bootload interface" USB debugging is enabled which don't effect fastboot anyways.
I've tried all 4 of my USB ports, I've followed the driver instructions to a "T", I've uninstalled all the
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- or ANYTHING else you see that resembles your Nexus.
Click to expand...
Click to collapse
Is the fastboot command not found or the device is the one not found? Unlocking the bootloader is very easy using fastboot. I've never run any of the toolkits.
Once the device is connected to your computer and in bootloader mode (vol+down and power), you should get the device id returned if you run "fastboot devices". Then it is a simply matter of just running "fastboot oem unlock", use the vol to scroll to yes, and press the power to select. That is pretty much there is to it.
cowabunga said:
Is the fastboot command not found or the device is the one not found? Unlocking the bootloader is very easy using fastboot. I've never run any of the toolkits.
Once the device is connected to your computer and in bootloader mode (vol+down and power), you should get the device id returned if you run "fastboot devices". Then it is a simply matter of just running "fastboot oem unlock", use the vol to scroll to yes, and press the power to select. That is pretty much there is to it.
Click to expand...
Click to collapse
It says fastboot device not found. I know this is a driver issue, and I've tried different drivers. I unlocked my 2012 nexus 7 in under 3 minutes, but this is not going to smoothy lol
budco2000 said:
It says fastboot device not found. I know this is a driver issue, and I've tried different drivers. I unlocked my 2012 nexus 7 in under 3 minutes, but this is not going to smoothy lol
Click to expand...
Click to collapse
And you are booted to the bootloader, right?
I use a mac. No crazy drivers to deal with. Just plug and go.
cowabunga said:
And you are booted to the bootloader, right?
I use a mac. No crazy drivers to deal with. Just plug and go.
Click to expand...
Click to collapse
I got my bootloader unlocked. Now I can't root it. I downloaded like 3 toolkits, all of them are failing. I've never had so many problems with one device as this one. Wug's toolkit didn't see the device in bootloader, but N-cry toolkit had no problem seeing the device in bootloader mode, which unlocked bootloader, but it wont flash recovery or root. Wug's tool kit will push the files for recovery and root, but then when the Nexus goes into bootloader wug's toolkit fails because it don't see the device in bootloader mode. The quick root tool doesn't do anything at all. The problem here is I'm using windows 8 and I just read that android SDK drivers have to be manually installed, but even that is giving me problems. I have a bad ass laptop, A dell alienware that's never gave me a problem. It came with windows 7, and i put windows 8 on it about 8 months ago, thinking about running the restore CD's and downgrading back to windows 7. ADB commands aren't responding from a command promt. I just want root, and its being a real pain in the ass.
budco2000 said:
I got my bootloader unlocked. Now I can't root it. I downloaded like 3 toolkits, all of them are failing. I've never had so many problems with one device as this one. Wug's toolkit didn't see the device in bootloader, but N-cry toolkit had no problem seeing the device in bootloader mode, which unlocked bootloader, but it wont flash recovery or root. Wug's tool kit will push the files for recovery and root, but then when the Nexus goes into bootloader wug's toolkit fails because it don't see the device in bootloader mode. The quick root tool doesn't do anything at all. The problem here is I'm using windows 8 and I just read that android SDK drivers have to be manually installed, but even that is giving me problems. I have a bad ass laptop, A dell alienware that's never gave me a problem. It came with windows 7, and i put windows 8 on it about 8 months ago, thinking about running the restore CD's and downgrading back to windows 7. ADB commands aren't responding from a command promt. I just want root, and its being a real pain in the ass.
Click to expand...
Click to collapse
Now that I think about it, I don't think I had to even deal with installing a root. I installed twrp2 for recovery and it automatically detected that I did not have root as I was rebooting and it prompted me if I wanted to install root. I remember select yes and after it rebooted, I had root.
Make sure you enable root access for "Apps and ADB" in developer options. You may find you already have root.
cowabunga said:
Now that I think about it, I don't think I had to even deal with installing a root. I installed twrp2 for recovery and it automatically detected that I did not have root as I was rebooting and it prompted me if I wanted to install root. I remember select yes and after it rebooted, I had root.
Make sure you enable root access for "Apps and ADB" in developer options. You may find you already have root.
Click to expand...
Click to collapse
I got it. I ended up using the rootkit for the 2012 nexus 7, i remembered it had an option to push image files, I push the recovery file, then flashed super user. all is good
Hi everyone !
I am pretty new here, therefore please forgive me if I have chosen wrong subject.
I have got a problem with Nexus 5x with Android8 OPR6 (Oreo), BHZ21d, the USB debugging is enabled, OEM lockdown. Moreover, I have ADB drivers installed. When connected to a PC, the phone is detected and when it enters the bootloader mode, the computer does not see it.
What I want to do is unlock it and go to Android 7.1
Maybe someone has such a case and knows how to solve this problem?
I would appreciate any help
PS. I tried the Nexus Tool and CMD and unfortunately can not get it.
If you boot regularly, connect phone with pc and enter fastboot devices: is your device listed?
i have a pixel xl unlocked not VZW and oem is checked blue enabled but cant unlock BL using all three commands fastboot oem unlock,fastboot flashing unlock and the critical command. Please help. Buyer code uxm and Google open 64
Just to be sure, you also enabled "USB debugging" as well, right?
Have you visited this 2 XLGuide?
Also there are further detailed platform tools steps in the 2 XL link in my sig.
Good luck!
USB enabled yes
Are your SDK Tools the latest version?
Have you tried multiple USB cables 2.0, 3.0, etc.
Do you get a serial number response when typing - fastboot devices
Have you tried multiple USB ports?
If your device is capable of having the bootloader unlocked, both the OP guide and my step by step guide have always worked on the 2 XL.
There is likely an issue with your adb or fastboot commands, or where the fastboot application folder is located.
I got BL unlocked and tried flash all but said error failed to load not enough space?
I got it ty for all your help
Phone is detected by "adb devices" but not detected by "fastboot devices"
I purchased a used P3a XL from Swappa. I would like to install a custom ROM. As we all know, in order for me to do that I need to unlock the bootloader. I think the phone is a Google Edition (checked SKU on box against what is sold in stores).
I have done quite a bit of research before posting here and think I have the process correct. I have enabled developer mode and toggled the OEM unlock option. I am able to "adb devices" and see the phone on my computer terminal. I "adb reboot bootloader" and the phone reboots in to "Fastboot Mode". When I do "fastboot devices" nothing shows. When I boot in to fastbootd (via stock recovery) and execute "fastboot devices" I can see the phone. I execute "fastboot flashing unlock" and it fails with "fastboot flashing unlock failed remote: unrecognized command flashing unlock".
I have tried this on my PixelBook with Linux installed and on my Ubuntu lab machine. Both of those machines give me the same results. I tried with my Windows 10 laptop, but the phone isn't detected by any of my USB-C to USB-A cables.
I have factory wiped the phone a few times and attempted the steps above, but it results in the same thing. Phone is not detected in fastboot. Interestingly, I am able to sideload the latest OTA (QQ3A.200605.001, Jun 2020) without any errors. After sideloading the latest OTA, I am still unable to unlock the bootloader.
I suspect one of two things:
1. The phone is a VZW/Sprint/T-Mo edition. Even so, VZW edition can be unlocked. I tried that method (found an XDA thread to do that).
2. Something is wonky with the phone (bootloader software)
Unfortunately, since I bought it second hand, I do not think Google would honor the hardware warranty to issue me an RMA.
What do you folks think may be an issue?
ruhrohs said:
I purchased a used P3a XL from Swappa. I would like to install a custom ROM. As we all know, in order for me to do that I need to unlock the bootloader. I think the phone is a Google Edition (checked SKU on box against what is sold in stores).
I have done quite a bit of research before posting here and think I have the process correct. I have enabled developer mode and toggled the OEM unlock option. I am able to "adb devices" and see the phone on my computer terminal. I "adb reboot bootloader" and the phone reboots in to "Fastboot Mode". When I do "fastboot devices" nothing shows. When I boot in to fastbootd (via stock recovery) and execute "fastboot devices" I can see the phone. I execute "fastboot flashing unlock" and it fails with "fastboot flashing unlock failed remote: unrecognized command flashing unlock".
I have tried this on my PixelBook with Linux installed and on my Ubuntu lab machine. Both of those machines give me the same results. I tried with my Windows 10 laptop, but the phone isn't detected by any of my USB-C to USB-A cables.
I have factory wiped the phone a few times and attempted the steps above, but it results in the same thing. Phone is not detected in fastboot. Interestingly, I am able to sideload the latest OTA (QQ3A.200605.001, Jun 2020) without any errors. After sideloading the latest OTA, I am still unable to unlock the bootloader.
I suspect one of two things:
1. The phone is a VZW/Sprint/T-Mo edition. Even so, VZW edition can be unlocked. I tried that method (found an XDA thread to do that).
2. Something is wonky with the phone (bootloader software)
Unfortunately, since I bought it second hand, I do not think Google would honor the hardware warranty to issue me an RMA.
What do you folks think may be an issue?
Click to expand...
Click to collapse
Sideloading is an adb function, not fastboot. Make sure you have the lastest Android platform tools. This doesn't mean you can unlock the bootloader but to get fastboot working.
Also make sure you have the oem cable or at least a decent cable, and use a 2.0 port if possible. I've seen other a/b devices refuse to work or give half commands with 3.0+ ports. What does it says underneath oem unlocking in dev settings? I've attached the latest adb/fastboot files just in case you might need them.
Tulsadiver said:
Sideloading is an adb function, not fastboot. Make sure you have the lastest Android platform tools. This doesn't mean you can unlock the bootloader but to get fastboot working.
Click to expand...
Click to collapse
I just updated my Ubuntu machine with the lastest SDK, so both ADB and Fastboot were updated. The phone can be seen with "adb devices". It can be seen with "fastboot devices", but only if the phone is in fastbootd mode. Wouldn't this confirm that fastboot works on the laptop?
41rw4lk said:
Also make sure you have the oem cable or at least a decent cable, and use a 2.0 port if possible. I've seen other a/b devices refuse to work or give half commands with 3.0+ ports. What does it says underneath oem unlocking in dev settings? I've attached the latest adb/fastboot files just in case you might need them.
Click to expand...
Click to collapse
I am using a PixelBook with the original USB-C to USB-C cable that came with the phone. My Windows laptop doesn't see the phone at all
OEM unlock option is enabled.
ruhrohs said:
I just updated my Ubuntu machine with the lastest SDK, so both ADB and Fastboot were updated. The phone can be seen with "adb devices". It can be seen with "fastboot devices", but only if the phone is in fastbootd mode. Wouldn't this confirm that fastboot works on the laptop?
I am using a PixelBook with the original USB-C to USB-C cable that came with the phone. My Windows laptop doesn't see the phone at all
OEM unlock option is enabled.
Click to expand...
Click to collapse
As far as your window laptop, you might try installing usb drivers.
https://developer.android.com/studio/run/win-usb
Tulsadiver said:
As far as your window laptop, you might try installing usb drivers.
https://developer.android.com/studio/run/win-usb
Click to expand...
Click to collapse
Yup, tried that as well. I even went as far as wiping one of my lab machines, installed Windows 7, copied and installed the command line tools only from here: https://developer.android.com/studio#downloads, but no dice. For Windows, I think it's a cable issue. I'm getting new USB-C to USB-A cables delivered tomorrow. Once I get them, I will try on my Windows laptop.
Update to my issue...
Bought a 3 pack of Anker cables. Plugged each of them to my phone and to each of my Win 7 and Win 10 laptops. Both laptops are able to charge the phone, however the don't detect the phone for data transfer/USB debugging. I checked device manager, deleted/uninstalled all Android devices that were listed (including my first generation Pixel XL), rebooted my laptops and tried again. No dice... At this point, I'm chalking it up to the Pixel 3a XL phone itself and an issue with the hardware.
Note to self... Buy a brand new phone for an extra $100 and I would have saved myself over 4 days of troubleshooting an issue.
ruhrohs said:
Update to my issue...
Bought a 3 pack of Anker cables. Plugged each of them to my phone and to each of my Win 7 and Win 10 laptops. Both laptops are able to charge the phone, however the don't detect the phone for data transfer/USB debugging. I checked device manager, deleted/uninstalled all Android devices that were listed (including my first generation Pixel XL), rebooted my laptops and tried again. No dice... At this point, I'm chalking it up to the Pixel 3a XL phone itself and an issue with the hardware.
Note to self... Buy a brand new phone for an extra $100 and I would have saved myself over 4 days of troubleshooting an issue.
Click to expand...
Click to collapse
You do realise that you've got to change the USB settings for it to do data transfer right???
thatsupnow said:
You do realise that you've got to change the USB settings for it to do data transfer right???
Click to expand...
Click to collapse
my problem more than once, ashamed to say. after updating drivers and cords. then forgot to pull my notifications down for that last little line. it's a learning process though. (so they say).
kevinchristopherson said:
my problem more than once, ashamed to say. after updating drivers and cords. then forgot to pull my notifications down for that last little line. it's a learning process though. (so they say).
Click to expand...
Click to collapse
No worries dude even when you change default usb settings it still stays in charging mode
thatsupnow said:
You do realise that you've got to change the USB settings for it to do data transfer right???
Click to expand...
Click to collapse
Yup, I know that I need to change it to data transfer, however the phone isn't detected by either of my Windows laptops. The phone is only detected via ADB on my Chromebook. I can do an "adb reboot bootloader" and it'll accept the command, but "fastboot devices" or "lsusb" shows no devices.
kevinchristopherson said:
my problem more than once, ashamed to say. after updating drivers and cords. then forgot to pull my notifications down for that last little line. it's a learning process though. (so they say).
Click to expand...
Click to collapse
Yup, my first gen Pixel XL will notify me when I pull down the notifications, but the Pixel 3a doesn't.
I ended up setting up the phone and used it for a fewdays. It works fine, however I'm used to running AdAway, AFWall, EX Kernel Manager, Greenify, High Brightness Mode, NapTime, Titanium Backup and Viper4Android. There are workarounds to enable Greenify and NapTime via ADB, but it's a moot point without the other root dependent apps.
Updating this thread to close this out.
Bought a brand new Pixel 3a XL from the Google store. I was able to root without any issues on my Windows 10 laptop. I attempted the same exact process with the same USB port and USB cable for the Pixel 3a XL that I bought from Swappa, but it didn't work. This confirms my educated guess that it's a hardware issue on the phone.
The secondary market may soon be flooded with Pixel 3a XLs once the Pixel 4a is released. Before you get burned on a non-rootable phone, ask the seller how long they have owned the device and check the warranty on it. As of this post, you can check the IMEI Here: hxxps://store.google.com/repair (replace the hxxps with https).
Good luck!
You need to download the google usb driver and update the Pixel 3 driver in Device manager with the usb driver. Then the computer will recognize the phone as a fastboot device while it's in bootloader.
For me what solved this was I wasn't adding the "platform-tools" folder to my path.
I was using "fastboot.exe flashing unlock"
But once I added to path and did "fastboot flashing unlock" it worked like a charm
On Linux, did you try sudo fastboot flashing unlock? This is the only thing that works for me. Sudo before all fastboot commands.
In my case on Ubuntu 20.04, it was a USB 3.0 port problem. It was detect device with fastboot devices but other commands does not has a response. My laptop hasn't got a USB 2.0 port. Then I disabled internal USB 3.0 support in my BIOS and now fastboot is working normally. But all USB 3.0 support is stopped. It seems USB 2.0 hub is the better option. I will set back the BIOS setting later.
Yesterday i bought the G020B version, and the same happened to me while unlocking bootloader, fastboot keeps on <waiting for device> like if the phone was not even connected
I searched for a driver that could work and found this (For windows)
Basically, my system can't detect properly the phone because the driver was not 'updated'. (Even when i can use fastboot on other devices)
Hope it works for you or everyone here.