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
Hi,
I was trying to flash my phone to 5.1 and I think I screwed up and ran a command I wasn't supposed too.
Now I can't do anything because I keep getting rejection messages with: (bootloader) Preflash validation failed.
I think the command that screwed me over was the: fastboot flash partition gpt.bin
I'm willing to flash back down to 5.0.1. However I don't know how and looking around the sites I'm getting confused as nothing is working for me.
My model is XT1097.
Am I completely screwed? If not. How do I get out of this mess?
Locatus said:
Hi,
I was trying to flash my phone to 5.1 and I think I screwed up and ran a command I wasn't supposed too.
Now I can't do anything because I keep getting rejection messages with: (bootloader) Preflash validation failed.
I think the command that screwed me over was the: fastboot flash partition gpt.bin
I'm willing to flash back down to 5.0.1. However I don't know how and looking around the sites I'm getting confused as nothing is working for me.
My model is XT1097.
Am I completely screwed? If not. How do I get out of this mess?
Click to expand...
Click to collapse
Now when I reboot my phone it comes up with:
"Version downgraded for boot"
"Failed to validate boot image"
"Fastboot Reason: Fall-through from normal boot mode"
Edit:
It seems to be failing to flash in the system, boot, and recovery files
I tried to upgrade from Android M preview 3 to 6.0 Marshmallow using the flash-all.bat.
There were error messages and the phone would not boot into recovery.
I went back to fastboot to flash files one at a time.
When I try to flash bootloader it fails with the "Preflash validation error" message.
Is this telling me that I can't flash the bootloader because it was already flashed during the (unsuccessful) flash-all.bat?
Can I flash the other files to get the phone back to working order?
Hi, I have the same issue. Were you able to flash the new bootloader?
I've read and heard from several people that the flash-all.bat doesn't work correctly. I'd recommend flashing the .img files separately.
Hi there,
a friend asked me for help with restoring his german Moto G 2014 (XT1068). The last working software on the device was the Marshmallow update. He was having software issues and softbricked the device when trying to install a custom ROM.
Fastboot mode and stock recovery is accesible, the bootloader is unlocked and the device is stuck on the "WARNING: BOOTLOADER UNLOCKED" screen when trying to boot normally.
I have tried following this guide to revert the phone back to stock firmware with a matching system image. Both the XT1068_TITAN_RETDE_6.0_MPB24.65-34-3_cid7_CFC and XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC images will flash without any error messages. However, the device does not boot the new software. Also, when trying to relock the bootloader, the mfastboot oem lock command failes with the error message Not supported command in current status!. I tried to substitute mfastboot with fastboot, changed USB cables and downloaded new copies the images, with no success.
Digging deeper, I found out that I could not wipe cache or data using the stock recovery. This will fail with the error message blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed. Further troubleshooting attempts lead me to try twrp custom recovery software (Version 3.1.1) which I could only start using the mfastboot boot twrp-3.1.1-0-titan.img command since flashing the image as custom recovery will not fail but the phone instantly and silently reverts to stock recovery - even when not rebooting inbetween. Consequently, any attempts to flash an image using the software will fail with E1001: Failed to update system image.
At this point, I have no idea what else I could try. That's why I turn to you, great community of XDA .
Any help would be greatly appreciated.
Hello. So, I got my Moto G5s Plus around the last week of October or beginning of November. It is a great device, but I learned about the camera flaws by Motorola and unlocked the bootloader to fix it by following this XDA thread here for camera fixing and the Chromatix mod. I learned that I could edit build.prop without flashing the TWRP recovery but using it temporarily following the guide here. build.prop edit would enable cam2api for third party cam apps. The Chromatix mod threads/posts were for the G5 Plus, which I didn't realize at the time and didn't backup original Chromatix files. However, That went successfully and I could still use my phone with better camera quality. Note that prior to doing this fix and before unlocking the bootloader (I believe) I had updated my device from Nougat to Oreo. My bootloader is indeed unlocked.
Now, when the 1 October OTA Update came I was hesitent because I had came across some rooting/custom rom/custom recovery/mod articles while learning about unlocking the bootloader. Yet and before reading more to get educated on this, I applied the update to my phone. I was hoping it wouldn't brick it or that it would fail if it didn't work. It failed (because of the modification on the stock ROM) at the last bit of the update and rebooted my phone. My phone worked and it let me know nothing was changed by the failed update. However, my phone since then has shown as if it is up-to-date in system updates.
So, basically I have been trying to flash TWRP for my Moto G5s Plus after that was done. I want to see about backing up my stock ROM (or the most important parts) possibly getting a good custom ROM installed (which I believe they have their own official Android security updates from Google?). However flashing TWRP hasn't worked. I get the following in PowerShell (cmd):
PS C:\Android SDK\platform-tools> fastboot flash recovery twrp.img
Sending 'recovery' (10236 KB) OKAY [ 0.407s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.172s]
Finished. Total time: 0.594s
Note that I renamed twrp-3.1.1-sanders.img to twrp.img as it was a suggestion I followed at the time. This I heard is normal, but when I go to Recovery Mode on my phone I see this:
Start Up Failed:
Repair message stuff
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
~~~
Error: failed to load kernel!
~~~
I also tried to find the latest stock ROM to flash because I believe I read I may need to do that. I found SANDERS_RETAIL_8.1.0_OPSS28.65-36-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and tried to use "Apply update from ADB" from the stock Recovery (when it was working normally after powering off and not with kernel errors because of this). It failed.
I couldn't find the right answer(s). Thank you to anyone that can help me or others who have done the same!!
EDIT (11/19/2018):
So, last night I tried wiping my data in stock recovery and then I tried to do this again. It still didn't work. I also tried to apply the same stock zip as well as boot_magisk.img from this thread here https://forum.xda-developers.com/moto-g5s-plus/development/stock-kernel-prerooted-8-1-0-t3863301.
PS C:\Android SDK\platform-tools> fastboot flash boot boot_magisk.img
Sending 'boot' (10702 KB) OKAY [ 0.391s]
Writing 'boot' (bootloader) Image not signed or corrupt
OKAY [ 0.141s]
Finished. Total time: 0.563s
It all still fails. However, now when I boot up my phone it goes straight to the bootloader instead of loading the OS right away. I can select START to start the phone normally from there.
I got all this resolved through XDA's Telegram group (& specific group for G5s Plus/sanders)! I have TWRP (Treble) and custom rom working after getting an official stock rom from them flashed using fastboot commands!
I don't know if I should or a mod can close/erase this thread now?
Try typing fastboot oem fb_mode_clear while in bootloader
Coala990 said:
Try typing fastboot oem fb_mode_clear while in bootloader
Click to expand...
Click to collapse
Thanks for the suggestion/tip. I will probably try that if I reflash twrp treble (or another version of twrp for Sanders) again. This has been resolved.