Database Users

Fastboot driver problem on Windows 10 64-Bit

Hello,
I am trying to connect my EVGA Tegra Note 7 in fastboot mode to a Windows 10 64-Bit machine, but device manager is only showing this as a fastboot device with a yellow exclamation mark. I have tried all approaches I could find in this forum (SuperTool, Windroid, download drivers from Nvidia Homepage, 15 Sec. ADB driver) but cannot get a successful fastboot connection. ADB connection is fine.
Any ideas what I might need to do to get Windows and the fastboot driver to recognize my device?
Regards
Sven

Have to tried the latest driver version?

"Waiting for any devices" with Moto G4

Excuse me for my bad English. I am new on this Forum. Please help me, I have a big problem!
I can’t use Fastboot command, because ewery time I got the „Waiting for devices” error message 
1) I have a Motorola Moto G4 phone (XT 1622, athene)
2) This mobile are not rooted.
3) I want to unlock my bootloader, after this I want to install TWRP, and after this I van root my mobile, for install the custom Lineage OS.
4) On my phone I activated at the Developper Otions the USB debugging, and OEM Unlocking.
5) I connected my phone to my PC, I used first time Windows 10. On this system my Moto G4 are identified: Motorola ADB interface. No problem with identification, no any yelow exclamation matrk, no unidentified device!
6) I have installed the correct ADB and Fastboot driver v.1.4.3 (link is made from this site)
7) I have installed the Motorola driver from the official Motorola site.
8) All ADB command work fine, for example adb devices, adb reboot bootloader, etc.
9) But no fastboot command work, when I tested the fastboot devices, I got the „Waiting for devices”. Of corse befor this, I rebooted my phone in fastboot mode! If I use any fastboot command, I got this error message.
10) I try to use the excellent tools (thank you for this): Universal Fastboot & ADB tool, latest version, but the situation in this case is the same, „Waiting for devices”.
11) Of corse I rebooted the PC after instalation of the drivers, the fastboot.exe is in the right paths, etc.
12) I have installed the Universal USB Driver with the Universal Fastboot & ADB tool, Install drivers button, PC rebooted after this.
13) I used Windows 10, Windows XP, and Ubuntu, and in all cases I got the „Waiting for devices”
14) Under Ubuntu I got this message, despite that on Ubuntu the ADB and Fastboot driver installations are cleare.
15) I tested all on many other PC.
16) Every time I connected my phone to the PC only on USB 2.0 port, I changed the USB port, and I changed the USB cable too.
17) I read hundred ot tutorilas on youtube, on differant Forums, but none of them helped.
18) I uninstalled or reinstalled a many timet he ADB and fastboot drivers (I tested a lot of drives from the net), and I installet a many times the official Motorola driver, and the Google universal USB driver, but nothing
Please tell me what can I do for solve this devil situation, Please help me! Thank you again!

NVIDIA shield tv 2015 stuck after flash-all.bat

After updating my shield tv to Oreo I successfully downgraded to 6.3.0 so that I could play PUBG mobile using octopus app. Well now that PUBG mobile detects the octopus app and bans players for using the app I wanted to go back to Oreo. I downloaded the recovery image 7.1.0 and got my device recognized by my pc windows 10. Ran the command adb devices and my device was recognized. I proceeded to run the adb Fastboot devices and my pc recognized my device. I then ran the adb reboot bootloader command. Then I ran the flash-all.bat command. This is where I’m stuck. My device is stuck in bootloader. My pc no longer detects my device when I run the adb devices or Fastboot. I am able to boot to recovery kernel on the shield. I have tried to apply update from adb but I think I’m not getting the correct files. If I select apply update from adb My PC does recognize my device as sideload. No Fastboot devices found. Please help me get my device back to Oreo or just operating.

Fix it
Hi did you manage to fix your shield as I have the same problem

I bricked my shield tv
I bricked my 2015 16gb shield tv. Powers up then turns off immediately

You must install the USB Drivers from NVIDIA, there is a separate driver that your computer needs to communicate while in fastboot/bootloader. So just because ADB works, does not mean Fastboot will work.

I have repaired several SHIELD TV 2015,And I can add shield TV 2015 storage。32G /64G /128G。Just need to replace EMMC.
https://item.taobao.com/item.htm?spm=a1z38n.10677092.0.0.594c1debq5W8P3&id=576292085112
The link above is to buy the chip and repair the machine by oneself.
https://item.taobao.com/item.htm?spm=a1z38n.10677092.0.0.594c1debq5W8P3&id=576414610358
This link needs to be sent to China to replace FLASH chips.

My NVIDIA is dead ?no os no fastboot mod no adb and no recognize by my PC for install the drivers i have just the NVIDIA boot logo who freeze after booting

Unlocking bootloader on Windows 10 Driver issues Help!

I'm dumbfounded. I have unlocked bootloaders and rooted for years. Just got my OP8P.
I also have a new Microsoft Surface Pro with Windows 10.
I installed ADB, installed Fastboot.
Unlocked developer options and turned on USB Debugging and Developer Unlock.
Windows device manager shows ADB INTERFACE for the my device in device manager.
I can open can open Power Shell and/or the CMD prompt. I've done both.
I can type adb devices in the command prompt and I CAN see my device.
I can reboot it fastboot from the CMD prompt so I KNOW Wndows sees my phone.
BUT ONCE I'M IN FASTBOOT, the problem starts.
Fastboot does NOT see my device. Commands return the words "Waiting for Device..."
I BELIEVE the issue is with the drivers. When I boot into Fastboot, my device location changes in Device Manager from USB>ADB Interface to Portable Devices>Android.
The Android Device icon has a yellow triangle with an exclamation mark. It's says the driver for this device is not installed. But everything was working fine and the drivers were fine while the device was powered up normally.
If I try to manually install the driver it fails and says "cannot update drivers for your Android".
What heck is going on? What did I do wrong?
I've uninstall and reinstalled the drivers direct from Oneplus. I've uninstall and reinstalled the drivers direct from Google. 'I ve uninstall and reinstalled the drivers direct from Windows.
Why can't device and drivers be recognized in Fastboot. And why can't I update the drivers for the "Android" device?

Fastboot mode not detected in Windows 10 device Manager

Hello Everyone,
I would like to install fastboot ROM on Redmi Note 7 and my PC cannot recognized it on fastboot mode. I almost tried everything like intall 5sec fastboot driver and latest fastbott drivers but it didn't work. I sincerely ask you guys how can I solve it.
Thank you so much

saonaylinn said:
Hello Everyone,
I would like to install fastboot ROM on Redmi Note 7 and my PC cannot recognized it on fastboot mode. I almost tried everything like intall 5sec fastboot driver and latest fastbott drivers but it didn't work. I sincerely ask you guys how can I solve it.
Thank you so much
Click to expand...
Click to collapse
Install Miflash +drivers.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
and/or
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf

I recently started having trouble sideloading updates through ADB. I was using Win 11, PowerShell and had Bitdefender installed as anti-virus. However, I had no problem on a Win 10 machines using the same programs.
To fix it on my primary Win 11 machine, I disconnected from internet after my download of the OTA, killed BitDefender, and used a Command window instead of PowerShell. That worked for me.
Granted fastboot is different than ADB, but it could be the same problem. Also make sure your Platform Tools is up to date.