HI
I tried to unlock the bootloader in oneplus 7. (Did all necessary setting like oem unlocking,Android reboot, USB debugging, USB installer)
when i reboot the device using bootloader, Device appearing in fastboot mode.
But when i check in "fastboot devices" there is no listing of devices !!
Normal "adb devices" is listing the device.
when i try to execute the command "fastboot oem unlocking " -Nothing is happening in Mobile.
Kindly help to resolve this issue.
androiduser0304 said:
HI
I tried to unlock the bootloader in oneplus 7. (Did all necessary setting like oem unlocking,Android reboot, USB debugging, USB installer)
when i reboot the device using bootloader, Device appearing in fastboot mode.
But when i check in "fastboot devices" there is no listing of devices !!
Normal "adb devices" is listing the device.
when i try to execute the command "fastboot oem unlocking " -Nothing is happening in Mobile.
Kindly help to resolve this issue.
Click to expand...
Click to collapse
What does it say on the phone?
Sent from my mata using XDA Labs
possibly change the USB cable and use the one supplied with the device
ignore
Related
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!
Hi i was trying to enable oem in Galaxy a5 SM-A500H i tried enabling it in developer settings but it didnt work i tried changing time
i tried it with adb i ran adb reboot bootloader and then it started the bootloader and i tried to run fastboot devices and fastboot oem unlock
first didnt print any devices
and fastboot oem unlock says "waiting for devices" i waited 5 minutes nothing changed
but adb devices worked before booting into bootloader
pasha5 said:
Hi i was trying to enable oem in Galaxy a5 SM-A500H i tried enabling it in developer settings but it didnt work i tried changing time
i tried it with adb i ran adb reboot bootloader and then it started the bootloader and i tried to run fastboot devices and fastboot oem unlock
first didnt print any devices
and fastboot oem unlock says "waiting for devices" i waited 5 minutes nothing changed
but adb devices worked before booting into bootloader
Click to expand...
Click to collapse
Maybe you find something more in the specific forum for the "old" A series on here https://forum.xda-developers.com/f/galaxy-a3-a5-a7-a8-a9-android-development.4857/
Regarding the fastboot commands you are trying to execute, this model doesn't support fastboot, the OEM unlock won't work at all.
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.
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
I would like to unlock the bootloader. I've enabled "Developer Mode" , "USB debugging", and "OEM unlocking". I also installed Minimal ADB and Fastboot on my Windows 10 PC. In the ADB and Fastboot terminal, it shows up as an adb device. "adb reboot bootloader" just causes the device to restart. I've only found 2 other guides, both of which are inconclusive. I've already unlocked the device with AT&T but that didn't solve my inability to unlock the bootloader. Any advice would be helpful.