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
Related
hi..
i've ota'd my device with JB, and flashed it with CWM.. the problem is i cannot flash the superSU, i've checked a few a threads and guides, and although one says rooting only works for 4.0.4 firmwares ,another http://forum.xda-developers.com/showthread.php?t=2256821 says it will work on all firmwares, the message i get is E:failed to verify whole-file signature
E: signature verification failed.
which to me seems to indicate a problem with SU rather then rom. i've tried it with both 1.34 version and 1.25 version, i've read somewhere that SuperSU may not work on all devices, but i didn't see any alternatives. i've looked into CF-Auto_root but it doesn't seem to have a version for the relay..
Did you use this su flashable *.zip?
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
md5: 6462ac14cd38ed7c539ce3e29a6b92a8
yes, stil same message
can i use twrp?
emaayan said:
can i use twrp?
Click to expand...
Click to collapse
To flash SU? Sure. I think there even is a function of some sort to install su in twrp.
Sent from my SGH-T699
sadly i cannot flash that as well
due to the same problem with cwm , i need it in odin format. so my real problem is to find a cwm twrp in odin format that is compatible with the relay and enables signature verifiaction skip
QUOTE=Kueber;42798462]To flash SU? Sure. I think there even is a function of some sort to install su in twrp.
Sent from my SGH-T699[/QUOTE]
emaayan said:
due to the same problem with cwm , i need it in odin format. so my real problem is to find a cwm twrp in odin format that is compatible with the relay and enables signature verifiaction skip
Sent from my SGH-T699
Click to expand...
Click to collapse
[/QUOTE]
If you flash this cwm.tar.md5 file via odin you should be able to install the stock jelly bean rom and SU in recovery mode right after that.. I did this few days ago, just to test stock jelly bean.
If you already tried this.. wellp, no idea what's going on.
this is the exact cwm i tried, via odin, and no matter, i try to flash through it, (well i didn't try to original stock rom) whether it's TWRP su on several versions, i always go the same issue with signature verification, so my first problem is how do i install a cwm or TWRP which allow me to disable signature verification? i'm assuming i can't just pick up any cwm or twrp, and try to odin them, i need the ones compatible with relay.
Maybe a silly prompt, but is the date and time current in phone?
Yea, why shouldn't they be?
Sent from my SGH-T699 using Tapatalk 2
Someone tried any rooting method on 4.1.2 ?
I dont want to mess my phone...
Oy vey, never had this much trouble with a new phone. I am fresh off a factory image restore, flashed the latest TWRP recovery (2.6.3.4) and I cannot flash anything. I keep getting this:
E: Error executing updater binary binary in zip ' /sdcard
?
Update: Apparently something is up with the latest TWRP, there are some other users experiencing the same issue.
0dBu said:
Oy vey, never had this much trouble with a new phone. I am fresh off a factory image restore, flashed the latest TWRP recovery (2.6.3.4) and I cannot flash anything. I keep getting this:
E: Error executing updater binary binary in zip ' /sdcard
?
Update: Apparently something is up with the latest TWRP, there are some other users experiencing the same issue.
Click to expand...
Click to collapse
I just had a smilar problem.. I rooted, installed TWRP - 2.6.3.2.. Downloaded Catalysm Rom, and tried flashing it.. said failed and now im stuck at Google Logo.
Edit: I tried putting the phone of for couple of mins.. started bootloader and entered recovery. Then flashed the ROM again. It worked.. So maybe try that.
0dBu said:
Update: Apparently something is up with the latest TWRP, there are some other users experiencing the same issue.
Click to expand...
Click to collapse
Three letters:
CWM
Use the third DL link there. It's the unofficial but it just works.
theesotericone said:
Three letters:
CWM
Use the third DL link there. It's the unofficial but it just works.
Click to expand...
Click to collapse
But TWRP is so much nicer. Apparently the ROM devs, or at least some of them are using outdated updater binaries. Apparently this can also be resolved in TWRP by unmounting/mounting System (can't remember which, haven't tried it yet) after wiping.
Sent from my Nexus 5 using Tapatalk
Hello,
I have a Nexus 5 with root, stock rom, Franco Kernel and the custom recovery is TWRP. I accomplished this by following a guide around this forum, I know very little about Android. The Android version i'm running is the 4.4.2 and the phone keeps asking me to update do the newer version, however, when I try to do it, it takes me to the TWRP menu, and when I try to install it there, I get this error:
"/system/bin/thermal-engine-hh" has unexpected contents
E: Error executing updater binary in zip
Error flashing zip
How can I update the phone to the newer version of android? Can anyone help me? Thanks.
Start here, then still questions in that thread
http://forum.xda-developers.com/showthread.php?p=69234
Sent from my Nexus 5 using XDA Free mobile app
Hello,
Thanks for your reply. I can't access your link though.
D5R said:
Hello,
Thanks for your reply. I can't access your link though.
Click to expand...
Click to collapse
Something is goofed up with xda. It's the ota help in the general forum. Look for it there. Should have everything you need
Sent from my Nexus 5 using XDA Free mobile app
D5R said:
Hello,
Thanks for your reply. I can't access your link though.
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
D5R said:
Hello,
I have a Nexus 5 with root, stock rom, Franco Kernel and the custom recovery is TWRP. I accomplished this by following a guide around this forum, I know very little about Android. The Android version i'm running is the 4.4.2 and the phone keeps asking me to update do the newer version, however, when I try to do it, it takes me to the TWRP menu, and when I try to install it there, I get this error:
"/system/bin/thermal-engine-hh" has unexpected contents
E: Error executing updater binary in zip
Error flashing zip
How can I update the phone to the newer version of android? Can anyone help me? Thanks.
Click to expand...
Click to collapse
First thing, turn off mobile data. Your phone may try re-download it over and over again and use up your mobile data plan.
To install the ota via the ota update on the stock rom you will need to return to stock recovery and maybe stock kernel (not sure about this one).
NOTE: Before trying the below steps as I haven't tested them myself, please backup your ROM first. Better safe than sorry.
You can try installing the OTA updates manually from TWRP. You can find the links in the post - http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327.
If you are running 4.4.2 KRT16M you will need to download three updates.
1. KTU84M from KOT49H (4.4.2 update to 4.4.3)
2.KTU84P from KTU84M (4.4.3 update to 4.4.4)
Download them together and also put on a flashable zip of TWRP in the same location as it looks like it will reinstall the stock recovery.
You can even put on one of Franco kernel just in case too.
In TWRP select install zip and install number 1 first, then install 2. and finally install TWRP again. You should be updated to 4.4.4.
You can then install Franco kernel again just in case.
I hope this makes it easier.
EDIT: follow the link in the previous post as it has different scenarios and the steps needed.
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes and/or kernel, reboot into recovery, flash the OTA , boot to bootloader, connect to pc, fastboot flash recovery, reboot into recovery, flash supersu.
Rooted stock = reboot into recovery, flash the ROM.
No brainer really. Flashing an OTA if rooted is a fool's errand.
Sent from my Nexus 5 using Tapatalk
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?
Will I continue to get OTA software updates if I root and unlock the boot loader (to install TWRP)?
Thanks,
Hish747
Yes, make sure to untick to update the recovery in the debug options
Send from OnePlus One using Tapatalk
Yes.Of course.But it happened to me that the update script showed some errors. I had to fix them by downloading the original files and replacing my system files.
want to love this device but it seems like its always something.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
Sorry wrong thread...
Satras said:
Yes, make sure to untick to update the recovery in the debug options
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Can I dirty flash the nightlies from CM11S if I have just unlocked the bootlader and rooted?
There is no nightly for CM11s just for CM11.
I recommend to do a clean install including factory reset.
Keep in mind that after flashing something, you need to flash root at the end too
Send from OnePlus One using Tapatalk
So we will still get OTA's great! Great phone for costumizations.
ZTube said:
Yes.Of course.But it happened to me that the update script showed some errors. I had to fix them by downloading the original files and replacing my system files.
Click to expand...
Click to collapse
That does not happen if you just unlock, root and install a custom recovery.
Also a custom kernel would be fine
Send from OnePlus One using Tapatalk
Sorry if this is a bit of a n00b question (I know people are sensitive about that!) but I have searched around a bit and not found a solution to this issue. Here's the situation...
So what i've done so far is unlocked the bootloader, installed TWRP, and SuperSU (so I have root). I also unchecked the update recovery box in dev options. When told I need to update I downloaded the update, hit install, the phone reboots and takes me to TWRP. When in TWRP I hit install, navigate to the cache and try to install the update /cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip
When I do that, I get the following:
"
E:Error installing zip file '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Done processing script file
Installing '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E: Error executing updater binary in zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Error flashing zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Updating partition details...
"
Anybody got any ideas?
Seems TWRP expects a MD5 file.
I use CWM as recovery and can install the update OTA. Maybe try CWM recovery
Send from OnePlus One using Tapatalk
Satras said:
Seems TWRP expects a MD5 file.
I use CWM as recovery and can install the update OTA. Maybe try CWM recovery
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Most people that ive read about are using twrp and had no problem updating.
aamir.m.ali said:
Sorry if this is a bit of a n00b question (I know people are sensitive about that!) but I have searched around a bit and not found a solution to this issue. Here's the situation...
So what i've done so far is unlocked the bootloader, installed TWRP, and SuperSU (so I have root). I also unchecked the update recovery box in dev options. When told I need to update I downloaded the update, hit install, the phone reboots and takes me to TWRP. When in TWRP I hit install, navigate to the cache and try to install the update /cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip
When I do that, I get the following:
"
E:Error installing zip file '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Done processing script file
Installing '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E: Error executing updater binary in zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Error flashing zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Updating partition details...
"
Anybody got any ideas?
Click to expand...
Click to collapse
Yeah, you gotta open the zip on your pc, modify META-INF/com/google/android/updater-script and remove the code (its in the top part) that mentions the incompatible data error. Then try flashing again.
aamir.m.ali said:
Most people that ive read about are using twrp and had no problem updating.
Click to expand...
Click to collapse
Yeah, I don't like TWRP and got CWM installed, so I can only give support about that [emoji213]
Send from OnePlus One using Tapatalk