Unlock tool seems not to work - Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans

I installed the universal adb drivers and rebooted.
I "installed" the tools (adb and fastboot).
I enabled USB debugging.
I run "adb devices", authorized the PC and saw my phone connected.
I successfully signed in with the unlocking tool.
But my phone isn't listed.
The unlocking tool log file mentions my f2 pro, though.
Any hint?

Is the files are same?
{
"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"
}
Did you follow this procedure?
https://c.mi.com/thread-2262302-1-0.html

NOSS8 said:
Is the files are same?
View attachment 5389529
Did you follow this procedure?
https://c.mi.com/thread-2262302-1-0.html
Click to expand...
Click to collapse
Very similar but not exactly the same: I downloaded the files from the link in lineageos lmi page.
In particular, the tool is "miflash_unlock-en-5.5.224.24.zip" from mi.com: it's the latest version.
Will try again with your link, even if it's not 100% clear.
Thanks: will keep posted with news.
Current steps.
1. Log into the unlocking tool
2. Put pone in fastboot mode
3. Run the tool, connect via USB and hit refresh: NO OUTPUT
4. Close the tool and from CMD run "fastboot.exe devices": NO OUTPUT
5. Put phone in normal mode w/ USB debugging
6. From CMD run "adb.exe devices": device is listed
7. Hold on

I am unable to execute step no.3 from MI forum:
> 3. Use another PC (64-bit) to unlock if MI Unlock Tool fails to detect your device/ unknown error.
As I only have 1 Windows PC, as per my religion.

Uqbar said:
I am unable to execute step no.3 from MI forum:
> 3. Use another PC (64-bit) to unlock if MI Unlock Tool fails to detect your device/ unknown error.
As I only have 1 Windows PC, as per my religion.
Click to expand...
Click to collapse
I am using version 4.5.813.51.
I had a similar problem in 2020 with MiUnlock, the phone would disconnect when launching the program, solved using an older w10 pc.
Try to use an old version of miUnlock to have the same files as on my capture above.(Install the programs at the root of the disk).
Remove all drivers and restart (show hidden devices).
Install platform-tools. (Install the program at the root of the disk)
With Miunlock install the drivers.
Don't forget to enable usb debugging.
Connect the phone before launching miUnlock.
good luck.

Do you mean i shouldn't install the universal adb drivers?
Which drivers is the mi.com website referring to?

Uqbar said:
Do you mean i shouldn't install the universal adb drivers?
Which drivers is the mi.com website referring to?
Click to expand...
Click to collapse
yes.and verify in peripheral devices(remove manually if if necessary).
All drivers are with Miunlock ant platform-tools.

you can also download this program (which will be useful later) and install the drivers with it.
Are you logged in with your Xiaomi account on Mi Unlock? No need to connect the phone

Yes i am logged in...

NOSS8 said:
you can also download this program (which will be useful later) and install the drivers with it.
Are you logged in with your Xiaomi account on Mi Unlock? No need to connect the phone
Click to expand...
Click to collapse
So I don't need any USB driver (they are thus irrelevant). It's all internet-bound.
Are you sure? I don't see my phone, yet. How long do I need to wait?

Uqbar said:
So I don't need any USB driver (they are thus irrelevant). It's all internet-bound.
Are you sure? I don't see my phone, yet. How long do I need to wait?
Click to expand...
Click to collapse
Install drivers with Miunlock and miflash
Usb debugging do you see your phone on the pc?
Fastboot mode do you see your phone on the pc?
which version of W10?

If you have whatsapp ,message me here,its easy bro,you are doing something little wrong

Uqbar said:
I installed the universal adb drivers and rebooted.
I "installed" the tools (adb and fastboot).
I enabled USB debugging.
I run "adb devices", authorized the PC and saw my phone connected.
I successfully signed in with the unlocking tool.
But my phone isn't listed.
The unlocking tool log file mentions my f2 pro, though.
Any hint?
Click to expand...
Click to collapse
disable drivers signature check in windows, afyer that install fastboot drivers

Related

Trying to install /e/OS on FP3, but it hangs on fastboot on Windows 10

Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
{
"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 someone point me into the right direction?
Nijs said:
Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
Can someone point me into the right direction?
Click to expand...
Click to collapse
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I do not see the interface you mention, however, I see 'Android' under 'other devices' and 'FP3' under 'portable devices' and 'Google Nexus ADB Interface' under SAMSUNG Android Phone (I did not install this, I assume Windows did this in the background).
Which option should I select to install the driver manually? Or none of them?

Device descriptor request failed after connecting redmi note 5 pro

Hi there,
I had reboot my Redmi note 5 pro in fastboot mode, (shown in capture4 picture). Then i tried to read the fastboot devices connected to my system using the command- "fastboot devices". Then, in the devices it showed a devices but with "??????" like id. After that it got disconnected. Now when I am trying to connect my phone to the system, then "USB device not recognized" error is coming.
I tried to connect my mobile in another system, but there also same error is coming. The problem is not getting solved. I even made factory reset by going to settings, to try to make the phone read in system as earlier. But it is not getting recognized now. What should I do. Please help.. I am attaching screenshots.
{
"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"
}
Download Xiaomi's USB driver ( ADB & Fastboot ) suitable to your phone to PC and install it on PC, if not already yet.
Xiaomi Driver.zip - Devdrive - File Hosting For Publishers
Download file - Xiaomi Driver.zip
devdrive.cloud
jwoegerbauer said:
Download Xiaomi's USB driver ( ADB & Fastboot ) suitable to your phone to PC and install it on PC, if not already yet.
Xiaomi Driver.zip - Devdrive - File Hosting For Publishers
Download file - Xiaomi Driver.zip
devdrive.cloud
Click to expand...
Click to collapse
It's installed, it's not working. The phone is not getting read in the system altogether. the USB device is getting recognized, neither in ADB devices nor in device manager or in my computer.
In Windows Device Manager ADB isn't shown under heading "Universal Serial Bus controllers" but under heading "ADB Interface" or "Android Phone" or similar, and this only when phone is connected to PC and ADB server got started.
jwoegerbauer said:
In Windows Device Manager ADB isn't shown under heading "Universal Serial Bus controllers" but under heading "ADB Interface" or "Android Phone" or similar, and this only when phone is connected to PC and ADB got started.
Click to expand...
Click to collapse
Do you think I don't know this? I know how to view ADB devices very well. The phone is not showing anywhere. Please try to understand fully.
jwoegerbauer said:
In Windows Device Manager ADB isn't shown under heading "Universal Serial Bus controllers" but under heading "ADB Interface" or "Android Phone" or similar, and this only when phone is connected to PC and ADB server got started.
Click to expand...
Click to collapse
The phone is connected, ADB drivers and Xiaomi drivers are installed, still the phone is not showing in device manager. The phone is altogther not recoginzed by system. It's a different issue. The phone is even not shown in my computer or anywhere, just not recognized USB device.
USB debugging enabled?
xXx yYy said:
USB debugging enabled?
Click to expand...
Click to collapse
yes, it's enabled.
Brother, I am facing this problem too. Did You solve this problem ? Please tell me the solution.
@amitrajhello did you find any solution? I am facing the same issue with Poco m2 pro.
Hey I got Same Error in RN5 Pro, Any Fix???
Have you tried a different USB Cable?
amitrajhello said:
yes, it's enabled.
Click to expand...
Click to collapse
Or, https://softwarekeep.com/help-cente...uest-failed-unknown-usb-device-in-windows-10/
See if that works for you.
Creepergames360 said:
Have you tried a different USB Cable?
Or, https://softwarekeep.com/help-cente...uest-failed-unknown-usb-device-in-windows-10/
See if that works for you.
Click to expand...
Click to collapse
Hey, if you own a RN5 Pro Please drop the Hardware Id's like this (https://xiaomi.eu/community/attachments/fastboot-jpg.33150/) while phone is connected to pc in fastboot mode
because maybe by using this (https://forum.xda-developers.com/t/...r-request-failed-fastboot-windows-10.3375320/) I can Fix my Driver Issue!!

OnePlus 8 T-Mobile Conversion Problem

Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
{
"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"
}
because the driver is not installed for recovery I think:
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!
Costik said:
Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
View attachment 5499393
because the driver is not installed for recovery I think:
View attachment 5499395
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!
Click to expand...
Click to collapse
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.
SilverZero said:
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.
Click to expand...
Click to collapse
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.
Costik said:
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.
Click to expand...
Click to collapse
Yep, I think that's exactly what I did. I can't remember which fastboot drivers I updated to bit I'll bet they're both the same, and that's the point in the process where I updated drivers as well.
Cheers!

Question MiUnlockTools doesn't detect my phone

Hi everyone,
I wanna unlock bootloader of my phone, but MiUnlockTools doesn't detect it, however `fastboot devices` command show device. I tried different versions of MiUnlockTools (6.5.314.7, 5.5.224.24, 4.5.814.51), different bootloader interface drivers: by Google of 2013 and by Xiami of 2016, nothing changed.
Also I tried to install XiaoMiTool V2, it recognize device and switch from fastboot to system with adb, and Mi PC Suite, all was useless.
I use Windows 10.0.19044 with Test Mode and with disabled driver signification, stock USB Cable with USB 2.0 port, usb debugging and OEM is enabled in MIUI, all tools was executed in administrator mode.
I read lot of threads with same issues, tried all suggested solutinons, bot nothing works. Does anyone can help me?
{
"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"
}
ulanzetz said:
Hi everyone,
I wanna unlock bootloader of my phone, but MiUnlockTools doesn't detect it, however `fastboot devices` command show device. I tried different versions of MiUnlockTools (6.5.314.7, 5.5.224.24, 4.5.814.51), different bootloader interface drivers: by Google of 2013 and by Xiami of 2016, nothing changed.
Also I tried to install XiaoMiTool V2, it recognize device and switch from fastboot to system with adb, and Mi PC Suite, all was useless.
I use Windows 10.0.19044 with Test Mode and with disabled driver signification, stock USB Cable with USB 2.0 port, usb debugging and OEM is enabled in MIUI, all tools was executed in administrator mode.
I read lot of threads with same issues, tried all suggested solutinons, bot nothing works. Does anyone can help me?
View attachment 5565555
Click to expand...
Click to collapse
try with another PC.
had the same issue with an amd pc... if you can try iy on a intel pc.
use this mi flash tool to install drivers *2021.02.26
and i use this unock tool
Change your usb chord
wendale1231 said:
Change your usb chord
Click to expand...
Click to collapse
read the post, it's already done.
ulanzetz said:
Hi everyone,
I wanna unlock bootloader of my phone, but MiUnlockTools doesn't detect it, however `fastboot devices` command show device. I tried different versions of MiUnlockTools (6.5.314.7, 5.5.224.24, 4.5.814.51), different bootloader interface drivers: by Google of 2013 and by Xiami of 2016, nothing changed.
Also I tried to install XiaoMiTool V2, it recognize device and switch from fastboot to system with adb, and Mi PC Suite, all was useless.
I use Windows 10.0.19044 with Test Mode and with disabled driver signification, stock USB Cable with USB 2.0 port, usb debugging and OEM is enabled in MIUI, all tools was executed in administrator mode.
I read lot of threads with same issues, tried all suggested solutinons, bot nothing works. Does anyone can help me?
View attachment 5565555
Click to expand...
Click to collapse
thats not what you are supposed to be using
Follow this guide
d_g_m_2000 said:
had the same issue with an amd pc... if you can try iy on a intel pc.
Click to expand...
Click to collapse
Thanks, I also used AMD PC. Just installed Windows on my Intel MacBook Pro and all works.
Seems to be bug on AMD
ulanzetz said:
Thanks, I also used AMD PC. Just installed Windows on my Intel MacBook Pro and all works.
Seems to be bug on AMD
Click to expand...
Click to collapse
I think more that it's some version of Windows because I had exactly the same problem with a w10 Intel pc and it worked with a w10 AMD pc.

Android PC Problem

So I have a Crosstopic Android and Windows 10 Problem. I installed Havoc Os 4.16 on my device and now my HP Laptop does not show the Redmi 5 Plus Phone in the device Manager, but the device is charging.
But when I go into Fastboot mode the device is showing and I can use USB-Debugging.
I tried different cables and ports.
USB Debugging and Root is Enabled.
What can I do?
Wrong ADB driver in use. Download and install the Xiaomi Redmi 5 Android USB driver.
xXx yYy said:
Wrong ADB driver in use. Download and install the Xiaomi Redmi 5 Android USB driver.
Click to expand...
Click to collapse
Thanks for the reply.
So I already did the following.
1) Downloaded the correct Driver with the inf file.
2) went to fastboot on my device and connected it to the Pc
3) Installed ADB Driver via Update Driver
What am I doing wrong? Is there maybe a exe file so I do not need to connect my phone to install the right driver?
To install ADB driver on PC it's NOT required Android device and PC are connected via USB: why should they also be connected?
xXx yYy said:
To install ADB driver on PC it's NOT required Android device and PC are connected via USB: why should they also be connected?
Click to expand...
Click to collapse
So when I connect it via Fastboot the Driver Shows up otherwise when I do not connect it I do not have a Driver to install.
I don't understand why you keep talking about FastBoot: ADB and FastBoot are two completely different drivers: ADB allows you to operate on device's Android OS, whereas FastBoot allows you to operate on device's bootloader.
BTW:
How to install ADB driver on PC in detail is described here
Download And Install Xiaomi Redmi 5 USB Driver For Windows - FlashXiaomi
In this article, We will publish links for Xiaomi Redmi 5 USB Driver to transfer files and Update your Phone to latest Android OS
flashxiaomi.com
xXx yYy said:
I don't understand why you keep talking about FastBoot: ADB and FastBoot are two completely different drivers: ADB allows you to operate on device's Android OS, whereas FastBoot allows you to operate on device's bootloader.
BTW:
How to install ADB driver on PC in detail is described here
Download And Install Xiaomi Redmi 5 USB Driver For Windows - FlashXiaomi
In this article, We will publish links for Xiaomi Redmi 5 USB Driver to transfer files and Update your Phone to latest Android OS
flashxiaomi.com
Click to expand...
Click to collapse
Exactly what I did. I tried installing the Android ADB Interface. But then see The Device cannot start Code 10.
{
"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 error code 10 is a common driver error in Windows OS. It indicates that the driver for the specific device is failing to load.
You can try to uninstall then reinstall the driver.

Categories

Resources