Hello, I've searched and searched and can't seem to figure it out but for some reason I can run adb commands within the OS but can't run fastboot commands. Says waiting for device. Yes USB debugging is enabled and oem unlock is to. Running windows 10 with minimal adb and fastboot. The device is running Android 6.0 and the bootloader says ftp locked. Please help I'm trying to unlock the bootloader via my unlock code.
Reinstall the adb drivers
Try a with a windows 7 PC
Sorry for the late response but I had to use Ubuntu to do it must be something with windows 10. All is well now, thanks everyone.
Windows 10 doesn't work well with adb or fastboot
Related
Hi
I've had some hard time trying to unlock my GT-I9060I's bootloader (so I can install unsigned custom ROMs) but I didn't succeed.
Thins I've tried so far:
Installed Android SDK
Installed ADB and Fastboot drivers
Changed the android driver to Android Bootloader Interface
The problem seems to either be my computer not recognizing the phone in fastboot mode or simply my phone not booting in fastboot mode (even though
HTML:
adb reboot bootloader
rebooted my phone)
How can I unlock my bootloader?
h1ve said:
Hi
I've had some hard time trying to unlock my GT-I9060I's bootloader (so I can install unsigned custom ROMs) but I didn't succeed.
Thins I've tried so far:
Installed Android SDK
Installed ADB and Fastboot drivers
Changed the android driver to Android Bootloader Interface
The problem seems to either be my computer not recognizing the phone in fastboot mode or simply my phone not booting in fastboot mode (even though
HTML:
adb reboot bootloader
rebooted my phone)
How can I unlock my bootloader?
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
Please post in our Android hacking and development section here:
http://forum.xda-developers.com/android/help
You'll receive expert advice there. Good luck!
I have followed the instructions 3 times and keep getting same result it like adb is not reconizing my phone but my computer is? any help please
Adb commands work when the rom is booted and fastboot commands are needed to unlock the bootloader.
http://forum.xda-developers.com/ido...all-custom-t3475961/post69028659#post69028659
I have an Honor 8 FRD-L04 in fastboot/rescue mode and the ADB drivers doesn't recognize my phone when I type in fastboot oem unlock (unlock code) I am a noob sorry.
I hope you can help me because I am trying to install TWRP for my honor 8 EMUI 5.1 Nougat
How can I make my device recognizable.
First make sure you have ADB correctly installed on your PC. If it is installed but not working try to delete the entire folder, then download and install it again
Hello, my device is J7 2016 (SM-J710FQ) I installed twrp through odin and flashed custom ROMs but I didn't unlock the bootloader and I need to unlock now but since I use custom rom there is no "OEM Unlocking" option in developer options. I followed some guides and threads but I couldn't make it.
Here is what I did:
-Installed latest drivers for my phone
-Installed adb and fastboot
-Installed adb and fastboot drivers but I cannot change the driver. My phone is detected as "Samsung Mobile USB Composite Device" in fastboot and when I try to use the "Android Bootloader Interface" driver an incompatibility error occurs and driver doesn't change.
-My computer has Windows 10 in one disk, Mac OS in one disk and Windows 7 as virtual machine. I will install ubuntu alongside Mac OS.
Please help me to unlock bootloader / use fastboot
@strix said:
Hello, my device is J7 2016 (SM-J710FQ) I installed twrp through odin and flashed custom ROMs but I didn't unlock the bootloader and I need to unlock now but since I use custom rom there is no "OEM Unlocking" option in developer options. I followed some guides and threads but I couldn't make it.
Here is what I did:
-Installed latest drivers for my phone
-Installed adb and fastboot
-Installed adb and fastboot drivers but I cannot change the driver. My phone is detected as "Samsung Mobile USB Composite Device" in fastboot and when I try to use the "Android Bootloader Interface" driver an incompatibility error occurs and driver doesn't change.
-My computer has Windows 10 in one disk, Mac OS in one disk and Windows 7 as virtual machine. I will install ubuntu alongside Mac OS.
Please help me to unlock bootloader / use fastboot
Click to expand...
Click to collapse
You already unlocked your bootloader by enabling the OEM Unlocking option. If you hadn't unlocked your bootloader, you wouldn't have flashed twrp and custom roms. Why do you want to reunlock it again?
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.