ADB don't work in Fastboot mode. - Redmi Note 8 Questions & Answers

I am trying to root my Redmi Note 8. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letting me to post images
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.

Replace adb by fastboot in fastboot mode
ex instead of
adb reboot
type
fastboot reboot

You've to use the fastboot command instead of adb. Please note that fastboot doesn't have all adb features, e.g. install, shell, etc

[email protected] said:
I am trying to root my Redmi Note 8. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letting me to post images
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.
Click to expand...
Click to collapse
adb commands only work when phone is turned on and connected to pc using ADB.. it wont work n fastboot mode. In fastboot mode the command is fastboot.
example:
in adb-> adb devices
in fastboot-> fastboot devices

Related

[Q] Help with ADB....Question

I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....
I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....
adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.

[Q] ADB not working, Fastboot does.

I also cannot get into ADB. I type adb devices and it doesn't list my device. fastboot devices does list it.
No matter if my phone is in "Fastboot" or "HBOOT" its the same outcome.
In addition, USB debugigng and ADB network is enabled.
I have even reinstalled the HTC drivers and rebooted the phone several times and such.
I maybe wrong, adb will not work in fastboot or hboot mode. It works when you are in recovery or when you are at desktop.

device not found

adb devices returns no listed devices,
One_X_All-In-One_Kit says device not found.
Tested with different drivers (HTC drivers from One_X_All-In-One_Kit,and Universal_Naked_Driver_0.72), phone is detected by Windows, in bootloader it says fastboot usb, but I can't do sh*t And it used to work just fine a month ago.
Tested on 2 different computers with different USB cables... (Win 7 and 8 run as admin).
One strange thing is that I remember updating TWRP to 2.6.0.0 and now it's 2.4.something. What happened, what can I do?
Just want to update boot.img so I can install CM10.2, currently on CM10.1.
No ideas?
I can connect adb over WiFi, but ofcourse it says offline.
USB debugging ticked?
A
Adb doesn't work in the bootloader. Only fastboot commands
Iceax123 said:
USB debugging ticked?
A
Click to expand...
Click to collapse
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
kbal said:
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
Click to expand...
Click to collapse
adb does not work in bootloader...
of that doesnt help, try another USB port... I know this sounds ridiculous but trust me, it helped me once before.
Well, i managed to get my phone be detected in adb and fastboot, by manually installing Nexus adb drivers (have a disk option).
Drivers that used to work- HTC drivers, won't do anymore. Don't know why.

Going mad just can't get fastboot to work?

I have tried windows and editing the inf file for it to recognise the Swift but adb works but fastboot doesn't. That is after toggling USB debug several times to get the authorization prompt to appear. I have tried Ubuntu 15.10 live CD, updated udev rules but adb/fastboot does not detect any device.
Is anyone able to help? I am at a complete loss of what I am doing wrong?
I just want to unlock and flash twrp 3 recovery.
Thanks
xda163fm said:
I have tried windows and editing the inf file for it to recognise the Swift but adb works but fastboot doesn't. That is after toggling USB debug several times to get the authorization prompt to appear. I have tried Ubuntu 15.10 live CD, updated udev rules but adb/fastboot does not detect any device.
Is anyone able to help? I am at a complete loss of what I am doing wrong?
I just want to unlock and flash twrp 3 recovery.
Thanks
Click to expand...
Click to collapse
Think fast boot only works in bootloader mode see here for unlock instructions
http://https://wiki.cyanogenmod.org/w/Install_CM_for_crackling
If I am using windows what drivers should I install? Adb works but does fastboot need drivers also? I have tried fastboot both with phone in and out of the fastboot screen - I have to pull battery to get out of fastboot mode! Thanks
Quite close to begging here never had problems like this with previous phones. Adb works (it reboots into fastboot) but fastboot doesnt it just says waiting for devices.
Any pointers appreciated - thinking it is driver related whatever I choose it seems to say compatible driver not found.
Any pointer to drivers that should work would be great?
Have tried again in Ubuntu (not got adb or fastboot working Ubuntu 15.10 live cd) and in Windows (adb working but fastboot now).
Help!
xda163fm said:
Quite close to begging here never had problems like this with previous phones. Adb works (it reboots into fastboot) but fastboot doesnt it just says waiting for devices.
Any pointers appreciated - thinking it is driver related whatever I choose it seems to say compatible driver not found.
Any pointer to drivers that should work would be great?
Have tried again in Ubuntu (not got adb or fastboot working Ubuntu 15.10 live cd) and in Windows (adb working but fastboot now).
Help!
Click to expand...
Click to collapse
I can't get fastboot working either. Really annoying me.
I have got this sorted. I will post details in the morning. I used a live USB of Ubuntu 15.10.

Can't unlock bootloader - fastboot issue

Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
TheeWolf said:
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
Did you already disable driver signing? Pretty sure you have to do that with Win 10. I would disable driver signing, and then use " 15 second adb installer" from XDA. Always has worked for me...

Categories

Resources