ok. I'm tired so go easy on me. I'm running Windows 7 32bit. I have Dell PC Suite installed. I've got the full SDK installed. I've also got the R288920 drivers installed. I've been trying (since 3.00am) to get Fastboot to work and it would seem no matter what i do i just cannot. My Streak (Steve's 1.90) shows up in Device Manager as "Android ADB Interface". I've tried all 6 usb ports on my pc. I've tried Adb Composite. Adb Bootloader. Adb Interface and nothing works. I should also mention i had to do a clean install of Windows yesterday and prior to that Fastboot worked fine. I'm a semi-noob and i'm convinced that this is a driver problem. My question is this, can someone please tell me where i've gone wrong? As the man with the steering wheel down his pants said to the Doctor "this is driving me nuts".
Problem solved. Fastboot file was corrupted.
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
Hey Guy
I was trying to find a solution for the last 4 hours. I was running the Neutrino Rom before my display got a hardware error. Before I sent it back for warranty, I installed the original Motorola Firmware so the "unlocked" in the starting display is gone. Now I got my phone back and I wanted to unlock it again, because neither rooting nor installing a custom rom is possible. So I installed the drivers and the phone got recognized in normal mode. Furthermore I reboot it in RSD support mode and Windows 8 installed the SF Flash Olympus thing. I also can use fastboot. The only thing which doesnt recognize my phone is RSD lite so I couldnt find a way to unlock the bootloader. I also started in Admin mode and disabled the Windows User Control thing.... I changed the cable cuz I read it might be the cable. Still isnt working. As soon as I connect my phone in RSD support mode, Windows makes the sound of a connected device but still RSD won't recognize it. Don't know what to do. Is there another option?
I'm running on Android 2.3.4 (Build 4.5.2A-74_OLE-31.20)
It's german Telekom
I don't want to do another RSD Lite Thread but I tried every suggestion in all the other threads.
Thanks alot for your help
Tried on a XP Computer....Not working either...
Which version of RSD are you running?
- Remember to use a rear USB port just in case
- Download and install the latest USB drivers from Motorola. They can be found here: USB and PC Charging Drivers - Motorola Mobility, Inc. USA
- Download and install the latest RSD Lite as a computer Administrator (currently version 5.4.4) from here: RSDLite5.6
coolni said:
Hey Guy
I was trying to find a solution for the last 4 hours. I was running the Neutrino Rom before my display got a hardware error. Before I sent it back for warranty, I installed the original Motorola Firmware so the "unlocked" in the starting display is gone. Now I got my phone back and I wanted to unlock it again, because neither rooting nor installing a custom rom is possible. So I installed the drivers and the phone got recognized in normal mode. Furthermore I reboot it in RSD support mode and Windows 8 installed the SF Flash Olympus thing. I also can use fastboot. The only thing which doesnt recognize my phone is RSD lite so I couldnt find a way to unlock the bootloader. I also started in Admin mode and disabled the Windows User Control thing.... I changed the cable cuz I read it might be the cable. Still isnt working. As soon as I connect my phone in RSD support mode, Windows makes the sound of a connected device but still RSD won't recognize it. Don't know what to do. Is there another option?
I'm running on Android 2.3.4 (Build 4.5.2A-74_OLE-31.20)
It's german Telekom
I don't want to do another RSD Lite Thread but I tried every suggestion in all the other threads.
Thanks alot for your help
Click to expand...
Click to collapse
I couldn't get RSD Lite 5.6 to connect to my Atrix on Windows 8 either. I had to use a Windows 7 computer ( that has all the moto USB drivers installed on it ) to unlock my bootloader. Once you install the moto drivers, and you plug in the phone, you should see it installing usb drivers. If you turn on usb connection (from the notification bar USB options) to SDCard storage it will install more drivers. Then you can open the usb selection menu in the notification bar again and switch back to none. Finally got to Settings, Applications, Developer Options, and enable USB debugging which will install even more drivers.
Then firing up RSD Lite you should see it connect to your phone after that. I just couldn't get it to do it in Windows 8.
forget about it.....
you are locked after servicing your phone
no way to install anything ...
the strange thing is that after connecting the phone serviced
windows doesnt recognize the driver
but evrtyhin is fine with my other atrix 4g.
i dont know what they have done to the phone not even trying to load via sbf works.....
nothing
This may be an "old" issue, but i ran into a problem. I have tried every compatible driver for my phone and adb works fine. However, when i reboot into fastboot, the phone is not recognized.
I've tried changing the id of the usb drives and changing the drivers for my phone. I have a functioning adb and fastboot, but now that i've upgraded to 8.1, i can't fastboot flash anything.
Does anyone know of a solution for this on our DNA?
-DroidIsDNA- said:
This may be an "old" issue, but i ran into a problem. I have tried every compatible driver for my phone and adb works fine. However, when i reboot into fastboot, the phone is not recognized.
I've tried changing the id of the usb drives and changing the drivers for my phone. I have a functioning adb and fastboot, but now that i've upgraded to 8.1, i can't fastboot flash anything.
Does anyone know of a solution for this on our DNA?
Click to expand...
Click to collapse
Have a look at
http://forum.xda-developers.com/showthread.php?t=2521504
For whatever reason fastboot on my PC (win10) doesn't detect my phone, adb detects it fine when it's in recovery or booted normally, I cannot send fastboot commands as it says waiting for device. I've tried a few things like the LG Mobile Driver and a universal driver but it still isn't working. Any ideas?
Just to clarify I am in Fastboot mode when trying this.
Edit: Also tried the Google USB drivers from the SDK manager, didn't make a difference
I ended up simply doing it on an Ubuntu installation. Works perfectly on there, not sure why Win10 doesn't work though.
My problem is solved.