[Q] Help? Softbrick, stuck in AP Fastboot: Security Version Downgraded / Boot Failure

Search This thread

DaveTheRave

Member
Sep 29, 2007
19
9
Clovis
Hey guys, I did something really stupid.

I acquired an Atrix HD through a third party, network/sim unlocked it to work on T-Mobile, and tried to flash 4.1.2 Mexican Retail (MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX) through RSD Lite 6.1.5 after removing the getvar command and.. it failed half way. I forgot to unlock the bootloader before flashing.

Now I'm stuck and I've tried almost everything to fix it. I've searched Google and XDA, in the process I have downloaded Myth Tools, sirhoover_atrixhd_utility, motochopper, motopocalypse, and moto-fastboot, tried them all to the best of my knowledge and nothing is working. I've even edited the XML file to exclude the files it fails on.

Common errors I encounter:
Fastboot reason: Boot failure
Fastboot reason: Flash failure
Partition (boot) Security Version Downgraded
Preflash Validation Failed for boot
Partition (system) Security Version Downgraded
PIV black validation for system failed
Invalid PIV image: system


Worst part is, I can't unlock my bootloader because I need ADB to do so! Recovery will give me ADB but only to sideload (available on certain recoveries I've managed to flash). If you have any ideas or information that could assist me in getting my phone back to normal, whether that's unlocking the bootloader through fastboot or flashing a stock rom sucessfully, I would greatly appreciate it! :good:
 

deeje00

Senior Member
Jan 8, 2011
2,078
407
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.

Sent from my PACMAN MATRIX HD MAXX
 

DaveTheRave

Member
Sep 29, 2007
19
9
Clovis
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.

Sent from my PACMAN MATRIX HD MAXX

Thanks for your reply :)

I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img

Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC


I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
 
Last edited:

audit13

Inactive Recognized Contributor
Jun 4, 2012
12,911
5,052
Toronto
Thanks for your reply :)

I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img

Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC


I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..

Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.

Did you try re-downloading the firmware?
 

DaveTheRave

Member
Sep 29, 2007
19
9
Clovis
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.

Did you try re-downloading the firmware?

Just tried re-downloading everything on a brand new Windows install on a different computer, still having problems.

No matter how hard I try, I cannot get boot.img or system.img to flash from any Stock firmware, whether it's AT&T, Mex, or Bell

Using snap-fastboot:

snap-fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)

snap-fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.343s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)


I'm going to try making a Motorola Factory cable in the meantime. Any other suggestions?

EDIT: Factory cable didn't help.. is there a way to generate a higher security version? No matter what, the bootloader always displays Partition (boot/system) Security Version Downgraded
I really don't want this to end up being a paperweight
 
Last edited:

TabascoTX

Senior Member
Jun 13, 2009
422
42
South Central Texas
Redmi 9A
I just got a new Atrix HD replacement and its showing firmware of 9.8.0Q-97_MB886_FFW-20 . Its not the same as the firmware available here: http://sbf.droid-developers.org/ .... I get the same error even after modifying the XML file in the SBF. Wonder if the last update caused an issue. Running into some similar issue with the replacement. Its not wanting to bootloader unlock.
 

akbear78

New member
Jul 10, 2013
1
0
Did you mount the system before installing?

Sent from my SAMSUNG-SGH-I537 using xda app-developers app
 

DaveTheRave

Member
Sep 29, 2007
19
9
Clovis
Sorry I've been MIA, been busy with work.

Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)

1. adb reboot bootloader

2.fastboot oem fb_mode_set

3.fastboot oem fb_mode_clear

3.fastboot erase userdata

4.fastboot erase cache

5.fastboot reboot

Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/

Thanks for the reply! I wished this worked for me. After completing the steps successfully, I get:
Partition (boot) Security Version Downgraded
Fastboot Reason: Boot Failure

Code:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

fastboot oem fb_mode_set
...
OKAY [  0.006s]
finished. total time: 0.006s

fastboot oem fb_mode_clear
...
OKAY [  0.005s]
finished. total time: 0.005s

fastboot erase userdata
erasing 'userdata'...
OKAY [  3.095s]
finished. total time: 3.095s

fastboot erase cache
erasing 'cache'...
OKAY [  1.669s]
finished. total time: 1.669s

fastboot reboot
rebooting...
finished. total time: 0.005s

Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?

Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?

That's exactly where I got my firmwares from. And to answer your question, I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
 
Last edited:
  • Like
Reactions: deelan_chan

Inforc

New member
Apr 17, 2017
1
0
Boot problem

Hello here I have a problem and I made everything from my knowledge but It's not fixed.
I have a Motorola Droid Maxx X8 verison XI1080, version 4.4.4, built number SU4.21,
If I install or do something and I switch off and I turn on my phone it disappears as if it is never done and if I try to reinitialize the phone I have a error Fastboot Reason: Boot Failure
If I get the fastboot and I take recovery its said Boot up failed.
I did everything I flashed with RSD and I update it with Motorola update but still nothing we see that the flashing and the update works but on reboot Its has no effect on the phone its stays as if you did nothing.
Please help me! I look forward to a solution, I thank you more.
 
Last edited:

Waseemahpz

Member
Oct 2, 2017
5
0
have u solved the problem

Please explain how u have solved the problem ,my moto g4 plus in same problems
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Found a fix for the AP Fastboot loop
    List of commands to type in. ( in order)

    1. adb reboot bootloader

    2.fastboot oem fb_mode_set

    3.fastboot oem fb_mode_clear

    3.fastboot erase userdata

    4.fastboot erase cache

    5.fastboot reboot

    Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
    1
    Sorry I've been MIA, been busy with work.

    Found a fix for the AP Fastboot loop
    List of commands to type in. ( in order)

    1. adb reboot bootloader

    2.fastboot oem fb_mode_set

    3.fastboot oem fb_mode_clear

    3.fastboot erase userdata

    4.fastboot erase cache

    5.fastboot reboot

    Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/

    Thanks for the reply! I wished this worked for me. After completing the steps successfully, I get:
    Partition (boot) Security Version Downgraded
    Fastboot Reason: Boot Failure

    Code:
    adb reboot bootloader
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    error: device not found
    
    fastboot oem fb_mode_set
    ...
    OKAY [  0.006s]
    finished. total time: 0.006s
    
    fastboot oem fb_mode_clear
    ...
    OKAY [  0.005s]
    finished. total time: 0.005s
    
    fastboot erase userdata
    erasing 'userdata'...
    OKAY [  3.095s]
    finished. total time: 3.095s
    
    fastboot erase cache
    erasing 'cache'...
    OKAY [  1.669s]
    finished. total time: 1.669s
    
    fastboot reboot
    rebooting...
    finished. total time: 0.005s

    Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?

    Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?

    That's exactly where I got my firmwares from. And to answer your question, I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.