Database Info

Unable to re-lock nexus-s through fastboot

i'm in the process of re-locking my bootloader in order to send it to Samsung for repair (home button not working). when i run the command line "fastboot oem lock", it just keeps hanging at "waiting on device" and nothing happens. i have the correct drivers installed. when i run "adb devices", it shows up the device. however, when i run "fastboot devices", it does not show up anything. any help on relocking my bootloader would be appreciated. Thanks!

Probably shouldn't be answering this here buuuuut...
adb reboot bootloader
and THEN
fastboot oem lock.
See what happens. You have to be in boot loader mode. Please move your questions to the Q&A section sir.

i did enter that command in order to get into fastboot. after that , i ran the command "fastboot oem lock" but it gets stuck at "waiting on device"

Update your drivers

Yea at this point I'd say its a connectivity problem. Drivers and or cable, but since you are getting adb devices to recognize, its not your cable. You should really use ubuntu, you would save yourself a lot of time, because you don't really have to deal with drivers like windows.

'sudo fastboot oem lock'
You need to be super user.

sure you went into bootloader and not recovery? because adb is seen in recovery and doesnt work in bootloader!

Fastboot command on Nexus 7 2012 not working

I want to unlock my Nexus 7's (android 4.4.4) bootloader but when i enter the command adb reboot boootloader it works but when i enter fastboot oem unlock it starts waiting for a device, and when i type in fastboot devices no devices are displayed. adb is working fine, but fastboot seems to not communicate with my device. Thanks for any help.
I'm using a Nexus 7 (2012) running Androis 4.4.4 KitKat.

ADB shows device when on but not Fastboot?

Hey guys, I'm pretty new to rooting and have gotten to the point where the bootloader is unlocked and am getting the screen where the device is unlocked and can't be trusted. Right now I am having trouble getting my computer to recognize ADB when it's in Fastboot mode. When the phone is in OS it will show the name of the device attached but once I boot into Fastboot I can't get the device to show using ADB Devices. I have the moto drivers installed and when the phone is on OS it shows (moto g7) in RSD Lite but shows (Fastboot river S) when in fastboot mode
- USB Debugging is enabled
- OEM Unlocking is on
- USB File Transfer On
Any idea what the issue could be?

Nevermind, I got it.. it's Fastboot Devices... I'm an idiot

sean909 said:
Hey guys, I'm pretty new to rooting and have gotten to the point where the bootloader is unlocked and am getting the screen where the device is unlocked and can't be trusted. Right now I am having trouble getting my computer to recognize ADB when it's in Fastboot mode. When the phone is in OS it will show the name of the device attached but once I boot into Fastboot I can't get the device to show using ADB Devices. I have the moto drivers installed and when the phone is on OS it shows (moto g7) in RSD Lite but shows (Fastboot river S) when in fastboot mode
- USB Debugging is enabled
- OEM Unlocking is on
- USB File Transfer On
Any idea what the issue could be?
Click to expand...
Click to collapse
When it's in fastboot use fastboot commands
Code:
fastboot devices
Setting up and Using adb.exe and fastboot.exe https://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

Pc can't communicate when in bootloader(tried everything)....

I just purchased a OnePlus Nord N10 5G (BE2026)
Originally it was running OxygenOs 10.x.x.x
Following guides from oneplus website and here on XDA I was able to successfully unlock the bootloader and of course ADB worked fine as well as Fastboot in the bootloader etc...
After unlocking the bootloader I realized that OxygenOs 11.0.2.BE86AA was available via OTA. Which is now what the phone is currently running.
***MAIN ISSUE***
after unlocking the bootloader in order to gain root access via TWRP and Magisk my PC fails to find any devices while the phone is in Fastboot mode... ADB still works just fine but as soon as I run "adb reboot bootloader" or boot to bootloader via buttons the PC will not detect the phone any longer while in the bootloader or Fastboot mode...
I have triple checked that:
SDK USB drivers
ONEPLUS USB DRIVERS
Windows Universal USB drivers
USB Debugging
OEM Unlocking
PC is granted developer access
newest version of ADB & Fastboot
and everything else I can find on this issue searching Google & XDA for the past 3 days
* one issue that I found strange, only when the phone was booted into the bootloader Windows device manager showed Android as an unknown device. Which I could only solve by using Zadig and installing Winusb driver... but still running "fastboot devices" while phone is in bootloader / Fastboot mode still shows no devices....
I've been trying to solve this about 4 days now scouring the internet for any information I could find and nothing seems to work. But everything worked just fine before I unlocked the bootloader / flashed OxygenOs 11 via OTA and now windows to see the phone while in the bootloader....

When phone is got booted into bootloader / fastboot mode then phone can't get seen / accessed by ADB. Point.

jwoegerbauer said:
When phone is got booted into bootloader / fastboot mode then phone can't get seen / accessed by ADB. Point.
Click to expand...
Click to collapse
@jwoegerbauer not entirely sure what you are trying to imply with your message...
If you are trying to point out that ADB doesn't work in bootloader / fastboot mode, I am completely aware of this. And never mentioned otherwise in my original message.
With my phone booted up into Android
And I run "adb fastboot bootloader" the phone will reboot into bootloader mode but my PC still shows waiting for devices... Or if I boot into bootloader / fastboot mode manually and run “fastboot devices" it shows no connected devices. And no fastboot Commands work either... I am not trying to run ADB Commands in fastboot mode.

AFAIK starting with Android 10 the command sequence should be as this
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
...
fastboot reboot
because fastbootd got moved to Android's userspace.

How to unlock Android Bootloader using ADB & Fastboot LG K30

Hi My name is NS₵,
I'm here on XDA Developers to learn about rooting and downgrading Android phone software. This will be my first time doing so with my old mobile device. I have an LG K30 and I'm trying to downgrade its firmware from Android 9 to Android 8.
I have been successful at using Android Platform Tools to "adb reboot" and "adb fastboot". At the moment the fastboot command does not pick up on the plugged-in device.
The LGK30 USB connection for: File Transfer. Meaning I can "Transfer Documents and media files to the connected device". This could be the reason that fastboot isn't working. The other USB connections are: Charging, Photo Transfer and MIDI Device.
When I run the command "adb devices" I get the following response: LMX410FGf5a1e0f3 device. Then I run the command "adb reboot-loader" and then the device boots into reboot loader. The screen contains the following text:
Welcome to fastboot mode for bootloader unlock:
1. Read device
fastboot oem device-id
2. Write unlock Key
fastboot flash unlock unlock.bin
3. Check bootloader is unlocked
fastboot getvar unlocked
The drivers I have downloaded for this device are the following: LGE Mobile MTP Device and MTP USB Device

No way to root a LG K30 here is the link