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.
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!
hi every one
i hade some issue when i want to unlock oneplus2 bootloader,when i try to tape unlock oem fastboot toold me enable oem unlock from setting => option de developemnt => tooggle allow oem unlock
any idea about enable oem unlock from adb or cmd
thanks
deleco said:
hi every one
i hade some issue when i want to unlock oneplus2 bootloader,when i try to tape unlock oem fastboot toold me enable oem unlock from setting => option de developemnt => tooggle allow oem unlock
any idea about enable oem unlock from adb or cmd
thanks
Click to expand...
Click to collapse
http://lmgtfy.com/?q=enable+oem+unlock+ .
OEM Unlock can't be enable in fastboot / ADB, you'll have to reboot into normal mode, follow steps described in the link I've provided, and reboot into fastboot mode. Be aware too that that OEM Unlocking your phone will wipe your data (App, Pictures, etc).
Oh yeah, please, SEARCH next time, PLEASE, PLEASE, PLEASE!!!!!!
casual_kikoo said:
http://lmgtfy.com/?q=enable+oem+unlock+ .
OEM Unlock can't be enable in fastboot / ADB, you'll have to reboot into normal mode, follow steps described in the link I've provided, and reboot into fastboot mode. Be aware too that that OEM Unlocking your phone will wipe your data (App, Pictures, etc).
Oh yeah, please, SEARCH next time, PLEASE, PLEASE, PLEASE!!!!!!
Click to expand...
Click to collapse
thanks for your quick reply
but i cant boot into normal mode i hade frp and i want to by passe it by flashing stock rom
deleco said:
thanks for your quick reply
but i cant boot into normal mode i hade frp and i want to by passe it by flashing stock rom
Click to expand...
Click to collapse
First off whats FRP? and if the phone is locked at this point and you cant boot it you will not be able to unlock it sorry but on the other hand you dont need an unlock bootloader to flash a stock rom but once again if the phone is locked even after you flash the stock rom it will be locked still. Sounds like you found someone phone maybe you should return it
I am in same situation. Can't boot rom adb not enabled, bootloader locked.
I cannot flash anything via fastboot, if only I could enable adb some how
Do you have USB Debugging enabled?
If you are stuck at factory reset protection you should probably enter into it using the Google credentials or your pattern.. If you don't remember them its fine. But if it's not your phone, please return back.
@ewalk4866 frp is factory reset protection that is introduced in intention of avoiding data stealing... If you reset your phone when it is locked, you have to input your old password or pattern to get pass through lockscreen pattern.
More information here > https://support.google.com/nexus/answer/6172890?hl=en
Sent from my ONE A2003 using Tapatalk
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
I'm holding off twrp + bootloader unlock because I want to be able to undo in case I need to use my warranty. Is twrp/bootloader unlock reversible? Many thanks
Yes. Flash complete stock everything, boot into bootloader, connect to PC, and "fastboot oem lock".
Is it sure that it works??I have a A2017G and i have open BL and a B29 Custom Rom and i want back to Lock Bootloader
Kevinkuensken said:
Is it sure that it works??I have a A2017G and i have open BL and a B29 Custom Rom and i want back to Lock Bootloader
Click to expand...
Click to collapse
Yup! I've done it plenty of times. You do need to format the data partition though. This could mean that it'll wipe out even your internal storage, so back that up as well!
Im on stock and then i go to edl and then i type fastboot oem lock but nothing happend
Kevinkuensken said:
Im on stock and then i go to edl and then i type fastboot oem lock but nothing happend
Click to expand...
Click to collapse
Boot into bootloader, not EDL.
Erahgon said:
Yup! I've done it plenty of times. You do need to format the data partition though. This could mean that it'll wipe out even your internal storage, so back that up as well!
Click to expand...
Click to collapse
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
BlazingBullets said:
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
Click to expand...
Click to collapse
Locking it again is good for when you want to sell the device or send it in for warranty repair.
BlazingBullets said:
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
Click to expand...
Click to collapse
Yeah, the unlock procedure is the same as before. If you didn't restore the original boot image before the relock, then it's just a matter of booting into fastboot and unlocking the device. Note that this will cause your data to be wiped as well!
If you restore your boot.bin backup file from when your device was locked, does this lock the bootloader? "fastboot oem lock", "fastboot flashing lock" nor "fastboot oem device-info" does nothing for me. Is there any other way to check if your bootloader has been relocked?
Thanks
H0lmEd said:
I'm holding off twrp + bootloader unlock because I want to be able to undo in case I need to use my warranty. Is twrp/bootloader unlock reversible? Many thanks
Click to expand...
Click to collapse
Hi there,
Were you ever able to re-lock your bootloader on your A2017G?
I just want root for now but understand that I'll need to unlock the bootloader first. Before doing that, I want to make sure I can re-lock the bootloader if needed.
Thanks for letting us know!
joaste said:
Hi there,
Were you ever able to re-lock your bootloader on your A2017G?
I just want root for now but understand that I'll need to unlock the bootloader first. Before doing that, I want to make sure I can re-lock the bootloader if needed.
Thanks for letting us know!
Click to expand...
Click to collapse
Guys/Gals, it is seriously as simple as using the fastboot command in reverse. I've done it a few times already with mine.
If you used the following to unlock....
fastboot devices
fastboot oem unlock
.....then you can use the following commands to relock
fastboot devices
fastboot oem lock
fastboot devices is not necessary, but I do it to make sure the devices is being recognized by ADB/FASTBOOT
sauerkraut17 said:
Guys/Gals, it is seriously as simple as using the fastboot command in reverse. I've done it a few times already with mine.
If you used the following to unlock....
fastboot devices
fastboot oem unlock
.....then you can use the following commands to relock
fastboot devices
fastboot oem lock
fastboot devices is not necessary, but I do it to make sure the devices is being recognized by ADB/FASTBOOT
Click to expand...
Click to collapse
Thanks for the answer.
But there are a few files to flash before using that command according to this thread.
Doesn't anything need to be flashed again (e. g. stock files or anything)?
Correct, but you would have already flashed those in order to use the unlock command in the first place.
Are you trying to relock on marshmallow or nougat?
sauerkraut17 said:
Correct, but you would have already flashed those in order to use the unlock command in the first place.
Are you trying to relock on marshmallow or nougat?
Click to expand...
Click to collapse
My phone is only a few days old. I'm debating whether to keep it or not (considering the Mate 9, but the price is not the same - love the form factor and bigger screen though - sound won't be the same and I think I'll miss the MiPop button on the Axon (never thought that would happen )).
I'm on the latest MM (B10 - the A2017G model).
Following the mentioned thread, I got to the point of installing TWRP (the signed version), only to realize that besides making backups, there is not much else I can do with that without unlocking the bootloader. I really just wanted to flash supersu and install adaway fro the time being until development matured for this phone (maybe also play around with viper - had great results on my LG G4).
HI, I get the error "FAILED (remote: unknown command)" in ADB when I enter "fastboot oem lock". Any way to fix this?
Guys, can anyone help me? I really need to lock the bootloader!
How can I fix the error "FAILED (remote: unknown command)" in ADB when I enter "fastboot oem lock"?
I'm on MM B11 Stock.
https://i.imgur.com/fdkgYs6.jpg
Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.
Hello all! I have been trying to unlock my bootloader on my SGP311. I have searched the threads, followed the instructions, and still have problems. i initially looked at my service menu to determine if it is unlockable and it said yes. I then went through the steps to unlock it and it kept saying failed. Then, it finally worked, and my tablet rebooted. i got dual recovery loaded and then proceeded to wipe and install lineageOS from recovery. recovery kept failing to install the new rom. i then had to reflash a stock rom because the tablet wouldnt even boot into recovery again. now my service menu simply says rooting status: unknown and says nothing about the bootloader. What the heck happened?
Gilly86 said:
Hello all! I have been trying to unlock my bootloader on my SGP311. I have searched the threads, followed the instructions, and still have problems. i initially looked at my service menu to determine if it is unlockable and it said yes. I then went through the steps to unlock it and it kept saying failed. Then, it finally worked, and my tablet rebooted. i got dual recovery loaded and then proceeded to wipe and install lineageOS from recovery. recovery kept failing to install the new rom. i then had to reflash a stock rom because the tablet wouldnt even boot into recovery again. now my service menu simply says rooting status: unknown and says nothing about the bootloader. What the heck happened?
Click to expand...
Click to collapse
You can't install LOS Rom from the dual recovery (XZDR). By flashing stock ROM, you bootloader may be locked again.
Check this guide to unlock it, and install LOS.
It simply will not let me unlock the bootloader anymore. And I can't seem to find a firmware that I can flash to get me to the appropriate version
so far, part of the problem is flashtool in androxyde still using the command fastboot -i 0x0fce oem unlock 0xkey. windows 10 denies this command every time and should be fastboot oem unlock 0xkey. But even doing so manually through the cmd prompt, it still will not let me unlock the bootloader. does anyone have a ftf file that has an unlockable bootloader? seems mine locked up completely when i reflashed the rom
Gilly86 said:
so far, part of the problem is flashtool in androxyde still using the command fastboot -i 0x0fce oem unlock 0xkey. windows 10 denies this command every time and should be fastboot oem unlock 0xkey. But even doing so manually through the cmd prompt, it still will not let me unlock the bootloader. does anyone have a ftf file that has an unlockable bootloader? seems mine locked up completely when i reflashed the rom
Click to expand...
Click to collapse
bootloader is in device, not in firmware, so no such firmware exist you ask for.