Related
Hi, I have a friend who currently has
Android Recovery System <2e> on his droid. Wanting to know if there's a way to change from that to Amons? Also, while using the <2e> any zip he tries to install comes up with the error E: Can't open /cache/recovery/command
If he scrolls down to Apply sdcard: update.zip he gets:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification fialed
Installation aborted.
This happens when trying to open .zip's such as Evil Eris 2.0 or any other zip. I have Amon's recovery and these zips work fine for me.
Any and all help is appreciated. Thanks in advance.
was anything changed within the .zip files?... because if so that will cause it. Also i know if you rename the .zip file you will also recieve the problem because they signed with that specific name. Otherwise, i suggest deleting it from you SD and downloading the .zip again and do a wipe data/dalvik and reflash. But remember to do a nand backup! Lemme know what you get....
No files/names have been changed. If I could get Amon's recovery I could mod his phone for him. I have Amon's and do not have this issue. It is prbably something I am not doing due to being unfamiliar with the recovery he has. Basicaly I think all I really need is a way to get his recovery to read Amon's and I'm good.
andrew8806 said:
was anything changed within the .zip files?... because if so that will cause it. Also i know if you rename the .zip file you will also recieve the problem because they signed with that specific name. Otherwise, i suggest deleting it from you SD and downloading the .zip again and do a wipe data/dalvik and reflash. But remember to do a nand backup! Lemme know what you get....
Click to expand...
Click to collapse
Are you certain about that, or is that unique to that specific recovery menu?
I rename my update.zip's and ROM's after they've been signed and don't run into issues.
If his phone is rooted just download rom manager from the market, open it, scroll all the way to the bottom and hit flash alternative recovery.
That should do it.
.mak said:
Are you certain about that, or is that unique to that specific recovery menu?
I rename my update.zip's and ROM's after they've been signed and don't run into issues.
Click to expand...
Click to collapse
I change the name of update.zip and it always fails to verify.
I have a GTab2 10.1, rooted with Odin.
After rooted, I opened Rom Manager, and see the Icon ClockworkMod: tapped, and oh, Rom Manager Installed versione 6.0.1.1
Then I see CyanogenMod icon, 9 and 10. I checked both, started download, Gtab rebooted but installation was aborted with an error
E:Can't open /sdcard/ clockworkmod /download/get.cm/get/jenkins/7108/cm-9.1.0-p5110.zip
(No such file or directory)
Installation aborted.
Continued manually, and the file WAS there, in the propher path.
Tryed to flash it, but another error
E:Error in /emmc/sdcard/clockworkmod/download/get.cm/get/jenkins/7108/cm-9.1.0-p5110.zip
Status 7
* * *
ok, tried another path, using the nice tutorial posted in
http://forum.xda-developers.com/showthread.php?t=1786828
I downloaded the propher file cm-10-2012-08-29-NIGHTLY-p5110.zip, but same error.
So prolly I'm missing something, but what?
bock2 said:
I have a GTab2 10.1, rooted with Odin.
After rooted, I opened Rom Manager, and see the Icon ClockworkMod: tapped, and oh, Rom Manager Installed versione 6.0.1.1
Then I see CyanogenMod icon, 9 and 10. I checked both, started download, Gtab rebooted but installation was aborted with an error
E:Can't open /sdcard/ clockworkmod /download/get.cm/get/jenkins/7108/cm-9.1.0-p5110.zip
(No such file or directory)
Installation aborted.
Continued manually, and the file WAS there, in the propher path.
Tryed to flash it, but another error
E:Error in /emmc/sdcard/clockworkmod/download/get.cm/get/jenkins/7108/cm-9.1.0-p5110.zip
Status 7
* * *
ok, tried another path, using the nice tutorial posted in
http://forum.xda-developers.com/showthread.php?t=1786828
I downloaded the propher file cm-10-2012-08-29-NIGHTLY-p5110.zip, but same error.
So prolly I'm missing something, but what?
Click to expand...
Click to collapse
1.
Have you tried to install the CM file from CWM Recovery.
I think it could be a compatibility-issue between Galaxy Tab 2 and ROM Manager.
Had the same problem as you,but it worked through CWM Recovery.
2.
You could try moving the CM file to the external memory and try flashing it from there to see if the problem persists.
Maybe it's because CWM Recovery is unable to flash the file from internal memory.
INSTRUCTIONS
First time installing CyanogenMod 9/10 to your Galaxy Tab 2, or coming from another ROM:
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM9/10 ZIPs to your internal SDCard
- Boot into Recovery
- Flash CM9/10 zip from internal SDCard
- Flash GApps zip from internal SDCard
- DO A DATA WIPE / FACTORY RESET
- Reboot
- Don't restore Apps using Titanium Backup!
Upgrading from earlier version of CyanogenMod 9/10:
- Copy CM9/10 ZIP to your internal SDCard
- Boot into Recovery
- Flash CM9/10 zip from internal SDCard
- Reboot
Click to expand...
Click to collapse
Do it like that and you will never have any problems, Download from the threads provided. Follow the instructions to the letter and you cant go wrong. If you are not sure of anything ASK first and someone will help you out.
:laugh:
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Thanks for this. Will try now.
Worked great. Had to copy the apk and odex file.
Good job! It's great to see the steps for Windows users!
Just a heads up that I simply extracted the files I needed from and on my N7 using Root Explorer, without using my PC at all.
Great guide! Method worked perfectly on my Nexus 7 going from 4.1.2 to 4.2, thanks
Please... is there some other way to update the files w/o installing Java on my Windoze PeeCee? I accidentally messed up my YouTube.apk with Titanium Backup... now I can't update from 4.1.2 --> 4.2 JB.
EDIT: JavaPortable FTW... updating (fingers crossed)
EDIT: SUCCESS TY OP!
For anyone who flashed the 4.2 clock/keyboard already
Hey, for anyone who flashed the 4.2 clock and keyboard on their Nexus 7 already and need to roll back to do the 4.2 update, I used OP's method to make a flashable zip that puts the 4.1.2 clock and keyboard back.
Worked perfectly for my Nexus 7 to get me up and running. Hope it helps anyone!
cantthinkofa.com/files/RestoreClockKeyboard.zip
galaxy nexus
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Nice Guide
perfect, the guide works just fine. Now finally running 4.2.
Awesome guide... Thanks... Happily running 4.2 now aften beeing stuck at libutils.so...
Sent from my Nexus 7 using xda premium
damagno said:
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Click to expand...
Click to collapse
I don't have a Galazy Nexus, but I think the steps should be the same. Here is a link to the factory images: https://developers.google.com/android/nexus/images#takju . It looks like they now have links for older versions, rather than just the newest images (which is how it was when I made my guide). So that's pretty sweet.
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1.
Click to expand...
Click to collapse
I was wondering if you could tell me how you did it? I'm searching a way to install 4.2.1 with no avail as of yet :crying:
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
Click to expand...
Click to collapse
Yes. I am having the same issue. I cannot update mine from 4.2 to 4.2.1. I wonder to know which original stock image you have used. Can you list a detail procedure?
Thank you very much.
Ric
dev/block/param
legom said:
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Click to expand...
Click to collapse
my error 7 was generated by emmc: dev/block/mmdblk0p7 (the file is "param" any suggestions?
Thanks. After searching for a lot of time, this post helped me updating my SGS3.:victory: I previously tried to integrate youtube update into rom using titanium backup.
GallStones said:
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual)
Click to expand...
Click to collapse
Yes, that's what I mean. The reason I didn't want to do this on my device is because I had modified some other system files that I wanted to keep the modifications for.
Wow, thanks a lot OP! Your guide helped me fixing an error during the update to 4.2.2 on my Nexus 4.
please include a video ,im getting lost in the details
solved.
There is a lot of problems installing updates atm. I am currently stuck in CMW because none of the CM 10.1 roms will flash.
Here is what happens:
Status 7 (if I dont modify the script)
Installation aborted (if I have modified the script)
I know we can edit the script file and delete the device check and or the format of /system. But for me, it is not working. I have tried many editors (on OS X) but the finished zip is always 0.3 MB bigger than the original, making me suspect that its saving the script file wrong.
So if any one could link me a .zip they have used, I would be very grateful!
Here's the OTA zip extracted from 5.1 XT1527. Fully unmodified.
It patches a lot of system apps, modem and gpt.
https://mega.nz/#!ixpQyRYI!OSIzlz8OOp3VChQGSkOW-f9gdy87g6cGQZiE4MeaUrI
PsyClip-R said:
Here's the OTA zip extracted from 5.1 XT1527. Fully unmodified.
It patches a lot of system apps, modem and gpt.
https://mega.nz/#!ixpQyRYI!OSIzlz8OOp3VChQGSkOW-f9gdy87g6cGQZiE4MeaUrI
Click to expand...
Click to collapse
asks encryption key ... it is impossible to download without introducing
---------- Post added at 12:04 ---------- Previous post was at 12:02 ----------
ENRIQUEMM said:
asks encryption key ... it is impossible to download without introducing
Click to expand...
Click to collapse
Now if, after modifying the link.
Thank you
ENRIQUEMM said:
Now if, after modifying the link.
Thank you
Click to expand...
Click to collapse
Yep, I've fixed that.
Let me know if you will install it.
You patch this update yourself ?
I am leery about running it.. it patches everything you can imagine.
xpmule said:
You patch this update yourself ?
I am leery about running it.. it patches everything you can imagine.
Click to expand...
Click to collapse
Nope. Cuz I'm usin' XT1527 firmware on XT1524. So my recovery and modem are different. Thus I can't install this update.
It's untouched. Factory package, extracted from /cache partition.
ahh ok thanks
i seen it downloaded OTA to that folder on my XT1527 device too.
what about Bootloader concerns guys ?
people are talking about that on the stock firmware topic
and they linked to this topic..
and i guess just open TWRP and flash it then right ?
xpmule said:
ahh ok thanks
i seen it downloaded OTA to that folder on my XT1527 device too.
what about Bootloader concerns guys ?
people are talking about that on the stock firmware topic
and they linked to this topic..
and i guess just open TWRP and flash it then right ?
Click to expand...
Click to collapse
Actually You need fully untouched (factory origin) partitions, ie. recovery, firmware, radio, boot etc.
There shouldn't be any problem with unlocked bootloader.
if you need a stock phone then you have to use the ADB-Side Load method then right ?
and the release notes are vague from Moto
EDIT:
i can confirm the file posted on Mega is the same as the OTA update from Moto.
I got both just now and hex compared them.. using BeyondCompare (HEX)
xpmule said:
i can confirm the file posted on Mega is the same as the OTA update from Moto.
I got both just now and hex compared them.. using BeyondCompare (HEX)
Click to expand...
Click to collapse
Thanks for help. So now guys may download and flash without worries.
ya i guess i am running a different modem too.
hmm this is getting complicated hahah
at first i thought you could do a flash like i seen guys doing on a Moto G tutorial..
they backed up all with TWRP then installed stock recovery + stock firmware etc.
then connected to PC with adb fasttools and flashed it that way (have not used that method yet)
that means you put phone into fastboot connection mode and connect with stock recovery.
then the update is flashed over usb while the update is on your PC.
and in the tutorial the guy then re-flashed TWRP and restored back his data.
BUT !
This update patches every single stock apk and pretty much every aspect of the system.
including the modem !
so if you did restore your old modem then it's not patched.
and some of us have a 5.0.2 modem so hmmm
maybe it would be ok (security wise) if the 5.0.2 modem was stage fright patched too ?
When I Trying to INtall the update From TWRP got this error:
Processing OpenRecoveryScript file...
I:command is: 'install'
I:value is: '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'auto'
I:Trying to find zip '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip' on '/data/media/0'...
I:Looking for zip at '/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/data/media/0/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/data/media/0/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Trying to find zip '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip' on '/external_sd'...
I:Looking for zip at '/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/external_sd/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Installing zip file '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Installing '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
installing gptupgrade updater extensions
file_contexts path is present in /tmp/file_contexts
mount point :/system location: /dev/block/bootdevice/by-name/system , file system type :ext4script aborted: Package expects build fingerprint of motorola/surnia_retus/surnia_umts:5.1/LPI23.29-15/19:user/release-keys or motorola/surnia_retus/surnia_umts:5.1/LPI23.29-18.9/4:user/release-keys; this device has motorola/omni_surnia/surnia:5.1.1/LYZ28E/squid207132027:userdebug/test-keys.
Package expects build fingerprint of motorola/surnia_retus/surnia_umts:5.1/LPI23.29-15/19:user/release-keys or motorola/surnia_retus/surnia_umts:5.1/LPI23.29-18.9/4:user/release-keys; this device has motorola/omni_surnia/surnia:5.1.1/LYZ28E/squid207132027:userdebug/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
E:Error installing zip file '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Done processing script file
read what i said before.about "test-keys"
your phone was flagged.
the update knows you have custom content and refused the install
it seen you have root/super su or have a custom kernel or rom etc.
How to apply the update manually?
Hi,
I have the xt1524 bought from retail in Europe (Germany). I managed to upgrade it to stock xt1527 retus 5.1, but the stagefright update keeps on failling to install. I have the motorola drivers and adb and fastboot, also unlocked the bootloader. How can I apply this update manually?
Thanks in advance!
tomoff said:
Hi,
I have the xt1524 bought from retail in Europe (Germany). I managed to upgrade it to stock xt1527 retus 5.1, but the stagefright update keeps on failling to install. I have the motorola drivers and adb and fastboot, also unlocked the bootloader. How can I apply this update manually?
Thanks in advance!
Click to expand...
Click to collapse
You simply can't install this OTA on 1524 hardware.
I suppose you use 1524 modem and other partitions. The script updates every of these partitions.
At first it asserts partitions software, and of course it fails.
If only smb wills to modify the script.
jgomez-m said:
When I Trying to INtall the update From TWRP got this error:
Processing OpenRecoveryScript file...
I:command is: 'install'
I:value is: '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'auto'
I:Trying to find zip '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip' on '/data/media/0'...
I:Looking for zip at '/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/data/media/0/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/data/media/0/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Trying to find zip '/storage/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip' on '/external_sd'...
I:Looking for zip at '/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/external_sd/sdcard1/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
I:Looking for zip at '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Installing zip file '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Installing '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
installing gptupgrade updater extensions
file_contexts path is present in /tmp/file_contexts
mount point :/system location: /dev/block/bootdevice/by-name/system , file system type :ext4script aborted: Package expects build fingerprint of motorola/surnia_retus/surnia_umts:5.1/LPI23.29-15/19:user/release-keys or motorola/surnia_retus/surnia_umts:5.1/LPI23.29-18.9/4:user/release-keys; this device has motorola/omni_surnia/surnia:5.1.1/LYZ28E/squid207132027:userdebug/test-keys.
Package expects build fingerprint of motorola/surnia_retus/surnia_umts:5.1/LPI23.29-15/19:user/release-keys or motorola/surnia_retus/surnia_umts:5.1/LPI23.29-18.9/4:user/release-keys; this device has motorola/omni_surnia/surnia:5.1.1/LYZ28E/squid207132027:userdebug/test-keys.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
E:Error installing zip file '/external_sd/Blur_Version.23.11.15.surnia_retus.retus.en.US.zip'
Done processing script file
Click to expand...
Click to collapse
Who said OTA might be installed in TWRP?
AFAIK stock recovery required.
PsyClip-R said:
Who said OTA might be installed in TWRP?
AFAIK stock recovery required.
Click to expand...
Click to collapse
I could solve it, after all, I just reinstall a stock ROM and delete: cache, davilk cache, and Internal (user data)
then I had to install TWRP again
I guess we need to remove the modem patches from the update to allow installation on XT1524 ?
Interrested too : the update did download to my phone.
Got the .zip from /cache and waiting to update the script
napo7 said:
I guess we need to remove the modem patches from the update to allow installation on XT1524 ?
Interrested too : the update did download to my phone.
Got the .zip from /cache and waiting to update the script
Click to expand...
Click to collapse
Not sure if the script will pass the signature validation.
Though there's another way to update. Apply patches to files one by one, including boot.img, gpt.mbn and flash these patched versions on top of current fw. Excluding modem.
But this might be dangerous due to gpt.mbn flashing.
So guys I recently applied OTA patch to boot.img (i.e. kernel). It's relatively safe to boot it, but there's no 100% guarantee it will work as expected. Who knows what did Moto changed in there.
https://mega.nz/#!bsowHYTa!4sOxRwngUHLFyi8gAb1ZxVpitqCN24DkyMRnF3aZa58
If You have bootloader unlocked, TWRP and XT1527 firmware on Your XT1524 (or Regular 1527 without Stagefright patch), try to load it without flashing.
fastboot boot boot.img
Don't forget about the full backup.
Warning! I'm not responsible for damages you might made to your device. You're doing it by youself, and to your own responsibility
I have xt1527 android 6.0 stock and bootloader loock and stock recovery
i cant' install this update.zip?