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.
Related
So I've been trying to root/unlock my CDMA nexus and I'm having a very frustrating problem that's preventing me from doing it with any of the toolkits available OR the manual method. I have the android SDK installed, samsung's USB drivers, and everything else I've been told to get. I can detect my phone when it's connected (and USB debugging is on) using adb commands but ONLY when the phone is booted as normal. If I reboot into the bootloader, my computer no longer detects it, and I can no longer act upon it via adb. This, of course, is preventing me from getting anywhere on the unlocking/root front. Anyone have any ideas? I'm fresh out.
ADB doesn't work in boot loader/fastboot. Adb only works in recovery or when Android is fully running.
You need to use fastboot commands in bootloader/fastboot.
"Fastboot devices" to see if it's detected.
Sent from my Galaxy Nexus
have you installed the hboot drivers?
As above, you have to use fastboot commands when the phone is in bootloader. Try "Fastboot devices" to see if your computer sees the phone.
Fastboot commands don't detect the phone either. Fastboot is installed, as I can get it via command prompt to show available commands and whatnot, it just does not detect a device to work on.
I am also having this exact problem when i try to install the new touch cwm beta that was just released. Its not detecting the device while in the bootloader, and when i try to fastboot flash recovery it just says <waiting for device> and does nothing.
I know this is a little late, but I figured I’d post here to help anyone else out that is having this problem. I was trying to update my Galaxy Nexus from 4.0.2 to 4.0.4 using fastboot when I ran into the problem you’re having. I did this from a Windows 7 machine, and the fix for me was as follows:
1. After booting into the bootloader and having your phone plugged into your computer, open Computer Management.
2. Under Device Manager, in Computer Management, you should see a listing for a device called “Android 1.0” and it’ll have the little yellow triangle with the exclamation point on it.
3. Right click on the Android 1.0 device and select “Update Driver Software…”
4. Click “Browse my computer for driver software”
5. Click “Let me pick from a list of device drivers on my computer”
6. If you installed the Samsung drivers for the phone, scroll down until you see a device listed as “SAMSUNG Android Phone”
7. Select it and click next
8. It should auto populate the driver information. Click next and it will install the device
9. Go back to your CMD prompt and fastboot devices should now list the phone.
Hope this helps!
Quicks man your the best!
...or use Linux #trolling
Sent from my Galaxy Nexus using xda app-developers app
I've been trying to access my GNex in fastboot mode, but my computer doesn't recognize it when it is in fastboot. I have tried to install the samsung adb drivers, but not matter what I try, I cannot get my computer to connect using the adb when the device is in fastboot. Any help would be appreciated.
I am running window 7 x64 btw.
EDIT: When my device is connected and I am not in fastboot mode, i am getting the "SAMSUNG Android ADB Interface" listed in device manager. So I am assuming I have the driver installed correctly.
EDIT 2: When I use
Code:
adb reboot bootloader
the device goes from recognized to Android 1.0, and if I try to
Code:
fastboot oem unlock
I get
Code:
<waiting for device>
rbmako69 said:
I've been trying to access my GNex in fastboot mode, but my computer doesn't recognize it when it is in fastboot. I have tried to install the samsung adb drivers, but not matter what I try, I cannot get my computer to connect using the adb when the device is in fastboot. Any help would be appreciated.
I am running window 7 x64 btw.
EDIT: When my device is connected and I am not in fastboot mode, i am getting the "SAMSUNG Android ADB Interface" listed in device manager. So I am assuming I have the driver installed correctly.
EDIT 2: When I use
Code:
adb reboot bootloader
the device goes from recognized to Android 1.0, and if I try to
Code:
fastboot oem unlock
I get
Code:
<waiting for device>
Click to expand...
Click to collapse
After 'adb reboot bootloader', and device being recognized as "Android 1.0", just manually update the driver: its the same driver that you used for adb. Windows is dumb.
Use search or browse the forums, read the stickies, this has been covered over and over again.
Sent from my i9250
If all else fails get mskips galaxy nexus toolkit v10.x, see xda thread or google skipsoft, and let it sort out drivers and adb, it has easy options and a good help section, should get the job done.
Btw if you are having driver issues you should try the driver download pack from samsung official website's manuals and downloads, its a tad under 30mb, run it then reboot computer then plug in gnex and any missing drivers should auto install, be patient, windows is a retard so it may take a coupla minutes
sent via xda premium from starkissed noozxoide maguro gnex paranoid beta9.5
This worked for me:
rootzwiki -> Google/Nexus Devices -> Galaxy Nexus -> "Galaxy Nexus Root Procedure - (broken) ADB Method Dont USE" -> page 3, second to last post on the page (by litso):
"EDIT: Scratch that, was able to use the PDANet drivers. Install PDA Net, reboot into bootloader, open device manager, manually select the directory "C:\Program Files (x86)\PdaNet for Android\usbwin". Fastboot will then recognize the device and allow you to unlock."
I can't post a link because I am a 'new user' due to low number of posts, but that is the path to your solution. I literally just went through this yesterday.
It's basically what bk201doesntexist said in the above post. I used the pdanet driver, but I'm sure the normal Samsung driver should work.
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
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
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...