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.
Related
Two days ago I tried to use Easy Root ToolV11 to root my device that's running 14.1.1.A.0.402 Model D6503, it said "waiting for device".
I looked something up a bit and tried to install ADB driver, but nothing shown up in my detected ANDROID device list even though it was already plugged in to my PC.
I also tried to set up ADB PATH by following a tutorial in this thread http://forum.xda-developers.com/showthread.php?t=2559009 but it didn't work.
In my device manager my device is under "portable devices" instead "android devices"
I also tried towelroot on my phone. It said that my phone is rooted, but root checker said "This device does not have proper root access"
Ps. usb debugging mode and unknown sources are enabled
edit:
The driver that was install for my device is from microsoft. (see pictures below)
I uninstalled the driver and it was reinstall again every time i plugged my device in. I tried to update the driver, but it said that my driver is already up to date.
GalosSide said:
Two days ago I tried to use Easy Root ToolV11 to root my device that's running 14.1.1.A.0.402 Model D6503, it said "waiting for device".
I looked something up a bit and tried to install ADB driver, but nothing shown up in my detected ANDROID device list even though it was already plugged in to my PC.
I also tried to set up ADB PATH by following a tutorial in this thread http://forum.xda-developers.com/showthread.php?t=2559009 but it didn't work.
In my device manager my device is under "portable devices" instead "android devices"
I also tried towelroot on my phone. It said that my phone is rooted, but root checker said "This device does not have proper root access"
Ps. usb debugging mode and unknown sources are enabled
Click to expand...
Click to collapse
Are you using Windows 8?
cpumaster said:
Are you using Windows 8?
Click to expand...
Click to collapse
im using windows 7 sp1
also I just realize that i cannot use Sony PC Companion to do anything with my device it said that internet connection is required, but I am already connected.
Not sure but perhaps the drivers were not correctly installed. Try this?
http://forum.xda-developers.com/showthread.php?t=2635830
hush66 said:
Not sure but perhaps the drivers were not correctly installed. Try this?
http://forum.xda-developers.com/showthread.php?t=2635830
Click to expand...
Click to collapse
I'm still getting the same problem with the driver install.
I think i know what the problem is right now. The driver that was install for my device is from microsoft. (see pictures 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"
}
I uninstalled the driver and it was reinstall again every time i plugged my device in. I tried to update the driver, but it said that my driver is already up to date.
Well, I just plugged in my Z2 to my PC and checked the driver details and it's exactly the same as yours. So it might not be an issue with the driver after all.
You mentioned that you have already done the ADB setup but it didn't work. When you said "it didn't work", do you mean the ADB couldn't be setup, or did you mean you still got the "waiting for device" message? To check if your ADB has been setup properly, go into the command prompt and type adb devices. You should see a serial number (of your phone) as the response.
And you should also have had the fastboot drivers installed. Use this tool to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2588979
hush66 said:
Well, I just plugged in my Z2 to my PC and checked the driver details and it's exactly the same as yours. So it might not be an issue with the driver after all.
You mentioned that you have already done the ADB setup but it didn't work. When you said "it didn't work", do you mean the ADB couldn't be setup, or did you mean you still got the "waiting for device" message? To check if your ADB has been setup properly, go into the command prompt and type adb devices. You should see a serial number (of your phone) as the response.
And you should also have had the fastboot drivers installed. Use this tool to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Finally it work!!!!
I'm rooting right now and it's stuck at cleaning up......what do i do now
GalosSide said:
Finally it work!!!!
I'm rooting right now and it's stuck at cleaning up......what do i do now
Click to expand...
Click to collapse
restart the install.bat file.. happens from time to time that it get stuck on cleaning up.
Check the official thread about Easy Root and you'll see loads of people had the same problem.
Just re-run the program and it will work.
Frantiic87a said:
restart the install.bat file.. happens from time to time that it get stuck on cleaning up.
Check the official thread about Easy Root and you'll see loads of people had the same problem.
Just re-run the program and it will work.
Click to expand...
Click to collapse
I did and it said "insmod: init_module '/data/local/tmp/wp_mod.ko' failed (File exists)"
edit:
I restart my phone and root again. It's finally rooted.
Thank you every one for helping me.
Thank you!
sorry we facing the same problem so please tell me if found a solution
ADB FASTBOOT Drivers
Nothing worked for me accept this one.
I went there downloaded this driver installed it and it did its magic.
https://www.driveridentifier.com/sc...14379&scanid=92D42FEE7DDD4826835F8C3C3611A400
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic 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"
}
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
@lost101, Need your expert advice on this. Others, please do help.
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices​
lost101 said:
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices​
Click to expand...
Click to collapse
Live booted uBuntu Raring Ringtail 13. Added the necessary repositories first ;
sudo add-apt-repository ppa: phablet-team/tools && sudo apt-get update
Click to expand...
Click to collapse
. Further installed the ADB & Fastboot ;
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
. Got success messages.
Further using the terminal, used two commands ;
sudo adb devices
Click to expand...
Click to collapse
sudo fastboot devices
Click to expand...
Click to collapse
The result was exactly the same which i get in Windows command prompt. The list of devices shows a blank. I've installed the drivers and rechecked them, the device is listed as "Motorola ADB Interface" under Device Manager :
and; shows as Fastboot condor S in hardware eject box.
I fail to understand why it isn't showing as connected only in the fastboot menu. Fastboot reason is given as "fall through from not charger boot mode". The device shows only the fastboot screen by default. If any other option like recovery etc is selected, it throws the error message as bootup failed. Scenario is exactly of the same pic which was posted in #1.
Please suggest the next step.
@BBThumbHealer - Starting to look like Bootloader corruption. An unbrick method could be applied to potentially restore a functional Bootloader. One exists for Falcon 5.1 - unsure about Condor at this time.
I would try to eliminate the USB cable as the problem by trying alternatives.
BBThumbHealer said:
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
Click to expand...
Click to collapse
I was stucked in the same problem yesterday. I succeeded and recovered my Moto E to live again.
As in the screenshot you posted. Your bootloader is locked. You need to unloack the bootloader. To do so follow the steps in the link given below :
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Login or create your Moto ID and follow the steps as described.
After that you'll have to flash the firmware again. hope this helps.
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 ??
Heyo
Following situation:
I tried to root and flash my old Sony Xperia Z3 compact which I have been using as an mp3 player. I successfully did so (I think), however when I wiped my data to flash to linage os, it gave me error 7. I assumed it was because my TWRP version was way out of date so I updated that, and hit "reboot into recovery" to activate the new twrp version.
Unfortunately the phone didn't boot into recovery and just wound up stuck at the sony screen without anything else since no OS is installed.
I can't boot into recovery manually either, it just boots into the sony logo and gets stuck there.
I do have a backup in twrp but I can't install that since I can't get into recovery, and I can't manually access the storage since usb debugging is not active while on the sony startup screen.
Is there anything I can do or is my z3c rip?
I can connect the phone in fastboot and flashmode and flashtool does recognize it, however I can't really seem to do anything while in flashmode and fastboot mode doesn't work since flashtool tells me I don't have the right drivers for the device, however when I try to install the driveres it hands out an error message
{
"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"
}
StanYz said:
Heyo
Following situation:
I tried to root and flash my old Sony Xperia Z3 compact which I have been using as an mp3 player. I successfully did so (I think), however when I wiped my data to flash to linage os, it gave me error 7. I assumed it was because my TWRP version was way out of date so I updated that, and hit "reboot into recovery" to activate the new twrp version.
Unfortunately the phone didn't boot into recovery and just wound up stuck at the sony screen without anything else since no OS is installed.
I can't boot into recovery manually either, it just boots into the sony logo and gets stuck there.
I do have a backup in twrp but I can't install that since I can't get into recovery, and I can't manually access the storage since usb debugging is not active while on the sony startup screen.
Is there anything I can do or is my z3c rip?
I can connect the phone in fastboot and flashmode and flashtool does recognize it, however I can't really seem to do anything while in flashmode and fastboot mode doesn't work since flashtool tells me I don't have the right drivers for the device, however when I try to install the driveres it hands out an error message
Click to expand...
Click to collapse
If your using Windows 10 you'll probably need a Windows 7 virtual machine if you don't have a physical PC with Windows 7 already installed. That or you'll need to turn on test mode for Windows
But if I may ask what fhe error(s) output whwn trying to install said drivers?
TheExploitedOne said:
If your using Windows 10 you'll probably need a Windows 7 virtual machine if you don't have a physical PC with Windows 7 already installed. That or you'll need to turn on test mode for Windows
But if I may ask what fhe error(s) output whwn trying to install said drivers?
Click to expand...
Click to collapse
I've attatched 4 screenshots in my OP, thats all I see, it doesn't actually state what the error is, just that it didn't finish.
Will it go through with win7? Actually that aside, is there a way to force a new os onto the phone via the flashtool to begin with?
Since your Windows computer needs to recognize the Xperia z3 based on Qualcomm chipset once connected, the PC should have installed proper USB drivers. which in no case depends on Windows version or Windows edition. You have to obtain the USB drivers and also the ADB / Fastboot drivers from OEM's / Carrier's website. It's never a good idea to install the ADB / Fastboot drivers elsewhere offered on WEB.
And once installed, restart the PC.
If successful then use
jwoegerbauer said:
Since your Windows computer needs to recognize the Xperia z3 based on Qualcomm chipset once connected, the PC should have installed proper USB drivers. which in no case depends on Windows version or Windows edition. You have to obtain the USB drivers and also the ADB / Fastboot drivers from OEM's / Carrier's website. It's never a good idea to install the ADB / Fastboot drivers elsewhere offered on WEB.
And once installed, restart the PC.
If successful then use
Click to expand...
Click to collapse
---
My carrier doesn't offer any drivers whatsoever.
But all of that aside, even if I do get fastboot running, is there even a way to force a new OS onto the phone via some tool?
Hi,
I am experiencing issues with my Poco M4 Pro 4G and trying to unlock the bootloader. What I am currently doing is the following;
I enabled developer options, enabled usb debugging and OEM unlocking. I went to unlock status hit agree and hit pair and have waited 7 days for the timer to run out
I shut down the phone and then enter fastboot by holding the volume down button and the power button at the same time.
I downloaded the mi flash unlock tool from here and I logged in using the same account as on the phone, and got up to this screen.
{
"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 then connect the phone which currently has the fastboot logo on to the computer but the button stays grey.
The following is what I have done;
I have installed adb tools. When the phone is booted and is connected to my computer I can see it via "adb devices" in CMD as admin. I can even send it to fastboot mode by "adb reboot fastboot"
I have installed the qualcomm drivers but I am unsure if they are the correct ones.
I have tried with different cables.
I have tried with different PCs.
The computer that I am using mainly to try and unlock the bootloader is a laptop and the specs are as follows;
Model: GP72 2QE Leopard Pro
Intel Core i7 5700HQ
16GB RAM
The other systems that I have tried are almost identifically specced both are AMD based on X570 Mobo and a Ryzen 7 3700X
There does seem to be a known problem with the Mi Unlock tool not being able to communicate properly with the system drivers. There are some tips for getting it working on this thread:
https://forum.xda-developers.com/t/...ol-cannot-detect-phone.3663139/#post-73566526
If that post doesn't solve the problem then try reading through the later posts in that thread.
Sorry for the late reply, I did the suggestion and it worked! Thank you for the help.
My goal was to flash the indonsian rom of the device onto and I had a bit of a problem last night I ended up sending it into a bootloop because the connection wasn't stable from the computer to the phone, I just woke up today and tried it again on a different computer and a brand new cable and the connection wasn't cutting out at all. I put it in fastboot and succesfulyl flashed it. I can't thank you enough for the help.
I just need to know if I need to close this thread or something now that my issue is complete. I'm new around here so I don't know if I shoudl do that.
The Spike Man said:
I just need to know if I need to close this thread or something now that my issue is complete. I'm new around here so I don't know if I shoudl do that.
Click to expand...
Click to collapse
No need, your experience may be shared by others in which case it will be useful to have somewhere to talk about it
The Spike Man said:
Hi,
I am experiencing issues with my Poco M4 Pro 4G and trying to unlock the bootloader. What I am currently doing is the following;
I enabled developer options, enabled usb debugging and OEM unlocking. I went to unlock status hit agree and hit pair and have waited 7 days for the timer to run out
I shut down the phone and then enter fastboot by holding the volume down button and the power button at the same time.
I downloaded the mi flash unlock tool from here and I logged in using the same account as on the phone, and got up to this screen.
View attachment 5681651
I then connect the phone which currently has the fastboot logo on to the computer but the button stays grey.
The following is what I have done;
I have installed adb tools. When the phone is booted and is connected to my computer I can see it via "adb devices" in CMD as admin. I can even send it to fastboot mode by "adb reboot fastboot"
I have installed the qualcomm drivers but I am unsure if they are the correct ones.
I have tried with different cables.
I have tried with different PCs.
The computer that I am using mainly to try and unlock the bootloader is a laptop and the specs are as follows;
Model: GP72 2QE Leopard Pro
Intel Core i7 5700HQ
16GB RAM
The other systems that I have tried are almost identifically specced both are AMD based on X570 Mobo and a Ryzen 7 3700X
Click to expand...
Click to collapse
Are u sure m4 pro 4g is qualcom ?
Thought is mediatek
aariss said:
Are u sure m4 pro 4g is qualcom ?
Thought is mediatek
Click to expand...
Click to collapse
It is mediatek.