Develop Bugs

[Unrooting] fastboot does not detect OP3, while adb does

For the past few days I've been trying to pass SafetyNet with root and after I failed, I tried to unroot my phone as passing SafetyNet is more important to me than having root. In the processing of doing so, I messed up some things on my device. I flashed all uninstalllers of SuperSU, Xposed, Magisk and other stuff I flashed through TWRP and deleted all SU files in bin and xbin. It removed root but I still wasn't able to pass safety net. I then messed up somehow and removed my TWRP and now when I try to access recovery it simply boots up my phone. I decided it would be the best to simply reset my phone using fastboot and adb (maybe even lock the bootloader again?). Fastboot however, cannot detect my device while abd can (not in the bootloader menu though). I have searched arround on the internet, have installed tons of drivers, reinstalled the SDK + Android Studio,... but I can't seem to get it work. When my device is booted up, it shows in Device Manager as "ONEPLUS A3003" and when in fastboot mode, it shows as "Android Bootloader Interface". Updating the drivers doesn't help. Would love if someone was able to help me out here!

The problem is the last update windows 10. You need to connect your phone in fastboot mode to your PC. Then go to the Device Manager, find there KEDACOM USB Device, clicked and appears in the ANDROID BOOTLOADER INTERFACE. Click on it right mouse button, put the Update Driver Software, then search for drivers on the computer, then select DRIVERS FROM THE LIST and select FASTBOOT INTERFACE (USB GOOGLE ID).

lubinek79 said:
You need to connect your phone in fastboot mode to your PC. Then go to the Device Manager, find there KEDACOM USB Device, clicked and appears in the ANDROID BOOTLOADER INTERFACE. Click on it right mouse button, put the Update Driver Software, then search for drivers on the computer, then select drivers from the list and select FASTBOOT INTERFACE (USB GOOGLE ID).
Click to expand...
Click to collapse
I'll try that out tomorrow, thanks for your reply!

lubinek79 said:
The problem is the last update windows 10. You need to connect your phone in fastboot mode to your PC. Then go to the Device Manager, find there KEDACOM USB Device, clicked and appears in the ANDROID BOOTLOADER INTERFACE. Click on it right mouse button, put the Update Driver Software, then search for drivers on the computer, then select DRIVERS FROM THE LIST and select FASTBOOT INTERFACE (USB GOOGLE ID).
Click to expand...
Click to collapse
Thanks for help, Worked for me

lubinek79 said:
The problem is the last update windows 10. You need to connect your phone in fastboot mode to your PC. Then go to the Device Manager, find there KEDACOM USB Device, clicked and appears in the ANDROID BOOTLOADER INTERFACE. Click on it right mouse button, put the Update Driver Software, then search for drivers on the computer, then select DRIVERS FROM THE LIST and select FASTBOOT INTERFACE (USB GOOGLE ID).
Click to expand...
Click to collapse
Got it working with your help! Had to completely remove the drivers first and than put my PC into flight mode though, because Windows 10 would keep reinstalling the drivers. Thanks for your help!

Not able to detect phone in fastboot

Tried on windows 10 and 7:
Phone is detected by ADB and commands work no problem. Boot in to fastboot (download mode) and the device isn't found when using "fastboot devices". The phone appeared in device manager with the yellow triangle but I manually updated the driver to "Android Bootloader Interface" however, I still get nothing. Am I missing something?
Thank you.

Mine never has shown in fastboot, if it shows up in device manager it should work fine. To test just try fastboot reboot.

If you corrected the issue with the driver,the problem may be with the versions of Fastboot you are using. You can download the latest Fastboot and ADB files from Google directly if you search for them it should be the first or second link.

You need google usb drivers

I have the latest google usb and platform tools on a windows 7 &10 systems using different usb ports along with multiple cables and I can not detect the phone, but I can flash.

Unable to get xA2 in fastboot mode

Hi there,
strugggling to get the xa2 into fastboot mode so I can flash a new boot.img and root. I've enabled OEM unlocking and installed the USB drivers. the command 'adb reboot fastboot' doesn't work, just reboots the phone. adb over usb works fine. The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED. I use 'fastboot devices' to see it if it connected. I've tried this on 2 PCs now to no avail
I'm thinking maybe the fastboot drivers are wrong?
Does anyone have any other suggestions or help?
Thanks

jaw2floor said:
Hi there,
strugggling to get the xa2 into fastboot mode so I can flash a new boot.img and root. I've enabled OEM unlocking and installed the USB drivers. the command 'adb reboot fastboot' doesn't work, just reboots the phone. adb over usb works fine. The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED. I use 'fastboot devices' to see it if it connected. I've tried this on 2 PCs now to no avail
I'm thinking maybe the fastboot drivers are wrong?
Does anyone have any other suggestions or help?
Thanks
Click to expand...
Click to collapse
Hi
Install "5 seconds adb drivers"
Connect the turned off phone to PC via USB just pressing volume down button (no power) and keep pressing it until you see the LED turning green or blue.
Here u have! :highfive:

faby GT said:
Hi
Install "5 seconds adb drivers"
Connect the turned off phone to PC via USB just pressing volume down button (no power) and keep pressing it until you see the LED turning green or blue.
Here u have! :highfive:
Click to expand...
Click to collapse
Hi thanks for getting back to me,
I assume you meant the '15 second installer', which I just did just install successfully. I am still unable to see the device with 'fastboot devices' command.
Other info: I have factory reset the phone, made sure oem unlock is checked, tried the same process on another computer. I can get adb mode to work fine, but the command 'adb reboot fastboot' just reboots the phone as usual

jaw2floor said:
The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED.
Click to expand...
Click to collapse
That is the correct behaviour.
Blue LED = Fastboot mode
Green LED = Flash mode (for reflashing stock firmware with XperiFirm in case EVERYTHING is broken)
Install these drivers:
https://adb.clockworkmod.com/
When in Fastboot mode, go to device manager, there is an Android device in there (may also be called MTP device).
In the device manager, install a new driver for that and use the ADB driver from C:\Program Files (x86)\ClockworkMod\Universal ADB Driver
Windows will tell you that it's the wrong driver. Install it anyway and Fastboot will recognize your XA2 now.

schmatzler said:
That is the correct behaviour.
Blue LED = Fastboot mode
Green LED = Flash mode (for reflashing stock firmware with XperiFirm in case EVERYTHING is broken)
Install these drivers:
https://adb.clockworkmod.com/
When in Fastboot mode, go to device manager, there is an Android device in there (may also be called MTP device).
In the device manager, install a new driver for that and use the ADB driver from C:\Program Files (x86)\ClockworkMod\Universal ADB Driver
Windows will tell you that it's the wrong driver. Install it anyway and Fastboot will recognize your XA2 now.
Click to expand...
Click to collapse
If it won't work, after that just go to devices and printers and delete Xperia XA2. It will work.
Else, after installing 15 seconds, inside device manager, update the driver of your phone (or mtp device), select local, then Android device, then fastboot. Disconnect the phone and reconnect as before (volume down)

Fastboot is VOL. UP (on this device)! (Not vol. down)
So basically turn off the device, hold Vol. UP and simply connect to USB, hold Vol. UP until LED is steady blue and you are set.
Note: VOLUME UP activates fastboot and VOLUME DOWN enables flashmode and/or recovery mode

Similar trouble here.
1. VOL UP + plug in USB: Blue led blinks once, then phone shows it's charging (turned off)
2. adb reboot bootloader: Phone just turns off

Corias said:
Similar trouble here.
1. VOL UP + plug in USB: Blue led blinks once, then phone shows it's charging (turned off)
2. adb reboot bootloader: Phone just turns off
Click to expand...
Click to collapse
I had the same issue with my XA2.
The solution (at least for me) was: different USB cable and different USB-port. As it turns out, my cable was somehow worn out (though data transfer and charging was working quite well). Going into fastboot, the blue led lit very short time and then the phone restarted. Furthermore on my PC it somehow only worked on the one USB port and not the other (both USB 3.0).
--> Maybe trying the most obvious might help also some of you

BoernMe said:
I had the same issue with my XA2.
The solution (at least for me) was: different USB cable and different USB-port. As it turns out, my cable was somehow worn out (though data transfer and charging was working quite well). Going into fastboot, the blue led lit very short time and then the phone restarted. Furthermore on my PC it somehow only worked on the one USB port and not the other (both USB 3.0).
--> Maybe trying the most obvious might help also some of you
Click to expand...
Click to collapse
Did solve this by connecting to different PC. No cable/port/hub change did help. Looks like there was some trouble with drivers (though the same PC fastboots Z3 Tablet Compact perfectly).

Same
I'm also having the same issue with my Xperia XA2 Ultra. (boy that's a mouthful)
Phone model is H3223.
Host OS is Windows 10 Pro v. 2004.
Using latest Android SDK tools (i.e. ADB and Fastboot platform tools): platform-tools_r30.0.5-windows. Got it directly from Android site.
I think I had a previous driver for Android already installed or somehow Windows got it. ADB worked, Fastboot didn't. Read online about someone on this forum getting it to work by using XZ2 driver from Sony as they evidently don't have a published driver for this device. The person who posted this solution had reported problems with this driver recently. I tried it anyway.... ADB commands work and my phone shows up when listing devices. Reboot into fastboot mode and the only thing my phone does is show a blue light indicator... no splash screen or logo. To me this means it's starting fastboot but my driver isn't working with it to recognize it as any commands for fastboot return nothing or fail. It doesn't show up under fastboot devices command.
Does anyone have a clue as to what to do?

that_random_guy said:
Same
I'm also having the same issue with my Xperia XA2 Ultra. (boy that's a mouthful)
Phone model is H3223.
Host OS is Windows 10 Pro v. 2004.
Using latest Android SDK tools (i.e. ADB and Fastboot platform tools): platform-tools_r30.0.5-windows. Got it directly from Android site.
I think I had a previous driver for Android already installed or somehow Windows got it. ADB worked, Fastboot didn't. Read online about someone on this forum getting it to work by using XZ2 driver from Sony as they evidently don't have a published driver for this device. The person who posted this solution had reported problems with this driver recently. I tried it anyway.... ADB commands work and my phone shows up when listing devices. Reboot into fastboot mode and the only thing my phone does is show a blue light indicator... no splash screen or logo. To me this means it's starting fastboot but my driver isn't working with it to recognize it as any commands for fastboot return nothing or fail. It doesn't show up under fastboot devices command.
Does anyone have a clue as to what to do?
Click to expand...
Click to collapse
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.

I had the same problems with my device XA2 H3113 and Win10.
My solution: Try it with Ubuntu. Just grab an 8GB usbstick, install Ubuntu via usb-installer, boot ubuntu and open a terminal
sudo apt update
sudo apt install adb fastboot

LolRoll said:
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.
Click to expand...
Click to collapse
Hey can you please provide me a link to the drivers? as I've been trying so many drivers and they don't work.

LolRoll said:
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.
Click to expand...
Click to collapse
works for me

[HELP] MI a2 lite Fastboot Exits aAutomatically

I have a mi a2 lite and i want to unlock its bootloader, i have alrready enabled oem unlocking on developer options, when i boot my device in fastboot and connect to computer, command window says waiting for device and after 15-20 seconds of connecting my device to my pc, fastboot mode automatically exits and shows charging animation. Please anyone can help?
My device is in andoid pie (stable).

Check if you have installed drivers and run "fastboot devices" to see if device is recognised.

Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.

hossman said:
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
Click to expand...
Click to collapse
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.

I've tried restarting my pc as well as my phone and after 5-6 attempts it is now unlocked.
Thanks guys for supporting and giving response to my post
Love ya'll

CherryFarmer8 said:
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
Click to expand...
Click to collapse
same problem boss, did you already solved this? please help me out

Andrew.kathy said:
same problem boss, did you already solved this? please help me out
Click to expand...
Click to collapse
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA

capajga said:
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
Click to expand...
Click to collapse
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate

CherryFarmer8 said:
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
Click to expand...
Click to collapse
I also have this problem drivers are installed and fine but when I go to fastboot within like 15 sec it automatically turns off.

I fixed it with this https://forum.xda-developers.com/attachments/howto_driver-zip.2480396/

ADB don't work in Fastboot mode.

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