Database Users

CM 10.1 wont flash error executing updater binary in zip

I rooted my phone and installed TWRP recovery. When i try to flash a cm 10.1 (LOKI) i get the error: Error executing binary in zip ' /external_sd/cm-10.1 -20130524-N
What am i doing wrong?

This error sometimes occurs while flashing a custom ROM on new devices. i dont know why but i know i've seen it happen to phones, tablets, etc of all brands. it is commonly fixed by downgrading to the previous/an older version of twrp. in this case, i dont know if an earlier version for the s4 exists as i use cwm only. i would imagine it would flash in cwm, but i would also imagine you would prefer to stay on twrp. just passing on what i know. cheers

Error executing updater binary in zip (TWRP)

I'm getting this error when trying to flash lollipop roms. I can flash Kitkat roms fine as I'm currently running xdabbeb VS982.5 1.0.0 (G3 rom), but it won't let me flash any lollipop rom. I installed twrp via the autorec program which installs 2.7.0.0 then I updated twrp within twrp with the flashable zip.
Please help
Thank you

Anyone?

Seriously no one knows? What is everyone else using that is flashing the latest 5.0.2 roms?
What am I getting this error?
Please help

Possible Fix
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.

Thanks for the suggestion. I'll give it a try. If there is no. Md5 what do I do then?

All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?

I tried resurrection remix and liquid lollipop roms. I had no issues with the initial 5.0 lollipop roms so I'm not sure what changed with 5.0.2.
So the md5 checker generates the .Md5 then you just put that on the SD card with the rom?

Resurrection remix should have an md5 on the download page right below the rom itself.

derekmt95 said:
All you need to do if it comes to that is download an md5 checker on your computer. Just curious, what rom are you trying to flash?
Click to expand...
Click to collapse
Can you point me to the program to use on my computer? Do I just load the .zip file in the program to generate the .md5sum file then put both the zip and the .md5sum file on the sdcard before flashing?
Thanks

derekmt95 said:
I've also had this problem. The only way I can seem to fix it is to also download the .md5 along with the rom itself. Just make sure its in the same folder as the rom. Everytime I have that problem with TWRP this seems to fix it. Let me know if it works for you!
Edit: Also I forgot to mention, if one isn't available to download I can help with that.
Click to expand...
Click to collapse
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.

xxNiradxx said:
Nope, I downloaded the md5 file along with the zip and I'm still getting the same "error executing updater binary in zip".
Any other suggestion? How is no one else having this same issue? I'm using the latest version of TWRP 2.8.3.1 probably like most people. I don't understand.
Click to expand...
Click to collapse
Try to reflash the TWRP.. or maybe is something wrong with the zip file
Use the TWRP compiled by blastagator

Nope, still getting same error with latest twrp.

Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.

xxNiradxx said:
Finally got it working. I downgraded TWRP to 2.7.0.0 and the lollipop roms are flashing fine now.
Thanks everyone for your help.
Click to expand...
Click to collapse
How did you downgrade because I cannot seem to find a way to do it.

TheAnonymousButler said:
How did you downgrade because I cannot seem to find a way to do it.
Click to expand...
Click to collapse
just run AutoRec again and you are all set.

LG G2 cm-11 M12 : Error executing updater binary in zip (TWRP)
kashif87 said:
just run AutoRec again and you are all set.
Click to expand...
Click to collapse
Hi, I am having the same problem. Actually my LG G2 was stuck in boot loop with secure boot error. I used SRK tool to flash the partition files as well as TWRP recovery 2.8.6.1. I have wiped everything and there is no OS installed. I am stuck in TWRP recovery screen [cannot downgrade /upgrade]. I am using and OTG cable to flash the cm-11 custom ROM but it is giving me the same error. Can anyone help ?? It has been 10 days I am trying and my phone is dying please help...
Thanks in advance...

before flash 5.1.1 aosp lollipop rom u must to flash first lollipop bootstack

Hi,
I am assuming the reply was for me. Actually I am not installing lollipop. I am going for kitkat but nothing is working now. I have tried cm-10.2, cm-11 M12, cm-11 M7 but all are showing "error executing updater binary in zip". Please if someone can help me out....
Thanks is advance....

@[email protected] i think kk aosp room need jb bootleader

Hello everyone,
I am running a D802 on stock Lollipop and installed TWRP 2.8.6.0 via AutoRec. Now I booted into recovery, wiped System and Cache and got the Error message when installing CrDroid (Marshmallow 6.0.1). Now I tried installing TWRP 3.0.2.0, which succeeded and then downloaded the twrp 2.7.0.0 zip to try that as the ROM still wouldnt install. But it wont install the older TWRP. So I am asking for help to either
1) Install TWRP 2.7.0.0
or
2) Delete the getprop lines from updater-script (after I removed them I get an error 6 so i probably removed too much?)
Thank you in advance
(Guide for Error 7: http://forum.xda-developers.com/showthread.php?t=2522762)
EDIT: Someone said installing another Kernel might allow installation of the ROMs. Which Kernel could work for my phone?
EDIT 2: When flashing TWRP 2.7.0.0 it says "assert failed: run_program("/tmp/loki.sh")==0". So what exactly am I missing on my phone? Is Loki the MM Bootloader?
EDIT 3: Could it be that the build.prop was deleted when I wiped system? Would be weird if that was the cause, but I simply dont know..
Edit: Booted in Downloa Mode and flashed v30D KDZ with the 2014 LG Flashtool. Works with Stock ROM for now

Status 7 Error for All Roms.

Whenever I am flashing Roms (Cm 14, AOSP, R.Remix) or any other rom, TWRP is showing STATUS 7 error for each and every rom. I tried modifying script file too but then TWRP fails to detect binary-script file and installation gets abort. What to do?

It means you have the wrong version of firmware package installed. For CM14 and all it's derivatives you must have OOS 3.0.2 installed before to get the compatible TZ.

Should I install This?
pitrus- said:
It means you have the wrong version of firmware package installed. For CM14 and all it's derivatives you must have OOS 3.0.2 installed before to get the compatible TZ.
Click to expand...
Click to collapse
Should I Install this one?
I am using OnePlus 2 (INDIA)
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip

Did you made a proper "Wipe" of the device before an installation of each rom?

piyushmodi01 said:
Whenever I am flashing Roms (Cm 14, AOSP, R.Remix) or any other rom, TWRP is showing STATUS 7 error for each and every rom. I tried modifying script file too but then TWRP fails to detect binary-script file and installation gets abort. What to do?
Click to expand...
Click to collapse
Use HybridRecovery v3.4

Same issue with Hybrid Recovery V. 3.4
Updater Process Ended with ERROR 7.

Weird.... I would use fastboot to return to stock
Sent from my ONE A2005 using Tapatalk

I can't
I can't install that ROM, have the same error with TRWP.. my OP is A2005

Problems with flashing custom roms

Hi all
I have a Smasung Galaxy note 3 (sm-n9005 htle)
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
so i googled for this error. and found a fix.. so i deleted the first lines in the updater-script... after that i tried it again. But it ditent work. It fails with the massage: could not found the binary file.
I wiped and formated the Smartphone as well.
I spend allready the whole day to install any custom rom...
Im really sad about this... maybe someone can help me.
And sorry for my bad english.

Did you confirm the phone's model # in download before flashing TWRP?

audit13 said:
Did you confirm the phone's model # in download before flashing TWRP?
Click to expand...
Click to collapse
Do you mean, that i downloaded the TWRP for my device model? Yes i did
Otherwise what do you mean?

Before flashing anything, especially if I got the phone used, I boot the phone into download just to confirm that the model # matches the label under the battery.
Only after confirming the model # in download do I start flashing files to the phone.
Does the error 7 happen with all custom ROMs?

audit13 said:
Before flashing anything, especially if I got the phone used, I boot the phone into download just to confirm that the model # matches the label under the battery.
Only after confirming the model # in download do I start flashing files to the phone.
Does the error 7 happen with all custom ROMs?
Click to expand...
Click to collapse
The Modelnumber in the downloadmode and the number under the battery are the same.
Yes i tried maybe five custom roms.

Fail is usually user fails to read instructions .
Error one .
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
Aroma installer does not work and thats why instructions tell you to use the older TWRP .
Instructions .
>>>Get a good recovery. TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
>>>TWRP recovery recommended, 2.8.7.0. Newer versions are not supported

JJEgan said:
Fail is usually user fails to read instructions .
Error one .
I allready rooted it and installed the TWRP 3.0.2-0. That worked fine.
Now i tried to install some custom rom... it doesent work... it shows me the error 7 ...
Aroma installer does not work and thats why instructions tell you to use the older TWRP .
Instructions .
>>>Get a good recovery. TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
>>>TWRP recovery recommended, 2.8.7.0. Newer versions are not supported
Click to expand...
Click to collapse
Thanks for it.
I tried now the TWRP 2.8.7.0. For my device there are two versions. The twrp-2.8.7.0-hlte-4.3.img.tar and twrp-2.8.7.0-hlte-4.4.img.tar.
First i tried now the twrp-2.8.7.0-hlte-4.4.img.tar but still gives me an error :
Updating partition deteils...
... done
Full SELinux support is present.
MTP Enabled
Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data.
Please try another package or run factory reset
E:Error executing updater binary in zip '/external_sd/cm-23.1-20161016-NIGHTY-hlte.zip'
Updating partition details...
...done
The other version of TWRP doesent work. It ends up in a reboot circle.

Try Philz Recovery .
That fails flash a clean stock rom
BUT FIRST
.Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'
Can't install this package on top of incompatible data.
Please try another package <<<< or run factory reset >>>
---------- Post added at 11:57 AM ---------- Previous post was at 11:43 AM ----------
You would be best flashing stock rom through Odin and then if you have problems post exact details .
What rom flashed etc .

JJEgan said:
Try Philz Recovery .
That fails flash a clean stock rom
BUT FIRST
.Installing '/external_sd/cm-23.1-20161016-NIGHTLY-hlte.zip'
Can't install this package on top of incompatible data.
Please try another package <<<< or run factory reset >>>
---------- Post added at 11:57 AM ---------- Previous post was at 11:43 AM ----------
You would be best flashing stock rom through Odin and then if you have problems post exact details .
What rom flashed etc .
Click to expand...
Click to collapse
Hell Yeah!
Thanks a lot it finaly worked with Philz Recovery...
I wiped my phone several times before intsalling the rom... but with Philz Recovery it worked!
Thanks so much! Im really happy now... its not the first device with a custom rom... but the first with problems
Thanks thanks thanks

LineageOS installation problems on Samsung A3 SM-A300FU a3xelte

Hi,
I hope I post into the correct category.
I am trying to install on LineageOS on a Samsung A3 SM-A300FU a3xelte using twrp and start to be completely confused.
I try to explain "historically".
I purchased the unused device running Android 5.
Following the installation instructions under <https://wiki.lineageos.org/devices/a3xelte/install>I tried to install several versions of TWRP for Samsung Galaxy A3 2016 (Exynos) (twrp-3.5.2_9-a3xelte to twrp-3.2.1-0-a3xelte) using heimdall as well as odin.
Every attempt ended up in "image too large for recovery".
Searching a smaller compatible version I tried versions down to twrp-3.0.0 --> Same result "image too large for recovery".
Even lineageos recovery (lineage-17.1-20210411-recovery-a3xelte) could not be installed successfully.
In the meantime I installed a combination stock rom (COMBINATION_OXA_FA44_A300FUXXU1AOK1_OXAOK1_CL4447487_QB7014253_REV00) and the probably newest Stock Rom (Baseband version A300FUXXU1CPH3, Android 6.0.1) and repeated the installation attempts for twrp as mentioned earlier.
"USB debugging" was activated. This device does not have option "OEM unlock", but some research is telling me that this is most likely not the problem.
In order to proceed somehow I installed successfully "TWRP_2.8.7.0_A3_F-H-FU_5.0.2_v2" using Odin. I know, that this version should not be used on a3xelte
Nevertheless this version has only 12,8 MB.
I could boot into twrp. The installation of lineage-os failed - as expected - because of the "wrong" device. Therefore I deleted the leading "assert" lines from updater-script, packed the whole thing newly as zip and tried installing using "adb sideload" as well as twrp "Install".
Obviously these installations failed on line
block_image_update("/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");
I examined the existence of /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM. This path in fact does not exist on my device, but only /dev/block/platform/soc.0/by-name/SYSTEM
I changed the update script again using that path without installation success.
What completely screwed me up: If I run in twrp "blockdev --getsize64" it shows for
system : 2575302656 (2,4GB ?)
recovery : 15728640 (ca. 15 MB)
This explains why I could not install the twrp-a3xelte versions. They are actually too large for the recovery partition.
But the system partition seems to be large enough and I wonder why I found different pathes than the update-script expects.
Has anyone any idea how to get lineage-os installed on this device ?
Thanks in advance for any hint.

honza1 said:
Hi,
I hope I post into the correct category.
I am trying to install on LineageOS on a Samsung A3 SM-A300FU a3xelte using twrp and start to be completely confused.
I try to explain "historically".
I purchased the unused device running Android 5.
Following the installation instructions under <https://wiki.lineageos.org/devices/a3xelte/install>I tried to install several versions of TWRP for Samsung Galaxy A3 2016 (Exynos) (twrp-3.5.2_9-a3xelte to twrp-3.2.1-0-a3xelte) using heimdall as well as odin.
Every attempt ended up in "image too large for recovery".
Searching a smaller compatible version I tried versions down to twrp-3.0.0 --> Same result "image too large for recovery".
Even lineageos recovery (lineage-17.1-20210411-recovery-a3xelte) could not be installed successfully.
In the meantime I installed a combination stock rom (COMBINATION_OXA_FA44_A300FUXXU1AOK1_OXAOK1_CL4447487_QB7014253_REV00) and the probably newest Stock Rom (Baseband version A300FUXXU1CPH3, Android 6.0.1) and repeated the installation attempts for twrp as mentioned earlier.
"USB debugging" was activated. This device does not have option "OEM unlock", but some research is telling me that this is most likely not the problem.
In order to proceed somehow I installed successfully "TWRP_2.8.7.0_A3_F-H-FU_5.0.2_v2" using Odin. I know, that this version should not be used on a3xelte
Nevertheless this version has only 12,8 MB.
I could boot into twrp. The installation of lineage-os failed - as expected - because of the "wrong" device. Therefore I deleted the leading "assert" lines from updater-script, packed the whole thing newly as zip and tried installing using "adb sideload" as well as twrp "Install".
Obviously these installations failed on line
block_image_update("/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");
I examined the existence of /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM. This path in fact does not exist on my device, but only /dev/block/platform/soc.0/by-name/SYSTEM
I changed the update script again using that path without installation success.
What completely screwed me up: If I run in twrp "blockdev --getsize64" it shows for
system : 2575302656 (2,4GB ?)
recovery : 15728640 (ca. 15 MB)
This explains why I could not install the twrp-a3xelte versions. They are actually too large for the recovery partition.
But the system partition seems to be large enough and I wonder why I found different pathes than the update-script expects.
Has anyone any idea how to get lineage-os installed on this device ?
Thanks in advance for any hint.
Click to expand...
Click to collapse
Hm ... unused device?
So it should be on stock firmware with original partition sizes.
Have you check to boot into stock recovery before?
Maybe there is something wrong with this "unused" device.
You can try to flash a recent stock firmware with original pit file to re-partition to stock partition sizes.
On windows pc use Odin for flashing.
When on stock Samsung firmware, try to flash twrp recovery again.