Database Info

[10/14/2012][RELEASE][UNOFFICIAL]Stock 67.21.125 ICS FXZ[Minimal/Minimal-Standard]

Do you want the fastboot files for ics (official AT&T US)?
well its all (or almost all) here!!!
Note: This is the minimal standard that is just missing the system.img and the junk apps in the preinstall partition, we should get it with the %100 OEM official .
Also: I'm not responsible if this brick's your Atrix 2!!!
And finally, the download link:
Minimal
Minimal Standard
Cheers,
TCF38012
PS: Don't flash your own system.img this WILL SOFT BRICK YOUR DEVICE.
List of Images Needed(by priority):
1. System (DON'T USE THE SOUTH AFRICIAN ONE AND SOFT BRICK)

Reserved.

Good job man!
It's important to have an ICS FXZ.
Sent from my MB865 using xda app-developers app

sad_but_cool1 said:
Good job man!
It's important to have an ICS FXZ.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but it is incomplete so don't totally rely on it.

So what happens if you bork your system image? Have you tested that yet?
I do see you are looking for a system image, but I am curious how this can save you from a boot loop without that.
Nice start though.

jimbridgman said:
So what happens if you bork your system image? Have you tested that yet?
I do see you are looking for a system image, but I am curious how this can save you from a boot loop without that.
Nice start though.
Click to expand...
Click to collapse
Thanks.
I have every image now except for radio.
I'll upload the final one for the second leak when I make the most hardest part(radio.img)

tcf38012 said:
Thanks.
I have every image now except for radio.
I'll upload the final one for the second leak when I make the most hardest part(radio.img)
Click to expand...
Click to collapse
You can grab it off the phone and use the ext4utils to package it up, there are few guides on how to do it for the og atrix, and you can figure the rest out from there.... that is similar to how I have done it.

Don't we have to worry about the certs on those missing img files? From my understanding, you can't just dd/cat those images and flash on anyone's phone.. and from some of our previous tests with mtnlion.. we've tried that.
Or, would everyone have to make their own images? Found this in a post by whirleyes (not sure how much weight it holds, but similar idea):
whirleyes said:
Next time you got it back from service, do
Code:
cat /dev/block/system > /mnt/sdcard/system.img
& put it somewhere safe.
It seems that you can restore own system partition backup from fastboot.
Condition :
bootloader won't check security certificate when restored from own backup
you must used moto-fastboot.exe & not fasboot.exe
Click to expand...
Click to collapse
I would really like to see this fxz come to life though... keep it up.

alteredlikeness said:
Don't we have to worry about the certs on those missing img files? From my understanding, you can't just dd/cat those images and flash on anyone's phone.. and from some of our previous tests with mtnlion.. we've tried that.
Or, would everyone have to make their own images? Found this in a post by whirleyes (not sure how much weight it holds, but similar idea):
I would really like to see this fxz come to life though... keep it up.
Click to expand...
Click to collapse
Yes that works with moto-fastboot since it does not check during flashing. Now booting those is another issue. The boot image is the one to really worry about. System image and others not so much, even the recovery image is not signed.

jimbridgman said:
Yes that works with moto-fastboot since it does not check during flashing. Now booting those is another issue. The boot image is the one to really worry about. System image and others not so much, even the recovery image is not signed.
Click to expand...
Click to collapse
Right, but whirleye's was saying the certs aren't checked only if you flash your own system.img on your own phone.. or that's what i took away from it. Plus, we flashed the ICS system and boot from your phone on mtnlion's, and he came out with new CG errors.. still stuck in fastboot.
I guess this is a good place to elaborate on all of this.. if it's not considered hijacking.
@tcf38012 - has this been tested?

alteredlikeness said:
Right, but whirleye's was saying the certs aren't checked only if you flash your own system.img on your own phone.. or that's what i took away from it. Plus, we flashed the ICS system and boot from your phone on mtnlion's, and he came out with new CG errors.. still stuck in fastboot.
I guess this is a good place to elaborate on all of this.. if it's not considered hijacking.
@tcf38012 - has this been tested?
Click to expand...
Click to collapse
Right, that is why I was saying that flashing is easy, but booting is much harder with the locked bootloader checking the signature before booting, hence the cg errors from MY image on someone else's phone.

Updated 10/14/2012!!!
Cheers!!!

tcf38012 said:
Updated 10/14/2012!!!
Cheers!!!
Click to expand...
Click to collapse
So what exactly is this and how do we use it?
Sent from my MB865 using xda premium

tmease1 said:
So what exactly is this and how do we use it?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It is the partial fastboot files for ATT US 4.0.4. Nothing like a bootloader unlock or jellybean. When you are softbricked, just use these in AP fastboot and you are back to normal
Cheers!!!

I do not understand exactly how this works, please be more explicit.
Well let me know if this would work for me, my problem was that upgrading from GB to ICS 2.3.6 Official OTA, everything worked well and use the computer all day, until it froze and reboot and get stuck in the Motorola logo and back and restarted.

Andr3s said:
I do not understand exactly how this works, please be more explicit.
Well let me know if this would work for me, my problem was that upgrading from GB to ICS 2.3.6 Official OTA, everything worked well and use the computer all day, until it froze and reboot and get stuck in the Motorola logo and back and restarted.
Click to expand...
Click to collapse
This may help you since it sounds like you are softbricked. At this point you have nothing to lose and the boot.img is already there on your phone. Give it a shot and if it doesn't work you may be able to take it to AT&T since it was the official OTA that bricked ya. Good luck!!!

Ok friend, another question, as I use the files that I download, Minimal, Minimal Standard? also you do with South Africa FXZ file?
regards

Andr3s said:
Ok friend, another question, as I use the files that I download, Minimal, Minimal Standard? also you do with South Africa FXZ file?
regards
Click to expand...
Click to collapse
Minimal Standard. All you need from the South Africa FXZ is the system.img and flash with "moto-fastboot flash system system.img". Don't flash anything else from the South Africa FXZ.
Cheers!!!

Ok to get this straight, first put the phone in Fastboot bike, then unzip the file 4.0.4_67.21.125_edison_fxz_minimal_standard, run the file and then run flash.bat "moto-fastboot flash system system.img" with the system.img? That is so true?
if this is so I could include the system.img file in the same folder and add the file. bat line "moto-fastboot flash system system.img"?

Hello, after doing all this, I have this problem
Invalid CG OTV (CG: systema): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X0056)
Invalid CG OTV (CG: system)
sending 'mbm' (256 KB)... OKAY [ 0.024s]
writing 'mbm'... OKAY [ 0.466s]
rebooting into bootloader... OKAY [ 0.285s]
sending 'mbmloader' (41 KB)... FAILED (command write failed (No such file or
directory))
sending 'mbm' (256 KB)... FAILED (command write failed (No such file or
directory))
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
sending 'lbl' (16 KB)... FAILED (command write failed (No such file or
directory))
sending 'logo.bin' (854 KB)... FAILED (command write failed (No such file or
directory))
< waiting for device >
sending 'ebr' (16 KB)... OKAY [ 0.007s]
writing 'ebr'... OKAY [ 0.502s]
sending 'mbr' (16 KB)... OKAY [ 0.249s]
writing 'mbr'... OKAY [ 0.471s]
sending 'devtree' (512 KB)... OKAY [ 0.286s]
writing 'devtree'... OKAY [ 0.519s]
sending 'boot' (8192 KB)... OKAY [ 1.401s]
writing 'boot'... OKAY [ 0.877s]
sending 'recovery' (9216 KB)... OKAY [ 1.609s]
writing 'recovery'... OKAY [ 1.433s]
sending 'radio' (12080 KB)... OKAY [ 1.109s]
writing 'radio'... OKAY [ 1.906s]
sending 'cdrom' (12032 KB)... OKAY [ 1.049s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
sending 'preinstall' (262144 KB)... OKAY [ 17.227s]
writing 'preinstall'... OKAY [ 28.739s]
sending 'preinstall' (20480 KB)... OKAY [ 1.433s]
writing 'preinstall'... OKAY [ 1.901s]
sending 'system' (262144 KB)... OKAY [ 19.473s]
writing 'system'... OKAY [ 29.494s]
sending 'system' (229120 KB)... OKAY [ 15.423s]
writing 'system'... OKAY [ 25.304s]
erasing 'userdata'... OKAY [ 0.045s]
erasing 'cache'... OKAY [ 0.666s]
rebooting...
Press any key to continue . . .
Click to expand...
Click to collapse

Help - device not booting

I was already on stock 4.4.2. Used RSD to flash it when the phone was on JB. My phone's suddenly not botting anymore though. Just stock on the boot animation screen. I tried flashing back the same firmware, but I get "Phone Returned Failed" error on RSD lite every time
What can I do? My phone was completely stock. Bootloader wasn't unlocked.
*edit*: Boot animation runs fine. Then it's just stuck at the orb thingy which just keeps going.

pyromaniac1 said:
I was already on stock 4.4.2. Used RSD to flash it when the phone was on JB. My phone's suddenly not botting anymore though. Just stock on the boot animation screen. I tried flashing back the same firmware, but I get "Phone Returned Failed" error on RSD lite every time
What can I do? My phone was completely stock. Bootloader wasn't unlocked.
*edit*: Boot animation runs fine. Then it's just stuck at the orb thingy which just keeps going.
Click to expand...
Click to collapse
Need more details on "fail." Just saying it failed won't narrow down anything.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
Need more details on "fail." Just saying it failed won't narrow down anything.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Tried flashing VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml, get this error.

pyromaniac1 said:
Tried flashing VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml, get this error.
Click to expand...
Click to collapse
you have to edit the xml file and completely remove the line containing "gpt" in that error. the partition table cant be changed/downgraded once upgraded.

bweN diorD said:
you have to edit the xml file and completely remove the line containing "gpt" in that error. the partition table cant be changed/downgraded once upgraded.
Click to expand...
Click to collapse
I did
still luck. Whatever item it tries to flash it returns the same error. I even deleted everything in between that to system.img. Gives the same error trying to flash system.img

pyromaniac1 said:
I did
still luck. Whatever item it tries to flash it returns the same error. I even deleted everything in between that to system.img. Gives the same error trying to flash system.img
Click to expand...
Click to collapse
try this, its not the same as the utility in the dev forum, its a modified version.

bweN diorD said:
try this, its not the same as the utility in the dev forum, its a modified version.
Click to expand...
Click to collapse
Flashed the XML with RSD lite. still the same error. Removed the GPT line and tried again. Same thing.

pyromaniac1 said:
Flashed the XML with RSD lite. still the same error. Removed the GPT line and tried again. Same thing.
Click to expand...
Click to collapse
Mmk, do not use rsd, use the bat file at the bottom of the directory. You defeated the purpose of it by using rsd.
Sent from my G2 running SlimKat

bweN diorD said:
Mmk, do not use rsd, use the bat file at the bottom of the directory. You defeated the purpose of it by using rsd.
Sent from my G2 running SlimKat
Click to expand...
Click to collapse
Ran the script twice. Managed to copy this the second time :/. Phone reboots after flashing is done and like before still stuck at the end of the boot animation.
[*] Press any key to continue.
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.328s
sending 'sbl1' (101 KB)...
OKAY [ 0.028s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.156s
sending 'sbl2' (126 KB)...
OKAY [ 0.029s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.155s
sending 'sbl3' (512 KB)...
OKAY [ 0.058s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.323s
sending 'rpm' (140 KB)...
OKAY [ 0.030s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.279s
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.286s
sending 'aboot' (256 KB)...
OKAY [ 0.038s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.292s
sending 'modem' (30720 KB)...
OKAY [ 2.262s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.385s
sending 'fsg' (165 KB)...
OKAY [ 0.032s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.144s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.045s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.043s
sending 'logo' (854 KB)...
OKAY [ 0.081s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.200s
sending 'boot' (10240 KB)...
OKAY [ 0.751s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.468s
sending 'recovery' (10240 KB)...
OKAY [ 0.779s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.503s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.044s
sending 'system' (30720 KB)...
OKAY [ 3.806s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 5.397s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.045s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.044s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.006s

pyromaniac1 said:
Ran the script twice. Managed to copy this the second time :/. Phone reboots after flashing is done and like before still stuck at the end of the boot animation.
Click to expand...
Click to collapse
hmm, not good!
it looks like the hole phone is r/o when in fastboot. i have seen this before several times and have yet to see any one fix it.
i thought a few of those may fail, although you weren't actually downgrading any of them, they shouldn't have, but every writing and erasing command has failed. i was hoping that didn't happen.
we didn't try a factory reset but that's pointless, as the script tried it and it failed.
i dont think there is a way to fix this. maybe @SamuriHL has an idea.
just so you know Sam, the "modified" script i gave him a few post down uses moto fastboot to flash everything.
figured that was the best shot, if there was one, given what he already tried.
thanks

Without having read everything cause I'm pressed for time, my gut instinct says this:
USB cable (make sure it's the oem cable that came with the phone...yes, it matters), USB port (usb 2.0 NOT 3.0), or USB driver issue.

SamuriHL said:
Without having read everything cause I'm pressed for time, my gut instinct says this:
USB cable (make sure it's the oem cable that came with the phone...yes, it matters), USB port (usb 2.0 NOT 3.0), or USB driver issue.
Click to expand...
Click to collapse
thanks!
i hope its something that simple. since the other instances were unlocked devices running custom recovery (with other mitigating factors), this seems rarely fixable as none of the other causes for a true r/o situation apply here.
im afraid to tell him to try a fdr in recovery, as i have seen quite a few cases go worse lately for no reason.
maybe a simple fix is what is needed.
thanks for your input either way.

I always try simple before moving on to the hard stuff. To me it feels like a communication issue with the phone but I don't know for sure. It's a guess. I'd start there at the very least.

SamuriHL said:
I always try simple before moving on to the hard stuff. To me it feels like a communication issue with the phone but I don't know for sure. It's a guess. I'd start there at the very least.
Click to expand...
Click to collapse
Well a factory reset was the first thing I tried anyway. So no luck there. I've tried it with the OEM cable on my laptop as well as a different cable on my PC. Not sure about the USB 3.0 or 2.0 though. I have a lenovo x230 laptop with 2 USB 3.0 ports so ill try again and see if using those ports with the OEM cable makes a difference.

You can not use a USB 3 port. It will fail.
Sent from my SM-P600 using Tapatalk

Nope. Tried it on my PC and laptop both on the usb 2.0 port with the oem cable. Still the same

pyromaniac1 said:
Nope. Tried it on my PC and laptop both on the usb 2.0 port with the oem cable. Still the same
Click to expand...
Click to collapse
I would go an uninstall all drivers, reboot, and then reinstall the drivers and then hook your phone up again to see if that helps. Could be either drivers are corrupted or something else is hosed up.
Since you've tried it on two different computers and it failed, I'm assuming you used the same drivers on both machines? What version of the drivers are you using?
You might want to go to the moto site and get the Motorola helper to bring down the drivers.

i assume you've tried both RSD Lite and motofastboot?

SamuriHL said:
i assume you've tried both RSD Lite and motofastboot?
Click to expand...
Click to collapse
he did, several times.
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
SamuriHL said:
i assume you've tried both RSD Lite and motofastboot?
Click to expand...
Click to collapse
results from mfastboot are in post 9.
failed writing and or erasing at every step. i made the script for him, he posted the results.
even if a couple would have failed as writing equal code, they all wouldn't have as it flashes each separately.

Yea, not a situation I've seen before. Almost like the partition table is screwed up somehow so it doesn't know the mount points to flash to. Just for fun, let's try something.
Boot her up in AP Fastboot mode, connect it to USB 2.0, then try this:
o) From a cmd prompt, type: fastboot oem fb_mode_clear
o) Then flash the FXZ again either with motofastboot or RSD.
I'm just curious.

[Q] xt926 - help is appreciated

device: VZW motorola droid razr hd xt926 - completely stock, no customizing at all, every update that came to the phone I installed without problem.
About a month ago (~dec 16, 2014 I believe) the phone was lagging and unresponsive so I powered down, restarted, and that is when the problem began. Upon restart the phone got to the red motorola logo and would hang there. holding the power button would power down for a second, then restart.. so I soft reset it to the boot menu where it atleast wasnt heating up drastically. I left it plugged in because there was no way to power down. From there I began researching the xt926 and seeing other people's problems about the phone hanging at boot logo.
I scoured these forums (and numerous others) for problems similar to mine. Since I was able to get into the boot options menu I've tried everything I could find.. rsd lite, rsd flasher, motorola device manager, house of motorola, droid razr utility...
I tried for about 5 days straight and gave up, took it to a local cell repair place and asked what they would do to repair it. They mentioned a few of the things I tried and said that I had went further than they would go. Out of pity (I believe) they gave me an old BB curve which I've been using the last month. I've been shopping around lately for new phones and wanted to give the razr hd one last crack before relenting and getting a new phone (either S5 or HTC one M8).
First question I guess is, is the phone unusable and beyond repair? upon power up, the phone gets to the red motorola logo for about 2 seconds then goes to this presumed fail boot screen.
it lists:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 03:17:13)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode: USB Connected
Load kernel (boot) failed
Fastboot Reason: Boot Failure
I can restart the phone from here by clicking the power button, it restarts, hits logo screen, then right back here.
I can get to the boot selection screen by holding the volume up button when its restarting.. it'll get to the boot menu and then restart after about 3 seconds of idle time if I dont pick something quickly.. the 5 options at the boot selection are:
Normal Powerup
Recovery
AP Fastboot
Factory
BP Tools
Normal Powerup, Factory, and BP Tools do nothing.. the phone restarts and hits logo screen then boot failure.
AP Fastboot restarts phone and goes to the same boot screen, but instead of the load kernel boot failure stuff it says: Fastboot Reason: Key Pressed. This is the same result as during powerup/restart holding the volume down key.
Recovery restarts, gets to logo screen, then after about 5 seconds gets to the droid dude with the red exclamation triangle over his open chest. From here I can get it into the recovery mode with 5 selections..
reboot system now
apply update from sdcard
apply update from ADB
wipe data/factory reset
wipe cache partition
All of that being said.. do I have any options to get this phone functional?
Your time and effort is greatly appreciated.
Cheers

I'm assuming that you tried the wipe data from recovery option ? And then to be clear did you actually download and install a factory image using RSD?

i would try rsd lite again with all the latest version of the fxz/sbf in case you were using an old one. this thread from @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083 is the latest for the xt926 make sure you have the moto drivers installed. if you need i can help with teamviwer or hangouts if you want just pm me for details.
as a side note i do not think that your phone is dead just soft bricked.
---------- Post added at 10:21 PM ---------- Previous post was at 10:14 PM ----------
randymancanstand said:
device: VZW motorola droid razr hd xt926 - completely stock, no customizing at all, every update that came to the phone I installed without problem.
Cheers
Click to expand...
Click to collapse
__

I appreciate the input, sorry for the delay in my response.
I'm assuming that you tried the wipe data from recovery option ? And then to be clear did you actually download and install a factory image using RSD?
Click to expand...
Click to collapse
yes, I factory wiped and using rsd lite, droid razr utility, rsd flasher I tried many different images.. through different iterations and combinations. When rsd lite had no effect installing the different images I had, I moved onto a different program. I wasnt exactly sure which image the system required.. I went through the following:
VZW_XT926_4.1.1_9.8.1Q_39_VQW_CFC.xml
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
VZW_XT926_4.4.2-KDA20.62-10_1FF.xml
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
I am unsure if they are 'factory' images
i would try rsd lite again with all the latest version of the fxz/sbf in case you were using an old one. this thread from @SamuriHL http://forum.xda-developers.com/droi...46-15-t2873083 is the latest for the xt926 make sure you have the moto drivers installed. if you need i can help with teamviwer or hangouts if you want just pm me for details.
as a side note i do not think that your phone is dead just soft bricked.
Click to expand...
Click to collapse
I am glad to hear that the phone may have a chance yet. I will look into the latest image. I have RSD Lite v6.2.4.. could someone remind me of the basic flash process?
connect the phone to my pc
put the phone into fastboot,
load up rsd lite
load up image in rsd lite
????
profit?
Again, thank you for your time.
edit: I also have motorola mobile driver 6.4.0 installed

RSD Lite v6.2.4
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
When i click start it fails and gives status:
Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
Am currently trying house of moto..

randymancanstand said:
RSD Lite v6.2.4
VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
When i click start it fails and gives status:
Failed flashing process. 1/17 flash partition "gpt.bin" -> Phone returned FAIL.
Am currently trying house of moto..
Click to expand...
Click to collapse
this may sound to simple but are you unziping the sbf/fxz?

billycar11 said:
this may sound to simple but are you unziping the sbf/fxz?
Click to expand...
Click to collapse
yes definitely

okay maybe your partitions are messed up then i have seen @bweN diorD help people with that before so he may be able to help.

randymancanstand said:
yes definitely
Click to expand...
Click to collapse
flash this in fastboot. use the data wipe batch file.
if the phone doesnt boot fully to the setup screen within 10min after flashing, its likely toast.
edit,
on second thought, dont close the prompt until you see if it boots up or not. if not, copy all the text from inside the prompt and post it here for me to look at.
thanks

The download is going incredibly slow, but when its done I will flash it and report back.
Thanks for the direction

randymancanstand said:
The download is going incredibly slow, but when its done I will flash it and report back.
Thanks for the direction
Click to expand...
Click to collapse
so the download is crawling along.. it has finished prematurely a couple times already. I'll open the .rar and it says its incomplete.
Is this for matt's droid utility? I have a copy of it I got on 12/17/14.. with an fxz labeled:
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_RSD
I'll keep trying the download from the link you provided in the mean time

randymancanstand said:
so the download is crawling along.. it has finished prematurely a couple times already. I'll open the .rar and it says its incomplete.
Is this for matt's droid utility? I have a copy of it I got on 12/17/14.. with an fxz labeled:
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_RSD
I'll keep trying the download from the link you provided in the mean time
Click to expand...
Click to collapse
You need to use the one I just provided.
Not sure what's up with the DL speeds, my account is paid, so that almost never happens.

bweN diorD said:
You need to use the one I just provided.
Not sure what's up with the DL speeds, my account is paid, so that almost never happens.
Click to expand...
Click to collapse
no dice...
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] Be VERY aware! This WILL wipe your userdata, including contacts, apps, etc.
[*] I am not responsible if this wipes your internal sdcard, and you should
[*] backup anything worth it to you to your external sdcard and computer before
[*] you choose to continue. You can exit now with the X button on this window.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] This script will also wipe your data (did i mention this will wipe your data
?).
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.340s
sending 'sbl1' (101 KB)...
OKAY [ 0.030s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.160s
sending 'sbl2' (127 KB)...
OKAY [ 0.030s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.160s
sending 'sbl3' (512 KB)...
OKAY [ 0.060s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.350s
sending 'rpm' (140 KB)...
OKAY [ 0.030s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.300s
sending 'tz' (210 KB)...
OKAY [ 0.030s]
writing 'tz'...
Failed to erase partition
Failed to flash partition tz
FAILED (remote failure)
finished. total time: 0.300s
sending 'aboot' (256 KB)...
OKAY [ 0.040s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.310s
sending 'modem' (30720 KB)...
OKAY [ 2.400s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.540s
sending 'fsg' (165 KB)...
OKAY [ 0.030s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.160s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.050s
sending 'logo' (854 KB)...
OKAY [ 0.090s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.220s
sending 'boot' (10240 KB)...
OKAY [ 0.810s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.550s
sending 'recovery' (10240 KB)...
OKAY [ 0.822s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.556s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
sending 'system' (30720 KB)...
OKAY [ 2.400s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 4.010s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.053s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.060s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.010s
Hit ENTER to return.

Sorry, but throw it in the trash and move on.
I have seen this exact scenario many times, its not fixable.

bweN diorD said:
Sorry, but throw it in the trash and move on.
I have seen this exact scenario many times, its not fixable.
Click to expand...
Click to collapse
I figured as much.. any idea what could bring this on?
Like I said, no modifications to the phone, it was lagging/hanging so I restarted it.. simply would not boot afterward..
Anyway, thanks for your time and effort. Atleast I know for sure it is done with.
Cheers

randymancanstand said:
I figured as much.. any idea what could bring this on?
Like I said, no modifications to the phone, it was lagging/hanging so I restarted it.. simply would not boot afterward..
Anyway, thanks for your time and effort. Atleast I know for sure it is done with.
Cheers
Click to expand...
Click to collapse
no one seems to know whats causing it. some have mods, some dont. the hole device just seems to become write protected for no reason.

Flash Fails while flashing system.img : invalid entry hash for system index=0

I m using Droid Ultra (xt1080) SU6-7.7 and i was trying to flash the same firmware because the previous one was corrupted and wifi and bluetooth stoped working and settings began to crash , etc.
I downloaded RSD Lite latest version and adb drivers and stuff and i charged the phone to 100% and finally started flash and it went good in the start but when it began to flash system.img it took a long time and FAILED. with a message on the screen "invalid entry hash for system index=0"
I also tried House Of Moto , Adb and Fastboot but it also gives the error: "invalid sparse file format at header magi". PLEASE HELP ME OUT OF THIS MY DEVICE IS BRICKED
the firmware i m trying to flash " VZW-4.4.4-SU6-7.7-release-keys.xml.zip "

DeXtern00b said:
I m using Droid Ultra (xt1080) SU6-7.7 and i was trying to flash the same firmware because the previous one was corrupted and wifi and bluetooth stoped working and settings began to crash , etc.
I downloaded RSD Lite latest version and adb drivers and stuff and i charged the phone to 100% and finally started flash and it went good in the start but when it began to flash system.img it took a long time and FAILED. with a message on the screen "invalid entry hash for system index=0"
I also tried House Of Moto , Adb and Fastboot but it also gives the error: "invalid sparse file format at header magi". PLEASE HELP ME OUT OF THIS MY DEVICE IS BRICKED
the firmware i m trying to flash " VZW-4.4.4-SU6-7.7-release-keys.xml.zip "
Click to expand...
Click to collapse
did you verify md5 checksum?

sd_shadow said:
did you verify md5 checksum?
Click to expand...
Click to collapse
How to do that.... i m a noob in android....
Thanks in Advance

sd_shadow said:
did you verify md5 checksum?
Click to expand...
Click to collapse
i dont think its something wrong in the file because i have tried download the file twice and from other websites either

Nothing wrong in md5
sd_shadow said:
did you verify md5 checksum?
Click to expand...
Click to collapse
@sd_shadow i just confirmed the md5 and its the same in the xml.... and when i flash it manualy in fastboot i get the error : Cannot load system.img: Not enough space..
please tell me what to do.... my device is nearly bricked and i have lost all hope

DeXtern00b said:
@sd_shadow i just confirmed the md5 and its the same in the xml.... and when i flash it manualy in fastboot i get the error : Cannot load system.img: Not enough space..
please tell me what to do.... my device is nearly bricked and i have lost all hope
Click to expand...
Click to collapse
try mfastboot
Code:
mfastboot flash system system.img -P

Still no luck
sd_shadow said:
try mfastboot
Code:
mfastboot flash system system.img -P
Click to expand...
Click to collapse
Thats what i got after your command : @sd_shadow
C:\android-sdk-windows\platform-tools>mfastboot flash system system.img -P
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [ 68.798s]
writing 'system'...
OKAY [ 25.042s]
sending 'system' (262144 KB)...
OKAY [ 60.104s]
writing 'system'...
OKAY [ 25.229s]
sending 'system' (262144 KB)...
OKAY [ 35.584s]
writing 'system'...
OKAY [ 24.540s]
sending 'system' (262144 KB)...
OKAY [ 29.200s]
writing 'system'...
OKAY [ 23.672s]
sending 'system' (262144 KB)...
OKAY [ 16.759s]
writing 'system'...
OKAY [ 23.892s]
sending 'system' (7783 KB)...
OKAY [ 0.813s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 334.857s

@sd_shadow is there a way o flash another Os in fastboot like ubuntu or something to unbrick the dev if not then how do i flash android back on it? :/

DeXtern00b said:
@sd_shadow is there a way o flash another Os in fastboot like ubuntu or something to unbrick the dev if not then how do i flash android back on it? :/
Click to expand...
Click to collapse
no
Sent from my KFFOWI using XDA Labs

@sd_shadow then how can i unbrick it

DeXtern00b said:
@sd_shadow then how can i unbrick it
Click to expand...
Click to collapse
try flashing just the boot.img then reboot
Sent from my DROID Turbo using XDA Labs

Still no luck
sd_shadow said:
try flashing just the boot.img then reboot
Sent from my DROID Turbo using XDA Labs
Click to expand...
Click to collapse
No Valid PIV block in SP for system
piv validation failed (system)
Boot up failed @sd_shadow

Soft brick after attempting flashing stock ROM

Hi, just so you know, I am very new to this so please excuse any dumb mistakes I may have done.
I got a stock ROM for my device from LMSA and I am attempting to flash it using fastboot. The first problem I came across while trying to do this, which I still don't know how to fix, is that whenever I try to flash my bootloader with bootloader.img, I get this:
C:\Users\spong\OneDrive\Documents\platform-tools>fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.342s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I've searched online for answers on how to fix it, and I came to threads like this which told me to try to just keep going with the rest of the flashes, which I then tried. After, I tried entering recovery mode. I got a no command error, so I went back to fastboot to try to just start my phone with the start option, in which I got a bootloop where it first, sent me to the Motorola screen for a couple seconds, showed me a warning about my unlocked bootloader, went back to the Motorola screen for 10-20 seconds, then turned my screen black for a second, and started over again. This happens for a long time until, finally, I get an error message saying: (color corresponding)
Boot failed. Press POWER KEY to Retry
Your device didn't start up successfully.
Follow these instructions if the failure cannot be recovered after retrying.
If this is a Verizon device, please use Software Repair Assistant on your computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
If this is not a Verizon device or Software Repair Assistant did not help for any reason, please contact customer care center for further assistant.
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode​
Click to expand...
Click to collapse
I'm using T-Mobile on my device, so it isn't locked to Verizon or using Verizon (my phone is unlocked carrier), so I decided to try to flash boot_a and boot_b with my boot.img:
C:\Users\spong\OneDrive\Documents\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.504s]
Writing 'boot_a' OKAY [ 0.512s]
Finished. Total time: 2.020s
C:\Users\spong\OneDrive\Documents\platform-tools>fastboot flash boot_b boot.img
Sending 'boot_b' (65536 KB) OKAY [ 1.504s]
Writing 'boot_b' OKAY [ 0.506s]
Finished. Total time: 2.014s
Click to expand...
Click to collapse
Doing this changed nothing.
I honestly do not know what to do, since I can't find any help online anywhere for my specific scenario. I found this forum of someone having a really similar problem with me, but they never fixed it and just decided to flash a stock ROM, which is what I was already doing.
Any solution, and I mean any, will help.
Here is the ROM that I was trying to flash, and here is my "fastboot getvar all" txt file.

I have similar issue here. Please if anyone knows how to manage this