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] How to relock the bootloader!?!?

I have decided to post a new thread as all the other threads on this are not for my phone.
I try to do what bootloader says which is 'fastboot oem lock begin' but I get stuck.
It says afterwards:
Code:
...
<bootloader> Ready to flash signed images
OKAY [ 0.476s ]
finished. total time: 0.479s
But what are the signed images?
So I skip flashing the 'signed images' and go ahead and type: 'fastboot oem lock' and it gives me this error:
Code:
...
<bootloader> Re-Lock Failure. See display.
OKAY [ 0.644s ]
finished. total time: 0.667s
So, I look at the display and it says:
Code:
Fastboot Reason: Reboot to bootloader
fastboot: max download size: 100MB
USB connected
Fastboot command failed
OEM lock
OEM lock begin
Getvar partition-type:recovery
Fastboot command failed
Getvar max-download-size
OEM lock
E:No valid PIV block in SP for cdrom
E:piv validation failed (cdrom)
E:Falied to validate piv objects
Re-lock failure
Somebody please help me!! I have been trying to search for my phone's stock rom for days without success! PLEASE HELPPP!!!!

If you only want to go back to stock-firmware, you don't have to relock your bootloader. You only have to flash the stockimage with RSD-Lite.
But if you really want to relock:
http://forum.xda-developers.com/showpost.php?p=44430691&postcount=4
Firmwares fro our Razr I:
http://sbf.droid-developers.org/phone.php?device=13

ICuaI said:
If you only want to go back to stock-firmware, you don't have to relock your bootloader. You only have to flash the stockimage with RSD-Lite.
But if you really want to relock:
http://forum.xda-developers.com/showpost.php?p=44430691&postcount=4
Firmwares fro our Razr I:
http://sbf.droid-developers.org/phone.php?device=13
Click to expand...
Click to collapse
Thank you. It did work but I want to know, how do you tell when it is locked?
Also, I have already tried to go back to stock firmware using RSD-Lite but I don't know where to find the needed file...If you can help with that, I would be very grateful.
Thank you,
GoldenPaul27

Do you have to change the downloaded file extension so it doesn't have the .zip on the end of it?

GoldenPaul27 said:
Do you have to change the downloaded file extension so it doesn't have the .zip on the end of it?
Click to expand...
Click to collapse
No, the is zipped. You have to unzip this file first.

HTML:
ICuaI said:
No, the is zipped. You have to unzip this file first.
Click to expand...
Click to collapse
OK. I shall try this. Thank you for your help so far.

nice
I wanted this 2, tks!!

Just another question:
How do you tell when the bootloader is relocked??

Did anyone successfully able to solve this problem?

START (Green)
Restart bootloader (Red)
Recovery mode (Red)
Power off (White)
Press voluse key to select, and press power key to select.
FASTBOOT MODE (Red)
PRODUCT_NAME - msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - 9fbc1152
SECURE BOOT - enabled
DEVICE STATE - locked
I have used (http://www.androidbrick.com/unbrick-oneplus-one-two-3-3t-qualcomm-hs-usb-qdloader-9008/) MSMDownload Tool, this (http://www.technobuzz.net/unbrick-oneplus-3/) tool and (https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/) this MSMDownloadTool, they all showed “Download Complete”. And then my boots to fastboot mode with message mentioned above.
I can not go to recovery mode which is asked in one plus download support (http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.6/)
In fastboot mode if I give any command from Command Prompt it says Not Allowed since OEM is Locked

If you can boot android you need to go into developer options (tap 7 times in the build in Settings/about). IN developer options enable the Allow OEM unlock options and then just use the fastboot command to unlock bootloader. *fastboot oem unlock*

Jahdiel2011 said:
If you can boot android you need to go into developer options (tap 7 times in the build in Settings/about). IN developer options enable the Allow OEM unlock options and then just use the fastboot command to unlock bootloader. *fastboot oem unlock*
Click to expand...
Click to collapse
Nope. I can't boot android. I am stuck at fastboot mode only with no recovery mode.

lukesh9923 said:
Nope. I can't boot android. I am stuck at fastboot mode only with no recovery mode.
Click to expand...
Click to collapse
Is the device recognized in fastboot mode?

Jahdiel2011 said:
Is the device recognized in fastboot mode?
Click to expand...
Click to collapse
Yes. (btw I have tried "fastboot oem unlock" in command prompt it say remote oem unlock not allowed.

Have you tried this unbrick tutorial?
https://forum.xda-developers.com/on...k-unbrick-tutorial-oneplus-3t-t3515306/page41

qbanlinxx said:
Have you tried this unbrick tutorial?
https://forum.xda-developers.com/on...k-unbrick-tutorial-oneplus-3t-t3515306/page41
Click to expand...
Click to collapse
Yes I did.

Have you used the unoffical OnePlus 3t toolkit?

Some details on how you ended up in this predicament might be useful to those trying to help.

OcazPrime said:
Have you used the unoffical OnePlus 3t toolkit?
Click to expand...
Click to collapse
Are you referring to MSMDownloadTool V 3.0?

Check this video https://youtu.be/jCgldi9Upes

I have uploaded a video. If someone can see and help me here https://youtu.be/jCgldi9Upes

Well since you have fastboot, why don't you try flashing stock recovery? Then you could flash a full rom zip from there if it worked. That or make sure you are using the right files for your device in the unbrick tool.
Edit: Nevermind. Your bootloader is locked so idk.
Edit2: Does your PC recognize the device as being in fastboot?
Sent from my OnePlus 3T using XDA Labs

Fastboot boot recovery "filename" (download recovery from oneplus)..
than flash latest full zip and reboot... (adb sideload "filename"
---------- Post added at 09:41 AM ---------- Previous post was at 09:38 AM ----------
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3t.img

MrMeeseeks said:
Well since you have fastboot, why don't you try flashing stock recovery? Then you could flash a full rom zip from there if it worked. That or make sure you are using the right files for your device in the unbrick tool.
Edit: Nevermind. Your bootloader is locked so idk.
Edit2: Does your PC recognize the device as being in fastboot?
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Yes my laptop do recognize my phone while it is connected in fastboot mode

oTeMpLo said:
Fastboot boot recovery "filename" (download recovery from oneplus)..
than flash latest full zip and reboot... (adb sideload "filename"
---------- Post added at 09:41 AM ---------- Previous post was at 09:38 AM ----------
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3t.img
Click to expand...
Click to collapse
C:\adb>fastboot boot recovery recovery_op3t.img
cannot load 'recovery': No such file or directory.
C:\adb>fastboot flash recovery recovery_op3t.img
target reported max download size of 442499072 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.741s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.765s

lukesh9923 said:
Yes my laptop do recognize my phone while it is connected in fastboot mode
Click to expand...
Click to collapse
Try fastboot oem unlock
Sent from my OnePlus 3T using XDA Labs

MrMeeseeks said:
Try fastboot oem unlock
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
C:\adb>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
I have tried it before as well.

lukesh9923 said:
C:\adb>fastboot boot recovery recovery_op3t.img
cannot load 'recovery': No such file or directory.
C:\adb>fastboot flash recovery recovery_op3t.img
target reported max download size of 442499072 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.741s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.765s
Click to expand...
Click to collapse
Ups
Fastboot boot recovery_op3t.img
Sent from my ONEPLUS A3003 using Tapatalk

oTeMpLo said:
Ups
Fastboot boot recovery_op3t.img
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
C:\adb>Fastboot boot recovery_op3t.img
downloading 'boot.img'...
OKAY [ 0.727s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.759s

Help!!, frp locked bootloader locked

So what happend is i wanted to get oreo on my pra la1 so i re branded it to al00c chinese version (after unlocking my bootloader)
using the al00c oem file , i flash d it in twrp and then i wanted google play services which is not there in chinese version so i unlocked bootloader again and flashed oreo twrp and then flashed pra lx1 oem info and i did not dload the lx1 software:crying: so stupid of me now i m running chinese software on lx1 and without google play now my frp and bootloader is locked. now when i try dload it goes to 5% and says system update failed . WHAT DO I DO NOW TO GET PRA LX1C432 OREO??
THANX IN ADVANCE

Try Firmware finder for huawei + erecovery method , which is :
- download firmware finder on *another android phone* and search for exact phone model (ex : PRA-LA1C185)
- choose the very first firmware down the list
- Get an update thorugh dns >> Manually >> Register update
- After that , reboot your bricked phone into erecovery by ( power + volume*+*)
- press download recovery and last firmware
- wait till getting package
- by now should firmware start downloading
- let phone complete it's work and reboot
Hope that's work for you ?

I have the bootloader unlocked via DC Unlocker. Must pay 3,99€ because it's okay.
NOW: I want flash twrp via adb-fastboot and it comes
FAILED (remote: partition length get error)

EgonsS said:
I have the bootloader unlocked via DC Unlocker. Must pay 3,99€ because it's okay.
NOW: I want flash twrp via adb-fastboot and it comes
FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Have you tried this command ? fastboot flash recovery_ramdisk xxx (recovery image name)

I don't understand why there isn't any one who can develop something that can push the img files with fastboot without restriction like it's done by dc phoenix
---------- Post added at 08:16 PM ---------- Previous post was at 08:13 PM ----------
victoriordachi said:
Have you tried this command ? fastboot flash recovery_ramdisk xxx (recovery image name)
Click to expand...
Click to collapse
this is what this pra-la1 fastboot reply
C:\adb>fastboot flash recovery_ramdisk TWRPprague311.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24468 KB)...
OKAY [ 0.894s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.905s​

RAR1991 said:
I don't understand why there isn't any one who can develop something that can push the img files with fastboot without restriction like it's done by dc phoenix
---------- Post added at 08:16 PM ---------- Previous post was at 08:13 PM ----------
this is what this pra-la1 fastboot reply
C:\adb>fastboot flash recovery_ramdisk TWRPprague311.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24468 KB)...
OKAY [ 0.894s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.905s​
Click to expand...
Click to collapse
Try this recovery https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 . 0.2 test build . Install using the same command

victoriordachi said:
Try this recovery https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 . 0.2 test build . Install using the same command
Click to expand...
Click to collapse
thanks for the interest but like always.
C:\adb>fastboot flash recovery_ramdisk TWRPprague311.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24468 KB)...
OKAY [ 0.937s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.953s​

victoriordachi said:
Have you tried this command ? fastboot flash recovery_ramdisk xxx (recovery image name)
Click to expand...
Click to collapse
FAILED (remote: partition error)

So I was digging on my phone and I was able to put it in recovery mode it shows USB logo with 5 % and adb devices command give that result
E:\>adb devices
List of devices attached
PSEDU17315000315 recovery​if anyone can get something from that

Hassan__12 said:
So what happend is i wanted to get oreo on my pra la1 so i re branded it to al00c chinese version (after unlocking my bootloader)
using the al00c oem file , i flash d it in twrp and then i wanted google play services which is not there in chinese version so i unlocked bootloader again and flashed oreo twrp and then flashed pra lx1 oem info and i did not dload the lx1 software:crying: so stupid of me now i m running chinese software on lx1 and without google play now my frp and bootloader is locked. now when i try dload it goes to 5% and says system update failed . WHAT DO I DO NOW TO GET PRA LX1C432 OREO??
THANX IN ADVANCE
Click to expand...
Click to collapse
Try this:
fastboot flash recovery xxx(name of recovery).IMG.
It's the old nougat command. Might work. Depends on what partition scheme your device has. Give it a shot. Likely won't but you can try.

Got same issue yesterday. After some i got a length partition issue.
I did the full OTA from eRecovery. Now i'm on PRA-LX1 8.0.0.368 C02 (NOT C432).
I should try again (i believe my device is now totally stable - i think i flashed bad rom with HuRUpdater...) and see if i can flash a TWRP (certainly 3.2.1 Oreo) with fastboot flash recovery_ramdisk twrpfile.img
Will let you know.

hello colleagues need your help huawei PRA-LA1 on the screen only huavei write how the bootloader will unlock me

Question Help installing LineageOS on Pixel 5a5g (Can't unlock)

Hey all, new poster but long time user of the site, just never needed an account until today lol. Anyways, just got a Pixel 5a5G that I am trying to install LineageOS on. I am following the instructions from here, and once I get to the point of flashing the vendor_boot partition, I receive this:
Code:
PS C:\Windows\system32> fastboot flash vendor_boot C:\Users\bobby\Downloads\vendor_boot.img
target reported max download size of 268435456 bytes
sending 'vendor_bootb' (98304 KB)...
OKAY [ 2.225s]
writing 'vendor_bootb'...
FAILED (remote: Not allowed to flash (vendor_bootb))
finished. total time: 2.307s
When running fastboost unlock bootloader, I receive this:
Code:
PS C:\Windows\system32> fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.055s]
finished. total time: 0.056s
I have reflashed the stock firmware with the Android Flashing Tool to 13.0.0, both keeping the bootloader locked and unlocked. I have tried unlocking and relocking the bootloader. I used the utility's "full-flash" feature to flash both partitions, all to no avail. Research on here seems to point that the bootloader is locked, but fastboot says it isn't, settings is greyed out saying the bootloader is already unlocked, and fastboot mode on the phone says Device state: unlocked.
Any ideas?

Did you remove your screenlock and Google account before flashing?

Leberkuchen said:
Did you remove your screenlock and Google account before flashing?
Click to expand...
Click to collapse
Yes. I've flashed from a factory install with no passcode or account ever set. Same issue

From the output it's trying to write vendor_bootb??? Some combination of this should fix it:
-Make sure to use platform tools r33.0.3, the latest r34 has at least one known problem with fastboot and I don't trust it
-If you're using powershell you have to run the command as .\fastboot flash you can only run fastboot flash if you are in cmd
-Make sure both slots are on latest February firmware (probably not really necessary but a last ditch effort)