Can any one help me with this error
error executing updater binary .zip
getting this error while flashing latest build:confused :
comparing TZ version TZ.BF.20-2.0.0109 to TZ.BF.20-2.00123
assert failed: oppo.verify_trustzone("TZ.BF2.0-2.0.0109) == "1"
error executing updater binary .zip '/sdcard/download/cyanide 5.1
You need change this line in updater-script in the .zip rom file. (META-INF/com/google/android)
Maestropcxp said:
You need change this line in updater-script in the .zip rom file. (META-INF/com/google/android)
Click to expand...
Click to collapse
No that isn't right. He's on the wrong firmware, he needs to fish the correct firmware.
XDA Moderator
Transmitted via Bacon
saimad4u said:
Can any one help me with this error
error executing updater binary .zip
getting this error while flashing latest build:confused :
comparing TZ version TZ.BF.20-2.0.0109 to TZ.BF.20-2.00123
assert failed: oppo.verify_trustzone("TZ.BF2.0-2.0.0109) == "1"
error executing updater binary .zip '/sdcard/download/cyanide 5.1
Click to expand...
Click to collapse
You need to flash the 5/15/2015 firmware, before you flash the rom .
See below for a link.
i was on latest firmware dated 15/5/2015 but couldn't flash it so flashed old firmware dated 5/5 to flash rom.
comparing TZ version TZ.BF.20-2.0.0109 to TZ.BF.20-2.00123
TZ.BF.20-2.0.0109 old
TZ.BF.20-2.00123 new
there was a conflict between these last when i flashed old firmware
TZ.BF.20-2.0.0109 to TZ.BF.20-2.0.0109 it worked
saimad4u said:
i was on latest firmware dated 15/5/2015 but couldn't flash it so flashed old firmware dated 5/5 to flash rom.
comparing TZ version TZ.BF.20-2.0.0109 to TZ.BF.20-2.00123
TZ.BF.20-2.0.0109 old
TZ.BF.20-2.00123 new
there was a conflict between these last when i flashed old firmware
TZ.BF.20-2.0.0109 to TZ.BF.20-2.0.0109 it worked
Click to expand...
Click to collapse
So, the ROMs updater script was not up to date.
Related
hey guys i hope some one can help me out here.
i just bought a Samsung galaxy s2 so i downloaded Odin and rooted it i currently am using
model number gt-i9100
android version 2.3.5
baseband vr i9100xxki3
kernel vr 2.6.35.7-i9100xxki3-cl577579 [email protected] #2
build number gingerbread.xxki3
here is the problem im having. i downloaded rom manager. i follow the instructions to flash clockwork rom when i click to install the CyanogenMod 7 mod it restarts the phone and while trying to go into the clockwork recovery i get this message half way through the start up
---installing package...
finding update package...
opening update package...
verifying update package...
e:failed to verify whole-file signature (in red letters)
e:signature verification failed (in red letters)
installation aborted
what am i doing wrong? what can i do to fix this and how can i get the latest rom from CyanogenMod installed on my gs2?
please help me im very green!!
roms
i think i have figered out my issue the reason i cant flash back to stock bell firmware or any roms is because the xxki3 firmware i downloaded was a tar package which contained a bootloader file. apparent (correct me if im wrong) but that bootloader package had checksums in the firmware which only alows me to boot my phone with the xxki3 firmware. so does this mean i cant change and im stuck with this software? is it possible to get bells stock firmware but is it possible to get the stock bootloader file? or am i just plane screwed and should be luck that at least my phone still works?
Hi. i would like update my nexus s I9023 from 4.0.3 with CWM and unlocked bootloader from 4.0.4.
all files that i have found is or a full update (from 2.3.6), or a flashable update from stock recovery.
Is there any update can be flashed from cwm, or i shoud made a full installation?
maybe you should check this dude:
http://forum.xda-developers.com/showthread.php?t=1445635
there's an update zip from 403 to 404...
it's up to you whether you make a full installation or just performs an update, the result isn't different.
savantist said:
maybe you should check this dude:
http://forum.xda-developers.com/showthread.php?t=1445635
there's an update zip from 403 to 404...
it's up to you whether you make a full installation or just performs an update, the result isn't different.
Click to expand...
Click to collapse
if i make a full installation all my data will be deleted, right? i wouldn't restore all again!
EDIT:
i've download the zip, but with cwm i can't apply the update. i have the sequent error, after the "verifyng current system":
assert failed: apply_patch_check ("/system/modules/bcm4329.ko", ....
and so on.
Hi all
My device Moto G3 XT 1550
I am currently installed Nougat custom rom
Now i try to flash stock rom 6.0.1 Using fastboot
First comment
Fastboot flash partion gpt. bin
I got error
(Bootloader) preflash validation failed
Failed(remote failure)
What to do...
Any Solution
My mobile now condition only showing bootloader
Plz help me ...!
Thank u all
viknesh war said:
Hi all
My device Moto G3 XT 1550
I am currently installed Nougat custom rom
Now i try to flash stock rom 6.0.1 Using fastboot
First comment
Fastboot flash partion gpt. bin
I got error
(Bootloader) preflash validation failed
Failed(remote failure)
What to do...
Any Solution
My mobile now condition only showing bootloader
Plz help me ...!
Thank u all
Click to expand...
Click to collapse
Skip this command
Fastboot flash partion gpt. bin
Run other commands normally
Yes
I tried... Also this
But my device Not Booted
Tq for your help
If you updated the stock rom to latest January security patch update. Then its useless. I also tried and unable to flash.
Remember if update to latest firmware. You can't downgrade. never flash previous firmware. Wait till new firmware with January security patch uploaded.
If you not updated to latest then flash the correct latest firmware.
??
yes bro i updated january patch also .
thank you bro i am waiting for new build.....
Hi everyone
I can't flash my J4+ using ODIN, on my phone i have this error "sw rev check : [aboot] fused 5 > binary 2.
Let me explain to you what happened to me
I have flashed Ressurection Remix rom on my phone using TWRP, I used the ROM but I wanted to return to stock ROM, I wanted to flash the stock firmware, but I've got the same error as mentionned, I runned ODIN as an administrator, same error, used different firmwares for my phone, I've got the same error for all the firmwares that I tried, except for two, one I've got an error which is "Unsupport dev_type" and another with this error "sw rev check : [aboot] fused 5 > binary 1".
I tried flashing the stock rom using TWRP and boot.img, vendor.img and sytem.img, but I've got an error "This is old binary. Please update latest binary! (boot.img) SECURE FAIL : KERNEL"
I tried different versions of ODIN but it also doesn't work and I have the same errors.
I can Ressurection Remix on my phone, but I want to return to stock ROM and it fails for me.
My phone is a SM-J415F/DS (MWD)*
MWD means Morocco.
I downloaded the firmware from different websites (Sammobile,firmware.mobi, samsony ...)
Please help me and sorry for my bad english
Hi y'all
So basically I've followed the https://topjohnwu.github.io/Magisk/install.html tutorial to the T . However, my phone has booted into download mode instead of, well, rooted android with the error ODIN MODE(AVB FAIL) Error verifying vbmeta: Hash Mismatch (3).
https://imgur.com/Q0OgDA6
How can I at least bring it into a flashable state?
Kaiser1871_ said:
Hi y'all
So basically I've followed the https://topjohnwu.github.io/Magisk/install.html tutorial to the T . However, my phone has booted into download mode instead of, well, rooted android with the error ODIN MODE(AVB FAIL) Error verifying vbmeta: Hash Mismatch (3).
https://imgur.com/Q0OgDA6
How can I at least bring it into a flashable state?
Click to expand...
Click to collapse
You should still be able to flash an unmodified full stock firmware or a stock combination firmware to possibly repair any damage then flash the full stock firmware. Try using the "repartition" setting in Odin when you flash the stock firmware, it may or may not also require flashing the firmware along with the PIT file for your specific model number. Your PIT file may be available for download or you may be able to extract it from the firmware files.