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!
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.
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.
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.
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.
Having the same problem with Redmi 4X. It gives "Can't get info, connect again" error. I will try it again in 2-3 days and see if it works.
ytkimirti said:
Having the same problem with Redmi 4X. It gives "Can't get info, connect again" error. I will try it again in 2-3 days and see if it works.
Click to expand...
Click to collapse
Could you try clicking on the settings icon and looking at the logs to see if you’ve got the same unknown command error?
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
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.
Same here
I want unlock redmi 5a
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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?
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 (Edit:-I tried it but it also doesn't work)
Is there any other unofficial app to unlock bootloader of redmi devices except xiaomi unlock tool v2
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.
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
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 ?
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/
Sulina01 said:
I got it from here:
https://xiaomitools.com/download/mi-flash-unlock-tool-v5-5-224-55/
Click to expand...
Click to collapse
Thanks! I'll try it out when I get a chance and let you all know if it helps. Have you tried this one @Kumar7873 ?
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.
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
Related
I'm trying to allow bootloader unlock but keep getting the error above. I've seen various posts on this in the past but am still stumped after doing the following :
- the phone is an xperia Z3 compact
- enabled Developer options
- enabled USB debugging
- allowed installation of apps from unknown sources
- set 'Install software' with USB Connectivity
- unlocked sim (network unlocked)
- received unlock code from Sony
- running software on Ubuntu linux
Commands I've run
=================
fastboot -i 0x0fce oem unlock 0xB9D9999DF99BDB9A
...
FAILED (remote: Command not allowed)
finished. total time: 0.003s
[email protected]:~# fastboot getvar version
version: 0.5
finished. total time: 0.002s
[email protected]:~# fastboot devices
YT9110A9BX fastboot
Anybody got any other ideas ? Thanks in advance.
I think the problem is that the setting of "Bootloader unlock allowed: No" can't be unset other than by Sony. I have contacted them but I'm not holding my breath.
Need help to unlock bootloader. Htcdev website says get_identifier_token. Issue command in fastboot and I get C:\Users\Dvine\Desktop\ADB>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.107s]
finished. total time: 0.123s
There seems to be 2 fastboot modes. One when I reboot to bootloader and I get fastboot to detect device. Different message than in the download mode, it has a recovery like menu but the options are different. There is one for usb-debug mode which just reboots the phone. I get the killswitch message in download mode, in the white screen after reboot bootloader I get C:\Users\Dvine\Desktop\ADB>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.037s
3days of playing in adb shell and there is no root shell. adb root dose nothing nor an error. adb shell, then su gives an error that it dosen't exists. Anything to point me in some direction would be awesome
Update
DvineGem said:
Need help to unlock bootloader. Htcdev website says get_identifier_token. Issue command in fastboot and I get C:\Users\Dvine\Desktop\ADB>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.107s]
finished. total time: 0.123s
There seems to be 2 fastboot modes. One when I reboot to bootloader and I get fastboot to detect device. Different message than in the download mode, it has a recovery like menu but the options are different. There is one for usb-debug mode which just reboots the phone. I get the killswitch message in download mode, in the white screen after reboot bootloader I get C:\Users\Dvine\Desktop\ADB>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.037s
3days of playing in adb shell and there is no root shell. adb root dose nothing nor an error. adb shell, then su gives an error that it dosen't exists. Anything to point me in some direction would be awesome
Click to expand...
Click to collapse
So I have found that the root user UID is 1000. ADB shell id: uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(ad
b),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),300
6(net_bw_stats) context=u:r:shell:s0
Hi, I am wondering how to unlock my Xiaomi Redmi 4X. I don't know I 'm doing wrong. Maybe you know what I'm supposed to do. I will attach MiUnlock error screen and log.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Logs from Mi Unlock:
2019-10-5 Version:3.5.910.35 Process<00000CA0> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Begin List Enviroment Variables.
=C:=C:\
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Marcin\AppData\Roaming
CommonProgramFiles=C:\Program Files (x86)\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=DESKTOP-SO4ICA5
ComSpec=C:\Windows\system32\cmd.exe
DriverData=C:\Windows\System32\Drivers\DriverData
HOMEDRIVE=C:
HOMEPATH=\Users\Marcin
LOCALAPPDATA=C:\Users\Marcin\AppData\Local
LOGONSERVER=\\DESKTOP-SO4ICA5
NUMBER_OF_PROCESSORS=12
OneDrive=C:\Users\Marcin\OneDrive
OS=Windows_NT
Path=C:\VulkanSDK\1.1.121.2\Bin;C:\Python37\;C:\Python37\Scripts\;C:\Python27\;C:\Python27\Scripts;C:\MSYS64\mingw64\bin;C:\Program Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\dotnet\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Program Files\Git\cmd;C:\MinGW\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin;C:\Program Files\CMake\bin;C:\Ninja;D:\Programy\Apktool;D:\Programy\dex2jar-2.0;C:\AndroidSDK\platform-tools;C:\Users\Marcin\AppData\Local\Microsoft\WindowsApps
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_ARCHITEW6432=AMD64
PROCESSOR_IDENTIFIER=AMD64 Family 23 Model 8 Stepping 2, AuthenticAMD
PROCESSOR_LEVEL=23
PROCESSOR_REVISION=0802
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files (x86)
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules;C:\Program Files\Microsoft Message Analyzer\PowerShell\
PUBLIC=C:\Users\Public
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\Marcin\AppData\Local\Temp
TMP=C:\Users\Marcin\AppData\Local\Temp
USERDOMAIN=DESKTOP-SO4ICA5
USERDOMAIN_ROAMINGPROFILE=DESKTOP-SO4ICA5
USERNAME=Marcin
USERPROFILE=C:\Users\Marcin
VK_SDK_PATH=C:\VulkanSDK\1.1.121.2
VULKAN_SDK=C:\VulkanSDK\1.1.121.2
windir=C:\Windows
__COMPAT_LAYER=Installer
End List Enviroment Variables.
Process list:
AGMService.exe AGSService.exe AdobeUpdateService.exe ApplicationFrameHost.exe BrMfcMon.exe BrMfcWnd.exe BrccMCtl.exe Discord.exe GamingServices.exe GamingServicesNet.exe GoogleUpdate.exe LMIGuardianSvc.exe LockApp.exe LsaIso.exe Memory Compression MiPhoneHelper.exe MsMpEng.exe NVDisplay.Container.exe NVIDIA Web Helper.exe NisSrv.exe ProtonVPNService.exe Registry RtkNGUI64.exe RuntimeBroker.exe SearchIndexer.exe SearchUI.exe Secure System SecurityHealthService.exe SecurityHealthSystray.exe SettingSyncHost.exe SgrmBroker.exe ShellExperienceHost.exe SkypeApp.exe SkypeBackgroundHost.exe StartMenuExperienceHost.exe Steam.exe SteamService.exe System SystemSettings.exe TeamViewer_Service.exe VSSVC.exe WUDFHost.exe WmiApSrv.exe WmiPrvSE.exe YourPhone.exe [System Process] armsvc.exe audiodg.exe chrome.exe conhost.exe csrss.exe ctfmon.exe dllhost.exe dwm.exe explorer.exe fontdrvhost.exe hamachi-2-ui.exe hamachi-2.exe lsass.exe miflash_unlock.exe nvcontainer.exe remoting_host.exe services.exe sihost.exe smartscreen.exe smss.exe software_reporter_tool.exe spoolsv.exe steamwebhelper.exe svchost.exe taskhostw.exe unsecapp.exe usocoreworker.exe vmcompute.exe vmmem wininit.exe winlogon.exe
DEBUG <12:46:04.166,T:6284> : miflash_unlock start
DEBUG <12:46:05.296,T:6160> : auto refresh device list
DEBUG <12:46:05.299,T:6160> : use desp:Urządzenie kompozytowe USB instead of Android
DEBUG <12:46:05.301,T:6160> : use desp:Android Composite ADB Interface instead of ADB Interface
DEBUG <12:46:05.304,T:6160> : new usb\vid_2717&pid_ff48\37a1deb27d74
INFO <12:46:05.304,T:6160> : fastboot devices
DEBUG <12:46:21.823,T:6160> : auto refresh device list
INFO <12:46:21.829,T:6160> : fastboot devices
DEBUG <12:46:21.897,T:6160> : auto refresh device list
INFO <12:46:21.903,T:6160> : fastboot devices
DEBUG <12:46:38.184,T:5916> : Login success and get user detail
DEBUG <12:46:38.603,T:5916> : WA_AccountLogin
DEBUG <12:46:38.603,T:6284> : WA_AccountLogin
DEBUG <12:46:38.603,T:6284> : get set_check_page msg
DEBUG <12:46:38.604,T:6284> : longin page switch to check page
DEBUG <12:46:38.604,T:13444> : check right function start
DEBUG <12:46:40.508,T:13444> : Begin login unlockApi
DEBUG <12:46:42.453,T:13444> : End login unlockApi
INFO <12:46:45.372,T:13444> : status result: {
"applyStatus" : 2,
"code" : 0,
"description" : null,
"shouldApply" : false,
"uid" : "1794168327"
}
WARNING<12:46:45.373,T:13444> : missing uid in unlock status json
DEBUG <12:46:45.373,T:13444> : unlock status: 2
DEBUG <12:46:45.373,T:13444> : should apply:false
DEBUG <12:47:18.907,T:6160> : auto refresh device list
DEBUG <12:47:18.910,T:6160> : use desp:Urządzenie kompozytowe USB instead of Android
DEBUG <12:47:18.913,T:6160> : new usb\vid_2717&pid_ff48\37a1deb27d74
INFO <12:47:18.913,T:6160> : fastboot devices
DEBUG <12:47:18.985,T:6160> : auto refresh device list
DEBUG <12:47:18.987,T:6160> : use desp:Urządzenie kompozytowe USB instead of Android
DEBUG <12:47:18.989,T:6160> : use desp:Android Composite ADB Interface instead of ADB Interface
DEBUG <12:47:18.992,T:6160> : changed usb\vid_2717&pid_ff48\37a1deb27d74
INFO <12:47:18.992,T:6160> : fastboot devices
DEBUG <12:47:19.041,T:6160> : auto refresh device list
DEBUG <12:47:19.043,T:6160> : use desp:Urządzenie kompozytowe USB instead of Android
DEBUG <12:47:19.045,T:6160> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO <12:47:19.048,T:6160> : fastboot devices
DEBUG <12:47:23.980,T:6160> : auto refresh device list
DEBUG <12:47:23.983,T:6160> : use desp:Urządzenie kompozytowe USB instead of Android
DEBUG <12:47:23.984,T:6160> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO <12:47:23.987,T:6160> : fastboot devices
DEBUG <12:47:24.038,T:6160> : auto refresh device list
DEBUG <12:47:24.040,T:6160> : use desp:Urządzenie kompozytowe USB instead of Android
DEBUG <12:47:24.042,T:6160> : use desp:Android Composite ADB Interface instead of ADB Interface
INFO <12:47:24.044,T:6160> : fastboot devices
DEBUG <12:48:02.996,T:6160> : auto refresh device list
INFO <12:48:03.007,T:6160> : fastboot devices
DEBUG <12:48:13.403,T:6160> : auto refresh device list
DEBUG <12:48:13.409,T:6160> : use desp:Android Bootloader Interface instead of Android
DEBUG <12:48:13.416,T:6160> : new usb\vid_18d1&pid_d00d\37a1deb27d74
INFO <12:48:13.416,T:6160> : fastboot devices
DEBUG <12:48:13.476,T:6160> : auto refresh device list
DEBUG <12:48:13.477,T:13948> : -s 37a1deb27d74 oem device-info
DEBUG <12:48:13.479,T:6160> : use desp:Android Bootloader Interface instead of Android
INFO <12:48:13.481,T:6160> : fastboot devices
DEBUG <12:48:13.535,T:6160> : auto scan usb in 1 second.
DEBUG <12:48:13.537,T:13948> : ...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
.HłJp˙xą˛±™
DEBUG <12:48:13.537,T:13948> : getvar product -s 37a1deb27d74
DEBUG <12:48:13.592,T:13948> : product: santoni
finished. total time: 0.001s
=ČłtŽ
DEBUG <12:48:13.593,T:13948> : getvar tokenversion -s 37a1deb27d74
DEBUG <12:48:13.640,T:13948> : tokenversion: 37a1deb2
finished. total time: 0.001s
INFO <12:48:13.640,T:13948> : tokenversion: 37a1deb2
finished. total time: 0.001s
DEBUG <12:48:13.640,T:13948> : oem get_token -s 37a1deb27d74
DEBUG <12:48:13.684,T:13948> : ...
FAILED (remote: unknown command)
finished. total time: 0.001s
INFO <12:48:13.684,T:13948> : ...
FAILED (remote: unknown command)
finished. total time: 0.001s
INFO <12:48:13.684,T:13948> :
DEBUG <12:48:13.684,T:13948> : to check erase feature for 37a1deb27d74
DEBUG <12:48:14.542,T:6160> : use desp:Android Bootloader Interface instead of Android
INFO <12:48:14.549,T:6160> : fastboot devices
DEBUG <12:48:20.791,T:13948> : An unlocked device is an easy target for malware which may damage your device or cause financial loss.
DEBUG <12:48:24.481,T:6284> : User click unlock button!
DEBUG <12:48:30.407,T:13948> : -s 37a1deb27d74 oem device-info
DEBUG <12:48:30.458,T:13948> : ...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
Qߌ0¦Ż‡·Ů˛r
DEBUG <12:48:35.407,T:13948> : VerifyDeviceInfo
INFO <12:48:35.408,T:13948> : product:santoni
DEBUG <12:48:35.408,T:13948> : getvar tokenversion -s 37a1deb27d74
DEBUG <12:48:35.471,T:13948> : tokenversion: 37a1deb2
finished. total time: 0.001s
INFO <12:48:35.471,T:13948> : tokenversion: 37a1deb2
finished. total time: 0.001s
DEBUG <12:48:35.471,T:13948> : oem get_token -s 37a1deb27d74
DEBUG <12:48:35.514,T:13948> : ...
FAILED (remote: unknown command)
finished. total time: 0.001s
INFO <12:48:35.514,T:13948> : ...
FAILED (remote: unknown command)
finished. total time: 0.001s
INFO <12:48:35.514,T:13948> :
WARNING<12:48:35.514,T:13948> : Cannot get token.
I assume you've already turned on USB debugging,logged in into Mi account in developers option also turned on OEM unlocking too and if not then turn them on and try again.
Usually it takes 72 Hours to unlock or maybe more. so wait and try again later. you should get what exact time you need to wait for in mi unlock tools.
sometimes using different version of mi unlock tools helps.
also several people often face issue with server issue for unlocking.
one need to send request to xiaomi to unlock bootloader from same account which is logged in into phone, upon approval from xiaomi then bootloader can be unlock. but i think rending bootloader unlocking requests are no longer needed because few months back i was able to unlock my two friends Redmi note 4X and Redmi 3S after 72 hours of waiting time before that it was getting stuck on 99% and then would immediately fail with message could not unlock.
metelhammer said:
I assume you've already turned on USB debugging,logged in into Mi account in developers option also turned on OEM unlocking too and if not then turn them on and try again.
Usually it takes 72 Hours to unlock or maybe more. so wait and try again later. you should get what exact time you need to wait for in mi unlock tools.
sometimes using different version of mi unlock tools helps.
also several people often face issue with server issue for unlocking.
one need to send request to xiaomi to unlock bootloader from same account which is logged in into phone, upon approval from xiaomi then bootloader can be unlock. but i think rending bootloader unlocking requests are no longer needed because few months back i was able to unlock my two friends Redmi note 4X and Redmi 3S after 72 hours of waiting time before that it was getting stuck on 99% and then would immediately fail with message could not unlock.
Click to expand...
Click to collapse
I tried to unlock the bootloader a few months earlier, but with the same error. I tried different versions of Mi Unlock tools without effect. Finally, I unlocked the bootloader using the unofficial "XiaoMiTool V2"!
M4rc1nV said:
I tried to unlock the bootloader a few months earlier, but with the same error. I tried different versions of Mi Unlock tools without effect. Finally, I unlocked the bootloader using the unofficial "XiaoMiTool V2"!
Click to expand...
Click to collapse
That is good to know you've now bootloader unlocked on your Redmi 4X.
I was able to unlock bootloader official way on Redmi note 3 (Snapdragon variant ), Redmi 4X, Redmi note 4X(Snapdragon variant), and Redmi 3S. all of them could not got unlocked in first attempt and all of them was needed to be unlocked after 72 Hours of waiting period. in my case i was able to unlock them after 72 hours because on very fourth day i unlocked.
My guess,maybe in your case the gap of few months could have been barrier because after 72 hours of waiting time i (at least me) have not seen anyone having issue with unlocking and were able to unlock it successfully.
Anyways, now you have unlocked bootloader on your phone. enjoy. cheers!
This question is probably xiaomi-related as a whole, but I didn't find a dedicated forum for xiaomi.
After a week of waiting I try to unlock my Xiaomi Redmi Note 10 Pro and get "Unknown error(-1)" in the unlocker app.
Here's the relevant part of the log:
Code:
DEBUG 22:39:58.050,T:5568 : manual refresh device list
DEBUG 22:39:58.050,T:1624 : manaul refresh device list
DEBUG 22:39:58.053,T:1624 : use desp:Android Bootloader Interface instead of Android
DEBUG 22:39:58.056,T:1624 : new usb\vid_18d1&pid_d00d\{SERIAL}
INFO 22:39:58.056,T:1624 : fastboot devices
DEBUG 22:39:58.098,T:7420 : -s {SERIAL} oem device-info
DEBUG 22:39:58.140,T:7420 : (bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.000s]
Finished. Total time: 0.000s
DEBUG 22:39:58.140,T:7420 : getvar product -s {SERIAL}
DEBUG 22:39:58.181,T:7420 : product: sweet
Finished. Total time: 0.000s
DEBUG 22:39:59.062,T:5568 : manual refresh device list
DEBUG 22:39:59.062,T:1624 : manaul refresh device list
DEBUG 22:39:59.062,T:7420 : -s {SERIAL} oem device-info
DEBUG 22:39:59.065,T:1624 : use desp:Android Bootloader Interface instead of Android
INFO 22:39:59.068,T:1624 : fastboot devices
DEBUG 22:39:59.107,T:7420 : (bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
Finished. Total time: 0.001s
DEBUG 22:39:59.277,T:7420 : VerifyDeviceInfo
INFO 22:39:59.278,T:7420 : product:sweet
DEBUG 22:39:59.278,T:7420 : getvar tokenversion -s {SERIAL}
DEBUG 22:39:59.321,T:7420 : getvar:tokenversion FAILED (remote: 'GetVar Variable Not found')
Finished. Total time: 0.000s
INFO 22:39:59.321,T:7420 : getvar:tokenversion FAILED (remote: 'GetVar Variable Not found')
Finished. Total time: 0.000s
INFO 22:39:59.321,T:7420 : tokenversion=0
DEBUG 22:39:59.321,T:7420 : oem get_token -s {SERIAL}
DEBUG 22:39:59.363,T:7420 : FAILED (remote: 'unknown command')
fastboot: error: Command failed
INFO 22:39:59.363,T:7420 : FAILED (remote: 'unknown command')
fastboot: error: Command failed
DEBUG 22:39:59.363,T:7420 : getvar token -s {SERIAL}
DEBUG 22:39:59.403,T:7420 : token: {TOKEN}
Finished. Total time: 0.000s
INFO 22:39:59.403,T:7420 : token: {TOKEN}
Finished. Total time: 0.000s
DEBUG 22:39:59.403,T:7420 : to sign token with key for device:sweet
DEBUG 22:39:59.405,T:7420 : Begin login unlockApi
ERROR 22:40:00.857,T:7420 : 2 req url https://ru-unlock.update.intl.miui.com/{USERDATA}
ERROR 22:40:00.858,T:7420 : 2 req cookie
DEBUG 22:40:01.880,T:7420 : End login unlockApi
ERROR 22:42:03.500,T:7420 : net err:-1 url:https://ru-unlock.update.intl.miui.com/api/v3/ahaUnlock
DEBUG 22:42:03.500,T:7420 : unlock return:-1 msg:
Personal info like serial number and unlock token have been replaced with all caps in curly braces.
Looks like a problem on the backend of xiaomi. One of the two REST API calls fails.
Yes I added my account and ticked "OEM Unlock" in developer settings.
Any help or thoughts on the matter would be appreciated.
selamba said:
This question is probably xiaomi-related as a whole, but I didn't find a dedicated forum for xiaomi.
After a week of waiting I try to unlock my Xiaomi Redmi Note 10 Pro and get "Unknown error(-1)" in the unlocker app.
Here's the relevant part of the log:
Code:
DEBUG 22:39:58.050,T:5568 : manual refresh device list
DEBUG 22:39:58.050,T:1624 : manaul refresh device list
DEBUG 22:39:58.053,T:1624 : use desp:Android Bootloader Interface instead of Android
DEBUG 22:39:58.056,T:1624 : new usb\vid_18d1&pid_d00d\{SERIAL}
INFO 22:39:58.056,T:1624 : fastboot devices
DEBUG 22:39:58.098,T:7420 : -s {SERIAL} oem device-info
DEBUG 22:39:58.140,T:7420 : (bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.000s]
Finished. Total time: 0.000s
DEBUG 22:39:58.140,T:7420 : getvar product -s {SERIAL}
DEBUG 22:39:58.181,T:7420 : product: sweet
Finished. Total time: 0.000s
DEBUG 22:39:59.062,T:5568 : manual refresh device list
DEBUG 22:39:59.062,T:1624 : manaul refresh device list
DEBUG 22:39:59.062,T:7420 : -s {SERIAL} oem device-info
DEBUG 22:39:59.065,T:1624 : use desp:Android Bootloader Interface instead of Android
INFO 22:39:59.068,T:1624 : fastboot devices
DEBUG 22:39:59.107,T:7420 : (bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
Finished. Total time: 0.001s
DEBUG 22:39:59.277,T:7420 : VerifyDeviceInfo
INFO 22:39:59.278,T:7420 : product:sweet
DEBUG 22:39:59.278,T:7420 : getvar tokenversion -s {SERIAL}
DEBUG 22:39:59.321,T:7420 : getvar:tokenversion FAILED (remote: 'GetVar Variable Not found')
Finished. Total time: 0.000s
INFO 22:39:59.321,T:7420 : getvar:tokenversion FAILED (remote: 'GetVar Variable Not found')
Finished. Total time: 0.000s
INFO 22:39:59.321,T:7420 : tokenversion=0
DEBUG 22:39:59.321,T:7420 : oem get_token -s {SERIAL}
DEBUG 22:39:59.363,T:7420 : FAILED (remote: 'unknown command')
fastboot: error: Command failed
INFO 22:39:59.363,T:7420 : FAILED (remote: 'unknown command')
fastboot: error: Command failed
DEBUG 22:39:59.363,T:7420 : getvar token -s {SERIAL}
DEBUG 22:39:59.403,T:7420 : token: {TOKEN}
Finished. Total time: 0.000s
INFO 22:39:59.403,T:7420 : token: {TOKEN}
Finished. Total time: 0.000s
DEBUG 22:39:59.403,T:7420 : to sign token with key for device:sweet
DEBUG 22:39:59.405,T:7420 : Begin login unlockApi
ERROR 22:40:00.857,T:7420 : 2 req url https://ru-unlock.update.intl.miui.com/{USERDATA}
ERROR 22:40:00.858,T:7420 : 2 req cookie
DEBUG 22:40:01.880,T:7420 : End login unlockApi
ERROR 22:42:03.500,T:7420 : net err:-1 url:https://ru-unlock.update.intl.miui.com/api/v3/ahaUnlock
DEBUG 22:42:03.500,T:7420 : unlock return:-1 msg:
Personal info like serial number and unlock token have been replaced with all caps in curly braces.
Looks like a problem on the backend of xiaomi. One of the two REST API calls fails.
Yes I added my account and ticked "OEM Unlock" in developer settings.
Any help or thoughts on the matter would be appreciated.
Click to expand...
Click to collapse
Try the Xiaomi official unlock tool
Laptapper said:
Try the Xiaomi official unlock tool
Click to expand...
Click to collapse
That's what I've been doing
Code:
ERROR 22:42:03.500,T:7420 : net err:-1 url:https://ru-unlock.update.intl.miui.com/api/v3/ahaUnlock
If you go to this url in your browser, it will ask for defaul http sign in. Curious. Entering my mi account credentials didn't work.
Hi, compatriot.
I have solved absolutely same issue, but with Poco X3 Pro, with version 5.5.0224.55 of Mi Unlock tool.
Яндекс
Найдётся всё
disk.yandex.ru
xjr00t said:
I have solved absolutely same issue, but with Poco X3 Pro, with version 5.5.0224.55 of Mi Unlock tool.
Яндекс
Найдётся всё
disk.yandex.ru
Click to expand...
Click to collapse
I registered on XDA Developers just to appreciate this comment.
Mi Unlock Tool 5.5.0224.55 solved my booloader unlock issue with Xiaomi Redmi 10.
Hello i have problem with the mi9 of my friend
her phone seems to be block in boot process...we can see the Mi logo and the android power up with 3 points moving like if it is starting but nothing happens...
we let it starting for one complete night nothing has changed.
I can access to recovery mode pushing volume up + start button...i could do swap data but she doesn't want to loose some phone call records cause their is the voice of her last chat with her mum passed away some months ago...
for now what i know :
- her phone doesn't have the usb debugging options activated ;(
- when i connect the phone to my pc it doesn't recognized and appears on my pc
- i tried the miassitsant option in the recovery mode but mipcsuite doesn't see it too...
- not sure a mi account was created on her phone...she said she think we did one but the infos( id andpass was kept on a sms on her phone LOL)
so for now the only thing i see is that, in adb, when i typed .\adb devices i can see a number with "sideload" written beside it....does it help to find a way to modify the boot.img for an update or to transferts files from the phone to my pc?
question more : what is the path for phone calls recorded in a MI9? maybe i could use a push or pull option in adb?
i thought aboput contacting xiaomi for unlock the phone but as it seems to be blocked in boot mode i don't now if it would change something
i hope you understood well my poor english
please help ...
If it can help here is what i have when i used the miflash program
""""""""""""""""""""""""""""""""""""""
AGMService.exe AGSService.exe Adobe CEF Helper.exe Adobe Desktop Service.exe AdobeIPCBroker.exe AdobeUpdateService.exe ApplicationFrameHost.exe AudialsNotifier.exe BdVpnService.exe CCXProcess.exe CCleaner64.exe CCleanerBrowserCrashHandler.exe CCleanerBrowserCrashHandler64.exe Calculator.exe CefSharp.BrowserSubprocess.exe Creative Cloud.exe Dashboard.Service.exe Dashboard.exe DiscoverySrv.exe EpicGamesLauncher.exe EpicWebHelper.exe HPPrintScanDoctorService.exe LockApp.exe Memory Compression MiPhoneHelper.exe MoUsoCoreWorker.exe Music.UI.exe NVDisplay.Container.exe OfficeClickToRun.exe OneDrive.exe ProductAgentService.exe Registry RtkNGUI64.exe RuntimeBroker.exe ScanToPCActivationApp.exe Scheduler.exe ScpService.exe ScpTrayApp.exe SearchApp.exe SearchFilterHost.exe SearchIndexer.exe SearchProtocolHost.exe SecurityHealthService.exe SecurityHealthSystray.exe SettingSyncHost.exe SgrmBroker.exe ShellExperienceHost.exe StartMenuExperienceHost.exe SwUSB.exe System SystemSettings.exe TextInputHost.exe UserOOBEBroker.exe Video.UI.exe WUDFHost.exe WmiPrvSE.exe YourPhone.exe [System Process] adb.exe armsvc.exe audiodg.exe bdagent.exe bdntwrk.exe bdredline.exe bdservicehost.exe bdvpnapp.exe conhost.exe csrss.exe ctfmon.exe dasHost.exe dllhost.exe dwm.exe ensserver.exe explorer.exe fontdrvhost.exe lsass.exe lync.exe miflash_unlock.exe node.exe runSW.exe services.exe sihost.exe smartscreen.exe smss.exe spoolsv.exe svchost.exe taskhostw.exe unsecapp.exe updatesrv.exe wininit.exe winlogon.exe
DEBUG <10:37:18.136,T:16292> : miflash_unlock start
DEBUG <10:37:18.684,T:13176> : auto refresh device list
DEBUG <10:37:18.699,T:13176> : use bus desp:MI 9 instead of Android ADB Interface
DEBUG <10:37:18.715,T:13176> : new usb\vid_18d1&pid_4e11\d9995836
INFO <10:37:18.715,T:13176> : fastboot devices
WARNING<10:37:24.212,T:16292> : account loading error:-21
DEBUG <10:37:24.946,T:16292> : [0]End: data:text/html,chromewebdata
DEBUG <10:37:25.261,T:13176> : auto refresh device list
DEBUG <10:37:25.268,T:13176> : use bus desp:MI 9 instead of Android ADB Interface
INFO <10:37:25.272,T:13176> : fastboot devices
ERROR <10:37:31.387,T:13168> : http get error code[curl]:6
INFO <10:37:48.319,T:1116> : new app version:6.5.406.31 url:http://miuirom.xiaomi.com/rom/u1106245679/6.5.406.31/miflash_unlock-en-6.5.406.31.zip
DEBUG <10:37:50.540,T:13176> : auto refresh device list
DEBUG <10:37:50.556,T:13176> : use desp:Android Bootloader Interface instead of Android
DEBUG <10:37:50.571,T:13176> : remove usb\vid_18d1&pid_4e11\d9995836
DEBUG <10:37:50.571,T:13176> : new usb\vid_18d1&pid_d00d\d9995836
INFO <10:37:50.571,T:13176> : fastboot devices
DEBUG <10:37:50.656,T:15372> : -s d9995836 oem device-info
DEBUG <10:37:50.756,T:15372> : ...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
DEBUG <10:37:50.756,T:15372> : getvar product -s d9995836
DEBUG <10:37:50.841,T:15372> : product: cepheus
finished. total time: 0.000s
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""
i tried to download files from devices but not sure of the path where the voice records are saved :
adb pull [-l] /internal share storage/MIUI/sound_recorder/call_rec/
adb pull [-l] /MIUI/sound_recorder/call_rec/
is the path correct?