[HELP] Unable to unlock bootloader

Search This thread
By:
Advanced…
R

ro-jc

Member
Mar 27, 2022
7
1
This is my first time posting on this forum, please do correct me if I'm doing something wrong or haven't provided some information I should have.

I have a Redmi 4 running MIUI Global 11.0.2 (NAMMIXM) which is about four years old and whose bootloader I've been trying to unlock for the past 2-3 days and running into issues.

I run linux on the system I use on a day to day basis, so my first option was XiaoMiTool V2. I enabled developer options, OEM unlocking, added my account in the Mi Unlock Status option and logged in successfully from within the tool but while running the operation to unlock the bootloader through it, I hit an error telling me that there was a serviceToken that was missing. I did find a thread on here that linked to a github issue for the tool, which recommends changing a line (or a few) in the source code and rebuilding the tool. I'm yet to try this, but I figured finding a windows laptop and using the official tool may be easier.

I got my hands on a laptop running windows 10 Pro and downloaded the mi unlock tool version 6.5.224.28 from the official website which when launched prompted me to get the latest version which was apparently 6.5.314.30. After logging in and fumbling around with the drivers for a bit, I got it to recognize my device in the fastboot mode and it finished verifying my device and launched the unlocking process but stopped when it reached 99% with the error "Can't get info, connect again". That's when I found some threads suggesting I enable Mi Cloud and Find My Device and did that, to no avail.

I logged into my Mi account in a browser and located my phone through it as a thread suggested and waited for more than a day (again, what seemed to have worked for someone in the thread). This time I tried with my PC with a clean install of windows 10 dual booted with linux. I still get the same thing error about not getting info, even using drivers installed using a previous version of Mi Unlock tool (the latest one seemed to be missing the program to install the drivers). I tried unlocking with previous versions of this tool too (3.5.1108.44, 4.5.813.51) but with them, on logging in I would just be taken to what seemed like would be my Mi Account page and left there with no obvious indication as to what I'm expected to do next - just connecting my device in the fastboot mode didn't seem to do anything.

I had a look at the logs of the Mi Unlock tool (latest version) :
Code: 
2022-3-27 Version:6.5.314.30 Process<00003708> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Begin List Enviroment Variables.
...
DEBUG  <16:43:16.635,T:13496> : Login success and get user detail
DEBUG  <16:43:16.702,T:13496> : WA_AccountLogin
DEBUG  <16:43:16.702,T:14344> : WA_AccountLogin
DEBUG  <16:43:16.702,T:14344> : get set_check_page msg
DEBUG  <16:43:16.704,T:14344> : longin page switch to check page
DEBUG  <16:43:16.704,T:5844> : check right function start
DEBUG  <16:43:18.091,T:5844> : sign result:{
   "code" : 0,
   "descCN" : "成功",
   "descEN" : "success",
   "description" : "成功"
}

DEBUG  <16:43:31.699,T:14032> : auto refresh device list
DEBUG  <16:43:31.703,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:31.705,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
DEBUG  <16:43:31.709,T:14032> : new  usb\vid_2717&pid_ff48\6b803337d440
INFO   <16:43:31.709,T:14032> : fastboot devices
DEBUG  <16:43:31.816,T:14032> : auto refresh device list
DEBUG  <16:43:31.819,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:31.821,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO   <16:43:31.824,T:14032> : fastboot devices
DEBUG  <16:43:31.931,T:14032> : auto refresh device list
DEBUG  <16:43:31.933,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:31.936,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO   <16:43:31.938,T:14032> : fastboot devices
DEBUG  <16:43:32.102,T:14032> : auto refresh device list
DEBUG  <16:43:32.106,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:32.108,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO   <16:43:32.111,T:14032> : fastboot devices
DEBUG  <16:43:37.662,T:14032> : auto refresh device list
INFO   <16:43:37.668,T:14032> : fastboot devices
DEBUG  <16:43:37.803,T:14032> : auto refresh device list
INFO   <16:43:37.807,T:14032> : fastboot devices
DEBUG  <16:43:43.906,T:14032> : auto refresh device list
DEBUG  <16:43:43.909,T:14032> : use desp:Android Bootloader Interface instead of Android
DEBUG  <16:43:43.912,T:14032> : new  usb\vid_18d1&pid_d00d\6b803337d440
INFO   <16:43:43.912,T:14032> : fastboot devices
DEBUG  <16:43:44.024,T:14032> : auto refresh device list
DEBUG  <16:43:44.025,T:13616> : -s 6b803337d440 oem device-info
DEBUG  <16:43:44.027,T:14032> : use desp:Android Bootloader Interface instead of Android
INFO   <16:43:44.029,T:14032> : fastboot devices
DEBUG  <16:43:44.165,T:13616> : (bootloader)     Device tampered: false
(bootloader)     Device unlocked: false
(bootloader)     Device critical unlocked: false
(bootloader)     Charger screen enabled: true
(bootloader)     Display panel: Ò’ƒ¾§EÈò5gggíxŠz ‰§fžÿ…§ÍåÊ3†”ÓMí£
OKAY [  0.006s]
Finished. Total time: 0.006s
DEBUG  <16:43:44.165,T:13616> :  getvar product -s 6b803337d440
DEBUG  <16:43:44.271,T:13616> : product: santoni
Finished. Total time: 0.001s
DEBUG  <16:43:44.272,T:13616> :  getvar tokenversion -s 6b803337d440
DEBUG  <16:43:44.384,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:44.384,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:44.384,T:13616> : tokenversion=6
DEBUG  <16:43:44.384,T:13616> :  oem get_token -s 6b803337d440
DEBUG  <16:43:44.612,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
INFO   <16:43:44.613,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
DEBUG  <16:43:44.613,T:13616> : to check erase feature for 6b803337d440
DEBUG  <16:43:44.615,T:13616> : Begin login unlockApi
ERROR  <16:43:46.310,T:13616> : 2 req url https://in-unlock.update.intl.miui.com/sts?d=bl_01f3e0e93ab5329dab777a9b453ac160&ticket=0&pwd=0&p_ts=1648379597000&fid=0&p_lm=2&auth=ALRhbCOwLwCVP4G8%2B0HGkyQJdN4UyJTLqcT%2FXwe0aZEIJ5gYJh7CgdEmYOyxwrtV1uFDOJ1YJF126OUqwXUTBK7EWkaiOs%2FF099ycMzhxjyTcwoySarBgXJq1hrfb7CNIgfCpo5%2Fejs7agoSOw69KB9XyjXbZThnEhC0V4g0V8g%3D&m=4&tsl=1&nonce=s5orK%2FNcr%2BgBozRh&_ssign=YFNhkFVWn%2FAUc6bTqDP1yWN9A68%3D&clientSign=xb1TM%2Fhxp16l5gPlyyiEEW7uZsg%3D
ERROR  <16:43:46.310,T:13616> : 2 req cookie
DEBUG  <16:43:46.615,T:13616> : End login unlockApi
DEBUG  <16:43:46.981,T:13616> : An unlocked device is an easy target for malware which may damage your device or cause financial loss.
DEBUG  <16:43:49.177,T:14344> : User click unlock button!
DEBUG  <16:43:54.794,T:13616> : -s 6b803337d440 oem device-info
DEBUG  <16:43:54.929,T:13616> : (bootloader)     Device tampered: false
(bootloader)     Device unlocked: false
(bootloader)     Device critical unlocked: false
(bootloader)     Charger screen enabled: true
(bootloader)     Display panel: Ò’ƒ¾§EÈò5gggíxŠz ‰§fžÿ…§ÍåÊ3†”ÓMí£
OKAY [  0.006s]
Finished. Total time: 0.006s
DEBUG  <16:43:59.808,T:13616> : VerifyDeviceInfo
INFO   <16:43:59.809,T:13616> : product:santoni
DEBUG  <16:43:59.810,T:13616> :  getvar tokenversion -s 6b803337d440
DEBUG  <16:43:59.948,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:59.948,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:59.948,T:13616> : tokenversion=6
DEBUG  <16:43:59.948,T:13616> :  oem get_token -s 6b803337d440
DEBUG  <16:44:00.058,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
INFO   <16:44:00.058,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
WARNING<16:44:00.058,T:13616> : Cannot get token.
INFO   <16:44:29.472,T:15240> : new app version:6.5.314.30 url:http://miuirom.xiaomi.com/rom/u1106245679/6.5.314.30/miflash_unlock-en-6.5.314.30.zip
DEBUG  <16:46:19.529,T:14032> : auto refresh device list
DEBUG  <16:46:19.537,T:14032> : remove usb\vid_18d1&pid_d00d\6b803337d440
INFO   <16:46:19.537,T:14032> : fastboot devices
DEBUG  <16:46:27.971,T:14344> : Close app after cef_close
DEBUG  <16:46:27.990,T:14344> : miflash_unlock exit
From what I can make out from it, it seems to me that running the oem command get_token is the point of failure but unfortunately, I have no idea what that command does or is supposed to do. I have tried running the fastboot commands that the log indicated that the tool was running from a powershell/command prompt window and they give me the same results (one thing I did notice while trying out some commands was that running "fastboot getvar all" seemed to give me a set of variables, one of which was called "token", but I'm not sure if that's relevant here).
I'm not sure how to go ahead diagnosing from here as I couldn't find much information about the oem commands of Xiaomi devices. I'm not sure if there's some step I'm missing in the process or if the latest version of the tool has something different that just doesn't work with my device.

I would greatly appreciate any help on this, either with things to do that might fix the issue or even just references to pages that might clear things up regarding the error I'm getting. Please do let me know if there's any other information I have to provide.

Thank you!
 
metelhammer

metelhammer

Senior Member
Jan 18, 2018
377
93
I assume you've logged in your same account as in your device and in mi unlock tools.
Also you have enabled OEM unlocking and USB debugging on in developers options if not then please go to developers options and turn them on.

skip this if you've already enabled this, to enable developers options got to settings > about phone > tap several times on MIUI version. you'll see developers options in settings > additional settings > developers options and then enable OEM unlocking and USB debugging.

you'll need to add your mi account in mi unlocking status(sometimes account doesn't get added due to server issues so try again with mobile data or through different Wi-Fi network )

After adding your mi account now try again unlocking bootloader again.
To do that shut down your device boot into fastboot mode by holding volume down and power button together.
connect your device to pc and open mi unlock tools log in with same mi account as in your device and then unlock it. you should get your device bootloader unlocked. if in case you get errors like stuck on 50% 99% or if it asked to wait for 48hours/72hours then you'll have to wait for that much of time and try again later and then it'll get unlocked.

for me back in 2017 when i bought Redmi 4X it was 72 hours of waiting time and later after waiting time got over it was got unlocked instantly.
 
R

ro-jc

Member
Mar 27, 2022
7
1
Thank you for the reply.

I went through all the steps that you mentioned right from my first attempt at unlocking the boot loader and have made sure that OEM unlocking and USB debugging have stayed on.

I have added my mi account in the mi unlocking status too, and done so multiple times (using mobile data each time, according to the instructions given on the mi unlock status page), having received confirmation that it was added each time (I even tried logging out and back in to my mi account a few times, before adding it in the mi unlocking status again of course).

If I had got a wait time, I would be happy to wait but unfortunately I haven’t received one, which leaves me unsure of whether just waiting will solve the issue. Each time it stops and fails at 99% and gives me the error described in my first post.
 
  • Like
Reactions: Hasan Khurshid
metelhammer

metelhammer

Senior Member
Jan 18, 2018
377
93
ro-jc said:
Thank you for the reply.

I went through all the steps that you mentioned right from my first attempt at unlocking the boot loader and have made sure that OEM unlocking and USB debugging have stayed on.

I have added my mi account in the mi unlocking status too, and done so multiple times (using mobile data each time, according to the instructions given on the mi unlock status page), having received confirmation that it was added each time (I even tried logging out and back in to my mi account a few times, before adding it in the mi unlocking status again of course).

If I had got a wait time, I would be happy to wait but unfortunately I haven’t received one, which leaves me unsure of whether just waiting will solve the issue. Each time it stops and fails at 99% and gives me the error described in my first post.
Click to expand...
Click to collapse
As you are getting stuck at 99% error that means you'll be able to unlock it soon, just don't try unlocking often. please wait for the gap of at least around 48 hours or so and then try again.
this is known error since xiaomi introduced bootloader locking and i am surprised that it is not yet solved.
I've also had this stuck at 99% issue as far as i remember i tried unlocking a day after and i got my device unlocked.
this happens often due to server issue from server.
 
R

ro-jc

Member
Mar 27, 2022
7
1
metelhammer said:
As you are getting stuck at 99% error that means you'll be able to unlock it soon, just don't try unlocking often. please wait for the gap of at least around 48 hours or so and then try again.
this is known error since xiaomi introduced bootloader locking and i am surprised that it is not yet solved.
I've also had this stuck at 99% issue as far as i remember i tried unlocking a day after and i got my device unlocked.
this happens often due to server issue from server.
Click to expand...
Click to collapse
I did try giving it a day without any attempts to unlock the first time I tried, but I’ll give it a break for 2-3 days and try again as you said. But I have a feeling(because of the logs) that this time around, it may not help…


Do you know of any possible explanation to what‘s happening in the logs of the Mi Unlock tool that I have attached?
I have a feeling that the latest version of the unlock tool may have made a change to the process of getting a certain token(whose purpose I have no idea about) from the device. It seems to be trying to use a fastboot oem command “get_token” which my device does not seem to support (or is it the expected behaviour maybe when the account is not bound properly?) but turns out a newer device does have it. I tried running the command with a redmi note 8 pro connected and it gave me an output in place of the error that I get with my device while running the same command.

I also dug around in the source code and logs of the open source XiaomiToolV2 and from what I could gather, it uses “getvar token” which does work for my device (though running it on the note 8 pro gives me an output which seems to be most parts of what’s returned by oem get_token and some other character joined together).
I also tried the workaround for the tool from the github issue and it seemed to fix the problem of the missing serviceToken(change in login url). But now I get the same error which I got with version 5 of the mi unlock tool (Please use the common tool). I’m wondering if this error is because of some fairly recent change in the url to which the unlock requests are directed to(?)….but I could be very wrong about that.
 
ytkimirti

ytkimirti

New member
Mar 30, 2022
2
0
Xiaomi Redmi 4X
Code: 
Finished. Total time: 0.001s
DEBUG  <18:12:23.162,T:12488> :  getvar tokenversion -s 6dc90507d440
DEBUG  <18:12:23.276,T:12488> : tokenversion: 6dc9050
Finished. Total time: 0.001s
INFO   <18:12:23.277,T:12488> : tokenversion: 6dc9050
Finished. Total time: 0.001s
INFO   <18:12:23.277,T:12488> : tokenversion=6
DEBUG  <18:12:23.277,T:12488> :  oem get_token -s 6dc90507d440
DEBUG  <18:12:23.530,T:12488> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
INFO   <18:12:23.531,T:12488> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
DEBUG  <18:12:23.531,T:12488> : to check erase feature for 6dc90507d440
DEBUG  <18:12:23.539,T:12488> : Begin login unlockApi
DEBUG  <18:12:24.063,T:11976> : use desp:Android Bootloader Interface instead of Android
INFO   <18:12:24.069,T:11976> : fastboot devices
ERROR  <18:12:24.413,T:12488> : 2 req url https://unlock.update.intl.miui.com/sts?d=bl_474db0fac78a405a60fac4862185ca78&ticket=0&pwd=0&p_ts=1648652084000&fid=0&p_lm=1&auth=VBZJI%2BwJ3NMzbSUIiH5%2Fau56FAhs8nHr1fNW%2BG9nlHLDt1cABt6ghFHvzuL8KBz2Ee7MQ4ixw5iJ0Wxf7jWfaCP%2BRn2JsxYhCA0LwXwrHs99%2FRcKSAvdaD1hrCq8Ou%2BpcbG6kzdv7KIe440%2BwipvEskho18AWPFMBoknX7P2lhA%3D&m=1025&tsl=1&nonce=67NTHhX4z8UBo0Yw&_ssign=p5SbP7wm2mgNoKe4p7nv8%2Fu5Cxo%3D&clientSign=M9GSiuewC2pKysGyYFcy1tx%2BmtY%3D
ERROR  <18:12:24.413,T:12488> : 2 req cookie
DEBUG  <18:12:25.443,T:12488> : End login unlockApi
DEBUG  <18:12:27.155,T:12488> : An unlocked device is an easy target for malware which may damage your device or cause financial loss.
DEBUG  <18:12:34.149,T:2472> : User click unlock button!
DEBUG  <18:12:46.171,T:12488> : -s 6dc90507d440 oem device-info
DEBUG  <18:12:46.300,T:12488> : (bootloader)     Device tampered: false
(bootloader)     Device unlocked: false
(bootloader)     Device critical unlocked: false
(bootloader)     Charger screen enabled: true
(bootloader)     Display panel: 48ğH1Äã…¾cÕ1¾€¢:YåÂn‘yíû:Õê¾aó˜o
mɺ
OKAY [  0.006s]
Finished. Total time: 0.007s
Yep, the same error
 
R

ro-jc

Member
Mar 27, 2022
7
1
I’m doubtful we’ll be able to unlock an mi 4 with this version of the tool. And they seemed to have changed something about the unlock process too since the previous versions. Version 5 asks me to use the common user tool. And so does the XiaomiTool V2.
 
Last edited:
H

Hasan Khurshid

Member
Jul 2, 2018
30
0
Same here
I want unlock redmi 5a
Untitled.png
 
H

HurricaneAikas

New member
Apr 25, 2022
1
0
ro-jc said:
This is my first time posting on this forum, please do correct me if I'm doing something wrong or haven't provided some information I should have.

I have a Redmi 4 running MIUI Global 11.0.2 (NAMMIXM) which is about four years old and whose bootloader I've been trying to unlock for the past 2-3 days and running into issues.

I run linux on the system I use on a day to day basis, so my first option was XiaoMiTool V2. I enabled developer options, OEM unlocking, added my account in the Mi Unlock Status option and logged in successfully from within the tool but while running the operation to unlock the bootloader through it, I hit an error telling me that there was a serviceToken that was missing. I did find a thread on here that linked to a github issue for the tool, which recommends changing a line (or a few) in the source code and rebuilding the tool. I'm yet to try this, but I figured finding a windows laptop and using the official tool may be easier.

I got my hands on a laptop running windows 10 Pro and downloaded the mi unlock tool version 6.5.224.28 from the official website which when launched prompted me to get the latest version which was apparently 6.5.314.30. After logging in and fumbling around with the drivers for a bit, I got it to recognize my device in the fastboot mode and it finished verifying my device and launched the unlocking process but stopped when it reached 99% with the error "Can't get info, connect again". That's when I found some threads suggesting I enable Mi Cloud and Find My Device and did that, to no avail.

I logged into my Mi account in a browser and located my phone through it as a thread suggested and waited for more than a day (again, what seemed to have worked for someone in the thread). This time I tried with my PC with a clean install of windows 10 dual booted with linux. I still get the same thing error about not getting info, even using drivers installed using a previous version of Mi Unlock tool (the latest one seemed to be missing the program to install the drivers). I tried unlocking with previous versions of this tool too (3.5.1108.44, 4.5.813.51) but with them, on logging in I would just be taken to what seemed like would be my Mi Account page and left there with no obvious indication as to what I'm expected to do next - just connecting my device in the fastboot mode didn't seem to do anything.

I had a look at the logs of the Mi Unlock tool (latest version) :
Code: 
2022-3-27 Version:6.5.314.30 Process<00003708> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Begin List Enviroment Variables.
...
DEBUG  <16:43:16.635,T:13496> : Login success and get user detail
DEBUG  <16:43:16.702,T:13496> : WA_AccountLogin
DEBUG  <16:43:16.702,T:14344> : WA_AccountLogin
DEBUG  <16:43:16.702,T:14344> : get set_check_page msg
DEBUG  <16:43:16.704,T:14344> : longin page switch to check page
DEBUG  <16:43:16.704,T:5844> : check right function start
DEBUG  <16:43:18.091,T:5844> : sign result:{
   "code" : 0,
   "descCN" : "成功",
   "descEN" : "success",
   "description" : "成功"
}

DEBUG  <16:43:31.699,T:14032> : auto refresh device list
DEBUG  <16:43:31.703,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:31.705,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
DEBUG  <16:43:31.709,T:14032> : new  usb\vid_2717&pid_ff48\6b803337d440
INFO   <16:43:31.709,T:14032> : fastboot devices
DEBUG  <16:43:31.816,T:14032> : auto refresh device list
DEBUG  <16:43:31.819,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:31.821,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO   <16:43:31.824,T:14032> : fastboot devices
DEBUG  <16:43:31.931,T:14032> : auto refresh device list
DEBUG  <16:43:31.933,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:31.936,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO   <16:43:31.938,T:14032> : fastboot devices
DEBUG  <16:43:32.102,T:14032> : auto refresh device list
DEBUG  <16:43:32.106,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:32.108,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO   <16:43:32.111,T:14032> : fastboot devices
DEBUG  <16:43:37.662,T:14032> : auto refresh device list
INFO   <16:43:37.668,T:14032> : fastboot devices
DEBUG  <16:43:37.803,T:14032> : auto refresh device list
INFO   <16:43:37.807,T:14032> : fastboot devices
DEBUG  <16:43:43.906,T:14032> : auto refresh device list
DEBUG  <16:43:43.909,T:14032> : use desp:Android Bootloader Interface instead of Android
DEBUG  <16:43:43.912,T:14032> : new  usb\vid_18d1&pid_d00d\6b803337d440
INFO   <16:43:43.912,T:14032> : fastboot devices
DEBUG  <16:43:44.024,T:14032> : auto refresh device list
DEBUG  <16:43:44.025,T:13616> : -s 6b803337d440 oem device-info
DEBUG  <16:43:44.027,T:14032> : use desp:Android Bootloader Interface instead of Android
INFO   <16:43:44.029,T:14032> : fastboot devices
DEBUG  <16:43:44.165,T:13616> : (bootloader)     Device tampered: false
(bootloader)     Device unlocked: false
(bootloader)     Device critical unlocked: false
(bootloader)     Charger screen enabled: true
(bootloader)     Display panel: Ò’ƒ¾§EÈò5gggíxŠz ‰§fžÿ…§ÍåÊ3†”ÓMí£
OKAY [  0.006s]
Finished. Total time: 0.006s
DEBUG  <16:43:44.165,T:13616> :  getvar product -s 6b803337d440
DEBUG  <16:43:44.271,T:13616> : product: santoni
Finished. Total time: 0.001s
DEBUG  <16:43:44.272,T:13616> :  getvar tokenversion -s 6b803337d440
DEBUG  <16:43:44.384,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:44.384,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:44.384,T:13616> : tokenversion=6
DEBUG  <16:43:44.384,T:13616> :  oem get_token -s 6b803337d440
DEBUG  <16:43:44.612,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
INFO   <16:43:44.613,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
DEBUG  <16:43:44.613,T:13616> : to check erase feature for 6b803337d440
DEBUG  <16:43:44.615,T:13616> : Begin login unlockApi
ERROR  <16:43:46.310,T:13616> : 2 req url https://in-unlock.update.intl.miui.com/sts?d=bl_01f3e0e93ab5329dab777a9b453ac160&ticket=0&pwd=0&p_ts=1648379597000&fid=0&p_lm=2&auth=ALRhbCOwLwCVP4G8%2B0HGkyQJdN4UyJTLqcT%2FXwe0aZEIJ5gYJh7CgdEmYOyxwrtV1uFDOJ1YJF126OUqwXUTBK7EWkaiOs%2FF099ycMzhxjyTcwoySarBgXJq1hrfb7CNIgfCpo5%2Fejs7agoSOw69KB9XyjXbZThnEhC0V4g0V8g%3D&m=4&tsl=1&nonce=s5orK%2FNcr%2BgBozRh&_ssign=YFNhkFVWn%2FAUc6bTqDP1yWN9A68%3D&clientSign=xb1TM%2Fhxp16l5gPlyyiEEW7uZsg%3D
ERROR  <16:43:46.310,T:13616> : 2 req cookie
DEBUG  <16:43:46.615,T:13616> : End login unlockApi
DEBUG  <16:43:46.981,T:13616> : An unlocked device is an easy target for malware which may damage your device or cause financial loss.
DEBUG  <16:43:49.177,T:14344> : User click unlock button!
DEBUG  <16:43:54.794,T:13616> : -s 6b803337d440 oem device-info
DEBUG  <16:43:54.929,T:13616> : (bootloader)     Device tampered: false
(bootloader)     Device unlocked: false
(bootloader)     Device critical unlocked: false
(bootloader)     Charger screen enabled: true
(bootloader)     Display panel: Ò’ƒ¾§EÈò5gggíxŠz ‰§fžÿ…§ÍåÊ3†”ÓMí£
OKAY [  0.006s]
Finished. Total time: 0.006s
DEBUG  <16:43:59.808,T:13616> : VerifyDeviceInfo
INFO   <16:43:59.809,T:13616> : product:santoni
DEBUG  <16:43:59.810,T:13616> :  getvar tokenversion -s 6b803337d440
DEBUG  <16:43:59.948,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:59.948,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:59.948,T:13616> : tokenversion=6
DEBUG  <16:43:59.948,T:13616> :  oem get_token -s 6b803337d440
DEBUG  <16:44:00.058,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
INFO   <16:44:00.058,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
WARNING<16:44:00.058,T:13616> : Cannot get token.
INFO   <16:44:29.472,T:15240> : new app version:6.5.314.30 url:http://miuirom.xiaomi.com/rom/u1106245679/6.5.314.30/miflash_unlock-en-6.5.314.30.zip
DEBUG  <16:46:19.529,T:14032> : auto refresh device list
DEBUG  <16:46:19.537,T:14032> : remove usb\vid_18d1&pid_d00d\6b803337d440
INFO   <16:46:19.537,T:14032> : fastboot devices
DEBUG  <16:46:27.971,T:14344> : Close app after cef_close
DEBUG  <16:46:27.990,T:14344> : miflash_unlock exit
From what I can make out from it, it seems to me that running the oem command get_token is the point of failure but unfortunately, I have no idea what that command does or is supposed to do. I have tried running the fastboot commands that the log indicated that the tool was running from a powershell/command prompt window and they give me the same results (one thing I did notice while trying out some commands was that running "fastboot getvar all" seemed to give me a set of variables, one of which was called "token", but I'm not sure if that's relevant here).
I'm not sure how to go ahead diagnosing from here as I couldn't find much information about the oem commands of Xiaomi devices. I'm not sure if there's some step I'm missing in the process or if the latest version of the tool has something different that just doesn't work with my device.

I would greatly appreciate any help on this, either with things to do that might fix the issue or even just references to pages that might clear things up regarding the error I'm getting. Please do let me know if there's any other information I have to provide.

Thank you!
Click to expand...
Click to collapse
Hey. I'm also affected by this issue. I have waited about a week before trying to unlock the bootloader again, but with no success. Have you tried to unlock your bootloader recently?
 
Kumar7873

Kumar7873

New member
Apr 29, 2022
4
1
Same issue here i am also trying to unlock bootloader in my Redmi 4x but i also get the same error can't get device info and stuck at 99%.I think maybe we can unlock the bootloader by flashing the phone to the oldest miui supported which i think is miui 8 by using edl mode and then by using platform tools and command prompt (Note:- I have not tried this yet but i think it will work)
 
S

Sulina01

New member
Apr 29, 2022
3
0
Kumar7873 said:
Same issue here i am also trying to unlock bootloader in my Redmi 4x but i also get the same error can't get device info and stuck at 99%.I think maybe we can unlock the bootloader by flashing the phone to the oldest miui supported which i think is miui 8 by using edl mode and then by using platform tools and command prompt (Note:- I have not tried this yet but i think it will work)
Click to expand...
Click to collapse
Did you try this : https://forum.xda-developers.com/t/...r-security-issues-stuck.4414465/post-86714179
I had the same "can't get info, connect again" problem and it worked for me.
 
Kumar7873

Kumar7873

New member
Apr 29, 2022
4
1
ro-jc said:
This is my first time posting on this forum, please do correct me if I'm doing something wrong or haven't provided some information I should have.

I have a Redmi 4 running MIUI Global 11.0.2 (NAMMIXM) which is about four years old and whose bootloader I've been trying to unlock for the past 2-3 days and running into issues.

I run linux on the system I use on a day to day basis, so my first option was XiaoMiTool V2. I enabled developer options, OEM unlocking, added my account in the Mi Unlock Status option and logged in successfully from within the tool but while running the operation to unlock the bootloader through it, I hit an error telling me that there was a serviceToken that was missing. I did find a thread on here that linked to a github issue for the tool, which recommends changing a line (or a few) in the source code and rebuilding the tool. I'm yet to try this, but I figured finding a windows laptop and using the official tool may be easier.

I got my hands on a laptop running windows 10 Pro and downloaded the mi unlock tool version 6.5.224.28 from the official website which when launched prompted me to get the latest version which was apparently 6.5.314.30. After logging in and fumbling around with the drivers for a bit, I got it to recognize my device in the fastboot mode and it finished verifying my device and launched the unlocking process but stopped when it reached 99% with the error "Can't get info, connect again". That's when I found some threads suggesting I enable Mi Cloud and Find My Device and did that, to no avail.

I logged into my Mi account in a browser and located my phone through it as a thread suggested and waited for more than a day (again, what seemed to have worked for someone in the thread). This time I tried with my PC with a clean install of windows 10 dual booted with linux. I still get the same thing error about not getting info, even using drivers installed using a previous version of Mi Unlock tool (the latest one seemed to be missing the program to install the drivers). I tried unlocking with previous versions of this tool too (3.5.1108.44, 4.5.813.51) but with them, on logging in I would just be taken to what seemed like would be my Mi Account page and left there with no obvious indication as to what I'm expected to do next - just connecting my device in the fastboot mode didn't seem to do anything.

I had a look at the logs of the Mi Unlock tool (latest version) :
Code: 
2022-3-27 Version:6.5.314.30 Process<00003708> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Begin List Enviroment Variables.
...
DEBUG  <16:43:16.635,T:13496> : Login success and get user detail
DEBUG  <16:43:16.702,T:13496> : WA_AccountLogin
DEBUG  <16:43:16.702,T:14344> : WA_AccountLogin
DEBUG  <16:43:16.702,T:14344> : get set_check_page msg
DEBUG  <16:43:16.704,T:14344> : longin page switch to check page
DEBUG  <16:43:16.704,T:5844> : check right function start
DEBUG  <16:43:18.091,T:5844> : sign result:{
   "code" : 0,
   "descCN" : "成功",
   "descEN" : "success",
   "description" : "成功"
}

DEBUG  <16:43:31.699,T:14032> : auto refresh device list
DEBUG  <16:43:31.703,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:31.705,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
DEBUG  <16:43:31.709,T:14032> : new  usb\vid_2717&pid_ff48\6b803337d440
INFO   <16:43:31.709,T:14032> : fastboot devices
DEBUG  <16:43:31.816,T:14032> : auto refresh device list
DEBUG  <16:43:31.819,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:31.821,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO   <16:43:31.824,T:14032> : fastboot devices
DEBUG  <16:43:31.931,T:14032> : auto refresh device list
DEBUG  <16:43:31.933,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:31.936,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO   <16:43:31.938,T:14032> : fastboot devices
DEBUG  <16:43:32.102,T:14032> : auto refresh device list
DEBUG  <16:43:32.106,T:14032> : use desp:USB Composite Device instead of Android
DEBUG  <16:43:32.108,T:14032> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO   <16:43:32.111,T:14032> : fastboot devices
DEBUG  <16:43:37.662,T:14032> : auto refresh device list
INFO   <16:43:37.668,T:14032> : fastboot devices
DEBUG  <16:43:37.803,T:14032> : auto refresh device list
INFO   <16:43:37.807,T:14032> : fastboot devices
DEBUG  <16:43:43.906,T:14032> : auto refresh device list
DEBUG  <16:43:43.909,T:14032> : use desp:Android Bootloader Interface instead of Android
DEBUG  <16:43:43.912,T:14032> : new  usb\vid_18d1&pid_d00d\6b803337d440
INFO   <16:43:43.912,T:14032> : fastboot devices
DEBUG  <16:43:44.024,T:14032> : auto refresh device list
DEBUG  <16:43:44.025,T:13616> : -s 6b803337d440 oem device-info
DEBUG  <16:43:44.027,T:14032> : use desp:Android Bootloader Interface instead of Android
INFO   <16:43:44.029,T:14032> : fastboot devices
DEBUG  <16:43:44.165,T:13616> : (bootloader)     Device tampered: false
(bootloader)     Device unlocked: false
(bootloader)     Device critical unlocked: false
(bootloader)     Charger screen enabled: true
(bootloader)     Display panel: Ò’ƒ¾§EÈò5gggíxŠz ‰§fžÿ…§ÍåÊ3†”ÓMí£
OKAY [  0.006s]
Finished. Total time: 0.006s
DEBUG  <16:43:44.165,T:13616> :  getvar product -s 6b803337d440
DEBUG  <16:43:44.271,T:13616> : product: santoni
Finished. Total time: 0.001s
DEBUG  <16:43:44.272,T:13616> :  getvar tokenversion -s 6b803337d440
DEBUG  <16:43:44.384,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:44.384,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:44.384,T:13616> : tokenversion=6
DEBUG  <16:43:44.384,T:13616> :  oem get_token -s 6b803337d440
DEBUG  <16:43:44.612,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
INFO   <16:43:44.613,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
DEBUG  <16:43:44.613,T:13616> : to check erase feature for 6b803337d440
DEBUG  <16:43:44.615,T:13616> : Begin login unlockApi
ERROR  <16:43:46.310,T:13616> : 2 req url https://in-unlock.update.intl.miui.com/sts?d=bl_01f3e0e93ab5329dab777a9b453ac160&ticket=0&pwd=0&p_ts=1648379597000&fid=0&p_lm=2&auth=ALRhbCOwLwCVP4G8%2B0HGkyQJdN4UyJTLqcT%2FXwe0aZEIJ5gYJh7CgdEmYOyxwrtV1uFDOJ1YJF126OUqwXUTBK7EWkaiOs%2FF099ycMzhxjyTcwoySarBgXJq1hrfb7CNIgfCpo5%2Fejs7agoSOw69KB9XyjXbZThnEhC0V4g0V8g%3D&m=4&tsl=1&nonce=s5orK%2FNcr%2BgBozRh&_ssign=YFNhkFVWn%2FAUc6bTqDP1yWN9A68%3D&clientSign=xb1TM%2Fhxp16l5gPlyyiEEW7uZsg%3D
ERROR  <16:43:46.310,T:13616> : 2 req cookie
DEBUG  <16:43:46.615,T:13616> : End login unlockApi
DEBUG  <16:43:46.981,T:13616> : An unlocked device is an easy target for malware which may damage your device or cause financial loss.
DEBUG  <16:43:49.177,T:14344> : User click unlock button!
DEBUG  <16:43:54.794,T:13616> : -s 6b803337d440 oem device-info
DEBUG  <16:43:54.929,T:13616> : (bootloader)     Device tampered: false
(bootloader)     Device unlocked: false
(bootloader)     Device critical unlocked: false
(bootloader)     Charger screen enabled: true
(bootloader)     Display panel: Ò’ƒ¾§EÈò5gggíxŠz ‰§fžÿ…§ÍåÊ3†”ÓMí£
OKAY [  0.006s]
Finished. Total time: 0.006s
DEBUG  <16:43:59.808,T:13616> : VerifyDeviceInfo
INFO   <16:43:59.809,T:13616> : product:santoni
DEBUG  <16:43:59.810,T:13616> :  getvar tokenversion -s 6b803337d440
DEBUG  <16:43:59.948,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:59.948,T:13616> : tokenversion: 6b80333
Finished. Total time: 0.001s
INFO   <16:43:59.948,T:13616> : tokenversion=6
DEBUG  <16:43:59.948,T:13616> :  oem get_token -s 6b803337d440
DEBUG  <16:44:00.058,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
INFO   <16:44:00.058,T:13616> : FAILED (remote: 'unknown command')
fastboot: error: Command failed
WARNING<16:44:00.058,T:13616> : Cannot get token.
INFO   <16:44:29.472,T:15240> : new app version:6.5.314.30 url:http://miuirom.xiaomi.com/rom/u1106245679/6.5.314.30/miflash_unlock-en-6.5.314.30.zip
DEBUG  <16:46:19.529,T:14032> : auto refresh device list
DEBUG  <16:46:19.537,T:14032> : remove usb\vid_18d1&pid_d00d\6b803337d440
INFO   <16:46:19.537,T:14032> : fastboot devices
DEBUG  <16:46:27.971,T:14344> : Close app after cef_close
DEBUG  <16:46:27.990,T:14344> : miflash_unlock exit
From what I can make out from it, it seems to me that running the oem command get_token is the point of failure but unfortunately, I have no idea what that command does or is supposed to do. I have tried running the fastboot commands that the log indicated that the tool was running from a powershell/command prompt window and they give me the same results (one thing I did notice while trying out some commands was that running "fastboot getvar all" seemed to give me a set of variables, one of which was called "token", but I'm not sure if that's relevant here).
I'm not sure how to go ahead diagnosing from here as I couldn't find much information about the oem commands of Xiaomi devices. I'm not sure if there's some step I'm missing in the process or if the latest version of the tool has something different that just doesn't work with my device.

I would greatly appreciate any help on this, either with things to do that might fix the issue or even just references to pages that might clear things up regarding the error I'm getting. Please do let me know if there's any other information I have to provide.

Thank you!
Click to expand...
Click to collapse
Bro did you find a way to unlock bootloader? If no then try this method and tell me if it works then i will also do it
 

Attachments

  • Screenshot_2022-05-03-22-24-49-496_com.android.chrome.jpg
    Screenshot_2022-05-03-22-24-49-496_com.android.chrome.jpg
    71.1 KB · Views: 32
R

ro-jc

Member
Mar 27, 2022
7
1
HurricaneAikas said:
Hey. I'm also affected by this issue. I have waited about a week before trying to unlock the bootloader again, but with no success. Have you tried to unlock your bootloader recently?
Click to expand...
Click to collapse
I have not. I did try to see if I could do anything with the xiaomi tool v2 for a bit, but I only got so far as to get the error: "Failed to unlock your device. Please use the common user tool on the official website". After that, I've tried nothing.

Kumar7873 said:
Same issue here i am also trying to unlock bootloader in my Redmi 4x but i also get the same error can't get device info and stuck at 99%.I think maybe we can unlock the bootloader by flashing the phone to the oldest miui supported which i think is miui 8 by using edl mode and then by using platform tools and command prompt (Note:- I have not tried this yet but i think it will work)
Click to expand...
Click to collapse
This seems like a lot of effort for me at the moment, especially cause I don't expect my phone to even last that long anymore. I may try something with this EDL mode eventually, though probably not anytime soon.

Sulina01 said:
Did you try this : https://forum.xda-developers.com/t/...r-security-issues-stuck.4414465/post-86714179
I had the same "can't get info, connect again" problem and it worked for me.
Click to expand...
Click to collapse
This seems promising, though I believe when I had tried that version of the tool, it gave me an error which said: "Failed to unlock your device. Please use the common user tool on the official website". Maybe I got some other version by mistake. Could you please send us a link to somewhere we can download the version that you used to unlock your device @Sulina01 or @Hasan Khurshid ?
 
S

Sulina01

New member
Apr 29, 2022
3
0
ro-jc said:
This seems promising, though I believe when I had tried that version of the tool, it gave me an error which said: "Failed to unlock your device. Please use the common user tool on the official website". Maybe I got some other version by mistake. Could you please send us a link to somewhere we can download the version that you used to unlock your device @Sulina01 or @Hasan Khurshid ?
Click to expand...
Click to collapse
I got it from here:
https://xiaomitools.com/download/mi-flash-unlock-tool-v5-5-224-55/
 
Kilolo

Kilolo

Member
May 20, 2022
7
0
Sulina01 said:
Did you try this : https://forum.xda-developers.com/t/...r-security-issues-stuck.4414465/post-86714179
I had the same "can't get info, connect again" problem and it worked for me.
Click to expand...
Click to collapse
i tried this, and it still having infinite loading despite using QR code

i wonder if there's anyway to unlock the bootloader for my redmi 4x


edit : using connect with facebook work, what the hell. but i couldn't connect from the phone so i had to go into i.mi.com to connect my xiaomi account to facebook.

i could go to the unlock page, but failed at 99% so far because i just realized i used my phone as tethering the whole time so i think i'll need some other wifi source for my laptop.

i'll try again once i get access to a free wifi, things sounds heading into direction so far for me.
 
Last edited:
arelano693

arelano693

New member
May 26, 2022
2
0
This is the message I got while trying to unlock my Redmi Note 10 Pro

The phone has been locked by the account number 189***692 and cannot be unlocked by finding the phone

I've tried almost every MI unlock files, no success
IMG-20220524-WA0001.jpg
 
You must log in or register to reply here.

Similar threads

A
is there anyway to unlock bootloader without permission on miui 10?
Replies
16
Views
23K
Gintarevys
Gintarevys
B
LOCKED bootloader / possible to flash anything?
Replies
21
Views
31K
C
Cataljn
S
[HELP] Phone is stuck at Linux Penguin Logo ( Bootloader, Recovery Not Responding)
Replies
15
Views
19K
shrinath25
shrinath25
P
UNLOCKING Bootloader through oofficial way also VOID warranty ?
Replies
8
Views
7K
pyshydv
pyshydv
Ank_S
Is unlocking bootloader via Linux possible?
Replies
5
Views
6K
bx2nero
bx2nero

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 1
    R
    ro-jc
    Thank you for the reply.

    I went through all the steps that you mentioned right from my first attempt at unlocking the boot loader and have made sure that OEM unlocking and USB debugging have stayed on.

    I have added my mi account in the mi unlocking status too, and done so multiple times (using mobile data each time, according to the instructions given on the mi unlock status page), having received confirmation that it was added each time (I even tried logging out and back in to my mi account a few times, before adding it in the mi unlocking status again of course).

    If I had got a wait time, I would be happy to wait but unfortunately I haven’t received one, which leaves me unsure of whether just waiting will solve the issue. Each time it stops and fails at 99% and gives me the error described in my first post.
    View
    1
    Kumar7873
    Kumar7873
    Is there any other unofficial app to unlock bootloader of redmi devices except xiaomi unlock tool v2
    View

New posts