I am trying to unlock the boot-loader on my OPO. I have followed all the instructions to the best of my abilities. It is saying no fastboot devices found. I have installed so many drivers I do not know what to do next. I have turned on USB debugging, so I know that is right. Any help would be appreciated.
did it
Volfanoftwins said:
I am trying to unlock the boot-loader on my OPO. I have followed all the instructions to the best of my abilities. It is saying no fastboot devices found. I have installed so many drivers I do not know what to do next. I have turned on USB debugging, so I know that is right. Any help would be appreciated.
Click to expand...
Click to collapse
Don't know what happened by the device showed up?????
I also flashed oxygen! Proud of myself!
Related
Hey guys I really hope you can help me out because I have a bricked N5. So this is my first time attempting to flash anything to my phone and I decided to check out the android L preview. I watched a bunch of videos and got everything set up (SDK, unlocked bootloader). After I unlocked the bootloader, I forgot to enable usb debugging before I booted into fastboot and attempted to flash L. When I try to flash L I get "writing bootloader... FAILED (remote: invalid bootloader image)" every time. So I said screw it I'll just flash 4.4.4 and be done with it but I get the same FAILED msg in cmd. I'm assuming this is the issue that's preventing me from successfully flashing anything to my phone but not 100% sure. I've tried to get my phone into recovery mode but can't seem to make that work either. What can I do to fix this? keep in mind that just today was the first time I've ever used the command prompt =/ Thanks in advance for giving this a read and I really hope its just some simple fix *fingers crossed*
USB Debugging has NOTHING to do with bootloader or fastboot. The ONLY thing USB Debugging is related to is ADB while booted into Android.
You might want to read some more threads: [Resource] All Guides and Info Threads
Lethargy said:
USB Debugging has NOTHING to do with bootloader or fastboot. The ONLY thing USB Debugging is related to is ADB while booted into Android.
You might want to read some more threads: [Resource] All Guides and Info Threads
Click to expand...
Click to collapse
well turn's out all I had to do was restart my laptop and now everything has decided to work. Thanks for the response Lethargy
Hello everyone
I've recently got an LG Q6 M700N, and I'm trying to root it, but I've came across a problem. Whenever I type in adb reboot bootloader, the phone simply reboots to the system. It won't go into bootloader. Have any of you encountered this issue? Can you give me a fix or a workaround? Developer options are ON, OEM Unlock is ON, drivers are installed, tried with multiple USB ports on my PC, adb sees the device in debug mode.
Thanks in advance!
If I've posted in the wrong thread: My bad! Sorry.
See thread in dev section
deleted
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
try using search next time because its already been talked abput here https://forum.xda-developers.com/oneplus-6/help/relock-bootloader-t3798135
Actually, I DID read that. I didn't just roll off the cabbage truck. If you have time to post snippy replies (I also searched YOUR post history), then maybe you can point out where in that thread the answer to my question is. I could see if there was a thread where this specifically happened, or if it had been talked about over and over, but I couldn't find one. You do know this is a fairly new device, right? TBH, you're just being rude. To count on someone to hit the right search terms for a single thread where the info exists is just asinine.
1) I have not seen anyone with this situation on the OP6 yet
2) The OP5T had an unbrick tool
3) Most phones have a way to restore the OS to factory
If it can't be restored without calling OnePlus, then why not just say so? I'll answer for you, it's because you actually enjoy replying in such a manner. Grow up.
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Flapjack said:
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
Click to expand...
Click to collapse
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
[email protected] said:
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
I did, but I got the "software image does not exist" error. Does it matter whether I downloaded the 5.13 or 5.15 vesion?
mikex8593 said:
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
Click to expand...
Click to collapse
I tried several times. It throws the following error, which when searched for, always seemed to be someone forgetting to enable OEM unlocking in settings:
Code:
FAILED (remote: oem unlock is not allowed)
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Flapjack said:
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Click to expand...
Click to collapse
Hi buddy,
I tired to relock the bootloader and success in that but the phone stuck at fastboot mode, neither restarting to system nor to anything. Kindly help me if i can flash the stock rom in locked bootloader is so how.
THanks in adv
Did you try msm download tool ?
My OnePlus was bricked and it's bootloader is locked too, I have tried most of the steps like msm and those Bat files etc. But error is coming
"Remote : Flashing is not allowed in locked state"
Even tried that all in one tool that also can't unlock my bootloader
Now plz someone show me steps it will be a great help
hey
I have unloaded my bootloader. Since then, the cell phone is no longer recognized on the pc in fastboot mode. can someone help me ?
Thanks in advance
This seems to be a pretty common issue. Make sure you have the right drivers.
thanks where can I get the correct drivers?
Desortsu said:
thanks where can I get the correct drivers?
Click to expand...
Click to collapse
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
And make sure you really are in the correct fastboot mode. My first few attempts failed because I didn't go from bootloader to recovery to fastboot.
Aoso make sure you using the side port to cennet.
hello that helped with the side port. a huge thank you but now I'm facing the next problem ... is there a way to lock the bootloader again?
Desortsu said:
hello that helped with the side port. a huge thank you but now I'm facing the next problem ... is there a way to lock the bootloader again?
Click to expand...
Click to collapse
It's already covered somewhere here... (1) Flash original stock boot.img back to the device (2) Use 'fastboot oem asus-csc_lk" to lock the device
Just mind that some owners of the CN/CN>WW converted versions apparently have issues re-unlocking the device again if you change your mind later. If you have a WW version you're fine however.
Desortsu said:
hello that helped with the side port. a huge thank you but now I'm facing the next problem ... is there a way to lock the bootloader again?
Click to expand...
Click to collapse
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com
Problem solved. Trying different USB cable (2.0) worked.
-----
Hi, I was trying to downgrade from Android 12 to 11. Following guide step by step, including
USB Debugging, Turn on OEM Unlocking, then used adb to boot into bootloader. Device state was locked. Ran fastboot flashing unlock but then stuck at Waiting for Device. Phone didn't go into warning to unlock bootloader.
I noticed that Boot slot is b, not sure if that matters.
Also tried to follow Google's own flash too, got stuck at the same phone screen.
Any help is appreciated.
Kenneth
kenship said:
Problem solved. Trying different USB cable (2.0) worked.
-----
Hi, I was trying to downgrade from Android 12 to 11. Following guide step by step, including
USB Debugging, Turn on OEM Unlocking, then used adb to boot into bootloader. Device state was locked. Ran fastboot flashing unlock but then stuck at Waiting for Device. Phone didn't go into warning to unlock bootloader.
I noticed that Boot slot is b, not sure if that matters.
Also tried to follow Google's own flash too, got stuck at the same phone screen.
Any help is appreciated.
Kenneth
Click to expand...
Click to collapse
Sounds like a driver issue. It's either the Google USB driver: https://developer.android.com/studio/run/win-usb
or the ADB driver: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
Thks for the reply. Well I can't say for sure but switching USB ports and changing cable eventually solved my issue. I kept reinstalling Google USB driver as well so any one of them could be the problem. But I really don't worry now since I successfully flashed 11 back.