Unlock bootloader without installing MiUnlock - Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe

Hello, is it possible to unlock the bootloader without having to install MiUnlock.
I am using Linux and I am stuck at this step:
Code:
$ fastboot eom unlock
FAILED (remote: Token Verify Failed, Reboot the device)
Is it possible to get the token from Xiaomi's website (giving the IMEI of the phone) and simply do:
Code:
$ fastboot eom unlock TOKEN
I feel that installing a whole program to get a simple token is too much... Also Linux is not officially supported.
Thank you

lapwat said:
Hello, is it possible to unlock the bootloader without having to install MiUnlock.
I am using Linux and I am stuck at this step:
Code:
$ fastboot eom unlock
FAILED (remote: Token Verify Failed, Reboot the device)
Is it possible to get the token from Xiaomi's website (giving the IMEI of the phone) and simply do:
Code:
$ fastboot eom unlock TOKEN
I feel that installing a whole program to get a simple token is too much... Also Linux is not officially supported.
Thank you
Click to expand...
Click to collapse
I've spent a lifetime searching for the same option, but no there is no other way but to use MiUnlock. Anyway, there is not a need for you to install anything, you just need to run the program and let it do its job.

Related

help to unlock bootloader after relocked

I want to unlock bootloader for my device to install a cook rom but when i use the command
Fastboot OEM get_identifier_token
The result window shows and disappears immediately so i can not copy code to unlock my phone.
Please help me. THANKS
Are you trying to use the old token? You have to go back through the unlock process to get a the token identifier and then it should work.

"FAILED (remote: unknown command)" trying to unlock bootloader

Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
This is what I get:
Code:
C:\Minimal ADB and Fastboot>fastboot devices
ZY322MF6XP fastboot
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.000s
I updated drivers and adb and fastboot with no luck.
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
I'd double check that Allow OEM Unlock in dev options is actually on
ZeroPoke said:
I'd double check that Allow OEM Unlock in dev options is actually on
Click to expand...
Click to collapse
Tried it with it on and off twice!
Angelelz said:
Tried it with it on and off twice!
Click to expand...
Click to collapse
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
H0LT3R said:
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
Click to expand...
Click to collapse
Yeah, can't get the unique identifier though, that particular command is not working for me. Anyone have any idea why?
Hi,
For Working this command "Fastboot oem get_unlock_data"
First you need to remove or delete your phone's SCREEN LOCKS like your fingerprint, face-unlock, pattern or password etc... And keep on NONE option in lock screen. After all above procedure done than, You run that commend "Fastboot oem get_unlock_data". After runing thant command, You will not get "FAILED (remote: unknown command)"
It will work 200%.
PRUTHVIRAJ S VASUDEV said:
It will work 200%.
Click to expand...
Click to collapse
no. it doesnt.
It depends on your fastboot version. Please check "fastboot --version" and post it here.
---------- Post added at 03:49 AM ---------- Previous post was at 03:44 AM ----------
...or try "fastboot oem help". This option will show you whether this command is available.
hi!
i have same problem.
product: Lenovo TB-7504x
fastboot getvar info:
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: WT98997_LTEROW
version-preloader: 0.1.00
version: 0.5
PS: Allow OEM Unlock in developer options is actually on
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
renforrest-EX said:
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
Click to expand...
Click to collapse
same
Did you try another USB port? Some users reported that USB 3.0 did not work but 2.0.
I would be willing to bet this is happening on devices that are not allowed to be unlocked. Like those purchased from a phone company.
its been a week since i'm trying on my htc 10, but getting the same error, i tried,
- delete the drivers and re-install
- delete sync manager
- enabled debug & oem unlock
- done reset factory for the phone
- change USB ports and cables
- tried 3 latops
nothing works, sometimes i'll just the error "waiting for any phone" and other times "FAILED (remote: unknown command)"
Angelelz said:
Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
FAILED (remote: unknown command)
finished. total time: 0.000s[/CODE]
I updated drivers and adb and fastboot with no luck.
Try fastboot oem unlock first, then fastboot oem get_unlock_data
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
Click to expand...
Click to collapse
Try fastboot oem unlock first then fastboot oem get_unlock_data
I'm following a tutorial and obviously got stuck and the very same step as you did. And presumably you are following a tutorial, too.
1. Go to Security Settings and remove device lock (PIN, fingerprint, whatever you are using) and set it to NONE.
2. Go to Developer Settings and Unlock Bootloader. (If you skip step 1., you'll be asked to unlock your device here, but find that the Unlocking failed afterwards. Hence, go to step 1. and remove the lock first.)
3. fastboot oem unlock
Done. (Bootloader is unlocked now. Confirm via boot to fastboot mode (Volume down + Power button))
fastboot oem get_unlock_data is probably removed (deprecated) and maybe you don't even need a key from the manufacturer to unlock anymore.
gelignite said:
maybe you don't even need a key from the manufacturer to unlock anymore.
Click to expand...
Click to collapse
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
WoKoschekk said:
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
Click to expand...
Click to collapse
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
gelignite said:
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
Click to expand...
Click to collapse
Moto E4 is a developer's device without a locked bootloader. I thought you were talking about a Moto G6.
Baronstragen said:
Try fastboot oem unlock first then fastboot oem get_unlock_data
Click to expand...
Click to collapse
fastboot oem unlock worked for me

OEM unlocking

Hello,
I have a brand new Xperia XZ1 Compact (G8441) and I'm setting out to install LineageOS on it.
I understand the first step is to unlock the bootloader. I have followed Sony's instructions here but I get this error when I run the fastboot unlock command:
./fastboot oem unlock 0xE8475F4F6417A194B (I also tried without the 0x)
FAILED (remote: 'Incorrect format for unlock data')
I then tried following a different article at getdroidtips but I get this error:
./fastboot -i 0x0fce oem unlock 0xE8475F4F6417A194B
fastboot: invalid option -- i
I'm also confused if I even have to run the above commands because I managed to enable "OEM Unlock" from the Developer options menu. This OEM Unlock option wasn't initially visible when I first enabled Developer Options so I'm curious why it suddenly appeared.
Any help would be greatly appreciated, thank you!
I was able to get it to work on a windows machine, after installing this:
[Tool] Latest ADB Fastboot and USB Driver installer tool for Windows
All praise and All Thanks to God ADB Fastboot and USB Driver installer tool for Windows, which will always install the latest version. To update the adb fastboot and usb drivers again, just rerun the tool. OS Requirements: Windows 7 and Above...
forum.xda-developers.com
u can also do it using flashtool thats how i did it

Question Oneplus 10 Pro Lock Bootloader

Hi, i wanted to relock my Bootloader again. I deinstalled Magisk per app , did a factory reset and now i should be able to do Fastboot oem Lock in adb or not ? Cause i get failure every Time i try that its an unknown command. Can someone Help me mabye?
Edit like that, Reboot Bootloader work but then from there on not.
C:\adb2>adb reboot bootloader
C:\adb2>fastboot oem lock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
We used fastboot flashing unlock to unlock bootloader so I guess you need to use
Fastboot flashing lock
yes that was it thank you much

How do I unlock the bootloader??

So I can't seem to get the phone's bootloader to unlock... using the official tool, v.7.6, in the log I see its trying to execute "fastboot oem get-token" but the phone doesn't react to the command and just says "FAILED (remote: 'unknown command')" What should I do about it???
So I found a solution, you have to download v.5.5.1224.27, any other version doesn't work, it has to be this specific one.

Categories

Resources