Vivo y21l bootloader unlock? - General Topics

i tried to unlock my vivo y21l using adb command "fastboot oem unlock" but i get an error saying "device lock" message but my phone get identified by adb command so it's not a driver problem.is there any other way to unlock the bootolader? i just want to root my phone but not any one click methods are working so i guess it's because of locked bootloader maybe.thanks for anyone who can help.

Imalka Muthukumara said:
i tried to unlock my vivo y21l using adb command "fastboot oem unlock" but i get an error saying "device lock" message but my phone get identified by adb command so it's not a driver problem.is there any other way to unlock the bootolader? i just want to root my phone but not any one click methods are working so i guess it's because of locked bootloader maybe.thanks for anyone who can help.
Click to expand...
Click to collapse
Hi I can see you have already asked this before here
https://forum.xda-developers.com/showthread.php?t=3584719
You can bump your original post once every 24 hours but please don't create duplicate threads
Kind Regards
Sawdoctor

Related

rooting problem in moto g 1st gen

I have moto g xt-1033 running on android lollipop 5.1. Today when I'm trying to unlock my bootloader, I faced a problem. There showed an error saying "failed to erase partition, general unlock failure, oem unlock failure". But when i tried it again, it said it is already unlocked. I'm getting unlocked warning message while booting. Now I'm trying to root it using chainfire auto root. When I'm running the root-windows.bat file, command prompt is asking me to enter any key to continue and then nothing is happening. Phone is showing some messages like "cmd: oem unlock","cmd: oem unlock","cmd: oem unlock-go","cmd: oem unlock-go","cmd: flashing unlock". Then it is not moving. Please help me.
Can you post the screen shot of command prompt response ?
Did you get the unlock key from Motorola ?
Regards
Janardhan TS
sent from Mi
prasadbulusu said:
I have moto g xt-1033 running on android lollipop 5.1. Today when I'm trying to unlock my bootloader, I faced a problem. There showed an error saying "failed to erase partition, general unlock failure, oem unlock failure". But when i tried it again, it said it is already unlocked. I'm getting unlocked warning message while booting. Now I'm trying to root it using chainfire auto root. When I'm running the root-windows.bat file, command prompt is asking me to enter any key to continue and then nothing is happening. Phone is showing some messages like "cmd: oem unlock","cmd: oem unlock","cmd: oem unlock-go","cmd: oem unlock-go","cmd: flashing unlock". Then it is not moving. Please help me.
Click to expand...
Click to collapse
Flash latest twrp recovery..
then flash su binary in twrp....
with this method u can easily root your moto g .....

error 0x7000 while unlocking bootloader, "remote: unlock failed". Simply put.

error 0x7000 while unlocking bootloader, "remote: unlock failed". Simply put.
I cant find a single post that also has unlock failed as apart of the error, I need help, I don't know why this is happening.
I type fastboot oem unlock and press volume up... unlock failed return to fastboot in 3s comes up on screen.
and in cmd: FAILED: (Remote: Unlock failed - Err:0x7000)
Edit: OEM unlocking is enabled in dev options
pls help clanezo.
Clanezo said:
I cant find a single post that also has unlock failed as apart of the error, I need help, I don't know why this is happening.
I type fastboot oem unlock and press volume up... unlock failed return to fastboot in 3s comes up on screen.
and in cmd: FAILED: (Remote: Unlock failed - Err:0x7000)
Edit: OEM unlocking is enabled in dev options
pls help clanezo.
Click to expand...
Click to collapse
First, you didn't say what device model number you have.
Next, not all devices can be unlocked and not all devices that can be unlocked can use the "oem unlock" command. Some devices use "fastboot flashing unlock" command to unlock bootloader.
Last, just because your device has the "oem unlock" option in dev settings, doesn't mean your device can be unlocked.
Sent from my LGL84VL using Tapatalk
Model number
Oh, sorry. It's a huawei lua-lo2. Is it possible to unlock that phone?
Droidriven said:
First, you didn't say what device model number you have.
Next, not all devices can be unlocked and not all devices that can be unlocked can use the "oem unlock" command. Some devices use "fastboot flashing unlock" command to unlock bootloader.
Last, just because your device has the "oem unlock" option in dev settings, doesn't mean your device can be unlocked.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Seems you didn't see my first reply, see below.. or above, where ever this reply is placed.
Clanezo said:
Seems you didn't see my first reply, see below.. or above, where ever this reply is placed.
Click to expand...
Click to collapse
Have you tried doing a simple Google search for:
"Unlock bootloader huawei lua-lo2"
If there is a known method, that will find it, if it doesn't find anything then there is not a known method.
Sent from my LGL84VL using Tapatalk
Droidriven said:
First, you didn't say what device model number you have.
Next, not all devices can be unlocked and not all devices that can be unlocked can use the "oem unlock" command. Some devices use "fastboot flashing unlock" command to unlock bootloader.
Last, just because your device has the "oem unlock" option in dev settings, doesn't mean your device can be unlocked.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Have you fixed this error?
Droidriven said:
Have you tried doing a simple Google search for:
"Unlock bootloader huawei lua-lo2"
If there is a known method, that will find it, if it doesn't find anything then there is not a known method.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Can you please help me regarding this issue.. i am facing the same error 0x7000 after executing fastboot oem unlock command. The device asks whether you want bootloader to be unlocked.. then I press volume up to say yes.. then it gets failed with error 0x7000.
I have checked all precautions.. oem unlock is on in developer mode and all the drivers are successfully installed.
my device is lenovo A5.

Unlocked Oneplus 7 pro when unlocking bootloader getting error

I have a SIM unlocked Oneplus 7 pro T-Mobile version that had gone through the process of unlocking boot loader with adb and fastboot.
But when I try the command "fastboot oem unlock". I get an error code with "Remote: Please flash unlock code".
I was able to get the unlock code using another fastboot command, but I haven't been able to find out how to either apply it, flash it, or maybe I missed something?
Nitruckz said:
I have a SIM unlocked Oneplus 7 pro T-Mobile version that had gone through the process of unlocking boot loader with adb and fastboot.
But when I try the command "fastboot oem unlock". I get an error code with "Remote: Please flash unlock code".
I was able to get the unlock code using another fastboot command, but I haven't been able to find out how to either apply it, flash it, or maybe I missed something?
Click to expand...
Click to collapse
You must get the BL unlock token from OnePlus.
https://www.oneplus.com/account/sign-in?return_to=https://www.oneplus.com/unlock_token
https://www.getdroidtips.com/how-to-unlock-t-mobile-oneplus-7-pro-bootloader/

Doogee X95 smartphone

Hi,
I have a new X95 with Android 10 go edition. aperently I get an error message when I use some apps.
do not disturb access this feature is not available on this device
Is there anything I can do, to solve this problem?
I would like to flash another img file to the device but got all the time <wating for device> any solution for that?
Constantly get 'unauthorised', oem boot set to unlocked, usb debugging enabled, tried revoking and re-enabled no change....help
tennoguchi said:
Constantly get 'unauthorised', oem boot set to unlocked, usb debugging enabled, tried revoking and re-enabled no change....help
Click to expand...
Click to collapse
Use only this command:
Fastboot flashing unlock
I too want to unlock, root and customize the X95... And failed at the very first steps.
I hope some of the forum gurus watches this phone/thread
Here's the steps I took and the errors I got, any help would be appreciated!
1. enable "OEM unlocking" in development options
2. adb reboot fastboot
3. a) fastboot flashing unlock FAILED (remote: 'Unrecognized command flashing unlock')
3. b) fastboot oem unlock FAILED (remote: 'Command not supported in default implementation')
Also, this phone seems not to be recognized in bootloader mode (displays only "=> fastboot", but fastboot doesn't recognize any device).
When booting to recovery, entering fastboot from there (same as after "adb reboot fastboot"), I can get to the point of failure above.
I'm really uncomfortable with the current setup, any help would be appreciated!
Someone got root
Someone got root.
Thank you.
gatolocox said:
Someone got root.
Thank you.
Click to expand...
Click to collapse
This answer/question (?) is not really helpful, can you please elaborate?
Any news on how to root the x95?
Olize said:
Any news on how to root the x95?
Click to expand...
Click to collapse
I haven't tried since the failure reported above, meanwhile I got a redmi note 9s for 119€, so I'm using this one on a custom setup now.
Still using the x95 as an AP, I'm interested on any progress made on the topic..

Question Is it possible to OEM Unlock a CN to WW ROG Pho 5s Pro, I've tried everything

I'm on the latest Android 13. I've been trying to unlock and root this phone but OEM Unlock isn't in Developer Options and most fastboot commands give the error FAILED (remote: 'Command not supported in default implementation').
I contaced Asus and that's how I found out it was originally a CN version(now WW) but they said they can't help me. I've installed ADB, Fastboot and the USB drivers and the phone is detected by "fastboot devices" but "fastboot oem unlock" gives the above error. fastboot flashing unlock gives error Unrecognised command.
Not sure if this means anything but all the adb commands to reboot to bootloader/recovery/fastboot all just reboot to the first "Start" page option.
I found a thread here that seemed to be specifically about my problem but the contents were deleted and nothing else I've found has helped me past this point(a few other posts were very helpful though).
Am I stuck on this? Thanks for any info you can give.
<Moderator Edit>: Post edited. I will PM you as to why shortly.
I have rog phone 5s pro tencent edition china rom... and I success to convert to global ww rom
krampyl said:
I'm on the latest Android 13. I've been trying to unlock and root this phone but OEM Unlock isn't in Developer Options and most fastboot commands give the error FAILED (remote: 'Command not supported in default implementation').
I contaced Asus and that's how I found out it was originally a CN version(now WW) but they said they can't help me. I've installed ADB, Fastboot and the USB drivers and the phone is detected by "fastboot devices" but "fastboot oem unlock" gives the above error. fastboot flashing unlock gives error Unrecognised command.
Not sure if this means anything but all the adb commands to reboot to bootloader/recovery/fastboot all just reboot to the first "Start" page option.
I found a thread here that seemed to be specifically about my problem but the contents were deleted and nothing else I've found has helped me past this point(a few other posts were very helpful though).
Am I stuck on this? Thanks for any info you can give.
Click to expand...
Click to collapse
You can't root this device that way. You need the ASUS unlock tool and I believe ASUS have pulled their unlock service for the time being. I think you will find tens if not hundreds of posts related to this topic on the forum. Patching via EDL is an option but not done so far as everyone have used the ASUS Unlock tool?
krampyl said:
I'm on the latest Android 13. I've been trying to unlock and root this phone but OEM Unlock isn't in Developer Options and most fastboot commands give the error FAILED (remote: 'Command not supported in default implementation').
I contaced Asus and that's how I found out it was originally a CN version(now WW) but they said they can't help me. I've installed ADB, Fastboot and the USB drivers and the phone is detected by "fastboot devices" but "fastboot oem unlock" gives the above error. fastboot flashing unlock gives error Unrecognised command.
Not sure if this means anything but all the adb commands to reboot to bootloader/recovery/fastboot all just reboot to the first "Start" page option.
I found a thread here that seemed to be specifically about my problem but the contents were deleted and nothing else I've found has helped me past this point(a few other posts were very helpful though).
Am I stuck on this? Thanks for any info you can give.
Click to expand...
Click to collapse
Also, do not pay anyone on Facebook or other places for this type of work. Just a friendly advise to save you some $.

Categories

Resources