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
Background: After a night of searching I was unable to find a solution for this. I'm a newbie in the phone tech, but I did root couple of them, back in the days, with stock recovery and with TWRP. The first owner of this phone said it was working well until this happened.
Problem: I got this phone in the state where it's stuck on Nokia logo. Developer mode is not enabled, therefore OEM is not unlocked as well, and I'm only left with a stock recovery with an option to sideload update from ADB, and a Fastboot (Download) mode. I haven't been able to find a trusted firmware and even if I did I don't think it would work without OEM unlock...
Any ideas?
And, oh, I'm using Linux.
Thanks
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.
Hi everyone
I was just trying to get a banking app to work and turned off developer settings as it seemed to be detecting that, this worked brilliantly except that I needed to restart after making a change to the phone and I had completely forgot to turn it back on and now it's on a bootloop. Windows in device manager does detect it "Android bootloader interface" but ADB doesn't detect it when in the bootloader.
When I did have usb debugging on it was detecting the phone at this stage perfectly and nothing else has changed so I know that the ADB drivers and the cable are working, unless theres been an update since I last installed it around a year and a half ago which would fiix this.
The bootloader is also unlocked too.
Would doing a factory reset help from within the bootloader help at all?
I'm not sure how to fix this and any help would be very much appreciated.
EDIT: Fixed, I could still flash the RAW file.