Hi!
Please help me...
My Infocus M210 is rooted and I've edited the build.prop from a build prop editor to speed up internet data connection but the editor goes wild and changes everything written on the build.prop then forced my phone to shut down and when I start my phone, it stuck at boot loop.
I've already wipe data/factory reset on its built-in Android system recovery <3e>.
but I think its the worst thing that I've done.
Coz I thougt it disabled debugging and removed root permission from my device.
I've used Apply update from ADB.
I tried to sideload stockrom.zip but when its completed sending on my phone, then says "installation aborted" I've tried different ROMs but same result.
I have also tried shell commands:
adb pull /system/build.prop
adb -d -e -s <serialNumber> shell am start options -D
but all shell commands doesn't work and says "error:closed"
So then I've tried Fastboot mode
but my devices wasn't found
so I have followed some threads and watched youtube tutorials:
So I removed drivers via "usbdeview"
Then installed Fastboot device/ Fastboot interface drivers manually.
but I almost tried all drivers from official to many google drivers
but still my device wasn't found in cmd
says "waiting for device"
Now I'm thinking if there are some tricks to fix adb "error:closed"
or try different computers for fastboot
I already used my Windows 7 64-bit from my friend
and Windows XP 32-bit from my friend
Please Help me... :crying:
Hello,
Welcome to XDA.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
The experts there may be able to help. Good luck.
[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?
Hello, I hope that this topic can be opened here, if not please move it or let me know and I will delete it.
In adb I am getting the error "failed to check server version: protocol fault (couldn't read status): No error" and I cannot see my device when I use the command "adb devices". Moreover, it seems like my phone is not letting me authorize my laptop for USB debugging despite trying different options to getting it to work. I have tried different trouble shooting methods that I have found online, but nothing has worked so far. If anyone has any ideas, it would be greatly appreciated.
I am using a POCO F2 Pro that has had its bootloader unlocked and I am running Xiaomi.eu version 12.0.4 (stable) and using a Windows 10 machine to connect with my phone. I did not have much problems with the flashing off TWRP, using ADB commands, or flashing the ROM when I did all of these things last month.
Now, however, I have been having some problems. I believe it started when I tries to update the System FW a few days ago in the phone instead of flashing it manually. Because it was the stable version, and because the option existed in my system settings, I thought that I would be able to update it without going through those steps. The update downloaded and I got the correct file, but when I hit install, I did not get the new FW, despite the phone rebooting. I've been having problems with adb since this time, I believe.
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Saratoga79 said:
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Click to expand...
Click to collapse
Hello, thanks for your reply. I tried that yesterday, but I gave it another try today. This was the error that I received when I ran the command in Powershell:
Program 'adb' failed to run: No application is associated with the specified file for this operationAt line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
When I ran the command in Command Prompt, I got the error "failed to read response from server".
Trying to start the server also lead to an error "protocol fault (couldn't read status): No error
---------
Part of my issues may be coming from the fact that I no longer get the authorize USB debugging on my phone, even after I have revoked the authorizations. I've tried different ports, different USB cables, and even factory resetting my phone, to no luck.
Try using the latest platform tools from Google.
batuken said:
Try using the latest platform tools from Google.
Click to expand...
Click to collapse
From what I know, I am using the latest SDK platform tools. I initially downloaded from that site either in late July or early August, and yesterday I deleted the old files and re-installed them from the website. Is there an additional step that I might have missed in removing the old files from my computer?
Additionally, the .android folder in my user profile is now empty (no adb_key file(s) inside).
I have a very old Wikipad tablet, which these days tends to only get used for playing old video games. I hadn't used it for a few months, but now whenever I switch it on I get an error:
"Unfortunately, System UI has stopped"
No matter how many times I tap OK, the error just keeps popping up, with the occasional "unfortunately, Launcher has stopped" thrown in as well.
There are plenty of suggestions online for how to fix these errors (remove apps, empty cache, etc.), but those all rely on you actually being able to access the UI and settings. I can never get past these errors on top of a blank screen.
If I enter the Power/Volume-Down boot menu, I get the options of "normal boot", "fastboot protocol", "recovery kernal" and "forced recovery". Selecting "Recovery Kernel" shows the image of the android lying down with an exclamation mark above it. However, I'm not sure where to go from there. No commands appear on screen and various power/volume button combinations don't seem to do anything.
Does anyone know the correct commands to do a factory reset on a Wikipad (or have any other suggestions as to how to resolve the errors)? I'm not bothered about losing all of the data on it.
Thanks!
OK, after weeks of scratching my head on this one for a few weeks and deciding to post the question on this forum, I figured it out myself a couple of days later
I downloaded Fastboot and Android USB drivers from the links posted here:
Fastboot.zip, ADB, & Android USB Drivers | HighOnAndroid.com
highonandroid.com
I installed Android USB drivers (by ClockworkMod). I plugged the Wikipad in to my laptop (Windows 10), powered it off and booted it holding the power and volume down keys. I selected the "fastboot protocol" option. An unknown "fastboot" device then appeared in Device Manager. I had to manually select the ClockworkMod generic Android driver before it was recognised.
Running "fastboot devices" then listed a device. Running "fastboot -w" then deleted all user data (there's no confirmation prompt, it just runs). It also threw an error:
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I ignored the error and rebooted the Wikipad. It then booted in to the first time start-up wizard and the System UI errors are gone. All of the data I had on it is gone too, but that's no big deal.
Good evening I have read all the messages of the forum, and I have tried the various solutions to solve the problem.
It tells me "Invalid boot image!" and does nothing else even when restarting. Connecting it to the PC I can see the code of the tablet with ADB and command fastbot devices.
The tablet is recognized in peripheral management as Asus Android Device / Asus Bootloader Interface
I downloaded this firmware ... ME302KL-OPEN_epad-eng-900M-hdpi-H00_0.16.F_0521-10.10.0.52.4.8-20130731-1422-Rawdata.rar but it doesn't work.
I ran the flashall.cmd file as administrator (Right click on the file and choose: run it as administrator)., The command "debrick-flashall.cmd", and also the commands flashall-ME302KL-1GMEM.cmd or if you also have the brick debrick-flashall-ME302KL-1GMEM.cmd without the tablet exiting FASTBOOT mode. Is it possible that it doesn't work because my operating system is WIN 10 ?? ... is there any firmware that works with windows 10 or some other indication to solve the problem.
Thank you