I have tried just about everything i can think of to make the phone be detected in fastboot, but nothing is working. The phone is detected through adb, but when i boot into fastboot and run fastboot devices, no devices are found. Device manager aslo says a code 28 error on the drivers for the device in fastboot, and i have looked all over for fastboot drivers and cannot find any. Im really stumped atm.
Related
Hello. Im trying to unlock bootloader on my wifes phone. All adb commands works. After I type adb reboot bootloader phone goes to fastboot mode and thats ok. But after I type fastboot devices nothing is happening. How can I fix it?
Gedablo666 said:
Hello. Im trying to unlock bootloader on my wifes phone. All adb commands works. After I type adb reboot bootloader phone goes to fastboot mode and thats ok. But after I type fastboot devices nothing is happening. How can I fix it?
Click to expand...
Click to collapse
it is a problem of s1 boot device driver . i even tried diabling driver signature on my win10 like every post suggested but no luck . i'm also trying to get over it
disable driver signature in win 10 and when windows boots go to device manager and update driver of s1 boot device from the files of given link
https://dl.xda-developers.com/4/0/0....zip?key=oeHhoI_uttjO0gP6y4vAiA&ts=1526629864
Hello, today I finally received my one plus 6. Been loving the device so far
I was on my way to Chuck a custom recovery and rom unlocked the bootloader no drama
I then hit a Plato of fastboot coming up with no command error as in fastboot isn't working in cmd I have researched heaps about it and I can not find a single thing. I tried to reinstall drivers and all that, and yes I'm running cmd in the fastboot files, only adb seems to be working but I can no longer use fastboot on my PC.
Has anyone come across this error, it seems to be that after installing the one plus drivers it stopped working correctly and fastboot commands no longer register in fastboot...
My phone is detected in fastboot mode so it's not the drivers. What could be causing this, is it the computer at fault?
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
J0hncramer said:
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
Click to expand...
Click to collapse
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
LokifiedMee said:
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
Click to expand...
Click to collapse
I just tried fastboot devices in powershell while the phone is connected via USB in fastboot mode and nothing was listed
Edit: i was able to get fastboot to work, I had to do the following steps i found on stack exchange to get my device to show up properly in device manager:
https://stackoverflow.com/questions/8588595/android-fastboot-devices-not-returning-device
Open device manager
Find Unknown "Android" device (likely listed under Other devices with an exclamation mark)
Update driver
Browse my computer for driver software
Let me pick from a list of devices, select List All Devices
Under "Android device" or "Google Inc", you will find "Android Bootloader Interface"
Choose "Android Bootloader Interface"
Click "yes" when it says that driver might not be compatible
Click to expand...
Click to collapse
With fastboot working and issues in device manager solved I was able to get TWRP loaded to my phone via fastboot and change my boot slot to get back into the phone
My phone is running perfectly fine. But after updating my phone last week officially, my PC doesn't recognize the phone in Fastboot. I'm trying to flash a custom recovery and root it, but in CMD, when I type fastboot devices, nothing comes up.
I am in the Fastboot mode when I try to do this. My phone was rooted earlier too with no issues. Also, in the Fastboot mode, The Bootloader version and the baseband version is blank. I tried different ports and a different cable along with a different PC, nothing seems to help.
Any suggestions?
Hi, did you ever get an answer?
I am having this exact same problem as well. Computer isn't recognizing the device as a fastboot device, I can't even run the fastboot boot recovery.img command to get into recovery.
I was able to get it to recognize my phone in fastboot mode by following the directions in this post: https://forum.xda-developers.com/t/...nize-device-but-adb-can.4040635/post-84052027
Though I never was able to root or install TWRP, this did allow my computer to recognize the phone in fastboot mode.
Hello, i have a really weird problem. When the phone is power up and working i can adb devices and see in the list my phone,. But when im in fastboot adb devices show empty. The phone is recognized in my device list with the drivers in fastboot mode.
I have installed a lot of drivers
i have tried in windows 10 and windows 7
thanks in advance.
When you're in fastboot mode you need to use the fastboot command, not ADB...
Try fastboot devices.