Database Develop

Unable to flash ANYTHING please help!

I keep on trying to flash ANYTHING to my bionic(stuck in ap fastboot with boot failure) and every time I go to flash something it keeps on shifting to "FAILED<remote: battery low>
I am at my wits end, I tried the fxz, and it failed, I tried the r3l3as3droot fix and it fails.... Can someone PLEASE help soon?

You've got to charge the battery. There are ways to do it by cutting off the end of a spare usb cable, and you can find that here somewhere.... I just don't remember where.

Try flashing via RSD lite. See if that works.
http://rootzwiki.com/topic/13105-a-easier-way-back-to-the-update-path/
Sent using xda premium

RSD fails almost immediately. I dont knwo what else to do. I think I officially bricked myself.

htcdesirezgeorge said:
RSD fails almost immediately. I dont knwo what else to do. I think I officially bricked myself.
Click to expand...
Click to collapse
Did you even read sreven.rn's post. You need to charge your battery. Fastboot/rsd will do nothing until you get that battery charged.

This post has the answer you seek
http://www.droidforums.net/forum/droid-x-tech-support/189467-need-help-dead-battery-trick.html
Sent from my DROID BIONIC using xda premium

That is a great tip dellenrules! I'll have to keep this one in mind.

Anyone know if the battery will charge in this FlashBoot mode?
I am on Battery Low, can't boot to phone screwed myself earlier with all the flashing. Not stuck at Flash Failed, can't RSD, can't flash via Flashboot because of low battery.
Wonder if I leave it there will it charge

smilepak said:
Anyone know if the battery will charge in this FlashBoot mode?
I am on Battery Low, can't boot to phone screwed myself earlier with all the flashing. Not stuck at Flash Failed, can't RSD, can't flash via Flashboot because of low battery.
Wonder if I leave it there will it charge
Click to expand...
Click to collapse
I'm 99% positive it will not charge in fastboot mode.

Crap. Was there like a USB hack somewhere that will get this to work? I can't remember. I am screwed!

HOW TO FIX A TOTALLY BRICKED BIONIC (& HOW TO McGUYVER CHARGE A DEAD BATTERY too)
I have prepared an uber zip file that contains all you need.
Wish I had it last night! I was up until 3am, worked on this for about 6 hours, and then this finally worked. I tried everything. fastboot, one click this, sd lite, etc. none of it worked.
You will praise me.
this worked - Got my phone back!
of course, I tried every solution in the world and was profoundly frustrated for hours and ran out of battery. but this WORKED. NOTHING else did.
I also had to do the McGuyver thing with an old blackberry usb charger.
snip the end off, strip the red and black wires, insert the red to positive on your battery (battery out of the phone!) insert black to negative, THEN plug in the charger. let it go for at least 1/2 hour.
my uper zip file - UNZIP THIS file to a FOLDER on YOUR DESKTOP.
http://dl.dropbox.com/u/12759680/fastboot.zip
also Manually copy files (update893 and update901) to your SD card!!!!!
(take out the micro sd, load the files onto it using an adapter.)
1. Put phone in Fastboot mode, connect to computer [hopefully you have the drivers installed. if not, search for Motorola_End_User_Driver_Installation_5.2.0_32bit or the 64 bit if that's your operating system
whenever there is a command, I copied it and pasted it in the command window (ctrl v does not work to paste, you must right click and then paste) dont copy the friggin quotation marks
2. Open a command terminal and go to the Stock folder ("cd C:\Documents and Settings\YOUR NAME\Desktop\fastboot")
3) type these commands in the terminal window and wait for the flashing to finish before going to the next line.
----> "moto-fastboot.exe flash webtop grfs.img" (This file will be flashed in 4 parts)
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
Then reboot into stock recovery (volume up+down and power; then select recovery then volume up)
When in recovery, hit both volume up+down, then go to wipe data
then flash update893.zip
If you come upon the triangle with the exclamation point and the android man, dont freak out, hit the power button, down volume, both volume at once, and eventually you will be in recovery.
you will so do a dance.
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
wait a day. then, If you're feeling adventurous, reboot into stock recovery and flash 901!
I'm no maven, but I got my phone back and then to 901.
havent rooted again but I'm waiting for the developers to catch up to 901, which I downloaded and flashed after getting the damn phone back.

No dice for me
failed at flashing Web Top Frfs.img
Load_file: could not allocate xxxx
Pass preinstall.img
Failed system.img
Writing system .... INFOPreflash Validation Failure
FAILED (remote: )
Reboot phone...
Invalid Flash mode (s) (Boot Failed)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG Version (CG: boot)
is where I am at now

finally got these two installed
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
once reboot, did wipe cache and wipe data
update 893, failed during verify data....
crap..

Ok, here is the deal. It is IMPOSSIBLE to revive your phone from the process that I did. UNDER NO CIRCUMSTANCES SHOULD YOU FLASH 5.5.901 AND THEN DO A FACTORY RESTORE OR RECOVER IN TO A CUSTOM ROM. DO NOT ATTEMPT OR YOU WILL IRREPARABLE BRICK YOUR PHONE!

htcdesirezgeorge said:
Ok, here is the deal. It is IMPOSSIBLE to revive your phone from the process that I did. UNDER NO CIRCUMSTANCES SHOULD YOU FLASH 5.5.901 AND THEN DO A FACTORY RESTORE OR RECOVER IN TO A CUSTOM ROM. DO NOT ATTEMPT OR YOU WILL IRREPARABLE BRICK YOUR PHONE!
Click to expand...
Click to collapse
What are you talking about when you say factory restore? Are you talking about doing a factory data reset?
Because many have done FDR's without a problem.
Have you tried the one click script that P3Droid and the guys at rootzwiki came up with to get everybody back on the upgrade path?

That's weird.
I returned to stock from 901 using the method in the first link I posted without a hitch.
FYI
Sent from my DROID BIONIC using xda premium

I believe the second post was the answer to your problem.. now second option is to cut a usb cable and connect the negative and positive cables to your battery and leave it for an hour or so to charge..
Sent from my DROID BIONIC using XDA App

This guy obviously doesn't want any help.
He pops in once in a while with a frantic nonsensical post and doesn't bother to read our posts that can help him.

nateohio said:
This guy obviously doesn't want any help.
He pops in once in a while with a frantic nonsensical post and doesn't bother to read our posts that can help him.
Click to expand...
Click to collapse
Oh no, I definitely wanted help BUT I was dumb and used my bionic as my sole internet connection. I have my insurance replacement now($100 down the drain). I had tried ALL of the fixes but non even remotely succeeded. What ended up happening was that I somehow made it where it would not even begin to flash files. I purchased an extended battery but yyyyyeeeeaaaaahhhhh lol, so now I have shiney new supplied for my new phone lol.
Oh wells, you win some and lose some.

Fails for me on first line
idivorceyou said:
I have prepared an uber zip file that contains all you need.
Wish I had it last night! I was up until 3am, worked on this for about 6 hours, and then this finally worked. I tried everything. fastboot, one click this, sd lite, etc. none of it worked.
You will praise me.
this worked - Got my phone back!
of course, I tried every solution in the world and was profoundly frustrated for hours and ran out of battery. but this WORKED. NOTHING else did.
I also had to do the McGuyver thing with an old blackberry usb charger.
snip the end off, strip the red and black wires, insert the red to positive on your battery (battery out of the phone!) insert black to negative, THEN plug in the charger. let it go for at least 1/2 hour.
my uper zip file - UNZIP THIS file to a FOLDER on YOUR DESKTOP.
http://dl.dropbox.com/u/12759680/fastboot.zip
also Manually copy files (update893 and update901) to your SD card!!!!!
(take out the micro sd, load the files onto it using an adapter.)
1. Put phone in Fastboot mode, connect to computer [hopefully you have the drivers installed. if not, search for Motorola_End_User_Driver_Installation_5.2.0_32bit or the 64 bit if that's your operating system
whenever there is a command, I copied it and pasted it in the command window (ctrl v does not work to paste, you must right click and then paste) dont copy the friggin quotation marks
2. Open a command terminal and go to the Stock folder ("cd C:\Documents and Settings\YOUR NAME\Desktop\fastboot")
3) type these commands in the terminal window and wait for the flashing to finish before going to the next line.
----> "moto-fastboot.exe flash webtop grfs.img" (This file will be flashed in 4 parts)
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
Then reboot into stock recovery (volume up+down and power; then select recovery then volume up)
When in recovery, hit both volume up+down, then go to wipe data
then flash update893.zip
If you come upon the triangle with the exclamation point and the android man, dont freak out, hit the power button, down volume, both volume at once, and eventually you will be in recovery.
you will so do a dance.
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
wait a day. then, If you're feeling adventurous, reboot into stock recovery and flash 901!
I'm no maven, but I got my phone back and then to 901.
havent rooted again but I'm waiting for the developers to catch up to 901, which I downloaded and flashed after getting the damn phone back.
Click to expand...
Click to collapse
My phone goes strait to AP Fastboot Flash Mode (S)(Invalid CDT) at power up.
When I enter the first line of these instructions "moto-fastboot.exe flash webtop grfs.img" I get an error that states
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Any ideas?

[Q] Can't get fastboot on Mac to see droid a855's.

I am using a MacBook (OS 10.6.8) with fastboot installed. It works when I use it with a Kindle Fire. I have not one, but three, factory cables, all of which (1) work with the Kindle Fire and (2) seem to work with my two broken-touchscreen a855 droids. I'm pretty sure that I've been able to get the droids into fastboot mode with the factory cable (and, in one case, without it) since (a) the info shown for the droids by System Profiler on the MacBook is very different when I boot with the factory cable (or boot holding down the volume down button) than what it is when I boot normally and connect with a normal cable and (b) I can boot with the factory cable without the battery installed.
But when I run fastboot the way I successfully run it to access the Kindle Fire, it doesn't recognize that the Droid is there. I've tried:
Code:
fastboot devices
fastboot -i 0x22b8 reboot
fastboot -i 0x22b8 reboot-bootloader
fastboot -i 0x22b8 getvar product
and all of the last three without '-i 0x22b8' as well.
It hangs either with no message or with the line:
< waiting for device >
until I press ^c, and sometimes I actually have to close the Terminal window to get out of it.
Is there something different I need to do to get fastboot on the Mac to recognize the Droids?
BTW, I can't use adb yet on these Droids because, without touch, I can't get to the setting to 'allow USB debugging'. Or is there a way to navigate the settings using the keyboard? (I would also need a way to get past the locked startup screen.)
CORRECTION noted on 2012/10/03: My point (a) above is only true in a certain situation. At times, perhaps depending on the battery status, and not when using a factory cable, System Profiler will show one of my Droids as SE Flash OMAP3430 MI rather than as Motorola A855, and the screen of the Droid will show, in plain white text on black:
Code:
Bootloader
2C.7C
[farther down:]
Battery OK
OK to Program
Transfer Mode:
USB
[With cable disconnected, the last two lines become:]
Connect USB
Data Cable

The A855 Droid does not support fastboot. If you're trying to flash a new image it either has to be done through a custom recovery or by using RSD Lite.

Isn't the A855 the same as the 'Droid 1'?
Dave Lister said:
The A855 Droid does not support fastboot. If you're trying to flash a new image it either has to be done through a custom recovery or by using RSD Lite.
Click to expand...
Click to collapse
Isn't the A855 the same thing as the Droid 1? If it is, then it is included in user SkOrPn's list of devices for which his factory cable works. Since he has probably sold hundreds of such cables, he would almost certainly know by now if he's wrong about that.
It's possible that I'm wrong about the identity of the A855 with the Droid 1. But if I'm not, my next guess is that you are wrong about the A855 not supporting fastboot. What are your sources for that assertion?

aarons510 said:
Isn't the A855 the same thing as the Droid 1? If it is, then it is included in user SkOrPn's list of devices for which his factory cable works. Since he has probably sold hundreds of such cables, he would almost certainly know by now if he's wrong about that.
It's possible that I'm wrong about the identity of the A855 with the Droid 1. But if I'm not, my next guess is that you are wrong about the A855 not supporting fastboot. What are your sources for that assertion?
Click to expand...
Click to collapse
The A855 is the Droid 1. What a factory cable allows you to do w/ an A855 is power the device even when the battery is dead due to the device only charging when the phone is fully booted, not in recovery or bootloader modes. I am my own source for this, as I have owned an A855 since it was released in November 2009 and was on the DroidMod ROM team for a time. The phone simply does not support fastboot.

Thanks for the clarification. I have downloaded RSD Lite 5.7 from tucows, but I have no idea what to do with it! (It's a zip file, but the contents is a single file with the .msi extension, which probably means I'll have to borrow access to a windoze machine to run it. I have and use a Mac.) Can you point me to a guide or the most compact compendium of info on using RSD Lite (or not having to use it!) that you know about that I can refer to without getting lost in hundreds or thousands of posts?
BTW, can I do these things without having a functioning touch screen? I already have one new digitizer ready to install, but I'd rather not install it until I have a good idea that the Droid will work reasonably well with it.

Finding an RSD Lite alternative for Linux/Mac took about 2 seconds of googling: http://www.atrixforums.com/forum/mo...h-any-sbf-file-without-rsdlite-mac-linux.html
And you don't need a working touchscreen for flashing RSDs or Custom Roms.

I had forgotten about the Linux/Mac alternative to RSD Lite. To put the phone into bootloader mode, press and hold "up" on the D-pad and then turn on the phone. You can then flash any .sbf file intended for the A855. I believe there are still some floating around that only flash a custom recovery image, which you can then use to install a new ROM off the SD card. Navigation in recovery is done w/ the power and volume buttons.

I've had some limited success. I downloaded sbf_flash, added .sh to the name and made it executable, then downloaded "VZW_A855_FRG01B_QSC6085BP_C_01.43.01P_SW_UPDATE_01.sbf" (a.k.a. 'FRG83G') from Peter Alfonso's site. I managed to get each of my two broken-touch droids (ignoring a third one I have with a broken USB/charge port!) into the mode with 'OK to Program' on the screen, and ran 'sudo ./sbf_flash.sh *.sbf' from the directory containing the two downloads. This got both of them into a state where I was supposed to 'touch' a green android, but couldn't, so I don't even know what ROM I have installed and whether it is rooted or not.
Any suggestions as to what further testing I can do on these Droids before deciding which to take apart and install the new digitizer on? Any way to get into USB Debugging mode without navigating with a touch screen?
BTW, one of the Droids also has a very unreliable (i.e., nearly useless) power button, so I got that one into the bootloader mode by (1) removing the battery, (2) connecting a factory cable to the Droid and then to the computer while holding down the 'up' button on the D-Pad, and (3) replacing the battery. Then I removed the factory cable and replaced it with a standard one before running sbf_flash. (Maybe I could have done it with the factory cable left in, but I didn't try.)

[Q] yet another soft bricked bionic

I love my bionic, and it has plenty of life left in it. Except for the fact that I screwed it up. Here's what happened: I had it rooted, had bootstap installed, backed up my system using the bootsrap recovery, and then tried to install a CM 10.1 zip file I found from somewhere on these forums. It gets to the load screen and then I see the blue CM wheel that NEVER stops turning (at least not within the 4 hours or so I let it run). No problem I say, I'll just reload my backup. Oh wait, you need a working system to do that. DOH!! So now, if I let it boot normally I get the perpetual CM boot screen. I've downloaded several other ROMs and tried to use the stock recovery to install them but it keeps saying "signiture not verified" or some such other nonsense which leads me to believe that's not an option. I've spent quite a bit of energy googling and going through forums on how to fix this, but all I can find are how to's with old outdated links.
If someone has a current link to whatever .xfz file I need or some other magical way to fix this, I would be indebted to you. As I said, I love this phone (it still looks and functions like new otherwise) and it seems like in it's current state I should be able to fix it somehow but I may be on my way to the Verizon store a little earlier than planned if I cant figure this out. Any takers?

Sounds very similiar to my issue.. no response to mine yet either.

Here's a link for your RSD
http://sbf.droid-developers.org/cdma_targa/VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip
Use RSD Lite to restore your phone. Google is your friend. Read & follow all instructions. I am in no way responsible for what you do to your phone.
Best of luck!

Low battery when trying to program bootloader.
Ok, I made somewhat of a noob mistake here. I read somewhere that there was an ICS ROM that could be flashed on the safe side using Bootstrap. Thing is, I couldn't remember or find the one I'd read about. Long story short, I flashed Icarus 1.8.3 on safe side using Bootstrap, which didn't work. I wiped everything there is to, including System. Big No No. Phone no likey Icarus on safe side (I know, the instructions said Safestrap 3.11 only). My question, other than buying a spare battery charger to charge the battery without the phone, can I charge it using the phone? I can boot into stock recovery, bootloader, and the screen where you select Normal Boot, Fast Flash, etc. I'll buy the charger if need be, but I'd rather not shell out the $50 or so for it if I don't have to. Thanks in advance.

:thumbup:

Edited to reflect personal unbrick success:
For those of you looking for a way to flash the SBF/FXZ file from within a Linux environment:
There's a "manual" method suggested at a different site using fastboot; unzip the zip archive (SBF file) and flash the listed/pertinent files/images individually to the device. It's still written up with windows-users in mind, but I don't see why it wouldn't work in Linux. Hope that helps someone.
Here's the jist of the commands that were involved in succesfully unbricking my Droid Bionic using the appropriate SBF file for my Android version:​
Code:
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash mbmloader mbmloader.bin
fastboot flash mbm mbm.bin
fastboot reboot-bootloader
fastboot flash cdt.bin cdt.bin
fastboot erase cache
fastboot erase userdata
fastboot flash lbl lbl
fastboot flash ebr ebr
fastboot flash mbr mbr
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cdrom cdrom
fastboot flash preinstall preinstall.img
fastboot flash webtop grfs.img (skip this step if you are using a JB fxz)
fastboot flash radio radio.img
fastboot reboot
Obviously, don't forget that you have to be in fastboot mode to use the `fastboot` command (Hardware keys: VolUp +Power)
**Once again, I was lucky enough to stumble upon a posting by someone else on androidforums. Feel free to check it out at the above-mentioned link, perhaps you could adapt it to your own situation in times of despair.

Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic

Mr. HQ said:
Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic
Click to expand...
Click to collapse
Yup...they have a neatly organized list view of the SBF files, for all of the different android versions for the Droid Bionic (XT875), as well as a huge number of other devices.
Here's the section for the Bionic: http://sbf.droid-developers.org/cdma_targa/list.php

I can't exactly speak for how to solve the original problem, but for others who may search here. I use safestrap on my phones (3 between the kids and I all Bionics) and I put a newer version of Cyanogenmod on one phone just yesterday and I had the same problem. after trying a few things and still having the stuck boot, I deleted the ROM1 (this was the ROM slot I was using) slot and re-created it. Next I reinstalled CM10.1.3 and it booted. Safestrap is a great way to flash custom ROMS in my opinion I would recommend it highly!

Thanks for this one
Mr. HQ said:
Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic
Click to expand...
Click to collapse
Glad I read this post....

Xt875 hard brick
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery

SPheDaGhost said:
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery[/
are you sure your battery is good? you need to externally charge your bat, sometimes when phone is not functioning properly the bat will rapidly discharge, i dont know how clever you are but you can cut the end off an old charger and achieve a recharge by cleverly connecting the cut off leads to the bat
Click to expand...
Click to collapse

Have a external battery charger
hugh a said:
SPheDaGhost said:
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery[/
are you sure your battery is good? you need to externally charge your bat, sometimes when phone is not functioning properly the bat will rapidly discharge, i dont know how clever you are but you can cut the end off an old charger and achieve a recharge by cleverly connecting the cut off leads to the bat
Click to expand...
Click to collapse
I have a external batter charger (see attachment) already, although I do know how to make one myself. It was less time consuming to go to the store and buy one. Plus it was only 5 bucks which isn't that bad. This external battery charger also displays the percent of battery life remaining. But I'll do what you suggest and see if that works out. Another strange thing is that if I plug the usb cord without the battery the charging (white) light comes on, which before it never did.
I know that the bionic droid xt875 uses the targa firmwares. I crashed my device flashing the spyder given to me by a source here on this forum. I was trying use my bionic with a gsm network so I follow this other guide. before I had followed this guide I had run through the proper proceedures of edit build.prop and radiocomm nv edit...etc.etc.. I was only managing to get no service on the HWB so I found an article pertaining to my particular model and tried it and subsequently it failed and now I'm stuck with a nice little paper weight.
Any other suggestions with this matter would be greatly appreciated. I'll keep you posted if the conditions changes.
Click to expand...
Click to collapse

[SOLVED] Cat't flash anything to my phone - Help

Hi folks,
Yesterday I got my droid 4. It had terrible rom in it!
So I decided to wipe all data and flash a stable rom. This is my first motorola phone, accidentally I wiped everything including clockworkmod, safestrap, everything
Then I had battery low problem. After 1 night searching all the internet I cound't find easiest solution than making factory cable. Today I made a factory usb cable, this one solved the low battery problem. I'm able to flash via RSD Lite now
I downloaded and tried to flash latest rom from this page- http://sbf.droid-developers.org/phone.php?device=11
RSD gave me this error "failed flashing process. 20/25 system "system.img" - usb error occurred while reading/writing"
I tried to flash by running RSD lite administrator rules. I updated version of RSD nothing helped. It always stuck step 20 while flashing system.img (I have windows 8.1)
I thought may the file I downloaded is damaged. md5 checking is normal. File was okay.
Then I downloaded oldest ICS rom and tried to flash it. RSD gave me an error while flashing. I googled the problem and figured out that I can't downgrade android version.
So here I am, I don't know what to do guys. I just wanna use my phone with a stable normal working rom. Can be official stock rom, doesnt meter. I don't need root permissions. All I need is unlock simlock, because I don't live in USA.
Please show me the way to get this fastboot screen off from my face
Thanks!

What I tried recently,
Tried to flash all stock images - all of them fails while flashing system.img
Tried to flash on 3 different computers. One of them runs on windows 8.1, other one windows 8, last one windows 7 - nothing changes
Tried to flash manually with fastboot by following xml file. Gives "too many links" error while flashing system.img file.
Tried to flash system.img file using mfastboot.exe - nothing changed
What I'm doing wrong with this system.img files? No matter how im tring to flash it. Just something goes wrong :/

Which bootloader is it on?
Can't downgrade stock android version
Safest to use newest xml /firmware version
Make sure you install Motorola drivers first, and verify by opening device manager, and checking they are Motorola drivers being used.
More in my list
sd_shadow's [Collection] of Links for Droid 4
Sent from my Amazon OtterX using Tapatalk

Yes I was trying to flash latest xml firmware. Drivers are okay, I can flash some files in xml firmware fastboot works pretty good. But somehow it stucs while flashing system.img
Keep giving "too many links" error. I'm downloading Live OpenSuse to try on linux also. I hope this will solve my problem.

Solved! I also tried to flash system image on Linux (Ubuntu) I got an another error (no such a device)
Then I read somewhere that prolem could be the cable. I made my factory cable which seems terrible as I said before But I had to use it otherwise I was getting battery low error.
I did little trick. I switch on the phone into Ap Fastboot Mode with original usb cable and ac charger connected. It said "battery ok". Than I plugged out the usb cable from ac charger and connected to my computer. And started to flash images iimmediately using fastboot.
Using fastboot is impotent because if you use RSD Lite to flash images will cause to restart your phone after flash each file. There are min 10 files to flash any xml stock firmware. Restart causes to get battery low - cannot program error again. So you can flash all files manually.
Or export the stock firmware zip file. And find the xml file in folder. Open the xml and delete all restart commands between flash commands. I think you can finish flashing all files in this way without restarting.
May you can remove battery and charge it out of your phone and try to flash rom with charged battery and quality usb cable. If available order a brand new motorola factory cable or make a beautiful one not as same as my terrible one
Anyway I hope this going to save someones time to solve problem. I spent almost 3 full days to solve this. Finally I'm texting with this lovely droid 4 keyboard

ayuda help no se ingles pero me paso lo mismo que a ti, help help
help help
me paso lo mismo que a ti

I bricked my Moto X 2013 VZW Dev Edition - any chance of revival?

I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?

At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.

PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.

I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!

ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk