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
Related
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
DeviceSettings said:
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
Click to expand...
Click to collapse
I'm not sure what's happening with your computer not seeing the phone, but if you have a microsd adaptor you could get a stock RUU onto your card and flash back to stock.
Edit: or just your boot.img. If you can get into hboot you're not bricked.
Part fix
As previous poster said, put a PH...IMG with boot on it and you'll be able to boot up again. Yours is third phone reported here with USB problem after failed S-0ff.
I can boot my rom, but no radio or wifi, No charging, and no computer can see it for fastboot. Hoping for cure soon.
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Same thing happened to me. I just finished uninstalling HTC Sync and Android SDk, then reinstalled both. Now the drivers are working properly, and computer sees my phone again. This should help.
***edit: this process helped with my computer finding software drivers to connect phone to computer. Before- "Windows could not find drivers for Android device" (device manager in windows)
I could never get it to work in the first place. Cleanflash finds and flashes to it just fine but the s off just can't see my phone once it reboots.
Sent from my ADR6425LVW using XDA
DeviceSettings said:
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Click to expand...
Click to collapse
If the phone is rebooting to the screen with the arrow when you press power to enter fastboot then try going to recovery, your regular recovery will probably not show up but another stock hboot menu will. Then try selecting fastboot there and see if you can run fastboot commands without rebooting to arrow screen.
Sent from my HTC Vigor
Success getting it to reboot with the boot.img from the rom I was running....But unfortunately the usb is fried. Can not charge the phone or connect to a computer. So I guess that is another potential risk with using this method.
Ouuuuch :/
Sent from my ADR6425LVW using xda premium
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
DeviceSettings said:
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
Click to expand...
Click to collapse
Warranty!
(edit: kidding, no need for a ****storm)
I'm trying to reset my atrix because of warranty issues. I tried everything so far I could find but RSD 6.1.4 wont recognize my Atrix. I installed the newest drivers, and I've tried different usb ports, run as admin.... Everything won t work for me. Whenever I boot in fastboot and use "moto-fastboot devices", my phone will show up. It s just not working with rsd
I'm running WIN8 64-bit (might be the problem?)
Have no idea what else to try
coolni said:
I'm trying to reset my atrix because of warranty issues. I tried everything so far I could find but RSD 6.1.4 wont recognize my Atrix. I installed the newest drivers, and I've tried different usb ports, run as admin.... Everything won t work for me. Whenever I boot in fastboot and use "moto-fastboot devices", my phone will show up. It s just not working with rsd
I'm running WIN8 64-bit (might be the problem?)
Have no idea what else to try
Click to expand...
Click to collapse
Probably yes I too have WIN8 and to get working drivers I used some program to disassemble driver and install it manually but in my case fastboot doesn't work too, but it can bee new atrix series where is blocked rsd. And does you put phone in rds mode
I bought my One with bootloader unlocked but the guy who sold me the phone unrooted the phone before shipping and i've tried to follow the rooting and the unlocking bootloader through fastboot methods but every time i open sdk manager it just says i have to update, i update then it says restart, and no mater what i do, cmd just keeps telling me fastboot is not a recognized command... blah blah... short question is, is there a rooting app i can purchase or if anyone can give me a helping hand?
Edit: I have followed the steps exactly, switched off fastboot in power menu, and powered off entered fastboot from bootloader, plugged in device, entered cmd and tried it but i get the aforementioned error.
Edit 2: I made the folder and placed my files and it seemed to go a little smoothly but it says waiting on device and just hangs there. The computer is still not recognizing the phone, i still get USB not recognized. try reconnecting the device....
Oh also, trying to install a recovery to this, so i can root... but just an easy way
Please help me, someone... the bootloader says unlocked btw. but fastboot does nothing when trying to flash via cmd.
if you are running windows 8 you may need to install the correct drivers, i had the same problem when i tried to root my M7 and im runinng windows 8, if youd like the drivers, PM me i cant remember where i got them from, but i have them still. Also if you can try switching USB ports, i had to use a different one and everything went kinda smooth after that.
sakumaxp said:
if you are running windows 8 you may need to install the correct drivers, i had the same problem when i tried to root my M7 and im runinng windows 8, if youd like the drivers, PM me i cant remember where i got them from, but i have them still. Also if you can try switching USB ports, i had to use a different one and everything went kinda smooth after that.
Click to expand...
Click to collapse
I sent you a pm... i am on win8, and i don't think its the ports because when the phone is fully on, it i can open it through windows, its just it doesn't work when it's in bootloader/fastboot
HyDRo1X said:
I sent you a pm... i am on win8, and i don't think its the ports because when the phone is fully on, it i can open it through windows, its just it doesn't work when it's in bootloader/fastboot
Click to expand...
Click to collapse
ok i switched to a win8 an everything seemed fine, but i get a long list of processing cmd after i type the fastboot flash recovery... and then continued as followed but nothing... still get red triangle
Ok got it... Windows 8 problems
Sent from my HTC One using xda premium
So I have run into a problem with my HTC Evo 4G LTE. I rooted a while back but I decided that I didn't really like the roms that would actually work, and so I tried doing an RUU to get back to stock. What ended up happening was that my phone is now S-ON but it says Unlocked and Tampered. but the custom recovery is still there so I can actually do updates to my phone. I have tried to re-root so I can try the RUU again but for some reason I can't get my phone to be recognized by fastboot or the adb. I don't know if its because I have incorrect drivers or what the issue is. Whenever I try to open ADB it just runs through a block of text and closes instantly, same for fastboot. I don't know anymore which instructions or methods to follow since I don't know what exactly the problem is. I've tried looking on here for issues like mine but I can't seem to figure it out. I just want to get my phone as close to stock as possible but I am seriously stuck right now and I need serious help. I would really appreciate it.
Open the cmd window from your android-sdk/platform tools folder
bigdaddy619 said:
Open the cmd window from your android-sdk/platform tools folder
Click to expand...
Click to collapse
I've done that but I don't know what exactly it is I'm supposed to do once I do that. Like how do I get back to fully stock? Or should I be trying to re-root to RUU again? Moonshine doesn't recognize my device in fastboot usb, it says something like usb device not recognized because of a malfunction. I'm sorry for being clueless but I'm at a loss at what to do.
DashEndar said:
I've done that but I don't know what exactly it is I'm supposed to do once I do that. Like how do I get back to fully stock? Or should I be trying to re-root to RUU again? Moonshine doesn't recognize my device in fastboot usb, it says something like usb device not recognized because of a malfunction. I'm sorry for being clueless but I'm at a loss at what to do.
Click to expand...
Click to collapse
Uninstall everything HTC from your PC then reboot
Unplug your phone then install the latest drivers from HERE the ones dated 6/6/13
Plug phone in and let the drivers install
They might install while in bootloader and custom recovery also
then give moonshine another try
Should I only install the drivers or install HTC Sync as well?
DashEndar said:
Should I only install the drivers or install HTC Sync as well?
Click to expand...
Click to collapse
Moonshine won't work if HTC Sync is installed
bigdaddy619 said:
Moonshine won't work if HTC Sync is installed
Click to expand...
Click to collapse
Ok, I'm going to give this a try and see how it goes. Thanks for responding.
DashEndar said:
Ok, I'm going to give this a try and see how it goes. Thanks for responding.
Click to expand...
Click to collapse
No worries good luck
DashEndar said:
Ok, I'm going to give this a try and see how it goes. Thanks for responding.
Click to expand...
Click to collapse
So I uninstalled all the drivers and everything HTC and restarted. I then tried to install that driver from your link. It said the driver wasn't supported by my operating system which is Windows 8 64 bit and then finished installing. When I plugged in my phone it didn't seem like anything installed. The EVO is recognized by computer as a media device I guess. I switched the usb mode to mount as disk drive and it seemed to install a driver. Then I ran moonshine again but when it went into the bootloader, again it said the USB device was not recognized.
DashEndar said:
So I uninstalled all the drivers and everything HTC and restarted. I then tried to install that driver from your link. It said the driver wasn't supported by my operating system which is Windows 8 64 bit and then finished installing. When I plugged in my phone it didn't seem like anything installed. The EVO is recognized by computer as a media device I guess. I switched the usb mode to mount as disk drive and it seemed to install a driver. Then I ran moonshine again but when it went into the bootloader, again it said the USB device was not recognized.
Click to expand...
Click to collapse
Hmmm not really sure then I have been away from the Evo for a while
Try this
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
bigdaddy619 said:
Hmmm not really sure then I have been away from the Evo for a while
Try this
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Click to expand...
Click to collapse
Trying what you say and everytime I select MyHTC it says it installs, then just disconnects and reconnects again saying usb device not recognized.
DashEndar said:
Trying what you say and everytime I select MyHTC it says it installs, then just disconnects and reconnects again saying usb device not recognized.
Click to expand...
Click to collapse
Hmmm sorry I'm kinda out of ideas
Anyone else with any idea what is going on here with my phone?
Uninstall everything HTC (again). Download and install HTC Sync Manager. Once install is complete, uninstall only HTC Sync Manager. The latest HTC Drivers will remain installed. Put your device into fastboot mode, and connect to the PC. Drivers should install, and the bootloader should go from saying FASTBOOT to FASTBOOT USB.
Captain_Throwback said:
Uninstall everything HTC (again). Download and install HTC Sync Manager. Once install is complete, uninstall only HTC Sync Manager. The latest HTC Drivers will remain installed. Put your device into fastboot mode, and connect to the PC. Drivers should install, and the bootloader should go from saying FASTBOOT to FASTBOOT USB.
Click to expand...
Click to collapse
I just tried this, plugged it in and it still says the message of USB device not recognized. I'm really not understanding what happened as to why the fastboot is just not recognizing the drivers. I also noticed the word fastboot in red changes to fastboot usb when I move the selection down from bootloader to any of the other options. Is it supposed to do that?
DashEndar said:
I just tried this, plugged it in and it still says the message of USB device not recognized. I'm really not understanding what happened as to why the fastboot is just not recognizing the drivers. I also noticed the word fastboot in red changes to fastboot usb when I move the selection down from bootloader to any of the other options. Is it supposed to do that?
Click to expand...
Click to collapse
I think your issue may be with your computer. Do you have another computer you could try this on? I personally have never used windows 8, but it is always something that could be an issue.
DashEndar said:
I just tried this, plugged it in and it still says the message of USB device not recognized. I'm really not understanding what happened as to why the fastboot is just not recognizing the drivers. I also noticed the word fastboot in red changes to fastboot usb when I move the selection down from bootloader to any of the other options. Is it supposed to do that?
Click to expand...
Click to collapse
Yes, when you're connected to your computer via fastboot it will say "Fastboot USB". Don't worry about the message on your computer-I get them all the time and I can still run commands via ADB & fastboot without any problems.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Yes, when you're connected to your computer via fastboot it will say "Fastboot USB". Don't worry about the message on your computer-I get them all the time and I can still run commands via ADB & fastboot without any problems.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
But in Moonshine when it loads fastboot it doesn't work, it just times out. It finds the device and restarts it, but after it gets into the bootloader it fails. That is what I'm trying to figure out.
When you connect in fastboot USB mode, what happens when you run the command "fastboot devices" (without quotations)?
Sent from my HTC EVO 4G LTE
Well being that I can't open fastboot like normal because it just flashes and closes, I open a command window inside my platform-tools folder. Then I do the command fastboot shell and it says <waiting for device> and nothing happens. If i open the window and type adb devices it shows my phone's serial number, but fastboot devices or fastboot shell, nothing happens
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Darrian said:
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Click to expand...
Click to collapse
There is none. The only safe way to root is to flash TWRP in fastboot. Right now, you can try to force update through update.app
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Darrian said:
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Click to expand...
Click to collapse
Oh. But like I said, there is none.
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Darrian said:
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Click to expand...
Click to collapse
Have you tried changing the drivers.?
Yes
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Darrian said:
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Click to expand...
Click to collapse
Glad you fixed it. :highfive: