I am trying to unlock the bootloader of my moto z xt1650-03, adb seems to find it, but issuing the" adb reboot bootloader" command simply turns the device off instead of opening the bootloader.
Fastboot does not recognize the device if I manually put it in bootloader by key combination.
USB debugging enabled. Oem unlocking enabled.
My device is devoloper edition which has markings on top right corner of the phone and "Motorola Confidential Property not for sale" also written.
http://cloud.tapatalk.com/s/58d220f1149f5/Screenshot_20170322-115628.png?
http://cloud.tapatalk.com/s/58d220c3b881f/Screenshot_20170322-115638.png?
Sent from my XT1650 using Tapatalk
And do I have the latest software update ?
NPL25.86-17-3
zohaibshafijutt said:
I am trying to unlock the bootloader of my moto z xt1650-03, adb seems to find it, but issuing the" adb reboot bootloader" command simply turns the device off instead of opening the bootloader.
Fastboot does not recognize the device if I manually put it in bootloader by key combination.
USB debugging enabled. Oem unlocking enabled.
My device is devoloper edition which has markings on top right corner of the phone and "Motorola Confidential Property not for sale" also written.
http://cloud.tapatalk.com/s/58d220f1149f5/Screenshot_20170322-115628.png?
http://cloud.tapatalk.com/s/58d220c3b881f/Screenshot_20170322-115638.png?
Click to expand...
Click to collapse
while that command should work, it's not the only way
power off, hold volume down button, power on
Sent from my sailfish using XDA Labs
Are you suggesting that I put it into bootloader through key combination you just told ?
Sent from my XT1650 using Tapatalk
I put my device in bootloader adb devices command does not work but fastboot devices command works. When I execute the command to unlock my bootloader"fastboot oem get_unlock_data, it gives error
* ... INFOunlock data:
INFOcid_get_cid_data: version 0 datablock
INFOfailed
OKAY [ *0.016s]
finished. *total time: 0.016s
Sent from my XT1650 using Tapatalk
And as I said my device is "prototype" so no official support to unlock my bootloader.
Sent from my XT1650 using Tapatalk
Related
I am following the official guide [*1], which is suggested from this root instruction[*2].
But I keep getting this error:
Code:
C:\fastboot>fastboot.exe -i 0x0fce oem unlock 0xMYKEYGOTFROMSONY
...
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
What could be wrong? Is there anyway to get more debug information to see why it's failing?
Here is my settings:
Phone model: D6503 / Xperia Z2
OS: Win 7 64-bit
USB Driver: Android Bootloader Interface version 4.0.0.0 [12/6/2010]
(This one is using android_winusb.inf dowloaded from Sony official site, and the rest files from latest Android SDK (64-bit)[*3].)
In the service info > Rooting status: Bootloader unlock allowed: Yes
Running this cmd:
Code:
>fastboot.exe -i 0x0fce getvar version
shows "5.0".
I didn't insert the SIM card while unlocking.
The phone USB debugging mode is enable already.
*1 = unlockbootloader.sonymobile.com/instructions
*2 = androidcentral.us/2014/04/root-sony-xperia-z2-on-android-4-4-2/
*3 = dl.google.com/android/adt/22.6.2/adt-bundle-windows-x86_64-20140321.zip
If you run "adb devices" from wherever your adb.exe is, does your phone show up? That's a good way to test if your USB drivers are working.
Download latest flashtool and install all drivers again and then use flashtool folders to use USB might work out better for you
Sent from my D6503 using XDA Premium 4 mobile app
i think you shouldn't show your unlock key to us
He didn't.
@JMonkeYJ: I ran adb.exe with my Z2 phone in fastboot mode, but it didn't find any device.
@festa20: I downloaded flashtool-0.9.16.0-windows, installed it.
- then run flashtool\drivers\Flashtool-drivers.exe, install below drivers:
Flashmode drivers, fastboot drivers, Xperia Z2 Device Drivers.
(But when connect Z2 to the USB in fastboot mode, in Windows 7 Device Manager, it still shows:
SAMSUNG Android Phone (my old phone was a Samsung):
Sony ADB Interface (Driver Provider: Google Inc., Driver data: 12/6/2010, Driver Version: 4.0.0.0)
Looks like the ADB driver is still the old one I installed, not from the flashtool(?)
- I then run flashtool\x10flasher_lib\fastboot.exe in command line, still got same error...
Looks like it's a driver issue, how do I install the correct driver?
khumash said:
@JMonkeYJ: I ran adb.exe with my Z2 phone in fastboot mode, but it didn't find any device.
@festa20: I downloaded flashtool-0.9.16.0-windows, installed it.
- then run flashtool\drivers\Flashtool-drivers.exe, install below drivers:
Flashmode drivers, fastboot drivers, Xperia Z2 Device Drivers.
(But when connect Z2 to the USB in fastboot mode, in Windows 7 Device Manager, it still shows:
SAMSUNG Android Phone (my old phone was a Samsung):
Sony ADB Interface (Driver Provider: Google Inc., Driver data: 12/6/2010, Driver Version: 4.0.0.0)
Looks like the ADB driver is still the old one I installed, not from the flashtool(?)
- I then run flashtool\x10flasher_lib\fastboot.exe in command line, still got same error...
Looks like it's a driver issue, how do I install the correct driver?
Click to expand...
Click to collapse
If your device is plugged in to PC in fastboot mode you need to do "fastboot devices"
nickwarn said:
If your device is plugged in to PC in fastboot mode you need to do "fastboot devices"
Click to expand...
Click to collapse
Running "fastboot devices" can see my device now. But still fail to unlock.
Code:
Flashtool\x10flasher_lib>fastboot.exe devices
MYZ2SN fastboot
khumash said:
Running "fastboot devices" can see my device now. But still fail to unlock.
Code:
Flashtool\x10flasher_lib>fastboot.exe devices
MYZ2SN fastboot
Click to expand...
Click to collapse
Let me know when you have time I will help u through team viewer and see what we can do
Sent from my D6503 using XDA Premium 4 mobile app
We did it
Sent from my D6503 using XDA Premium 4 mobile app
festa20 said:
We did it
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Many thanks to festa20 walk me through the whole process!!!
help
hi
i have the same problem in my z2 d6503 please help i can enter the recovery mode when i used the commend
fastboot flash boot ***.img
it said not command not allowed even i cant flash my device in flashtools it said error with loader.sin
help
Sony xperia z2 tablet - failed command not allowed
nickwarn said:
If your device is plugged in to PC in fastboot mode you need to do "fastboot devices"
Click to expand...
Click to collapse
I get a similar msg.
Running SDK from Linux (Tiny Core)
fastboot fired up fine
But got similar message after following Sony step-by-step.
./fastboot devices
then tried
./fastboot -i etc.
RESULT:
FAILED: (REMOTE: Command not allowed)
Any ideas?
Is there a different tool I should try another utility?
This Z2 is a Verizon release...and I noticed Sony site mentions some Z2 devices cannot be unlocked.
Is this an evil empire block?
Help!
I have problem just like OP. How did you fixed it?
Bootloader Unlocked Allowed : Yes
and fastboot working, detect my phone.
I already tried with 14,15 digit IMEI but result are same as the output bootloader key is same
I have issue using this method as well as trying to use flashtool. Both doesn't work. For fastboot I get into the command prompt and it's just stuck on waiting for device. In flashtool it can't find my device and tells me to reboot the phone. Any ideas? BTW my phone is rooted does that have something to do with it?
you cant adb bootloader unlock unless you have added/modded some adb files
(only aplies to z2 btw)
(yes fastboot and flasmode too you need the files(try developer.sonymobile.com)
try flashtool from flashtool.net
install drivers first before trying
Envious_Data said:
you cant adb bootloader unlock unless you have added/modded some adb files
(only aplies to z2 btw)
(yes fastboot and flasmode too you need the files(try developer.sonymobile.com)
try flashtool from flashtool.net
install drivers first before trying
Click to expand...
Click to collapse
Still don't work after downloading again. Anyone else got it working willing to help out? I've tried going through Sony developer again and it doesn't work. BTW my handset says bootloader is unlockable.
nyichiban said:
Still don't work after downloading again. Anyone else got it working willing to help out? I've tried going through Sony developer again and it doesn't work. BTW my handset says bootloader is unlockable.
Click to expand...
Click to collapse
have you got the drivers, adb files, adb installed with fastboot n flashmode and do you have the files for those
you can get all these files from sonymobile or adb download
of course you can try the easy way to unlock which is USING FLASHTOOL
festa20 said:
We did it
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What did you do? I'm having the same problem as khumash, I get:
Code:
>fastboot.exe -i 0x0fce oem unlock 0xMYKEY
...
FAILED (remote: Command did not succeed)
finished. total time: 0.020s
However, my device shows up when I do "fastboot devices", though nothing shows up when I do "adb devices"
festa20 said:
Let me know when you have time I will help u through team viewer and see what we can do
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ive got the same problem is there any chance you could help me please? its been driving me crazy trying to do this lol.
Hi all,
I've been trying to flash ElementalX kernel on my Nexus 9... and somehow I messed it up completely.
Here are the facts:
1. Booting is stuck on Google logo with red writing "This is a development device not intended for production use" at the top
2. Bootloaders is locked - I can see it in fastboot (Device State - LOCKED)
3. There's no OS to boot into (to enable "fastboot oem unlock" command)
4. "fastboot oem unlock" results in "(bootloader) Permission denied for this command!"
5. I can boot into TWRP recovery and I can sideload files
At one point bootloader was unlocked, but I (stupidly) issued "fastboot oem lock" command which screwed everything up....
What to do, any advice?
Thank you!
Try searching before posting. http://forum.xda-developers.com/showthread.php?p=59799854, http://forum.xda-developers.com/showthread.php?p=61748288. It's even stickied.
Sent from my Nexus 9 using XDA Free mobile app
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead.
I can get a black screen with the blue led by running adb reboot bootloader and the phone is recognised from fastboot devices but when I try to unlock the bootloader I get an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
Any help appreciated.
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead or by running adb reboot fastboot
If feels like I haven't go the fastboot USB drivers but I can't see how or where I can add them.
Any help appreciated.
Click to expand...
Click to collapse
Disable driver signature enforcement then reinstall sony drivers
tapiwasam said:
Disable driver signature enforcement then reinstall sony drivers
Click to expand...
Click to collapse
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
adb reboot bootloader just goes into bootloader mode and not fastboot mode which is needed to unlock it. Go directly into fastboot by typing adb reboot fastboot
Then when your phone led is flashing blue, run your fastboot "oem unlock" command.
Saw now that you already tried that sorry about that.
Tried running cmd with admin privileges to see if that shows any difference?
Also from sony:
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
.... snip....
Click to expand...
Click to collapse
You don't need to unlock your bootloader to simply downgrade to official MM! Just use flashtool to flash the appropriate MM ftf. There are plenty guides available on XDA and elsewhere.
I'm lost in your explanation.
You wanted to unlock your bootloader to be able to downgrade your phone? That's right? And it's fine to me, but you don't need to do that if you don't feel like. Unlocking your bootloader is nog necessary to downgrade to MM via flashtool.
So you tried to unlock your bootloader. But what you write what happened afterwards is completely unclear to me, because it contradicts itself.
-->> "Also I can see the phone with both adb devices and fastboot devices"
Fine. This means your connected with your phone and fastbook recognizes your phone. So bootloader is unlocked and software to control that works fine.
-->> "However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led."
Fine, so you unlocked your bootloader, and rebooted in fastboot.
-->> Obviously. It's an unlocked bootloader, you can double unlock it or something like that. You can relock it if you want (which doesn't make any difference for what you want to do) but that's a different method.
Is there any reason that you absolutely need to a second method to enter fastboot mode? Or any fastboot mode? It could be possible with another kernel, but I don't see the point to flash another kernel. I would just leave it like it is.
PhilG57 said:
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
Click to expand...
Click to collapse
that is notmal behaviour, that is fastboot mode, indicated by that blue LED
Thanks for the clarification that I don't need to unlock the bootloader to downgrade using flashtool. What I didn't say was that I couldn't reinstall Nougat using the Sony tool software restore option or get anywhere with flashtool because the phone won't go into the blue led mode by inserting the USB and holding the up vol button. I did try running flashtool in one window and the command line tools in another with the idea of running flashtool first and then unplugging the phone and replugging it to use command line to get the blue LED state, but that doesn't work because the command line tools can't see the phone once flashtool is running and has addressed the phone.
From what i read, i assume you are on nougat and want to go back to MM, right?
So you would need flashmode instead of fastboot mode.
You get there with holding Vol down button and plugging in USB cable on turned off phone.
Flashmode also shows a green notification light instead of the blue one.
If you having Problems to get there, please check following:
make sure to have latest version of flashtool installed http://www.flashtool.net/downloads.php
install drivers from your flashtool\drivers folder
don't use an USB 3.0 port or cable(have heard of some people having trouble with)
PhilG57 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed) <- this
finished. total time: 0.042s
Any help appreciated.
Click to expand...
Click to collapse
OP, I had the exact same problem as you. At the time I tried absolutely everything but never found the culprit. So after several months I actually succeeded today
This is the guide I followed - https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388 and it worked perfectly.
A few pointers:
- Go to the service menu (*#*#SERVICE#*#*) before you begin, before you turn OEM Unlocking ON from Dev Options .
- Take note of what it says in Configuration and Firmware.
- Now enable OEM Unlocking and take note again, it should say stuff like Model Number: Unknown and other unknown stuff.
- Reboot - IMPORTANT.
- Use the guide I gave you and you will be fine, it took me ages to find a solution but now I'm on MM and rooted
Hope I helped :fingers-crossed::fingers-crossed::fingers-crossed:
Hello
I have a problem when I want to unlock my nexus 9.
First I have a problem because my tablet freezed.
I have made a factory reset, then google said me : used the first account to use your tablet" but I lost this account
So I want to flash my tablet.
to do that, I use the tutorial on HTC site. on step 5 they say:
type adb oem unlock
but the CMD windows just say:
<waiting for device>
then I try to show devices with adb device but my window don't show device.
to do those step my tablet was in recovery more "fastboot usb"
can you help me?
thanks
Jack
@jackvig Looks like you encountered Factory Reset Protection!
You can not use adb commands while in fastboot mode! "fastboot devices" should list your device.
And the command to unlock is "fastboot oem unlock" not adb!
Plus you won't be able to unlock the bootloader unless you have selected the option to do so in developer options, since you have factory reset that option may have been turned off even if you set it previously.
Your going to have to try and remember your account password to make the device usable.
Depending on what version/patch of the rom your device is on it maybe possible to Bypass FRP, google it.
If your device was on a very recent patch level, no bypass trick will work.
corkiejp said:
@jackvig Looks like you encountered Factory Reset Protection!
You can not use adb commands while in fastboot mode! "fastboot devices" should list your device.
And the command to unlock is "fastboot oem unlock" not adb!
Plus you won't be able to unlock the bootloader unless you have selected the option to do so in developer options, since you have factory reset that option may have been turned off even if you set it previously.
Your going to have to try and remember your account password to make the device usable.
Depending on what version/patch of the rom your device is on it maybe possible to Bypass FRP, google it.
If your device was on a very recent patch level, no bypass trick will work.
Click to expand...
Click to collapse
thanks @corkiejp for your reply
I agree with you for fastboot instead of adb but the result is the same.
I cannot go inside the tablet to change parameters
Some forum said that I can Unlock in recovery mode
Is it true?
when my tablet is in recovery mode (On/off + Vol Up)
the tablet show me device state : locked
I am in state HBOOT
the on my computer I do that
C:\Users\maison>fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.015s]
finished. total time: 0.018s
after I go in FASTBOOT mode then :
C:\Users\maison>fastboot oem unlock
< waiting for device >
what can I do to have the Key to unlock
No you need fastboot mode to unlock the bootloader!
Is the command "fastboot devices" listing your device. If not check your drivers for your device.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT4B6JT00881 fastboot
after that i try :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload volantis-ota-n9f27m-ad1aee0f.zip
loading: 'volantis-ota-n9f27m-ad1aee0f.zip'adb server is out of date. killing...
* daemon started successfully *
serving: 'volantis-ota-n9f27m-ad1aee0f.zip' (~0%) * failed to read command: Invalid argument
i think tablet i now connected to computer
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) ability is 0
(bootloader) Permission denied for this command!
OKAY [ 0.011s]
finished. total time: 0.014s
As suspected the option to unlock is not selected in developer options.
If your successful in sideloading an OTA image in recovery mode (not fastboot mode), you will still encounter FRP on booting the device.
Edit: - As said before ADB commands do not work in fastboot mode. And fastboot commands do not work in Recovery mode!
As said before your only hope is to remember your account and password used (or the very last account you used on the device might work).
If you haven't updated the rom in the last year, you maybe able to use FRP Bypass trick.
jackvig said:
Hello
I have a problem when I want to unlock my nexus 9.
First I have a problem because my tablet freezed.
I have made a factory reset, then google said me : used the first account to use your tablet" but I lost this account
So I want to flash my tablet.
to do that, I use the tutorial on HTC site. on step 5 they say:
type adb oem unlock
but the CMD windows just say:
<waiting for device>
then I try to show devices with adb device but my window don't show device.
to do those step my tablet was in recovery more "fastboot usb"
can you help me?
thanks
Jack
Click to expand...
Click to collapse
You should not have factory reset if you do not know the account password. It is protected by "factory reset protection". To prevent it from being used if it is stolen. You are most likely going to need the password for the account that was logged in when you reset.
Flashing is not going to help. And as mentioned previously, you cannot unlock the bootloader now since you cannot go into developer options and turn on oem unlocking.
Pleas guys, is there a way to put this device in DIAG MODE or a rom modified to get root without MI account?
int211 said:
Pleas guys, is there a way to put this device in DIAG MODE or a rom modified to get root without MI account?
Click to expand...
Click to collapse
How to enter DIAG Mode and backup IMEI using QPST - Xiaomi Firmware
If you’re looking for a ways on how to enter DIAG Mode and restore / backup IMEI on Xiaomi smartphone here’s a complete guide. Below you’ll find few working methods on how to boot your device in DIAG mode and backup IMEI with Qualcomm Product Support Tools.Advertisement Entering DIAG Mode and...
xiaomifirmware.com
or
*#*#717717#*#*
or
*#*#426#*#*
or
use terminal method (google it)
or youtube
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjmmb7B6eDyAhWJG-wKHXbtBVIQwqsBegQIBhAB&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8ZzQPwD7bnE&usg=AOvVaw2rqhhONfY3ZJhbDcDfglYU
please leave a lik or"thanks" button if a method work and tell update on which one worked
I tryed now this way but with no unlock bootloader have failure, I forgot to say the bootloader is locked, its hard
int211 said:
I tryed now this way but with no unlock bootloader have failure, I forgot to say the bootloader is locked, its hard
Click to expand...
Click to collapse
Youve tried unlocking from developer options?
NOTE: I AM NOT IN ANYWAY RESPONSIBLE FOR YOU BRICKING OR DAMAGING YOUR DEVICE, I WILL NOT BE HELD LIABLE FOR YOUR ACTIONS
Steps to unlock the bootloader Xiaomi Redmi Note 10
download and install adb and fastboot tools on pc,
open the folder where you installed adb fastboot tools
go to your phone
Unlock your phone and open the Settings menu.
Go to settings, very bottom system or device info open it
Tap build number several times andl do what must be done to enable developer option
Go to Settings--> System -> Developer Options. You will see a list of special options.
Find the following option: “OEM unlocking. Allow the bootloader to be unlocked”.
Tap on the toggle to enable OEM unlocking.
Enable USB debugging as well in the developer settings
A prompt will come up on your phone and choose always allow this Pc to connect and accept
Options
1
On your Pc ,Go to where you installed adb and fastboot "where the files and app are"
shift + right click empty area and open cmd or powershell here
Type adb reboot bootloader and Hit Enter
or
2
Press and hold the power button. Tap on Power off to turn off the phone.
Connect your phone to your computer using a USB cable.
then
Open CMD/Powershell on your computer, and enter the following command: fastboot devices
If the terminal returns something, it means the computer is successfully communicating with the phone.
Run the unlocking command: fastboot flashing unlock (if this doesnt work google fastboot unlocking commands and try the ones they have there)
The screen of the phone will give you two options once you run the unlocking command. Choose Unlock the bootloader using volume buttons.
Press the Power button to confirm your selection.
your bootloader is now unlocked happy rooting
flairepathos.info said:
Youve tried unlocking from developer options?
NOTE: I AM NOT IN ANYWAY RESPONSIBLE FOR YOU BRICKING OR DAMAGING YOUR DEVICE, I WILL NOT BE HELD LIABLE FOR YOUR ACTIONS
Steps to unlock the bootloader Xiaomi Redmi Note 10
download and install adb and fastboot tools on pc,
open the folder where you installed adb fastboot tools
go to your phone
Unlock your phone and open the Settings menu.
Go to settings, very bottom system or device info open it
Tap build number several times andl do what must be done to enable developer option
Go to Settings--> System -> Developer Options. You will see a list of special options.
Find the following option: “OEM unlocking. Allow the bootloader to be unlocked”.
Tap on the toggle to enable OEM unlocking.
Enable USB debugging as well in the developer settings
A prompt will come up on your phone and choose always allow this Pc to connect and accept
Options
1
On your Pc ,Go to where you installed adb and fastboot "where the files and app are"
shift + right click empty area and open cmd or powershell here
Type adb reboot bootloader and Hit Enter
or
2
Press and hold the power button. Tap on Power off to turn off the phone.
Connect your phone to your computer using a USB cable.
then
Open CMD/Powershell on your computer, and enter the following command: fastboot devices
If the terminal returns something, it means the computer is successfully communicating with the phone.
Run the unlocking command: fastboot flashing unlock (if this doesnt work google fastboot unlocking commands and try the ones they have there)
The screen of the phone will give you two options once you run the unlocking command. Choose Unlock the bootloader using volume buttons.
Press the Power button to confirm your selection.
your bootloader is now unlocked happy rooting
Click to expand...
Click to collapse
That's not a proper unlock bootloader..it is safe unlock bootloader using unlock tools from xiaomi. If you unlock the bootloader to CMD it's a chance to brick. I think the proper to unlock is xiaomi tools
akoaypinoy said:
That's not a proper unlock bootloader..it is safe unlock bootloader using unlock tools from xiaomi. If you unlock the bootloader to CMD it's a chance to brick. I think the proper to unlock is xiaomi tools
Click to expand...
Click to collapse
Both are safe but through fastboot, xiaomi wouldnt know that your mi acccount is linked to an unlocked device
flairepathos.info said:
Both are safe but through fastboot, xiaomi wouldnt know that your mi acccount is linked to an unlocked device
Click to expand...
Click to collapse
Yup. There's a chance if using CMD authenticated issue mi acc
akoaypinoy said:
Yup. There's a chance if using CMD authenticated issue mi acc
Click to expand...
Click to collapse
Well mi unlock tools will be your option to go for them
flairepathos.info said:
Youve tried unlocking from developer options?
NOTE: I AM NOT IN ANYWAY RESPONSIBLE FOR YOU BRICKING OR DAMAGING YOUR DEVICE, I WILL NOT BE HELD LIABLE FOR YOUR ACTIONS
Steps to unlock the bootloader Xiaomi Redmi Note 10
download and install adb and fastboot tools on pc,
open the folder where you installed adb fastboot tools
go to your phone
Unlock your phone and open the Settings menu.
Go to settings, very bottom system or device info open it
Tap build number several times andl do what must be done to enable developer option
Go to Settings--> System -> Developer Options. You will see a list of special options.
Find the following option: “OEM unlocking. Allow the bootloader to be unlocked”.
Tap on the toggle to enable OEM unlocking.
Enable USB debugging as well in the developer settings
A prompt will come up on your phone and choose always allow this Pc to connect and accept
Options
1
On your Pc ,Go to where you installed adb and fastboot "where the files and app are"
shift + right click empty area and open cmd or powershell here
Type adb reboot bootloader and Hit Enter
or
2
Press and hold the power button. Tap on Power off to turn off the phone.
Connect your phone to your computer using a USB cable.
then
Open CMD/Powershell on your computer, and enter the following command: fastboot devices
If the terminal returns something, it means the computer is successfully communicating with the phone.
Run the unlocking command: fastboot flashing unlock (if this doesnt work google fastboot unlocking commands and try the ones they have there)
The screen of the phone will give you two options once you run the unlocking command. Choose Unlock the bootloader using volume buttons.
Press the Power button to confirm your selection.
your bootloader is now unlocked happy rooting
Click to expand...
Click to collapse
At first, tks for all.
I tried to root with your informations but always get the same information, they say I don't have permition to do anything else.
"FAILED (remote: 'Token Verify Failed, Reboot the device')
in fastboot: error: Command failed
in ADB token error still the same.
Some other Idea to try help will be appreciated
Sorry my bad english.
int211 said:
At first, tks for all.
I tried to root with your informations but always get the same information, they say I don't have permition to do anything else.
"FAILED (remote: 'Token Verify Failed, Reboot the device')
in fastboot: error: Command failed
in ADB token error still the same.
Some other Idea to try help will be appreciated
Sorry my bad english.
Click to expand...
Click to collapse
You must unlock bootloader first
Does uypur phone show the authorization popup when you connect for adb and have you allowed always allow this device?
What are you all talking about in this thread?
There is NO WAY to initially unlock the bootloader without MI account, phoning home and waiting 167+hours.
PERIOD. let that sink in.
int211 said:
Pleas guys, is there a way to put this device in DIAG MODE or a rom modified to get root without MI account?
Click to expand...
Click to collapse
Whatever you want to do after that, requires this step before. There is no "root without MI account".