Recently upgraded to MIUI 11, it wiped TWRP and root. Wanting to re-root.
In fastboot mode, device isn't recognised by Windows 10: shows up as "Unknown USB Device (Device Descriptor Request Failed)". ADB works fine, fastboot doesn't.
I've tried installing drivers from Google and Xiaomi, neither work. Pretty sure it's a driver problem, but not sure how to fix it.
Any help would be greatly appreciated, cheers.
Have you tried manual driver installation from device manager?
ijwad said:
Recently upgraded to MIUI 11, it wiped TWRP and root. Wanting to re-root.
In fastboot mode, device isn't recognised by Windows 10: shows up as "Unknown USB Device (Device Descriptor Request Failed)". ADB works fine, fastboot doesn't.
I've tried installing drivers from Google and Xiaomi, neither work. Pretty sure it's a driver problem, but not sure how to fix it.
Any help would be greatly appreciated, cheers.
Click to expand...
Click to collapse
- close digital signature verification in w10 (google it)
- install TOOL ALL IN ONE v2.1 zip (search on xda) and install drivers from it
- you should install xiaomi pc suite, MiFlasher so that any unforseeable drivers also get addressed and installed.
plz try and report back
piakos said:
Have you tried manual driver installation from device manager?
Click to expand...
Click to collapse
Yes, I tried to uninstall + delete the broken driver from device manager. It always goes back to the Unknown driver, and claims it's is up-to-date when trying to install anything else.
YasuHamed said:
- close digital signature verification in w10 (google it)
- install TOOL ALL IN ONE v2.1 zip (search on xda) and install drivers from it
- you should install xiaomi pc suite, MiFlasher so that any unforseeable drivers also get addressed and installed.
plz try and report back
Click to expand...
Click to collapse
OK, I put Win10 in test mode, so it installs any unsigned drivers. Installed the drivers from the ALL IN ONE tool and MiFlasher. Installed PC Suite.
No change, the device is still listed as Unknown while in fastboot and recovery mode.
Also, the device acts like it's being plugged out and plugged back in every few seconds while in fastboot or recovery mode, while completely stationary. This doesn't happen in system. Not sure if that's relevant, but it's weird.
Is there a way to clean out all the drivers I've installed and start fresh? I recall having driver issues with Nexus devices in the past, and wiping all android drivers was the solution.
ijwad said:
Yes, I tried to uninstall + delete the broken driver from device manager. It always goes back to the Unknown driver, and claims it's is up-to-date when trying to install anything else.
OK, I put Win10 in test mode, so it installs any unsigned drivers. Installed the drivers from the ALL IN ONE tool and MiFlasher. Installed PC Suite.
No change, the device is still listed as Unknown while in fastboot and recovery mode.
Also, the device acts like it's being plugged out and plugged back in every few seconds while in fastboot or recovery mode, while completely stationary. This doesn't happen in system. Not sure if that's relevant, but it's weird.
Is there a way to clean out all the drivers I've installed and start fresh? I recall having driver issues with Nexus devices in the past, and wiping all android drivers was the solution.
Click to expand...
Click to collapse
You should try downloading and install Qualcomm drivers manually.
Those drivers are specifically for Qualcomm devices and intended for fastboot mode and EDL mode
Darklouis said:
You should try downloading and install Qualcomm drivers manually.
Those drivers are specifically for Qualcomm devices and intended for fastboot mode and EDL mode
Click to expand...
Click to collapse
Installed the Qualcomm drivers, no luck. Device still unrecognised.
I managed to root it before, so I'm worried this is a weird software issue on my Poco that could be solved with a full format. I'd like to try as many options before getting to that though, my last full backup was a few months ago.
Could you attach some screenshot of error on fastboot
armuttaqin said:
Could you attach some screenshot of error on fastboot
Click to expand...
Click to collapse
Yep, here you go.
ADB works fine, but the device isn't recognised in fastboot mode.
1. ADB works
{
"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"
}
2. Fastboot doesn't
You dont have the fastboot driver installed.You have to install it when the phone is in fastboot mode.it happened to me as well.
hexisg said:
You dont have the fastboot driver installed.You have to install it when the phone is in fastboot mode.it happened to me as well.
Click to expand...
Click to collapse
The problem is, the drivers won't install in fastboot mode. This error comes up when I try to manually install drivers from Google, Xiaomi, or Qualcomm directly in Device Manager:
Are you on an AMD RYZEN platform?
Shinichi Kudo said:
Are you on an AMD RYZEN platform?
Click to expand...
Click to collapse
Nope, Intel CPU. The specs are below, if it helps.
Delete this device "Unknown USB device ..." from the device manager when you're connected.
Select "remove driver ..." as well in this process.
Disconnect phone
Reboot PC
Connect phone in fastboot mode
Install fastboot driver manually.
rolex0815 said:
Delete this device "Unknown USB device ..." from the device manager when you're connected.
Select "remove driver ..." as well in this process.
Disconnect phone
Reboot PC
Connect phone in fastboot mode
Install fastboot driver manually.
Click to expand...
Click to collapse
Just tried this. It gave the same error, saying that the best driver is already installed.
Also, the "remove driver" option isn't there when uninstalling:
You need to manually override the driver, e.g. force the installation of the Google Android USB driver.
You can try to remove all the drivers and after the cleanup just let the Mi Unlock software install them for you.
I have done this after a clean windows installation to get all the drivers installed even when my device is already unlocked.
The Mi Unlock tool installs all the necessary drivers for me, you can try this I guess.
I have other problem with mtp transfer works only when adb enabled
Hello IJwad, I have the exact same problem. It occured after installing Miui 11. Is it already solved for you?
Smellie2 said:
Hello IJwad, I have the exact same problem. It occured after installing Miui 11. Is it already solved for you?
Click to expand...
Click to collapse
I'm having the same issue too. any way t0o fix it?? I'm on miui11
---------- Post added at 09:53 PM ---------- Previous post was at 09:28 PM ----------
Shinichi Kudo said:
You can try to remove all the drivers and after the cleanup just let the Mi Unlock software install them for you.
I have done this after a clean windows installation to get all the drivers installed even when my device is already unlocked.
The Mi Unlock tool installs all the necessary drivers for me, you can try this I guess.
Click to expand...
Click to collapse
I tried this but doesn't work
i have the same issue, think the problem is with the miui11 update not the windows's because i can fastboot into other device but no luck with poco.
i hope the next update would fix this or maybe not. anyone tried reolving this issue ?
Related
Hello, I'm facing a problem while trying to root my Sony Tablet S. Using "S.onyTablet.S__ALLinONE__v6.3" I can't start rooting my device because I get stucked when it says "waiting for device", nothing happens even if I wait 10 minutes.
I installed the ADB drivers and executed "adb devices" command, all went fine. I can see my tablet on my PC and have access to storage.
Is there sonthing I'm missing ? I tried other root methods using the same script but same result, once "waiting for device" and in other time "path specified inaccessible"
I hope you can guide me. Thanks
webdzdz said:
Hello, I'm facing a problem while trying to root my Sony Tablet S. Using "S.onyTablet.S__ALLinONE__v6.3" I can't start rooting my device because I get stucked when it says "waiting for device", nothing happens even if I wait 10 minutes.
I installed the ADB drivers and executed "adb devices" command, all went fine. I can see my tablet on my PC and have access to storage.
Is there sonthing I'm missing ? I tried other root methods using the same script but same result, once "waiting for device" and in other time "path specified inaccessible"
I hope you can guide me. Thanks
Click to expand...
Click to collapse
Go into tablet's Settings > Developer Options and set USB Debugging to ON.
Cat McGowan said:
Go into tablet's Settings > Developer Options and set USB Debugging to ON.
Click to expand...
Click to collapse
I already did that and checked for "unknown sources" as well.
do not run AiO directly from archive - unpack it, best location is root of C:\ for example.
then try to root. if it still fails, then try to right-click - run as admin.
if you have still problems - run task manager on pc, and check if some adb process exists,
if yes - kill it, then try again to use AiO.
I also had similar problem when had installed Droid Explorer - it runned in background,
with its adb - which caused some problems with communication.
oh, and always use newest ver - currently v6.4 (not 6.3).
br
condi
condi said:
do not run AiO directly from archive - unpack it, best location is root of C:\ for example.
then try to root. if it still fails, then try to right-click - run as admin.
if you have still problems - run task manager on pc, and check if some adb process exists,
if yes - kill it, then try again to use AiO.
I also had similar problem when had installed Droid Explorer - it runned in background,
with its adb - which caused some problems with communication.
oh, and always use newest ver - currently v6.4 (not 6.3).
br
condi
Click to expand...
Click to collapse
Same here, Droid Explorer became a disappointment because of that unfortunately.
Sent from my Nexus 4 using xda app-developers app
Thank you for your advices, so :
-updated to 6.4........................................ok
-adb process kill from task manager..........ok (didn't find any)
-unpack root software in C:\....................ok
- run as admin.....................................ok
- Root..................................................Failed, still getting stuck on "waiting for device"
Nonetheless, I noticed when running root software, I killed adb process created by the software and there for one second it recognized my tablet but the adb process turned on again and I got "error device not detected"
I am getting crazy, I rooted many phones without any problem, but this tablet........Grrrrrrrrr.......any suggestions?
Try changing the adb files from another source. That was solved my problem.
Sorry for bad English.
webdzdz said:
Thank you for your advices, so :
-updated to 6.4........................................ok
-adb process kill from task manager..........ok (didn't find any)
-unpack root software in C:\....................ok
- run as admin.....................................ok
- Root..................................................Failed, still getting stuck on "waiting for device"
Nonetheless, I noticed when running root software, I killed adb process created by the software and there for one second it recognized my tablet but the adb process turned on again and I got "error device not detected"
I am getting crazy, I rooted many phones without any problem, but this tablet........Grrrrrrrrr.......any suggestions?
Click to expand...
Click to collapse
Connect tablet to computer.
Power on tablet. Best to have tablet connected to charger or at least, fully charged.
Open Windows Device Manager.
In Device Manager, check to see if these two devices are shown.
Android Phone > Android Composite ADB Interface
Portable Devices > Sony Tablet S
If either is missing or has a yellow triangle next to it, ADB drivers need to be installed/reinstalled or the USB cable is defective.
If both are shown, then run adb.exe to see if it detects your tablet.
Open a command window in Condi's AiO's \files directory; e.g., C:\S.onyTablet.S__ALLinONE__v6.4\files.
Type the following.
adb kill-server
adb devices
The following should be displayed.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
2755010100xxxxx device
(Note: xxxxx added by me to hide actual serial number.)
Before closing the command window, type the following.
adb kill-server
If nothing was shown under "List of devices attached", then either the USB cable is defective or the adb.exe supplied with Condi's AiO is not compatible with your tablet (unlikely) and you will need to install and use a different version of adb.exe.
Good luck.
I ended up having to install Koush's universal ADB driver to get it to work with mine, however that may be because I have drivers from Samsung, HTC, and Sony for ADB on my computer already.
Cat McGowan said:
If nothing was shown under "List of devices attached", then either the USB cable is defective or the adb.exe supplied with Condi's AiO is not compatible with your tablet (unlikely) and you will need to install and use a different version of adb.exe.
Good luck.
Click to expand...
Click to collapse
Thank you very very very much, at last I rooted my tablet, indeed it was adb drivers which was a little daizy, I installed it manually and every thing went smooth.
Thanks to all of you.:good::good::good:
Cat McGowan said:
Connect tablet to computer.
Power on tablet. Best to have tablet connected to charger or at least, fully charged.
Open Windows Device Manager.
In Device Manager, check to see if these two devices are shown.
Android Phone > Android Composite ADB Interface
Portable Devices > Sony Tablet S
If either is missing or has a yellow triangle next to it, ADB drivers need to be installed/reinstalled or the USB cable is defective.
If both are shown, then run adb.exe to see if it detects your tablet.
Open a command window in Condi's AiO's \files directory; e.g., C:\S.onyTablet.S__ALLinONE__v6.4\files.
Type the following.
adb kill-server
adb devices
The following should be displayed.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
2755010100xxxxx device
(Note: xxxxx added by me to hide actual serial number.)
Before closing the command window, type the following.
adb kill-server
If nothing was shown under "List of devices attached", then either the USB cable is defective or the adb.exe supplied with Condi's AiO is not compatible with your tablet (unlikely) and you will need to install and use a different version of adb.exe.
Good luck.
Click to expand...
Click to collapse
good afternoon I have a problem with the root, the program detected the tablet but I stay in this
R5A fw detected using new root method!
* Waiting for device
* Device found
* pushing exploit
* But it does not progresses
device manager and portable devices (sony tablet) brand me a yellow triangle please help need to be root: Llanto:
velgeek said:
good afternoon I have a problem with the root, the program detected the tablet but I stay in this
R5A fw detected using new root method!
* Waiting for device
* Device found
* pushing exploit
* But it does not progresses
device manager and portable devices (sony tablet) brand me a yellow triangle please help need to be root: Llanto:
Click to expand...
Click to collapse
With your tablet connected to your computer, open Windows Device Manager, then right-click on the device with the yellow triangle and select "Update Driver Software" to re-install the device drivers. If the drivers were previously installed and working, they should re-install without problem. If they don't, re-install them using the tool or method you used the first time you installed them.
Cat McGowan said:
With your tablet connected to your computer, open Windows Device Manager, then right-click on the device with the yellow triangle and select "Update Driver Software" to re-install the device drivers. If the drivers were previously installed and working, they should re-install without problem. If they don't, re-install them using the tool or method you used the first time you installed them.
Click to expand...
Click to collapse
I have installed the drivers but to stay in pushing exploit
not if they are bad drivers to install, if you have them please put some link to the original drivers for windows 8 64bit
Here some pictures of the problem
{
"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"
}
and whether aparese me if I remove the USB debugging
velgeek said:
I have installed the drivers but to stay in pushing exploit
not if they are bad drivers to install, if you have them please put some link to the original drivers for windows 8 64bit
Here some pictures of the problemView attachment 2091987
and whether aparese me if I remove the USB debugging
View attachment 2091988
Click to expand...
Click to collapse
From the images you posted, the ADB drivers appear to be installed and working; however, here is a link for downloading the ADB drivers and instructions for installing them on Windows 8.
BluechipJ's Automated ADB Driver Installer for Sony Tablet S and P
Also, USB Debugging must be set ON during the process.
Cat McGowan said:
From the images you posted, the ADB drivers appear to be installed and working; however, here is a link for downloading the ADB drivers and instructions for installing them on Windows 8.
BluechipJ's Automated ADB Driver Installer for Sony Tablet S and P
Also, USB Debugging must be set ON during the process.
Click to expand...
Click to collapse
Thank you very much as I could, was the usb cable was damaged but the change and has been perfect, now I'm root
probleeemm!!!!! helpmee
hello I have a problem and I have root on my tablet XD thanks, but now try to update my tablet sony flasher tool, but you mistakenly install the Sony Tablet P and now I can not return it and try to ordinary restore factory wing And Also try Correctly installed, but when it finishes flashing and restarted, does not change anything. Could anyone please tell me how to fix it: Llanto:
Try this first:
Uninstall (and delete if possible) the driver then reinstall it
Install the USB-Drivers from the Android SDK first (should automatically be checked to install when opening the SDK Manager)
If the above fails here is how to manually install the drivers for USB-debugging:
Method 1:
Download the Google USB drivers from here
Extract the ZIP anywhere
In the Windows Device Manager right click "G Watch" and select to update the drivers
Select search for drivers on the computer (2nd option)
Point Windows to that folder you just extracted (should be called "usb_driver")
Select that folder and Windows should install the correct drivers. You might have to restart the PC.
If method 1 fails (which was the case for me) go to method 2
Method 2:
Again in the Windows Device Manager right click "G Watch" and select to update the drivers
Select search for drivers on the computer (2nd option)
Select choose driver from a list of device drivers on this computer
Choose "Android Device" and click next
Select "Google" as manufacturer and "Android ADB Interface Version X.x.x.x" (newest one, for me it is 9.0.0.0) as model then click next
Select yes in the next dialogue
Windows should now manually install this driver
Remember that you also have to allow USB debugging on the watch first and also accept the warning on the phone that will appear after the watch drivers are correctly installed, else ADB will not work.
The options might not always be accurate as my computer language is set to german and I just freely translated
Make sure you have an up to date ADB version as well. I updated both driver and platform-tools from SDK manager. I loaded the COMPOSITE ADB version 10 driver.
Also you may have to turn on Bluetooth Debuging in Wear App and on Watch before you can get a prompt to authorize your PC ADB connection. This will likely show on the Phone not the watch to accept. (I ran into this issue last night)
spiderflash said:
Try this first:
Uninstall (and delete if possible) the driver then reinstall it
Install the USB-Drivers from the Android SDK first (should automatically be checked to install when opening the SDK Manager)
If the above fails here is how to manually install the drivers for USB-debugging:
Method 1:
Download the Google USB drivers from here
Extract the ZIP anywhere
In the Windows Device Manager right click "G Watch" and select to update the drivers
Select search for drivers on the computer (2nd option)
Point Windows to that folder you just extracted (should be called "usb_driver")
Select that folder and Windows should install the correct drivers. You might have to restart the PC.
If method 1 fails (which was the case for me) go to method 2
Method 2:
Again in the Windows Device Manager right click "G Watch" and select to update the drivers
Select search for drivers on the computer (2nd option)
Select choose driver from a list of device drivers on this computer
Choose "Android Device" and click next
Select "Google" as manufacturer and "Android ADB Interface Version X.x.x.x" (newest one, for me it is 9.0.0.0) as model then click next
Select yes in the next dialogue
Windows should now manually install this driver
Remember that you also have to allow USB debugging on the watch first and also accept the warning on the phone that will appear after the watch drivers are correctly installed, else ADB will not work.
The options might not always be accurate as my computer language is set to german and I just freely translated
Click to expand...
Click to collapse
Yes, worked Thanks!!
i can finally get adb to see my g watch, but it only comes up as unauthorized, i can't seem to get past that point,
fixed.
tomh1979 said:
i can finally get adb to see my g watch, but it only comes up as unauthorized, i can't seem to get past that point,
Click to expand...
Click to collapse
take the watch off the charger. turn the screen of your phone on. then place the watch on the dock connected to the pc again. there should now come up a warning on the phone about accepting the usb debugging. accept it and your done.
you probably didn't see the notification before as it comes up on the phone and not the watch so when your phone screen is off you won't see it.
I always get a 'Code 28'-error. Any ideas? It says: "The drivers for this device are not installed. (Code 28)"
{
"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"
}
BTW: ADB access was already accepted on my phone.
Any ideas? Thanks in advance.
brakke97 said:
I always get a 'Code 28'-error. Any ideas? It says: "The drivers for this device are not installed. (Code 28)"
Any ideas? Thanks in advance.
Click to expand...
Click to collapse
Which driver did you select exactly?
Same problem... Can't install driver
So here's what I did.... I downloaded the latest google usb drivers. Putted the usb drivers folder into C disc in a folder android... So C//android/usb_drivers (I don't know if the line I typed is written right but you know where it is and what I'm talking about )
Then I plug in my watch (usb debugging already checked), right click the G watch in device manager. Update drivers.... Search manually to the downloaded usb driver folder (android/usb_drivers).
If I press next it fails. So I have to select my device... The only device closest to what I think is the right device is the Samsung android device.
So I press next it completes but still not properly connected.
Read about the Samsung android device issue... So deleted the drivers completely... Again... Reconnected my watch but it always shows as Samsung android device....
Tried it on Windows 8 and 7...no luck so far...
Haven't tried it with the sdk manager but it's not so clear to me... It is only to download the USB drivers? Or also to install them properly?
Pls help! I wanna root this bit**
Thanks!
liobeir said:
So here's what I did.... I downloaded the latest google usb drivers. Putted the usb drivers folder into C disc in a folder android... So C//android/usb_drivers (I don't know if the line I typed is written right but you know where it is and what I'm talking about )
Then I plug in my watch (usb debugging already checked), right click the G watch in device manager. Update drivers.... Search manually to the downloaded usb driver folder (android/usb_drivers).
If I press next it fails. So I have to select my device... The only device closest to what I think is the right device is the Samsung android device.
So I press next it completes but still not properly connected.
Read about the Samsung android device issue... So deleted the drivers completely... Again... Reconnected my watch but it always shows as Samsung android device....
Tried it on Windows 8 and 7...no luck so far...
Haven't tried it with the sdk manager but it's not so clear to me... It is only to download the USB drivers? Or also to install them properly?
Pls help! I wanna root this bit**
Thanks!
Click to expand...
Click to collapse
Have u tried @Tomsgt G watch toolkit?
dude1981 said:
Have u tried @Tomsgt G watch toolkit?
Click to expand...
Click to collapse
please help me drivers adb for G WACHT , 2 METOD FAILED
no popup on phone
Hi should the popup come upon every phone I have tried rebooting phone factory reset watch reboot computer delete and re install drivers I just cant get the popup to come up on phone when i enable adb I ave tried over and over
i dont even get the chance to install the driver. i am getting the connect/dissconnect sound all the time. i dont believe that my device or the charging station is broken. pins look fine
liobeir said:
So here's what I did.... I downloaded the latest google usb drivers. Putted the usb drivers folder into C disc in a folder android... So C//android/usb_drivers (I don't know if the line I typed is written right but you know where it is and what I'm talking about )
Then I plug in my watch (usb debugging already checked), right click the G watch in device manager. Update drivers.... Search manually to the downloaded usb driver folder (android/usb_drivers).
If I press next it fails. So I have to select my device... The only device closest to what I think is the right device is the Samsung android device.
So I press next it completes but still not properly connected.
Read about the Samsung android device issue... So deleted the drivers completely... Again... Reconnected my watch but it always shows as Samsung android device....
i wanna use the android wear apk installer. but it won't conect to the watch...
Tried it on Windows 8 and 7...no luck so far...
Haven't tried it with the sdk manager but it's not so clear to me... It is only to download the USB drivers? Or also to install them properly?
Pls help! I wanna root this bit**
Thanks!
Click to expand...
Click to collapse
same is this a problem. cause it keeps saying samsung adb drivers. i wanna load some apk on it...
hum seems to work maybe i need root
just unlocked bootloader XD
help!!
So I bought my Lg G Watch off some dude and it turns out the watch was Rooted. I tried to reset to factory default but it wouldn't let me and then i was told that I had to unroot it first but to do this I need to install the Lg G Watch Drivers which is where my problem lies! When I open device manager my device does not appear anywhere there, I have ADB debugging turned on but apparently I have to have it paired to a phone which I also can't do because in order to pair it to a new phone I have to factory reset it. I'm stuck, someone please help Ive also tried to do the Android SDK way of installing the drivers but nothing there either.
Jonathan3440 said:
So I bought my Lg G Watch off some dude and it turns out the watch was Rooted. I tried to reset to factory default but it wouldn't let me and then i was told that I had to unroot it first but to do this I need to install the Lg G Watch Drivers which is where my problem lies! When I open device manager my device does not appear anywhere there, I have ADB debugging turned on but apparently I have to have it paired to a phone which I also can't do because in order to pair it to a new phone I have to factory reset it. I'm stuck, someone please help Ive also tried to do the Android SDK way of installing the drivers but nothing there either.
Click to expand...
Click to collapse
You don't need to unroot the watch to reset it. On the watch just go to settings -> factory reset
Does not appear in device manager
OK I have tried my best to resolve this, but need to ask for help....
My g watch (LG-W100) does not appear on the device manager.... unless in fastboot mode.
I have, in the past, unlocked the bootloader, ghoma'd it (is that a thing?) but as support has now stopped, i returned my watch to stock using the ghoma tool.
I didn't change anything on my 2 pc's that I have used, so I assume it's a "watch" thing, my "about" says...
Software Version 5.0.1 (want to update this)
Build number LWX48P
Android Wear 1.0.5.1627902
Things i have tried....
Reset watch...3 times. enabled adb debugging, enabled bluetooth debugging.
Revoked permissions (was hoping to see a request on my phone, but nothing).
Put watch into fastboot mode (the only time the PC "see's" the watch) and followed the usb driver guides.
Tried to adb from recovery mod, the watch disappears from the device manager then so no adb.
Tried running "OTA Update to Lollipop 5.0.2 from kitkat KNX01Q" whilst in fastboot... no go.
Tried running "LG G Watch Restore Tools" whilst in fastboot... no go.
Cleaning the contacts on the watch and cradle (although as it shows up in fastboot, I don't think this is a problem).
Hitting it.... no go.
Swearing at it... no go.
REALLY Swearing at it... no go!
Last resort, looking on google for solutions... no go
Just to be clear, this is not a "see it in Device manager, click on it, driver update etc".... it does not appear on Device manager unless in fastboot.
Has anyone else come across this? If so, please help!
Thanks for sticking with it this far!
Boyzdad said:
OK I have tried my best to resolve this, but need to ask for help....
My g watch (LG-W100) does not appear on the device manager.... unless in fastboot mode.
I have, in the past, unlocked the bootloader, ghoma'd it (is that a thing?) but as support has now stopped, i returned my watch to stock using the ghoma tool.
I didn't change anything on my 2 pc's that I have used, so I assume it's a "watch" thing, my "about" says...
Software Version 5.0.1 (want to update this)
Build number LWX48P
Android Wear 1.0.5.1627902
Things i have tried....
Reset watch...3 times. enabled adb debugging, enabled bluetooth debugging.
Revoked permissions (was hoping to see a request on my phone, but nothing).
Put watch into fastboot mode (the only time the PC "see's" the watch) and followed the usb driver guides.
Tried to adb from recovery mod, the watch disappears from the device manager then so no adb.
Tried running "OTA Update to Lollipop 5.0.2 from kitkat KNX01Q" whilst in fastboot... no go.
Tried running "LG G Watch Restore Tools" whilst in fastboot... no go.
Cleaning the contacts on the watch and cradle (although as it shows up in fastboot, I don't think this is a problem).
Hitting it.... no go.
Swearing at it... no go.
REALLY Swearing at it... no go!
Last resort, looking on google for solutions... no go
Just to be clear, this is not a "see it in Device manager, click on it, driver update etc".... it does not appear on Device manager unless in fastboot.
Has anyone else come across this? If so, please help!
Thanks for sticking with it this far!
Click to expand...
Click to collapse
OK, problem solved....
I stumbled over root junky's youtube vid, a comment from a user had a similar problem, root junky's advice, get "LG G Watch Restore Tools V8.zip" from here... Root Junky's excellent site!. Now...
1) Put watch into fastboot mode (hold reset button for 10 seconds, and then when the LG logo come up, swipe from top left to bottom right).
2) Run "1 LG G Watch Tools for Windows.bat"
3) Ensure your watch (device) is shown.
4) Select "6" (Restore your G watch to stock)... let it do it's thing.
5) My watch got stuck in a boot loop....so...
6) Reset into fastboot, then recovery mode (tap ">" twice then tap "o") .
7) When in recovery mode, "wipe data/factory reset" (swipe down twice then right, then OK).
8) Back in recovery mode, "wipe cache partition" (swipe down 3 times then right).
9) Finally "reboot system now"..... my watch then showed up on windows as all tutorials
I then updated firmware from root junky's site (link above)... all good, thanks root junky!
Hopefully this will help someone!
Thanks a million.. method 2 worked for me
Dears,
I checked few forums for miui and couldn't find solution to my problem.
The issue I have is causing that PC doesn't see the phone. What I have tried:
- different cables
- different PCs
- debbuginig is on
- restore factory defaults
- reinstall drivers for PC
- MIUI PCsuite
nothing above works.
I was oryginally on custom miui, with installed TWRP. However, I thougt that this was rootcause of the problem. I decided then came back to MIUI Global 11.0.4. Global ROM I installed via OTG. With this move I lost TRWP and now, don't have PC access to reinstall TWRP. So currently I'm not sure what are my options to instal that again.
Regarding USB diagnose, when it's connected to PC, phone bips when it plugs and charges, however nothing comes up to select MTP. I change in system to either transfer photos, connect as MTP. None of the other options worked either. I run also diagnostics tool on the phone to check if USB port works and in both charging and OTG connection with reverse plug works fine. Fastboot works, but due to the fact, PC doesn't see the phone, ADB hasn't hooked it up. Means, updating system via console is not an option, unless USB detectability will be restored...
Any ideas what to do to restore PC connectivity? Appreciate any guides how to resolve this issue. If similar problem has been already resolved, I would be thankful if someone would direct me there either on PM or below this post.
I tried to find help on miuipolska but they thrown away my post into the bin and said I'm lazy spammer, gave me penalty points, locked my account and said because of people like me their forum looks like trash... So yeah plenty of help from them....
Thanks in advance for your help.
windows/linux?
aIecxs said:
windows/linux?
Click to expand...
Click to collapse
Windows
connect the phone in mtp mode. open device manager, uninstall drivers. disconnect&reconnect phone in mtp mode (developer settings - usb config) and usb-debugging enabled. if drivers not installed automatically, download qualcomm_driver.zip or usb_driver_r12-windows.zip (try both)
Hi,
Thanks, I did already but re-did once again with your drivers, still nothing. In my opinion it looks like phone stuck on charge only mode, regardless what is selected as a default USB action. There is a chime when usb is plugged but nothing happened on both PC and phone ... Any other ideas?
adb works in any usb mode even in charging only. problem must be with drivers or physical connection. try usb 2.0 port on windows 7
I've tried on 2.0 & 3.0 nothing works. My last software change (when this issue occured) to global I did via otg. I thought (in that time) that's a software issue, and took it back to original ROM. Would that be possible (installing global software via OTG) if phone's USB would be broken?
i am confused about what's the current state of your device. is fastboot working or not? if fastboot available, why did you say you can't install TWRP? you know you can enter fastboot with vol dn + power?
i wouldn't say it's possible using OTG if usb connector is broken physical
if phone is charging and no yellow triangle in windows devices manager, this means drivers are installed. there is no pop-up on this device because of persist.sys.usb.config=none in /system/etc/prop.default which mean you have to re-select MTP in developer options each time AFTER you connected the phone, again
in TWRP there is adbd running (after decryption successful) and MTP should work too, but you need to install drivers again because each boot mode is announcing itself as new device
another reason for adb not working is power shell (windows 10) download latest platform-tools open C:\Windows\System32\cmd.exe cd into folder and run adb.exe from there instead
if you think the MIUI causes this issue i don't think this is a bug, more like maybe some unclean rollback/ mixed up ROM/firmware. in this case (as last option) i recommend to backup /data and /sdcard from twrp and start with a clean install. use the XiaoMi MiFlash tool it does not require adb for flashing
for the backup you can boot twrp from fastboot without flashing with "fastboot boot twrp.img" it will hopefully decrypt userdata (check if data is mounted and files readable) then backup userdata only. pictures and downloads not included in backup, you need to run "adb pull /sdcard" manually after this (and of course save TWRP backup to PC)
Hello,
I'm able to put phone into fastboot - the issue is, Pc doesn't see the phone in that mode - therefore I'm not able to load in TWRP. I had TWRP before, but after loading global software via OTG, TWRP gone. I have tried to plug phone and then swap MTP options - still doesn't work.
Phone is charging, and no prompt message comes in on computer - so as you wrote, no missing driver. However, I still cannot see phone connected to the PC.
I tried ADB as well, to detect the phone through fastboot devices option - nothing.
When I pressed power and vol+, then it brings up simplified ''TWRP'' with only 3 options:
-Reebot
-wipe data
-connect with miAssistant - that doesn't work either.
I wish to have TWRP, then my situation would be much easier regarding flashing/reflashing the phone.
Any other suggestions which could be helpful to crack this nut?
Appreciate your help.
does fastboot work for other device?
i did xiaomi mi9T last time on same ADB and worked well. I was able to put TWRP on it.
Today I tried again adb on mine (phone from thread), and still console doesn't see it.
After command 'adb devices' there is long long nothing, followed console comes back to first line, without giving back any connected devices...
something else came to my mind, byt I;m not able to verify it, due to fact I need this phone. If i put on global software, and when configure it back to what I wanted i restored copy of the device from cloud, which was done on custom ROM. Could that have any potential effect on this? Whole my problem started when I installed new update of custom ROM. then lost USB, started different things and voila, I'm here...
please don't mix up adb with fastboot. these are two different modes with different drivers. adb works only with usb-debugging enabled, fastboot only works while phone is in fastboot mode (oem unlocking may required, but no usb-debugging). regardless of what was previously working, you should double check fastboot with other device now. this will break down the issue is related to your pc or phone. found old post for solving fastboot driver problems fastboot.reg
you can check if adb sideload is working in stock recovery (and here again, you need to wait for the drivers installed, as in every new mode for the first time). connecting two times and adb kill-server is helpful sometimes. use usb 2.0 port only and open device manager to make sure you can see the device
{
"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"
}
yes, unclean rollback/ mixed up ROM/firmware can cause this. but assuming such a software problem, it will only affect to mtp/adb but not to fastboot mode
without fastboot you are left with OTG for now, not much you can do
Hi, I was able to manage few tests. PC, ADB and cable work with other devices.
On the one with problem, I've done again full wipe, then checked if Pc sees it, but no success. Then I brought back copy of the device from cloud and nothing. Still phone doesn't see the PC, so PC the Phone. Again, when phone is plugged to PC, there is only chime it has happened, and charging starts. Changing different types of USB function in dev options doesn't make any difference.
I'm not bale to load different software even via OTG, as I don't have option in update menu, to select zip package from drive location....
Any ideas what to try/do next ?
use the working phone to track down which usb controller in device manager is related to the physical usb port (hierarchical view like screenshot above) if your phone is in fastboot mode but not visible, but the working phone is, the problem is electrical contact (otherwise you should see something regardless of the driver is installed or not)
Dear marian85-85, did you finaly founded a solution ?
I received my new one with Miui 12.02 already upgraded and I get the same issue on OTG, it's only charging and no USB-OTG detected
Tried with all USB setting ON, with developer activated. No phone device recognized on computer (1 linux and 3 windows). 3 differents cables working on another phone, restore factory, MI-Suite... I think Miui 12. can block usb data..
Any news next ?
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.
{
"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"
}
This is what it looks like, and if I try to boot into recovery or system it just says "no operating OS found."
Windows won't recognize it when trying to connect via USB.
Any way to fix this? Help would be greatly appreciated.
DustyFukuyama said:
View attachment 5759871
This is what it looks like, and if I try to boot into recovery or system it just says "no operating OS found."
Windows won't recognize it when trying to connect via USB.
Any way to fix this? Help would be greatly appreciated.
Click to expand...
Click to collapse
It's in fastboot mode. Have you tried using a different cable to connect to the PC? It must be a USB data cable. Also, have you downloaded the Motorola driver's on your PC and the latest driver's for adb/fastboot from Google? Another option is if you have another phone and a OTG adapter
Yeedatoy said:
It's in fastboot mode. Have you tried using a different cable to connect to the PC? It must be a USB data cable. Also, have you downloaded the Motorola driver's on your PC and the latest driver's for adb/fastboot from Google? Another option is if you have another phone and a OTG adapter
Click to expand...
Click to collapse
fsr I can't install Motorola USB Driver. It always says "the parameter is incorrect" when I do it, and I've tried all kinds of solutions to fix it. I'll try install it on my friend's laptop tonight and see if I can fix it there.
Yeedatoy said:
It's in fastboot mode. Have you tried using a different cable to connect to the PC? It must be a USB data cable. Also, have you downloaded the Motorola driver's on your PC and the latest driver's for adb/fastboot from Google? Another option is if you have another phone and a OTG adapter
Click to expand...
Click to collapse
So I successfully installed the Universal ADB Driver and Motorola USB Driver on my other computer and it still won't recognize my phone while in the fastboot mode. Any idea why this is the case?
DustyFukuyama said:
So I successfully installed the Universal ADB Driver and Motorola USB Driver on my other computer and it still won't recognize my phone while in the fastboot mode. Any idea why this is the case?
Click to expand...
Click to collapse
Make sure to install these. They were updated. Then, go to device manager on your PC, click add new drivers and manually find the location of all new drivers and make sure they install. Make sure the phone isn't plugged into the PC when you do this. Reboot the pc. When it boots, plug the phone in but not in fastboot. See if it will get discovered in regular adb. If still nothing, click update drivers manually and the option to choose which. Go to Google adb, click install. Try again
DustyFukuyama said:
So I successfully installed the Universal ADB Driver and Motorola USB Driver on my other computer and it still won't recognize my phone while in the fastboot mode. Any idea why this is the case?
Click to expand...
Click to collapse
I forget you're stuck in fastboot. Can you get it to boot into recovery? It will just show a green android logo with it's stomach opened up and say invalid command or some ****. Hold power and press either volume up or down until you see a new screen that has several other options... That's recovery. From there you can enter fastbootd. See if the pc recognizes fastbootd if you can't get the above solution to work. Also, you can avoid all this driver crap if you have another phone and an otg cable. Download Bugjaeuger adb from Google play and you can use the second device as a replacement for the PC
Yeedatoy said:
I forget you're stuck in fastboot. Can you get it to boot into recovery? It will just show a green android logo with it's stomach opened up and say invalid command or some ****. Hold power and press either volume up or down until you see a new screen that has several other options... That's recovery. From there you can enter fastbootd. See if the pc recognizes fastbootd if you can't get the above solution to work. Also, you can avoid all this driver crap if you have another phone and an otg cable. Download Bugjaeuger adb from Google play and you can use the second device as a replacement for the PC
Click to expand...
Click to collapse
So I solved the problem last night. Apparently, it was the USB cable. My PC won't recognize my phone in fastboot mode using this particular cable fsr. I never thought it was the faulty cable because it was working fine in Recovery and OS prior to brick, just not in fastboot. Thanks for the help, I really appreciate it!
DustyFukuyama said:
So I solved the problem last night. Apparently, it was the USB cable. My PC won't recognize my phone in fastboot mode using this particular cable fsr. I never thought it was the faulty cable because it was working fine in Recovery and OS prior to brick, just not in fastboot. Thanks for the help, I really appreciate it!
Click to expand...
Click to collapse
That's Awesome! Isn't it such a great feeling when it finally works!? Lol. I've been a victim of the faulty/wrong cable situation many times. It's so frustrating I can't begin to explain it. I've had phones that were left inoperable for 6 months because I gave up, and then came back with a clear head and sure as hell, it ended up just needing a different cable, even though I had already tried 4 different ones. It makes me want to destroy things! Lol. Glad you got it running again!