Related
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
I have a Kindle Fire 5th Gen (Fire OS 5.1.1 installed december 9th 2015). When I go into bootloader mode it says fastboot mode, but when I issue the command 'fastboot boot boot.img' this does not work. Does anyone know how to solve this? I used the same method on another Fire (same version) some weeks ago, and there I could boot into TWRP using the same method.
adb reboot bootloader
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.168s
fastboot getvar product
product: FORD
finished. total time: 0.002s
fastboot getvar version
version: 0.5
finished. total time: 0.002s
fastboot devices
G000H40454120K64 fastboot
Best regards,
Leen
toelen said:
I have a Kindle Fire 5th Gen (Fire OS 5.1.1 installed december 9th 2015). When I go into bootloader mode it says fastboot mode, but when I issue the command 'fastboot boot boot.img' this does not work. Does anyone know how to solve this? I used the same method on another Fire (same version) some weeks ago, and there I could boot into TWRP using the same method.
adb reboot bootloader
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.168s
fastboot getvar product
product: FORD
finished. total time: 0.002s
fastboot getvar version
version: 0.5
finished. total time: 0.002s
fastboot devices
G000H40454120K64 fastboot
Best regards,
Leen
Click to expand...
Click to collapse
Can't use this method with FireOS 5.1.1. Try FlashFire.
Davey126 said:
Can't use this method with FireOS 5.1.1. Try FlashFire.
Click to expand...
Click to collapse
Once the device is running a custom rom (mine is on Fire Nexus) and if the device was originally on 5.3.1 then can this method be used to boot into twrp recovery?
jinxt said:
Once the device is running a custom rom (mine is on Fire Nexus) and if the device was originally on 5.3.1 then can this method be used to boot into twrp recovery?
Click to expand...
Click to collapse
Nope - bootloader must be 5.0.x to permit twrp (or any custom recovery) to be booted. Bootloader can not be downgraded. You're stuck with Fastboot, mate.
so you can't use fastboot to chainload twrp on a 1time basis ? making the protected device bootloader irrelevant
i thought thats what ""fastboot boot boot.img "" was doing - chainloading
jinxt said:
so you can't use fastboot to chainload twrp on a 1time basis ? making the protected device bootloader irrelevant
i thought thats what ""fastboot boot boot.img "" was doing - chainloading
Click to expand...
Click to collapse
No. If possible it would have been offered. Bootloader is locked; Amazon crippled fastboot; boot command no longer recognized on v5.1+.
Ok i get it, hence the reason for the FAILED message from OP below:
toelen said:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.168s
Click to expand...
Click to collapse
Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Check your phone box, there is a sticker that should say "XT 1541 retXX" so you know wich region is right for your phone, then download the fw from the filefacory repo http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50 and flash it whit mfastbootV2
PS
Your phone have a dedicated section --> http://forum.xda-developers.com/2015-moto-g
edrpomidor said:
Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Click to expand...
Click to collapse
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
benjausen said:
Use mfastboot v2, and try to flash a firmware FROM THE SAME REGION. Did you change motoboot.img? If so then skip 5.X gpt.bin and motoboot.img flashing.
Click to expand...
Click to collapse
No I didn't
deleted
benjausen said:
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
Click to expand...
Click to collapse
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
edrpomidor said:
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
Click to expand...
Click to collapse
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
benjausen said:
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
Click to expand...
Click to collapse
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
edrpomidor said:
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
Click to expand...
Click to collapse
Try flashing CM12.1 then.
I've had a KFFOWI since Christmas but have been too busy to do anything with it. Unforutnately, this means that it has been updated to 5.1.4. Now I want to see what I can do with it.
I've read many posts on this excellent forum over the past few days about this device. I thought I'd start by trying to load the custom recoveries CM and TWRP.
I have ADB and Fastboot on a Linux box (I don't use Windows at all). I Can put the device into Fastboot mode; the way I do this is to boot to stock recovery and then choose "reboot to bootloader". I verify Fastboot from my Linux prompt like this:
Code:
$ sudo fastboot -i 0x1949 getvar product
product: FORD
finished. total time: 0.002s
I have downloaded the recoveries and try to boot them like this:
Code:
$ sudo fastboot -i 0x1949 boot TWRP_Fire_2.8.7.0_adb.img
downloading 'boot.img'...
OKAY [ 0.256s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.258s
However, as you can see, it does not work. I guess that the bootloader has been updated with one that does not have the boot command.
I also found this thread which would appear to confirm my suspicions but I can't find any more recent information about this.
So is this correct, that it's no longer possible to run a custom recovery like this? Or am I doing something wrong ?
I doubt it, but will downgrading to 5.1.2 fix this?
(I also read the KFFB thread and also this one thread about fastboot, but perhaps it is out of date with respect to this?).
ogpog said:
...So is this correct, that it's no longer possible to run a custom recovery like this? Or am I doing something wrong ?
I doubt it, but will downgrading to 5.1.2 fix this?
Click to expand...
Click to collapse
For the reasons stated in your full post custom recoveries can not be used/booted once FireOS has been updated beyond 5.0.1 via normal OTA (ie: no steps taken to protect bootloader).
As you probably know FlashFire can be used to install custom ROMs and take other actions normally performed in a custom recovery like twrp. However, stock recovery is still the only way to recover the device if the installed rom won't boot or unstable.
I see, so the ability to boot a recovery was lost after 5.0.1. I didn't catch that from my reading. I am working on getting FlashFire up and running but I need to get root first. I won't pollute this thread with my efforts in that regard.
Hi!
Few weeks ago I decided to root my phone, I'll give you a long detail on how it went.
First, I watched a youtube video, and the follow-up video on how to unlock bootloader and root my phone titled [How to Unlock the bootloader on your Huawei Android device P8 Lite]. The bootloader part went simply, other than the fact that my phone already showed PHONE unlocked during the bootloader screen. After that I tried rooting, and that is where the problems began. When I installed SuperSU or other SuperUser, it said that my binary files were missing, reinstall root, nothing worked.
So, I could get rid of it eventually, and I came across KingRoot. It solved most of my problems, I could get root authorization, but few more advanced apps needed "real" root, since the binary file problem came up again. Today I decided to give it another try and use the old method I saw in that video. Here are the commands and the replies I got:
command: fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.0005s]
finished. total time: 0.007s
command: fastboot oem unlock (unl. code)
FAILED (remote: root type is risk)
finished. total time 1.039s
command: fastboot oem relock (unl. code)
FAILED (remote: already fastboot unlocked)
finished. total time: 0.007s
As of now I deleted KingRoot and I wanted to get the root suggested in the MEGA-THREAD, but I'm afraid that something might be up with my phone, since it says that my phone is unlocked, yet I can't get binary su or other apps that require root, not just a fake root provided by KingRoot. Any suggestions?
PS. When using KingRoot I got the green sign from RootChecker, now it's red again, but the bootloader shows "root type at risk." I read somewhere that it's called "soft root," but I'm not sure.
first: supersu it's not to root, it's super user management.
before everything else maybe usefuil a full update with stock rom, to remove every kingroot "part" then follow this tutorial http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 : point 7 (twrp) and point 8 (root)