Adb/fastboot problem with new PC - Xiaomi Poco F1 Questions & Answers

I upgraded couple of days ago to new PC - Ryzen 5 2600/rog strix b450-f gaming with clean windows 10/64 and now i have problems with adb bootloaader driver and cmd commands. Before i was on intel xeon/gigabyte motherboard socket 775 windows 7/64
I use tool all in one, install usb drivers. When phone is turn on, with usb debuging, i can enter phone storage, device manager see phone as poco,everything is ok. When i start tool all in one i can see device id,i can go into fastboot mode(phone restart and go into fastboot). When phone goes into fastboot,device manager see it as Kedacom usb device/android bootloader interface, or sometimes as android phone/android composite usb device. I have adb/fastboot files all i need on pc. When i enter some command trough cmd,for example fastboot devices,or fastboot reboot bootloader, on phone screen goes to dark and in left top corner with small font is written phone will turn off. On cmd i see afther command i set and pres enter only ??????? questionmarks. So i must again manually enter fastboot mode.
I cant get fastboot/adb to work. I try to install other adb/fastboot drivers(xiaomi and google original from tool all in one),try to connect phone cable to other usb port(2.0/3.0/3.1) at the back of pc chase,also 2.0 in front case. I try other usb cable also. Try to manually update google drivers from this forum,then i cant bcouse some ini file is missing or if i set have disc and do manualy with some other driver it cant see phone in adb-fastboot mode. I try all that fall on my mind with no luck.
At the and i goes to my friend and try to install tool all in one,install google usb drivers from that tool,install adb/fastboot files. Try to enter fastboot and do same commands as before with cmd,and everything is working fine as it was with my old pc setup. Device manager see it as Kedacom usb device/android bootloader. He also have amd cpu/chipset - but it is not ryzen with fresh w10/64
Is there any fix for my case? Does anybody have same problem?

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.

Fastboot not detecting device

For whatever reason fastboot on my PC (win10) doesn't detect my phone, adb detects it fine when it's in recovery or booted normally, I cannot send fastboot commands as it says waiting for device. I've tried a few things like the LG Mobile Driver and a universal driver but it still isn't working. Any ideas?
Just to clarify I am in Fastboot mode when trying this.
Edit: Also tried the Google USB drivers from the SDK manager, didn't make a difference
I ended up simply doing it on an Ubuntu installation. Works perfectly on there, not sure why Win10 doesn't work though.
My problem is solved.

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.

Fastboot not detected on Note 9 Pro (joyeuse)

Hi guys,
i hope anyone has a solution for me here.
So i have this weired case where the phone shows up in ADB but not in fast boot in the windows device manager when using the Recovery/Fastboot mode.
I already tested 3 different PCs and multiple cables. I as well got lucky and a friend of mine got a note 9 as well. With this the Fastboot and ADB show so it shouldn´t be a driver issue.
Can anyone help me with this problem because i would have wanted to get TWRP on this phone.
...I think it's ok when it shows up in ADB. Did you hear the windows connection sound on the PC when you plug in the device?
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
kalehrl said:
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
Click to expand...
Click to collapse
As I wrote before, I got 2x the same Phone on hand one gets recognized and all by windows and shows up with the correct device driver in fastboot. The other phone doesn't show a thing, windows isn't even recognizing that it got connected in fastboot.
Strange is that the phone that doesn't get recognized in fastboot mode does get recognized in edl and adb mode.
So in the end I am looking for an information if this could be fixed or if the main board is some kind of damaged.
opg2000 said:
...I think it's ok when it shows up in ADB. Did you hear the windows connection sound on the PC when you plug in the device?
Click to expand...
Click to collapse
No sadly not, with the second device I could hear it connect and show correctly. The problem phone shows in adb and edl but not fastboot
Knoppersd said:
As I wrote before, I got 2x the same Phone on hand one gets recognized and all by windows and shows up with the correct device driver in fastboot. The other phone doesn't show a thing, windows isn't even recognizing that it got connected in fastboot.
Strange is that the phone that doesn't get recognized in fastboot mode does get recognized in edl and adb mode.
So in the end I am looking for an information if this could be fixed or if the main board is some kind of damaged.
Click to expand...
Click to collapse
I got the same issue but by installing the above driver and changing the new type-C cable.... helped me and solved my problem......
Knoppersd said:
Hi guys,
i hope anyone has a solution for me here.
So i have this weired case where the phone shows up in ADB but not in fast boot in the windows device manager when using the Recovery/Fastboot mode.
I already tested 3 different PCs and multiple cables. I as well got lucky and a friend of mine got a note 9 as well. With this the Fastboot and ADB show so it shouldn´t be a driver issue.
Can anyone help me with this problem because i would have wanted to get TWRP on this phone.
Click to expand...
Click to collapse
have yu got the solution of this because I am also facing the same issue.
No sorry, the phone is still dead and i moved on from it.
kalehrl said:
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
Click to expand...
Click to collapse
Managed to connect my Redmi Note 9 (merlin) to Fastboot with my Windows PC and install stock ROM with MiFlash thanks to this driver.
To install the driver i did:
1. Download driver from link above (ignored Firefox's warning of potential risk).
2. Unpack the rar file.
Now we must disable Windows Driver Signature for the driver to install correctly. It will only be disabled during a single boot and the automatically revert to active and secure again after reboot.
3. Restart Windows while holding the "Shift" key through Start Menu -> Power ->Restart.
4. The blue Windows Advanced Boot menu should appear. Select: "Troubleshoot" -> "Advanced Options" -> "Startup Settings" -> "Restart"
5. Computer will restart to the Startup Settings Menu. Press number "7" key on your keyboard to select "Disable driver signature enforcement". Windows then will boot to Desktop.
6. Search and open "Device Manger" on Windows menu.
7. Under "Other devices" right click "Android" (for me it appeared with a caution sign because of the default driver error) and then "Update driver".
8. Browse my computer for Drivers -> "Let me pick from a list..." -> Select "ADB Interface" (not sure if it is important which type of device is selected) -> "Have Disk".
9. Browse the downloaded driver folder that was unpacked on step 2 and select "android_winusb.inf" (this is the Windows driver).
10. On the Windows Security prompt select "Install this driver anyway".
From here on Fastboot mode should be recognized by the PC and you can install a ROM using MiFlash or following any other guide to install via Fastboot in this forum.

Question Win11 system & RealmeGt2 fastboot mode could not find any device!

My RealmeGt2Pro can use the data cable for ADB interaction when the phone is turned on. But after entering the Fastboot mode according to the official instructions, it cannot be operated through the data cable, because the device manager of the computer does not pop up any information about this phone.My system version is RMX3300_11_C.05 & Android 13.
XDA_194 said:
My RealmeGt2Pro can use the data cable for ADB interaction when the phone is turned on. But after entering the Fastboot mode according to the official instructions, it cannot be operated through the data cable, because the device manager of the computer does not pop up any information about this phone.My system version is RMX3300_11_C.05 & Android 13.
Click to expand...
Click to collapse
The device will not be detected in fastboot mode without fastboot drivers installed
Install the proper drivers and try again
Thank you, it's not a problem with the drive. After I changed to an original cable, I can identify the device normally in Fastboot mode.
NumberOneDz said:
The device will not be detected in fastboot mode without fastboot drivers installed
Install the proper drivers and try again
Click to expand...
Click to collapse
Thank you, it's not a problem with the drive. After I changed to an original cable, I can identify the device normally in Fastboot mode.

Categories

Resources