All of a sudden, my 6p went into boot loop today. No warning or anything else. Happened just like that.
I installed adb and fastboot as per Heisenberg's guide, but not able to run any commands.
'Fastboot flashing unlock' is giving me 'remote: oem unlock is not allowed' This must be because I did not enable OEM unlocking in the developer options.
'adb reboot bootloader' is giving me : 'errors: no devices/emulators found'
I tried to install TWERP, but that also failed with the error: 'remote: device is locked. Cannot flash images.'
I tried Skipsoft, but its saying 'Device mode cannot be detected'
What shall I do now?
pls help me..pls
I tried the instructions given HERE..but No luck
Without OEM Unlocking enabled your pretty much at a lose.
Only option is to buy another phone or have your warranty if applicable.
Sent from my Pixel XL using Tapatalk
Called Google Support and they are giving me a replacement device
When u get it I'd suggest that u enable OEM Unlocking even if u never root it. It can be a life saver
Sent from my Pixel XL using Tapatalk
7.0 ? 7.1 .1?
Yes. I am going to enable OEM unlocking, unlock bootloader, custom recovery and of course root it
Related
I need a little help here, I am trying to unlock my bootloader , I have already able oem unlocking and install the proper driver. But everytime I try fastboot oem unlock , it just reply " failed : oem unlock is disabled " in CMD. Does anyone else have the same problem?
I had problems with an older version. I think you have to try to update your platform-tools (fastboot, adb). Good luck!
So , where can I get an updated version?
e.g. https://developer.android.com/sdk/index.html and there "SDK Tools Only"
I kinda have the same issue I have downloaded all the proper tools and drivers but whenever I try the fastboot oem Unlock command it comes back saying it's completed but my screen just stays on the fastboot logo and does nothing until I restart it this happens on my pc and my mac, I'm not sure what I'm doing wrong and at this point I'm very frustrated.
Sent from my ONE A2005 using Tapatalk
thesickness13 said:
I need a little help here, I am trying to unlock my bootloader , I have already able oem unlocking and install the proper driver. But everytime I try fastboot oem unlock , it just reply " failed : oem unlock is disabled " in CMD. Does anyone else have the same problem?
Click to expand...
Click to collapse
Enable OEM Unlocking in developers option. Check if this solves the issue.
So I updated adb and fastboot with the latest SDK tools , and I still get "OEM unlock is disable" in fastboot even thou I have clearly enable USB debugging and OEM unlocking. I really need another way around here, the stock rom which is a H2OS feels very bloated for me.
Did you enable "" OEM UNLOCK "" from developer options ?
TheDj408 said:
Did you enable "" OEM UNLOCK "" from developer options ?
Click to expand...
Click to collapse
Yes , I have stated that I enable OEM unlock many times, that is why I need help here.
You might want to disable the pattern lock and then try!
Before I describe my issue I'll let you know I've been looking up articles on how to solve this for weeks now. first post to XDA, so bear with me I'm new
I have two OPT, both have a similar problem, but one is working (I dare not try to mess with it) and the other I've already tried and tried and now I'm stuck in fastboot, no recovery, no OS.
I HAD an OS on it (Paranoid Android 6.0.1), but I couldn't factory reset, and I needed to, so that I could sell the phone. when I tried to factory reset through OS settings, it would boot loop until I hard reset the phone. I had no recovery apparently (IDK how I did that) but trying to install a recovery requires the "OEM Unlocking" setting to be checked. and for some reason it won't let me check the box. My working OPT phone has the same problem, the "Allow OEM unlocking?" box pops up, I select enable, and the toggle moves itself back to the grayed out selection. so I couldn't install a custom recovery, I can't do any formatting or erasing in fastboot either without that selection for some reason either. trying to only gives me a "FAILED (remote: device is locked. cannot erase images)" or "FAILED (remote: device is locked. cannot flash images)"
AND SO, I tried this (search google for "mega unbrick guide for a hard bricked oneplus 2". I can't post links apparently as it is my first post. it will be on the oneplus website) and now I have no OS. or at least I believe I have no OS because trying boot causes a bootloop. I've tried all the methods, but I'm assuming because my bootloader is locked, It failed with the "A2001_save_brick_mini" tool.
And so, all I have right now is bootloader. didn't have a recovery I guess, and now I think I don't have an OS. and I can't do anything in fastboot because is returns with a "FAILED" hehe. dang locked bootloader. I have no idea how both of these phones have locked bootloaders anyways, because I obviously unlocked the bootloader to install a custom ROM in the first place. did the bootloader relock itself, or maybe during the process of installing the ROM, the bootloader relocked? I'm not sure as I wasn't watching for that. the phones had booted with the new OS, and so I happily went along my business and didn't find out I had a problem until I tried to factory reset one of them.
no I have no phones now with similar problems, but at different stages of the same issue.
My ONE A2005 is working, but I can't toggle the "OEM unlocking". At least it has a working custom recovery (TWRP)
and MY ONE A2003 is stuck in fastboot (fastboot recognizes it via "fastboot devices" and I can reboot and "fastboot oem device-info") with what I believe to be no recovery or OS.
ask me any questions to further explain my predicament, and PLEASE offer me any things to try. I ave two phones to test different things with. I would prefer to keep the working one working though.
Have you tried the fastboot oem unlock command?
DR_HAX34 said:
Have you tried the fastboot oem unlock command?
Click to expand...
Click to collapse
Ah yes, I forgot to write that in. That also results in a "FAILED (remote: unlock device to use this command)"
I can't unlock because of the OS, or perhaps lack of OS now; And I can't install a new OS or recovery because my bootloader is locked
use qualcomm recovery tool if you can't get any help. it'll restore your phone to 100% stock
Hi,
I've tried all the following steps in the video and I got the error "flashing lock is not allowed". I've already flashed stock rom and recovery and wiped the phone so it's as stock as it gets yet I still get the same error when I enter "fastboot oem lock". Please help ASAP!!!! I'm trying to update to Android 8.0 but the update keeps failing because my bootloader is unlocked
Thanks in advanced.
https://forum.xda-developers.com/oneplus-5/how-to/lock-oneplus-5-bootloader-guide-t3651819
Go to developer settings.. check the oem unlock option. If it's off, bootloader won't relock. You need to turn it on. If it's greyed out & can't be turned on, then you need to root your firmware or flash custom rom & turn it on.
When you have this problem, only magisk will help you turn on allow bootloader unlocked when it's grayed out.
So, you have to flash magisk, turn on allow bootloader to be unlocked in devlopper settings, then flash a clean OOS, make sure there's no modification like custom recovery or root, then relock your bootloader.
Good luck!
use command "fastboot flashing lock" instead of "fastboot oem lock", this will lock your bootloader
hope this tutorial will help you....!!! https://www.youtube.com/watch?v=CQYCSdDUdAU
I had the same problem and solved using magistik, reenable unlock volta loader and After relock.
I am using A2017U, and for some reasons i unlocked my bootloader and flashed custom rom. Now i want to lock my bootloader but i tried several times to enter fastboot but the device is not entering fastboot through any mean, i tried through physical kepess through adb command, everything.
please help me.
teji007 said:
I am using A2017U, and for some reasons i unlocked my bootloader and flashed custom rom. Now i want to lock my bootloader but i tried several times to enter fastboot but the device is not entering fastboot through any mean, i tried through physical kepess through adb command, everything.
please help me.
Click to expand...
Click to collapse
Maybe by using Axon 7 EDL toolkit to enable fastboot first (Unlock option), then "fastboot oem lock" in fastboot mode. Refer to https://forum.xda-developers.com/showpost.php?p=78267172&postcount=200 . Warning : you need stock ROM (no changes in boot, recovery, system/root etc...) to avoid bricking your phone.
Hi everyone,
Today I tried unlocking the bootloader on my Lenovo Z6 Pro to root my phone but I've hit a dead end.
I've enabled OEM unlocking and USB debugging on the developer options before using "adb reboot bootloader". I managed to get to bootloader mode alright, but neither "fastboot flashing unlock" nor "fastboot oem unlock-go" works; I always get "remote: flashing unlock is not allowed" or "remote: oem unlock is not allowed".
This makes it seem like I didn't enable OEM unlocking before, but I made sure it was enabled. Any ideas how I might solve this?
Hi,
First you have to get the sn.img file for unlocking your bootloader from the zui website. Reboot to bootloader, first flash the img file and then enter the command for unlocking. As far as I have tried, you have to use this image file every time you need to unlock the bootloader(if you have locked it)
Good luck
Sayi Keshkar said:
Hi,
First you have to get the sn.img file for unlocking your bootloader from the zui website. Reboot to bootloader, first flash the img file and then enter the command for unlocking. As far as I have tried, you have to use this image file every time you need to unlock the bootloader(if you have locked it)
Good luck
Click to expand...
Click to collapse
Thanks for the reply. I gave up rooting my device for a while but I got tired of my phone bugging all the time so decided to give it another shot. This time I have another problem and it's driving me crazy: ADB wouldn't detect my phone when it's connected so I still can't unlock my bootloader. I tried installing every driver I could find but nothing works, but I can transfer files through explorer just fine. It occured to me that the USB might be the problem but it's the exact same one I used the last time I tried rooting it and I didn't have this problem back then.