Database Info

E:Error executing updater binary in zip

Anybody figure out how to fix this? I can find people having this problem flashing 4.4 but I can't flash anything. I've tried to flash mf1 firmware, a 4.3 carbon nightly, and a 4.3 pac nightly. All with the same results. Here is exactly what I did -
I flashed PhilZ recovery earlier on a earlier version of TWRP.
kept getting a "failed" in PhilZ
Flashed latest TWRP via Odin
Tried flashing the above mentioned zips all with the error message.
Restored my hyper drive rls16 backup (4.1.2)
Installed latest TWRP via goomanager app
Edit : my phone is flashed to PagePlus so I kinda have to be careful I'm afraid of using Odin to go back to stock/rooted but my luck that's what it'll take. When I get home I'm going to try it with a older version of TWRP that's the only other thing I can think to try.
Any suggestions or info is appreciated.

delete

anyone ? please ?

Supposedly the update binary here is generic, you could try replacing the one in the rom zip with it
http://forum.xda-developers.com/showthread.php?t=2492496
Sent from my SCH-I535 using XDA Premium 4 mobile app

I've tried CWM PhilZ and TWRP all latest versions, and still can't get rid of this.
I Cannot install any rom, whatsoever. I did manage to install a MF1 radio zip, but that's it. I can't install 4.3 or even 4.2 ..
I've replaced the update-binary inside the zips, and edited the update-script and removed the stuff used for recognizing the device, still no dice ..
I ended up flashing a full mf1 img via Odin and then used casual to root/unlock/recovery install - and I STILL get the error. Not sure where to go from here. Seems like nobody else is having this problem unless they're not on the latest recovery and trying to flash KitKat.
Thought I'd share the rest of my story ..
edit: I was able to restore a old backup of 1.7 carbon ...lol. better than nothing or a TW rom, that's for sure.

When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app

dpeeps74 said:
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk

cjmcsw87 said:
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
OK, I have one for you to try, use the original rom zip (don't edit the update-script), when you flash in recovery and it failed, select boot and boot back into recovery, then reflash again. Try it with the latest TWRP 2.6.3.2.

SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:

cjmcsw87 said:
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
Click to expand...
Click to collapse
Nice, glad you have a happy ending!!

buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
Me too buddy, let me tell ya ..
I appreciate the advice along the way. Thank you.
now I just have to decide if I want carbon or pac as my daily driver for awhile.. Carbon is what i've almost always used after I figured out how bloated and laggy TW is.. Best of all my PagePlus flash is perfectly fine, didn't have to add APN's or mess with anything else to get data to work.
I hope this thread helps somebody else.

I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you

umka83 said:
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
Click to expand...
Click to collapse
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.

BadUsername said:
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
Click to expand...
Click to collapse
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU

umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
It's a recovery version problem, so either update your recovery or use an older one until you find something that works.

Problem Solved
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
After conducting my own research with this same problem I discovered a much simpler method of correcting the issue. When flashing KK roms with older versions of custom recoveries, the recoveries did not have sufficient instructions to to handle some of the file system changes in KK. I tried replacing the updater binaries from multiple ROMs to no avail. After about 24 hours of trial and error I managed to successfully flash Cyanogenmod cm-11-20140709-NIGHTLY-d801 and GAPPs aokp_gapps-kk-20140517 to my LG G2 D801. All that had to be done is to update TWRP from 2.6.3.2 to version 2.7.1. This version of TWRP had the necessary instructions to support a KK version custom ROM.

Good Job
Sent from my SM-G900F using XDA Free mobile app

Fixed
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
I had same issue, installed newest TWRP. Fixed! Used Odin to install.

I had the same issue as the OP. I was trying to flash a rom from the external SD card. I moved it to the Internal SD and it worked.
J

unlocked bootloader questions

So i unlocked the bootloader and got CWM installed as my recovery. Any custom ROM i try to install from ZIP on SDCARD tells me that the package is for a different device. it says it is for xt926 and a few others.
I have a CDMA RAZR HD so im 100% sure this is the correct to install. I have tried Carbon and the CM11 with no success.
SlimKat will install but all i get is a looped boot screen (the M).
I was able to RSD it back to stock kitkat but now that i FINALLY was able to unlock i want to flirt with custom roms.
Any help or suggestions are welcome.
Thanks in advance

I made a topic about the same thing more or less. If I'm not mistake, Dhacker is working on a build of CWM that will allow one to flash any ROM on the stock bootloader. Currently, you can only flash stock ROMs on it.

jldr said:
I made a topic about the same thing more or less. If I'm not mistake, Dhacker is working on a build of CWM that will allow one to flash any ROM on the stock bootloader. Currently, you can only flash stock ROMs on it.
Click to expand...
Click to collapse
No, the ROMs need to be updated to work with the KK bootloader. You can use dhacker's CM11 test builds and not much else right now.

I was under the impression that CWM will flash ANY custom ROM. Bootloader never gets modded, only unlocked. I was thinking of trying TWRP but i had a harder time installing that recovery.\\
Thanks for responce

GOT IT.
So i was trying the epinter builds. Will this work:
cm-11-20140615-UNOFFICIAL-RAZR-HD_M-KITKAT-TEST.zip
I got this from http://androidhosting.org/Devs/Dhacker29/

killrhythm09 said:
No, the ROMs need to be updated to work with the KK bootloader. You can use dhacker's CM11 test builds and not much else right now.
Click to expand...
Click to collapse
Oh I see. Thanks for the reply.

divxdvd said:
GOT IT.
So i was trying the epinter builds. Will this work:
cm-11-20140615-UNOFFICIAL-RAZR-HD_M-KITKAT-TEST.zip
I got this from http://androidhosting.org/Devs/Dhacker29/
Click to expand...
Click to collapse
Yes, that will work.
divxdvd said:
I was under the impression that CWM will flash ANY custom ROM. Bootloader never gets modded, only unlocked. I was thinking of trying TWRP but i had a harder time installing that recovery.\\
Thanks for responce
Click to expand...
Click to collapse
Make sure you're using the latest version of CWM or TWRP also. Those are also in dhacker's folder.

I got the same error while trying CM11 from the Dhacker29 folder. I am on CWM v.6.0.4.8.
This package is for "moto_msm8960, xt907, xt926, vanquish.
Im installing the correct file with CWM installed from his folder.
I am not sure what i am doing wrong? Do i need TWRP?

divxdvd said:
I got the same error while trying CM11 from the Dhacker29 folder. I am on CWM v.6.0.4.8.
This package is for "moto_msm8960, xt907, xt926, vanquish.
Im installing the correct file with CWM installed from his folder.
I am not sure what i am doing wrong? Do i need TWRP?
Click to expand...
Click to collapse
You need a newer recovery like I edited into my last post. Either CWM 6.0.4.9 or TWRP 2.7.1.0.

YOU ARE AWESOME!!!
I got 6049 installed and then my phone took CM11 as well.
Very excited!!! I have been deprived of custom ROMs since i bought this phone 1.5 years ago... (STUPID LOCKED BOOTLOADER)
Back in business BABY!!!!

Awesome, glad you got it working.
Just be warned that there may be bugs since CM11 is still running on nightly builds and snapshots.

error executing updater binary

Hi Guys,
I have tried many of the ROMs available however, for the most part, I get this error "error executing updater binary" in TWRP. I have also tried CWM and Philz recovery. The only ROM that installs is CM11. Does any one know what is the issue? Anyone got a solution? Thanks.
Current Recovery: TWRP 2.7.1.1

I'm the only one experiencing this issue?

Specifically which ROMs have you tried?
Transmitted via Bacon

I've tried the following:
AOSP from the Oneplus homepage
AOSP flapped
mahdi-rom
Team GUMMY

Are you checking the md5 when you download?
Transmitted via Bacon

No, I did not. However, having said that, would it really be the case of corrupt downloads across multiple roms? As well, CM11 installs perfectly fine.
I'll do some checking now.

bill1clinton said:
No, I did not. However, having said that, would it really be the case of corrupt downloads across multiple roms? As well, CM11 installs perfectly fine.
I'll do some checking now.
Click to expand...
Click to collapse
It's possible, I'm just throwing out the usual causes of your problem. It wouldn't be the first time it's happened.
Transmitted via Bacon

Well, just re-downloaded AOSP from the oneplus homepage and flapped AOSP. I also checked their md5 hashes; they match. I will report back.

I'm getting this same message, except I'm getting it when trying to install the new OTA update. I'm rooted with custom recovery, but haven't flashed any ROM. After I download the update, I push "install update" and my phone reboots into TWRP to install the update, and then gives me the "error executing updater binary" error. I tried downloading the update manually off the web and installing it via TWRP on my own, but it gave me the same message. Not really sure what else to do at this point.

timmaaa said:
It's possible, I'm just throwing out the usual causes of your problem. It wouldn't be the first time it's happened.
Transmitted via Bacon
Click to expand...
Click to collapse
Just tried to flash both, both times I get the "error executing updater binary" error. I do not have the technical expertise to try to correct this.

Anyone else with any ideas?

Unzip the ROM that works and the ROM that doesn't with 7zip, then swap the update-binary from the working to the non. Rezip (set to store) then either sign the ROM or toggle SIG verification in recovery, then make nandroid, wipe clean, flash
By the way, what version do you have? 16 64? Chinese? Can you get bootloader info?

demkantor said:
Unzip the ROM that works and the ROM that doesn't with 7zip, then swap the update-binary from the working to the non. Rezip (set to store) then either sign the ROM or toggle SIG verification in recovery, then make nandroid, wipe clean, flash
By the way, what version do you have? 16 64? Chinese? Can you get bootloader info?
Click to expand...
Click to collapse
The ROM that works is CM11 nightly and the one that I would like to install is pure AOSP. Are you certain that their update binary files would/could be interchangeable?
And how to do you "set to store"? I use 7zip.
I have the international 64GB. And I am not sure how to check my bootloader.
I really do apologize for my newb-ness on this matter.

There shouldn't be an issue, but of course I can't promise as I don't know what specifically is going on in your case
When you choose zip, there you will have different compression options, choose store
Try
fastboot oem device-info
Write down output here
No worries, we all are noobs in our own ways

did anyone figure this out? im having the same issue trying to install lollipop roms

Same problem here
jlinn75 said:
did anyone figure this out? im having the same issue trying to install lollipop roms
Click to expand...
Click to collapse
Hi have same problem here.
my Bootloader is unlocked, I have phone rooted, I use last bacon twrp version. I already clean all phone.
I could install any rom, finally I found cm-11.0-XNPH44S-bacon-signed-fastboot.zip with fastboot.bat file that helped me to recover my phone.
I did all steps from all guys I searched, I can't know why I always appear error "error executing updater binary".
I tried cm-12-20150124-NIGHTLY-bacon.zip, I tried BlissPop-v1.8-bacon-OFFICIAL-20150123-2230.zip, all same error. I also tried to install original cm-11, same error.
I don't know what to do more or why? I checked Bootloader is unlocked.

viriatis said:
Hi have same problem here.
my Bootloader is unlocked, I have phone rooted, I use last bacon twrp version. I already clean all phone.
I could install any rom, finally I found cm-11.0-XNPH44S-bacon-signed-fastboot.zip with fastboot.bat file that helped me to recover my phone.
I did all steps from all guys I searched, I can't know why I always appear error "error executing updater binary".
I tried cm-12-20150124-NIGHTLY-bacon.zip, I tried BlissPop-v1.8-bacon-OFFICIAL-20150123-2230.zip, all same error. I also tried to install original cm-11, same error.
I don't know what to do more or why? I checked Bootloader is unlocked.
Click to expand...
Click to collapse
I get the exact same error, as you I can only flash CM-11, strange cause I was running Euphoria OS Lollipop!
Someone must know the cause!

sad problem
doe or die said:
I'm getting this same message, except I'm getting it when trying to install the new OTA update. I'm rooted with custom recovery, but haven't flashed any ROM. After I download the update, I push "install update" and my phone reboots into TWRP to install the update, and then gives me the "error executing updater binary" error. I tried downloading the update manually off the web and installing it via TWRP on my own, but it gave me the same message. Not really sure what else to do at this point.
Click to expand...
Click to collapse
I'm having exactly same problem. So is this common problem or what? I had multirom and xposed framework but after uninstalling them both I get the same error again. I hope this does not happen when we are getting the Lollipop-update. Sry for bad enklish.
Anyone help?

[Q] OnePlus One Stock ROM - Error executing updater binary

New to the forum as a member but I have been learning a lot from the people that post here.
I have now come to a point where I am now needing help.
I would like to install the Cyanogenmod OnePlus One stock ROM and I am being prevented by the updater binary.
I have tried using the latest version of TWRP (2.8.0.1), TWRP (2.7.0.0) as well as an older version (2.6.3.3) and to no avail.
Can anyone highlight to me what I must do to fix this issue?

martay777 said:
New to the forum as a member but I have been learning a lot from the people that post here.
I have now come to a point where I am now needing help.
I would like to install the Cyanogenmod OnePlus One stock ROM and I am being prevented by the updater binary.
I have tried using the latest version of TWRP (2.8.0.1), TWRP (2.7.0.0) as well as an older version (2.6.3.3) and to no avail.
Can anyone highlight to me what I must do to fix this issue?
Click to expand...
Click to collapse
This is a recovery issue. use version 2.7.0.8

zelendel said:
This is a recovery issue. use version 2.7.0.8
Click to expand...
Click to collapse
Thanks zelendel, I ended up trying with 2.7.1.1 and it worked.

Roms not flashing

I have recently unlocked my bootloader using sunshing, and installed twrp 2.8.0.1 as my custom recovery. I do not have any problems flashing stock based roms but when I try to flash cm11(or other) based roms I'm always met with:
Code:
This package is for "xt1052, ghost, xt1053, ghost_retail, xt1055, ghost_usc, xt1056, ghost_sprint, xt1058, ghost_att, ghost_rcica xt1060, ghost_verizon" devices; this is a " ",
Code:
E:Error executing updater binary in zip 'location-of-rom.zip' :
These are roms from the Moto x xda forum I'm trying to flash. Any help is appreciated as ive searched for hours for a fix or someone having the same problem on my device with no luck.

I tried to RSD back to 4.4.2 19.5.3 stock where i started, and took all the ota updates, flashed twrp 2.8.0.1 through fastboot. Tried flashing a cm11 rom from the moto x "crdroid" and same errors as usual. Can anyone offer any assistance? The only roms that are flashing correctly are based off stock. Is there something in the rom zip i need to modify for my phone?

Having Similar issues
I am running into the same issue, I loaded the eclipse rom on to my phone and it does not matter which version or location I download it from the rom boots minus the red filter and is terribly unstable. I am in the process of trying to Fastboot Venom, but so for nothing else is recognized.

You have to modify the met.inf file to flash these roms.
Kuatous said:
I am running into the same issue, I loaded the eclipse rom on to my phone and it does not matter which version or location I download it from the rom boots minus the red filter and is terribly unstable. I am in the process of trying to Fastboot Venom, but so for nothing else is recognized.
Click to expand...
Click to collapse

But how?
Archangel said:
You have to modify the met.inf file to flash these roms.
Click to expand...
Click to collapse
What would you recommend as a how to do so? I have been researching and I am finding the folder but not what part to modify.

Could you elaborate a little Archangel? What do I need to change specifically in the file? And where can I find it?

Sorry didnt see the response,,,you need to the Team Gummy thread in this area
http://forum.xda-developers.com/showthread.php?t=2676291&page=9
and follow the directions I asked another user. It involves unzipping and modding the meta.inf file and take out some file numbers so the install will not look for specific phones.
slikerhael said:
Could you elaborate a little Archangel? What do I need to change specifically in the file? And where can I find it?
Click to expand...
Click to collapse