Prerequisites:
Your PC must be at least Windows 7 Service Pack 1, although you must install every Visual C++ Redistributable Runtime and the Windows Device Recovery Tool.
Your Phone OS version must be at least 8.10.14219.341 or newer. If not, please update it using the windows insider app.
Have registered your device as a developer with the WP SDK.
Remove pin lock and turn off reset protection before the update procedure.
{
"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"
}
:fingers-crossedlease follow this guide at your own risk as I am not responsible for bricked devices, dead SD cards or thermonuclear war:crying:.
Instructions:
1. Backup Your device.
2. Download Iutool (WP_CPTT_NT-x86-fre.msi) from the attachments section and install it. The default install directory will be
Code:
C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
3. Download the M8.Rar that reflects your Carrier and extract the contents to C:\ on your PC.
M8ATT
M8Verizon
M8TMobile
Code:
C:\M8ATT
Code:
C:\M8Verizon
Code:
C:\M8TMobile
4. Open Command Prompt as administratior and change directory to where Iutool is installed.
Code:
cd C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
5. Plug your M8 into your PC and check to see if Iutool discovers your device by typing
Code:
iutool -l
If your device appears then you are ready to continue
If you met error 80070490 when executing iutool -l then disconnect your device and remove it from the Devices & Printers section of Control Panel
6. Assuming you extracted the correct zip into C:\ you are either going to type
Code:
iutool -V -p C:\M8ATT
Code:
iutool -V -p C:\M8Verizon
Code:
iutool -V -p C:\M8TMobile
That command will push the update to your device and it will prepare for the installation! Once the update is ready, take it! You'll want to find something to occupy your time as the process will take 40 minutes.
8. Once booted into W10 open Settings and navigate to the "For Developers" menu and enable Developer Mode.
9. Download and install Interop-Tools from it's respected thread and follow the For All other OEM Devices section to Interop/Cap Unlock your M8 if you had planned on doing so.
Interop-Tools https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
10. Use any method that you know to modify your model(DeviceTargetingInfo) to a supported W10 Mobile Device
11. Now enable Windows insider preview builds and set to either slow or release ring.
12. Go into phone update and search for update. You should be brought to build 14393 or later. Updating to this build will fix critical issues/bugs you met earlier.
13. I also recommend a factory reset after all updates as that will reset Registry values to defaults and fix other things as well.
A HUGE thanks to @hikari_calyx for the Offline Update package V4.1 that he had put together over on the Windows 10 Mobile forums!
Another HUGE thanks to @gus33000 for Interop-Tools!​
RECOMMENDED TO ADD:
1. If you met 80070490 error when executing iutool -l, disconnect your phone, and delete your phone in Device & Printers (Run "control printers") and delete your phone listed on it, then reconnect your phone again.
2. You can also install Mobile Enterprise provisioned package in order to get 10586.753. This provisioned package will be available with my Offline Update Package V4.
3. I also recommended to modify PhoneHardwareVariant to RM-1045 if you are going to modify to L930. You should also modify PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB.
4. Turn off reset protection before update procedure.
hikari_calyx said:
RECOMMENDED TO ADD:
1. If you met 80070490 error when executing iutool -l, disconnect your phone, and delete your phone in Device & Printers (Run "control printers") and delete your phone listed on it, then reconnect your phone again.
2. You can also install Mobile Enterprise provisioned package in order to get 10586.753. This provisioned package will be available with my Offline Update Package V4.
3. I also recommended to modify PhoneHardwareVariant to RM-1045 if you are going to modify to L930. You should also modify PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB.
4. Turn off reset protection before update procedure.
Click to expand...
Click to collapse
PhoneHardwareVariant to RM-1045 if you are going to modify to L930? does this affect anything?
PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB? will this help service? i had not changed these values before updating myself.
AnierinB said:
PhoneHardwareVariant to RM-1045 if you are going to modify to L930? does this affect anything?
PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB? will this help service? i had not changed these values before updating myself.
Click to expand...
Click to collapse
In some case, without modifying them, you can't search any update.
I successfully installed WP 10.0.14393.953 in my HTC M8 and everything seems ok but the in-call volume that is very very low, quite inaudible. Any ideas? Thanks, ALe
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
---------- Post added at 06:50 AM ---------- Previous post was at 06:30 AM ----------
Cashdog53 said:
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
Click to expand...
Click to collapse
Never mind. Fixed the problem by removing my SD card, and restarting the phone I think...
zagreo said:
I successfully installed WP 10.0.14393.953 in my HTC M8 and everything seems ok but the in-call volume that is very very low, quite inaudible. Any ideas? Thanks, ALe
Click to expand...
Click to collapse
ThIs is normal as I've encountered the same issue.
Bugs I know of:
Front facing camera sometimes causes reboot (switching from back in most cases)
Sound will sometimes only go through one speaker (works itself out but happens every now and then)
Flashlight toggle in quick settings has a long delay and sometimes doesn't work at all
Dot view doesn't work (but I personally delete the "extras" apps as the update process somehow made that possible for me)
Other than all that I'm pretty amazed at the way this devices handles the OS... every time I've gone back to 8.1 I'd instantly regret it after the setup
Hi so I tried installing Interops on my WP 10 HTC but for whatever reason it doenst let me install stating i dont have 10.0.14393.953 or higher but if i recall i have 10.0.15xxx.xxx Im not home so i cannot check the actual numbers.
Cokefrevr said:
Hi so I tried installing Interops on my WP 10 HTC but for whatever reason it doenst let me install stating i dont have 10.0.14393.953 or higher but if i recall i have 10.0.15xxx.xxx Im not home so i cannot check the actual numbers.
Click to expand...
Click to collapse
Are you trying to install interop tools via the store? From what I can recall installing the pre release via device hub worked on all builds for me
Cashdog53 said:
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
---------- Post added at 06:50 AM ---------- Previous post was at 06:30 AM ----------
Never mind. Fixed the problem by removing my SD card, and restarting the phone I think...
Click to expand...
Click to collapse
Everything work out?
AnierinB said:
Are you trying to install interop tools via the store? From what I can recall installing the pre release via device hub worked on all builds for me
Click to expand...
Click to collapse
Yea trying to install from the store, sorry for being stupid really tired but device hub?
Cokefrevr said:
Yea trying to install from the store, sorry for being stupid really tired but device hub?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71000190&postcount=607
Download arm dependencies and arm interop tools. Extract and install dependencies one by one via file manager before installing interop tools appx.
Oh and it's called the device portal... here's a link to info on that https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile
AnierinB said:
https://forum.xda-developers.com/showpost.php?p=71000190&postcount=607
Download arm dependencies and arm interop tools. Extract and install dependencies one by one via file manager before installing interop tools appx.
Oh and it's called the device portal... here's a link to info on that https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile
Click to expand...
Click to collapse
Thanks, although it seems to be auto closing, then if i open it again it stays loading and auto closes again.
I've got the same problem installing interop tools i've install the dependencies and the appxbundle but when i try to open the program on the phone it only show a logo for a few seconds and go back to the main screen. Is interop tools the only way to modify the devicetargetinfo ? Please advice.
Cokefrevr said:
Thanks, although it seems to be auto closing, then if i open it again it stays loading and auto closes again.
Click to expand...
Click to collapse
rayxanber said:
I've got the same problem installing interop tools i've install the dependencies and the appxbundle but when i try to open the program on the phone it only show a logo for a few seconds and go back to the main screen. Is interop tools the only way to modify the devicetargetinfo ? Please advice.
Click to expand...
Click to collapse
https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
Follow the for all other OEM Device section. Interop tools has changed a bit since I last used the device.
And yes that reminds me.. In worst case you can't get interop tools to work I'm afraid you'll have to change it before you do the offline update via The modified preview for developer's.. But no worries as the WDRT tool can bring you back to 8.1 NP.
Besides that.. How's the experience with w10 on the m8 for you guys?
AnierinB said:
[*]Your PC must be at least Windows 7 Service Pack 1, but you must install every Visual C++ Redistributable Runtime and Windows Device Recovery Tool. Windows 8/8.1/10 are also acceptable.
Click to expand...
Click to collapse
I found that only 2013 was necessary, and specifically the x86 (not x64, even if you have a 64bit computer and 64bit OS) as iutool is a 32bit binary. This link should also be handy for anyone wanting to install all the Visual C redistributables.
AnierinB said:
(If you met error 80070490 when executing iutool -l, disconnect your phone, and delete your phone from Device & Printers section of control panel. Then reconnect your phone again)
Click to expand...
Click to collapse
This didn't work for me on my main computer. Even after I removed ALL windows devices. I got out a burner laptop, installed Win10 fresh and set up the necessary tools and only then did iutool work for me.
AnierinB said:
Besides that.. How's the experience with w10 on the m8 for you guys?
Click to expand...
Click to collapse
Once I can figure how to get Win10 to update, I'll let you know.
[EDIT] WOW, I just found https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile, that I can upload the app using nothing but a browser. All this time I was thinking I'd have to use the USB cable and find yet another deployment tool.. but I still get the same problem as Cokefrevr and rayxanber in that it always auto-closes or crashes.
[EDIT2] Ok, finally found out that anything beyond the 1.9 beta crashes in this old windows build. At least the 1.9 beta runs... now I need to figure out what this cryptic statement means in terms of steps:
AnierinB said:
11. Use any method that you know to modify your model(DeviceTargetingInfo) to a supported W10 Mobile Device
Click to expand...
Click to collapse
[EDIT3] I found https://windowsinsiderbits.blogspot.com/2017/03/upgrading-unsupported-windows-phone-81.html which led me to the steps:
1. Edit registry HKLM/SYSTEM/Platform/DeviceTargetingInfo changing PhoneManufacturerModelName to RM-1105 and PhoneModelName to "Lumia 950" (taken from http://www.lumiafirmware.com/ )
2. Run the Windows Insider app, select the Insider Slow release (it should automatically reboot)
3. Check for updates in the Settings > Update & security > Phone update
Now I'm finally updated to Version 1607 OS Build 10.0.14393.448
[EDIT4] And now that it's on the current windows version, the Interop Tools from the store can run... but it needs some kind of extensions which I think are what is referenced in the 'Other Device' section, but needs Interop Tools to run before extensions can be side-loaded? That doesn't make much sense. I guess I'm fine with my device saying HTC Lumia 950 until Interop works or I find a better simple registry editor without so many complicated dependencies.
[EDIT5] Looks like the RC beta from the originally linked thread works on this version. I have to say, the self-web-host to install applications is by far the easiest way to side-load apps. I think the only thing I miss by going up to Win10 is the dotview. :crying: I hope some awesome developer makes a dot-view addition to Win10. Oh... looks like it's downloading the 1703 version now...
reukiodo said:
I found that only 2013 was necessary, and specifically the x86 (not x64, even if you have a 64bit computer and 64bit OS) as iutool is a 32bit binary. This link should also be handy for anyone wanting to install all the Visual C redistributables.
This didn't work for me on my main computer. Even after I removed ALL windows devices. I got out a burner laptop, installed Win10 fresh and set up the necessary tools and only then did iutool work for me.
Once I can figure how to get Win10 to update, I'll let you know.
[EDIT] WOW, I just found https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile, that I can upload the app using nothing but a browser. All this time I was thinking I'd have to use the USB cable and find yet another deployment tool.. but I still get the same problem as Cokefrevr and rayxanber in that it always auto-closes or crashes.
[EDIT2] Ok, finally found out that anything beyond the 1.9 beta crashes in this old windows build. At least the 1.9 beta runs... now I need to figure out what this cryptic statement means in terms of steps:
[EDIT3] I found https://windowsinsiderbits.blogspot.com/2017/03/upgrading-unsupported-windows-phone-81.html which led me to the steps:
1. Edit registry HKLM/SYSTEM/Platform/DeviceTargetingInfo changing PhoneManufacturerModelName to RM-1105 and PhoneModelName to "Lumia 950" (taken from http://www.lumiafirmware.com/ )
2. Run the Windows Insider app, select the Insider Slow release (it should automatically reboot)
3. Check for updates in the Settings > Update & security > Phone update
Now I'm finally updated to Version 1607 OS Build 10.0.14393.448
[EDIT4] And now that it's on the current windows version, the Interop Tools from the store can run... but it needs some kind of extensions which I think are what is referenced in the 'Other Device' section, but needs Interop Tools to run before extensions can be side-loaded? That doesn't make much sense. I guess I'm fine with my device saying HTC Lumia 950 until Interop works or I find a better simple registry editor without so many complicated dependencies.
[EDIT5] Looks like the RC beta from the originally linked thread works on this version. I have to say, the self-web-host to install applications is by far the easiest way to side-load apps. I think the only thing I miss by going up to Win10 is the dotview. :crying: I hope some awesome developer makes a dot-view addition to Win10. Oh... looks like it's downloading the 1703 version now...
Click to expand...
Click to collapse
Glad you got it working.. Haven't logged in to xda in a while because i'm using micro g on my Android device so sorry about the absence of help. How you liking it so far? HTC should have supported this huh? p.s lumia 735 works best for device spoofing.. 950 is unnecessary
I'm curious, which phone should I change it to in the registry, to receive updates? To make sure it doesn't break?
Also I'm using Interop Tools 1.9 since apparently, everything after that crashes, and I can't unlock Interop/cap it keep turning off. Do you have any pointers to what I should do?
nar001 said:
I'm curious, which phone should I change it to in the registry, to receive updates? To make sure it doesn't break?
Also I'm using Interop Tools 1.9 since apparently, everything after that crashes, and I can't unlock Interop/cap it keep turning off. Do you have any pointers to what I should do?
Click to expand...
Click to collapse
What carrier do you have? I used an ATT varient and before using the offline update I used the custom preview for developers method to change my device to a lumia 735 on wp 8.1 then did the offline update because interop tools kept failing for me at the time as well. if I remember correctly, you can also use interop tools to change the device targeting info but nothing else if you can't cap unlock/ interop unlock your device.
And about cap unlocking your device:
Download the NDTK packages and the WPAK utilities
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored >" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click
on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.
AnierinB said:
What carrier do you have? I used an ATT varient and before using the offline update I used the custom preview for developers method to change my device to a lumia 735 on wp 8.1 then did the offline update because interop tools kept failing for me at the time as well. if I remember correctly, you can also use interop tools to change the device targeting info but nothing else if you can't cap unlock/ interop unlock your device.
And about cap unlocking your device:
Download the NDTK packages and the WPAK utilities
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored >" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click
on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.
Click to expand...
Click to collapse
Am I supposed to do all this on my computer, or the phone? And I don't have the "NDTK" button on Interop 1.9 on my M8 (It's the AT&T version, if that helps)
[TOOL][WIN/LIN/MAC] MiUnlockTool - Unlock bootloader of xiaomi devices on mac & linux
Ciao xda users, I'm here to introduce a new tool of mine, MiUnlockTool.
MiUnlockTool is an unofficial tool used to unlock bootloader on Xiaomi devices. This tool is copied from the original windows MiFlashUnlock tool and works the same way. The main feature of this tool is compatibility with linux and mac operating system (and windows too).
If you want more information about the tool and the story behind you can read below, if you just want the download link, here it is:
DOWNLOAD LINK
Requirements: java (javafx for gui if not included in your jdk/jre)
Usage:
- Download and extract the zip file
- If you don't have it, install java
- On windows:
-- open MiFlashUnlock.bat for graphical interface or:
-- open a cmd windows and cd into extracted dir and use "MiUnlockTool.bat username password" command for command-line usage
- On linux:
-- open a terminal window and cd into extracted dir and use "sudo ./MiUnlockTool.sh" command for gui interface or "sudo ./MiUnlockTool.sh username password" for command-line
- On mac:
-- open (double click) MiFlashUnlock.command for graphical interface or
-- open a terminal window and cd into extracted dir and use "./MiFlashUnlock.command username password" for command-line
- Attach your locked device in fastboot mode.
- If you are using gui just follow what you see on your screen
- If you are using command line version remember that there is no confirmation request before unlock and no check if the bootloader is already unlocked.
Possible errors:
- If you get a permission related error on linux or mac when launching the tool, open a terminal and cd into extracted dir and use "chmod 777 MiUnlockTool.sh" (or MiUnlockTool.command on mac) to set the executable permission.
- If your device isn't recognized:
-- On windows: install adb drivers
-- On linux/mac trying launching the tool with sudo (sudo ./MiUnlockTool.sh on linux or sudo ./MiUnlockTool.command on mac)
- Other problems launching the tool: try running "java -jar bin/MiUnlockTool.jar" command
- If you get some errors with javafx class not found stuff when you try to launch the gui, then you are missing javafx library. See openjfx package on linux.
- Any other problem: provide feedback in the comments.
Additional info: original MiFlashUnlock tool is just a bridge between fastboot, you (and your account login credentials) and xiaomi server: the tool gets device info from the device and send them to the server together with the account login token, the server checks wherever you satisfy all their requirements (account authorized, account associated with device in developer settings etc) and if everything is okay the server reply with the unlock key for your device instance (every time you reboot your phone you need a new key). Then the tool send the key to the device with a custom build of fastboot and if the key is right then the device is unlocked, else it reboots. After I discovered all the process behind the original unlock tool (and all the security encryption techniques) I decided to replicate it with a java (cross-platform) tool which embeds a custom fastboot version and replicates what the original tool does. That's a simple explaination of how my tool works (obviously it's more complicated than that).
This tool requires all of what is required by the original tool (an authorized xiaomi account binded to the device through developer options for three days if I remember correctly).
FAQs:
- Is this tool safe to use?
Yes, the main part is communication between tool and server, a safe thing. Also the unlock procedure itself is safe: or the key is correct or it is not. In both cases the device will not be damage.
- How did you find out how to replicate the original tool?
Thank you for your question. It's been a bit difficult since the original tool has been obfuscated and virtualized (protected against reverse engeneering) with a powerful protector: VMProtect. I've spent some time to reverse it (and custom fastboot too) and I finally did it. I will not explain in details how I did it.
- Is this tool more powerful than the original on? why should I use it on Windows?
Absolutely not, my tool is worst than the original one (it will have more bugs and on windows it doesn't manage drivers for example), that's why you should NOT use it on Windows. I made it work even with Windows because it was very simple to do. You can use it one Windows just to test it if you like, but I recommend using the better original tool MiFlashUnlock.
- Wow, you did a tool already done by developers paid by xiaomi, who is paying for the effort you put into this?
No one, I try to help people and getting appreciation for my work is a bit of a reward to me, but if you want to show your gratitude even more and support me as a developer you can make a donation, I will appreciate that even more (donation link below)
- I have to put my xiaomi account credentials, should I trust this?
I'm the developer of XiaoMiTool, I hope that a little bit of my reputation together with the hopefully good early feedback of reckless users on this tool is enough. If you are more a geek you can track the traffic and see that the only server connected are xiaomi and miui.
- I wanted too see the source of this tool but I see it is a bit obfuscated, why?
Xiaomi clearly doesn't wanted people to see how MiFlashUnlock works (since they obfuscated it a lot), I don't want to disrespect xiaomi decision by releasing the source plain, so I decided to obfuscated it a bit just to make it a bit harder to see (even if my tool is 100 times easier to reverse than the original)
- Can I share this tool?
Of course yes, but I would like you to share it using the xiaomitool.com link (not mega.nz one) so that if I release an update new people will get that and not the old version (there is no tool update enginge built in).
- You're english is not wonderful...
I know, hopefully it is understandable enough
Feedback.
I love feedback, feedback is the best you can do to help me improving this tool. I have not time to answer everybody's questions but I generally read feedback and do my best to make the tool work. If the tool worked or if the tool didn't worked you can write it in the comments, adding additional information like what error you get, what screen you see when the tool get stuck or even what you tried to solve the problem are precious to me. I have not all of xiaomi devices, I fully ested my tool only with two devices (a redmi 4x and a mi note 2) and only on two operating systems (linux and windows), so any new combination could lead to new errors or problems. Please include also your operating system when leaving feedback. Sometimes there are problems on gui which are not on command-line version, so if the tools fails launching or when using gui I suggest trying the command-line version.
Donation: free software is great from users prospective, but developers who spend hours of their time and don't get money for it are more unhappy to develop further free tools, so if you liked the tools and it saved you from the need to do 5000 kilometers to get a windows pc, or from the need to download a virtual machine image with your 32kB internet connection, you can show your gratitude by offering me a tasty, cold beer by clicking the link below
DONATION LINK
Download: you missed the download link at the top? Here it is again:
DOWNLOAD LINK
Fully obfuscated tool. Maybe bloatware or password hijacker
Problems with mi unlock on ubuntu system
Dear,
I tried to run this miunlock on my linux pc and it did not work. I installed the javafx using "sudo apt install openjfx" . After I ran "sudo ./*.sh". The program open, but when I put my email and password, it does not connect with the xiaomi server. I tried to access using facebook login and I have the same problem. How can I solve this problem? Do you have any idea?
Thanks
Danillo
The program does not find the phone connected. But "sudo fastboot reboot" work
---------- Post added at 12:03 PM ---------- Previous post was at 11:51 AM ----------
dpvalverde said:
Dear,
I tried to run this miunlock on my linux pc and it did not work. I installed the javafx using "sudo apt install openjfx" . After I ran "sudo ./*.sh". The program open, but when I put my email and password, it does not connect with the xiaomi server. I tried to access using facebook login and I have the same problem. How can I solve this problem? Do you have any idea?
Thanks
Danillo
Click to expand...
Click to collapse
Reinstall certs
disconnects phone on checking bootloader status with an error message on top left corner of phone "press any key to shutdown"
and stays stuck after reconnecting in fastboot mode when reading device info.
How to install it on manjaro arch Linux. did u keep it in AUR.?
Status : Success unlock bootloader
Device : Redmi 4X
Waiting Time : 72hours
Thx for the tool . love3 ??????
worked a treat.
had been struggling to use the mi tool for windows and my device was not being detected.
this took me barely a minute to unlock.
Waiting for a fastboot device...
Well, the communication with the 'net seems to work as intended but that is where it stops:
Code:
[18:01:15][INFO ] Starting login procedure
[18:01:24][INFO ] Login procedure succeeded
[18:01:25][INFO ] Checking account unlock permission
[18:01:27][INFO ] Unlock permission confirmed
[18:01:27][INFO ] Waiting for a fastboot device
Using the fastboot command line works for the same user account so this won't be solved by running the tool as root. The device reports itself as 18d1:d00d Google Inc. and shows up clearly when using the fastboot command line tool:
Code:
$ fastboot devices
deadbeef fastboot
(no, my device ID is not deadbeef)
Tried OpenJDK 10 and 9, Oracle JRE 8, no difference.
Digging deeper using strace shows the problem: the 'special' fastboot command you include (in bin/MiUnlockTool_res) is a 64-bit executable while I'm running the tool on a 32-bit machine. Substituting the provided tool for a link to the version already present on this machine makes the command progress to the error:
Code:
$ java -jar bin/MiUnlockTool.jar '[email protected]' 'mysupersecretpassword'
[18:19:25][INFO ] Starting login procedure
[18:19:36][INFO ] Login procedure succeeded
[18:19:36][INFO ] Checking account unlock permission
[18:19:39][INFO ] Unlock permission confirmed
[18:19:39][INFO ] Waiting for a fastboot device
[18:19:39][INFO ] Device connected: deadbeef
[18:19:39][INFO ] Obtaining device info...
[18:19:40][INFO ] Device info obtained
[18:19:40][INFO ] Checking if unlock will erase data and server message
[18:19:42][INFO ] Unlock procedure will erase userdata
[18:19:42][INFO ] Server message: An unlocked device is an easy target for malware which may damage your device or cause financial loss.
[18:19:42][INFO ] Querying unlock server for unlock key
[18:19:48][ERROR ] Unlock request replied with error code 20036
[18:19:48][ERROR ] Error meaning: After %d hours of trying to unlock the device
I guess I have to wait, how long I do not know as this is not shown in either mode (command line or GUI).
Anyway, you might want to add a 32-bit fastboot command or just tell users to install a native version and use that.
@YetAnotherForumUser
I see the same error message when I tried to unlock MI 8 (global version bought yesterday in official Xiaomi store in Poland). I tried official Xiaomi tools on Windows 10, but without any success (verify failed at 50%).
I'm using it on a Linux laptop, I get "buffer overflow detected" after "starting final unlock procedure" and then it fails
i have this 2 errors on linux tring to unlocking my redmi note 5 [20:59:38][ERROR ] Unlock request replied with error code 20036
[20:59:38][ERROR ] Error meaning: After %d hours of trying to unlock the device
After waiting 360 hours I was able to unlock my Mi 8 with this tool on my Ubuntu! With official MiFlashUnlock tool I wasn't able to unlock this device on Windows 10. Thanks a lot!
YetAnotherForumUser said:
Code:
...
[18:19:48][ERROR ] Unlock request replied with error code 20036
[18:19:48][ERROR ] Error meaning: After %d hours of trying to unlock the device
I guess I have to wait, how long I do not know as this is not shown in either mode (command line or GUI).
Click to expand...
Click to collapse
After about 13 days - I only tried twice in between - the thing is now unlocked. I needed to run the tool on a 64-bit machine as the 32-bit fastboot crashed (with a message in the lines of "* buffer overflow detected *"), possibly due to the longish argument used in the unlocking procedure.
YetAnotherForumUser said:
After about 13 days - I only tried twice in between - the thing is now unlocked. I needed to run the tool on a 64-bit machine as the 32-bit fastboot crashed (with a message in the lines of "* buffer overflow detected *"), possibly due to the longish argument used in the unlocking procedure.
Click to expand...
Click to collapse
I also used 64-bit OS -> Ubuntu 18.04 x64. It would be nice to see amount hours instead of %d, however it's just a minor bug. This tool is the best choice for Linux, MacOS and event Windows 10 users.
Hey guys,
Although I've unlocked & rooted other Android's in the past, this is my first time with a Xiaomi device. I've tried running the tool, and appear to get the "Error meaning: After %d hours of trying to unlock the device" error. Am I right in thinking this is just a bug in terms of the hours displayed, and that I will just need to wait the 15 or so days before I can unlock the device? At what point does that 15 days begin?
Also, once unlocked, what is the best way to flash a ROM? ADB via Terminal?
Looking to flash the Global MIUI over the Chinese one I currrently have.
Thanks!
Help. Can not connect to my phone in fastboot when using this tool. But the MiUnlock is still connected
huynhkhoa said:
Help. Can not connect to my phone in fastboot when using this tool. But the MiUnlock is still connected
Click to expand...
Click to collapse
Windows or linux ?
naik2902 said:
Windows or linux ?
Click to expand...
Click to collapse
window bro, please help me :crying:
huynhkhoa said:
window bro, please help me :crying:
Click to expand...
Click to collapse
Why r u not using original miunlock tool for windows ?
Did u enable oem unlock, usb debugging?
Installed fastboot drivers
Use fastboot devices command to check if u r device connected to pc.
Did u bind ur account to miunlock status in developer option?