Fastboot problems - GT540 Optimus General

I am trying to flash Android 2.3.3 with Cynagon Mod but I cannot because my Win7 computer wont install the driver properly, it says Fastboot Interface Google USB ID but it also says there was an error in installing it, so what do I do
The CMD is stuck on < waiting for device >

Install all drivers with this tools : http://www.mediafire.com/?oqbqy9e74uqj5s9

Related

[Q] 2.3.6 fastboot is not reading device

am running stock 2.3.6 on att am attempting to root but fastboot doesnt recognize my device i type in moto-fastboot devices it doesnt do anything just restarts with a new command line ............ i installed the 5.50 drivers but nothing its just pissing me off i have usb debugging on n the usb set to none ..do i have to install the usb charging drivers ??
message sent! Android Sdk?

"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!

Device bricked

Hi!
I bricked my axon7 g.. I had a running CM15.1 and wanted to restore a CM14.1 backup. First of all i downloaded and flashed the modem and bootloader for cm14.1. after that i wiped system and data and rebootet into recovery. Here I noticed a bug wich i already had when I updated to CM15.1: the data and system partition are unable to mount. So i download and installed a other recovery (nfound) and rebooted. And here is the Problem: I'm unable to go into the recovery.
After some hours of trying different methods I need your help. This is what I found out:
1) I can boot into FFBM and fastboot
2) when I boot into fastboot the windows device manager shwos me Android ADB Device
3) when i try to use the adb tool i says:
Search >>> interface found >>> Android ADB Interface
Checking ADB Interface:
Command execution adb devices >>> !!! Error !!! no answer from phone
This is becuase usb debugging was not enabled.
4) When i use the dfu tool and wnat to confirgure the ports it only says: this device has no usb ports or (when i turn of virus scanner and reboot..) "the tool is running"
Is there any way to flash a recovery?
Thank you!
I solved it via fastboot and adb

PC fastboot recognition issue

Today i tried to install a custom ROM update which caused a softbrick and now my device is stuck at the logo. I naturally decided to flash a stock rom in order to solve this. I went ahead and downloaded a MIUI 11 global stable one, next was rebooting into fastboot and connect it to my PC...
...When i rebooted my phone into fastboot, my PC didn't recognize the device at all. Device Manager says "USB Unknown Device (Device Descriptor Request Failed)". I verified the USB port and cable works properly with another phone, i installed USB drivers and ADB/fastboot ones, still nothing.
Is there anything I'm missing? I'm not very adept at these topics, I previously flashed mine into a PE custom ROM purely by following tutorials mindlessly.
Try the app "Xiaomi ADB/Fastboot Tools", this has the option to flash stock ROMs. The USB drivers that I have installed on my computer are "minimal ADB Fastboot 1.4.3".
You could also solve the problem with the tool "MiFlash Pro".

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?

Categories

Resources