When I try to install the USB Drivers It fails with an error message.
ADB devices works, but fastboot devices doesnt.
I'm on Windows 10.
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
redpoint73 said:
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
Click to expand...
Click to collapse
Yes, I'm trying fastboot from the bootloader screen.
On windows 8.1 it works, I can install the needed drivers, on windows 10 I cannot. Doesn't work. I wonder why adb works but fastboot doesn't.
I had this exact issue up until today, and this what I did to get fastboot on my shield tablet:
1. Uninstall all adb usb drivers just to make sure you start from a clean slate.
2. Then go to Nvidia (https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB) and download their Nvidia shield tablet drivers.
3. While plugged into the computer (have the tablet set to transfer files or mtp) go to the Bootloader menu on your shield tablet and then on your computer go to device manager and update the drivers. For me the device showed up as Fastboot, right click and select update drivers from the folder that you unzipped your nvidia shield tablet drivers to. When I did this I actually got an 'This device cannot start. (Code 10)' error message but I think this is okay because when I looked at the device manager again a new listing had appeared near the top called Android Composite Device.
4. Now go through the exact same process to install the drivers that you did for the 'fastboot' device but now for the 'Android Composite Device', you should also still get the 'This device cannot start. (Code 10)'. After you've done all that reboot the Shield Tablet.
5. Once the tablet has rebooted go to command prompt with Administrator Privledges and type ADB devices and your device should show up, then type adb reboot bootloader and the tablet will reboot into the bootloader menu. I this point I did not select fastboot protocol and I'm not sure if this made a difference, but in any case in the command prompt type Fastboot devices and at least for me this finally worked.
I hope this helps.
Thank you Captain_FSU! :good:
I had the same problem. My Shield K1 was showing up on adb devices but not at fastboot devices. I was unable to update the driver. In Win 10 Device Manager my Shield was showing up at Portable Devices and it was impossible to install the driver there. So finally I am able to unlock bootloader and install TWRP.
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
For some reason, when I go to my fastboot mode, it shows blank screen. Any idea how i can get back to the default fastboot mode screen which usually shows device state, etc. My phone boots up fine , its OEM unlocked but without fastboot im unable to flash custom recovery or rom or do anything to be honest. One plust 6T. Please help
crmemaster said:
For some reason, when I go to my fastboot mode, it shows blank screen. Any idea how i can get back to the default fastboot mode screen which usually shows device state, etc. My phone boots up fine , its OEM unlocked but without fastboot im unable to flash custom recovery or rom or do anything to be honest. One plust 6T. Please help
Click to expand...
Click to collapse
with normal boot, i can access adb commands, its just that fastboot mode is blank and hence unable to access commands. Ive installed all possible drivers, i think the kernel is broken. Any possible way to fix this?
crmemaster said:
with normal boot, i can access adb commands, its just that fastboot mode is blank and hence unable to access commands. Ive installed all possible drivers, i think the kernel is broken. Any possible way to fix this?
Click to expand...
Click to collapse
Is developer options and usb debugging enabled in your phones settings? Also no screen lock set? If so if you have another Android device that's also rooted with magisk you can use Osm0sis and Surge's fastboot/adb magisk module, (a quick search in magisk will pull it up) Install it on your other device and use an otg cable ($5 online or make one yourself) and using termux app from "other phone" with connected otg & magisk root type: su (hit enter) grant root once it pops up then type: adb reboot bootloader then tick the pop up on phone you are trying to boot recovery on when it pops up. Then type: fastboot boot twrp_3.4.0-9-11.img (hit enter) Just make sure you put your TWRP recovery.img in correct directory on phone you you're using termux app on with otg and fastboot/adb module to boot the phone you are trying to boot to recovery.
Using root explorer directory in termux is: /data/data/com.termux/files/home/
place your TWRP_3.4.0-9-11.img ,, which ever TWRP image you are trying to boot in that directory...
Hope this makes sense. I don't use Windows and haven't for many years now. I've unlocked bootloader's and rooted many devices using another Android device this way now for years. Super easy! Not sure why you would be getting a black screen. Have you searched for solution to this? I would definitely search , a lot about the black screen situation.. Make sure you have a charged battery too. Sounds stupid I know but it's possible you are at 0%.. Hope this helps...
(Edit)
Hi,
i'm facing the problem that my phone only starts in "FastBoot Mode" at least i guess that's the mode.
OnePlus 6 with root.
It happened after i rebooted after installing an OTA Update and installing a Magisk Manager Update.
I used the method described here. The last few times it worked perfectly.
But now the only thing that happens when i try to boot the phone is a screen that says
FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - d8a34971
SECURE BOOT - yes
DEVICE STATE - unlocked
with the volume button i can select "START, Restart bootloader, Recovery Mode and Power off"
but nothing happens when i select e.g. Recovery Mode, or simply START.
The phone shows the boot logo for a second, then I'm back at the screen with "FastBoot Mode"
I installed the USB-drivers for the device and can find it with my PC when i type "fastboot devices" in the command prompt.
But that's pretty much all. I don't know how to continue.
I would be very glad if i could keep my data, is there a way to save my phone and if not how do i install the normal OS again?
I really hope someone can help me here.
Edit:
When I type "adb devices" it says "List of devices attached" but there is no entry.
USB-Debugging is on, since the Root-process i didn't touch the developer options
So should be the USB mode for file transfer (MTP)
I'm not sure if i checked the "always allow from this computer" setting
So following this guide the only thing i can't do is checking the prompt for USB-debugging since i can't boot the OS.
Is there anoter way to get a adb connection?
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery (with twrp is possible but not recommended). The updates will be done on the slot not used for example...
forum.xda-developers.com
For everyone that can't connect to the device via ADB but fastboot, this does the trick.
Thank you guys!
My phone. - Galaxy A51, One UI Version is 4.1, Android version is 12, Product Name – SM-A515F.
Stock ROM up to date.
I can boot into download mode, +/- volume, connect to pc. Works just fine.
But + volume & power boots into safe mode; - volume & power boots into safe mode; +/- volume & power boots into safe mode; +/- volume only boots into safe mode. I have ran out of button sequences to try.
What is wrong with my phone, is it impossoble to boot into recovery mode on my model of phone. This is why I cannot install TWRP as when I install via Odin, it will not boot into recovery post installation.
I am stumped.
Hello!
What is about phone: is it bootlooping or is it in downloading mode?
Other question: from what source did you download the twrp.tar file?
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
V0latyle said:
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
Click to expand...
Click to collapse
Guy, to complete the TWRP installation, it is needed to flash Disable_Dm-Verity_ForceEncrypt from TWRP, otherwise the device will not boot properly
vmirrimv said:
Other question: from what source did you download the twrp.tar file?
Click to expand...
Click to collapse
It's in Stock now. But it was stuck in a bootloop, but could boot into download mode. These are the recovery's which all installed but I could not boot into. I cannot boot into recovery now I am in Stock. It's as if there is no recovery option for my A51.
Twrp+vbmeta_A11.tar,
TWRP-11-3.6.0-a51-20220210-1636.tar,
TWRP-11-3.6.1-a51-20220228-2050.tar,
TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar,
TWRP-11-3.6.2-a51-20220602-0515.tar,
twrp-a51-3.5.0_10-1_ianmacd.tar
vmirrimv said:
Guy, to complete the TWRP installation, it is needed to flash Disable_Dm-Verity_ForceEncrypt from TWRP, otherwise the device will not boot properly
Click to expand...
Click to collapse
I was stuck in a bootloop and could not boot into TWRP..
Unless there is a way to flash Disable_Dm-Verity_ForceEncrypt in downlad mode using Odin?
V0latyle said:
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
Click to expand...
Click to collapse
Hi I am back in stock now, so no TWRP installed. Would this method boot you into Stock recovery?
Do I need to be in download mode or just normal mode when connecting the phone to the pc?
Hello, can you say what version of Android your phone on?
If it is on 12th, then I would say, that the problem is, that this version may not fully supported for TWRP working
Because as I tried, there was a fail in the procces.
Sorry, i did not see that you have already written about it
Yep, think I will have to download Android 10 stock rom; and hopefully be able to install 10 via Odin from 12 back to 10.
Sign1 said:
Hi I am back in stock now, so no TWRP installed. Would this method boot you into Stock recovery?
Do I need to be in download mode or just normal mode when connecting the phone to the pc?
Click to expand...
Click to collapse
ADB commands must be issued in system. The alternative would be from fastboot but it doesn't seem you can access that.
Try flashing TWRP again, but immediately hold Volume Up during boot to force booting into TWRP. Newer Samsung firmware does seem to have some sort of security measure that will replace a custom recovery, so you'll have to flash the Multidisabler to disable stock recovery auto-restoration.
Sign1 said:
Yep, think I will have to download Android 10 stock rom; and hopefully be able to install 10 via Odin from 12 back to 10.
Click to expand...
Click to collapse
I do not want to mislead you, but you will not be able to roll back from Android 12 to Android 10, because the current binary version of your phone (5) cannot be changed to lower one (4).
Maximum as you can do, is to downgrade to the 11th version and there, as I think and tried, the Twrp+vbmeta_A11.tar recovery file will be flashed sucessfuly and you will be able to enter TWRP without issues like bootloop.
Other problems are, as I think, that you may forgot to enable USB Debugging on your phone and authorize it with your computer, you may forgot to set the default USB Configuration as data transfer (MTP), or even you may not unlocked the bootloader.
I think they are the reasons because of which you could not enter TWRP, because, as I have tried to flash One UI 4.1 Android 12 according to this thread recently: https://forum.xda-developers.com/t/...ecovery-project-v3-6-2-android-11-12.4400869/
everything has been sucessful, both flashing and entering and following rebooting to Stock system.
Or you may even not removed the check mark from the parameter "Auto Reboot" in Odin
vmirrimv said:
I do not want to mislead you, but you will not be able to roll back from Android 12 to Android 10, because the current binary version of your phone (5) cannot be changed to lower one (4).
Maximum as you can do, is to downgrade to the 11th version and there, as I think and tried, the Twrp+vbmeta_A11.tar recovery file will be flashed sucessfuly and you will be able to enter TWRP without issues like bootloop.
Click to expand...
Click to collapse
Cheers for that, just downloaded Android 10, took me twelve hours to download, so its no use to me. I need to download Android 11.
vmirrimv said:
Or you may even not removed the check mark from the parameter "Auto Reboot" in Odin
Click to expand...
Click to collapse
Yep did that.