Database Info

[Q] Mount USB storage under ClockWorkmod Recovery 6.0.1.0

Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max

Use this guide to recover your device.

Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.

How did you erase everything? Was it through fastboot or CWM?

I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.

maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...

maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2

*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2

The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?

Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2

Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307

I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2

AP Fastboot Flash Mode not being detected on pc

I've searched the whole sight and tried a bunch of so called fixes and still when i plug in my atrix 2 in boot mode (only it boot mode it does this) all i hear is instead of the dehdo that lets u know its connected i hear duhduhduh and RSD doesnt detect my device... im trying to fxz to 2.3.5 then ota upto ICS then root but i cant do any of these because of this please help.

greatanomaly said:
I've searched the whole sight and tried a bunch of so called fixes and still when i plug in my atrix 2 in boot mode (only it boot mode it does this) all i hear is instead of the dehdo that lets u know its connected i hear duhduhduh and RSD doesnt detect my device... im trying to fxz to 2.3.5 then ota upto ICS then root but i cant do any of these because of this please help.
Click to expand...
Click to collapse
First and foremost, this belongs in the q&a section. Is your phone an MB865, an ME865, is it AT&T branded? Have you tried uninstalling then reinstalling the Motorola drivers on your PC? Tried a different USB port and/or another PC? Can you give a little more information? Awesome sound effects, by the way.lol
Sent from this thing.

1BadWolf said:
First and foremost, this belongs in the q&a section. Is your phone an MB865, an ME865, is it AT&T branded? Have you tried uninstalling then reinstalling the Motorola drivers on your PC? Tried a different USB port and/or another PC? Can you give a little more information? Awesome sound effects, by the way.lol
Sent from this thing.
Click to expand...
Click to collapse
thank u lol but im sure u can imagnine the sound an...
AT&T
MB865
and i do believe i said ive tried nearly everything that is listed on this site well other sites to...
I dont need special files for my special model phone or the fact that its at&t but if that information helps u make it connect to my pc like it does when its not in fastboot then there ya go and btw to the Q/A section they can move it...

greatanomaly said:
thank u lol but im sure u can imagnine the sound an...
AT&T
MB865
and i do believe i said ive tried nearly everything that is listed on this site well other sites to...
I dont need special files for my special model phone or the fact that its at&t but if that information helps u make it connect to my pc like it does when its not in fastboot then there ya go and btw to the Q/A section they can move it...
Click to expand...
Click to collapse
Yeah, I was kidding. This site can be too serious at times. I know you said you tried everything, but a lot of people say that and it isn't always true, especially when they ask questions on the same day they became a member. I wasn't trying to offend you or insinuate anything. I asked if you had an AT&T branded phone because I was curious as to why you wanted to flash to 2.3.5 then ota to 2.3.6 then ota again to 4.0.4 instead of using this:
http://forum.xda-developers.com/showthread.php?t=1961310
to go straight to 4.0.4?
So your PC isn't detecting your phone, but ONLY when in fastboot mode, correct? Is the phone detecting the PC? By that I mean, on my phone when I boot into fastboot mode, at first it says:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Connect USB
Data Cable
Then when I connect it to the PC it changes to:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Transfer Mode:
USB Connected
Are you at least getting that?
Sent from this thing.

stuck on boot logo
1BadWolf said:
Yeah, I was kidding. This site can be too serious at times. I know you said you tried everything, but a lot of people say that and it isn't always true, especially when they ask questions on the same day they became a member. I wasn't trying to offend you or insinuate anything. I asked if you had an AT&T branded phone because I was curious as to why you wanted to flash to 2.3.5 then ota to 2.3.6 then ota again to 4.0.4 instead of using this:
http://forum.xda-developers.com/showthread.php?t=1961310
to go straight to 4.0.4?
So your PC isn't detecting your phone, but ONLY when in fastboot mode, correct? Is the phone detecting the PC? By that I mean, on my phone when I boot into fastboot mode, at first it says:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Connect USB
Data Cable
Then when I connect it to the PC it changes to:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Transfer Mode:
USB Connected
Are you at least getting that?
Sent from this thing.
Click to expand...
Click to collapse
no sir ny fone is not showing this
it still says
Connect Usb
data cable
i stuck while i was on jbleak 4.1.2 and through SD card i flashed CM 10.1
once it worked but now it stucked on the boot logo ... it appears and gone ... and then shows black screen.
even in recovery when i tried to reinstall same zip file of CM10.1 it failed on signature verification.
please help me sir help me..!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying:

Gr8mobiPro said:
no sir ny fone is not showing this
it still says
Connect Usb
data cable
i stuck while i was on jbleak 4.1.2 and through SD card i flashed CM 10.1
once it worked but now it stucked on the boot logo ... it appears and gone ... and then shows black screen.
even in recovery when i tried to reinstall same zip file of CM10.1 it failed on signature verification.
please help me sir help me..!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Chill man..nothing to worry about..please install motorola drivers..it should work.

its still not working
nishant203 said:
Chill man..nothing to worry about..please install motorola drivers..it should work.
Click to expand...
Click to collapse
wot motorola driver ..?? i have installed moto device manager and it is not showing any thing connected.. because it remain in boot mode..:crying::crying::crying::crying::crying::crying::crying:

Use Virtual PC
I still have the same issue. I have installed Windows 7 on VM Ware workstation i.e virtual desktop and then followed the below steps :-
-Reboot your Virtual PC
-Install Motorola drivers.
-Reboot your computer
-Install RSD Lite
-Reboot your computer
-Boot your phone into Fastboot mode
-Connect your phone to your computer using a high-quality (preferably OEM) cable.
-Let your PC install any necessary drivers. When it finishes it should tell you that the device "Fastboot Edison S" is ready for use.
-Turn your phone off, disconnect the cable
-Reboot your computer
-Boot your phone back into Fastboot mode
-Wait a couple seconds then connect your phone to your computer
-Wait a couple more seconds, then look at the bottom text that's displayed on your phone. It should say
This means that your phone is connected to your computer.
-Open up RSD Lite
-Wait a couple seconds. At the top of the list should be your phone (under model it should say "Fastboot Edison S")
-If you've done all this and everything has worked out for you, flash the fxz! Make sure to follow the instructions in the noob thread as specifically as possible

Gr8mobiPro said:
wot motorola driver ..?? i have installed moto device manager and it is not showing any thing connected.. because it remain in boot mode..:crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
This seems to be happening more lately. it IS a driver issue of some sort, that is for sure. I would just use one of the scripts, or moto-fastboot manually. they do the same thing as rsd but through command line either with your own typing, or a .bat script.
This may also work better in linux, so you can try downloading a live cd/usb of ubuntu and seeing if it is recognized. no need for drives with linux, just download one of the scripts that includes the moto-fastboot utility. Let me know if you need more help.

same issue
i am having the same issue with my at&t atrix 2. it is soft bricked due to an upgrade from gb to jbleak. ap fastboot flash mode (s) oa.65 battery ok ok to program connect usb data cable same message i have installed different motorola usb driver versions. i have also soldered the 4 pin to the 1 red+5v factory usb cable
https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNE6DkvEZi41YPAYKVPqH_AlA4f4cQ
but still my pc says unable to recognize usb device. i dnt what to do any more. im in mexico and purchasing a new phone is very expensive i need help is there something any one can do i am sure my device is not completely bricked i just cant get the mofokin pc to recognize the mofokin phone in fastboot

[Q] Xoom won't boot

So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Update: I've been trying different cables. I found one where the computers will see that a devices is connected, but am getting "USB device not recognized" with either set of drivers that I have on both computers. Making progress, but could still use some help.

DiGi760 said:
So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Click to expand...
Click to collapse
I had a problem similar to that about a year ago, somewhere in these forums was the suggestion to remove the SD card and then do a factory reset, it worked for me. My xoom just stopped working, I thought at first it was a flat battery but after charging the symptoms were the same as yours, might be worth searching through the forums if you haven't already

There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?

DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
Sorry can't help , mine is just over 2 years old and except for that one problem have never had any issues so have never needed to even connect it to a PC

DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
I recently discovered these handy files when I needed to return to stock:
4G Xoom (MZ600) Restore
3G Xoom (MZ601/3) Restore
WiFi Xoom (MZ604) Restore
If you need to find out which Xoom model it is, power on whilst holding the volume down button, this will take you in to fastboot. Then (you sound like you'd know how do this, PM me if you don't) use "fastboot getvar all". This will return the model.
Unzip the file above, there's a batch file in there which will install the drivers, then fastboot the firmware over.
If you boot to fastboot, then run the batch file, it installs the drivers, then "adb device", then it asks if your device is connected - it won't show up cos it's in fastboot. Just ignore that and say yes, and it'll start flashing the files.
Sorry if I'm too late - don't visit these boards much these days. Good luck, let me know if this works.

Thanks for giving me something to try. I uninstalled the moto drivers I had and installed the ones included in the zip file and restarted my computers. The Windows 8 computer never recognizes that the xoom is connected in any mode. The 7 machine does see it in fastboot mode but as a "fastboot" device for which it fails to find drivers. When I run fastboot getvar all, all I get is <waiting for device>.
I do know that this is a wifi only (mz604) xoom. Thanks for the image files. If I can get this stupid thing to communicate with a computer, I think I'll be in business.

In fastboot mode (vol -) it won't acknowledge that it's connected. Just fastboot your image over and it will work.

If I try to do anything with fastboot, it just says "< waiting for device >". Fastboot doesn't see a device to flash to.

OK, it's either your cable or your driver. Many cables are for charging only, and have no data lines. I throw those away.
As to drivers, I'm Debian for 15 years so can't advise on Winduhs.
Oh, one more thing: I've noticed that on my old HP laptop I had to use a certain USB port, or else it wouldn't comm with my phone for fundamental actions like loading new firmware.

These were the drivers I used: https://motorola-global-portal.cust...sion/L3RpbWUvMTM4NjM1MjA0NC9zaWQvWEo3SWU5SGw=
They don't seem to be windows 8 certified though.
Sent from my Nexus 5 using Tapatalk

We finally got it. We used DriverEasy to look for drivers because we have a bunch of extra licenses and the drivers we had obviously weren't working. DriverEasy was able to install an "Android Bootloader" driver that must not be part of the SDK. Once that was installed, I was able to use fastboot to flash the images from above. The device is in good working order again and fully updated.
Thanks for all your help.

Always nice to hit the Thanks button for those who've helped.

[Q] LG-P506 Fastboot Can See My Device But Won't Show The Serial Number

So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.

baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.

damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.

baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.

shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.

ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.

baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk

ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.

LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >

[Q] XT926 issue - waiting for device

Phone: Droid Razr HD XT926, locked bootloader, was rooted, not sure now
Issue: OTAs had not worked for awhile, but I wanted to go to KitKat. So, I tried to use Matt's 1.41 utility. I may not have had the most up-to-date Motorola USB drivers when I started. The update did not work. Now, I just get the "Motorola Logo and Dual Core Technology text", but phone then goes black. I am able to get to AP fastboot screen, but all attempts to re-try Matt's 1.41 utility, or the House of Moto 4.1, or RSD Lite 6.2.4 are unsuccessful. All of them show <waiting for device>.
Any ideas why I can't get past <waiting for device>?
Fastboot screen:
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected

Assuming you've updated the drivers at this point, are using the stock usb cord and following all the details in the op to a T? Might try another USB port...

grnsl2 said:
Assuming you've updated the drivers at this point, are using the stock usb cord and following all the details in the op to a T? Might try another USB port...
Click to expand...
Click to collapse
You are correct on those assumptions except the stock usb cord. The cord I am using was fine when I first started my adventure. USB debugging was on and plugging in the phone+cord caused PC to recognize the phone. But, now my PC does not even flinch when I plug the phone+cord into the USB port. Should the PC be flinching (recognizing the phone) when all are plugged in? If it is not, any recommended tricks to encourage PC and phone to play nice together?
I have tried two different ports. I will check documentation and verify they are 2.0. I will also see about finding a motorola OEM cable just to rule that out.
Thanks for the response!

Additional info:
- Motorola USB drivers I used (USB Driver.6.4.0.2014-10-24): [droidrzr website] /index.php/topic/57858-motorola-tools-rsd-lite-usb-driver/

I used to do a lot of flashing from various laptops to different phones with mixed results. Certainly strange when sometimes one works and the other does not. Hard to pinpoint why with so many variables. In your situation, working at one point then bam...

grnsl2 said:
I used to do a lot of flashing from various laptops to different phones with mixed results. Certainly strange when sometimes one works and the other does not. Hard to pinpoint why with so many variables. In your situation, working at one point then bam...
Click to expand...
Click to collapse
Update: Decided to give it another shot today. Went back to original cord (when I had success prior to bad flash). Booted to fastboot. Plugged into USB port. Today, my PC decided to try and recognize it! Windows failed once trying to find drivers for "Fastboot VANQUISH S". So, I decided to disconnect and try again. This time, drivers found! Fastboot screen changed to include the "usb connected" message below the "Fastboot Reason: Boot menu selected" message.
Using House Of Moto, I was able to successfully flash 4.4.2 183.46.10. Phone is charging up now in preparation for rooting and unlocking.

Good news there!