[Q] Error flashing stock recovery - Moto X Q&A

I'm on a locked, 4.4, non-DE. Rooted using SlapMyMoto .5c and have used MotoWpNoMo. Everything is fine, but I'd like to have the stock recovery back (since SlapMyMoto modified it).
I can flash the boot partition with the boot.img from the SBF, without issue. However, the recovery.img doesn't seem to work.
Code:
C:\Users\user\Desktop\adb>mfastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.960s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.111s
On the phone, I see the error:
Failed to hab check for recovery: 0x56
preflash validation failed for recovery
Click to expand...
Click to collapse
Is there some way around this or do I need to RSD Lite back to 4.2.2, root again and restore?

Not even a sarcastic reply.

theascended said:
Not even a sarcastic reply.
Click to expand...
Click to collapse
OK
Don't you know that just like pwnmymoto, slapmymoto disables recovery in order to disable write protection?
How did I do?
I was not sure of the answer & guessed!
Pretty that is the answer. Pwnmymoto did that to me anyway.

Ha. Not quite sarcastic enough... needs more cow bell.
They don't actually disable recovery. They modify the recovery image so that instead of booting into recovery, WP is simply disabled and the phone boots as normal. My problem is that I can't seem to restore the stock recovery using the tools and images provided through Motorola's website. This also has me concerned that using RSDLite may not even work since RSDLite basically just scripts the installation of the images/partitions in a certain order.
I'm surprised I'm the only person who has hit this (and wants to fix it) given how many people used pwnmymoto, rockmymoto and any version of slapmymoto before the 1.0.

Flashing the (cam) 4²² XML did work for me yet the root solution from there was too much for my old Mac. I wish I had tried the moto x tool kit aio utility.

Also... turns out I may have been wrong about the recovery image being modified... looks like it was the partition table that was modified.
I sucked it up and decided to risk losing my data (since I didn't know what the ramifications to flashing the partition data would be). Flashing gpt.bin seems to have fixed the issue and allowed me to flash the stock recovery. For anyone who isn't familiar with what it is you need to flash and ends up in this thread:
mfastboot flash partition gpt.bin
I didn't lose any data and have noticed no discernible loss in functionality (root or write protect).

not sure what you were trying to do.. but when I see hab check messages when trying to flash, it usually means you've got some miss-matched files/partitions on your phone.
the GPT.BIN has a little to do with security, etc.
Hopefully you are not in a state where you still have miss-matched files, because if you do, and you take an OTA, you could brick.

Indeed, I'm minorly concerned about that too.
I was just trying to restore the original recovery image functionality. No particular reason right now, just wanted to. Like I said before, I rooted using slapmymoto .5C and am on the 4.4 OTA. The files I used to flash (gpt, boot and recovery) were from the 4.4 SBF (VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip). I think I'm covered here, but I'm also not taking the current OTA until its rooted or I can unlock, neither of which seems likely to happen anytime soon.

Related

[SOLVED] Mfastboot assistance (trying to flash TWRP)

having some flashing issues
I can confirm good file download, drivers on PC are good, I'm using a back USB port, USB cable is BRAND NEW! lol, have Write protection off as well. Tried both fastboot and mfastboot just for good measure. Any thoughts? Do I NEED to have an unlocked bootloader for this? please say no
Also the file shows up as a different size on the fastboot screen, it's over 10mb.
C:\Users\Ivan Lee\Downloads\Android\adt-bundle-windows-x86-20131030\sdk\platform
-tools>mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
sending 'recovery' (9854 KB)...
OKAY [ 0.850s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.250s
Click to expand...
Click to collapse
You need a unlocked bootloader to flash twrp. If you are locked then you must use safestrap recovery.
Travisdroidx2 said:
You need a unlocked bootloader to flash twrp. If you are locked then you must use safestrap recovery.
Click to expand...
Click to collapse
Was afraid of that... sucks. Would that mean only certain partitions have R/W access with "MotoWpNoMo"?
No the entire system has r/w access the only difference is you can flash a kernel with an unlocked boot loader. As a matter of fact safstrap is made from twrp they look and function the same. Only difference is SS has ROM slots for kexek kernels. Unlocked bootloaders don't need these slots we can flash just about anything within reason.
If you're on 4.4.2 you won't get root now tho. You'd have had to be rooted before upgrading.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
bigv5150 said:
No the entire system has r/w access the only difference is you can flash a kernel with an unlocked boot loader. As a matter of fact safstrap is made from twrp they look and function the same. Only difference is SS has ROM slots for kexek kernels. Unlocked bootloaders don't need these slots we can flash just about anything within reason.
Click to expand...
Click to collapse
I'll assume by system you mean system partition, I figured that since we can get root on 4.4 Write protection has to be removed from at the very least the system partition. Also, Yeah I know a little about safestrap and it's features but may not bother with it, had 3 Moto-x's so far, all have the same MMS issue so I'm probably def refunding it, that issue aside great phone. also, i don't want to unlock my bootloader (no warranty) especially since Moto's stock firmware has bugs in it.
kj2112 said:
If you're on 4.4.2 you won't get root now tho. You'd have had to be rooted before upgrading.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
No 4.4.2 stuff here. I mentioned having write protection off so I'm def rooted already thanks for the replies guys

[Q] Cannot flash recovery (TWRP)

I just got a Moto X on Sprint, and after successfully unlocking the bootloader, I do not seem to be able to flash TWRP. The flash seems to go ok, but when I boot the device into recovery, its still the stock recovery. Im attempting to use the official openrecovery-twrp-2.7.1.1-ghost.img image. Ive tried using the standard fastboot on OSX and WIn7-64bit, and in both situations I get this output:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.749s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.629s
The variable not supported seems to be the 'getvar partition-type:recovery' command (based on the output on the phone).
I have also tried using the fastboot provided by Motorola with the same output and result. On the forums somewhere I found a link to an older moto-fastboot-osx command, which has slightly different output, but the same results:
Code:
moto-fastboot-osx64 flash recovery openrecovery-twrp-2.7.1.1-ghost.img
sending 'recovery' (8220 KB)... OKAY [ 0.787s]
writing 'recovery'... OKAY [ 0.909s]
What am I doing wrong?
Have you double checked that your oprnrecovery-twrp...img file is not corrupt? Make sure to check it against the md5 checksum.
Yes, I verified the MD5, it is correct.
slushpupie said:
I just got a Moto X on Sprint, and after successfully unlocking the bootloader, I do not seem to be able to flash TWRP. The flash seems to go ok, but when I boot the device into recovery, its still the stock recovery. Im attempting to use the official openrecovery-twrp-2.7.1.1-ghost.img image. Ive tried using the standard fastboot on OSX and WIn7-64bit, and in both situations I get this output:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.749s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.629s
The variable not supported seems to be the 'getvar partition-type:recovery' command (based on the output on the phone).
I have also tried using the fastboot provided by Motorola with the same output and result. On the forums somewhere I found a link to an older moto-fastboot-osx command, which has slightly different output, but the same results:
Code:
moto-fastboot-osx64 flash recovery openrecovery-twrp-2.7.1.1-ghost.img
sending 'recovery' (8220 KB)... OKAY [ 0.787s]
writing 'recovery'... OKAY [ 0.909s]
What am I doing wrong?
Click to expand...
Click to collapse
Just a few thoughts...forgive me if any of this sounds redundant, or obvious....
Just reading your initial post, I would assume that you had used one of the previous root exploits and/or Safestrap BEFORE you got the BL unlocked. If so, it would be necessary to flash the entire stock SBF, before you would be able to successfully flash TWRP recovery........but your OP says you JUST got the phone, which would lead me to believe you didn't use a previous root exploit. Did you receive it NEW? Because the original owner could certainly have used exploit/safestrap.
If any of this is possible, you should follow the "Return to Stock" thread (manual method is suggested - easier and faster) and flash the entire Sprint 4.4.2 SBF. THEN you should be able to successfully flash TWRP. As I have often stated, a full SBF to stock can actually REPAIR a corrupted / modified (exploit / safestrap) filesystem. A "Factory Reset" does not repair any corruption that may be present.
2nd thought: I've seen some people confuse the "bootloader" screen (AP Fastboot Mode) for recovery. From the bootloader screen, you have to arrow down to highlight recovery, and press volume up to boot into recovery.
Alternatively, you can do it from fastboot: just type fastboot reboot-recovery
Let us know if any of this is relevant or solves your issue. If everything else fails, doing a full SBF back to stock fixes all issues nearly 100% of the time.
Good Luck
samwathegreat said:
Just a few thoughts...forgive me if any of this sounds redundant, or obvious....
Just reading your initial post, I would assume that you had used one of the previous root exploits and/or Safestrap BEFORE you got the BL unlocked. If so, it would be necessary to flash the entire stock SBF, before you would be able to successfully flash TWRP recovery........but your OP says you JUST got the phone, which would lead me to believe you didn't use a previous root exploit. Did you receive it NEW? Because the original owner could certainly have used exploit/safestrap.
Click to expand...
Click to collapse
It was purchased used, and the original owner was not very tech savy, so I assumed it was fully stock (it appeared so at first glance, anyway).
samwathegreat said:
If any of this is possible, you should follow the "Return to Stock" thread (manual method is suggested - easier and faster) and flash the entire Sprint 4.4.2 SBF. THEN you should be able to successfully flash TWRP. As I have often stated, a full SBF to stock can actually REPAIR a corrupted / modified (exploit / safestrap) filesystem. A "Factory Reset" does not repair any corruption that may be present.
Click to expand...
Click to collapse
Ill give this a try and report back. Perhaps there is something weird going on in there...
samwathegreat said:
2nd thought: I've seen some people confuse the "bootloader" screen (AP Fastboot Mode) for recovery. From the bootloader screen, you have to arrow down to highlight recovery, and press volume up to boot into recovery.
Alternatively, you can do it from fastboot: just type fastboot reboot-recovery
Let us know if any of this is relevant or solves your issue. If everything else fails, doing a full SBF back to stock fixes all issues nearly 100% of the time.
Good Luck
Click to expand...
Click to collapse
Im familiar with Android enough to know the difference between the bootloader and recovery, but thanks for making sure.
slushpupie said:
It was purchased used, and the original owner was not very tech savy, so I assumed it was fully stock (it appeared so at first glance, anyway).
Ill give this a try and report back. Perhaps there is something weird going on in there...
Im familiar with Android enough to know the difference between the bootloader and recovery, but thanks for making sure.
Click to expand...
Click to collapse
Haha, yes, I was hesitant to suggest there may be confusion between bootloader and recovery.... Glad you were on top of that one...
The return to stock thread is located here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Again, manual method is easier and faster.
You will flash the 4.4.2 Sprint SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
If my first theory was correct, you wouldn't be the first person who received a used phone that had an exploit used on it. The devs make it pretty easy even for not-so-tech-savvy people with all the "one-click" rooting scripts and the like. Often times, the seller just assumes that a "factory reset" will un-do the modifications, but in the case of the Moto X (with all the Write Protect-disable exploits and safestrap), the modifications actually persist through a factory reset.
samwathegreat said:
Haha, yes, I was hesitant to suggest there may be confusion between bootloader and recovery.... Glad you were on top of that one...
The return to stock thread is located here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Again, manual method is easier and faster.
You will flash the 4.4.2 Sprint SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
Well, I followed the directions and it seemed to flash ok. Booted it up, wanted to activate (I canceled that- I dont have service on the phone yet), everything seemed normal. Went back to flash TWRP, same behavior as before. Any other ideas?
slushpupie said:
Well, I followed the directions and it seemed to flash ok. Booted it up, wanted to activate (I canceled that- I dont have service on the phone yet), everything seemed normal. Went back to flash TWRP, same behavior as before. Any other ideas?
Click to expand...
Click to collapse
A couple more: some individuals have reported that they had issues using a USB 3.0 port. If possible, use a USB 2.0 port to flash the recovery.
If you flashed ALL the partitions in the SBF file starting with gpt.bin (basically manually executed the commands in the XML file, IN ORDER), it -should- have worked.
You might also try flashing twrp from a different PC...
OR
You can try flashing TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
This version is confirmed to work on all versions up to and including 4.4.2, so as long as you aren't on 4.4.3 yet, you can give this a shot.
And lastly, since I don't know exactly where you got the mfastboot binary, be sure to try the mfastboot binary linked in the 'return to stock' thread. That one is confirmed to work.
2 suggestions:
- try a different TWRP - I'm using a 2.7 that is referred to in one of the threads here
- after flashing > use the volume down button to highlight boot to recovery, and the volume up button to select (execute) that command ... my first time I tried the power button to select it and that doesn't work. I experienced some strange issues when trying to flash recovery if I didn't immediately boot into recovery (don't power down).
jasoraso said:
2 suggestions:
- try a different TWRP - I'm using a 2.7 that is referred to in one of the threads here
Click to expand...
Click to collapse
Ive tried a few, but will see if I can find some more to try. There seems to be no negative to trying them at this point.
jasoraso said:
- after flashing > use the volume down button to highlight boot to recovery, and the volume up button to select (execute) that command ... my first time I tried the power button to select it and that doesn't work. I experienced some strange issues when trying to flash recovery if I didn't immediately boot into recovery (don't power down).
Click to expand...
Click to collapse
The volume-key navigation is familiar to me (Ive had Android devices going back to the Samsung Moment), and I wasnt sure if I was getting into recovery or not since it just booted normally when I select recovery from the boot menu. However, when I specifically boot to recovery with 'adb reboot recovery' I get the tell-tale "No command" screen indicating I still have stock recovery.
slushpupie said:
Ive tried a few, but will see if I can find some more to try. There seems to be no negative to trying them at this point.
The volume-key navigation is familiar to me (Ive had Android devices going back to the Samsung Moment), and I wasnt sure if I was getting into recovery or not since it just booted normally when I select recovery from the boot menu. However, when I specifically boot to recovery with 'adb reboot recovery' I get the tell-tale "No command" screen indicating I still have stock recovery.
Click to expand...
Click to collapse
If you boot into stock recovery on Moto X, it shouldn't say "No command".... It should show "Dead Andy" - the broken android with the exclaimation point.
Are you trying to do this while android is booted? If so, unplug the USB, turn off the phone. Now hold down VOL DOWN and turn it back on. You should be on the bootloader screen (AP Fastboot mode). Plug the USB back in now
(^ I realize you probably already know the procedure, but good to have it here for others that might visit this thread)
Now VOL DOWN to recovery and VOL UP to boot it
What happens? Do you see Dead Andy?
I just tested the procedure on my phone (after flashing stock recovery back). After I select recovery and VOL UP to boot it, it takes less than 10 seconds for Dead Andy to appear. Pressing VOL UP + POWER brings up the stock recovery menu: reboot, apply update, wipe cache, etc. etc.
EDIT: I also just tried rebooting from within android as you stated you had done. After typing adb reboot bootloader, the phone promptly booted to the Dead Andy Stock Recovery screen.
Nowhere did it say "no command" on either the device itself, or the command prompt from which the adb command was executed...
samwathegreat said:
A couple more: some individuals have reported that they had issues using a USB 3.0 port. If possible, use a USB 2.0 port to flash the recovery.
Click to expand...
Click to collapse
My MacBook Pro only has USB3.0 ports. I would expect an issue to show some error, though (like in the transfer). It seems everything transfers just fine; it just doesn't seem to take.
samwathegreat said:
If you flashed ALL the partitions in the SBF file starting with gpt.bin (basically manually executed the commands in the XML file, IN ORDER), it -should- have worked.
Click to expand...
Click to collapse
It appeared the full SBF flashing process worked. It reset everything and prompted me for activation.
samwathegreat said:
You might also try flashing twrp from a different PC...
Click to expand...
Click to collapse
I dont really have anything different to try. Ive got another MBP, but its pretty much identical, and I get the same results when I try there. I have several VMs I can try- Ive tried with Win7-64bit (as mentioned in the original post) but that was the same too. I could try Linux too, if I get the time to set one up, but my gut says it wont be any different.
samwathegreat said:
You can try flashing TWRP 2.6.3.1 from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
This version is confirmed to work on all versions up to and including 4.4.2, so as long as you aren't on 4.4.3 yet, you can give this a shot.
Click to expand...
Click to collapse
Since I just reflashed back to the stock image, it is 4.4.2. Ive tried this version as well, with the same result.
samwathegreat said:
And lastly, since I don't know exactly where you got the mfastboot binary, be sure to try the mfastboot binary linked in the 'return to stock' thread. That one is confirmed to work.
Click to expand...
Click to collapse
Being on a Mac makes this a bit more challenging, but yes, I did try this in my Win7 virtual machine with the same results.
samwathegreat said:
If you boot into stock recovery on Moto X, it shouldn't say "No command".... It should show "Dead Andy" - the broken android with the exclaimation point.
Are you trying to do this while android is booted? If so, unplug the USB, turn off the phone. Now hold down VOL DOWN and turn it back on. You should be on the bootloader screen (AP Fastboot mode). Plug the USB back in now
(^ I realize you probably already know the procedure, but good to have it here for others that might visit this thread)
Now VOL DOWN to recovery and VOL UP to boot it
What happens? Do you see Dead Andy?
Click to expand...
Click to collapse
Yes, I see the dead andy image, with the no command message below him.
No, I am doing this from the bootloader. When I attempt to load recovery from the bootloader, I see the white unlocked warning image, then it goes and boots normally. Once into Android, I can issue 'adb reboot recovery' and that's when I see dead andy with the no command message. Confused yet? Cause I am.
samwathegreat said:
I just tested the procedure on my phone (after flashing stock recovery back). After I select recovery and VOL UP to boot it, it takes less than 10 seconds for Dead Andy to appear. Pressing VOL UP + POWER brings up the stock recovery menu: reboot, apply update, wipe cache, etc. etc.
EDIT: I also just tried rebooting from within android as you stated you had done. After typing adb reboot bootloader, the phone promptly booted to the Dead Andy Stock Recovery screen.
Nowhere did it say "no command" on either the device itself, or the command prompt from which the adb command was executed...
Click to expand...
Click to collapse
Im really at a loss then.. Ill try to restore the stock images again. Maybe I missed something the first go around.
slushpupie said:
Im really at a loss then.. Ill try to restore the stock images again. Maybe I missed something the first go around.
Click to expand...
Click to collapse
I suggest a slight variation:
After you extract the entire SBF file to the same folder where mfastboot resides:
First, boot to bootloader. Next, issue the following commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Device should reboot right back to bootloader. Now issue these commands (we are going to use mfastboot for ALL commands, and YES, we are repeating gpt and motoboot again. this is intentional):
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem config carrier sprint
mfastboot oem fb_mode_clear
mfastboot reboot
Lets see if we can flash TWRP now. I helped another user on a MAC with a similar issue, and this resolved it for him. I'm hopeful we will fix your issue as well.
samwathegreat said:
I suggest a slight variation:
After you extract the entire SBF file to the same folder where mfastboot resides:
First, boot to bootloader. Next, issue the following commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Device should reboot right back to bootloader. Now issue these commands (we are going to use mfastboot for ALL commands, and YES, we are repeating gpt and motoboot again. this is intentional):
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
<...>
Lets see if we can flash TWRP now. I helped another user on a MAC with a similar issue, and this resolved it for him. I'm hopeful we will fix your issue as well.
Click to expand...
Click to collapse
That did it, thanks! I wonder what is going on that I had to flash partition and motoboot twice. In any event, Im off and running. Thanks again!
slushpupie said:
That did it, thanks! I wonder what is going on that I had to flash partition and motoboot twice. In any event, Im off and running. Thanks again!
Click to expand...
Click to collapse
GPT stands for GUID Partition Table.
We aren't quite sure why this method works with stubborn flashes, but this is the theory:
We think that if the partition table somehow gets corrupted, the bootloader enforces write protection (on some or all partitions) even if you are unlocked...
The trick is to just flash the partition table, and the bootloader images, then immediately reboot, so the bootloader can load the NON-Corrupt partition table. Once the system reboots, all subsequent partition flashes seem to 'stick' without issue. It seems to involve some sort of 'bug' in the write protection implementation.
Regardless, once it is fixed, so is the issue. You shouldn't need to double-flash any partitions after rebooting like we did this time. AFAIK, all the users who got fixed using the above procedure have reported no further problems.
Just remember to never flash a previous version of android without checking here first. Most users who have to undergo the above procedure tried to downgrade for some reason, and many of them ended up having to do the procedures listed in the "Unbrick" thread (Not fun...)
Glad it all worked out.
samwathegreat said:
GPT stands for GUID Partition Table.
We aren't quite sure why this method works with stubborn flashes, but this is the theory:
We think that if the partition table somehow gets corrupted, the bootloader enforces write protection even if you are unlocked...
The trick is to just flash the partition table, and the bootloader images, then immediately reboot, so the bootloader can load the NON-Corrupt partition table. Once the system reboots, all subsequent partition flashes seem to 'stick' without issue. It seems to involve some sort of 'bug' in the write protection implementation.
Click to expand...
Click to collapse
Makes sense. Given that the bootloader is the one area you cant easily fix if you screw up, I would add as much protection as possible too. Of course, I would also add error messages... Makes me wonder if there is some hard coded entries in the event the GTP gets screwed up. Has anyone attempted to inspect the gpt.bin file?
samwathegreat said:
Regardless, once it is fixed, so is the issue. You shouldn't need to double-flash any partitions after rebooting like we did this time. AFAIK, all the users who got fixed using the above procedure have reported no further problems.
Just remember to never flash a previous version of android without checking here first. Most users who have to undergo the above procedure tried to downgrade for some reason, and many of them ended up having to do the procedures listed in the "Unbrick" thread (Not fun...)
Glad it all worked out.
Click to expand...
Click to collapse
Good to know. I dont plan on doing anything fancy, just want root for TI backups, really. I guess Ill see how well flashing the bootloader works again when the 4.4.3 OTA comes around to my phone.

Trouble restoring PE to stock KitKat

Unfortunately I loaded the leaked Lollipop build to my PE and it was working great, but I wanted to get on the soak test build. I downloaded the stock KK 4.4.4 system image from Motorola in order to restore before updated to soak test. All but one of the files flashes fine, the exception being motoboot.img. I get Preflash validation failed error for that file.
The phone boots and runs but the missing file means the update won't install. Does anyone have any thoughts on how to restore this file?
TMO_21.21.42.victara_tmo.tmo.en.US>mfastboot flash boot motoboot.img
target max-sparse-size: 256MB
sending 'boot' (2022 KB)...
OKAY [ 0.089s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.109s​
samabuelsamid said:
Unfortunately I loaded the leaked Lollipop build to my PE and it was working great, but I wanted to get on the soak test build. I downloaded the stock KK 4.4.4 system image from Motorola in order to restore before updated to soak test. All but one of the files flashes fine, the exception being motoboot.img. I get Preflash validation failed error for that file.
The phone boots and runs but the missing file means the update won't install. Does anyone have any thoughts on how to restore this file?
TMO_21.21.42.victara_tmo.tmo.en.US>mfastboot flash boot motoboot.img
target max-sparse-size: 256MB
sending 'boot' (2022 KB)...
OKAY [ 0.089s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.109s​
Click to expand...
Click to collapse
try:
Code:
mfastboot flash motoboot motoboot.img
holtenc said:
try:
Code:
mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Sorry, copy/paste error there.
I actually tried the motoboot motoboot.img too and get the same error.
well I'm not sure then man. I guess all I can suggest is follow THESE instructions to a T.
also if you have flashed any of the radios floating around these forums insert "fastboot flash modem radio.img" in there somewhere.
And of course make sure your bootloader is unlocked.
holtenc said:
well I'm not sure then man. I guess all I can suggest is follow THESE instructions to a T.
also if you have flashed any of the radios floating around these forums insert "fastboot flash modem radio.img" in there somewhere.
And of course make sure your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks, those are precisely the instructions I used. I haven't done anything with the radios. I flashed the leaked lollipop rom and then used the official image files to try to go back. The bootloader was initially not unlocked, I unlocked it only in an attempt to get the motoboot file to flash. Now I can't relock it because this part of the image is missing.
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
holtenc said:
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
Click to expand...
Click to collapse
Only thing I did with bootloader locked was the partition. As soon as I got to the motoboot and it failed, I figured I would need to unlock and did that. Since then, I've tried the whole process a couple of times with the same result. I will however, give it another shot.
You don't need motoboot to update. Go use the script and it will do everything for you.
tw1tch175 said:
You don't need motoboot to update. Go use the script and it will do everything for you.
Click to expand...
Click to collapse
Which script is that?
samabuelsamid said:
Which script is that?
Click to expand...
Click to collapse
My multitool in development section has stock restore included
holtenc said:
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
Click to expand...
Click to collapse
bhp090808 said:
My multitool in development section has stock restore included
Click to expand...
Click to collapse
Downloading V4.1 now, thanks
bhp090808 said:
My multitool in development section has stock restore included
Click to expand...
Click to collapse
I flashed with the multitool and was able to get back where I started with the leaked PE lollipop version but something is still missing because I can't relock the bootloader.

[Q] Issues with Recovery

I have a motorola X 2014 Pure Edition that a while ago i side loaded the Lollipop Soak test image, however since it wasn't the final, it appears that I was instructed to downgrade back to 4.4.4 and then I would be able to upgrade to 5.0-11. I downloaded the Factory image from Motorola and re-flashed the images onto my phone. However when I attempted to refresh the motoboot.img it failed with the error below. However all the other parts flashed alright without issues. I then booted my phone and it booted into Kit Kat. I then attempted to do the OTA upgrade for Lollipop but it fails and puts the phone into a endless reboot phase. When I try to go into Recovery Mode it doesn't work, i get to the broken android screen however I cannot get to the Recovery Menu at all.
I reached out to Motorola support and they said: "We can not help you with this issue. I recommend you post this on forums dedicated to this (aka XDA), it should be fairly easy to find someone to help you there. here is not issue with the Moto X 444 BL. it seems to me it is related to the "stock Android 4.4.4" you flashed on your phone. It looks like you have a mismatch somewhere between TZ, GPT and the version of the BL on this device; it might have been cause by what you flashed on the device before having to return to stock.. .. "
I'm at a loss right now other than trying to send my phone back to Motorola to see if they can fix it. Hoping someone might have an idea of what i can do to fix my issue??
% ./fastboot flash motoboot motoboot.img
14-12-04 - 14:25:59
target max-sparse-size: 256MB
sending 'motoboot' (2022 KB)...
OKAY [ 0.073s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.143s
Any help would be appreciated.
hey bro seems like the image might be corrupted. Try finding another motoboot.img. Or Lock and Unlock your bootloader again. And best of all try to get in fastboot and go back kitkat and keep it that way. Because i don't think you want to be in a brick again. Consult a person here on XDA that knows more about it. Thats my advice.
Sending it back won't work, your warranty is gone. Clearly stated in the page where you unlocked the bootloader. Sorry bro.
And btw next time please post this in the Moto X section.
Thank you! Greetz ErixGamer

[Stock ROM][Applied 1 October OTA Update]Trying to get TWRP custom recovery flashed

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.

Categories

Resources