Hello, I have a Blackview A8 (MT6580).
It works fine in the device manager:
Portable Devices: A8
USB Devices: ADB Interface
I run cmd as Administrator, and run "adb devices" command, it just show me "List of devices attached" and then the command prompt.
Can someone help me please?
Regards
homerangering said:
Hello, I have a Blackview A8 (MT6580).
It works fine in the device manager:
Portable Devices: A8
USB Devices: ADB Interface
I run cmd as Administrator, and run "adb devices" command, it just show me "List of devices attached" and then the command prompt.
Can someone help me please?
Regards
Click to expand...
Click to collapse
Install or update your ADB drivers.
Ashwinrg said:
Install or update your ADB drivers.
Click to expand...
Click to collapse
I have download some ADB drivers but how can I delete the current drivers from the device manager? When I press uninstall, it comes back when I plug in the smartphone agin. When I update the already installed driver, it says it was the newest update is already installed.
Sorry for my bad english.
homerangering said:
I have download some ADB drivers but how can I delete the current drivers from the device manager? When I press uninstall, it comes back when I plug in the smartphone agin. When I update the already installed driver, it says it was the newest update is already installed.
Sorry for my bad english.
Click to expand...
Click to collapse
When you connect your Android then it prompt for adb debugging? If not then download and install usb drivers of your android.
Ashwinrg said:
When you connect your Android then it prompt for adb debugging? If not then download and install usb drivers of your android.
Click to expand...
Click to collapse
When I connect my Android, it shows that it was connect as a media storage and that USB Debugging is active. On my PC, the media explorer gets open.
homerangering said:
When I connect my Android, it shows that it was connect as a media storage and that USB Debugging is active. On my PC, the media explorer gets open.
Click to expand...
Click to collapse
When you install proper usb drivers of your android then it prompt for adb debugging and detects in your pc.
Ashwinrg said:
When you install proper usb drivers of your android then it prompt for adb debugging and detects in your pc.
Click to expand...
Click to collapse
My PC detects the smartphone. I can go to my smartphone folders. In the device manager, there is a "MTP" device unter "USB Devices". It works fine, but I can't see any adb devices with the command prompt.
homerangering said:
My PC detects the smartphone. I can go to my smartphone folders. In the device manager, there is a "MTP" device unter "USB Devices". It works fine, but I can't see any adb devices with the command prompt.
Click to expand...
Click to collapse
When I tried to use adb on my android it also shows mtp, midi but I can't access adb. I also have installed adb drivers. When I installed my Lenovo usb drivers then it detects in pc command prompt.
homerangering said:
My PC detects the smartphone. I can go to my smartphone folders. In the device manager, there is a "MTP" device unter "USB Devices". It works fine, but I can't see any adb devices with the command prompt.
Click to expand...
Click to collapse
Does a pop-up show on your device requiring authorization of the computer for adb/usb-debugging ("RSA fingerprint")?
Your device installs the driver on plugging in - this the driver from which the computer can recognize your device. The ADB interface is another thing. If the ADB do not recognize your device (some can detect your device but says 'offline'), try downloading the latest version. If you only need the ADB, you could download Minimal ADB and Fastboot by shimp208 .
rolland.arriza said:
Does a pop-up show on your device requiring authorization of the computer for adb/usb-debugging ("RSA fingerprint")?
Your device installs the driver on plugging in - this the driver from which the computer can recognize your device. The ADB interface is another thing. If the ADB do not recognize your device (some can detect your device but says 'offline'), try downloading the latest version. If you only need the ADB, you could download Minimal ADB and Fastboot by shimp208 (search it here).
Click to expand...
Click to collapse
Thank you for your help.
I have download and install the ADB and Fastboot by shimp208.
Now, I can see the adb device (my smartphone).
But with my adb.exe of my DroidCam program, it shows still no devices. I want to use DroidCam with USB on my smartphone, but the adb.exe of the program didn't identify any adb devices. (See picture)
Regards.
Left: DroidCam
Right: ADB and Fastboot by shimp208
{
"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"
}
homerangering said:
Thank you for your help.
I have download and install the ADB and Fastboot by shimp208.
Now, I can see the adb device (my smartphone).
But with my adb.exe of my DroidCam program, it shows still no devices. I want to use DroidCam with USB on my smartphone, but the adb.exe of the program didn't identify any adb devices. (See picture)
Regards.
Click to expand...
Click to collapse
Hello there. Save a copy of your DroidCam program (backup). Then replace the ADB of your program (adb.exe, AdbWinApi.dll, and AdbWinUsbApi.dll) with the Minimal ADB and Fastboots'.
Simply copy adb.exe, AdbWinApi.dll, and AdbWinUsbApi.dll from Minimal ADB to your DroidCam program and replace them.
Then try running the adb from your program. Hope it works.
rolland.arriza said:
Hello there. Save a copy of your DroidCam program (backup). Then replace the ADB of your program (adb.exe, AdbWinApi.dll, and AdbWinUsbApi.dll) with the Minimal ADB and Fastboots'.
Simply copy adb.exe, AdbWinApi.dll, and AdbWinUsbApi.dll from Minimal ADB to your DroidCam program and replace them.
Then try running the adb from your program. Hope it works.
Click to expand...
Click to collapse
Thank you!!!! It works!!!!!! :good:
Related
Hi,
When I start up adb and use the command "Adb devices" my device show. I want to use adb shell, so I type "Adb shell" ofc. Then, when I try "Adb devices", my device does not show :/ Anyone have a solution?
First thing first, make sure you have USB debugging on.
To do this, go into About Phone, tap the build number 7 times (this should give you a toast notification that you are now a developer).
Go back, now go into the developer options what has come up above about phone.
Tick the USB Debugging box, and then connect your phone and try to connect with adb shell.
If this doesn't work, revoke USB debugging authorisations, then try adb shell again.
gamer649 said:
First thing first, make sure you have USB debugging on.
To do this, go into About Phone, tap the build number 7 times (this should give you a toast notification that you are now a developer).
Go back, now go into the developer options what has come up above about phone.
Tick the USB Debugging box, and then connect your phone and try to connect with adb shell.
If this doesn't work, revoke USB debugging authorisations, then try adb shell again.
Click to expand...
Click to collapse
That didn't work :/ Any other suggestions?
Have you installed the ADB drivers and drivers for the board set the Z2 uses?
gamer649 said:
Have you installed the ADB drivers and drivers for the board set the Z2 uses?
Click to expand...
Click to collapse
At least flashtool says I have ADB drivers installed?
Skanin said:
At least flashtool says I have ADB drivers installed?
Click to expand...
Click to collapse
I'm not sure what to suggest then. @Envious_Data any suggestions?
gamer649 said:
I'm not sure what to suggest then. @Envious_Data any suggestions?
Click to expand...
Click to collapse
{
"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"
}
A screenshot of what happens, if that helps
you're already connected in adb mode, as your pic shows, so why would you need to use adb devices again ?
what are you trying to do ? you've successfully connected to your device in adb mode and used the su command, so what do you want to do ?
ticktock666 said:
you're already connected in adb mode, as your pic shows, so why would you need to use adb devices again ?
what are you trying to do ? you've successfully connected to your device in adb mode and used the su command, so what do you want to do ?
Click to expand...
Click to collapse
Yeh, I know.. But I want to use the command "adb remount rw /system". If use it without "abd shell" I get a permission denied error, and in "adb shell" I get error: device not found.. (see picture)
Skanin said:
Yeh, I know.. But I want to use the command "adb remount rw /system". If use it without "abd shell" I get a permission denied error, and in "adb shell" I get error: device not found.. (see picture)
Click to expand...
Click to collapse
Note, don't use any quotes for the below commands.
1) Connect device to computer.
2) Type "adb shell" in cmd, then press enter.
3) Type "su", then press enter.
4) Type "mount -o rw,remount /system", then press enter.
Congratulations, it is now remounted. ADB devices will not work on the device, as the device cannot connect to itself to itself via USB.
what gamer said, you were simply using the wrong command for mounting
Hello, it is better if you view this thread on pc or on browser. Viewing via XDA app or XDA Lab app will make you crazy.
{
"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"
}
Can't you use fasboot commands even your phone is in fastboot mode and connected to computer?
Can't you install TWRP or anything via fastboot mode even if have entered fastboot mode and connected to computer?
Here is the solution! You just need to install your drivers on your computer correctly. On this thread, I will show you how to install fastboot and adb drivers on computer for our Redmi 3s.
Requirements
-A windows based computer
-15 seconds adb installer by @Snoop05
This method will work for every android devices which are based on Android Marshmallow (SDK 23) or devices with android Nougat 7.1.1 (SDK 25) by Custom ROMs.
OK, let's start!
Step1-Disconnect your android device from computer,
Step2-Download and install 15 second ADB installer from here:https://forum.xda-developers.com/showthread.php?t=2588979
Step3-Enter your android device to fastboot mode,
Step4-Connect your android device to computer,
Step5-Open device manager in computer,
Step6-Right click on the 'Android' under 'Other devices' and select 'Update Driver Software...',
Step7-Select 'Browse my computer for driver software',
Step8-Click on 'Let me pick from a list of device drivers on my computer',
Step9-Select 'Android Device' and click 'Next',
Step10-Select 'Android ADB Interface' and click 'Next',
Step11-Do step 6-7-8-9-10 and Select 'Android Bootloader Interface' and click 'Next',
Step12-Do step 6,7,8,9,10 and Select 'Android Composite Interface' and click 'Next'.
If you have already done all steps above, your fastboot mode is working well again, Congrats!
You can see everything that needs fastboot is working well,
Devices I used:
-A computer with windows 8,
-Xiaomi Redmi 3s Prime.
Credits
@Snoop05 for 15second adb installer.
Sorry for my bad English btw.
Thread by MyoHtet (aka BM Heades).
i followed all the steps but in the end get an error of 'could not load recovery.img' pls help
BM Heades said:
Hello, it is better if you view this thread on pc or on browser. Viewing via XDA app or XDA Lab app will make you crazy.
Can't you use fasboot commands even your phone is in fastboot mode and connected to computer?
Can't you install TWRP or anything via fastboot mode even if have entered fastboot mode and connected to computer?
Here is the solution! You just need to install your drivers on your computer correctly. On this thread, I will show you how to install fastboot and adb drivers on computer for our Redmi 3s.
Requirements
-A windows based computer
-15 seconds adb installer by @Snoop05
This method will work for every android devices which are based on Android Marshmallow (SDK 23) or devices with android Nougat 7.1.1 (SDK 25) by Custom ROMs.
OK, let's start!
Step1-Disconnect your android device from computer,
Step2-Download and install 15 second ADB installer from here:https://forum.xda-developers.com/showthread.php?t=2588979
Step3-Enter your android device to fastboot mode,
Step4-Connect your android device to computer,
Step5-Open device manager in computer,
Step6-Right click on the 'Android' under 'Other devices' and select 'Update Driver Software...',
Step7-Select 'Browse my computer for driver software',
Step8-Click on 'Let me pick from a list of device drivers on my computer',
Step9-Select 'Android Device' and click 'Next',
Step10-Select 'Android ADB Interface' and click 'Next',
Step11-Do step 6-7-8-9-10 and Select 'Android Bootloader Interface' and click 'Next',
Step12-Do step 6,7,8,9,10 and Select 'Android Composite Interface' and click 'Next'.
If you have already done all steps above, your fastboot mode is working well again, Congrats!
You can see everything that needs fastboot is working well,
Devices I used:
-A computer with windows 8,
-Xiaomi Redmi 3s Prime.
Credits
@Snoop05 for 15second adb installer.
Sorry for my bad English btw.
Thread by MyoHtet (aka BM Heades).
Click to expand...
Click to collapse
USB not recognized
But in my case it is showing under universal serial bus drivers and written unknown device and when I connect to computer in fastboot mode it says USB not recognised I used it on redmi 4A with A PC running on Windows 7 ultimate x 86 please help me to find out it
Hi to everybody
I am trying to correctly connect my new Ticawatch Pro with WearOS to my notebook win 7 Ultimate TEST MODE
The procedure is asking to put in fastboot mode the device but I can't because I don't know the procedure
Is there any workaround ??
I want underline that on this notebook I am able to connect without problems all my android devices like Xiaomi Mia1, Mi6, LG Nexus 5X and others
EDIT
I have applied the procedure having he smartwatch switched ON (=adb mode)
Now when I connect the device to the netbook it is recognized as ADB device:
I can see it into Manage resources (as Android Composite ADB Interface),
I can see it under list of USB devices (as Ticwatch pro)
BUT I CANNOT see it into Explorer in order to explore its hard memory space
Any suggestions ??
Hello,
So I am going to unlock the bootloader on my device. However...
Adb will recognize my device but in fastboot mode it won't. Fastboot devices show nothing.
I have already installed every necessary driver (universal adb driver, miflash drivers, official xiaomi usb driver, qualcomm driver, android sdk, etc...)
But still, fastboot unable to recognize my device...
But when I plug in other device (in my case, Mi A2) in fastboot mode, it recognizes successfully. So I don't know what to do next...
My device is currently in global version 10.3.9.0.PFQMIXM (Nov security)
Any help is appreciated! Thank you.
Connect A3 to the PC and open device manager. Is the driver installed correctly (no exclamation mark)? What is the device name in device manager?
_mysiak_ said:
Connect A3 to the PC and open device manager. Is the driver installed correctly (no exclamation mark)? What is the device name in device manager?
Click to expand...
Click to collapse
It did show as Android Composite ADB interface, I tried updating those drivers as well, but won't help...
Edit: Problem solved after uninstalling and reinstalling all the related drivers, now fastboot would recognize my phone. Thanks for your help anyways.
MarcusMario0605 said:
It did show as Android Composite ADB interface, I tried updating those drivers as well, but won't help...
Click to expand...
Click to collapse
Manually reinstall drivers and choose correct device type (android bootloader if I remember correctly). Automatic installation most probably won't work on recent Windows versions.
Edit: nevermind if you already fixed it [emoji846]
Fastboot not recognized
MarcusMario0605 said:
Edit: Problem solved after uninstalling and reinstalling all the related drivers, now fastboot would recognize my phone. Thanks for your help anyways.
Click to expand...
Click to collapse
I have the same problem with a recently acquired Mi A3 running android 10 with the security update Oct 5, 2020 connecting to Win10. I have used MiUsbDriver.exe from miflash_unlock to install drivers. It is recognized by adb devices and shows up in Win10 Device Manager as shown below:
{
"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"
}
However, after adb reboot bootloader, I see the Fastboot image on the A3, but fastboot devices finds nothing and nothing shows in Device Manager. If I rerun MiUsbDriver.exe while the phone is showing the fastboot screen I get
but nothing happens when I connect and reconnect the USB cable.
I have tried multiple usb cables on 2 different Win10 machines and one linux machine with both USB 2 and USB 3 ports and have never been able to make a connection when in fastboot mode on the phone.
using the same machines and cables fastboot works fine with connections to a Pixel 2XL and a LG V20.
You mention uninstalling and reinstalling the related drivers. Which drivers are "related"?
Any other suggestions to get the PC to recognize the phone in fastboot mode?
update: the next morning, tried yet another USB cable and fastboot now recognized. No explanation.
holistone said:
I have the same problem with a recently acquired Mi A3 running android 10 with the security update Oct 5, 2020 connecting to Win10. I have used MiUsbDriver.exe from miflash_unlock to install drivers. It is recognized by adb devices and shows up in Win10 Device Manager as shown below:
However, after adb reboot bootloader, I see the Fastboot image on the A3, but fastboot devices finds nothing and nothing shows in Device Manager. If I rerun MiUsbDriver.exe while the phone is showing the fastboot screen I get
but nothing happens when I connect and reconnect the USB cable.
I have tried multiple usb cables on 2 different Win10 machines and one linux machine with both USB 2 and USB 3 ports and have never been able to make a connection when in fastboot mode on the phone.
using the same machines and cables fastboot works fine with connections to a Pixel 2XL and a LG V20.
You mention uninstalling and reinstalling the related drivers. Which drivers are "related"?
Any other suggestions to get the PC to recognize the phone in fastboot mode?
update: the next morning, tried yet another USB cable and fastboot now recognized. No explanation.
Click to expand...
Click to collapse
link??
Sami Devo said:
link??
Click to expand...
Click to collapse
"link??" to what?
holistone said:
"link??" to what?
Click to expand...
Click to collapse
software that fixed u
Sami Devo said:
software that fixed u
Click to expand...
Click to collapse
reread the update at the bottom of the post: fixed with a different USB cable, no change of software. It seems not all USB cables are created equal. I don't know how to tell in advance the difference between them. My other USB cables worked for fastboot on different phones, but only one of the cables worked with the Mi A3 fastboot.
i got Huawei Mediapad T3 10 but storage to install app is very limted
so any app to make installation app in sd card momery
as i read the device not support that
but in ask any app or method to solve this
ant_gamal said:
i got Huawei Mediapad T3 10 but storage to install app is very limted
so any app to make installation app in sd card momery
as i read the device not support that
but in ask any app or method to solve this
Click to expand...
Click to collapse
You achieve this via ADB: Run the following command to set the default install location to your SD card:
Code:
adb shell pm setInstallLocation 2
Of course you will be required to enable the USB debugging option in the Developer option and download the ADB client on your computer - if not already done yet. To enable Developer option, go to Settings > About device > Build number and tap Build number seven times. Once activated, you will see a message that reads, “You are now a developer”. After enabling USB debugging, plug in your phone to your PC using USB and invoke ADB.
jwoegerbauer said:
You achieve this via ADB: Run the following command to set the default install location to your SD card:
Code:
adb shell pm setInstallLocation 2
Of course you will be required to enable the USB debugging option in the Developer option and download the ADB client on your computer - if not already done yet. To enable Developer option, go to Settings > About device > Build number and tap Build number seven times. Once activated, you will see a message that reads, “You are now a developer”. After enabling USB debugging, plug in your phone to your PC using USB and invoke ADB.
Click to expand...
Click to collapse
thank could you give me link to ADB and how to use
sorry i am not expert
i entered developer mode already
ant_gamal said:
thank could you give me link to ADB and how to use
sorry i am not expert
i entered developer mode already
Click to expand...
Click to collapse
Supposed your desktop is a Windows machine:
Matching ADB driver you'll get here
You preferredably install it to C:\ADB
You add C:\ADB to Windows PATH variable to easily access ADB from anywhere
Code:
set PATH=%PATH%;C:\ADB
You reboot Windows & reboot your HUAWEI
You connect your HUAWEI and Windows machine via USB cable
You open Windows command prompt and run following commands - one by one
Code:
adb devices
adb shell pm setInstallLocation 2
HTH
jwoegerbauer said:
Supposed your desktop is a Windows machine:
Matching ADB driver you'll get here
You preferredably install it to C:\ADB
You add C:\ADB to Windows PATH variable to easily access ADB from anywhere
Code:
set PATH=%PATH%;C:\ADB
You reboot Windows & reboot your HUAWEI
You connect your HUAWEI and Windows machine via USB cable
You open Windows command prompt and run following commands - one by one
Code:
adb devices
adb shell pm setInstallLocation 2
HTH
Click to expand...
Click to collapse
my pc run with win10 and i did what you say but could not run any line
see photos
{
"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"
}
i use left shift with right click
device not found although i connect the tab
@ant_gamal
I can't open the images provided.
jwoegerbauer said:
@ant_gamal
I can't open the images provided.
Click to expand...
Click to collapse
i tried many site to upload photos
if not view plz suggest web host site
@ant_gamal
Oops, was my fault:
Deprecated syntax
Code:
adb shell pm setInstallLocation 2
New syntax ( Android 4x)
Code:
adb shell pm set-install-location 2
Example screenshot:
Note: First switch from PS to CMD
i did not restart pc or tab
i did but say adb not recognize
i attach the tab and choose transfer file
then i tried what you said and give me this in photo
is there is any package software need to install first before do this commend line
ant_gamal said:
is there is any package software need to install first before do this commend line
Click to expand...
Click to collapse
No.
What you're doing wrong is entering an invalid path/to/ADB: in your case is must be C:\ADB\adb
is there is any tool
does not work
same message device not found
ant_gamal said:
is there is any tool
does not work
same message device not found
Click to expand...
Click to collapse
Of course you can install on your Android device a Terminal Emulator, if not done yet, and therein run command
Code:
pm set-install-location 2
FYI: I no longer participate on this thread, sorry for this.
jwoegerbauer said:
The tool to be used is ADB, nothing else.
FYI: I no longer participate on this thread, sorry for this.
Click to expand...
Click to collapse
i think problem that not recognize the device
ant_gamal said:
i think problem that not recognize the device
Click to expand...
Click to collapse
I've edited my post you quoted: re-read it.
hi, i have same problem with mediapad T3, lower space.
i make procedure adviced from jwoegerbauer.
first command: Ok, i see device connected
second command: Error: java.lang.SecurityException: Package Android does not belong to 2000
any help? thank you
Hey!
I am having difficulties unlocking the bootloader of my Redmi Note 5. I have already rooted a meizu phone and a lenovo tablet before and had no problems. However, with this one, I am able to enter the bootloader using the following command.
Code:
adb reboot bootloader
However, when I do this:
Code:
fastboot oem unlock
It outputs the following:
Code:
FAILED (remote: 'Token Verify Failed, Reboot the device')
fastboot: error: Command failed
The command
Code:
fastboot oem unlock-go
outputs the same results and rebooting my phone doesn't resolve the issue.
Additionnaly, using the Miui Unlock App doesn't work because it doesn't recognise my phone when in bootloader.
Please help!
Thanks in advance.
PS: I am using a Win10 64bits PC
Edit: I tried an older version of Miui Unlock and it detected my device, but couldn't unlock it. It stopped at 99% and output "couldn't unlock"
IMHO it's always recommended to check for boot-loader can get unlocked
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
0
Seppppx said:
You are supposed to use the mi unlock tool. Not these simple fastboot commands (xiaomi wants to make unlocking complicated)
Here is a steb-by-step guide
1. Make a Mi account
2. Apply for an unlock here https://en.miui.com/unlock/
3. Download Mi unlock by clicking on the unlock now and then download Mi Unlock.
4. Download the Mi Unlock app to PC, and sign in with your Mi Account;
5. Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot.
6. Connect your phone to PC using USB cable and click "Unlock".
You will probably have to wait some time (3 days, maybe a week or even a month).
it's been some time since I have unlock my Xiaomi phone so these steps might be wrong. If yes point that out please.
Click to expand...
Click to collapse
As I said in my post, I have tried using Mi Unlock. I have done all your steps up to the 6th because the app doesn't allow me to click unlock. I am guessing that it doesn't detect my phone in fastboot mode. About the time I have to wait, is it the time between when I apply for an unlock and when I can unlock my phone? This would explain why I can't unlock it. However I saw on another thread that Xiaomi removed the need to apply and wait to be able to unlock a phone. I don't really know how to feel about this one...
0
Seppppx said:
Do you have fastboot/adb drivers installed?
Click to expand...
Click to collapse
I'm pretty sure I do, because I have already rooted devices before. How do I check?
0
Seppppx said:
To check your drivers (and install) do this.
1. Plug your phone to the Pc.
2. Boot to fastboot (use googles platform tools, download below)
3. Open CMD as an administrator.
4. Navigate to the folder there you have platform tools in.
5. Type "fastboot devices" if you see no output you either have the wrong drivers installed or not installed
(Download the Google USB driver linked down)
6. To install drivers you open your Device Manager in windows.
7. Look for something like "Android Device" there. If it also has a warning sign that means that there are no drivers.
8. Right click on "Android Device"
9. Click on "Update driver"
10. Click on "Browse my computer for driver software"
11. Click on "Let me pick from a list of available drivers on my computer"
12. Click on "Have Disk..."
12. Browser for a driver under "Copy manufacturer's files from:"
13. Find the driver folder in the folder you saved it to and open it.
14. Double click on "android_winusb.inf
15. Click on "OK"
16. Click on "Next"
Done, you have installed a driver.
Download the Google fastboot/adb here https://developer.android.com/studio/releases/platform-tools
Direct download https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Download the google fastboot/adb driver here https://developer.android.com/studio/run/win-usb
Direct download https://dl.google.com/android/repository/usb_driver_r12-windows.zip
Click to expand...
Click to collapse
Well, I tried and went up to step 5 and there was no output. So I continued the steps, on step 7 I saw that my Adroid Device Driver had no warning sign, meaning that I have the wrong drivers. I continued on with your steps. After step 11, the control pannel shows 2 drivers named as "Android Bootloader Interface", however before step 15, the control pannel shows 3 different drivers named as "Android ADB Interface", "Android Bootloader Interface" and "Android Composite ADB Interface". The second one is selected by default, so I click ok and it installs. However, the "adb devices" and "fastboot devices" commands still show nothing in the command prompt. Is there something I am doing wrong?
0
Seppppx said:
You should reboot your phone after installing these drivers. I had the same problem, that fixed it.
Click to expand...
Click to collapse
Still nothing... There is no output to "adb devices" even after I install the driver and reboot my phone.
0
DemonBlu3000 said:
Still nothing... There is no output to "adb devices" even after I install the driver and reboot my phone.
Click to expand...
Click to collapse
{
"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"
}
Xiaomi USB Drivers are essential while connecting your smartphone in Fastboot Mode & Emergency Download Mode [EDL].
Seppppx said:
Do you get an output to "fastboot devices" that's the thing that matters when unlocking. I managed to my redmi note 4 to unlock without adb.
You also can get adb in the classic system where you boot. That works for me.
Click to expand...
Click to collapse
No, "fastboot devices" has no output on my computer, but it has one on another computer for some reason. On mine it doesn't and I need it to on mine.
0
Okay guys I figured it out. I was missing a step. I indeed had to use the Mi Unlock tool, but before doing so I had to enable an option beneath the "OEM unlock option", I don't remember how it was called but everything's fine now!