Hi, I'm trying to update from exodus to a newer exodus rom. Every time I try to update I get the errror:
comparing tz version tz.bf.2.0-2.0.0123 to tz.bf2.0-2.0.0109
which then results in an assert failed:
oppo.verify_trust zone (tz.bf.2.0-2.0.0123) == "1"
error flashing update.
I Have never really had this problem. Any advice on how to fix would be greatly appreciated. Till then ill stick with my old rom.
Guys beware
You need to update your firmware. Install the latest cm12.1 nightly. Then flash the exodus zip.
Thanks for the help guys!
Related
Hi Here I have a BIG problem with understanding whats going on. This is forth week how i'm trying to push update for GB 2.3.1.
a little story:
I had ICS based MIUI rom installed for around 1.5 year and was extremely happy with its UI and performance and regular weekly updates - since it become more and more lagy after every update. my phone was to week for its software and I decided go back stock.
My phones current details
nexus S
gingerbred 2.3.1
baseband : I9020XXKB3 (under battery GT-I9020T)
kernel : 2.6.35.7-g7f1638a
[email protected]#1
build number : GRH78
So what I done next i downloaded Odin and flashed stock gb 2.3.1 and now i can not update it in any way. System tryes to push OTA 4.0.1 but it ends up with following
______________________________
ClockworkMod Recovery v6.0.1.0
Finding update...
Opening update package..
Verifying update package..
E:failed to verify whole-file signature
E:signature verification failed
installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:radio:12583040:a32c1a32c13af21c32fa13af2c13a2f1a32fc12f31c2a3f1")
E:Error in /chache/odDgDain.zip
(status7)
Installation aborted
_________________________________
when i Rooted it i also noticed my outdated SU binary version 2.3.1 -ef
it also fails on update.
yesterday i tried to flash glados kernel through ROM manager and the phone crashed.
I have tried coupe different radios as well but ota update wont install Even with 'ota surviva'l and 'temp unroot' ticked in SuperUser
What should I do?
what causing all this?
should i install a different kernel or different gb version rom? In this case can U refer links pleas as Im TOTTALY LOST HERE guys
Thanx
smoke1 said:
Hi Here I have a BIG problem with understanding whats going on. This is forth week how i'm trying to push update for GB 2.3.1.
a little story:
I had ICS based MIUI rom installed for around 1.5 year and was extremely happy with its UI and performance and regular weekly updates - since it become more and more lagy after every update. my phone was to week for its software and I decided go back stock.
My phones current details
nexus S
gingerbred 2.3.1
baseband : I9020XXKB3 (under battery GT-I9020T)
kernel : 2.6.35.7-g7f1638a
[email protected]#1
build number : GRH78
So what I done next i downloaded Odin and flashed stock gb 2.3.1 and now i can not update it in any way. System tryes to push OTA 4.0.1 but it ends up with following
______________________________
ClockworkMod Recovery v6.0.1.0
Finding update...
Opening update package..
Verifying update package..
E:failed to verify whole-file signature
E:signature verification failed
installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:radio:12583040:a32c1a32c13af21c32fa13af2c13a2f1a32fc12f31c2a3f1")
E:Error in /chache/odDgDain.zip
(status7)
Installation aborted
_________________________________
when i Rooted it i also noticed my outdated SU binary version 2.3.1 -ef
it also fails on update.
yesterday i tried to flash glados kernel through ROM manager and the phone crashed.
I have tried coupe different radios as well but ota update wont install Even with 'ota surviva'l and 'temp unroot' ticked in SuperUser
What should I do?
what causing all this?
should i install a different kernel or different gb version rom? In this case can U refer links pleas as Im TOTTALY LOST HERE guys
Thanx
Click to expand...
Click to collapse
It's normal you can't flash OTA because you have a custom recovery. You need stock recovery for that. You can download a factory image from Google, extract it and flash the recovery inside using fastboot.
https://developers.google.com/android/nexus/images#soju
ALSO, stop using Odin. There's no need to use Odin or nearly on Nexus S. This thing is nearly unbreakable and you have more chances of breaking stuff with Odin than anything else.
thanx for quick replay
flashed factory GB 2.3.6 straight away using sdk tools
now will root it and install custom clockwork recovery to prevent from automatic OTA updating to lagy ICS
Use FOTAKill instead,
http://forum.xda-developers.com/showthread.php?t=1579154
Thanx for good advice. Installed it allready.
Sent from my Nexus S using xda premium
Hi guys, I want place question to CM11 oficial topic, but I have <10 post. So here is my issue. I have 4.2 FB Asus FW. Then installed latest TWRP. But if I want to install CM11 nightly build (tried last one and some older one) I allways get this message after some minutes of flashing:
E:Error executing updater binary in zip '/sdcard/cm11-20140111-NIGHTLY-tf300t.zip'
Error flashing zip '/sdcard/cm11-20140111-NIGHTLY-tf300t.zip'
FAILED
Thanks for helping,
froxic
froxic said:
Hi guys, I want place question to CM11 oficial topic, but I have <10 post. So here is my issue. I have 4.2 FB Asus FW. Then installed latest TWRP. But if I want to install CM11 nightly build (tried last one and some older one) I allways get this message after some minutes of flashing:
E:Error executing updater binary in zip '/sdcard/cm11-20140111-NIGHTLY-tf300t.zip'
Error flashing zip '/sdcard/cm11-20140111-NIGHTLY-tf300t.zip'
FAILED
Thanks for helping,
froxic
Click to expand...
Click to collapse
Use the TWRP that I posted about here:
http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
Philz CWM Recovery
froxic said:
Hi guys, I want place question to CM11 oficial topic, but I have <10 post. So here is my issue. I have 4.2 FB Asus FW. Then installed latest TWRP. But if I want to install CM11 nightly build (tried last one and some older one) I allways get this message after some minutes of flashing:
E:Error executing updater binary in zip '/sdcard/cm11-20140111-NIGHTLY-tf300t.zip'
Error flashing zip '/sdcard/cm11-20140111-NIGHTLY-tf300t.zip'
FAILED
Thanks for helping,
froxic
Click to expand...
Click to collapse
If you would like a flashable zip recovery, that you can just flash from your current recovery try this one out....
Philz-tf300t-recovery.zip
Thank you guys - posted TWRP worked like a charm! :good:
Trying to install a new rom (cm-12-20150113-unofficial-n8013.zip) But I get this message:
"
Finding update package...
Opening update package...
Installing update...
Warning: No_filecontextsThis package is for device: c0, p4notewifi, p4notewifiww, n8014, GT-N8013; this device is p4noterf.
E:/Erron in /external_sd/cm-12-20150113-unofficial-n8013.zip
(Status 7)
Installation aborted."
I can assure you, my tablet is the n8013... Why am I having this error? How can I fix it? This error also occurred while trying to install the BlissPop rom as well... I don't understand WHAT I'm doing wrong?
Thanks,
Kris.
Make sure you're using the latest custom recovery. Try redownloading the ROM.
I also get a STATUS7 trying to flash CM12.1 with CWM 6.0.1.1
I have yet to try TWRP but I need a TAR.MD5 packaged image, which I'm having trouble finding.
I'd run into this problem as well, and it actually has to do with your version of TWRP (at least to my knowledge). I was actually trying to flash a custom rom, knowing fully well that my device was GT-N013, when it gave me the error. Turns out, I flashed the recovery for the Gt-N8000 model.
As far as I know, GT-N8013 and p4notewifi are the same device, but considering your error said that "this device is p4noterf," flash the latest version of TWRP for either GT-N8013 or p4notewifi (specifically). Then try reflashing the ROM.
Can anybody help me? I'm trying to flash a few things and get this "zips signature verification failed 1" in all red error. Never had it before. I just flashed latest bliss ROM and noticed I couldn't flash a kernel, Google calendar or the new camera next mod.
Thanks in advance!
So I've had a chinese version of the opo since last summer, first thing I did was root it and unlock bootloader etc. I've been running a rom for quite a while (really embarrassing, but can't remember what rom). And I tried to flash a new one, but I got greeted with the message "error executing updater binary in zip". I've tried most things, updating firmware, updating to latest recovery, wiped everything, then trying to install, then rebooting and trying again, but no luck. Running CM12 nightlies work, so does oxygenos, however they're not that good tbh. Would love any help
Roxkyp said:
So I've had a chinese version of the opo since last summer, first thing I did was root it and unlock bootloader etc. I've been running a rom for quite a while (really embarrassing, but can't remember what rom). And I tried to flash a new one, but I got greeted with the message "error executing updater binary in zip". I've tried most things, updating firmware, updating to latest recovery, wiped everything, then trying to install, then rebooting and trying again, but no luck. Running CM12 nightlies work, so does oxygenos, however they're not that good tbh. Would love any help
Click to expand...
Click to collapse
Flash latest CM12.1 nightly first
And then flash your desired ROM
Or else
Flash factory images of latest version Cyanogen OS 12.1 and then flash TWRP and then your desired ROM
Guide to flash ROMs and factory images >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Mr hOaX said:
Flash latest CM12.1 nightly first
And then flash your desired ROM
Or else
Flash factory images of latest version Cyanogen OS 12.1 and then flash TWRP and then your desired ROM
Guide to flash ROMs and factory images >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Unfortunately these methods did not work for me, I can get on 12.1, but when I want to flash something else (resurection rom in this case) I get the error.
Its a firmware issue you need the correct firmware