Hi there,
I'm having problems when trying to install a ROM through the 'install zip from sideload' feature in ClockworkMod 6.0.4.3. My Windows 8.1 PC can't recognize the device at all while in the sideload (Mounting USB storage works perfectly). The device doesn't show up when I type
Code:
adb devices
in the command prompt, even when I run it as an administrator. It can't be the recovery because I've tried downloading from different places and tried to flash about 3 times.
Is anyone else having this problem? Or has had this problem in the past but has solved it already?
Thanks in advance
Do you have usb debugging enabled on the phone? It's under the developer options.
Swiftflikk said:
Hi there,
I'm having problems when trying to install a ROM through the 'install zip from sideload' feature in ClockworkMod 6.0.4.3. My Windows 8.1 PC can't recognize the device at all while in the sideload (Mounting USB storage works perfectly). The device doesn't show up when I type
Code:
adb devices
in the command prompt, even when I run it as an administrator. It can't be the recovery because I've tried downloading from different places and tried to flash about 3 times.
Is anyone else having this problem? Or has had this problem in the past but has solved it already?
Thanks in advance
Click to expand...
Click to collapse
Adb sideload should be working fine. Make sure you're not using a 3.0 usb hub.
Sent from my HTC One Max using Tapatalk!
Hello!
I was trying to downgrade a Moto E XT1021 and I don't remember how but I ended with the phone stucked in the "bootloader unlocked" screen.
Tried to access the phone on the fastboot flash mode and I can get into the mode by pushing volume down and power on for a few seconds. The problem is that I'm not able to send command to the phone because adb or fastboot doesn't detect it.
The USB cable seems to be working because on the phone screen you can read USB connected and USB disconnected every time I connect or disconnect the cable.
My guess is that there's a problem with the drivers, I've tried everything, of course installing the MotorolaDeviceManager_2.5.4.exe was the first step and then I ended up trying adb-setup-1.4.3.exe and also adb-setup-1..3.exe with no luck. I'm using Windows 7 professional 64 bits.
Right now phone driver says: Android Composite ADB interface.
Hardware ID is USB\VID_22B8&PID_2E80
If I remove the driver the device with no driver says "fastboot condor S"
I want to install 4.4.4 on that phone.
What can I do?
Thanks!
I solved it
Close the thread please.
provide the solution
draxofavalon said:
I solved it
Close the thread please.
Click to expand...
Click to collapse
at least provide the solution if anyone comes wandering again with the same problem
I really don't know why it worked, but I had several folders with adb, fastboot and firmwares and ona of the folders with fastboot detected the phone, I tried the other folder and that version of fastboot didn't detected the device; really weird.
Same software, same dll's but in different hard drives, the one on the C drive worked and the one in the D drive didn't detect the phone.
As I said, really weird.
Hey all.
I use a Redmi Note 3 (Snapdragon) and upto now I used CM13. I wanted to switch back to MIUI 8, as it supports LTE, so I tried to flash the MIUI ROM using TWRP. My device bricked and doesnt go past the loading screen. The bootloader also got locked and my device is also not being detected in adb command prompt. In device manager, I can only see ADB Bootloader driver but not any other. I tried installing ADB drivers again but it doesnt work. I believe I did not enable USB debugging. I have a TWRP backup of the previous ROM on my pc but is there any way to flash it?
Please help
Hi , I am new to xda and was previously viewing the posts of other users only, now I have an issue with one of my devices. I have a phicomm passion 660 in INDIA AKA Phicomm P660 in Europe.issue is the digitizer is broken ,USB debug is not enabled, ADB and Fastboot doesn't recognise the device as it appears to be issue with Google USB drivers( which is obvious due USB debug not enabled), all I want to do is use optical mouse to use the device again for DEDICATED VR VIEWING, I can boot the device to Fastboot and in normal boot the pc recognises the device as MTP, I tried steps from many other posts but since the device is not recognised by ADB , the result is ground zero,cant install cwm through sdcard due signature verification error.so any help or direction to relevant posts would be very helpful
Hi all,
I tried to flash the latest TWRP but for some reasons it's messed up. Now I can't enter recovery mode and just wondering if there is a way to re-install it.
I tried to do it via Fastboot mode but my PC(windows 10) can't recognize the phone when in Fastboot mode. I tried several ways(e.g. reinstall USB driver, remove / install driver via device manager, etc.) but no luck.
Any help/suggestion is appreciated.
Try with the original cable. It will work for sure. I had almost the same issue, tried various drivers, etc. Once I've connected the phone with its original cable, it was recognized instantly.
Strange, other people say, the original cable is bad quality??
I would use a different cable but an usb port on the mainboard no a front usb port.
Also i do all the adb und fastboot stuff on a linux machine, it's less struggeling with drivers then.
The original cable still works though, I'm not so sure what bad quality can that be... And yes, I haven't used it in these 3 years more than half of the time. In the past year I was using a 3m Ugreen cable which didn't do the trick for drivers, still working well.
However, with some changes in the kernel or whatsoever, the original cable doesn't charge the phone anymore while connected to the computer, but it ensures a good data transfer.
PS: USB type-C is more complex and not standardized for all manufacturers, which is a bit surprising, but that's it.
eqt2010 said:
Hi all,
I tried to flash the latest TWRP but for some reasons it's messed up. Now I can't enter recovery mode and just wondering if there is a way to re-install it.
I tried to do it via Fastboot mode but my PC(windows 10) can't recognize the phone when in Fastboot mode. I tried several ways(e.g. reinstall USB driver, remove / install driver via device manager, etc.) but no luck.
Any help/suggestion is appreciated.
Click to expand...
Click to collapse
you need to format whole phone in oder to be recognized by pc.try first deleting all drivers for x2.go to windows in device manager,reboot pc and reconnect phone to pc by using usb type c cable
thank you for all the recommendations. I will try original cable and other PC using Linux and see if that works.
Update: My windows 10 PC installed the wrong driver when phone is in fastboot mode. Working fine now after deleting it from Device Manager and reinstalling.
Hey everyone,
im trying to unlock the bootloader of my LG G5, but am unable to do so as the phone is not detected at all when in fastboot mode.
While it is recognized just fine as an adb device, after rebooting into fastboot mode via adb reboot bootloader it is not recognized as an USB Device in Windows (The device manager does not show any device with wrong drivers and does not react to replugging the device). I also tried it on a different machine with the same results.
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
I installed the necessary (I tried LG and Google) drivers and tried different USB ports (2.0 and 3.0) and cables. The phone just is not noticed as an usb device at all when in fastboot mode.
Could this be due to a broken usb port? Which seems odd because the phone is recognized when not in fastboot mode.
What else could cause this weird behaviour?
Thank You!
Just to be clear. After you booted into fastboot mode, did you try
Code:
fastboot devices
and it just showed nothing?
holgers0n said:
Hey everyone,
im trying to unlock the bootloader of my LG G5, but am unable to do so as the phone is not detected at all when in fastboot mode.
While it is recognized just fine as an adb device, after rebooting into fastboot mode via adb reboot bootloader it is not recognized as an USB Device in Windows (The device manager does not show any device with wrong drivers and does not react to replugging the device). I also tried it on a different machine with the same results.
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
I installed the necessary (I tried LG and Google) drivers and tried different USB ports (2.0 and 3.0) and cables. The phone just is not noticed as an usb device at all when in fastboot mode.
Could this be due to a broken usb port? Which seems odd because the phone is recognized when not in fastboot mode.
What else could cause this weird behaviour?
Thank You!
Click to expand...
Click to collapse
Do you have usb debugging on because some devices require it to be on in order to be able to use fastboot on the computer.
In addition to ADB and Fastboot you have to install the "Android USB Driver" that is suitable to your phone, too, to get Fastboot working.
I forgot to mention that, oem unlock and USB debugging is enabled.
I tried installing the LG and android USB driver. But there is no way I can install these drivers to my fastboot device, as it is not recognized as an USB device at all, its like I'm plugging an USB cable with nothing attached to it into the computer.
QUOTE="User699, post: 84602251, member: 11475773"]
Just to be clear. After you booted into fastboot mode, did you try
Code:
fastboot devices
and it just showed nothing?
[/QUOTE]
Fastboot devices does not show anything.
holgers0n said:
I tried installing the LG and android USB driver. But there is no way I can install these drivers to my fastboot device, as it is not recognized as an USB device at all, its like I'm plugging an USB cable with nothing attached to it into the computer.
Click to expand...
Click to collapse
The "Android USB Driver" is a Windows OS driver, hence it must get installed in Windows OS.
jwoegerbauer said:
The "Android USB Driver" is a Windows OS driver, hence it must get installed in Windows OS.
Click to expand...
Click to collapse
Yes i am aware of that. As mentioned i installed the driver, my phone is recognized as an adb device. I have seen some solutions suggesting installing the driver manually when the fastboot device is not recognized correctly but the device is not recognized at all. I also tried installing the drivers as legacy hardware (Android ADB interface, Android Bootloader Interface etc.) via device manager, which results in an error ( error code 10, device can not be started)
No more clues by me.
@holgers0n
I tried lsusb on my Xiaomi (I don't have lg) and it worked in fastboot also.
Since it doesn't show anything if you do fastboot devices, you could try to do the standard things:
1) Change usb port on your computer
2) Try another cable
3) If it's a usb type c, plug it into your smartphone, try if it works and if it doesn't, try around that cable and retry.
I am not 100 % sure but since you said
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
Click to expand...
Click to collapse
maybe you need to install non-free firmware as well.
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Narrry84 said:
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Click to expand...
Click to collapse
I'm also having the same issue with my Poco F1, it is recognized just fine as an ADB device, but not in fast boot mode. My laptop has both USB 2.0/3.1 ports hence I tried both but the result was just the same not recognised in fastboot mode
holgers0n said:
I also tried installing the drivers as legacy hardware (Android ADB interface, Android Bootloader Interface etc.) via device managerr, which results in an error ( error code 10, device can not be started)
Click to expand...
Click to collapse
yea I also manually installed USB drivers for my Poco F1 but in my case, I had no error
The same thing is happening to me on my LG g5, did you find a solution?
akashrathi7978 said:
I'm also having the same issue with my Poco F1, it is recognized just fine as an ADB device, but not in fast boot mode. My laptop has both USB 2.0/3.1 ports hence I tried both but the result was just the same not recognised in fastboot mode
yea I also manually installed USB drivers for my Poco F1 but in my case, I had no error
Click to expand...
Click to collapse
try linux, same thing has happened to me.
sanfi9 said:
The same thing is happening to me on my LG g5, did you find a solution?
Click to expand...
Click to collapse
try it on linux, install adb on linux and run "fastboot devices" I used to have the same problem.
akashrathi7978 said:
I'm also having the same issue with my Poco F1, it is recognized just fine as an ADB device, but not in fast boot mode. My laptop has both USB 2.0/3.1 ports hence I tried both but the result was just the same not recognised in fastboot mode
yea I also manually installed USB drivers for my Poco F1 but in my case, I had no error
Click to expand...
Click to collapse
Have you tried linux?
hellofriendlymanveriosns said:
Have you tried linux?
Click to expand...
Click to collapse
No, but i got it fixed with this AMD FASTBOOT FIX guide as i was using AMD Ryzen 5 5500U.
My laptop have both USB 2.0/3.1 ports hence it worked for me on USB 2.0 port (otherwise buy a USB 2.0 hub) after running that ".bat" file as "admin" it recognised my phone.
Keep in mind i uninstalled all 3rd party "adb tools" then rebooted my laptop and used Google's official Adb tool (approx 12mb) then ran "cmd" on the same path (keep the adb tool in :c drive)
akashrathi7978 said:
No, but i got it fixed with this AMD FASTBOOT FIX guide as i was using AMD Ryzen 5 5500U.
My laptop have both USB 2.0/3.1 ports hence it worked for me on USB 2.0 port (otherwise buy a USB 2.0 hub) after running that ".bat" file as "admin" it recognised my phone.
Keep in mind i uninstalled all 3rd party "adb tools" then rebooted my laptop and used Google's official Adb tool (approx 12mb) then ran "cmd" on the same path (keep the adb tool in :c drive)
Click to expand...
Click to collapse
STEPS I did to solve this issue on my Laptop with AMD CPU
🗃️POCO F1 Ultimate Collection & Guides📚
Welcome to POCO F1 Ultimate Collection! 🗃️ (beryllium) OFFICIAL STOCK MIUI ROM ©️ You can check my Guides for installation. Recovery ROM V12.0.3.0.QEJMIXM Fastboot ROM V12.0.3.0.QEJMIXM POCO F1 Global Stable ROM Library / POCO F1 MIUI...
forum.xda-developers.com
holgers0n said:
Hey everyone,
im trying to unlock the bootloader of my LG G5, but am unable to do so as the phone is not detected at all when in fastboot mode.
While it is recognized just fine as an adb device, after rebooting into fastboot mode via adb reboot bootloader it is not recognized as an USB Device in Windows (The device manager does not show any device with wrong drivers and does not react to replugging the device). I also tried it on a different machine with the same results.
Ubuntu also does not recognize the device at all, lsusb does not output the device anywhere. It also does get recognized as an adb device when booted up normally.
I installed the necessary (I tried LG and Google) drivers and tried different USB ports (2.0 and 3.0) and cables. The phone just is not noticed as an usb device at all when in fastboot mode.
Could this be due to a broken usb port? Which seems odd because the phone is recognized when not in fastboot mode.
What else could cause this weird behaviour?
Thank You!
Click to expand...
Click to collapse
Hello I have exactly the same problem. I know all the right drivers are installed, because I already flashed it from CN Rom to EEA ROM a few weeks ago. Usb debugging is activated, bootloader unlocked, etc . Nothing works.
Have you resolved the problem since?
Had the same problem after running:
adb reboot bootloader
Tried to run a fastboot command e.g. `fastboot getvar unlocked`, it gave the message `< waiting for any device >`
Solution
Assuming you have the bootloader driver installed, but its not connecting.
After running " adb reboot bootloader " with the device plugged in and in the bootloader follow these steps.
Open Device Manager => Win + R => devmgmt.msc .
Find the device called Android that has a yellow warning sign on it.
{
"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"
}
Open the properties and hit update driver.
Select "Browser my computer for drivers"
Select "Let me pick from a list..."
Select "Android Device"
(If this option doesn't show up, then you don't have the drivers installed)
Select Android Bootloader Interface
(If this option doesn't show up, then you don't have the drivers installed)
Click next and the the bootloader driver should be working.
This solution does need to be repeated when ever the device goes into bootloader mode i.e. when you want to run fastboot commands.
Mmm, just stumbled here to say that I had this problem since loong ago I unlocked the bootloader of my Z2121, and didn't know why. The reason is that I was using the Minimal ADB and Fastboot tool, because after reading the threads Bootloader driver issues on Windows 10? and [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows subsequently, and of course using fawazahmed0's Latest ADB Installer, my problem was solved.
The BAT installer in the thread downloads the actual BAT installer file whose download path you can find inspecting it, and that other actual installer file for now sets the installation folder name as "platform-tools", and also adds its path into your system's user Path variable to allow running ADB and Fastboot commands from whatever folder location. For this reason you must also change the Path variable along with the folder's name if you wish to do so, or edit and modify the actual installation BAT file to change the folder name (there are a few entries).
Hope this is of help.