Question fastboot command not working | waiting for any device - OnePlus Nord 2 5G

Hi all,
first of all: yes, I've used the search function but I couldn't find a solution.
I have a Nord 2 5G device and want to install Evolution X Custom ROM.
I followed the instructions in this forum (and other websites) and managed to downgrade to OOS 11 in order to get into fastboot. The adb command to boot into fastboot mode also worked and my device is saying
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. If you want to exit fastboot mode, please long press volume up and power buttons simultaneously.
Click to expand...
Click to collapse
However, the fastboot command to flash TWRP does not work. On the command line I can only see
< waiting for any device >
Click to expand...
Click to collapse
and I continuously hear the Windows device attached/device detached chime. The device manager shows this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After opening the properties, I can see this:
As it's German. It says:
The drivers for this device have not been installed. (Code 28).
There are no compatible drivers for this device.
Click to expand...
Click to collapse
So obviously I need additional drivers. I have downloaded the USB drivers from this website: https://developer.android.com/studio/run/win-usb, chose install from hard drive and pointed to the directory I have unzipped the driver set but Windows can't install them. I have also downloaded the OnePlus driver set from https://oneplusdriver.com/download-oneplus-driver and installed them.
Still, it doesn't work.
I am at the end of my rope now. What did I do wrong?
Thanks in advance!

I have same problem did you find solution

mckinley87 said:
Hi all,
first of all: yes, I've used the search function but I couldn't find a solution.
I have a Nord 2 5G device and want to install Evolution X Custom ROM.
I followed the instructions in this forum (and other websites) and managed to downgrade to OOS 11 in order to get into fastboot. The adb command to boot into fastboot mode also worked and my device is saying
However, the fastboot command to flash TWRP does not work. On the command line I can only see
and I continuously hear the Windows device attached/device detached chime. The device manager shows this:
View attachment 5835135
After opening the properties, I can see this:
View attachment 5835137
As it's German. It says:
So obviously I need additional drivers. I have downloaded the USB drivers from this website: https://developer.android.com/studio/run/win-usb, chose install from hard drive and pointed to the directory I have unzipped the driver set but Windows can't install them. I have also downloaded the OnePlus driver set from https://oneplusdriver.com/download-oneplus-driver and installed them.
Still, it doesn't work.
I am at the end of my rope now. What did I do wrong?
Thanks in advance!
Click to expand...
Click to collapse
Have you try to use platform-tools? It has adb and fastboot. I have always used that and no problem
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com

Look in Eigenshaften > Details > "Device instance path" (k.A. Gerätepfad?).
What's the VID/PID?
Is that in the stock INF file in android_winusb.inf?
If you want, you can just use Zadig drivers. I can give you "fastbogus.exe".
https://zadig.akeo.ie/
Select "WinUSB".

HamdiPiixel said:
I have same problem did you find solution
Click to expand...
Click to collapse
Yes, the thing is, I've installed the drivers in the wrong way. I'll try to give a step-by-step guide:
Go to Device Manager and find the Device (will have the yellow triangle. Right-click on it and choose upgrade driver (hope that's what's shown in the english version of Win 11). You'll see this:
Click the second option. You'll see this:
Here, choose the second option at the bottom. That's where I did it wrong. I selected the drivers in the dropdown menu and that doesn't work.
Click there...
and click there to select the diver *.inf file in the usb_driver folder.
That should work. It's important that you use the official Google Drivers (at least it was important here).
Hope that works.

mckinley87 said:
Yes, the thing is, I've installed the drivers in the wrong way. I'll try to give a step-by-step guide:
Go to Device Manager and find the Device (will have the yellow triangle. Right-click on it and choose upgrade driver (hope that's what's shown in the english version of Win 11). You'll see this:
View attachment 5856845Click the second option. You'll see this:
View attachment 5856867
Here, choose the second option at the bottom. That's where I did it wrong. I selected the drivers in the dropdown menu and that doesn't work.
View attachment 5856869
Click there...
View attachment 5856871
and click there to select the diver *.inf file in the usb_driver folder.
That should work. It's important that you use the official Google Drivers (at least it was important here).
Hope that works.
Click to expand...
Click to collapse
Hi,
I managed to install the ADB google drivers so I can now at least see Fastboot devices response properly but I do not know how to unlock the bootloader as the command "fastboot oem unlock" is not recognized and there is still no menu for the bootloader unlock (only the message on the black screen)
If anyone could help I would be be very grateful.
Thank you.
Best Regards
Lad

Related

[TUTORIAL] How to take Screenshots in Recovery Mode [noob friendly]

TAKING A SCREENSHOT IN RECOVERY MODE VIA DDMS ​​
INTRO - Many guys have the doubt that whether one can take a screenshot in recovery mode or Not ...... Well it is possible to take a screenshot in the recovery mode.let me help you to know how to....i made this guide soo Noob friendly, that too along with the picture's ..
The only way to take a screenshot in the recovery mode is via DDMS.....for more Awesome info on DDMS please have a look at this Thread.....(click me)
1) Install Java JDK :-​Before installing the Android SDK, you’ll have to install Oracle’s Java development kit. You can download it from here...(click me !!)
Even if you already have the Java runtime (JRE) installed, you’ll need to install the JDK as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After installing Java JDK , you can now download the Android SDK from Google .
NOTE:- If you see a any type of Java-related error during installation, then download and install the x86 version of the JDK, not the x64 one ..
Click to expand...
Click to collapse
2) Installing android SDK:-​Download Android SDK from here...(click me !!!)
After clicking on "DOWNLOAD FOR OTHER PLATFORMS" , you will get an extended menu ..
After downloading the .exe file , then Double click on the .exe file and install it in C:\ Drive or on whichever drive you wanna install .
Click to expand...
Click to collapse
Click to expand...
Click to collapse
3) Android SDK Setup
Click to expand...
Click to collapse
Once the Android SDK is downloaded and installed, launch the SDK Manager application from your Start menu.
Enable the Android SDK tools and SDK Platform-tools checkbox and click the Install button. This downloads and installs the platform-tools package, which contains ADB and other utilities.
After installing these packages , Go to the place where you installed ANDROID SDK . IN MY CASE , IT IS :-
Code:
C:\Program files(x86)l\Android\android-sdk\tools
If you used a different install location, you’ll find DDMS in the tools directory,inside your ANDROID-SDK directory .....
MOST IMPORTANT :- To DDMS with your device , you must Enable USB DEBUGGING and you install your device driver's
1) you must enable USB debugging on it. You’ll find this option under Developer Options on your device’s Settings screen
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
2)You must install your device drivers :- Individual OEM USB drivers for windows are available for each manufacturer and are listed in the official document ..
After you have downloaded you device drivers, then we have to install on our pc. for that :-
a) connect the device to the computer
b) right click on MY COMPUTER and click manage
c) go to devices > other devices and right click on device and select update driver software.
d) you should see an option to " BROWSE MY COMPUTER FOR DRIVER SOFTWARE" , which you nedd to click on and point to the location of your device driver installation file..​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
​
To test whether DDMS is working properly, connect your Android device to your computer using a USB cable
..Now it will show the devices connected ..
Now that you have sucessfully installed DDMS and now we are good to go further..​
NOW GO TO ANDROID FOLDER AND OPEN TOOLS
2)NOW RUN MONITOR.bat AS ADMINISTRATOR
3)NOW ANDROID DEBUG MONITOR WILL APPEAR ..
TIME TO TAKE A SCREENSHOT....​
​
Troubleshooting ;-
sometimes it will not recognize a Device in recovery mode..So in this case ,either uninstall your device drivers and then reinstall it OR refresh your device list in the DDMS device panel..... GOOD LUCK TAKING A SCREENSHOT​ :fingers-crossed:​
I am not from this section..just waned to share my guide in your section..heres a link to my original guide.... link = click me...!!
Thank you,
P.007​
Screenshots in recovery mode​​
Nice guide. Reserved for future use.
Sent from my Galaxy Ace GT-S5830 using xda premium
This is very useful, THANKS :good:
Clean and simple, thanks! :good:
it works on normal android system with me
but it wont work on the recovery (android system recovery) & on custom recovery (CWM)
even if i mount the usb storage under the recovery (monitor recognise the phone) , screenshot is just empty white
also in (android system recovery) the phone is recognised by monitor only when i press "adb / side load" thing
i want help :\

I can't load in fastboot mode

Hello,
I would like to root my Z5C, but I can't load the phone in fastboot mode.
I tried the following :
adb reboot bootloader (with my phone one, with usb debug)
the phone shut down completely, but nothing is displayed on the screen​
power up + volume up (from my phone shutdowned)
there are three vibrations, and sometimes the logo Xperia appears for a few second, but then the screen show the charging icon​
power down + plug usb (from my phone shutdowned)
nothing appends​
each time, I tried the following command to check if the phone was indeed in fastboot mode :
fastboot devices
but I get nothing (empty list).
Could you help me please?
thanks in advance.
As far as I know, only the led will light up. The display stays black. Have you looked in the device manager if your device is recognized there. Maybe as an unknown device etc?
then I probably don't have the correct driver. I installed this one
developer.sonymobile.com/downloads/drivers/xperia-z5-compact-driver
Do you know where I can find the correct driver?
In device manager, I see a new item when I plug my phone :
USB mass storage device
I tried to update the driver with the one mentioned before, but it says that it is already up to date.
Noneangel said:
Hello,
I would like to root my Z5C, but I can't load the phone in fastboot mode.
I tried the following :
adb reboot bootloader (with my phone one, with usb debug)
the phone shut down completely, but nothing is displayed on the screen​
power up + volume up (from my phone shutdowned)
there are three vibrations, and sometimes the logo Xperia appears for a few second, but then the screen show the charging icon​
power down + plug usb (from my phone shutdowned)
nothing appends​
each time, I tried the following command to check if the phone was indeed in fastboot mode :
fastboot devices
but I get nothing (empty list).
Could you help me please?
thanks in advance.
Click to expand...
Click to collapse
You've got some commands wrong. Volume up plus power is hard reset. You get 3 vibrations then phone is off.
To get into fastboot mode or flash mode you do not use power button and phone needs to be off. Simply hold volume up and plug in USB for fastboot mode, or hold volume down plus plug in USB for flash mode. Blue LED for fastboot and green LED for flash mode.
This is the best option for install and drivers: http://forum.xda-developers.com/showthread.php?p=48915118
I became a lot more understandable, thanks you.
I tried to install android driver from the topic you suggested (I know I should post in this topic, but I have not enough privileges to do so), but I have the following issue :
after the installation of the drivers, I followed the howto_driver.zip (the device is not recognized), and in step 5, I don't see the "android device" driver.
As suggested by
If you have problem with driver enumeration in Windows 8.1 install update KB2917929
Click to expand...
Click to collapse
I tried to install KB2917929 but during the installation I got
The update is not applicable for this computer​error. After a bit of googleing, I found this
answers.microsoft.com/en-us/windows/forum/windows_8-update/instalation-failure-for-kb2917929/9ebb0567-8923-4f13-8840-61dbe54212e5
Hi ,
The Best Thing To Install KB2917929 Is To Remove The KB2919355 Update
To remove the update, follow these methods:
Press Windows Key + X.
Click on Programs and Features.
Click on View installed updates on the left hand side.
Find the update KB2919355, right click on it and Uninstall​.
After That Re Install The KB2917929 Update And It Will Be Installed
Click to expand...
Click to collapse
But when I tried to uninstal KB2919355 I got this error :
An error has occurred. Not all of the updates were successfully uninstalled​I gave up and tried to install the usb driver from a folder. I downloaded the following driver : developer.android.com/studio/run/win-usb.html
but when I tried to update the driver, I get a message error saying
windows could not find driver software for your device.​I run out of option (I might try this with linux, but I have no machine running under linux right now).
try forcing install of the driver by selecting the unknow device/detected phone and update/install driver by "find software driver in pc" then "choose manually driver from a driver list" then "driver disk" button on the right, "explore" and go the folder and select the downloaded driver. Be sure to install the correct driver described in the guides.
I get the following after selecting the "driver disk" :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I suppose that by explore you mean Have disk.
I tried to select the usb driver directory, and I get the following error :
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based system​The folder I selected is the unzip of the driver from developer.android.com/studio/run/win-usb.html
I'm not much help with Windows, I'm still running XP lol
civicsr2cool said:
I'm not much help with Windows, I'm still running XP lol
Click to expand...
Click to collapse
LOL kinda old school these days :cyclops:

XT1022: Failed to validate system image. Connect USB Cable. Device Locked - Status 0

Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
@lost101, Need your expert advice on this. Others, please do help.
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices​
lost101 said:
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices​
Click to expand...
Click to collapse
Live booted uBuntu Raring Ringtail 13. Added the necessary repositories first ;
sudo add-apt-repository ppa: phablet-team/tools && sudo apt-get update
Click to expand...
Click to collapse
. Further installed the ADB & Fastboot ;
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
. Got success messages.
Further using the terminal, used two commands ;
sudo adb devices
Click to expand...
Click to collapse
sudo fastboot devices
Click to expand...
Click to collapse
The result was exactly the same which i get in Windows command prompt. The list of devices shows a blank. I've installed the drivers and rechecked them, the device is listed as "Motorola ADB Interface" under Device Manager :
and; shows as Fastboot condor S in hardware eject box.
I fail to understand why it isn't showing as connected only in the fastboot menu. Fastboot reason is given as "fall through from not charger boot mode". The device shows only the fastboot screen by default. If any other option like recovery etc is selected, it throws the error message as bootup failed. Scenario is exactly of the same pic which was posted in #1.
Please suggest the next step.
@BBThumbHealer - Starting to look like Bootloader corruption. An unbrick method could be applied to potentially restore a functional Bootloader. One exists for Falcon 5.1 - unsure about Condor at this time.
I would try to eliminate the USB cable as the problem by trying alternatives.
BBThumbHealer said:
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
Click to expand...
Click to collapse
I was stucked in the same problem yesterday. I succeeded and recovered my Moto E to live again.
As in the screenshot you posted. Your bootloader is locked. You need to unloack the bootloader. To do so follow the steps in the link given below :
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Login or create your Moto ID and follow the steps as described.
After that you'll have to flash the firmware again. hope this helps.

Unable to flash TWRP [FAILED (remote: Command not allowed)]

Hey all,
--> I'm trying to flash TWRP to my Sony Z5 Compact, but the flash fails during the writing process of the .img file
--> It gives me the following error: FAILED (remote: Command not allowed)
--> I am currently running build number 32.3.A.2.33
--> The phone is NOT rooted (but this should not matter I think... because I cant do that either if I cant write anything to my phone...)
Things that I have already done:
1. I enabled OEM unlocking in the developer options.
2. I enabled USB-Debugging in the developer options
3. The ADB and Fastboot drivers are working correctly
Does anyone know how I can fix this issue? I have already browsed the web for a fix, found a lot of people having the same issue, but nothing has worked for me.
Thanks in advance!
Horizon
i didnt see you unlocked the bootloader, i guess this is the problem
Here link:
https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
its the easy part,
besure you backup everything bootloader for me did factory rest
i did with CMD terminal
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
its always good idea to backup also DRM keys also unlock takes your warranty
A. Install the Android SDK and the device drivers
1. Download and install the Android SDK. The SDK Manager is included in Android Studio, but you don’t need to install more than the basic Android command line tools. These can be found at the bottom of the page.
Tip: Take note of the installation path, you may need to access specific files later.
a. If you are running Windows: You need to install additional drivers.
1. When completing the installation, open the Android SDK Manager and go to the Extras folder to install the Google USB driver.
2. Download and install an updated Fastboot driver. This is the standardandroid_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony devices.
3. Replace the original android_winusb.inf-file with the downloaded file in theusb_driver folder, located in the Android >sdk > extras > google folder on your computer.
b. If you’re running OSX or Linux, you are not required to install any additional drivers.
2. On your device, turn on USB debugging by going to Settings > Developer options and click to enable USB debugging.
a. If your device is Android Jelly Bean 4.2 or newer: Developer options are hidden by default. To enable, tap on Settings > About Phone > Build Version multiple times. Then, turn on USB debugging by going to Settings > Developer options.
B. Connect to Fastboot
1. Turn off your Xperia™ Z5 Compact.
2. Connect a USB-cable to your computer.
3. On your Xperia™ Z5 Compact, press the Volume up button at the same time as you connect the other end of the USB-cable.
a. Windows users: When asked for a driver, open the Devices and Printers directory, click on the fastboot driver and press Update. Browse and point towards the location of the new android_winbus.inf file.
4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
5. Enter the following command:
fastboot devices
Click to expand...
Click to collapse
6. Verify that you get an answer back without any errors.
C. Enter unlock key
WARNING! The command below contains your unlock key. If you perform this step, you will unlock the boot loader. This may void your warranty and/or any warranty from your operator.
1. If you still want to unlock the boot loader of your device, enter the following command:
fastboot -i 0x0fce oem unlock 0x(here your code you got by sony)
Click to expand...
Click to collapse
2. Verify that you get an answer back without any errors.
D. Done!
You have now unlocked the boot loader of your device
good luck, update if got it right
PS .i posted my imei by mistake hope i didnt miss to remove another :X
Hey man! Thanks for the quick response! Went right to work with it this morning... and it fixed it!
--> I completely missed the next steps from Sony. for some reason I thought that OEM unlocking option would do the magic lol..
--> After I unlocked it through cmd it was a breeze from there! Got my TWRP on there and the Lineage ROM
Thanks!

Please help me understand why I can use ADB but not fastboot

Hello. I recently brought back my x820 to life. I need a phone.
It had TWRP and a custom rom. I tried to wipe and I actually wiped too much. So I had to install stock rom again because for some reason, lineage gave me an error at install (like it wasn't the right rom but it really was since I found it here https://download.lineageos.org/x2).
So I try to install TWRP again: twrp-3.7.0_9-0-x2.img found here: https://eu.dl.twrp.me/x2/
I launch ADB on a cmd prompt
- adb devices (List of devices attached e816a730 device). Super it's working and recognized
- adb reboot bootloader (phone miraculousely reboots in fastboot mode - YAY)
- fastboot devices ....... goes back to c:\ADB .... no devices found
So I reinstall ADB (from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/). Y to all, reinstall drivers and everything. Reboot PC. Do everything again.....still the same weird fastboot < waiting for devices >.
Devloper options are enabled.
OEM is unlocked.
USB debugging is ON.
Cable has been changed.
Cables have been plugged on USB 2.0 ports (in the back), on 2 different computers.....still the same thing.
*#*#76937#*#* typed in and AT ports enabled.
Could someone have the kindness to help me figure out what's wrong with what I'm doing? I'm usually pretty comfortable with rooting, flashing etc....but I'm clueless here.
Thanks for any help or input.
First off, please install the Android SDK Platform Tools [instead of 15 seconds ADB installer]
Once done, install the Fastboot Drivers on your PC.
The ADB Tools [Platform Tools, 15 seconds installer, etc] don't have Fastboot binaries, so you will only be able to execute ADB-related commands and not the Fastboot ones.
Thanks.
I downloaded the fastboot drivers. But I can't seem to install them. In fastboot mode, I see this in my device manager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I follow instructions from here: https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/ (your link). Although I'm on windows 10.
When I try to update driver, whatever I do, I get this error:
Which means "the folder doesn't contain any compatible driver for your device. If it contains a driver, make sure it can work for x64 computers".
So I'm pretty sure it's a driver problem. Is there a way to completely uninstall previous drivers and go from scratch again? Or any cleverer solution?
Try removing the faulty device then disable driver signature enforcement and install drivers.
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf
Thanks to both of you. Especially to you binary who pointed me on the right tutorial. I was doing something wrong when updating drivers in fastboot mode. I chose a device before locating the .inf file.
YES
NOOOOOOOOOOOOOOOOOOO
The bottom screen was taken from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
"Show all devices" MUST be selected before going a step further apparently. All 3 drivers were installed flawlessly. TWRP was flashed successfully. I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Cheers guys.
lucky24i said:
I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Click to expand...
Click to collapse
Glad that you were able to rectify the driver issue. As far as TWRP is concerned, as soon as you flash it, boot straight to it [without booting to the system] and then check out the result.
In some instances, the device tends to replace TWRP with stock recovery upon boot. So avoid booting to the OS and use fastboot reboot recovery to straightaway boot to TWRP after flashing it.
Thanks. Working great

Categories

Resources