I flashed 2.7.1.2 from the official teamwin website, and did a factory wipe. I copied cm-11-20140831-NIGHTLY-moto_msm8960.zip with md5 to /external_sd and I try to install it from TWRP. It says:
Code:
Full SELinux support is present.
Installing '/external_sd/cm-11-20140831-NIGHTLY-moto_msm8960.zip'...
Checking for MD5 file
MD5 matched
Verifying zip signature...
This package is for devices with 4.4 bootloader
E:Error executing updater binary in zip '/external_sd/cm-11-20140831-NIGHTLY-moto_msm8960.zip'
Erro flashing zip '/external_sd/cm-11-20140831-NIGHTLY-moto_msm8960.zip'
Updating partition details...
I've found a similar issue which was due to TWRP 2.7.1.1 (and solved with upgrade to 2.7.1.2).
Previous attempts were to install M8-moto_msm8960 via ClockworkMod, resulting in dead WiFi. Then I upgraded to TWRP as more recent images would not flash in CWM, and tried nightly snapshot as per above. I am able to flash cm-11-20140708-SNAPSHOT-M8-moto_msm8960.zip in TWRP 2.7.1.2 now, WiFi works. I can wait for the next milestone, or the official CM11, and use M8, but I would like to be able to upgrade later anyway.
Any suggestions as to what to try?
eudoxos.eu said:
Code:
Verifying zip signature...
[B]This package is for devices with 4.4 bootloader[/B]
E:Error executing updater binary in ...
Click to expand...
Click to collapse
See http://forum.xda-developers.com/photon-q-4g-lte/general/cyanogenmod-11-0-photon-q-t2838299
Use moto_msm8960_jbbl builds.
kabaldan said:
See http://forum.xda-developers.com/photon-q-4g-lte/general/cyanogenmod-11-0-photon-q-t2838299
Use moto_msm8960_jbbl builds.
Click to expand...
Click to collapse
Thanks, that worked!
Hey,
I'm trying to update my One Plus One from CM11 44S(rooted) to CM12 Nightly, I have downloaded the CM12 Nightly file( cm-12-20150124-NIGHTLY-bacon.zip) from the official cyanogenmod page. I have TWRP [v2.8.4.1] recovery installed on my One Plus.
The issue:
I transferred the .zip file and gapps to my root folder and booted my phone into recovery. I performed a Backup of my ROM with the tools available with TWRP, then I wiped Cache,Dalvik Cache,System and Data. Now when I try to flash the .zip file from the Install section I get the following error.
E: Error executing updater binary in zip '/sdcard/Download/cm-12-20150124-NIGHTLY-bacon.zip'
error flashing zip.....Another statement that looks like an error.
Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.BF.2.0-2.0.0096
assert failed : oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1"Things I have tried :
1) repeated the above procedure two to three times
2) checked md5 checksum of the .zip file ==> it matched the one on the website
Can someone please help me sove this issue? Am I doing something wrong?
It only happened when youre coming from a KK ROM i dont know why. Flash an earlier nightly build e.g. 20150123 build, then flash 20150124 build. This worked for me.
redundant
I have not tried it yet, but don't you think it would be redundant since 20150123 would itself require a previous build.
Thanks for the support though.
sgovindN said:
I have not tried it yet, but don't you think it would be redundant since 20150123 would itself require a previous build.
Thanks for the support though.
Click to expand...
Click to collapse
Tried it didn't work.
Guys please help
Guys please help. I am too facing the same problem. I also even tried installing the previouds update of 23rd but it didn't help. Please help us...
Me too. I'm having the same problem in the same circumstances as @sgovindN. I've already tried CM12 from 23.01, 22.01, 13.01. The same error
Have all you guys updated your firmware?
Transmitted via Bacon
What do mean by updated firware. I am running on cynogenmod 11.0 44s version.
Pady200550 said:
What do mean by updated firware. I am running on cynogenmod 11.0 44s version.
Click to expand...
Click to collapse
In order to run the latest CM12 nightlies you need updated firmware, it's been mentioned countless times in both of the CM12 threads here on XDA.
Transmitted via Bacon
[Fixed]
I fixed this issue. The problem was the Trustzone issue error that popped up. This trustzone version is in the update binary so here is how you fix it.
Step 01 : Open the zip file with WinZip or WinRAR [do not extract]
Step 02 : Navigate to /META-INF/com/google/android
Step 03 : Open the file 'update-script' with Notepad++(recommended) {Traditional Notepad does not indent code so it is harder to find and edit}
Step 04 : On line 02 change
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");
to
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0096") == "1");
Step 05: Save the file
Similarly people facing Status 7 issue can troubleshoot by changing the model name in the 'updater-script' to the same as theirs, on line 01can fix the "Error".
Make sure you check the md5 checksum of the zip file from the official website, using a tool such as Android File Verifier.
sgovindN said:
I fixed this issue. The problem was the Trustzone issue error that popped up. This trustzone version is in the update binary so here is how you fix it.
Step 01 : Open the zip file with WinZip or WinRAR [do not extract]
Step 02 : Navigate to /META-INF/com/google/android
Step 03 : Open the file 'update-script' with Notepad++(recommended) {Traditional Notepad does not indent code so it is harder to find and edit}
Step 04 : On line 02 change
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");
to
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0096") == "1");
Step 05: Save the file
Similarly people facing Status 7 issue can troubleshoot by changing the model name in the 'updater-script' to the same as theirs, on line 01can fix the "Error".
Make sure you check the md5 checksum of the zip file from the official website, using a tool such as Android File Verifier.
Click to expand...
Click to collapse
I'm pretty sure that isn't actually fixing the issue, that's just sidestepping the safeguard that's built into the updater script.
Transmitted via Bacon
sgovindN said:
I fixed this issue. The problem was the Trustzone issue error that popped up. This trustzone version is in the update binary so here is how you fix it.
Step 01 : Open the zip file with WinZip or WinRAR [do not extract]
Step 02 : Navigate to /META-INF/com/google/android
Step 03 : Open the file 'update-script' with Notepad++(recommended) {Traditional Notepad does not indent code so it is harder to find and edit}
Step 04 : On line 02 change
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");
to
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0096") == "1");
Step 05: Save the file
Similarly people facing Status 7 issue can troubleshoot by changing the model name in the 'updater-script' to the same as theirs, on line 01can fix the "Error".
Make sure you check the md5 checksum of the zip file from the official website, using a tool such as Android File Verifier.
Click to expand...
Click to collapse
Thanks for your help. i have now successfully installed CynaodenMod 12 on to my Oneplus One.
Not able to update new rom by cyandelta. Guys help.
Pady200550 said:
Not able to update new rom by cyandelta. Guys help.
Click to expand...
Click to collapse
Which brings me back to my previous question earlier in the thread; have you updated your firmware?
Transmitted via Bacon
Yes now i able to update. I have searched regarding this. You have to download a file bacon firmware update and then u can install cm 12 nigtley
Pady200550 said:
Yes now i able to update. I have searched regarding this. You have to download a file bacon firmware update and then u can install cm 12 nigtley
Click to expand...
Click to collapse
That's right, that'd what you needed to do in the first place. The method posted by @sgovindN is not a solution at all, it just sidesteps the safeguard that's there to ensure that you're on the right firmware.
Transmitted via Bacon
LMAO I can't believe what @sgovindN did there.... TZ assert is there for a reason, and your "fix" is just a bs work around, @Pady200550 recent posts prove that. It would have taken far less effort to do it the proper way instead of coming up with that
If anyone ever find this thread in the future, DO NOT do what @sgovindN posted. Do it the proper way as @timmaaa posted with the updated firmware
Sent From Lollipopified Bacon Goodness!
Firmware Update?/
Pady200550 said:
Yes now i able to update. I have searched regarding this. You have to download a file bacon firmware update and then u can install cm 12 nigtley
Click to expand...
Click to collapse
I am on 4.4.4 custom rom PACman but unable to intall CM12/resurrection remix/Liquidsmooth/Blisspop (All 5.0 based) it gives me error : E: Error executing updater binary in zip '/sdcard/Download/cm-12-20150124-NIGHTLY-bacon.zip'
error flashing zip.....
please explain how did you mange to install CM12 ?
sagar0592 said:
I am on 4.4.4 custom rom PACman but unable to intall CM12/resurrection remix/Liquidsmooth/Blisspop (All 5.0 based) it gives me error : E: Error executing updater binary in zip '/sdcard/Download/cm-12-20150124-NIGHTLY-bacon.zip'
error flashing zip.....
please explain how did you mange to install CM12 ?
Click to expand...
Click to collapse
Are you using multirom? If yes, update to latest it will install blisspop for sure as secondary, I dunno about the rest
Since you're still on KitKat you need to install the cm12 firmware first though. You can find it in blisspop thread
Sent From Lollipopified Bacon Goodness!
I'm with cm11s as a primary in multirom and managed to install Liquidsmooth lollipop. Also managed to install CM12 but it crashes on load, and I get the "E:Error executing updater binary in zip '/tmp/mr_update.zip'" when trying to install Blisspop or tugapower.
From what you guys say, I shouldn't be able to run liquidsmooth as my "basis" is the CM11S firmware, but fact is I can xD
Isn't there a way to flash the updated firmware only over the secondary (lollipop) rom? Or is it possible to run CM11S as a secondary, with CM12 as primary?
I really want to try CM12 (to see the "future" for my OpO), but don't want to lose my fully customized CM11 just yet
Yo people !
With the new Incremental update for YNG1TAS2I3 for CM 12, when i try to update via TWRP i get an error
Package build print not verified as in attachment
Just wanted to confirm from experts
Deleting those lines from the updater-script solves the problem ?
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys" ||
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys" ||
abort("Package expects build fingerprint of oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys or oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
Or a better fix
Will flashing the stock CM12 recovery and flashing the incremental update help me ?
Can any one please upload and link me to the official CM12 recovery.img file
The Official CM recovery link is dead !
PS: Thank you Cynogen & OnePlus for the newest updates !
There was the exact same question asked and answered today....
http://forum.xda-developers.com/showthread.php?t=3137841
Lutzchker said:
that one isn't clear. If you did it succesfully can you help?
Click to expand...
Click to collapse
Either update the full ROM (not the Delta file) or choose a different .zip
Oh, and also the official OTA can not be installed from TWRP, only from Cyanogen recovery.
I'll rom whole build. Thanks again
Why not simply format system and then flash? Always works for me and all the data is there alogn with the settings. All i need to do is change dpi, build new host files by adaway, flash xposed zip and tada! it works as it should! the whole process takes not more than 3 minutes.
Installing PAC LP MR1 Official 20160326 - Error: "updater process ended with error=7"
Hello,
I am trying to install PAC LP MR1 Official 20160326 ROM as an additional rom in my oneplus (through TWRP MultiROM".
I am getting the following error: "updater process ended with error=7"
I looked online and couldn't find any solution. There are some threads about status 7 error. I am not sure if this is the same. I tried several suggested fixes and nothing helped.
Any of you guys faced this issue and managed to fix it.
This is part of the recovery log:
.................................................................................................................
oppo.verify_trustzone("TZ.BF.2.0-2.0.0123") == "1"
Comparing TZ version TZ.BF.2.0-2.0.0123 to TZ.BF.2.0-2.0.0109
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0123") == "1"
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
rm: invalid option -- M
BusyBox v1.22.1 bionic (2016-02-21 12:05 퍝�) multi-call binary.
Usage: rm [-irf] FILE...
Remove (unlink) FILEs
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
Failed to install ZIP!
.................................................................................................................
Thanks!
ali282h said:
removed
Click to expand...
Click to collapse
Flash latest modem and firmware before flashing this PAC ROM
Modem via recovery or extract on PC and run flash-modem.bat
THANK the post if I deserve
MZO said:
Flash latest modem and firmware before flashing this PAC ROM
Modem via recovery or extract on PC and run flash-modem.bat
THANK the post if I deserve
Click to expand...
Click to collapse
Thank you!
The issue has been fixed!!
Sent from my A0001 using XDA-Developers mobile app
Glad to help
Transmitted via BACON
I ran into a problem trying flashing LineageOS 16 into my one
I flashed newest twrp 3.3.0 successfully
But when I tried to use adb sideload to flash LineageOS a problem happened
The flashing process just ended immediatly
In the command prompt it says:
serving: 'lineage-16.0-20190422-nightly-bacon-signed.zip' (~0%) adb: failed to read command: No error
On my phone it says:
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Waring: No file_contexts
Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.BF.2.0-2.0.0096
Comparing TZ version TZ.BF.2.0-2.0.0123 to TZ.BF.2.0-2.0.0096
Comparing TZ version TZ.BF.2.0-2.0.0134 to TZ.BF.2.0-2.0.0096
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0109","TZ.BF.2.0-2.0.0123","TZ.BF.2.0-2.0.0134") == "1"
Updater process ended with ERROR: 7
I don't know what to do now, I googled, no one seems to have the same problem, I tried on a different computer, didn't work, I pushed the install package into my phone's storage and install from there, didn't work
Can anyone help?
I don't think you should be trying to adb sideload, just wipe Data, System, Dalvik, Cache (without internal storage) and flash the zip.
Be warned, lineage 16 currently has an issue where the wifi is unstable if used with gapps (https://gitlab.com/LineageOS/issues/android/issues/392).
You mean flash the zip from internal storage? I tried that, didn't work, same problem
Does it work with an older version of TWRP?
SethGeckoXDA said:
Does it work with an older version of TWRP?
Click to expand...
Click to collapse
Tried that, didn't work, same problem
tkgrand said:
Tried that, didn't work, same problem
Click to expand...
Click to collapse
I think this is because the modem needs to be updated before flashing.
Try flashing this modem zip before flashing rom. ---> https://androidfilehost.com/?fid=24052804347825946
Steps:
1.Open twrp
2.Flash modem
3.Flash lineage
3.Flash gapps
4.Restart
vicky2131 said:
I think this is because the modem needs to be updated before flashing.
Try flashing this modem zip before flashing rom. ---> https://androidfilehost.com/?fid=24052804347825946
Steps:
1.Open twrp
2.Flash modem
3.Flash lineage
3.Flash gapps
4.Restart
Click to expand...
Click to collapse
Yes! It works! Thank You!
twrp-3.6.2_9-0-bacon.img 14.9M 2022-05-30 00:09:30 UTC works as well. Thank you.