I've been trying to update on the PAC-ROM Nightly channel. I originally tried to flash the 9/20 update, then tried again with the 9/27 update and had the same issue. The original error message I got was simply "Error executing updater binary in zip" and I used a fix from OPO forums. After using I still get the same error message along with "assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0123")=="1". Some other threads on similar issues said I have to update to the CM12 firmware, but I have been updating on the same channel for the past 3 months or so with no issue. Only in the past two weeks has this been an issue. How can I proceed to update my ROM?
Related
Ok so here is the deal, I have read all of the different instructions, I fancy myself as someone who knows how to follow directions, and I am still receiving an error while trying to do the manual update.
The first error I receive is this one: E:Can't open /cache/recovery/command I get this error when I go to the system recovery screen, but it still allows me to choose "apply sdcard:update.zip [Alt+S]"
The second error I receive is:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current System...
assert failed: apply_patch_check
("MTD:boot:1888256:52022649d20fe
178f866dc52df8e882bd3da66bf:2357
248:84385c90406d6449ee5be40da765
cf77baaf6e58")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
This error is received when I click "apply sdcard:update.zip [Alt+S]
I hope someone can help me with this. Also before you ask, my phone is the MyTouch 3G 3.mm (non-fender), and to my knowledge it is stock. I have no interest in rooting my phone, so that is why I know I didn't root it. However, it is a recent referb that I received from T-mobile after my first one took to the grave. I appreciate anyone willing to be patient with me.
**UPDATE**
My OTA came through last night but it is also failing when it gets about half way through the installation. Anyone have an idea what could be causing this and how I can fix it?
I've encountered this recently and have no idea what causes it!
Long story short... i was trying to get off the Vodafone ROM from my phone and hopefully update too in the process. I flashed a couple of stock ROM images but each time the OTA would fail during installation as would a manual install. At first it would fail signature checking, so i would disable the check using Clockworkmod, run the update again and then i would get the error you posted.
I'm wondering now if the official 2.2.2 update will ever work, even when Vodafone release it, and whether the 2.3 update will also fail when that is released.
You and i may have to bite the bullet and go down the fully custom route. Once Gingerbread is released i'm hoping that one of the chefs releases a nice Stock version that i can use
Actually...
I was soooo frustrated with the way I was treated by a T-mobile rep, when I called about the error today, that I decided to cancel my service with them. I have had several issues with their products and services and continued to give them chances. However, after today's incident I decided to terminate service... just as soon as my new phone from my new provider arrives on Friday.
In addition, since I am no longer going to be using the phone, I decided to try my hand at rooting.... and what do you know, I did it without a problem. LOL Oh well.
Congrats on getting a new phone. It never hurts to have an old one spare to use for experimenting with new ROMs etc.
Hi guys,
I received an update to my device, but after I've started the update, it stopped updating.
I also tried with the "update.zip" file to the sdcard but it gave me an error ( status 7).
I've seen similar posts to this... I'm not exactly sure what the problem is, but maybe these links can help??
http://forum.xda-developers.com/showthread.php?t=1288370
http://forum.xda-developers.com/showthread.php?t=1298673
http://forum.xda-developers.com/showthread.php?t=1135929
So i've lurked in the forum forever, just now made an account. I don't have enough experience to post within the DEV forum so here we are. I've been using CM as my go to rom, just found out that MIUI V5. The issue is that when I flash the rom it FAILS. My Team Win recovery reads as follows 'Installing MIUI 4.6.6 / Skipping MD5 / E:Error executing updater binary in zip / Error flashing zip / Updating partition details...' FAILED. I didn't realize it did that the first time and I booted it and MIUI functioned what seemed to be fine. Now I see this is an issue it annoys me, HELP!
It's a known issue, sorry it annoys you.
Sent from my Nexus 5 using XDA Free mobile app
I was having this issue as well. Was generally just confused - I switched from twrp to cwm and was still getting those errors. On CWM it just says "Installing update..." For about 5 minutes before failing and when I rebooted it works. MIUI really messed up something in the script I guess.
I need some help/advice..
I have a 2013 Moto G purchased from Amazon (USA 16 GB Version)
I used the older instructions to convert it to a GPE running Lollipop 5.0 and everything worked fine. I switched to a different phone and set it aside as a spare. I decided a few weeks ago to get it upgraded in case I needed to use it. I tried to do the OTA updates and the first one worked. On the second one, it failed. I tried several times before downloading the latest firmware for the GPE and installed it. During the install, I got an error (don't remember what it said) but the install continued. On reboot, everything looked fine. Everything worked (Wi-Fi, camera, etc) but when I put the SIM from my Moto X in, it kept saying insert SIM. Nothing I tried fixed it. I then flashed the stock ROM and on reboot, it kept restarting the Optimizing Android routine. It would finish, black screen and start over. I then flashed the GPE ROM and still No SIM, but everything works fine. Last night, it got a notification of a patch, told it to install and it failed with the following error: /modem/image/adsp.b01 has unexpected contents E:error in /cache/update.zip (status 7) Installation Aborted. I reinstalled the GPE ROM and stock modems and still No SIM, but everything works fine. Last night, I tried the patch again on each set of modems and it failed with the following error: /modem/image/adsp.b01 has unexpected contents E:error in /cache/update.zip (status 7) Installation Aborted.
I then tried to reinstall the GPE ROM and got the error seen in the picture below:
Any advice or ideas to get back to a working, updatable system?
HELP
Anyone have any ideas to get this fixed and working?
Trying to install CM yields the error "Error executing updater binary in zip"
Hi! So I was a long-time android user, however, I had loaned my G2 AT&T out to a friend of mine while I was using an iPhone due to service issues. I recently got it back and would like to break back into the scene but after a couple years I'm a little nooby. I updated my TWRP but when trying to flash CM 12.1 I receive an error. In red it says:
E: Error executing updater binary in zip '/sdcard/cm-12.1-20151117-SNAPSHOT-YOG7DAO1KI-d800.zip'
I was able to get in what appears to be a broken PA installation, which fortunately includes file system exploration and messaging. Accessing the phone from the computer is no problem either. Any idea what the issue here may be? I've tried a couple of different things but haven't been able to get an actual complete install in.
I appreciate your guy's help! I tried scouring google but all I found appeared to be quick fixes for specific phones, barring one post who suggested flashing a file with a mysterious origin I didn't want to play around with that haha!
Cheers
Most likely a corrupt file. Try redownloading the ROM and get back to me.
---------- Post added at 09:28 PM ---------- Previous post was at 09:25 PM ----------
That or it doesn't support your specific model of the G2. And there's nightly's for your device in the CM 13 branch that I'd check out
https://download.cyanogenmod.org/?device=d800
Hey! I tried that twice and each time it resulted in the same error
I had seen the 13 nightlies but I was worried about some people having reported no gps functionality so I thought I'd go with the more stable build... I'd MUCH rather have marshmallow if it's totally working and all of that though. Mostly I just want a complete OS though :crying: