Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Try installing the usb driver https://developer.android.com/studio/run/win-usb
billyedit said:
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Click to expand...
Click to collapse
I'm confused about "sits unlocked" and if this means you're stuck on the unlocked bootloader warning screen. If the phone hangs you're better off keeping the bootloader unlocked until that problem is sorted out. If it's starting, on the other hand...
Waiting for device means fastboot isn't communicating with the phone. Could be USB drivers. But if you flashed Android 11 from the same computer, drivers were working then, right?
In Developer options make sure USB debugging is enabled. While there, and while the bootloader is still unlocked, make sure OEM unlock is in the On position; it will flip back to Off when the bootloader is locked again.
Use Platform Tools 33.0.3 when trouble shooting USB to avoid trouble shooting Platform Tools 34.x.x.
As long as you get serial number output from commands adb devices and fastboot devices, fastboot flashing lock should work to re-lock the bootloader. Remember to finalize locking with the phone buttons.
Thank you both is was indeed the USB driver that needed the google update... All is well! thanks
Related
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.
Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app
I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.
sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
hammy88 said:
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
Click to expand...
Click to collapse
i recommend for you to KDZ 20p refurbished..
and heres the instruccions same as 20i
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
hammy88 said:
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
Click to expand...
Click to collapse
did you click on screen when you gave the command to go into fastboot it shows some sort of numbers and leters and asks you if you want to allow phone .??/ did you
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
hammy88 said:
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
Click to expand...
Click to collapse
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
raptorddd said:
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
Click to expand...
Click to collapse
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
hammy88 said:
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
Click to expand...
Click to collapse
can try another computer maybe. i use the drivers from LGUP..
am afraid i do not know how to proceed from here. am pretty sure you are not alonei gave read someting similar but.. i didnt pay attention
I tried 3 other computers , did not help resolve the issue
hammy88 said:
I tried 3 other computers , did not help resolve the issue
Click to expand...
Click to collapse
i came across this try it.
http://forum.xda-developers.com/showpost.php?p=69339003&postcount=2
Use Linux dude, also try different cables. My stock g4 came with a bad cable that only charged.
I've had exactly the same problem as hammy88. Is what is referred to as "fastboot mode" the same as download mode? I know it's relatively easy to get into download mode. But "adb reboot bootloader" doesn't work for me.
Fastboot mode ≠ Download mode
If you did tick "Enable OEM unlock" , and adb reboot bootloader doesn't work, then I guess is BL is locked now.
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
hammy88 said:
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
Click to expand...
Click to collapse
Brother, be calm. Find the fastboot drivers. And update.
You will figure it out. Just do it.
Hi, Im kinda new to this bootloader thingy. What happen is, i updated the razer phone 2 to Pie, but notice wifi and sim card cant be detect. Even factory reset fails. So i thought of flashing new image on it. KINDA easy on my oneplus, but im not sure where I gone wrong on this razer phone 2, i accidentally unlock the bootloader. NOW the problem is HOW to relock it back? i been follow all youtube and guides all over the place but still fails.
The state of device atm, cannot be boot into Download Mode. Everytime I plug in usb c from Windows, it will boot into unlock bootloader warning page, and continue boot into the homescreen. testing the adbtools, fastboot also to no avail. Can anyone help and guide me how to relocking it back? Maybe i type wrongly on cmd or maybe other android steps not similar to razer one etc....:crying:help much appreciated.
Hold volume down while turning on. Then fastboot flashing lock.
the stock usb doesnt send things correctly in BL mode, https://www.amazon.com/Blackweb-3-Foot-Charge-Cable-Connector/dp/B07SG7P3KZ/ worked for me. with the correct usb cable you should be able to perform the lock commands correctly. can you give us more detail of what you tried on this phone so we know if we need to provide you additional information?
https://developer.razer.com/razer-phone-dev-tools/general-instructions/
"Locking the Bootloader
Locking the bootloader is recommended for security reasons. Some applications will not work with an unlocked bootloader.
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader Enter Download Mode:
Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
Lock the critical partitions of the Bootloader first by running this command: fastboot flashing lock_critical
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot."
I can't seem to enter download mode. All I have is fastboot mode and the option to either reboot, close the phone or enter recovery mode. I would really like to lock the bootloader, but I can't seem to be able to detect my phone on my PC even though I installed the fastboot driver.
The_Vinlander said:
I can't seem to enter download mode. All I have is fastboot mode and the option to either reboot, close the phone or enter recovery mode. I would really like to lock the bootloader, but I can't seem to be able to detect my phone on my PC even though I installed the fastboot driver.
Click to expand...
Click to collapse
You must use a USB 2.0 port. The RP2 isn't detected by fastboot when connected to a 3/3.1 port.
Reznor7 said:
You must use a USB 2.0 port. The RP2 isn't detected by fastboot when connected to a 3/3.1 port.
Click to expand...
Click to collapse
I tried this, but to no avail. I tried with 2 cables I had and it keeps telling me < waiting for device > when I enter this command; fastboot flashing lock_critical
The_Vinlander said:
I tried this, but to no avail. I tried with 2 cables I had and it keeps telling me < waiting for device > when I enter this command; fastboot flashing lock_critical
Click to expand...
Click to collapse
You need to go into your device manager and select [ android bootloader interface ] while in fastboot
Hi guys so my device is on global miui 12.0.6.0 stable and whenever i check for updates it says its the latest but I know there is an android 11 already, my device is still on android 10.
So next step is to unlock adb and fastboot right so I can update my device.
I did all the steps necessary.
OEM Unlock is on
MI account is connected on (mi unlock status)
usb debugging is on
install via usb is on
usb debugging security settings is on
No password (lockscreen)
Other things I've done:
I installed the Miui 12 on the check update screen twice
I factory reset on settings
I cleared all data on recovery settings (stock recovery only of miui)
andd still no LUCK! I badly need some of you high IQ guys here to help me resolve this please My mind hurts its like the factory of fastboot of this phone has somehow got corrupted....
I can hear a sound when connecting via usb when on black screen fastboot mode
I can even access adb commands like " adb reboot bootloader & adb reboot fastboot " and they all leads to the BLACK SCREEN FASTBOOT (NO LOGO) MODE T.T
Does >fastboot devices respond with your phone?
HaveSomeCyanide said:
Does >fastboot devices respond with your phone?
Click to expand...
Click to collapse
after tweaking and tweaking it does. Fortunately MI Unlock also works even if its just a black screen fastboot mode. so weird but it is what it is
HaveSomeCyanide said:
Does >fastboot devices respond with your phone?
Click to expand...
Click to collapse
after tweaking and tweaking it does. Fortunately MI Unlock also works even if its just a black screen fastboot mode. so weird but it is what it is
I believe that this shouldn't modify fastboot, try to reflash the latest and original MIUI rom using flash_all.bat (don't use flash_all_lock.bat)
It should fix any corrupted partitions. Or it may not do anything.
EDIT3:
Resolved! I changed the usb port on my computer... Weird problem as adb worked fine over the old port. What I say about having relocked the bootloader below is wrong. I just assumed I had because my system said so and I didn't see the scary letters at startup. Leaving this here in case it helps future idiots.
Excuse me if this is a dumb question. I'm not too familiar with how this is exactly supposed to work.
I tried to update and messed up (of course) so I had to do a full reset which relocked my bootloader. Now I have a locked device on the latest software but I can't see the device in with `fastboot devices` anymore. Thus I can't unlock the bootloader again.
I'm running the apt installed version of fastboot on ubuntu.
EDIT:
I did find the oem unlock toggle in settings but it's greyed out.
EDIT2:
`lsusb` is also recognizes nothing in when the device is in fastboot mode.