Develop Bugs

Rooting Galaxy Nexus fastboot < waiting for device >

Hi,
I am attempting to root my Galaxy Nexus using the guide at http://forum.xda-developers.com/showthread.php?t=1529058 I successfully get through the first step “adb reboot bootloader” and the phone gets to fastboot screen. I then do:
Code:
> fastboot oem unlock
and I get:
Code:
< waiting for device >
I also attempted to do:
Code:
fastboot devices
and I get nothing. However on the phone screen in red it says “FASTBOOT MODE”.
I think my driver is properly installed because when the phone boots up, and is unlocked, I can do
Code:
adb devices
and I get:
Code:
List of devices attached
<serial number> device
Are there different drivers for fastboot? (USB Debugging is obviously enabled because I can get the adb devices list.)
Thank you,
O. O.

yes there are different drivers for fastboot vs adb.

Zepius said:
yes there are different drivers for fastboot vs adb.
Click to expand...
Click to collapse
Thank you Zepius, so how do I get the fastboot drivers?
I would like to add that in ADB Mode i.e. when my phone is connected via the USB and is unlocked i.e. unlocked screen with the icons, I can see “SAMSUNG Android Phone” listed in the Device Manager. I am working on Windows 7.
O. O.

o.o. said:
Thank you Zepius, so how do I get the fastboot drivers?
I would like to add that in ADB Mode i.e. when my phone is connected via the USB and is unlocked i.e. unlocked screen with the icons, I can see “SAMSUNG Android Phone” listed in the Device Manager. I am working on Windows 7.
O. O.
Click to expand...
Click to collapse
follow this: http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1

Zepius said:
yes there are different drivers for fastboot vs adb.
Click to expand...
Click to collapse
Zepius said:
follow this: http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
Thank you very much Zepius. This helped and my device is now rooted.

Please edit title thread to include [SOLVED], thanks.
Sent from my Nexus

[Q] unlock bootloader prompt will not appear

When going through the adb commands and i type in fastboot oem unlock the command window says waiting for device but on the device nothing at all happens. Ive tried doing it in mtp and ptp modes but still nothing happens. device has never been rooted or unlocked before. On marshmallow and latest june security patch, please help

Wetbreadguy said:
tried doing it in mtp and ptp modes
Click to expand...
Click to collapse
It can only work in fastboot mode (when off press power+vol.dn).
The fastboot devices command must return your N7's serial number. If not, run it as root/admin and/or install a new driver and fastboot app or use NRT.

k23m said:
It can only work in fastboot mode (when off press power+vol.dn).
The fastboot devices command must return your N7's serial number. If not, run it as root/admin and/or install a new driver and fastboot app or use NRT.
Click to expand...
Click to collapse
I do have it in fastboot mode when i run the commands, i just originally set it in mtp or ptp modes.

fastboot never start after update to android 6

Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!

Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english

No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.

bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?

krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.

bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.

i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?

bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.

Here is screenshot from minimal adb...
Phone must be in MTP mode.

And here is phone in fastboot

Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.

bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.

can't boot into fastboot / fastboot can't find device

hello, this is my first post here.
i have a Samsung Galaxy S4 Mini (GT-I9195) and i want to install lineage on it. to do that i need to install twrp. i found several videos and instructions online, but i always get stuck at using any fastboot commands.
Code:
sudo adb devices
shows my device.
Code:
sudo adb reboot bootloader
reboots the phone and it goes into "download mode"
Code:
sudo fastboot devices
doesnt give any output
and any command with
Code:
fastboot
just outputs
Code:
< waiting for any device >
so, either my phone just isnt in fastboot mode, or i really dont know whats going on. could anyone help me with that, please?
about me: this is literally the first time im having an android device (im a sailfish user), so forgive me the possible beginners mistakes. also, my host pc is runing mint19.

Download Mode its fastboot mode for Samsung Devices, if you use Windows should use Odin, if you use GNU/Linux OS should use Heimdall for Samsung devices.

kevinarol said:
Download Mode its fastboot mode for Samsung Devices, if you use Windows should use Odin, if you use GNU/Linux OS should use Heimdall for Samsung devices.
Click to expand...
Click to collapse
thank you so much! i have never heard of that software before! that was really a great help! though it still doesnt work, but i guess ill make a new thread for the new issue...

Question I'm stumped - Fastboot mode LE2125 not responding to ADB commands

When I updated my LE2125 Oneplus 9 pro 5G to C.63 I lost root ( I tried the Magisk way when I previously updated and it allowed me to update and then preserve my root) and couldn't get it back.
So I decided to downgrade using MSM Tool and now I am on Oxygen OS build 11.2.2.2.LE15AA and I can no longer use any ADB commands when in Fastboot mode (the device does not respond), my laptop does not acknowledge using ADB Device (but it does when NOT in Fastboot mode).
The device shows Device State Locked.
When booting my phone up, I made sure in Developers options to set OEM Unlocking checked ON, as well as USB debugging checked ON.
When on Oxygen OS build 11.2.2.2.LE15AA and reboot into Recovery , I have the "Advanced" option, but not if I upgrade to LE2125_11.C.48_1480_202204082113 and rebooting into Recovery, choosing English, the next screen does not show the "Advanced" option as an available choice..
Laptop on Windows 10, have used MSM tool with my LE2125 with no issues. Anybody have any ideas?

LormaD said:
When I updated my LE2125 Oneplus 9 pro 5G to C.63 I lost root ( I tried the Magisk way when I previously updated and it allowed me to update and then preserve my root) and couldn't get it back.
So I decided to downgrade using MSM Tool and now I am on Oxygen OS build 11.2.2.2.LE15AA and I can no longer use any ADB commands when in Fastboot mode (the device does not respond), my laptop does not acknowledge using ADB Device (but it does when NOT in Fastboot mode).
The device shows Device State Locked.
When booting my phone up, I made sure in Developers options to set OEM Unlocking checked ON, as well as USB debugging checked ON.
When on Oxygen OS build 11.2.2.2.LE15AA and reboot into Recovery , I have the "Advanced" option, but not if I upgrade to LE2125_11.C.48_1480_202204082113 and rebooting into Recovery, choosing English, the next screen does not show the "Advanced" option as an available choice..
Laptop on Windows 10, have used MSM tool with my LE2125 with no issues. Anybody have any ideas?
Click to expand...
Click to collapse
You can't use adb commands in fastboot. You can only use fastboot commands. fastboot devices

jamescable said:
You can't use adb commands in fastboot. You can only use fastboot commands. fastboot devices
Click to expand...
Click to collapse
i meant to say fastboot commands...
i.e. fastboot devices, fastboot oem unlock, fastboot boot boot.img

LormaD said:
i meant to say fastboot commands...
i.e. fastboot devices, fastboot oem unlock, fastboot boot boot.img
Click to expand...
Click to collapse
Then it's a driver issue

jamescable said:
Then it's a driver issue
Click to expand...
Click to collapse
So you think it's a driver issue when the phone responds to my laptop when "Not" in Fastboot mode, and then no longer responds to commands when in Fastboot mode?...
Will try that...

LormaD said:
So you think it's a driver issue when the phone responds to my laptop when "Not" in Fastboot mode, and then no longer responds to commands when in Fastboot mode?...
Will try that...
Click to expand...
Click to collapse
Yes. A lot of people say adb works but fastboot doesn't. Usually there's a driver update in windows. Google it man. Very common

I had the same problem. After messing around with some drivers it finally started working

GeminiRx said:
I had the same problem. After messing around with some drivers it finally started working
Click to expand...
Click to collapse
Damn Drivers...
I did a system restore to an earlier point in Windows 10... I then redownloaded and installed oneplus USB drivers and it worked.