[Q] XT1064 Lollipop ota assert failed, installation aborted [Update: Solution Found] - G 2014 Q&A, Help & Troubleshooting

I have a Consumer Cellular XT1064 running 21.11.17.titan_retuaws.retuaws.en.US.na with an unlocked bootloader and am having trouble applying the lollipop ota upgrade patch. When I attempt to apply the patch in stock recovery, I get an error durning "Patching system files". The error reads "assert failed: apply_patch(*/system/framework/framework-res.apk" followed by a series of letters and numbers, and ultimately ending with "installation aborted".
I previously successfully applied the ota and was running Lollipop using this guide. While attempting to root, I couldn't get twrp to persist after a full boot nor could I successfully install supersu, so I decided to start from scratch (probably a bad move) and followed those same steps again, but this time ran into the assert failed error described above. I tried re-locking the bootloader, thinking that may help, but got error messages during the process, so that's a no-go. I've scoured the forums and web for another solution, but haven't come up with anything so far.
Maybe there are some files/settings that aren't being completely restored to 4.4.4 stock through the manual flashing process? I can't get RSD Lite to recognize this phone (even though it recognizes my Droid Maxx just fine).
Any other thoughts or suggestions would be much appreciated.

Solution for XT1064 assert failed errors when applying Lollipop ota
After much trial and error, I successfully found a way to get rid of the assert failed errors and get back to Lollipop. Thanks to diamondjoker5, I obtained the original retail firmware 21.11.23 and used fastboot commands to flash it over the 21.11.17 firmware. I then let the phone fully boot into 21.11.23, powered off, then followed the original ota update procedure once again, without any errors.

Related

[Q] Error Failed to Validate System image

Good day
I was trying to update my 2014 Moto G XT1068 from (Kitkat) 4.4.4 to 5.0.2 (Lollipop)
from following this link
http://forum.xda-developers.com/moto-g-2014/general/official-lollipop-indian-ota-captured-t3002674
Now forgive cause I am new to rooting etc, when I did try and root the phone using the global firmware, my sim was disable. So I decided to use differnet firmware with resulted in sim card not getting signal. So I end up using the Brazilian update for the firmware, and ended up having the phone in AP Fastboot Flash Mode with the error is " Error Failed to Validate System Image"
I have tried using different firmware to get back the phone to work, but to no luck, I am asking what steps can I take now to try and fix my problem.

Error sideloading lolipop for XT1053

To be safe, I completely reverted to stock 4.4.4. I made sure to flash the correct image with RSD Lite (TMO_RETAIL_XT1053_4.4.4_213.44.1_MR4_CFC.xml)
So my system and recovery should be completely stock.
I then tried to sideload this: http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864
But It does not work. I get the following error during "Verifying current system. . . " :
"/system/etc/install-recovery.sh" has unexpected contents.
Installation aborted.
WTF?
OK, reflashed 4.4.4 again and now its working. Dunno what happened!

Error updating Nexus 6 to 6.0.1

Hi all, new to the forums here. Sorry if this is in the wrong section. So I was trying to update my nexus 6 to 6.0.1 from 6.0 and I got this error
supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing Update...
Source: google/shamu/shamu:6.0/MRA58K/2256973:user/release-keys
Target: google/shamu/shamu:6.0.1/MMB29K/2419427:user/release-keys
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:8393958:28495c2ab9b8a2210fc396d8af35c29bc885fce9:8398054:bb5e73e0be23e9709b0acfd83db5c62140" has unexpected contents
E: Error in @/cache/recovery/block.map
(Status 7)
Installation aborted
Now I looked up status 7 errors and how to fix, but none had pertained to my particular issue, so I figured I'd check before doing anything drastic. For some info, I have rooted, unlocked bootloader, flashed a custom recovery and rom, but when Marshmallow came out, I flashed stock image for 6.0 to my phone through nexus root toolkit, which removed custom recovery, flashed to stock, but kept bootloader unlocked. So now I'm on clean stock 6.0 and I received the OTA and I tried to install it and this is the message I get. Any ideas on how to get my phone to update? Oh, and BTW if it matters, I'm on T-Mobile. Thanks in advanced!
First of all, don't rely on toolkits, it's really easy to do those steps yourself using fastboot.
Also it says that your boot.img is not stock, or stock enough, so you should reflash everything again, including boot, if you are really after the OTA. But at this point why are you trying to use the OTA, when you could just update to 6.0.1 byt flashing the boot.img and system.img, and radio. You clear cache and dalvik. and when it finishes rebooting and optimizing applications you'll have your 6.0.1.
istperson said:
First of all, don't rely on toolkits, it's really easy to do those steps yourself using fastboot.
Also it says that your boot.img is not stock, or stock enough, so you should reflash everything again, including boot, if you are really after the OTA. But at this point why are you trying to use the OTA, when you could just update to 6.0.1 byt flashing the boot.img and system.img, and radio. You clear cache and dalvik. and when it finishes rebooting and optimizing applications you'll have your 6.0.1.
Click to expand...
Click to collapse
Hey, that would be great! The only problem is I'm not particularly skilled in that field lol. Does the boot.img, system.img and radio come from the stock factory image, or do I have to download those separately? And would I install those with a particular program? Thanks, sorry for being such a noob
It's in the factory package mmb29k. Download it, and extract it, you'll have the bootloader, the radio, and a zip file with all the rest. You don't need the bootloader, it hasn't changed since the marshamllow preview. Extract the files from the zip file, then flash radio, boot.img and system.img.
For flashing you need fastboot, but the toolkit already installed it, it just calls it when you push buttons.
As for the flashing, everything is explained in the pinned post.

Failed OTA update MarshMallow XT1068

My phone is Moto G 2014 XT1068 Dual SIM with 5.02 Lollipop. The phone is unlocked but unrooted. I received the OTA notification for upgrading to MM. The process failed. Recovery mode was "no command available" (in Italian). So I installed TWRP recovery instead. The OTA prompt aimed at updating to MM reappared. After have Launched the updating process, the phone entered in TWRP recovery displaying the following error message:
"Package expects build fingerptint of motorola/titan_retaildsds/titan_umtsds:5.0.2/LXB22.99-16.3/5:user/release-keys or motorola/titan_retaildsds/titan_umtsds:6.0/MPB24.65-34/31:user/release-keys; this device has Motorola/omni_titan/titan:5.1.1/LYZ28J/2:eng/test-keys.
Updater process ended with ERROR: 7
Error installing zip file '/cache/Blur_Version.22.56.3.titan_retaildsds_retaildsdsall.en.03.zip
Done processing script file
MTP Enabled".
Any suggestion to allow OTA update to work properly?
Thank in advance.
---------------------------
I have solved the problem reinstalling Stock Lollipop 5.0.2. I now guess that the problem derived from the fact that I had changed the logo to avoid the annoying warning about the risks of having the phone unlocked.
Hope this may be helpful for those that have done a similar change in their phone.

Problem installing 1st december OTA

Hi everybody,
This morning I received the notification about the OTA update on my phone (new build: NPW26.7, software channel reteu), that is unlocked and rooted.
The problem is that the update fails everytime, even after I flashed the stock system image.
I tried also installing the OTA with adb-sideload, but it fails and the output is:
Code:
Opening update package...
Verifying update package...
Installing update...
Step 1/2Error applying update: 20 (ErrorCorde::kDownloadStateInitializationError)
E:Error in /sideload/package.zip
(Status 1)
I was wondering: is it possible that the update fails even if the system is stock, just because the bootloader is unlocked? Basing on my past experience, it should work anyway.
Or maybe I'm just receiving the wrong package? The OTA filename is Blur_Version.26.51.2.payton.retail.en.US.
Any ideas?
Ok, the issue was that, having rooted the phone, all the partitions - somehow - changed. In fact, taking a look at the logcat, it gave that "kDownloadStateInitializationError" after comparing the hash for the actual and expected partitions.
So I had to reflash all of them (partition, bootloader, modem, bluetooth, dsp, logo, boot, system, system_b and oem) to get it working.

Categories

Resources