March 22 2019 - I solved my issue
I don't know what is it with Xiaomi, but I was in the market for a decent budget phone, and a decent budget Tablet. By coincidence I settled on Xiaomi Pocophone F1 and Xiaomi Mi Pad, and when it comes to getting Adb to recognize my devices, both are having the same problem.
To answer first :
Yes both devices had their Xiaomi Adb drivers installed
Yes both devices have USB Debugging enabled
Yes both devices were detected in Fastboot mode by the Mi unlocking tool
Yes both devices were unlocked
Yes both devices are detected in Recovery Sideload mode by Adb
Yes both devices are detected in Miui by Adb
And yes, both devices are not being detected in Fastboot mode by Adb, and that's where I'm having trouble
Yes tried all USB 2.0 and 3.0 ports front and back.
Yes using both Power shell & cmd-here abd packages with command "adb devices" working as expected in all boot modes except fastboot.
PC: Fairly old AMD 64 bit dual core with Windows 10 64 bit
Xiaomi Mi Pad 4 Miui Android 8.1
Xiaomi Poco F1 Miui Android 9.0
And if it means anything, this is the same PC I've used to flash recoveries via Adb for LG & OnePlus devices.
Pls give me any software suggestions, tips, tricks, or links to similar threads with the same issue.
Related
Hello everyone, I'm using Redmi Note 3 and I have tried rooting it several times.
I have unlocked the bootloader. I have also installed the adb drivers.
When I connect phone in fastboot mode and write 'fastboot devices' in cmd it doesn't return anything. But when I connect when its on, adb devices returns the device code.
Please help.
Same, happens to mine too. Used to work with a previous install of windows, but now, nope.
Had this issue too.
Try going to Device Manager and check to see if Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Install minimalist ADB and fastboot and right click Android Bootloader Interface. Click Update Driver Software, browse computer, and then click the option to list driver files already present on your drive. It should pull up a fastboot driver that's an older version than the one you currently have. Install that and fastboot will work again.
Doesn't work
Can you please link the files for download when we're updating the driver software.
Hi guys,
Urgent help needed.
I got fedup from last 4 days trying to Unlock bootloader of my Redmi Note 3 Snapdragon (Kenzo). While unlocking bootloader getting error at 50% "Couldn't verify device (Not connected to Mi Phone)". Earlier I never faced this issue as Not connected to Mi Phone.
In August 2016, 1st time I unlocked bootloader officially. And after that more than 10 times I unlocked bootloader of my RN3.
From last 15 days I was using CM13.0, But 4 days ago I flashed Miui 8.0.1.0 via Edl method (Flash all selected), then tried to Unlock bootloader. Got the error "Couldn't verify device (Not connected to Mi Phone)"
Then flashed Miui 8.0.5.0 via Edl method (because unable to unlock bootloader). While unlocking bootloader, got the same error "Couldn't verify device (Not connected to Mi Phone)"
Tools / drivers installed on my Pc:
Mi flash 01.04.2016(64bit)
MiSetup3.2.1.3111_2717 (Mi PC Suite)
Adb driver adb-setup-1.4.3
& Already reinstalled the Adb driver adb-setup-1.4.3
Already searched on MI forum, couln't find any proper answer.
When I ran the same fastboot command (fastboot devices) on Zenfone 5 connected to Pc, it immediately shows Listed device.
But In fastboot mode, when I ran the command "fastboot devices" it shows nothing. [on my Redmi Note 3]
When I ran command "fastboot oem device-info" to check bootloader status, it shows Waiting for device.
Tried every possible way I know, but no success.
Kindly help me in this regard.
Thanks in advance.
Faruque007 said:
Hi guys,
Urgent help needed.
I got fedup from last 4 days trying to Unlock bootloader of my Redmi Note 3 Snapdragon (Kenzo). While unlocking bootloader getting error at 50% "Couldn't verify device (Not connected to Mi Phone)". Earlier I never faced this issue as Not connected to Mi Phone.
In August 2016, 1st time I unlocked bootloader officially. And after that more than 10 times I unlocked bootloader of my RN3.
From last 15 days I was using CM13.0, But 4 days ago I flashed Miui 8.0.1.0 via Edl method (Flash all selected), then tried to Unlock bootloader. Got the error "Couldn't verify device (Not connected to Mi Phone)"
Then flashed Miui 8.0.5.0 via Edl method (because unable to unlock bootloader). While unlocking bootloader, got the same error "Couldn't verify device (Not connected to Mi Phone)"
Tools / drivers installed on my Pc:
Mi flash 01.04.2016(64bit)
MiSetup3.2.1.3111_2717 (Mi PC Suite)
Adb driver adb-setup-1.4.3
& Already reinstalled the Adb driver adb-setup-1.4.3
Already searched on MI forum, couln't find any proper answer.
When I ran the same fastboot command (fastboot devices) on Zenfone 5 connected to Pc, it immediately shows Listed device.
But In fastboot mode, when I ran the command "fastboot devices" it shows nothing. [on my Redmi Note 3]
When I ran command "fastboot oem device-info" to check bootloader status, it shows Waiting for device.
Tried every possible way I know, but no success.
Kindly help me in this regard.
Thanks in advance.
Click to expand...
Click to collapse
Most probably your device is not recognized as a fastboot device.... please ensure that fastboot drivers for your kenzo are installed and not corrupted and if it does not help try on some other PC and don't forget to disable drive signature enforcement
Sent from my Redmi Note 3 using Tapatalk
Resolved
Torshak.mozyora said:
Most probably your device is not recognized as a fastboot device.... please ensure that fastboot drivers for your kenzo are installed and not corrupted and if it does not help try on some other PC and don't forget to disable drive signature enforcement
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Faruque007 said:
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU
Thank you a million times, you allowed me to finally unlock my bootloader. I love you, and I hope you and your children live long and fulfilling lives.
Faruque007 said:
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Click to expand...
Click to collapse
Dude you are my hero, Thank you soo much...
privateriem said:
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU
Thank you a million times, you allowed me to finally unlock my bootloader. I love you, and I hope you and your children live long and fulfilling lives.
Click to expand...
Click to collapse
Welcome bro
I'm glad and super happy, my method helped you. Enjoy.
Faruque007 said:
Hi,
Thanks for your helpful reply
Finally unlocked bootloader succesfully. The problem is with adb drivers on my Windows 10 64bit Pc. Earlier I had done with unlocking several times, never faced driver issue on fastboot mode. But from last 4-5 days suddenly my RN3 was not responding to any fastboot commands.
Followed this:
In Device Manager under Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Installed minimalist ADB and fastboot (minimal_adb_fastboot_v1.3.1_setup) and right clicked Android Bootloader Interface. Clicked Update Driver Software, browsed computer, and then clicked the option to list driver files already present on my drive. It pulled up a fastboot driver that's an older version than the one I currently have. Installed that and fastboot commands started working again.
Hope this help other users also, who are facing (Not connected to Mi Phone) or Waiting for device when initiate fastboot command like "fastboot oem device-info".
Please close this thread.
Thanks
Click to expand...
Click to collapse
Thanks for your help dude finally unlocked and rooted my device
tried all methods but this unlock button remains inactive. please help
I'm trying to root a pixel (sailfish). I'm able to find the device in adb, but when I go into bootloader, the device isn't there. I'm mostly trying things on my Mac, which I used to successfully root a Nexus 7, but I also had the same issue on a Raspberry Pi. What's more is that I have a Verizon Pixel, which is detected in bootloader (but I can't root it since it's Verizon), and the problematic Pixel in bootloader isn't even registering as a connected USB device when I use the command, "system_profiler SPUSBDataType". Anyone have any advice?
@macduffk
Try
Code:
adb reboot bootloader
fastboot devices
jwoegerbauer said:
@macduffk
Try
Code:
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
I’ve tried that. It doesn’t show anything.
I have spent months trying to figure out how to get TWRP flashed on my Pixel Phones (I have 2 of them). I have searched & read many links on this forum and can't find any firm details/directions on how to get TWRP on a pixel. From https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/ it appears I should of installed TWRP on the factory image first, but I went to Lineage a couple years ago on Android 9 & this was not an option back then.
Both phones have the two latest version of Lineage OS, Both Devices are UNLOCKED, Both have Developer Options Enabled, and on my Windows PC I have the latest version of SDK tools & drivers installed.
Plugging into the PC is done with a a tested/good USB cable plugged into a USB 2 Port. Here is what I am seeing with LinageOS running:
adb devices shows List of Devices Attached
FA77LO302202 device
After executing - adb reboot bootloader
adb devices -> shows an empty list, hence doing a -> fastboot devices shows no devices.
Going to Recovery Mode in Bootloader list of devices shows:
FA76F0303478 unauthorized
In Recovery Mode -> Advanced -> Enable ADB list of devices shows:
FA76F0303478 recovery
I can Apply Update in Recovery Mode via Sideload, but that does not help me get TWRP flashed.
With no devices showing in the main bootloader via adb I can't get the phone into autoboot mode. Per the link at android.gadgethacks.com in order to put the Factory Image back on the phone, https://developers.google.com/android/images, I need to get the phone into autoboot mode.
Anyone have any ideas????
Come-on guys & gals. I'm sure someone can help me at XDA get my devices to fastboot.
Hey guys n girls,
I just got my Oneplus 9 Pro. So I thought I can root my old Oneplus Nord 2 5G (yes the new one).
I cant find any fastboot drivers for the Oneplus Nord 2 5G. Are they still in development? I find a lot of root tutorials and unlocking bootloader tutorials but how can they work if there's no fastboot driver?
I booted into fastboot from adb and in device manager 1 device is showing up called "Android" with a warning sign. Also it connects and disconnects in an interval of like 5 seconds. I tried to find a driver from windows update but No. I tried to install the driver manually by selecting "Android" and then "Android bootloader". This installed a driver but "fastboot devices" gives me nothing. I have the lastest minimal adb and fastboot version. Someone help me please? I need the correct fastboot drivers for the Nord 2 5G
SOLVED! the user "Eastw1ng" helped me out! Check his thread for "unlocking bootloader on Nord 2" AMAZING!!!
I've been trying to unlock the bootloader in my phone (OnePlus7T Pro).
I can't see my phone when booted into fasboot mode or recovery mode (I can see the phone while normally working).
The command: fastboot devices shows no device. The same with adb devices command.
I think I need a proper driver for the device. I've already tried UniversalAdbDriverSetup.msi, but with no success.
I use PC with Ryzen processor and Win10.
Could you suggest a solution, please?
The UniversalAdbDriverSetup you referred to is not of any use. You instead have to install the Android USB Driver suitable to your phone:
Download OnePlus USB Driver for Windows (Latest Driver)
Download the latest and original OnePlus USB Driver to connect your OnePlus Smartphone to the Windows Computer quickly and easily.
androidmtk.com
kamien8 said:
I use PC with Ryzen processor and Win10.
Could you suggest a solution, please?
Click to expand...
Click to collapse
This might help...
[FIX] Fastboot issues on Ryzen based PCs
AMD has been known for it's notorious fastboot issues in the custom ROM community, especially with Xiaomi devices. I was trying to unlock the bootloader of my Redmi Note 5 Pro the other day and I encountered with an issue where Mi Unlock Tool...
forum.xda-developers.com
Thanks for information.
I can see the device when it is up and running. Still nothing when it is in FB mode, however I can see the Widnows sound of a connected device.
jwoegerbauer said:
The UniversalAdbDriverSetup you referred to is not of any use. You instead have to install the Android USB Driver suitable to your phone:
Download OnePlus USB Driver for Windows (Latest Driver)
Download the latest and original OnePlus USB Driver to connect your OnePlus Smartphone to the Windows Computer quickly and easily.
androidmtk.com
Click to expand...
Click to collapse
I uninstalled the previous drivers and installed the right one from the link. I also have used your version of adb and fastboot.
CXZa said:
This might help...
[FIX] Fastboot issues on Ryzen based PCs
AMD has been known for it's notorious fastboot issues in the custom ROM community, especially with Xiaomi devices. I was trying to unlock the bootloader of my Redmi Note 5 Pro the other day and I encountered with an issue where Mi Unlock Tool...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, I've heard about the fix. Run it, but still nothing happened.
Maybe I have to find somebody with Intel processor.
Because your phone's Android is version 10 try this
Code:
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
....
jwoegerbauer said:
Because your phone's Android is version 10 try this
Code:
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
....
Click to expand...
Click to collapse
Hi, I'm half way.
I checked on Intel proc, and I can see bootloaded phone in fastboot. ADB still can't see the device.
I was trying to re-install drivers, but no changes.
Unfortunately I need working ADB as I have to sideload an image.
I've since years a laptop powered by AMD Ryzen 5 in use: Fastboot always works like a hell. Hence I'm pretty sure that it doesn't matter whether Fastboot is run on an Intel or AMD powered computer.
If ADB isn't working as expected my guess is that "USB debugging" didn't get enabled on phone and phone didn't get re-booted afterwards.
USB debugging is enabled. When the phone is started normally, ADB works fine (for example I can use adb reboot bootloader command)
I thought, maybe there is a mess with the drivers in the device. Can it cause the issue?
So to confirm, this is the only one drivers package I need to run OnePlus (7T Pro) in bootloader and use fastboot and adb commands?
OnePlus 7T Pro USB Driver for Windows
Download the latest OnePlus 7T Pro Driver for Windows Computer. You can use the latest OnePlus Driver to connect OnePlus Device to the Computer.
oneplusdriver.com
Command
Code:
adb reboot bootloader
since Android 10 is incorrect: I've already told you this in a previous post.
jwoegerbauer said:
Command
Code:
adb reboot bootloader
since Android 10 is incorrect: I've already told you this in a previous post.
Click to expand...
Click to collapse
Yes, you're right.
adb reboot bootloader command works. Once I am in bootloader I still can connect phone via adb but fastboot doesn't work. That was my question, if the highlightet drivers are the only one I need.
Is it possible, that there is something wrong with the phone?
If ADB successfully connects to phone then your phone isn't booted into its bootloader, but into Android OS.