Related
Dunno if anyone actually uses 64 bit Vista around here, but if you do, I made a 64 bit version of the USB driver. It's unsigned, so before installing it you'll have to put Vista into test mode or it will refuse to load the driver:
1) Type "bcdedit /set testsigning on" at an admin command prompt
2) Reboot
3) Check to see if the desktop says "Test Mode" on the corners
(I'm not paying $300/yr for a kernel code signing certificate)
After that you should be able to install it like a normal driver. If adb seems to be freezing occassionally, try using adb_fixed.exe instead (don't forget to kill the adb server first).
Sweet! Thanks so much. I have XP 64 but it should work fine
dammit! a bit too late...i used vmware on my 64bit vista to create a virtual machine and 32 bit drivers..lol
but thank you for the drivers...will make my life easier
and welcome to xdadevs!
thank you, I like wise used a work around and dual booted xp and xp x64 so I could use the drivers but I will definilty thankfully switch back over to x64 now thanks much!
it works!
i'm working with original adb, no hangs at all.
aziwoqpd said:
Dunno if anyone actually uses 64 bit Vista around here, but if you do, I made a 64 bit version of the USB driver. It's unsigned, so before installing it you'll have to put Vista into test mode or it will refuse to load the driver:
1) Type "bcdedit /set testsigning on" at an admin command prompt
2) Reboot
3) Check to see if the desktop says "Test Mode" on the corners
(I'm not paying $300/yr for a kernel code signing certificate)
After that you should be able to install it like a normal driver. If adb seems to be freezing occassionally, try using adb_fixed.exe instead (don't forget to kill the adb server first).
Click to expand...
Click to collapse
Awesome! You should see if you can get the changes submitted to Google and then they might be inclined to release it with their signing cert.
Nice job aziwoqpd! I don't use vista myself, but lack of 64 bit vista drivers was a glaring problem.
Mods: this should probably be stickied
Thanks a lot, works like a charm
(Using Vista64 business edition)
Source ?
Hey, that's sounds really great ! Congratulations...
Can you provide the sources to your modifications ?
I'd like to be able to rebuild this myself. Yes, I'm a little anxious at the idea of installing a random driver from the Internet on my system ;-)
adb fixes?
aziwoqpd said:
If adb seems to be freezing occassionally, try using adb_fixed.exe instead (don't forget to kill the adb server first).
Click to expand...
Click to collapse
What's the issue with adb and what does your adb_fixed fixes? My adb seems to work fine, how do I know which one to use?
Could you give the source patch for adb, I like to see what I'm running too
adb_fixed just includes this patch: http://www.telesphoreo.org/pipermail/g1-hackers/2008-December/000191.html
I've attached a diff of the changes I made to the driver. Basically the only difference is that a pointer used for communication between the 32bit DLL and the 64bit driver needs to be explicitly defined as a 32bit pointer so that it's only 4 bytes wide. I also changed the version of Microsoft's WDF library to 1.7 since that's what I already had installed.
You'll also need the driver development kit (the WDK) from Microsoft to compile and link the thing. It's a (big!) free download, though. Just google for "WDK". It includes a command line utility called "build" that's not unlike make for userland code (you can try to use Google's Visual Studio files, but you'll have to hack them to work with x64 and they just end up calling build.exe anyway). For Vista you'll also have to test-sign the driver with a dummy certificate (the WDK help files have a walkthrough somewhere covering this). Or you could pay $300 a year to globalsign for a key! What a deal....
Hmm, it's not letting me attach the file. I'll just paste it:
Code:
diff -U4 -r ./common/android_usb_common_defines.h /mnt/sukiyaki/dev/andusb/common/android_usb_common_defines.h
--- ./common/android_usb_common_defines.h 2008-10-31 17:43:13.000000000 -0700
+++ /mnt/sukiyaki/dev/andusb/common/android_usb_common_defines.h 2008-11-14 14:18:51.439171200 -0800
@@ -132,8 +132,8 @@
ULONG transfer_size;
/// Pointer to the actual buffer for ADB_CTL_BULK_WRITE request. This field
/// is not used in ADB_CTL_BULK_READ request.
- void* write_buffer;
+ void* POINTER_32 write_buffer;
};
#endif // ANDROID_USB_COMMON_DEFINES_H__
diff -U4 -r ./driver/android_usb.inf /mnt/sukiyaki/dev/andusb/driver/android_usb.inf
--- ./driver/android_usb.inf 2008-10-31 17:43:13.000000000 -0700
+++ /mnt/sukiyaki/dev/andusb/driver/android_usb.inf 2008-11-14 15:54:04.556495700 -0800
@@ -10,9 +10,9 @@
Class=USB
ClassGuid={F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}
Provider=%GOOG%
DriverVer=date,1.0.0009.00000
-CatalogFile=androidusb.cat
+;CatalogFile=androidusb.cat
; ================= Class section =====================
[ClassInstall32]
@@ -27,9 +27,9 @@
; ================= Device section =====================
[Manufacturer]
-%MfgName%=Google,NTx86
+%MfgName%=Google,NTamd64
; For Win2K
[Google]
; For loopback testing
@@ -38,9 +38,9 @@
%USB\VID_0BB4&PID_0C01.DeviceDescRelease%=androidusb.Dev, USB\VID_0BB4&PID_0C01
%USB\VID_0BB4&PID_0C02&MI_01.DeviceDescRelease%=androidusb.Dev, USB\VID_0BB4&PID_0C02&MI_01
; For XP and later
-[Google.NTx86]
+[Google.NTamd64]
; For loopback testing
%USB\VID_18D1&PID_DDDD.DeviceDescTest%=androidusb.Dev, USB\VID_18D1&PID_DDDD
; HTC Dream
%USB\VID_0BB4&PID_0C01.DeviceDescRelease%=androidusb.Dev, USB\VID_0BB4&PID_0C01
@@ -85,21 +85,21 @@
AddReg=CoInstaller_AddReg
CopyFiles=CoInstaller_CopyFiles
[CoInstaller_CopyFiles]
-wdfcoinstaller01005.dll
+wdfcoinstaller01007.dll
[SourceDisksFiles]
-wdfcoinstaller01005.dll=1 ; make sure the number matches with SourceDisksNames
+wdfcoinstaller01007.dll=1 ; make sure the number matches with SourceDisksNames
[CoInstaller_AddReg]
-HKR,,CoInstallers32,0x00010000, "wdfcoinstaller01005.dll,WdfCoInstaller"
+HKR,,CoInstallers32,0x00010000, "wdfcoinstaller01007.dll,WdfCoInstaller"
[androidusb.Dev.NT.Wdf]
KmdfService = androidusb, androidusb_wdfsect
[androidusb_wdfsect]
-KmdfLibraryVersion = 1.5
+KmdfLibraryVersion = 1.7
;---------------------------------------------------------------;
[Strings]
THanks for the help....but how do I disable test mode after enabling it?
Thank you.
Thanks!
much appreciated.
remiks3 said:
THanks for the help....but how do I disable test mode after enabling it?
Click to expand...
Click to collapse
"bcdedit /set testsigning off" will turn testsigning back off, but you won't be able to use unsigned drivers any longer.
Thanks, I registered just so I could download that driver...
Just got my G1 flashed to the hacked RC and I wanted to play with some tethering on Vista X64...
This works perfectly on my XP 64 bit machine! Thank you!
I don't know if can help to sign the 64 bit driver , i try to post.
Test-signing the Micro Framework USB driver for installation on Vista 64-bit systems
The 64-bit version of Windows Vista requires all kernel mode drivers or services to pass a validation. In this follow-up of building USB driver in the Micro Framework, I’ll briefly outline the necessary steps to sign a driver that meets the requirement. These steps are intended for users working in a development environment. If you are planning to distribute drivers to third-parties, you should submit the driver for a WHQL signature or use a software publisher certificate. For more information about the bigger picture, review the kernel-mode signing guide on the WHQL website.
Let’s get on with the technical process. I’ve assumed you have a 64-bit Micro Framework USB driver built. If not, you’ll need to use the WDK and the WDK setup script, SETENV.BAT, to build the porting kit sample driver for an x64 (64-bit) Vista operating system. See the prior blog for detailed steps.
1. Open a command prompt with administrative privileges.
2. Run the command to enable test signed kernel mode drivers.
BCDEDIT /SET TESTSIGNING ON
3. Confirm the setting is correct by listing the Windows Boot Loader settings.
BCDEDIT /ENUM
4. Reboot to enable the new boot loader setting.
SHUTDOWN –t 60 –r
Notice the desktop background displays a new water mark after the reboot.
5. Open a command prompt and run the WDK SETENV.BAT command.
C:\apps\WDK\bin\SETENV.BAT C:\apps\WDK fre x64
6. Change directory to the porting kit root.
7. Set up the certificates folder.
MD Certificates
CD Certificates
8. Generate a self-signed certificate and private key.
Makecert –r –pe –ss MFCertificateStore –n “CN=MicroFrameworkOEM” OEMCertificate.cer
9. Open a MMC console and snap-in certificates for the current user. You will see the MFCertificateStore containing a private key and certificate. The certificate containing the public key is in a file called OEMCertificate.cer.
10. Add the certificate to the trusted publisher store.
Using the MMC certificate snap-in, right-click on the Trusted Publisher folder. Select import. Browse to the PK\Certificates\OEMCertificate.cer file.
11. Next, create a CAT file. First change directories to the Drivers\Vista64 folder. This folder contains the 64-bit USB driver under amd64 and the INF file.
CD BUILDOUTPUT\DRIVERS\VISTA64
12. Edit the INF file so that the version is 6.0.0.1 (or later as it matches the OS) and the driver date string is current.
13. Create a CAT file. The parameter to the “/driver” option must be the full path. Confirm the INF2CAT status output displays success with no warnings or errors.
INF2CAT /driver:C:\PK\Buildoutput\Drivers\Vista64\ /OS:Vista_x64
14. Sign the CAT file. The tool will use the the private key stored safely in the workstation certificate store.
SIGNTOOL sign /v /s MFCertificateStore /n MicroframeworkOEM /t http://timestamp.verisign.com/scripts.timestamp.dll MFUSB_PortingKitSample.cat
15. Verify the digital signature.
SIGNTOOL verify /kp /c MFUSB_PortingKitSample.cat amd64\MFUSB_PortingKitSample.sys
16. Plug in the Micro Framework device and install the newly signed driver. You’ll notice a pop-up that asks for permission to install the driver.
The steps above provide a process for signing 64-bit drivers that I use for Vista 64-bit testing. It is good to know the steps. But combined with the prior blog describing USB driver building, the labor to perform all these steps is too time-consuming. We’ll follow-up at a later time how to automate most if not all steps using the POWERSHELL toolset.
Jeff Simon
.Net Micro Framework
SDET - Porting Kit
Awesome, after 3 months finally got Windows to recognize. Thanks.
Vista 64 Development Mode Driver?
I'm runnin vista 64, and i can't get the "64 bit driver" that i found somewhere on here to work in Debug/Development Mode. anyone have one that they KNOW works?
So, I am sorry, if this is a stupid question, I am novice here. I am trying to run SDK manager on windows 7, 32-bit os. It's already installed. Whenever I try running SDK manager, It flashes for a sec and disappears. When I tried executing android.bat from tools, what I got was :
C:\Program Files\Android\tools>android
[INFO] Starting Android SDK and AVD Manager
'xcopy' is not recognized as an internal or external comman
operable program or batch file.
No command line parameters provided, launching UI.
See 'android --help' for operations from the command line.
Exception in thread "main" java.lang.NoClassDefFoundError:
ts/Display
at com.android.sdkmanager.Main.showMainWindow(Main.
at com.android.sdkmanager.Main.doAction(Main.java:2
at com.android.sdkmanager.Main.run(Main.java:99)
at com.android.sdkmanager.Main.main(Main.java:88)
I have java 6 up date 25 already installed and the path is already added to environ var. Also I am interested in developing for android, If anybody is interested in showing me how, I wud be very greatfull. Thanks in advance. Plzzzzzzz........ HELP.
Currently Using : HTC Desire Z.
And yes, I am having eclipse 3.2 already installed on my system. PLzz help................................., somebody......................, anybody.
General tip
If you double click some techie program on Windows and see it just appear and disappear like that, it usually means that this program is meant to be run in a command line window.
So go to All Programs -> Accessories -> Command Prompt and open that
Then go to wherever that program is installed and run it from there.
Oh, and note that Android development needs the JDK, not the JRE version of Java, The JDK contains all the extra parts needed for Java software development in general, including key parts needed by the Android SDK.
While the JRE can be downloaded from www java com , the JDK is only available from java.sun.com .
P.S.
Sorry for not making proper links, but I have not made enough posts to allow them yet.
I've no idea if this works for all Android tablets/phones but it sounds like it should.
It might also be common knowledge to most on here but I couldn't find it earlier.
This is a story that happened to a work college of mine and three of us have just spent half the morning trying to sort it out. It starts with a cheap £50 tablet from Amazon, the LelikTec A13 Touch Screen AllWinner, which my college's son bought for his daughters. Being kids they did what kids do and mucked around with all the settings which resulted in them locking themselves out of the tablet (by setting up a pattern lock and then forgetting it).
Unfortunately, the tablet was locked with the WiFi turned OFF, so an attempt to use the useful Google recovery system was unsuccessful (tip for Google there, make the password recovery system so you can enable and setup a WiFi link). Never mind, you can perform a factory reset on Android devices by booting into recovery mode by pressing the up volume and power buttons at the same time. Well for some unexplained reason this didn't work, it simply resulted in the distressing image of a dead Android on the screen.
So the next thing to do is attempt to use the Android Debug Bridge via USB. Now between us we knew this is what we needed to do, but no one knew exactly how, so here is a beginners, step-by-step guide.
Download the ADB SDK from this website.
http://developer.android.com/sdk/index.html
(If you have a 64 bit system then the top download button is all you need. If you have a 32 bit system then at the bottom of the webpage is "Download for other platforms" link and you can download the relevant software from here)
Install the ADB SDK so that it is on the c:\ drive (so that to navigate through it looks like c:\android-sdk\.....etc)
You now need to install the correct USB Drivers. If you navigate through to C:\android-sdk then you will see SDK Manager.exe.
Run up the SDK manager
Scroll through to Extras\Google USB Driver and check the box
Select Install packages. This will now have installed the usb drivers so that the development kit can talk to the tablet. (These drivers worked fine on a 64 bit machine but did not work on my 32 bit XP machine. I downloaded the drivers from here:-
http://www.kmods.net/android/misc_g59-usb_drivers_windows_7__vista__xp__32bit_p18.html
and they worked fine on the XP machine)
Close the SDK Manager
Now plug in the tablet to your PC using the USB cable supplied with the tablet.
Check the "DEVICE MANAGER" and you should see "ANDROID PHONE\Android ADB Interface"
(If you still have an unknown device then right click it navigate to "Update Driver" and then point it at the drivers USB drivers folder you may have downloaded earlier and update it)
This next step will make life a lot easier to unlock your tablet but take care in doing it.
a) Right Click "MY COMPUTER" and select properties\Advanced\Environment Variables
b) Scroll down until you see "Path" and select edit.
c) Add the following two lines to the end of the text making sure that you use ;(semicolon) between them.
e.g.C:\Program Files\WinNT\Bin\;c:\android-sdk\sdk\platform-tools\;c:\android-sdk\sdk\tools\
Now you all you have to do is follow the instructions on this website
http://www.addictivetips.com/androi...e-pattern-unlock-on-android-via-adb-commands/
As a brief summary:-
Goto ,<START> <RUN> and type in cmd
Cut this text:-
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
and paste it into the cmd window.(You have to right click to paste into the CMD window)
If you now reboot your tablet you will find it unlocked. Re-connect it to the internet, type in your Gmail account details and away you go.
There may be other, easier ways of doing this, but this is what we did and this is what worked for us.
Apologies if this is in the wrong part of the forum, please feel free to move if so.
[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?
I have an rca tablet I can not get any drivers to work to get to replace/update the firmware and I was wanting to ask if anyone has found anything that works.
I have tried mediatek, rca and all other drivers I can find and nothing seems to work on windows 10 64.
Thank You
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
xXx yYy said:
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
Click to expand...
Click to collapse
Thank You will give a try
I have a Windows 7 64 bit system and I am trying to find drivers to access an rca rct6703w13
I have tried every driver I can find and nothing seems to work does anyone know something that will work?
I would be very grateful if anyone could help?
Thank You
Oh boy, I still remember this pain trying to find and use such drivers on Windoze:
- try another port
- try another cable
- try this driver or that one
- try doing a rain dance with 3 days old undies on your head, and turn only clock wise, unless it's full moon, then turn counter clockwise but stop briefly after ever two and a half turns
Maybe, as workaround, you could boot from a linux CD and try your approach from there.
Whenever I flash from my debian, it works: If "fastboot devices" still doesn't show anything then usually I have forgotten to plugin the cable
By using my "Yet Another Universal ADB Driver" Package (see the link in my signature) one can remove all the old adb drivers if that is the issue, but this case seems to be more interesting...
On win10 it seems that the adb is embedded to the winusb driver the same or similar way (registry wise) that my package is using. Now that I have tested, the behavior is similar with my devices. When using file transfer connection the adb is not recognized. With others, charging, photo, midi the abd works fine. To make adb work with file transfer one have to install the correct driver. In this case google's general driver could be okay, one match for vendor and product ids in it ...
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
What I tested using virtual win7 64bit, it seems to behave the same way... which is a bit weird as I've tested it with my driver package. Worked okay then I think. The Android device used has changed since though.. It worked on win10 back then too.. the change has to have happened later.. or I didn't use file transfer..
@steadfasterX 's maid or salt or whatever it's called nowadays might be usable in this case. It's a Linux having SP flash tool etc. available..
edit: tested and it turned out that the updated phone is the problem... using another phone my driver package worked as expected..
@resxwni01
1. Don't confuse USB-driver and ADB-driver: the USB-driver since ever is by default part of any OS, so also of Windows OS. The ADB-driver is an extra protocol what allows you to communicate with a phone's Android ecosystem via an USB-connection.
2. Latest generic ADB-driver ( correct: ADB client ) got released August 2022 and is officially versioned 33.0.3.
3. AFAIK a 64-bit version of ADB-driver doesn't exist.
With regards to install this ADB-driver on a Windows 7,8.1,10,11 PC:
It's NO USB-driver installer - as introduced above by @CXZa - needed what unnecessarily bloats the Windows registry with crap.
You
1. simply create on any mounted drive of Windows PC a folder named "ADB",
2. extract there to the 3 files what are in the attached ZIP file,
3. add path of created folder "ADB" to Windows environment variable PATH, thus ADB-driver is systemwide accessible -
how to is described here
How to Set the Path and Environment Variables in Windows
Information on how to set the path and environment variables in Windows 2000, Windows XP, Windows Vista, and Windows 7.
www.computerhope.com
@jwoegerbauer , you're funny guy...