Related
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
I have a Nabi 2 that I am able to get into TWRP, but when I try to install any zip files, it gives me a flashing error. I also notice I that it shows unable to mount and when I power down from TWRP it states no OS installed. How can I reinstall the OS for a Nabi 2. Any help would be appreciated. Thanks.
ehscoto said:
I have a Nabi 2 that I am able to get into TWRP, but when I try to install any zip files, it gives me a flashing error. I also notice I that it shows unable to mount and when I power down from TWRP it states no OS installed. How can I reinstall the OS for a Nabi 2. Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Your TWRP version is too old. You need a newer one.
This is the general procedure to follow:
http://forum.xda-developers.com/showpost.php?p=51037177&postcount=21
Substitute this TWRP though
http://forum.xda-developers.com/showpost.php?p=59452953&postcount=2592
I followed the thread and updated the TWRP and now using 2.2.3.0 and still having the same problem. I try to go into the mount section and not able to click on anything. I tried flashing a zip that I was able to flash previously and that one does not work either.
ehscoto said:
I followed the thread and updated the TWRP and now using 2.2.3.0 and still having the same problem. I try to go into the mount section and not able to click on anything. I tried flashing a zip that I was able to flash previously and that one does not work either.
Click to expand...
Click to collapse
You should be using TWRP 2.6.3 or higher. The TWRP you are using has ICS kernel and can't read the device partitions. The second link I gave you is 2.8.5
I will try updating to s newer version and see if that works. Thanks for the info.
I can't post in the http://forum.xda-developers.com/oneplus-x/orig-development/rom-cyanogenmod-12-1-oneplus-x-t3254072 where is my phone.
I done all the steps, rooted my phone, backuped with TWRP, and deleted all of the content on the phone.
I am trying and failing to install Cyanogenmod(from the tread) with TWRP.
Message that i am geting is "error executing updater binary in zip".
I tried searching for the problem but only solution is to install CM-recovery, but the link is not correct and i cant find it anywhere for Oneplus X.
I see that some people installed Cyanogen mod with TWRP but i can't find solution for my problem.
Can someone help me solve the problem?
TrutY007 said:
I can't post in the http://forum.xda-developers.com/oneplus-x/orig-development/rom-cyanogenmod-12-1-oneplus-x-t3254072 where is my phone.
I done all the steps, rooted my phone, backuped with TWRP, and deleted all of the content on the phone.
I am trying and failing to install Cyanogenmod(from the tread) with TWRP.
Message that i am geting is "error executing updater binary in zip".
I tried searching for the problem but only solution is to install CM-recovery, but the link is not correct and i cant find it anywhere for Oneplus X.
I see that some people installed Cyanogen mod with TWRP but i can't find solution for my problem.
Can someone help me solve the problem?
Click to expand...
Click to collapse
You may want to try re downloading the zip file as the download may be corrupted.
If that dosent work tell me and I will try to find another solution.
Solved, i folowed 2 sets of instructions for rooting. And installed the wrong version of TWRP. With new version it works like a charm.
Device: Samsung Galaxy S7 SM-G930W8
TWRP Version: 3.0.2-2
Tried downloading the file to get around the DM-verity boot loop linked in the guide a couple times thinking it may have got corrupt downloading or transferring however nothing has changed.
flashing with TWRP worked fine, and for the sake of curiosity if maybe it was just having an issue with .zips and i should re-flash,
i attempted to install the SU file also linked in the guide linked below. however that was successful.
i have not attempted to fully re-start the phone as its been ages since i last owned, and rooted an android device. so I'm un-sure if the DM-Verity thing will lock me out of getting back into TWRP or not.
This is as far as it gets when attempting to install the .zip to fix DM-verity
-dumping & unpacking original boot image…
-Error: unpacking boot image failed
-Aborting…
Failed to patch boot image!
Updater process ended with ERROR: 1
Any help would be greatly appreciated. Thanks.
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
I have the EXACT same error, I followed the steps and I'm not new at all to rooting Samsung devices.
I believe the error is that they tell you to flash SuperSU first, on my girlfriends' s6 this wasn't necessary.
I have wiped data and factory reset, reflashed TWRP etc etc etc, I can't get this dm-verity to flash! I rebooted into system and everything seems to work OK though, I just installed the XPosed framework and it's booting again now so I believe that maybe because you first flashed the SuperSU this prevents the dm-verity stuff to work?
Anyone else have any idea?
CidHighwind said:
Device: Samsung Galaxy S7 SM-G930W8
TWRP Version: 3.0.2-2
Tried downloading the file to get around the DM-verity boot loop linked in the guide a couple times thinking it may have got corrupt downloading or transferring however nothing has changed.
flashing with TWRP worked fine, and for the sake of curiosity if maybe it was just having an issue with .zips and i should re-flash,
i attempted to install the SU file also linked in the guide linked below. however that was successful.
i have not attempted to fully re-start the phone as its been ages since i last owned, and rooted an android device. so I'm un-sure if the DM-Verity thing will lock me out of getting back into TWRP or not.
This is as far as it gets when attempting to install the .zip to fix DM-verity
-dumping & unpacking original boot image…
-Error: unpacking boot image failed
-Aborting…
Failed to patch boot image!
Updater process ended with ERROR: 1
Any help would be greatly appreciated. Thanks.
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Click to expand...
Click to collapse
Guys i had the same problem, then i searched on youtube for some help and i found this site where to download the zip file...it worked for me !!!
http://downloadandroidrom.com/file/tools/SuperSU/no-verity-opt-encrypt.zip
Hope it helps
I can't seem to find where you download anything on that page. every link just re-directs you to a bunch of spam.
CidHighwind said:
I can't seem to find where you download anything on that page. every link just re-directs you to a bunch of spam.
Click to expand...
Click to collapse
Scroll all the way down to "CLICK HERE to Download"
I downloaded this dm-verity zip and noticed it's about 100kb smaller than the one I got yesterday. Up until now my S7 has been working flawless even without this dm-verity zip. On my S6 this was absolutely necessary.. Can anyone comment on this?
I will probably try to flash this later today after I took a backup.
CidHighwind said:
I can't seem to find where you download anything on that page. every link just re-directs you to a bunch of spam.
Click to expand...
Click to collapse
CobyBE said:
Scroll all the way down to "CLICK HERE to Download"
I downloaded this dm-verity zip and noticed it's about 100kb smaller than the one I got yesterday. Up until now my S7 has been working flawless even without this dm-verity zip. On my S6 this was absolutely necessary.. Can anyone comment on this?
I will probably try to flash this later today after I took a backup.
Click to expand...
Click to collapse
Exactly
It opens a new page couple of times and then the dwl starts...
Sent from my herolte using XDA Labs
Flashing this new zip worked flawlessly, booted immediately. However now I'm seeing the "Kernel is not SEAndroid Enforcing" message on top. I didn't have this before flashing this even though I was rooted (Stock rom) and had TWRP installed
CobyBE said:
Flashing this new zip worked flawlessly, booted immediately. However now I'm seeing the "Kernel is not SEAndroid Enforcing" message on top. I didn't have this before flashing this even though I was rooted (Stock rom) and had TWRP installed
Click to expand...
Click to collapse
For me it was the same but looks like it's the only way to have a "working" rooted phone...when i rooted with cf-autoroot i couldn't flash the Roms because i couldn't have access to memory and wipe after flashing...like this you have the red string but you can wipe
Sent from my herolte using XDA Labs
Anyone have the download somewhere?
I went to the page post here but it just opens a window to "mirror31.downloadandroidrom.com/download/tools/SuperSU/no-verity-opt-encrypt.zip?token=640936718"
then just goes to a page that says ":An error occurred.
Sorry, the page you are looking for is currently unavailable.
Please try again later.
If you are the system administrator of this resource then you should check the error log for details.
Faithfully yours, nginx."
I've been trying for a couple hours to download it.
So right now I have a phone that I can't use, really need to fix this.
Updated zip
Ok guys, I've been working on a better zip that fixes the "Kernel is not SE Android enforcing" and also doesn't disable Force Encrypt. My reasoning is that it can interfere with "fully encrypting the phone" functionality which is required by some companies when registering your email. Anyway, if you wish to bring it back, just copy over 01-opt-encrypt and put it in patch.d folder.
alexceltare2 said:
Ok guys, I've been working on a better zip that fixes the "Kernel is not SE Android enforcing" and also doesn't disable Force Encrypt. My reasoning is that it can interfere with "fully encrypting the phone" functionality which is required by some companies when registering your email. Anyway, if you wish to bring it back, just copy over 01-opt-encrypt and put it in patch.d folder.
Click to expand...
Click to collapse
Found this when i was searching for DM-Verity disabler for my Redmi Note 7 pro with Stock MIUI ROM, just wondering if this will also works on Redmi Note 7 pro (encrypted, android 9).
Tks.
ne0t said:
Found this when i was searching for DM-Verity disabler for my Redmi Note 7 pro with Stock MIUI ROM, just wondering if this will also works on Redmi Note 7 pro (encrypted, android 9).
Tks.
Click to expand...
Click to collapse
I think it might work fine since all it does to stop the warning is to inject an echo command to the kernel. So in theory it should work. If it fails, the system isn't changed.
alexceltare2 said:
I think it might work fine since all it does to stop the warning is to inject an echo command to the kernel. So in theory it should work. If it fails, the system isn't changed.
Click to expand...
Click to collapse
Tks forn the quick reply.
One more question, what partition and (what files) do I need to backup in case something unexpected happened.
ne0t said:
Tks forn the quick reply.
One more question, what partition and (what files) do I need to backup in case something unexpected happened.
Click to expand...
Click to collapse
The Kernel partition. Use TWRP for that.
alexceltare2 said:
The Kernel partition. Use TWRP for that.
Click to expand...
Click to collapse
Sorry, can't find the KERNAL partition..do you mean BOOT?
There are Boot, Recovery, System, Data, Vendors, ...
ne0t said:
Sorry, can't find the KERNAL partition..do you mean BOOT?
There are Boot, Recovery, System, Data, Vendors, ...
Click to expand...
Click to collapse
Yes, I meant to say Boot. Boot and Kernel are the same.
alexceltare2 said:
Updated zip
Ok guys, I've been working on a better zip that fixes the "Kernel is not SE Android enforcing" and also doesn't disable Force Encrypt. My reasoning is that it can interfere with "fully encrypting the phone" functionality which is required by some companies when registering your email. Anyway, if you wish to bring it back, just copy over 01-opt-encrypt and put it in patch.d folder.
Click to expand...
Click to collapse
Thank you very much!!