Question Redmi 11S in in Unlock Client not detected - Redmi Note 11S 4G / POCO M4 Pro 4G (fleur)

Hello,
my Redmi 11S is in the Unlock Client not detected. But the Flash Tool find the device. That is strange for me.
But when i type fastboot devices in Fastboot the Phone is also not detected.
Can you help me?
I also treid the Xiaomi Tool V2 and the Tool detects the Phone and (USB Debugging is ok) an boots it in Fastboot and then the connection failed.
Is it a drvier problem? Where can i get the right drivers for Win 10?

The USB driver needs to support fastboot mode, try this one: https://developer.android.com/studio/run/win-usb

aricooperdavis said:
The USB driver needs to support fastboot mode, try this one: https://developer.android.com/studio/run/win-usb
Click to expand...
Click to collapse
This drivers are installed and the device is not detected.
Edit:
Drivers uninstalled and installed again and it works. Thanks.

Related

neo l_cant connect to fastboot

Hi my neo l not connecting in fastboot mode. I have updated all drivers but when i connect phone in fastboot mode a popup shows unrecognised usb device. Aldo not showing anything when i typed" fastboot devices " in cmd.
Mani-saini said:
Hi my neo l not connecting in fastboot mode. I have updated all drivers but when i connect phone in fastboot mode a popup shows unrecognised usb device. Aldo not showing anything when i typed" fastboot devices " in cmd.
Click to expand...
Click to collapse
Hello friend, try to connect to another USB port on your computer, if it does not work disconnect any USB devices you may have connected and try again, if still don't work is because drivers are not installed, try re-install them again, what windows version are you using, if it is Windows 8 there is special procedure how to install fastboot drivers,
Good luck
Yeah first make sure you see it in the Device Manager on Windows.
galarpo said:
Hello friend, try to connect to another USB port on your computer, if it does not work disconnect any USB devices you may have connected and try again, if still don't work is because drivers are not installed, try re-install them again, what windows version are you using, if it is Windows 8 there is special procedure how to install fastboot drivers,
Good luck
Click to expand...
Click to collapse
I have instaled all fastboot drivers. Also changed the cable.and in device manager it showing unknown device.
I am using windows 8 .which method for installing drivers???
how to
Mani-saini said:
I have instaled all fastboot drivers. Also changed the cable.and in device manager it showing unknown device.
I am using windows 8 .which method for installing drivers???
Click to expand...
Click to collapse
1- Hold SHIFT and restart you computer, always holding SHIFT or run this "shutdown /r /o"
2- You should be now on "Advanced Startup options", select "Troubleshoot" --->"Advanced Options"--->"Startup settings"--->"restart"
3- Next select option 7
4- plug your phone to computer in fastboot mode and install flashtool drivers, remenber to say yes on the windows appearing during installation, after everything is installed, restart your computer and problem solved.

[SOLVED] Unbrick with locked bootloader

As the title reads, I am stuck in a bootloop I guess coming from uninstalling more system apps than was probably wise.
I tried to flash via Mi Flash but I get a "can't flash a locked phone" error.
I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too).
What options do I have?
Much appreciated,
Ultimatum
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
have you tried to re-install the Driver? make sure that you only use win 64 bit for flashing, many issues occurred when you try to flash using win 32 bit
I am using Windows 10 64 bit. Moreover, I have installed ADB drivers separately (although these seem to come with the Mi Flash utility too).
I think it's intended behavior not to be able to flash via Fastboot with the bootloader locked? I was hoping to be able to restore via Mi PC Suite but it can't seem to see the phone, although the computer does and Mi Flash does too.
try using Mi PC Suite, http://en.miui.com/thread-92720-1-1.html, After Mi PC Suite is installed, make sure that your phone is in fastboot mode, connect your phone to a computer, and select the correct ROM file to flash
"I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too)."
For some reason, Mi PC Suite is not detecting the phone.
Ultimatum99 said:
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
Click to expand...
Click to collapse
Hello there,
I faced the same situation, but unfortunately in download mode, the phone is not detected in MiFlash, it detected as QHSUSB_BULK in Windows. Phone is detected while in fastboot and normal mode, but not in download mode. Do you have any idea what to do?
I expect this is a driver issue, but I can't figure out what.. I'm using Windows 64 bit, disabled driver signature enforcement, and installed all driver from MiFlash installation (there were 3 of driver notification prompt).
noersetiawan said:
Hello there,
I faced the same situation, but unfortunately in download mode, the phone is not detected in MiFlash, it detected as QHSUSB_BULK in Windows. Phone is detected while in fastboot and normal mode, but not in download mode. Do you have any idea what to do?
I expect this is a driver issue, but I can't figure out what.. I'm using Windows 64 bit, disabled driver signature enforcement, and installed all driver from MiFlash installation (there were 3 of driver notification prompt).
Click to expand...
Click to collapse
You need to update QHSUSB_BULK to the Qualcomm driver.
Device Manager > Select QHSUSB_BULK > Update Driver Software > Find manually the location of the driver, most likely: C:\Program Files (x86)\Xiaomi\MiPhone\Qualcomm\Driver
The driver should now appear as Qualcomm something, and Mi Flash should be able to see the phone.
Does this work?
Ultimatum99 said:
You need to update QHSUSB_BULK to the Qualcomm driver.
Device Manager > Select QHSUSB_BULK > Update Driver Software > Find manually the location of the driver, most likely: C:\Program Files (x86)\Xiaomi\MiPhone\Qualcomm\Driver
The driver should now appear as Qualcomm something, and Mi Flash should be able to see the phone.
Does this work?
Click to expand...
Click to collapse
Hi,
Thank you for the help. Unfortunately it doesn't work straight away, fortunately this leads me to the right direction, after I tried to point the driver to Xiaomi directory, a window dialog says the driver is 32 bit thus noninstallable for my PC, then I looked around for 64 bit driver for Qualcomm, installed it. I can finally install the driver but the phone is detected as unknown USB device, after removing it from Device Manager, restarted my PC, and tried again, it's still the same, on the third try it finally detected properly. It's working now, thank you very much.
Really weird why did MiFlash comes with noninstallable driver.
Ultimatum99 said:
As the title reads, I am stuck in a bootloop I guess coming from uninstalling more system apps than was probably wise.
I tried to flash via Mi Flash but I get a "can't flash a locked phone" error.
I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too).
What options do I have?
Much appreciated,
Ultimatum
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
Click to expand...
Click to collapse
My 3s prime is locked bootloader, developer option off, oem disable thus not able to flash as device is in bootloop.
Garu8 said:
My 3s prime is locked bootloader, developer option off, oem disable thus not able to flash as device is in bootloop.
Click to expand...
Click to collapse
you have to flash in edl mode not fastboot so google on how to take redmi 3s into edl mode then you can flash the rom in locked bootloader.in redmi 3 we use volume up and volume down and power button.press all three at the same time and it will take u to edl mode.screen becomes all black but if you plug it to ur computer and press refresh in miflash then it will show as com 10 or 20.thats for redmi 3.maybe redmi 3s has the same steps
jokerpappu said:
you have to flash in edl mode not fastboot so google on how to take redmi 3s into edl mode then you can flash the rom in locked bootloader.in redmi 3 we use volume up and volume down and power button.press all three at the same time and it will take u to edl mode.screen becomes all black but if you plug it to ur computer and press refresh in miflash then it will show as com 10 or 20.thats for redmi 3.maybe redmi 3s has the same steps
Click to expand...
Click to collapse
I have already tried to switch to edl mode using cmd with "fastboot oem edl" command but it enter bootloop. It happen because oem is locked alongwith usb debugging as I didn't unlock developer option.
Garu8 said:
I have already tried to switch to edl mode using cmd with "fastboot oem edl" command but it enter bootloop. It happen because oem is locked alongwith usb debugging as I didn't unlock developer option.
Click to expand...
Click to collapse
then you should buy a usb cable which has a button in it which forces xiaomi devices to boot into edl mode.i forgot its name but i think you can google to find it
jokerpappu said:
then you should buy a usb cable which has a button in it which forces xiaomi deveot into edl mode.i forgot its name but i think you can google to find it
Click to expand...
Click to collapse
I believe you are talking about dfc a.k.a deep flash cable. I have searched alot I couldn't find it on any e-commerce site except alibaba which doesn't ship at my place. Can yousuggest any seller or website if you ever came across selling dfc cable? Deep flash method is the only last resort for my problem other than sending phone to service centre. Could you suggest any website to make dfc cable manually?;as I have searched youtube but non of the method mentioned in it seemed liable to me.
Garu8 said:
I believe you are talking about dfc a.k.a deep flash cable. I have searched alot I couldn't find it on any e-commerce site except alibaba which doesn't ship at my place. Can yousuggest any seller or website if you ever came across selling dfc cable? Deep flash method is the only last resort for my problem other than sending phone to service centre. Could you suggest any website to make dfc cable manually?;as I have searched youtube but non of the method mentioned in it seemed liable to me.
Click to expand...
Click to collapse
i saw it on ebay also.i think that seller will ship worldwide to any country.
here is the link
http://www.ebay.com/sch/i.html?_fro...le.TRS0&_nkw=xiaomi+deep+flash+cable&_sacat=0
You don't need deep flash cable use button combo to put in edl mode. From device manager update driver for QHSUSB_BULK. \After that reboot pc with driver signature disabled, then open mi flash and phone should be recognised. Just found the thread I used to remove vendor rom.
http://en.miui.com/thread-254606-1-1.html
JUST MAKE SURE YOU DOWNLOAD THE ROM FOR YOUR DEVICE!:crying:
jazz452 said:
You don't need deep flash cable use button combo to put in edl mode. From device manager update driver for QHSUSB_BULK. \After that reboot pc with driver signature disabled, then open mi flash and phone should be recognised. Just found the thread I used to remove vendor rom.
http://en.miui.com/thread-254606-1-1.html
JUST MAKE SURE YOU DOWNLOAD THE ROM FOR YOUR DEVICE!:crying:
Click to expand...
Click to collapse
As I have already said edl mode won't work since developers option was not activated as edl requires oem activated. I had already tried all the methods.
By the way thanks to u all at xda as I have successfully flashed new rom using deep flash cable method...
Nexus 10 rooted in a bootloop
Hi folks! I'm a newbie with this stuffs so I'll do my best to explain the issue. I've recently rooted my Nexus 10 with Nexus root toolkit 2.1.9( I believe). All was fine until I turn it off and back on. Now I'm in a bootloop. I could use the Unroot+flash command but my windows 7 won't detect the device. It only detect it when my tablet is connected and turn off. In that case shows as MTP. Can anyone help me reinstalling the driver or else? Thank you
Novice12 said:
Hi folks! I'm a newbie with this stuffs so I'll do my best to explain the issue. I've recently rooted my Nexus 10 with Nexus root toolkit 2.1.9( I believe). All was fine until I turn it off and back on. Now I'm in a bootloop. I could use the Unroot+flash command but my windows 7 won't detect the device. It only detect it when my tablet is connected and turn off. In that case shows as MTP. Can anyone help me reinstalling the driver or else? Thank you
Click to expand...
Click to collapse
Hi,
This is Redmi 3 section. The correct section for your device is here. Please explain your issue there. Good luck!
Sent from my Redmi 3 using XDA Labs
Unbrick Xiaomi Redmi 3s prime with unlocked boot loader
Hi all,
I've a Xiaomi redmi 3s prime with rooted and unlocked bootloader. I tried unrooting from SuperSu and the phone is in bootloop now. I had TWRP recovery mod installed and a nandroid back up in my phone. But, I can't even enter the recovery mode now. Fast boot is working. Please help me to unbrick it without losing the data or recover the nandroid back up at least.
Thanks!!
Ultimatum99 said:
As the title reads, I am stuck in a bootloop I guess coming from uninstalling more system apps than was probably wise.
I tried to flash via Mi Flash but I get a "can't flash a locked phone" error.
I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too).
What options do I have?
Much appreciated,
Ultimatum
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
Click to expand...
Click to collapse
look
you got bootloop and its very very different from brick
update your title

Poco not being recognized in adb

poco f1 not recognised in adb windows 10
I unlocked bootloader and re did the USB debugging but the computer wont reconize poco in adb.
I've tried portable and normal and run as admin and installed the drivers but not showing.....any help appreciated
Your PC has an AMD Ryzen?? Try Intel...
ashboe said:
poco f1 not recognised in adb windows 10
I unlocked bootloader and re did the USB debugging but the computer wont reconize poco in adb.
I've tried portable and normal and run as admin and installed the drivers but not showing.....any help appreciated
Click to expand...
Click to collapse
you have to enable MTP (File Transfer) in Pop Up Screen on Phone once the phone is plugged in
ashboe said:
poco f1 not recognised in adb windows 10
I unlocked bootloader and re did the USB debugging but the computer wont reconize poco in adb.
I've tried portable and normal and run as admin and installed the drivers but not showing.....any help appreciated
Click to expand...
Click to collapse
Here's what i did, (not for poco but it worked for mido, kenzo) downloaded mi flash tool and installed the drivers from it's installed directory. And it worked.
fmcheetah said:
you have to enable MTP (File Transfer) in Pop Up Screen on Phone once the phone is plugged in
Click to expand...
Click to collapse
I'm such an idiot! That was it!
Hi guys,
Need your help.. am facing some weired issue with POCO F1 ... with adb..
1. I have enabled the debugging.
2. installed the google drivers.
3. CMD check reflects the adb device.. <some numbers>..
4 When i tried to connect the phone via usb to mi suite or hisuite... they fails to recognize the Phone..
I have intel processor ... and I am able to transfer stuffs via MTP mode.. but the software aren't recognizing.. any suggestions..
I have all this below mentioned files ..
qualcomm_driver-4.zip
TOOL_ALL_IN_ONE_2.0.1.1.zip
usb_driver_r12-windows.zip
XiaomiADBFastbootTools-Win32-master.zip
Xiaomi-UniversalAdbDriver.zip
HiSuite_8.0.1.300_OVE.exe
latest_usb_driver_windows.zip
minimal_adb_fastboot_v1.4.3_setup.exe
MiSetup2.2.0.7032_2717.exe
Does it have anything to do with USB .. is ours 3.0 ?? and 2.0 works ?? is there any setup to be done in mobile ??
Attachment shows --
1. adb with ? mark .. (disconnected device)
2. ADB composite device (now connected device with udpated google driver).
Please guide..
mini2015 said:
Hi guys,
Need your help.. am facing some weired issue with POCO F1 ... with adb..
1. I have enabled the debugging.
2. installed the google drivers.
3. CMD check reflects the adb device.. <some numbers>..
4 When i tried to connect the phone via usb to mi suite or hisuite... they fails to recognize the Phone..
I have intel processor ... and I am able to transfer stuffs via MTP mode.. but the software aren't recognizing.. any suggestions..
I have all this below mentioned files ..
qualcomm_driver-4.zip
TOOL_ALL_IN_ONE_2.0.1.1.zip
usb_driver_r12-windows.zip
XiaomiADBFastbootTools-Win32-master.zip
Xiaomi-UniversalAdbDriver.zip
HiSuite_8.0.1.300_OVE.exe
latest_usb_driver_windows.zip
minimal_adb_fastboot_v1.4.3_setup.exe
MiSetup2.2.0.7032_2717.exe
Does it have anything to do with USB .. is ours 3.0 ?? and 2.0 works ?? is there any setup to be done in mobile ??
Attachment shows --
1. adb with ? mark .. (disconnected device)
2. ADB composite device (now connected device with udpated google driver).
Please guide..
Click to expand...
Click to collapse
My Phone is clean wiped..No OS on it...how can i enable debugging?

Device in Fastboot mode not recognized at all as USB device

Hey everyone,
im trying to unlock the bootloader of my LG G5, but am unable to do so as the phone is not detected at all when in fastboot mode.
While it is recognized just fine as an adb device, after rebooting into fastboot mode via adb reboot bootloader it is not recognized as an USB Device in Windows (The device manager does not show any device with wrong drivers and does not react to replugging the device). I also tried it on a different machine with the same results.
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
I installed the necessary (I tried LG and Google) drivers and tried different USB ports (2.0 and 3.0) and cables. The phone just is not noticed as an usb device at all when in fastboot mode.
Could this be due to a broken usb port? Which seems odd because the phone is recognized when not in fastboot mode.
What else could cause this weird behaviour?
Thank You!
Just to be clear. After you booted into fastboot mode, did you try
Code:
fastboot devices
and it just showed nothing?
holgers0n said:
Hey everyone,
im trying to unlock the bootloader of my LG G5, but am unable to do so as the phone is not detected at all when in fastboot mode.
While it is recognized just fine as an adb device, after rebooting into fastboot mode via adb reboot bootloader it is not recognized as an USB Device in Windows (The device manager does not show any device with wrong drivers and does not react to replugging the device). I also tried it on a different machine with the same results.
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
I installed the necessary (I tried LG and Google) drivers and tried different USB ports (2.0 and 3.0) and cables. The phone just is not noticed as an usb device at all when in fastboot mode.
Could this be due to a broken usb port? Which seems odd because the phone is recognized when not in fastboot mode.
What else could cause this weird behaviour?
Thank You!
Click to expand...
Click to collapse
Do you have usb debugging on because some devices require it to be on in order to be able to use fastboot on the computer.
In addition to ADB and Fastboot you have to install the "Android USB Driver" that is suitable to your phone, too, to get Fastboot working.
I forgot to mention that, oem unlock and USB debugging is enabled.
I tried installing the LG and android USB driver. But there is no way I can install these drivers to my fastboot device, as it is not recognized as an USB device at all, its like I'm plugging an USB cable with nothing attached to it into the computer.
QUOTE="User699, post: 84602251, member: 11475773"]
Just to be clear. After you booted into fastboot mode, did you try
Code:
fastboot devices
and it just showed nothing?
[/QUOTE]
Fastboot devices does not show anything.
holgers0n said:
I tried installing the LG and android USB driver. But there is no way I can install these drivers to my fastboot device, as it is not recognized as an USB device at all, its like I'm plugging an USB cable with nothing attached to it into the computer.
Click to expand...
Click to collapse
The "Android USB Driver" is a Windows OS driver, hence it must get installed in Windows OS.
jwoegerbauer said:
The "Android USB Driver" is a Windows OS driver, hence it must get installed in Windows OS.
Click to expand...
Click to collapse
Yes i am aware of that. As mentioned i installed the driver, my phone is recognized as an adb device. I have seen some solutions suggesting installing the driver manually when the fastboot device is not recognized correctly but the device is not recognized at all. I also tried installing the drivers as legacy hardware (Android ADB interface, Android Bootloader Interface etc.) via device manager, which results in an error ( error code 10, device can not be started)
No more clues by me.
@holgers0n
I tried lsusb on my Xiaomi (I don't have lg) and it worked in fastboot also.
Since it doesn't show anything if you do fastboot devices, you could try to do the standard things:
1) Change usb port on your computer
2) Try another cable
3) If it's a usb type c, plug it into your smartphone, try if it works and if it doesn't, try around that cable and retry.
I am not 100 % sure but since you said
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
Click to expand...
Click to collapse
maybe you need to install non-free firmware as well.
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Narrry84 said:
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Click to expand...
Click to collapse
I'm also having the same issue with my Poco F1, it is recognized just fine as an ADB device, but not in fast boot mode. My laptop has both USB 2.0/3.1 ports hence I tried both but the result was just the same not recognised in fastboot mode
holgers0n said:
I also tried installing the drivers as legacy hardware (Android ADB interface, Android Bootloader Interface etc.) via device managerr, which results in an error ( error code 10, device can not be started)
Click to expand...
Click to collapse
yea I also manually installed USB drivers for my Poco F1 but in my case, I had no error
The same thing is happening to me on my LG g5, did you find a solution?
akashrathi7978 said:
I'm also having the same issue with my Poco F1, it is recognized just fine as an ADB device, but not in fast boot mode. My laptop has both USB 2.0/3.1 ports hence I tried both but the result was just the same not recognised in fastboot mode
yea I also manually installed USB drivers for my Poco F1 but in my case, I had no error
Click to expand...
Click to collapse
try linux, same thing has happened to me.
sanfi9 said:
The same thing is happening to me on my LG g5, did you find a solution?
Click to expand...
Click to collapse
try it on linux, install adb on linux and run "fastboot devices" I used to have the same problem.
akashrathi7978 said:
I'm also having the same issue with my Poco F1, it is recognized just fine as an ADB device, but not in fast boot mode. My laptop has both USB 2.0/3.1 ports hence I tried both but the result was just the same not recognised in fastboot mode
yea I also manually installed USB drivers for my Poco F1 but in my case, I had no error
Click to expand...
Click to collapse
Have you tried linux?
hellofriendlymanveriosns said:
Have you tried linux?
Click to expand...
Click to collapse
No, but i got it fixed with this AMD FASTBOOT FIX guide as i was using AMD Ryzen 5 5500U.
My laptop have both USB 2.0/3.1 ports hence it worked for me on USB 2.0 port (otherwise buy a USB 2.0 hub) after running that ".bat" file as "admin" it recognised my phone.
Keep in mind i uninstalled all 3rd party "adb tools" then rebooted my laptop and used Google's official Adb tool (approx 12mb) then ran "cmd" on the same path (keep the adb tool in :c drive)
akashrathi7978 said:
No, but i got it fixed with this AMD FASTBOOT FIX guide as i was using AMD Ryzen 5 5500U.
My laptop have both USB 2.0/3.1 ports hence it worked for me on USB 2.0 port (otherwise buy a USB 2.0 hub) after running that ".bat" file as "admin" it recognised my phone.
Keep in mind i uninstalled all 3rd party "adb tools" then rebooted my laptop and used Google's official Adb tool (approx 12mb) then ran "cmd" on the same path (keep the adb tool in :c drive)
Click to expand...
Click to collapse
STEPS I did to solve this issue on my Laptop with AMD CPU
🗃️POCO F1 Ultimate Collection & Guides📚
Welcome to POCO F1 Ultimate Collection! 🗃️ (beryllium) OFFICIAL STOCK MIUI ROM ©️ You can check my Guides for installation. Recovery ROM V12.0.3.0.QEJMIXM Fastboot ROM V12.0.3.0.QEJMIXM POCO F1 Global Stable ROM Library / POCO F1 MIUI...
forum.xda-developers.com
holgers0n said:
Hey everyone,
im trying to unlock the bootloader of my LG G5, but am unable to do so as the phone is not detected at all when in fastboot mode.
While it is recognized just fine as an adb device, after rebooting into fastboot mode via adb reboot bootloader it is not recognized as an USB Device in Windows (The device manager does not show any device with wrong drivers and does not react to replugging the device). I also tried it on a different machine with the same results.
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
I installed the necessary (I tried LG and Google) drivers and tried different USB ports (2.0 and 3.0) and cables. The phone just is not noticed as an usb device at all when in fastboot mode.
Could this be due to a broken usb port? Which seems odd because the phone is recognized when not in fastboot mode.
What else could cause this weird behaviour?
Thank You!
Click to expand...
Click to collapse
Hello I have exactly the same problem. I know all the right drivers are installed, because I already flashed it from CN Rom to EEA ROM a few weeks ago. Usb debugging is activated, bootloader unlocked, etc . Nothing works.
Have you resolved the problem since?
Had the same problem after running:
adb reboot bootloader
Tried to run a fastboot command e.g. `fastboot getvar unlocked`, it gave the message `< waiting for any device >`
Solution
Assuming you have the bootloader driver installed, but its not connecting.
After running " adb reboot bootloader " with the device plugged in and in the bootloader follow these steps.
Open Device Manager => Win + R => devmgmt.msc .
Find the device called Android that has a yellow warning sign on it.
{
"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"
}
Open the properties and hit update driver.
Select "Browser my computer for drivers"
Select "Let me pick from a list..."
Select "Android Device"
(If this option doesn't show up, then you don't have the drivers installed)
Select Android Bootloader Interface
(If this option doesn't show up, then you don't have the drivers installed)
Click next and the the bootloader driver should be working.
This solution does need to be repeated when ever the device goes into bootloader mode i.e. when you want to run fastboot commands.
Mmm, just stumbled here to say that I had this problem since loong ago I unlocked the bootloader of my Z2121, and didn't know why. The reason is that I was using the Minimal ADB and Fastboot tool, because after reading the threads Bootloader driver issues on Windows 10? and [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows subsequently, and of course using fawazahmed0's Latest ADB Installer, my problem was solved.
The BAT installer in the thread downloads the actual BAT installer file whose download path you can find inspecting it, and that other actual installer file for now sets the installation folder name as "platform-tools", and also adds its path into your system's user Path variable to allow running ADB and Fastboot commands from whatever folder location. For this reason you must also change the Path variable along with the folder's name if you wish to do so, or edit and modify the actual installation BAT file to change the folder name (there are a few entries).
Hope this is of help.

Mi unlock tool not detecting device

I am trying to unlock the bootloader on my poco f1. But when I boot it into fast boot and connect the phone it shows "Press any button to turn off" and the unlock tool does not detect the device either. I have enabled USB debugging and OEM unlocking on, I had successfully signed into the mi account and the unlock tool. I tried to check adb devices, it didn't show on fast boot but did show when the device was booted normally. I also tried disabling the driver enforcement on my pc. None of these worked. Can somebody please help me with this
ATS995 said:
I am trying to unlock the bootloader on my poco f1. But when I boot it into fast boot and connect the phone it shows "Press any button to turn off" and the unlock tool does not detect the device either. I have enabled USB debugging and OEM unlocking on, I had successfully signed into the mi account and the unlock tool. I tried to check adb devices, it didn't show on fast boot but did show when the device was booted normally. I also tried disabling the driver enforcement on my pc. None of these worked. Can somebody please help me with this
Click to expand...
Click to collapse
Are you using AMD Ryzen system or Intel? If you are using AMD Ryzen, check and read carefully the AMD Ryzen Fastboot Fix Guide from my POCO F1 Ultimate Collection & Guides thread.
Retrial said:
Are you using AMD Ryzen system or Intel? If you are using AMD Ryzen, check and read carefully the AMD Ryzen Fastboot Fix Guide from my POCO F1 Ultimate Collection & Guides thread.
Click to expand...
Click to collapse
No I use an Intel system
ATS995 said:
No I use an Intel system
Click to expand...
Click to collapse
Change usb port
Use USB3 fix
polve93 said:
Change usb port
Use USB3 fix
Click to expand...
Click to collapse
Tried using another USB 2.0 port . Still no detection
ATS995 said:
Tried using another USB 2.0 port . Still no detection
Click to expand...
Click to collapse
Try installing xiaomi flash tool v2 it will help to detect the device

Categories

Resources