**ISSUE RESOLVED - UPDATED FIRMWARE**
I've been using the Exodus nightlies for the last few months and updating with no issue until the latest one (exodus-5.1-20150921-NIGHTLY-bacon.zip). When I try to update, it passes the MD5 check but then errors out with "error executing updater". I have tried the following and any tips on what I can try next would be greatly appreciated.
Steps taken:
1. I've tried dirty flashing exodus-5.1-20150921-NIGHTLY-bacon.zip from both the Exodus Updater application as well as Exodus website.
2. I was running TWRP 2.8.6.1 when I initally tried to install the nightly. After some searching, people seemed to resolve the issue by updating TWRP. I updated TWRP to 2.8.7.0 but I'm still experiencing the same issue.
Anyone experiencing the same thing? Any suggestions on what I can try next?
Related
So I saw that an official version of Xposed was posted for 5.1. I tried flashing the zip like in the instructions but I keep getting
Code:
error executing updater binary in zip xposed-v72-sdk22-arm.zip
and bootloops. This is the replacement tablet I got from Nvidia for the recall and I unlocked the bootloader an have TWRP installed. I tried running the uninstall zip, even though it didnt have xposed installed before, but that didn't work. I'm tempted to just factory reset and try again but I'd like to get it working with my current settings before resorting to that if possible. I also had this issue with romracer's port of xposed. What else could I do to get it to work?
Error with bliss pop and cm 12
I know this is an older thread but I have recently tried to root and install a custom rom and I get the same error. I have the most current version of TWRP flashed and I have looked up others who have installed both CM 12 and bliss pop, to follow their steps. For example formating the casch and system before install, and every time I get the same error. What am I doing wrong? Any help would be greatly appreciated.
some more Information? any errortext?
Sorry I didn't explain that, it's the same error as the first post. "Error executing updater binary in zip" then it will list the path of the zip with the rom I'm trying to install.
Hi,
I've got TWRP 3.0.2-0 recovery installed with CM12.1.1 YOG7DAS2K1 and am receiving the OTA update for CM13.0 ZNH0EAS2JK Incremental but the installation fails with an error message in recovery saying it's expecting "YOGDAS2K1" level but finds "YOG4PAS1N0". This happens whether I re-enable the CM Recovery update or not.
I found a thread here on XDA linking to all CM official updates. I flashed the recovery from "cm-12.1-YOG7DAS2K1-bacon-signed-fastboot" successfully and then tried the update again but it still failed. Again, happens whether I have CM Recovery update enabled or not.
Verifying current system...
system partition has unexpected contents
E : Failed to install @/cache/recovery/block.map
Click to expand...
Click to collapse
So now I flashed TWRP again. Does someone know what I should do to install the update ? Preferably without returning to stock first.
Solved
Feeling a bit stupid really...
Right under my post in the list was this post which deals with my problem exactly. I just updated my phone using that guide.
Hi Guys,
I have an unlocked Desire S running TWRP 2.6.3.0. I've never had any problems installing new builds before, but every time I do now it always failed and I always get the error "Error executing updater binary in zip '/sdcard/cm-11-20161203-UNOFFICIAL-saga.zip"
I've tried installed the Open Desire Project Cyanogenmod builds 11, 12 and 13. The phone previously had 11 installed and I had no problems whatsoever flashing it. Any help would be greatly appreciated!
I've been using ResurrectionRemix a few months now and never had any issues with it. Today I tried flashing the newest update (2017-07-07) from sourceforge as usual. Now I'm stuck in a bootloop.
Things I've tried, all using ADB sideload from within TWRP:
- flashing older versions (RR-N-v5.8.3-20170620-bacon-Official & RR-N-v5.8.3-20170609-bacon-Official) that have worked before
- uninstalling magisk
- wiping cache/dalvik
- change up the order in which I did those things
Any ideas? I had this issue once when I flashed an update to RR and accidently installed SuperSU when TWRP asked for it, but flashing the update again helped out and probably removed SuperSU. No idea what's going on here. Will provide additional information where needed. Thanks!
I have the following installed:
[url]https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670[/URL]
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
-Snowrider- said:
I have the following installed:
https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
Click to expand...
Click to collapse
Try the following :
-uninstall magisk using uninstaller(available in magisk forum)
-clear system,data,cache,dalvik
-install only the rom with out gapps
if it boots properly then you can install the gapps later or else if u find flashing gapps is causing the bootloop then use an older version and double check the compatibility.
if still not just try out another nougat rom
Thanks for the suggestion.
I tried your steps with the latest stable slimrom 7.1.2, lineage 14.1 and carbonrom 5.1 and I am still seeing the same issue. I was able to clean install the lineage 15.1 beta I linked to though in addition to restoring my backup as I have done before. I might try to clean install a different 8.1 (AOSP for example) and see if that one works. This will help narrow down if the issue is caused by 8.1 in general or specifically something that the lineage 15.1 beta has done.
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
CedArctic said:
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
Click to expand...
Click to collapse
This is what I ended up doing and it did the trick. Thank you for the suggestion.