Related
Hello XDA,
I just got a v10 and while i'm new to the phone, I'm not new to rooting/ installing custom roms etc. But for the life of me I cant unlock to bootloader of this phone which if im not mistaken, is the only way to get root. I just installed adb on my windows 10 laptop and I'm trying to enter fastboot on my devices by plugging in the power cable and pressing the volume down and I'm greeted with a screen that says"*welcome to fastboot mode for bootloader unlock: *quick Guidance...etc" I cant exit out of this mode so I assume this is fastboot mode? It doesnt look like any fastboot mode Ive ever seen. Anyways when trying to run the fastboot oem unlock command, I am stuck on "waiting for device". I honestly dont know whats wrong with my setup but if someone could help that would be fantastic. I have tried installing the Lg united drivers and samsung drivers but they dont seem to work. Please advise if you could.
http://forum.xda-developers.com/showthread.php?t=3490604
gamin92 said:
http://forum.xda-developers.com/showthread.php?t=3490604
Click to expand...
Click to collapse
So to get it to work I have to install unbuntu software on my computer, boot into it and then install adb? I'm not getting this?
ayo234 said:
So to get it to work I have to install unbuntu software on my computer, boot into it and then install adb? I'm not getting this?
Click to expand...
Click to collapse
I looked online at some forums about this issue and I got it fixed Here what the post said
1. Connect your device while in fastboot mode.
2. open the device manager (ctrl + X on windows 10)
3. find your device "XXX ADB Device"(Mine was "Alcatel ADB Device" but it can be anything)
4. click on the arrow
5. right click on the Android Bootloader Interface
6. Click on "Properties"
7. Go to "Driver" Tab
8. Click "Uninstall"
9. Mark the "Delete the driver software for this device
10. Click OK
11. Disconnect and Reconnect your device from the cable
12. Windows device manager should show an item in the list that simply says Other devices, and will expand to "Android". Do those next steps quickly! (OR: just disconnect from the internet. Some people report it works). You have between 5-10 seconds until Windows changes it to another driver. If device manager changes the driver to "Kedacom USB device" (or something else, start over from step 8).
13. Right click and choose "Update driver software" -> Browse my computer for driver software -> Let me pick from a list...
14. Choose "Kedacom USB device" (or something else that seems logical)
15. Uncheck "Show compatible hardware"
16. Choose "Android bootloader interface version _" that is the latest (should be 28.8.2016).
17. Hopefully it will work for you
Extremely helpful and it solved my problem. Here the original thread, its post number 33
http://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
androidferret said:
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Augustoandro said:
Have you unlocked the bootloader?
Click to expand...
Click to collapse
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
androidferret said:
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
Click to expand...
Click to collapse
Please take a backup of ur data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
androidferret said:
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
Click to expand...
Click to collapse
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Augustoandro said:
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Click to expand...
Click to collapse
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
androidferret said:
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
Click to expand...
Click to collapse
I meant Kingoroot for PC and not Kingoroot Android.
They are different, although from the same company.
Wow it turns out I was using a fake Kingoroot from the Play Store so I take back my comments regarding KingoRoot.
I can't believe the Play Store allows such trash.
so I can connect my bricked phone to a Windows PC by shorting the test points. But the device (Qualcomm HS-USB QLoader xxx) also keeps on disappearing in Device Manager. In most cases, the device only shows up in Device Manager for 1 second and disappears immediately.
Any ideas on how to fix?
Thanks
edit1: tried on a laptop running Windows 10 and another laptop running Windows 7.
edti2: My phone is stuck in a bootloop. I cannot even get it to boot into fastboot mode.
mrjayviper said:
so I can connect my bricked phone to a Windows PC by shorting the test points. But the device (Qualcomm HS-USB QLoader xxx) also keeps on disappearing in Device Manager. In most cases, the device only shows up in Device Manager for 1 second and disappears immediately.
Any ideas on how to fix?
Thanks
Click to expand...
Click to collapse
Steps:
A).On the computer in windows disable driver signature enforcement featrure and turn off any protection like security suites,AV software or firewalls.To disable driver signature enforcement you must open command prompt and type:a)bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS and press enter
b)bcdedit.exe -set TESTSIGNING ON and press enter
c)reboot computer
d) install MI flash after reboot;download it from here :http://en.miui.com/thread-235865-1-1.html
B) On the phone:
1.Hold Vol - and Vol + and plug Usb cable in computer&phone
2.download ADB files from here http://en.miui.com/thread-235865-1-1.html
3.extract files from archive to folder
4. in this folder,where you have extracted adb files press:shift on keyboard and right click on the mouse in the same time and choose "open command window here"
5.in command window type:a)adb devices and press enter
b)adb reboot edl and press enter
Now you are in download mode
6.from device manager install qualcomm driver;it should be seen in other devices section;right click---update driver----navigate to :C/Program files(X86)/XIaomi/Mi flash/Qualcomm/Driver;Note:you need x64 windows computer for this operation
7.start MI flash---right click and run as administrator;browse for rom folder,you need a fastboot rom(the rom need with suffix tgz to be;not zip).Put the tgz archive(rom) in Local Disk C and extract with winrar!!!!!!(use winrar) to folder;rename the created folder to ROM.In MI flash when do browse for folder SELECT ENTIRE FOLDER NOT JUST THE FOLDER IMAGES.OK?
8.in MI Flash window press refresh button from up side;the device should appear on the list
9.in MI Flash windows in the down side of windows tick the litlle circle who say:Flash all
10.Press flash button from up
1.1. Wait until it finish flashing procedure:should appear in the right side from device peration completed succesfully
12.Remove usb cable and press power button on the device;keep the power button pressed until the device give you a vibration,the release it
ketan7731 said:
Steps: snip
Click to expand...
Click to collapse
My phone is stuck in a bootloop. I cannot even get it to boot into fastboot mode.
deleted
I have the same problem but mine is Red mi Note 9 Merlin SOC: MT 6768 what do i need to do, Phone cant go fast boot mode nor recovery but just boot re loop. My Mi account credentials are active and the phone boot lock is unlocked.The problem i have is the connection in the device manager comes and goes,May someone give the detailed info on how i my revive the phone
Hello,
Any root and custom ROM available for the Lenovo tab m8 tb8505 variant? The stock rom feels good for the price but if something better to make the tab feel nicer..
Thanks
I managed to root it for now, using magisk_manager.apk and a boot.img, I extracted from a file named "TB-8505F_S100133_200316_BMP.zip" (which is the latest firmware for the M8-8085F)
am unable to find any TWRP for the device.
but at least: got root now.
OTG and Charge Simultaneously
Hello,
I recently purchased the Lenovo tab m8 to replace the outdated navigation system in my car. I thought that since it came with a dock station that I would be able to connect the otg cable on the micro USB port. However this does not work, if it’s charging on the dock and I connect the OTG it stops charging. Does anyone know how I can die both things simultaneously?
am24901 said:
Hello,
I recently purchased the Lenovo tab m8 to replace the outdated navigation system in my car. I thought that since it came with a dock station that I would be able to connect the otg cable on the micro USB port. However this does not work, if it’s charging on the dock and I connect the OTG it stops charging. Does anyone know how I can die both things simultaneously?
Click to expand...
Click to collapse
Look here: https://www.instructables.com/id/DIY-Cable-to-Use-OTG-and-Simultaneously-Charge-the/
Test
---------- Post added at 08:00 AM ---------- Previous post was at 07:13 AM ----------
Xenograph said:
I managed to root it for now, using magisk_manager.apk and a boot.img, I extracted from a file named "TB-8505F_S100133_200316_BMP.zip" (which is the latest firmware for the M8-8085F)
am unable to find any TWRP for the device.
but at least: got root now.
Click to expand...
Click to collapse
@Xenograph:
Hi, would you care to specify in detail the rooting process used for your tb-8505F?
That would be very much appreciated!
I aquired the tb-8505X (LTE) model myself, but was surprised by not being able to dig up the rooting method specific for this model from the internet for two weeks now.
So far, my attempts to aquire root have got stuck at the initial stage of having my W7-64bit laptop communicate with TB-8505X via (first) ADB (lists the device) and (second) fastboot (no devices or waiting for devices).
My suspicion is that while ADB has at its disposal the correct W7-driver, subsequently fastboot is unable to operate with that driver.
Internet search shows the <fastboot-waiting for devices> to be rather common, but without coherent solution.
Any thoughts welcome, thanks!
Did you enable developer options and and there USB debugging and OEM Unlock?
I only plugged in mt 8505F, typed the command "adb reboot bootloader", waited until Windows installed the drivers and I was good to go.
After this started the root process
Cheers
Tom
Xenograph said:
I managed to root it for now, using magisk_manager.apk and a boot.img, I extracted from a file named "TB-8505F_S100133_200316_BMP.zip" (which is the latest firmware for the M8-8085F)
am unable to find any TWRP for the device.
but at least: got root now.
Click to expand...
Click to collapse
How did you actually root it?
I tried patched boot.img, won't work, tried patched recoevery img the M8 is in a bootloop.
Only boot up after I flashed standard recovery again
Cheers
Tom
tom1807 said:
Did you enable developer options and and there USB debugging and OEM Unlock?
I only plugged in mt 8505F, typed the command "adb reboot bootloader", waited until Windows installed the drivers and I was good to go.
After this started the root process
Cheers
Tom
Click to expand...
Click to collapse
Yes, enabled all three of them.
Then installed the ADB/Fastboot package on W7/X64.
Then the usb driver/drivers (don't know).
Then from the admin CMD adb list devices (returns device name)
Reboot tb8505 into fastboot mode.
adb>fastboot list devices (returns waiting for devices...)
Any other subsequent fastboot command returns the same ''waiting for devices''.
Could be this is better attempted from W10,Ios or linux.
Any thoughts? cheers!
I think its a driver problem, which adb/fastboot package did you install?
When you are in fastboot and you open your device manager, any device which shows an exclamation mark?
Cheers
Tom
tom1807 said:
I think its a driver problem, which adb/fastboot package did you install?
When you are in fastboot and you open your device manager, any device which shows an exclamation mark?
Cheers
Tom
Click to expand...
Click to collapse
adb-setup-1.4.3. (okt 10th 2015)
device manager: shows as Alcatel ADB device>Lenovo Android Interface (upon usb connection). No exclamation marks.
From CMD C:\adb>adb devices -l
returns
HA12A76E device product: Lenovo TB_8505X-EEA model:Lenovo_TB_8505X device:8505X
Disconnecting usb & rebooting 8505X into fastboot mode, reconnecting usb:
device manager shows Alcatel ADB Device>Android ADB Interface (sic) (without having changed drivers manually). No exclamation marks, btw.
Subsequently
C:\adb>fastboot devices
(returns nothing)
C:\adb>fastboot reboot
returns < waiting for device >
Reboot 8505X from fastboot mode by pressing power button >20 seconds.
Device manager shows Lenovo Android Interface again.
8505X shows usb debugging options back at 'No data transfer' again, which does that every reboot, so I reselect connect as Media device or as Camera after every reboot.
Q... said:
adb-setup-1.4.3. (okt 10th 2015)
device manager: shows as Alcatel ADB device>Lenovo Android Interface (upon usb connection). No exclamation marks.
From CMD C:\adb>adb devices -l
returns
HA12A76E device product: Lenovo TB_8505X-EEA model:Lenovo_TB_8505X device:8505X
Click to expand...
Click to collapse
Haven't used these, I just used the which Windows (in my case wW10) downloaded
Disconnecting usb & rebooting 8505X into fastboot mode, reconnecting usb:
device manager shows Alcatel ADB Device>Android ADB Interface (sic) (without having changed drivers manually). No exclamation marks, btw.
Subsequently
C:\adb>fastboot devices
(returns nothing)
C:\adb>fastboot reboot
returns < waiting for device >
Click to expand...
Click to collapse
I am assuming the device shows it is in fastboot mode, its listed in Device Manager under Android Phone(?) as ADB Interface
After reboot it is listed fro me under USB Devices as ADB Interface. In fastboot boot the driver is from Mediatek, in working mode, the driver is from Microsoft
8505X shows usb debugging options back at 'No data transfer' again, which does that every reboot, so I reselect connect as Media device or as Camera after every reboot.
Click to expand...
Click to collapse
Used Developer Options to set the Default USB configuration to "File Transfer" works as I set it
Cheers
Tom
Installed mediatek drivers for fastboot, to no avail.
Despite setting the usb preferences to file transfer, the 8505X resets that at every unplugging/rebooting to charging via usb/no data transfer, which also could be the problem, as before entering fastboot mode, usb is disconnected.
In fastboot mode no listing under USB devices in my dev mgr, btw.
Dev mgr shows Alcatel ADB Device>Lenovo Android Interface (as before) and moreover Lenovo Tab M8 under Portable devices. That's in normal working mode.
I presume you are on W10?
Regards, Q.
unlocked bootloader; no root
Hi,
managed to unlock the bootloader on TB-8505X by connecting it to an apple mac instead of W7. Worked via ADB and fastboot, without need to install USB drivers manually.
What would be the next advisable step(s) to take in order to achieve root?
I had a look @ the TWRP site, but there was no TWRP recovery offered for the TB8505F/X.
Any thoughts appreciated. Cheers!
Q... said:
Hi,
managed to unlock the bootloader on TB-8505X by connecting it to an apple mac instead of W7. Worked via ADB and fastboot, without need to install USB drivers manually.
What would be the next advisable step(s) to take in order to achieve root?
I had a look @ the TWRP site, but there was no TWRP recovery offered for the TB8505F/X.
Any thoughts appreciated. Cheers!
Click to expand...
Click to collapse
1. Go to Lenovo site and download Rescue and smart assistant. Install and run.
2. On the rescue tab you can download the firmware for your tab (it needs to be connected to the PC).
3. Goto where you downloaded the firmware. In the RomFiles folder find the boot.img file. copy it to your device.
4. Install Magisk Manager on your device. Run and select install. select the option to patch a file and select the boot.img file you copied to your device.
5. markdown the location that magisk shows where it saved the patched file. Copy this file back to your PC.
6. Flash the file to your device with fastboot flash boot <patched file location>
7. reboot your device and run again magisk manager this should install the magisk zip file and you are rooted.
Is there any custom recovery and roms available? This tab is quite awsome
Leboboy19 said:
Is there any custom recovery and roms available? This tab is quite awsome
Click to expand...
Click to collapse
I'm looking for a custom recovery as well.
I am having problems with Fastboot. I tried all the drivers etc. and always end up with:
C:\adb>fastboot devices
(returns nothing)
C:\adb>fastboot reboot
returns < waiting for device >
Any ideas how to connect with Fastboot?
I want to replace my old Mediatek based tablet with one of these.
So i hope that there's a method to invoke Fastboot or Download Mode by other means than ADB.
While on all other devices i have to keep power Button plus vol up or down plus sometimes Menü Button pressed, my Mediatek tablet requires holding vol up or down while attaching the thing via usb, w/o touching power to power up into Fastboot.
lecorbusier said:
I want to replace my old Mediatek based tablet with one of these.
So i hope that there's a method to invoke Fastboot or Download Mode by other means than ADB.
While on all other devices i have to keep power Button plus vol up or down plus sometimes Menü Button pressed, my Mediatek tablet requires holding vol up or down while attaching the thing via usb, w/o touching power to power up into Fastboot.
Click to expand...
Click to collapse
Holding down the down vol while pressing power gets you to Fastboot mode.
That's the common method. Good. On my Acer you need to attach a usb cable even for accessing the stock recovery. But i will dump it anyway, a Tab M8 FHD has been ordered...
Hi,
I just went through the unlocking process and wanted to share a few things I noticed. It won't be a "unlocking guide", but more kind of a "collection of tips and tricks". Hope this can help someone in sorting things out. Happy unlocking to everyone!
Disclaimer
I am writing these things here with my best knowledge, but I cannot guarantee they are 100% correct. So please take them at your own risk! Feel also free to respond in case I (probably) got something wrong.
"EU/global version" of Mi Pad 4
As someone stated in another thread, and as I understood it, there is no such "global" or "EU" version of this tablet, but there is a "global/EU" ROM you can flash on it. And it seems that in europe there has been some market on these tablets that came with the global ROM preinstalled. As far as I know, the only way to flash the global/EU ROM is to unlock the bootloader, so these sellers had to go through the same process of unlocking. Now the problem is: to unlock the bootloader you require to link the tablet with a Xiaomi account, and you need the same account to unlock it again. So I guess that for these tablets one needs to be careful when buying them with the global ROM preinstalled, as you may need the phone number associated with the Xiaomi account that was set by the seller back then to unlock it again! Fortunately the one I bought came with the official chinese ROM and with no Xiaomi account linked to it, so I could manage to unlock it.
SIM card being necessary to unlock bootloader
I read that in some guides it is stated that you need to have a SIM card to unlock the bootloader installed in the tablet, and some users are asking how to do this on wifi only tablets. From what I've seen, there is no such prerequisite for wifi-only devices (which is kind of obvious, but peaople still ask). You still have to give a phone number to confirm your Xiaomi account as there is the need to enter some security code sent via SMS at some point. But the SIM card holding that number can obviously be on any phone!
About Xiaomi Fastboot drivers for Windows
I had several issues on making the Xiaomi Fastboot drivers working on my Windows PC: On my laptop running Windows 11, I had the issue that whenever the Xiaomi Unlock Tool was trying to connect, the Fastboot mode on the tablet just stopped with the message "press any key to shutdown". This seems to be a driver issue on some USB3 ports. Someone claimed there is a solution (see this post), but I used a Windows 10 laptop instead (also with only USB3 ports) and it worked OK there. Also, sometimes I connect the tablet via USB in Fasboot mode and I get no response on Windows (as nothing is attached). I solved it by uninstalling the device and re-installing the drivers manually that are provided in the Xiaomi Unlock Tool "driver" folder.
To check whether the drivers are working, just connect the tablet via USB while in Fastboot mode and check the Windows device manager. If device "Android Bootloader Interface" is properly installed (I got Xiaomi Drivers v16.0.0.0), you should be all set. If you get "Android device" or something with a question mark on it, I suggest to install manually the drivers (right click on the device, select "update drivers", then "Browse on my computer", and point to the "driver\win10" or "driver\xp-win7-win8" folder of the Xiaomi Unlock Tool).
If you have fastboot in your Windows PATH, read here, otherwise just ignore this
It seems that the Xiaomi Unlock Tool has a "fasboot.exe" in its own folder, which it has to use to unlock the bootloader. In my case, I already had adb and fastboot in my Windows PATH (so that I could just type "adb" in any CMD), and I think that the tool was using my fastboot version instead of its own one. The issue I had is that for some reason, the unlock process was hanging on 99%, and the tablet was then exiting fastboot and booting back to system. I checked the log and it seems to me that some fastboot commands were failing. As soon as I removed fastboot from Windows path, it magically worked. So my advice here is to simply remove whatever fastboot you have in the Windows path before using the unlock tool.
Unlocking steps I did
Finally, here's what I did to unlock it. Again, disclaimer: I don't know if these steps are 100% correct, but they worked in my case. So follow them at your own risk!
I did it on a Mi Pad 4 Wifi with the stock chinese ROM (running MIUI 10.3.2 & Android 8.1.0).
Go to Settings -> Mi Account and login to your Xiaomi account on the tablet, or if you don't have any, make one. Make sure the phone number you entered is reachable.
Go to Settings -> Additional settings -> Developer options and make sure "OEM Unlocking" and "USB Debugging" are turned on.
Still on the Developer options, go to "Mi Unlock Status". If it says "Unlocked", well guess what., you can stop here . If not, tap on "Add account and device" and wait for the success message. If you get something like "try later" (my case), what I did is to logout and re-login on the Xiaomi account. I then got the "success" message finally.
Download the Xiaomi Unlock Tool from here. Extract somewhere but do not start yet.
Open Windows Device Manager (Win+R, enter "devmgmt.msc").
Turn off the tablet and boot to Fastboot (Vol. Down + Power buttons). Now connect the tablet via USB.
First check on the tablet: if it shows "press any key to shutdown", then you have a driver issue. Please see this post for the solution, or try using a different PC.
Then, check on the device manager. If you see just "Android" with a question mark popping up, then you need to install the drivers. If you see "Android Bootloader Interface", then you are all set. If you don't see anything, then you need to uninstall and reinstall the drivers instead.
To install the drivers: right click on the device with question mark, select "update drivers", then "Browse on my computer", and point to the "driver\win10" or "driver\xp-win7-win8" folder where you extracted the Xiaomi Unlock Tool. After installing the drivers, try to boot to fastboot a second time. If you don't see the previously mentioned "press any key to shutdown", then you are all set.
To uninstall the device: On Windows Device Manager menu, go to "View" -> "Show hidden devices". You should find a greyed out "Android Bootloader Interface". Right click on it and select "Uninstall". Then, repeat the process again (boot to fastboot etc) and hopefully you will get the "Android device" with question mark where you can install drivers on.
Before starting the unlock tool, make sure you don't have any adb or fastboot in your windows PATH. You can check it by simply typing "fastboot --version" on any Windows CMD and see if it does something. In case you have, you better remove it, as the unlock tool has its own version of fastboot packed with it and you better let it use that one instead.
Once drivers are installed, start the Unlock Tool and login to your Xiaomi account. Then, once you see "not connected to the phone", boot the device to Fasboot again and quickly connect it via USB. If you see "Please wait 168 hours" or something like that (I did not see any of that), then most of the guides say that unfortunately you have to wait.
If you see the "Unlock button" not being grayed out anymore, then go for it. Get rid of the annoying popups saying "you are a bad person if you unlock", and finger crossed everything goes smooth!
Cheers,
Michele
Hi thank you for sharing this,
My Mipad 4 is LTE version, however the SIM only works when I turn on Wifi. Therefor, I can't start unlocking as I couldn't connect via Mobile Data.
Is there any solution for this?