Database Develop

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

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:

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

deeje00 said:
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
Click to expand...
Click to collapse
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..

DaveTheRave said:
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..
Click to expand...
Click to collapse
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?

audit13 said:
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?
Click to expand...
Click to collapse
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

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?

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.

Did you mount the system before installing?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app

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/

Sorry I've been MIA, been busy with work.
TabascoTX said:
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/
Click to expand...
Click to collapse
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
audit13 said:
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?
Click to expand...
Click to collapse
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.

DaveTheRave said:
...I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
Click to expand...
Click to collapse
Try logging off and back on to see what happens. For me, using fastboot/adb commands on an x86 Win7 machine works more consistently than using an x64 Win7 machine.

TabascoTX said:
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/
Click to expand...
Click to collapse
When I run fastboot oem fb_mode_set, it just says "< waiting for any device >"

Sorry for the late reply. make sure you have adb installed and the drivers for the Atrix. Also,if possible and not in a boot loop or stuck in fastboot, device debugging should be enabled.

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.

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

[Q] TWRP fastboot boot problem

I have a VZW dev edition with unlocked bootloader and running 4.4.2. I would like to boot (not flash) into TWRP to install SuperSU so that I can keep the stock recovery installed, but I get this error in both mfastboot and the regular fastboot:
C:\platform-tools>fastboot boot twrp-2.6.3.1-ghost-4.4.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.953s
I'm running windows 8.1 and the unlocking process went without a problem.
It also doesn't work if I try: fastboot boot recovery twrp-2.6.3.1-ghost-4.4.img
Any ideas?
Thanks

Aeroman787 said:
I have a VZW dev edition with unlocked bootloader and running 4.4.2. I would like to boot (not flash) into TWRP to install SuperSU so that I can keep the stock recovery installed, but I get this error in both mfastboot and the regular fastboot:
C:\platform-tools>fastboot boot twrp-2.6.3.1-ghost-4.4.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.953s
I'm running windows 8.1 and the unlocking process went without a problem.
It also doesn't work if I try: fastboot boot recovery twrp-2.6.3.1-ghost-4.4.img
Any ideas?
Thanks
Click to expand...
Click to collapse
your trying this the hard way. power down phone
hold volume - and power till you get into the bootloader and then hit volume - till you highlight recovery then hit volume + and presto your in recovery.
enjoy

Aeroman787 said:
I have a VZW dev edition with unlocked bootloader and running 4.4.2. I would like to boot (not flash) into TWRP to install SuperSU so that I can keep the stock recovery installed, but I get this error in both mfastboot and the regular fastboot:
C:\platform-tools>fastboot boot twrp-2.6.3.1-ghost-4.4.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.953s
I'm running windows 8.1 and the unlocking process went without a problem.
It also doesn't work if I try: fastboot boot recovery twrp-2.6.3.1-ghost-4.4.img
Any ideas?
Thanks
Click to expand...
Click to collapse
Just flash TWRP, and you install root and SU and you're done. then reinstall stock recovery, seems like the simplest way to do it if what you tried is failing. Just don't forget you're rooted in case OTA comes your way.

The Moto X doesn't support booting just the recovery image like a Nexus device, unfortunately. All the posts I've read have indicated as such, yet to see anyone having successfully done so.
I'd do the same if I had a dev edition. I still don't understand why it doesn't support something so simple which should be available to any unlocked bootloader.

opps i did not understand what you was asking there is a simple way to do this.
Install TWRP with the mfastboot command then install SuperSU
then get the stock recovery img from the correct SBF zip and flash it also with the mfastboot command.
and presto root with stock recovery.

[Q] TWRP Tries to load but fails

Hi, I have an htc one m7 verizon. I am currently running nusense 7.8. I wanted to update to v8.0. Anyway I go to recovery from the menu and the screen goes black like it is going to the team win logo but it goes back to the white screen that says entering recovery. It stays on that screen until I power plus volume down. I am confused because twrp loaded fine. I have tried cwm as well. no recovery software will load. The phone boots to nusense 7.8 fine. Anyone know what would cause recovery software not to load?

Try flashing the latest version of TWRP through Fastboot to see if the issue resolves. Make sure you use TWRP for the Verizon M7.

MarkBell said:
Try flashing the latest version of TWRP through Fastboot to see if the issue resolves. Make sure you use TWRP for the Verizon M7.
Click to expand...
Click to collapse
I agree re-flash TWRP for Verizon
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
fastboot erase cache
fastboot reboot-bootloader

Thanks for throwing up the link clsA. I was about to do that a minute ago when my phone died. Lol.

I will give twrp 2.8.0.1 a try. I have tried several versions but not that one.

fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
fastboot erase cache
fastboot reboot-bootloader[/QUOTE]
I tried the above and I am still getting stuck with the white screen green htc logo and entering recovery at the top. I am happy with nusense 7.8 except for youtube not working. I do have some backups that are useless when twrp will not load. Maybe it is time to ruu this phone.

I installed the ruu VZW.M7.5.28.605.2.PN0731IMG.zip. It installed ok. I am still s off and rooted. I used flashify to flash twrp 2.8.0.1. My phone still will not load a recovery app.......I wonder if this is a hardware issue?

Anybody have any ideas? everything on my phone works accept the ability to load the recovery software. Like I said I was able to install an RUU file with fastboot. I would really like to get twrp working so I can backup and restore again.

I think I found my issue. I am pretty sure my recovery partition is hosed. The command fastboot format recovery fails. I get this message:
Formatting is not supported for filesystem with type 'raw.
Anybody know how to rebuild a corrupted recovery partition?

vaping redhead said:
I think I found my issue. I am pretty sure my recovery partition is hosed. The command fastboot format recovery fails. I get this message:
Formatting is not supported for filesystem with type 'raw.
Anybody know how to rebuild a corrupted recovery partition?
Click to expand...
Click to collapse
recovery partition is a raw partition, the only EXT4 partitions are /system, /cache, and /data
can you copy/paste your command prompt output as you do the fastboot commands that clsA gave you.

nkk71 said:
recovery partition is a raw partition, the only EXT4 partitions are /system, /cache, and /data
can you copy/paste your command prompt output as you do the fastboot commands that clsA gave you.
Click to expand...
Click to collapse
Here you go.
c:\adb>fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9596 KB)...
OKAY [ 1.071s]
writing 'recovery'...
OKAY [ 0.862s]
finished. total time: 1.935s
c:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.511s]
finished. total time: 0.512s
c:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.041s
I have tried flashify, and also an ruu version of twrp. still no go.

Have you tried turning s on, relocking bootloader, running RUU, doing factory reset in Stock recovery and then unlocking and installing TWRP? It is worth a shot I assure you. I had problems with TWRP about a month back and this solved it for me.

Installing twrp recovery from MacOS...

Hi,
Just got a used Tmobile LG G4 which had stock Marshmallow on it already. Have a working ADB setup on my Mac. Trying to follow these instructions from another post:
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
fastboot boot twrp-2.8.7.1-h811.img (phone boots TWRP)
The oem unlock command worked, I can just make out (if I squint!!) when i boot to bootloader mode that the bootloader is unlocked.
When I try fastboot boot twrp...img, I get the following output:
creating boot image...
creating boot image - 14723072 bytes
downloading 'boot.img'...
OKAY [ 0.433s]
booting...
FAILED (remote: dtb not found)
Any suggestions, am I doing something incorrectly?

Can't flash recovery (remote:not allowed)

Hi guys I have a problem now when trying to flash custom recovery using adb fastboot this log always appear:
fastboot flash recovery recovery.img
sending 'recovery' (10704 KB)...
OKAY [ 0.341s]
writing 'recovery'...
#FAILED (remote: Command not allowed)
finished. total time: 0.345s
SO,I dialed *#*#7378423#*#* and I found that my bootloader is unlocked
then I USED sony flash tool and flashed official 4.4.2 then tried and nothing
WIPED EVERY THING then flashed official 5.1.1 and tried to flash recovery and nothing happened
so I ROOTED 5.1.1 by KINGOROOT and dowloaded flashify then when tried to flash recovery.img it gives me message (recovery partition not found) and so are the boot (boot partition not found)
what can I do help please !

No one can fix my problem?!!

I just did it .....same problem like you. I rename the recovery img to boot.img then flash it to boot.img . Then it boot up twrp.

tllim73 said:
I just did it .....same problem like you. I rename the recovery img to boot.img then flash it to boot.img . Then it boot up twrp.
Click to expand...
Click to collapse
But thus I will flash boot not recovery, I know it will work because I did that but the orginal problem isn't solved