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
Related
When I try to install the CM11 nightly builds as found through this thread:
http://forum.xda-developers.com/showthread.php?t=2570965
the update process fails. Below a snip ffrom the TWRP log (I've attached the complete log).
minzip: Extracted file "/system/xbin/vim"
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sdcard/ROM/cm-11-20140101-NIGHTLY-tf300t.zip'
Error flashing zip '/external_sdcard/ROM/cm-11-20140101-NIGHTLY-tf300t.zip'
Through creative Googling I found some references to the install failing with TWRP and succeeding with CWM. However, the CWM ROM Manager tells me there is no supported recovery version for the TF300, so I have no idea which version to pick.
I should mention I may have partially broken my partition table when making nvFlash available though. I made another post about that:
http://forum.xda-developers.com/showthread.php?t=2594142
to which I was hoping to get a reply by now.
I'm hoping someone could help me out, I'd really like to try KitKat on this tablet.
Thanks!
Wrong TWRP?!
Orionos said:
When I try to install the CM11 nightly builds as found through this thread:
http://forum.xda-developers.com/showthread.php?t=2570965
t[...]
I'm hoping someone could help me out, I'd really like to try KitKat on this tablet.
Thanks!
Click to expand...
Click to collapse
Hmm, regularly the issue with TWRP for the TF300T is that you need a very specific/modified version, more often than not for the TF300T not the one from the TWRP site.
I can only recommend using this script to update to CM11, as it does all the installation/downloading/flashing for you, inlcuding the correct TWRP and CM/Omni and GAPPS.
http://forum.xda-developers.com/showthread.php?t=2579922
Hope this helps
recovery
Recheck the original post and make sure you are using the correct recovery.
buche,
Your script helped. When using that particular recovery, not only can I install KitKat, but my backups started working as well. Of course, the patched TWRP generates an error when installing CM10. Go figure.
norskyforce,
The post stated:
"To install, you need a recent CWM or other recovery."
I figured I was fine with the TWRP from the TWRP site. Apparently not.
Maybe I'll try the poster's recovery image. I'm still looking for the correct CWM to use, to see if it has more options. I miss 4ext
Thanks for the help.
Unfortunately, CM11/Omni don't appear to support my WiFi's channel 13. Took me a while to figure out why I could see all the neighbors' networks, but not my own.
And I just figured out neither CM10 or 11 supports my ASUS Connect Dock, which I use for the wired ethernet and USB. Grrr...
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!
My z3 is D6653, I have root, backed up TA partiition, unlocked bootloader and installed TWRP v2.4.8.0. I downloaded CM12 nightly on Feb 17th on download.cyanogenmod.org and copied it along with Google App to my SD card. When I came to recovery mode, after whippìg data, cache, things went wrong. I tried to install cm12 nightly on zip file multiple times but all failed. The error message said "this ROM is for D6603, D6633, your device is leo" and "error executing updater binary". My D6653 Z3 is recognized as "leo" which means that it is different from "z3" listed on cyanogenmod home page. What can I do now to have Cm12 on my z3?
This updater error is caused by the updater binary. Just open the zip on your PC, open the updater binary script and change the line where it says "z3" to leo". Cyanogen should be aware of that, but I think they are not changing it, as there is another device called "leo" from another manufacturer.
You could also get another ROM zip and copy the updater binary script from it to the CM12 one and repack it.
Omario-242 said:
This updater error is caused by the updater binary. Just open the zip on your PC, open the updater binary script and change the line where it says "z3" to leo". Cyanogen should be aware of that, but I think they are not changing it, as there is another device called "leo" from another manufacturer.
You could also get another ROM zip and copy the updater binary script from it to the CM12 one and repack it.
Click to expand...
Click to collapse
Which files do I need to edit? Do I just replace "z3" with "leo"?
Ariana Grande said:
Which files do I need to edit? Do I just replace "z3" with "leo"?
Click to expand...
Click to collapse
Only the updater binary which is located in the ROM zip.
Yes just replace the " z3".
Omario-242 said:
Only the updater binary which is located in the ROM zip.
Yes just replace the " z3".
Click to expand...
Click to collapse
Omario-242 said:
This updater error is caused by the updater binary. Just open the zip on your PC, open the updater binary script and change the line where it says "z3" to leo". Cyanogen should be aware of that, but I think they are not changing it, as there is another device called "leo" from another manufacturer.
You could also get another ROM zip and copy the updater binary script from it to the CM12 one and repack it.
Click to expand...
Click to collapse
this would be so much easy if there is a way to open this updater binary with notepad++ without an error .. any help there?
It should work just well with Notepad++. What error do you get when trying to open it?
Facing error"error executing updater binary in zip" ( 12.1.1 YOG7DAS2K1) Oneplus one
I tried wiping Data, Cache, System and then after flashing above update it says flashing failed.
Following are the details of my Oneplus one
TWRP : 2.8.7.0
CyanogenMod Version: 12.1-YOG4PAS3JL
Build Number: LMY48B
Device model- A0001
need a solution.
yeah same with me. Weird thing is it just says Error! nothing else is printed on the screen
I have found a solution for this problem.
You can follow this step:
1) Instead of downloading 65.8 MB incremental file go to cyanogen -support website( Sorry couldn't paste the link as i am new user) search for your device and you will find a link which will download the latest complete rom. This rom is of around 700mb.
2) Copy this downloaded rom mentioned above to ur device.
3) Take a Backup
4) Wipe Data, Cache,System or Simply just do factory reset with the help of TWRP
5) Install the Rom using TWRP
6) Reboot and finally your device will be updated and there will be no error.
it worked for me.
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.