Related
My Atrix is recognized by my computer under normal circumstances and when it's in RSD. But it is not recognized when in fastboot mode; I have reinstalled drivers, reflashed sbf, and unlocked phone. The very first step of rooting keeps giving me "waiting for devices", because phone is not recognized by computer.
I've been stuck here for 2 days now, reading, researching and I have come up with nothing. Any help would be greatly appreciated.
Please list the steps you follow from beginning up till the point you get the "waiting for devices" message.
Are you booted into fastboot on the phone? Are you using the Android SDK fastboot implementation or moto-fastboot? Do you have fastboot in your PATH or have you cd'd into the directory where you've extracted the fastboot package?
Having a similar issue... not my first go around on this model. I have been unlocked and the whole 9 yards...
I went back to locked stock 4.5.91 (to make sure I still could) successfully. Today I went through the usual manual and auto unlock methods and RSD mode will not work. I have the most recent drivers from Motorola. I tried alternate usb cables... I have the Flash Interface driver installed (3.2.11).
I launch RSD protocol but nothing happens on my PC and RSD Lite does not show device info....
Could Motorola have done this recently? Or is there an older RSD driver someone can point me to to try? My current one is 5-2011.
EDIT: Fastboot no go as well.... not trying to hijack just may be the same problem... I am going to factory again and give it a second go... ADB Devices does not see the phone either
what worked for me at least was reboot computer, reinstall motodriver helper or whatever its called, and plug in phone. it will say on the bottom left "installing drivers", then "drivers succesfully installed". then do fastboot. sometimes even when you install motodrivers, windows does not recognize it so it has to say "installing drivers" at bottom right. then try fastboot. at least thats what worked for me.
Dell2 said:
My Atrix is recognized by my computer under normal circumstances and when it's in RSD. But it is not recognized when in fastboot mode; I have reinstalled drivers, reflashed sbf, and unlocked phone. The very first step of rooting keeps giving me "waiting for devices", because phone is not recognized by computer.
I've been stuck here for 2 days now, reading, researching and I have come up with nothing. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Not sure if it matters on the drivers..but i had the same issue yesterday. I had the "waiting for device" as well...
i had installed the wrong drivers. I had the 32 when i needed the 64. After installing the right ones..my device was recognized.
ethantarheels123 said:
what worked for me at least was reboot computer, reinstall motodriver helper or whatever its called, and plug in phone. it will say on the bottom left "installing drivers", then "drivers succesfully installed". then do fastboot. sometimes even when you install motodrivers, windows does not recognize it so it has to say "installing drivers" at bottom right. then try fastboot. at least thats what worked for me.
Click to expand...
Click to collapse
Tried that as well earlier... not sure where I am going at this point
defnow said:
Not sure if it matters on the drivers..but i had the same issue yesterday. I had the "waiting for device" as well...
i had installed the wrong drivers. I had the 32 when i needed the 64. After installing the right ones..my device was recognized.
Click to expand...
Click to collapse
Pretty sure I installed 64 but maybe I better double check...
I just started over completely, figured it out . Thanks for help guys, I can try out Alien3 now.
I confess my main problem was boneheadiness, I kept putting phone in fastboot mode(kinda sorta). When
fastboot came up I would connect phone to my computer, I never hit volume up to actually select fastboot.
I been kicking my computer for 2 days, I shudda kicked my dang self.
I am still stuck...
PC will not identify phone in RSD or fastboot. I have tried all drivers I can find, have uninstalled and reinstalled all software, the drivers install in each mode but RSD or the official moto software upgrade will not ID the phone when connected...
Anyone have an idea what to do? I have locked an unlocked this thing once before the 4.5.91 update and again after. I used the official Motorola Software Updater to "update" back to locked stock and have had this issue ever since then....
halfevildruid said:
I am still stuck...
PC will not identify phone in RSD or fastboot. I have tried all drivers I can find, have uninstalled and reinstalled all software, the drivers install in each mode but RSD or the official moto software upgrade will not ID the phone when connected...
Anyone have an idea what to do? I have locked an unlocked this thing once before the 4.5.91 update and again after. I used the official Motorola Software Updater to "update" back to locked stock and have had this issue ever since then....
Click to expand...
Click to collapse
Have you tried the moto-fastboot package?
mysticdrew said:
Have you tried the moto-fastboot package?
Click to expand...
Click to collapse
been reading about this, everything I read wants the img files and I have all sbf. Thing is I can not unlock my bootloader...
I was able to root through fastboot with no issues so it is ok, but I will be d*&$^d if I can get rsd running so I can unlock... it's not like this is new to me I have unlocked this thing twice before...
I just trying this to solve on my computer (Asus G51), but nothing I can do, reinstalling drivers, RSD Lite, nothing helped to solve this problem...so I went to another one computer (Acer) and I did it without any problem, install RSD Lite then drivers, unlock my bootloader at first time...I don't know where's the problem is, but I want know it
Wellall started when I was trying to install Cyanogen mod into my U20a, I started reading the wiki, installed ADB, and other stuff, my personal hell started when I had to unlock the bootloader for my device. I have read many threads about this but I haven't found answers for the the issue that I'm getting.
First of all:
Device: U20a
OS: Windows 7 32
The problem is that when I run s1tool following the instructions that I have found in other threads (turn off the device, press the 'do the job' button, press the back button and plugging the USB cable) I do not receive any outcome from the s1tool, (I have waited 3 minutes waiting for any outcome but nothing happens), I have searched in the xda forums but I have only archived to get more and more frustrated with the s1tool.
So here I am looking for some answers and guidance.
Thanks.
have you got the SEMC driver installed?
you can obtained it within SEUS or install gordon's gate (inside flashtool package).
maybe it can sort out your problem.
szl.kiev said:
have you got the SEMC driver installed?
you can obtained it within SEUS or install gordon's gate (inside flashtool package).
maybe it can sort out your problem.
Click to expand...
Click to collapse
I have already installed the last gordons gate avariable, maybe I should uninstal precious drivers and try again? If there is a way to do that.
Bumping for some help.
Vykromod said:
Bumping for some help.
Click to expand...
Click to collapse
i'm on e10i but,
something that could have happpend : "faulty" usb connection...
did you tried with other USBcable/PC ?
Try having a scout about in Windows Device manager for the semc drivers.
I had a small issue when I first tried s1tool, Holding the phones back key and plugging in kicked the phone into 'flash' mode as a USB device, but I didn't have the drivers installed. (PC companion was installed, but that only seemed to contain the drivers for the phone when it was in normal (non-flash) mode)
When I tried to update driver in device manager, after downloading the usb drivers, they wouldn't install. I simply uninstalled the flash usb device in device manager. (It'll show up when the phone is plugged in, in flash mode)
Once removed, unplug the phone and turn it off. re-start by holding back key and plugging back in. Windows re-detected it and the second time around, installed the usb drivers.
Hope this helps
I also had the same problem.
I installed Gordon drivers from flashtool.. but still not able to detect the phone in flash mode.
me too, same problem
Windows XP
SE X8
nothing comes out even new verion s1tool use
Hello,
This must be a dumb question because all the guides seem to skip over this part but I'm having trouble installing the Windows 7 drivers. I downloaded the drivers, connected via USB, right clicked on the Android 1.0 in the device manager and updated the drivers. Everything seemed fine. Then I boot into fastboot and get a "Drivers were not installed successfully" pop-up.
I thought maybe I messed up and was supposed to install the drivers while in fastboot rather than while the phone was all the way booted up. So I rebooted the phone, uninstalled the drivers, booted in fastboot and tried to install the drivers while in fastboot. When I try it this way I right click on Android 1.0 in the device manager, go to the update driver option, select my file (there are two files in the driver folder I downloaded, androidusb and htcrndis, I tried them both) and I get an error before it can finish installing the driver. It says:
Windows found driver software for your device but encountered an error when trying to install it:
HTC Remote NDIS based Device
This device cannot start. (Code 10)
I'm sure it's something simple but I cant figure it out. Thanks for any help.
Sorry if I'm being a noob here but I seem to be unable to install fastboot drivers. I've tried pointing driver installation to the usb folder I've downloaded and unzipped but in device manager the device just appears for a few seconds then goes off. I tried using flashtool and installing the drivers from the drivers section, as it told me but even though I completed the installation a couple of times it still tells me everytime I try to enter fastboot in flashtool that the drivers are required and that they can be found in the drivers folder and I'm getting a bit of tired of this. I can't root, unlock bootloader or do anything worthwhile without the fastboot drivers it seems.
Sorry again if I'm being noob I came from a galaxy ace and over there it was a lot simpler and the process of rooting, installing CWM and flashing a ROM did not even warrant the use of a computer so I'm pretty confused.
jleonnn said:
Sorry if I'm being a noob here but I seem to be unable to install fastboot drivers. I've tried pointing driver installation to the usb folder I've downloaded and unzipped but in device manager the device just appears for a few seconds then goes off. I tried using flashtool and installing the drivers from the drivers section, as it told me but even though I completed the installation a couple of times it still tells me everytime I try to enter fastboot in flashtool that the drivers are required and that they can be found in the drivers folder and I'm getting a bit of tired of this. I can't root, unlock bootloader or do anything worthwhile without the fastboot drivers it seems.
Sorry again if I'm being noob I came from a galaxy ace and over there it was a lot simpler and the process of rooting, installing CWM and flashing a ROM did not even warrant the use of a computer so I'm pretty confused.
Click to expand...
Click to collapse
first check whether you checked the fastboot and flashtool drivers and installed.............if yes then try restarting your PC and then try again....... The problem u mentioned happens a lot(it happens to me)...... just be patience.......
Also try toggling between mtp and msc mode.
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
It's possible that your operating system (Windows 7 or 8) is preventing unsigned drivers to install. I've had the same issue and I could install the drivers successfully after disabling "Driver Signature Enforcement" on your Windows operating system. Reboot your PC and press F8 while booting. Then select " Disable Driver Signature Enforcement". Then install the unsigned driver.
Canalope86 said:
It's possible that your operating system (Windows 7 or 8) is preventing unsigned drivers to install. I've had the same issue and I could install the drivers successfully after disabling "Driver Signature Enforcement" on your Windows operating system. Reboot your PC and press F8 while booting. Then select " Disable Driver Signature Enforcement". Then install the unsigned driver.
Click to expand...
Click to collapse
Thanks. If that's the case I think I'll try it on my older Windows XP com.
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Luinwethion said:
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Click to expand...
Click to collapse
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
ante0 said:
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
Click to expand...
Click to collapse
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Luinwethion said:
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Click to expand...
Click to collapse
I ran into this also and I un-installed HiSuite, then re-installed it and after that in device manager set up drivers as seen in screen copy in attachement.
I also refer to this page for more info: https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
Luinwethion said:
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
Click to expand...
Click to collapse
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
AntoRei said:
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
Click to expand...
Click to collapse
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Luinwethion said:
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Click to expand...
Click to collapse
You can use this guide with linux?
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814