ADB devices can't find my phone when in fastboot - Xiaomi Redmi Note 6 Pro Questions & Answers

Hello is there any troubleshooting guide I can follow to find out why my redmi note 6 pro is not being found when I run the ADB devices command when i'm in fastboot?
It shows up fine when it's booted into the android OS.
I've enable USB debugging and authorized my PC. The device is unlocked as well.
Any help would be greatly appreciated.

recvoid said:
Hello is there any troubleshooting guide I can follow to find out why my redmi note 6 pro is not being found when I run the ADB devices command when i'm in fastboot?
It shows up fine when it's booted into the android OS.
I've enable USB debugging and authorized my PC. The device is unlocked as well.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
fastboot devices

You are the one asked in telegram too??

recvoid said:
Hello is there any troubleshooting guide I can follow to find out why my redmi note 6 pro is not being found when I run the ADB devices command when i'm in fastboot?
It shows up fine when it's booted into the android OS.
I've enable USB debugging and authorized my PC. The device is unlocked as well.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You installed the Xiaomi drivers?
Connected the phone to a USB 2.0 port on you pc? (if you don't have one, use a USB hub)

Aren't ADB and fastboot 2 different things? I only used fastboot in fastboot mode and ADB in recovery... I think your behavior is normal.

Related

[Completed] [Q] adb cant find the device after rebooting bootloader LG G4

Hello kind folk,
I've been experciening some trouble unlocking the bootloader of my LG G4 standard EU version.
I was using LG's way so i needed the Device ID. I enabled OEM unlock and usb debugging.
Downloaded adb and the drivers and everything worked fine the devices was found and i confirmed usb debugging.
When i issue 'adb reboot bootloader' the device goes into fastboot mode and doenst responds to commands from there,
it just keeps waiting for device. Also it doenst find it with 'adb devices' once in fastboot mode.
I tried finding differend methods but they all come down to this one, i have no idea what to do at this point.
Really could use some help here
Hi there,
You'd be best served asking for help from the experts who own your device here:
G4 Q&A, Help & Troubleshooting
Good luck

[Completed] Need Help Unlocking Bootloader From ADB

No bootloader interface is found !
ADB interface driver can be easily installed when "USB debugging" is enabled in phone because this way it allows Windows to detect a device with name string "ADB interface driver" and its specific vendor id along with product id. In my case, VID is VID_0bb4 and PID is PID_0004&MI_02 ( this PID is for ADB interface only). There is no problem in installation and detection of "ADB interface". adb reboot-bootloader is working from both Windows 7 64 bit command prompt and Ubuntu 15.04 terminal. Till now it is okay.
Now, this is what I am stuck at.
if anyone understood me with previous part please help me unlocking bootloader because unlocking bootloader requires switching into "fastboot" mode. With ADB command I am able to switch my phone into "fastboot" mode successfully. Now I disconnect USB cable from phone. Phone is still in "fastboot" mode ("=>> fastboot ..." written in lowest left corner on the screen). I connect USB cable again. No other new device is found this time. Fastboot commands that is detecting my phone successfully is with that adb interface port. Why is that ? At least I have learned from Internet that "bootloader interface" is required for Windows to unlock bootloader. Now after searching through many android_winusb.inf file from USB driver folder, I found out that the device id (VID) is same for both "adb interface" and "bootloader interface" BUT product id (PID) is different for both interfaces. Now it is VID_0bb4&PID_0FFF.
According to inf, Windows/Linux will only detect "bootloader interface" when the device which here in this case is a phone provides the VID_0bb4&PID_0FFF through the USB cable. The real problem here is my phone which is Micromax Bolt A065 (Kitkat 4.4.2, Kernal 3.4.67) is providing only one VID/PID in both ADB and fastboot mode and that is of "ADB Interface" only.
How can I get my phone to send that "bootloader interface" vid/pid to Windows/Linux in fastboot mode ?
Latest Android SDK is installed.
Tested with many adb/fastboot USB Drivers from Internet.
Hi,
Thank you for using XDA assist.
I suggest you ask your question here http://forum.xda-developers.com/android/help where user with the similar experience might be able to assist you well.
Good luck
Vivek_Neel said:
Hi,
Thank you for using XDA assist.
I suggest you ask your question here http://forum.xda-developers.com/android/help where user with the similar experience might be able to assist you well.
Good luck
Click to expand...
Click to collapse
Thank you for the info.

ADB for GT-I9195

Hello,
I broke my screen and I want to use the androidscreencast in order to recover some data on my Samsung GT-I9195.
I installed ADB version 1.4.2.
When I plug my phone on my computer (win7), the phone is recognized and I can browse its content.
But the command adb devices returns nothing:
"List of devices attached:
"
Edit: I first tried to recover my phone with Kies but the phone is not recognized.
Can somebody help me?
Thanks in advance.
V.
vzhache said:
Hello, I broke my screen and I want to use the androidscreencast in order to recover some data on my Samsung GT-I9195.
I installed ADB version 1.4.2.
When I plug my phone on my computer (win7), the phone is recognized and I can browse its content.
But the command adb devices returns nothing:
"List of devices attached:"
Can somebody help me?
Thanks in advance.
V.
Click to expand...
Click to collapse
Before I start suggesting soloutions/ideas was USB Debugging enabled through developer options before the screen smashed as if not there's not much you can do via ADB.
TechMinerUK said:
Before I start suggesting soloutions/ideas was USB Debugging enabled through developer options before the screen smashed as if not there's not much you can do via ADB.
Click to expand...
Click to collapse
Unfortunately, debugging mode is not activated.
Is the activation of debugging mode mandatory for connecting a mobile thanks to adb?
vzhache said:
Unfortunately, debugging mode is not activated.
Is the activation of debugging mode mandatory for connecting a mobile thanks to adb?
Click to expand...
Click to collapse
I'm afraid that debugging mode is necessary for an adb connection to the device.
TechMinerUK said:
I'm afraid that debugging mode is necessary for an adb connection to the device.
Click to expand...
Click to collapse
I may probably dream, but is there a chance to activate the debug mode with a broken screen?
vzhache said:
I may probably dream, but is there a chance to activate the debug mode with a broken screen?
Click to expand...
Click to collapse
You would need very good gueswork :crying:

mate 8 usb connection problem

Hey Guys,
I have currently the stock NXTL29C432B320 firmware on my mate 8.
I want to unlock the bootloader, but my laptop can't see my Mate 8.
I installed HiSuite & adb universal drivers, but i cant connect with HiSuit. File transfer is possible but the DC unlocker tool and every other tool cant see it.
Also tried to install the HiSuit apk manually on my phone.
Usb debugging is activated and HiSuite HDB option also.
In adb it shows unauthorized
C:\adb>adb devices
List of devices attached
DLQ0215C25012187 unauthorized
Can someone help me?
Thanks
karakatos said:
Hey Guys,
I have currently the stock NXTL29C432B320 firmware on my mate 8.
I want to unlock the bootloader, but my laptop can't see my Mate 8.
I installed HiSuite & adb universal drivers, but i cant connect with HiSuit. File transfer is possible but the DC unlocker tool and every other tool cant see it.
Also tried to install the HiSuit apk manually on my phone.
Usb debugging is activated and HiSuite HDB option also.
In adb it shows unauthorized
C:\adb>adb devices
List of devices attached
DLQ0215C25012187 unauthorized
Can someone help me?
Thanks
Click to expand...
Click to collapse
Developer mode turned on??
p51d007 said:
Developer mode turned on??
Click to expand...
Click to collapse
Yes sure.
Did you allow access on your phone when you want to connect it to the ADB console on your PC?

Oneplus 8T fastboot not recognized KB05AA

adb devices command works perfectly but when I'm in bootloader, computer does not recognize my phone. fastboot devices returns nothing. device manager show Android with a triangle under "Other Devices".
1. Tried updating the driver and manually choosing it as Android ADB Interface or Android Bootloader Interface with no luck.
2. Tried uninstalling/reinstalling the USB drivers and adb still works normal but fastboot still won't recognize my phone.
3. Tried revoking USB debugging and reallowing debug from my phone. Still same issue.
4. Tried using original Oneplus USB C-C cable, Pixel USB C-C cable, USB A-C cable, generic USB C-C cable (Oneplus was still not recognized on fastboot but Pixel was recognized so it is not the cable/PC)
4. Tried reformatting my PC. Doing a clean install on everything and still same issue.
My last resort is this thread. I would really like to unlock my Oneplus 8T bootloader and root but for some reason, fastboot does not recognize my phone. I just hooked up my Pixel phone after reformatting my PC and adb/fastboot worked normally like it should.
grimlust said:
adb devices command works perfectly but when I'm in bootloader, computer does not recognize my phone. fastboot devices returns nothing. device manager show Android with a triangle under "Other Devices".
1. Tried updating the driver and manually choosing it as Android ADB Interface or Android Bootloader Interface with no luck.
2. Tried uninstalling/reinstalling the USB drivers and adb still works normal but fastboot still won't recognize my phone.
3. Tried revoking USB debugging and reallowing debug from my phone. Still same issue.
4. Tried using original Oneplus USB C-C cable, Pixel USB C-C cable, USB A-C cable, generic USB C-C cable (Oneplus was still not recognized on fastboot but Pixel was recognized so it is not the cable/PC)
4. Tried reformatting my PC. Doing a clean install on everything and still same issue.
My last resort is this thread. I would really like to unlock my Oneplus 8T bootloader and root but for some reason, fastboot does not recognize my phone. I just hooked up my Pixel phone after reformatting my PC and adb/fastboot worked normally like it should.
Click to expand...
Click to collapse
try this https://forum.xda-developers.com/oneplus-8t/how-to/guide-fastbootd-to-recognized-computers-t4192449
---------- Post added at 01:00 PM ---------- Previous post was at 12:58 PM ----------
You can also try installing the oneplus drivers in the oneplus drive that pops up when you plug in your phone
Edit: Scratch that. I guess the 8T doesn't come with a driver partition. Try this https://oneplususbdrivers.com/oneplus-8t-usb-driver-download/
Install Universal ADB Drivers first and then boot Oneplus 8T to fastboot mode, repair oneplus device driver to "ClockworkMod Android ADB Interface" on Windows, you can use fastboot command for unlock bootloader now.
Universal ADB Drivers https://adb.clockworkmod.com/
I had the worst bloody time getting fastboot drivers installed for my 8T (KB2007, T-Mo).
I ended up having to find the device id for my device and manually patch and resign Google's USB drivers to get it working. If you can handle reading batch files and stuff, clone the repositories at https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows and https://github.com/fawazahmed0/windows-unsigned-driver-installer.
grimlust said:
adb devices command works perfectly but when I'm in bootloader, computer does not recognize my phone. fastboot devices returns nothing. device manager show Android with a triangle under "Other Devices".
1. Tried updating the driver and manually choosing it as Android ADB Interface or Android Bootloader Interface with no luck.
2. Tried uninstalling/reinstalling the USB drivers and adb still works normal but fastboot still won't recognize my phone.
3. Tried revoking USB debugging and reallowing debug from my phone. Still same issue.
4. Tried using original Oneplus USB C-C cable, Pixel USB C-C cable, USB A-C cable, generic USB C-C cable (Oneplus was still not recognized on fastboot but Pixel was recognized so it is not the cable/PC)
4. Tried reformatting my PC. Doing a clean install on everything and still same issue.
My last resort is this thread. I would really like to unlock my Oneplus 8T bootloader and root but for some reason, fastboot does not recognize my phone. I just hooked up my Pixel phone after reformatting my PC and adb/fastboot worked normally like it should.
Click to expand...
Click to collapse
Hi Grimlust i am in this exact scenario is it your device problem solved. If it has done can you walk me through the steps you went through to get that result. Please its my last chance to revive my one plus 8T
savio97 said:
Hi Grimlust i am in this exact scenario is it your device problem solved. If it has done can you walk me through the steps you went through to get that result. Please its my last chance to revive my one plus 8T
Click to expand...
Click to collapse
don't know if you still need it but today i was as desperate as you were and this helped me
How to Install Google's Android Bootloader Interface Drivers
In this comprehensive guide, we will show you how to download and install the Google's Android Bootloader Interface Drivers on your PC.
www.droidwin.com

Categories

Resources