EDIT: Fixed (Post #2)
After years of successfully unlocking bootloaders and rooting all my phones, I'm at a loss on this one...
I went through the process of unlocking my bootloader. And I'm able to use the basic fastboot commands (reboot bootloader and reboot). However, when I try to boot TWRP (still on Sep 5th update) it says it can'ed because my bootloader is still in the locked state.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In addition, when I'm in the bootloader it says "Devices State: Locked" - Indicating that the bootloader is not unlocked, even though it is.
Process:
1) Enabled Developer options and checked "Allow OEM Unlocking" and "USB Debugging"
2) Connect phone to computer and run "ADB Devices" using CMD
3) Accept the ADB approval pop-up on the phone
4) Confirm the computer recognizes the phone through ADB
5) "adb reboot bootloader"
6) (phone now in bootloader) "fastboot devices" to ensure CMD recognizes the phone and it does
7) fastboot boot /path/to/twrp.img
8) Fails due to "Locked State"
But when I try to unlock the phone again, it says it's already unlocked (check above screenshot).
I'm stumped.
Any ideas?
I was able to fix it. I tried fastboot flashing unlock instead of fastboot flashing unlock_critical and it fully unlocked the phone. Fastboot shows the device as unlocked and I can now boot TWRP.
sn0warmy said:
I was able to fix it. I tried fastboot flashing unlock instead of fastboot flashing unlock_critical and it fully unlocked the phone. Fastboot shows the device as unlocked and I can now boot TWRP.
Click to expand...
Click to collapse
Just want thru same thing. Yup, regular unlock command worked for me too.
Same thing happened to me I just ran the regular command and it unlocked as well.
You need a different cable, the usbc to usbc cable does not allow you to do everything. Trust me I was stuck for nearly 24 he's trying figure out why it kept saying my phone was locked even tho it wasn't.
mackentosh said:
You need a different cable, the usbc to usbc cable does not allow you to do everything. Trust me I was stuck for nearly 24 he's trying figure out why it kept saying my phone was locked even tho it wasn't.
Click to expand...
Click to collapse
It's not the cable. I used the USB-A to USB-C cable from the Google Store. I learned this lesson with issues utilizing the USB-C to USB-C cable with the original Pixel XL.
This cable:
https://store.google.com/us/product/usb_c_usb_a_2?hl=en-US
mackentosh said:
You need a different cable, the usbc to usbc cable does not allow you to do everything. Trust me I was stuck for nearly 24 he's trying figure out why it kept saying my phone was locked even tho it wasn't.
Click to expand...
Click to collapse
Usba to c used here too. C to c wouldn't work.
mackentosh said:
>>signature<<.
Click to expand...
Click to collapse
You ass, I thought that was an actual bug on my screen.
socal87 said:
You ass, I thought that was an actual bug on my screen.
Click to expand...
Click to collapse
?????????
When?
sn0warmy said:
I was able to fix it. I tried fastboot flashing unlock instead of fastboot flashing unlock_critical and it fully unlocked the phone. Fastboot shows the device as unlocked and I can now boot TWRP.
Click to expand...
Click to collapse
After what step do I enter that command?
Related
Hello buddies,
I am having a sort of problem with my M8.
Just to make it clear from the beginning I'm pretty much a noob in this.
So after I got my phone debranded byba rooting method and had twrp installed I wanted to flash the stock recovery in my device so I can get OTA updates.
The momental state of the device: stock firmware 1.54.401.10, S-On, tempered, unlocked bootloader.
At first everything was going fine, but when I typed the command to erase cache before flashing the recovery.img, cmd in my pc crashed.
Now when I connect my device, in cmd I can see it only when I check usb debugging, when it's unchecked there isn't any device on the list unauthorised like it should be.
When I enter the command to reboot into fastboot, my device just reboots and when I get into fastboot manually cmd doesnt recognize it.
Just to make clear I don't think it's the drivers fault, I installed/uninstalled them several times and tried it in another pc and the same thing happens.
I messed up again something with the drivers, now I get two devices with the same name in fastboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When i try to reboot now into fastboot it says: error: more than one device andemulator
Sent from my HTC One_M8
I got it working
Sent from my HTC One_M8
leart369 said:
I got it working
Click to expand...
Click to collapse
How?
redpoint73 said:
How?
Click to expand...
Click to collapse
Firstly I installed a tiny program for drivers, where i uninstalled all the drivers which had been in relation with the phone(i can't remember the program name, i will post it later when i'm at home) then i revoked the usb debugging and connected my phone with usb debug off and let the pc install the drivers by itself. After that i checked debugging and fastboot recognized it with adb devices, i rebooted into bootloader and typed fastboot devices(it showed my device).
Flashed the recovery and done
Sent from my HTC One_M8
leart369 said:
Firstly I installed a tiny program for drivers, where i uninstalled all the drivers which had been in relation with the phone
Click to expand...
Click to collapse
Like some kind of PC clean-up program?
I knew it had to be a driver issue, but the fastboot response you were getting was odd or at least new to me. So glad you sorted it out. Nice work!
redpoint73 said:
Like some kind of PC clean-up program?
I knew it had to be a driver issue, but the fastboot response you were getting was odd or at least new to me. So glad you sorted it out. Nice work!
Click to expand...
Click to collapse
More like a driver manager, i'll post the name when i get on my laptop
The programm is called usbdeview, sorted my drivers by date and uninstalled all drivers that have been installed these days. And then connected the phone again wihout installing anything just let windows do his job
Sent from my HTC One_M8
Hello
i have a problem. When i connect my phone to my computer with Fastboot. My phone says "FASTBOOT USB" and 15 sec later I get this error and my phone says "FASTBOOT"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone is on Fastboot mode. Adb and Fastboot driver are installed. Please HELP me!
evildog1 said:
Hello
i have a problem. When i connect my phone to my computer with Fastboot. My phone says "FASTBOOT USB" and 15 sec later I get this error and my phone says "FASTBOOT"
My phone is on Fastboot mode. Adb and Fastboot driver are installed. Please HELP me!
Click to expand...
Click to collapse
Windows 8/8.1 has had issues with using devices in Fastboot mode. Luckily, a fix is already available. Follow the instructions in the thread linked below and make sure you have the drivers installed and HTC sync removed
http://forum.xda-developers.com/htc-wildfire-s/general/driver-finally-how-to-fastboot-to-t2857536
Click to expand...
Click to collapse
This method does not work
evildog1 said:
Hello
i have a problem. When i connect my phone to my computer with Fastboot. My phone says "FASTBOOT USB" and 15 sec later I get this error and my phone says "FASTBOOT"
My phone is on Fastboot mode. Adb and Fastboot driver are installed. Please HELP me!
Click to expand...
Click to collapse
Here is your solution: http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
evildog1 said:
This method does not work
Click to expand...
Click to collapse
Have you installed the drivers for the phone? Because the only reason for it to not work is the unavailability of the drivers
csoulr666 said:
Have you installed the drivers for the phone? Because the only reason for it to not work is the unavailability of the drivers
Click to expand...
Click to collapse
I have installed the HTC drivers and enter FASTBOOT again but the word "FASTBOOT USB" disappear without any errors on Windows 8.
evildog1 said:
I have installed the HTC drivers and enter FASTBOOT again but the word "FASTBOOT USB" disappear without any errors on Windows 8.
Click to expand...
Click to collapse
And what about HTC sync, is it installed as well? Also try to use a newer version of fastboot just in case(if you haven't updated it in some time)
csoulr666 said:
And what about HTC sync, is it installed as well? Also try to use a newer version of fastboot just in case(if you haven't updated it in some time)
Click to expand...
Click to collapse
@evildog1: If you have usb connection in recovery mode your drivers are ok. Please read my previous link on this page for solving the problem in windows 8.1.
Marcel1962 said:
@evildog1: If you have usb connection in recovery mode your drivers are ok. Please read my previous link on this page for solving the problem in windows 8.1.
Click to expand...
Click to collapse
i successfully flashed custom recovery with my old computer running Windows 7.
when i connect my device to my computer running Windows 7 without any HTC drivers, the word "USB" did not disappear from Fastboot and it always says "FASTBOOT USB". i installed HTC Drivers and run Fastboot flash and it worked perfectly.
On Windows 8. without any HTC Drivers, it tells me that there was something wrong with the USB. After i installed HTC Drivers and run Fastboot again, the word "USB" disappear from Fastboot screen without any errors.
EDIT: Solved
Before you ask, yes, I do have USB debugging on, and I do have ADB and fastboot drivers installed. I'm running Windows 10.
The ADB shell is working well while the watch is in "normal" system mode, but after I boot it into fastboot with the "adb reboot bootloader" command, it's no longer recognized by my PC. "adb devices" brings up an empty list, and entering any command at all gets ADB stuck at < waiting for any device >.
What do?
Instead of adb use
Code:
fastboot devices -l
ranf said:
Instead of adb use
Code:
fastboot devices -l
Click to expand...
Click to collapse
I mean I did that, sorry for being unclear.
Anyway, it was a Windows 10 driver issue. Apparently you have to manually specify via Device Manager that the watch uses Android ADB while it's in fastboot mode.
[NUMINIT] said:
I mean I did that, sorry for being unclear.
Anyway, it was a Windows 10 driver issue. Apparently you have to manually specify via Device Manager that the watch uses Android ADB while it's in fastboot mode.
Click to expand...
Click to collapse
Hi,
I have the same problem, how did you solve it in WIN 10 ?
Ferdinand
fmcheetah said:
Hi,
I have the same problem, how did you solve it in WIN 10 ?
Ferdinand
Click to expand...
Click to collapse
If I recall correctly, the watch showed up as an unknown device while plugged in in fastboot mode. It's just a matter of identifying it (unplug & plug in and see which one reacts) and manually pick "ADB device" or some such from the manual update settings.
I am having a problem with this also. After having many android devices and other OS's......this is the first time I have been unable to get the correct drivers to be able to see my watch file system on my Win7 PC....and Win10 laptop.
Here is what I get when trying to update the driver with ADB debugging enabled in on watch as well..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here are my choices available:
I get stuck selecting the right choices and all lead to the same "code 10" cant find/install driver.
RR215 said:
I am having a problem with this also. After having many android devices and other OS's......this is the first time I have been unable to get the correct drivers to be able to see my watch file system on my Win7 PC....and Win10 laptop.
Here is what I get when trying to update the driver with ADB debugging enabled in on watch as well..
Here are my choices available:
I get stuck selecting the right choices and all lead to the same "code 10" cant find/install driver.
Click to expand...
Click to collapse
This is probably a dumb question, but it never hurts to make sure: you do have the drivers installed, right?
That is my problem....I dont see it in the available list. I have several other android devices in use with no problems, also have the Sony PC Companion 2.1 on my PC and use that.
I am actually not in OP's situation actually now that I re-read the thread over. This is in normal boot mode. How do i get the correct driver for the watch from here.
Thanks for your help.
Phone will only connect to adb in bootloader mode and shows as (unauthorized) despite USB debugging enabled. Tried revoking all but did not fix.
Won't prompt for file transfer or USB debugging. Nothing even shows up in device manager when phone is booted into Android.
Tried 4 cables and 4 computers. Tried changing default usb mode.
Bootloader is unlocked.
I used to transfer files all the time but not it randomly does not connect.
You have to click on the popup on phone to "authorize" adb connection. Otherwise, u need latest platform tools and drivers
HueyT said:
You have to click on the popup on phone to "authorize" adb connection. Otherwise, u need latest platform tools and drivers
Click to expand...
Click to collapse
I never get the popup. It is as if the phone is connected to the wall when I plug it into my computer. EXCEPT when I am in booted into recovery and it says it is unauthorized.
adb devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not detected in fastboot mode at all.
The only option I see is to try factory reset via recovery.
I see this in recovery
Now I literally can't get anything to show in device manager or adb/fastboot.
I have tried every driver and guide under the sun. Disabled driver signature enforcement. Ran the convert MSM and the regular 1907 MSM, didn't fix.
No matter how many times I install the OP drivers or Google nothing even shows in device manager even when "Show hidden devices" is checked. This picture I am in the system with USB debug and OEM unlock enabled set to file transfer (Although it never prompted me for anything, in fact USBDeview doesn't show anything when I plug in the phone):
So it recognized your hd1907 in EDL mode for msmtool? If so then it's a software prob and fixable with oos10:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
HueyT said:
So it recognized your hd1907 in EDL mode for msmtool? If so then it's a software prob and fixable with oos10:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
Click to expand...
Click to collapse
I already ran this patched MSM like 10 times, I just get left in fastboot with no recovery or system and am forced to run the regular 1907 MSM to get back. Also tried Ubuntu just now and still not detected. I am very confident it is a software issue (on both phone and pc maybe) but I just can't figure it out for the life of me.
Now my bootloader is locked and I can't even connect to fastboot to unlock it again.
My sim is genuinely unlocked and I also have the genuine unlock_code.bin.
Currently spinning up a brand new install of Windows on my laptop to test with. Do you have exact recommendations for drivers? Some people recommend the Oneplus one and others the Google. What about the all in one tool driver install?
I currently have a network unlocked stock fully updated OOS 11.0.1.6.HD63CB system with locked bootloader. (I tried OTA updating to see if it would fix it)
Jonnyswboy said:
I already ran this patched MSM like 10 times, I just get left in fastboot with no recovery or system and am forced to run the regular 1907 MSM to get back. Also tried Ubuntu just now and still not detected. I am very confident it is a software issue (on both phone and pc maybe) but I just can't figure it out for the life of me.
Now my bootloader is locked and I can't even connect to fastboot to unlock it again.
My sim is genuinely unlocked and I also have the genuine unlock_code.bin.
Currently spinning up a brand new install of Windows on my laptop to test with. Do you have exact recommendations for drivers? Some people recommend the Oneplus one and others the Google. What about the all in one tool driver install?
I currently have a network unlocked stock fully updated OOS 11.0.1.6.HD63CB system with locked bootloader. (I tried OTA updating to see if it would fix it)
Click to expand...
Click to collapse
U need Qualcomm USB 9008 drivers
HueyT said:
U need Qualcomm USB 9008 drivers
Click to expand...
Click to collapse
I successfully ran the MSM several times.
After above patched MSMtool, Then can't u do "fastboot flashing unlock_critical" to unlock bootloader? Only then do u fastboot flash all oos10 files
HueyT said:
After above patched MSMtool, Then can't u do "fastboot flashing unlock_critical" to unlock bootloader? Only then do u fastboot flash all oos10 files
Click to expand...
Click to collapse
After above patched MSMtool I cannot connect to PC via fastboot. I just bought a Pixel 6, but thanks for the help.
It’s been a while since my last root project I was able to download and install one plus drivers. Got adb downloaded, my phone is recognized initially when when I try the command adb devices. Enter the command adb reboot bootloader which works flawlessly. However once in bootloader mode none of the Fastboot commands work. I keep on getting the waiting for device prompt.
I check device manager in windows 10 and the device is showing. Am I missing something? I tried 3 different cables, USB ports I can’t figure it out. Is there a special adb package I need to get or driver or something?
Quick specs
X570 chipset
AMD Ryzen 9 5900x
Gigabyte arous Master v2
I am using a usb 3.0 hub however I tried different ports on my pc and same issue
Oem unlock is enabled
Windows 10 Pro
Official one plus drivers
No other usb are connected besides the one hub.
Any help would be much appreciated.
Thanks
Make sure that you use the latest Platform tools from the Android website when using ADB or Fastboot. Also, can you show a screenshot of the device manager here when you're connected with your device in Fastboot mode?
here is a screenshot of my device manager when im in windows and my phone is at the home screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here what it shows in fastboot bootloader mode
nofroyo said:
here is a screenshot of my device manager when im in windows and my phone is at the home screen
View attachment 5665575
Here what it shows in fastboot bootloader mode
View attachment 5665577
Click to expand...
Click to collapse
You're missing the Fastboot drivers as you can see on the SS, Android connected, but it's missing the driver. Remember, OnePlus Drivers don't install the fastboot drivers, just standard ADB. Also, Fastboot uses different set of drivers, they're not the same as ADB.
I uploaded the ADB-Setup, install it, and it will install the Fastboot drivers too from Google. Make sure that your phone is connected to the PC and in fastboot (bootloader) mode when installing these.
After, restart the PC once, and you're good to go.
ekin_strops said:
You're missing the Fastboot drivers as you can see on the SS, Android connected, but it's missing the driver. Remember, OnePlus Drivers don't install the fastboot drivers, just standard ADB. Also, Fastboot uses different set of drivers, they're not the same as ADB.
I uploaded the ADB-Setup, install it, and it will install the Fastboot drivers too from Google. Make sure that your phone is connected to the PC and in fastboot (bootloader) mode when installing these.
After, restart the PC once, and you're good to go.
Click to expand...
Click to collapse
Thank you for the help I got it working, now I just need to figure out which root package I use for my phone. seem like a few different versions from what i can see. AA device is unlocked north american variant