Good Afternoon,
I took my Pixel C to a CEX store a few months back, just turned it on and they set a PIN and I cannot get it to boot. I tried going into recovery mode to factory reset but get 'no command'. The bootloader is locked and it looks like USB debugging is disabled because I cannot get my computer to recognize it despite having adb/fastboot installed and the Google USB drivers.
Have you any ideas about how I can fix this please? I can get into fastboot mode on the device but cannot get WIndows to recognise it is there.
This is now resolved, I had to add the device ID to android_winusb.inf - fastboot then recognised the device and I could perform a bootloader unlock which in-turn erased the tablet and allowed me back in.
Swatto86 said:
This is now resolved, I had to add the device ID to android_winusb.inf - fastboot then recognised the device and I could perform a bootloader unlock which in-turn erased the tablet and allowed me back in.
Click to expand...
Click to collapse
Hello, please can you tell me how you added the device ID, I have the 64gb variant. And I'm facing similar issues
Related
Hey all,
I've been rooting phones for a little bit, so when I got my Nexus 7 a couple weeks ago and found that it was as simple as "fastboot oem unlock", I was thrilled. However, it ended up not being that simple, of course.
At first I couldn't get the device to show up for ADB or fastboot at all, even though Windows recognized the device. I downloaded the zip file of the drivers from Google, no luck. Downloaded a new version of the Android SDK, and used the adb/fastboot from it, and then ADB was able to see the N7 and was able to reboot it into the bootloader. However, once in the bootloader, it stops recognizing that the N7 is connected again. Trying "fastboot oem unlock" just causes the program to display <waiting for device> indefinitely.
So that's where I'm stuck now, I haven't been able to find any concrete details on this that are for the N7 2013 (pretty much everything I've found has either not been helpful or has been related to the original N7). Anyone able to help from here? Thanks!
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
DowntownJeffBrown said:
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
Click to expand...
Click to collapse
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
tigerxchaos said:
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
Click to expand...
Click to collapse
When you have the device connected to your computer when it's at the Bootloader screen, what does Device Manager show on your computer? Does it recognize the tablet but doesn't know what it is? You may need to install the drivers when you have the device in the Bootloader menu. I use the Google USB Driver (which you can download in the SDK Manager), right click on the device in Device Manager, select "Update Driver Software", "Browse my computer for driver software", "Let me pick from a list of device drivers on my computer", then browse the list. It may be listed under Android Device, Google...just look down the list, then select the appropriate driver. I believe from there you can select "Android Bootloader Interface", and that should let fastboot commands work.
You may need to reboot the computer.
Make sure you are using the usb cable that came from asus.
Thanks for the help. I tried the process again on a different computer, and eventually got it to work. I was able to unlock bootloader and flash TWRP 2.6.3.0. However, I was only able to mount System, Cache, and USB-OTG as partitions in TWRP, so I couldn't figure out where to drop the SuperSU binary .zip file. I tried rebooting, and (this may have been a mistake) installed the TWRP SU binaries on the way out. Now the device is stuck in a bootloop. Not sure if it was related to the SU binaries or the fact that I couldn't load any sort of data partition. Any thoughts?
EDIT: Apparently the root instructions don't make it clear that you will lock your data partition if you don't boot the device after unlocking the bootloader. I went straight into TWRP from the bootloader after unlocking it, and got a password request. Hit "Cancel" and it let me into TWRP, but factory reset failed. I had to wipe data, wipe cache, then reboot, then do a factory reset and now I'm back in.
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Put in fastboot mode, connect to computer and manually select fastboot interface from the device manager "install device/update driver manually" box. That worked for me.
JusTeN_ said:
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Click to expand...
Click to collapse
Its fine just search for fastboot devices and see if your device comes up. Mine was showing the same thing and i continued and it worked
Hey Everyone,
I've posted before but the thread died down and I'd really like to figure this out just for curiosity sake. A couple of months ago I purchased a Moto G Fast as my first root/Custom ROM phone and was never able to get the boot loader unlocked. I have the Android SDK downloaded, the Motorola drivers downloaded, USB debugging enabled, USB mode set to data transfer, etc. However, every time I try to unlock the bootloader the phone is not detected by the Android SDK. My computer detects a device, but does not know what kind of device it is. On the phone itself I never get prompted for a USB connection (from what I understand you usually get a "trusted device" prompt). I've tried this on both Linux (Manjaro) and Windows with the same result (or lack thereof). Also, just to be clear, I am booting the phone into fastboot when trying to unlock the boot loader. Does anyone have any help or suggestions? Also, I'm not sure which ROM to go with. I'd like to run Lineage on the phone but it does not appear that this phone is supported in Lineage 17. Any ROM suggestions as well?
Thank you so much for any suggestions. I appreciate any help that can be offered.
PrettyDumbITGuy said:
Hey Everyone,
I've posted before but the thread died down and I'd really like to figure this out just for curiosity sake. A couple of months ago I purchased a Moto G Fast as my first root/Custom ROM phone and was never able to get the boot loader unlocked. I have the Android SDK downloaded, the Motorola drivers downloaded, USB debugging enabled, USB mode set to data transfer, etc. However, every time I try to unlock the bootloader the phone is not detected by the Android SDK. My computer detects a device, but does not know what kind of device it is. On the phone itself I never get prompted for a USB connection (from what I understand you usually get a "trusted device" prompt). I've tried this on both Linux (Manjaro) and Windows with the same result (or lack thereof). Also, just to be clear, I am booting the phone into fastboot when trying to unlock the boot loader. Does anyone have any help or suggestions? Also, I'm not sure which ROM to go with. I'd like to run Lineage on the phone but it does not appear that this phone is supported in Lineage 17. Any ROM suggestions as well?
Thank you so much for any suggestions. I appreciate any help that can be offered.
Click to expand...
Click to collapse
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
sd_shadow said:
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for pointing me in the right direction. Currently pouring over this info as we speak. At first I was inclined to think that this phone simply could not be unlocked (bought from Amazon marketplace and unlocked for all carriers), but even if that were the case the phone should still at least show up as a device either within my PC device or within the Android SDK command line tools. Perhaps I am wrong?
PrettyDumbITGuy said:
Thank you for pointing me in the right direction. Currently pouring over this info as we speak. At first I was inclined to think that this phone simply could not be unlocked (bought from Amazon marketplace and unlocked for all carriers), but even if that were the case the phone should still at least show up as a device either within my PC device or within the Android SDK command line tools. Perhaps I am wrong?
Click to expand...
Click to collapse
If you are connecting the phone to PC while already in bootloader mode, you don't need USB debugging enabled or USB mode set to data transfer.
There won't be a "trusted device" prompt if device is in bootloader mode.
If windows makes a connecting sound, it will be listed in device manager, if the bootloader screen doesn't show usb connected, that's a problem
Could be a bad usb cable, or bad usb port on the phone.
But none of that may matter, in settings/about phone it should say which software channel it's on something like Amazon, Retail US,
or it may say on the bootloader screen in the baseband or bootloader version.
sd_shadow said:
If you are connecting the phone to PC while already in bootloader mode, you don't need USB debugging enabled or USB mode set to data transfer.
There won't be a "trusted device" prompt if device is in bootloader mode.
If windows makes a connecting sound, it will be listed in device manager, if the bootloader screen doesn't show usb connected, that's a problem
Could be a bad usb cable, or bad usb port on the phone.
But none of that may matter, in settings/about phone it should say which software channel it's on something like Amazon, Retail US,
or it may say on the bootloader screen in the baseband or bootloader version.
Click to expand...
Click to collapse
Software Channel returns as "US Retail" and Software Variant returns as "Retus" (which I think is normal?) Should I turn USB debugging off and the boot into fastboot?
PrettyDumbITGuy said:
Software Channel returns as "US Retail" and Software Variant returns as "Retus" (which I think is normal?) Should I turn USB debugging off and the boot into fastboot?
Click to expand...
Click to collapse
You should be able to unlock US Retail, the usb settings don't matter in bootloader, but it's not in fastbootd is it?
What does the fastboot screen say?
sd_shadow said:
You should be able to unlock US Retail, the usb settings don't matter in bootloader, but it's not in fastbootd is it?
What does the fastboot screen say?
Click to expand...
Click to collapse
I apologize for the delay on this. The end of the week got pretty hectic at work.
To answer your question, the fastboot boot menu reads as follows:
AP Fastboot Flash Mode (Secure) - In red text
BL: MBM-3.0-rav-retus-c7bbc04d8e-210215
Baseband
Product/Variant
Serial Number
CPU
eMMC
DRAM
Console (NULL): null
Tools Mode Config: DISABLED
Power OK - in green text
oem_locked
Transfer Mode: USB Connected
The sections that are lacking in detail are sections I figured weren't relevant since they are phone specific (hardware) sections.
PrettyDumbITGuy said:
I apologize for the delay on this. The end of the week got pretty hectic at work.
To answer your question, the fastboot boot menu reads as follows:
AP Fastboot Flash Mode (Secure) - In red text
BL: MBM-3.0-rav-retus-c7bbc04d8e-210215
Baseband
Product/Variant
Serial Number
CPU
eMMC
DRAM
Console (NULL): null
Tools Mode Config: DISABLED
Power OK - in green text
oem_locked
Transfer Mode: USB Connected
The sections that are lacking in detail are sections I figured weren't relevant since they are phone specific (hardware) sections.
Click to expand...
Click to collapse
Baseband and product could be relevant, not likely though.
I would reflash the firmware with Lmsa rescue
Skip the device details when asked just go straight to rescue.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
sd_shadow said:
Baseband and product could be relevant, not likely though.
I would reflash the firmware with Lmsa rescue
Skip the device details when asked just go straight to rescue.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
So I went through that post and installed the Smart Assistant. I attempted rescue but the application simply does not detect the phone in fastboot mode or in debug mode. I am not sure what the issue could be. I should probably just send this phone back and get a different phone.
PrettyDumbITGuy said:
. I should probably just send this phone back and get a different phone.
Click to expand...
Click to collapse
I agree
sd_shadow said:
I agree
Click to expand...
Click to collapse
Thank you very much for your time and assistance. I truly appreciate it.
Just picked up a new Pixel 3 XL. I am able to see the device under adb devices when I'm booted normally but when I reboot bootloader I can't see device. I want to flash latest factory image before I install a custom ROM. USB debugging is enabled and allow bootloader unlock is also turned on. This is my first time with Windows 10, not sure if I'm missing something or not.
edit: downloaded USB driver from Google. My other Pixel shows the same symptom but bootloader is already unlocked on it.
Update your adb/fastboot tools.
I am trying for the first time to root my 7t pro McLaren, and I ran into a problem. When the boot loader is turned on, and I use fastboot devices, nothing happens. When I do adb devices with it powered on, it shows that its connected. I tried to use the oneplus usb driver update, and nothing happened. does anyone have any solutions? I have OEM unlocking turned on and SIM permantly unlocked. If it helps I'm running on windows 10.
KH-Squisshy said:
I am trying for the first time to root my 7t pro McLaren, and I ran into a problem. When the boot loader is turned on, and I use fastboot devices, nothing happens. When I do adb devices with it powered on, it shows that its connected. I tried to use the oneplus usb driver update, and nothing happened. does anyone have any solutions? I have OEM unlocking turned on and SIM permantly unlocked. If it helps I'm running on windows 10.
Click to expand...
Click to collapse
Hi.
What you want to do exactly?
To Root open bootloader as first.
Developer options /Default usb configuration/ file transfer. Then check if pc "see" your device. fastboot fastboot devices. If visible then u are at home let's say
Make sure your USB port on the phone is clean using compressed air. Though if it works with ADB it should also work in bootloader
Riski3Run said:
Hi.
What you want to do exactly?
To Root open bootloader as first.
Developer options /Default usb configuration/ file transfer. Then check if pc "see" your device. fastboot fastboot devices. If visible then u are at home let's say
Click to expand...
Click to collapse
I was trying to just root it, but I found out what it was. someone sent me the drivers to update my device in manage devices.