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
Thank's to this forum I have phone with 16gb memory, fastboot , TWRP and rooted - this is really great, thank you!
There is new update for 6039H - - 010 07p ~55Mb the of size, waiting for installation.
1st - where is this the file? Where "System updates" app is hiding it?
2nd - should we check update.zip somehow before flashing or just modify, flash and see results.?
Thank you.
Sent from my 6039H using Tapatalk
Just found where is ota hidden : /data/data/com.tcl.fota/.fotadownload
You need to have "Show hidden files" enabled in file manager to see/find it.
I tried use ota_modifier.sh get error:
ota_modifier.sh update.zip
The provided file is not a zip file!
then:
file update.zip
update.zip: Java Jar file data (zip)
In my system LXLE 14 witch is actually Ubuntu there is "zip" not a "Zip" witch is expected from script. I had to change this - editing script. One letter - big difference for linux.
Flashing update_modified.zip filed...
"/system/bin/app_process32" has unexpected contents.
E: Error executing updater binary in zip .... [path to my modified zip]
Error flasing zip [path]
[edit]
If you see this error reason is - root. Need to be fully unrooted!
Now everything went fine. Flashed thru TWRP, rerooted. Whole process takes quiet of time be patient.
Hello,
I can update my shield tablet. I get that error:
Code:
Updating partition details …
… done
Full SELinux support is present
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file …
Sskipping MD5 check*: no MD5 file found
Source*: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys
Verifying current system...
Package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys or nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys*; this device has nvidia/sb_na_wf/shieldtablet:6,0:MRA58K/41524_664,1902:user/release-keys.
Update process ended with ERROR*: 7
Error installing installing zip file '@/cache/recovery/block.map'
Done processing script file
MTP Enabled
Can someone help me?
bird12358 said:
Hello,
I can update my shield tablet. I get that error:
Code:
Updating partition details …
… done
Full SELinux support is present
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file …
Sskipping MD5 check*: no MD5 file found
Source*: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys
Verifying current system...
Package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys or nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys*; this device has nvidia/sb_na_wf/shieldtablet:6,0:MRA58K/41524_664,1902:user/release-keys.
Update process ended with ERROR*: 7
Error installing installing zip file '@/cache/recovery/block.map'
Done processing script file
MTP Enabled
Can someone help me?
Click to expand...
Click to collapse
some more information might help people help you mate, are you rooted, do you have a custom recovery installed or are you running a custom rom? things like that help us alot
I user to be as root. But I restore factory setting ans I still have thé error.
Should i made an other thing to suppress thé root settings.?
Yes Mate I thought no so do you have a custom recovery installed
Sent from my HTC One using Tapatalk
I don t think I have that recovery installed. Where could I find this?
bird12358 said:
I don t think I have that recovery installed. Where could I find this?
Click to expand...
Click to collapse
Turn off your tablet then hold volume down and the power button untill you get to the boot loader then use the volume down button to select recovery and press power if you have a custom recovery it will bot to it and it will say team win recovery
Sent from my HTC One using Tapatalk
It seems I don t have a custom recovery. How should I do nos?
How to fix it error 7 shows
Anyone help me
How to solve wrong baseband error
Open zip file, go to meta-inf>com>google>android
And delete first command in updater script,
Extract zip before doing that, and zip it again