Hi XDA,
I seldomly post anything cause most of the time i can find the answer down here but this time im stuck
as the title says i'm unable to flash any cm12 based rom i always get the error below and the installation stops:
"error executing updater binary in zip"
I'm on the latest TWRP recovery 2.8.6 and run the 3.19 hboot
In the past i was able to go from sense, to GPE, CM, AOKP, etc without any problem so somethings changed
My first thought was there was an issue with the recovery or the firmware.
it wasn't the first because phil's recovery also gives the error so if its the last I need some help
Bump
oGrady said:
Hi XDA,
I seldomly post anything cause most of the time i can find the answer down here but this time im stuck
as the title says i'm unable to flash any cm12 based rom i always get the error below and the installation stops:
"error executing updater binary in zip"
I'm on the latest TWRP recovery 2.8.6 and run the 3.19 hboot
In the past i was able to go from sense, to GPE, CM, AOKP, etc without any problem so somethings changed
My first thought was there was an issue with the recovery or the firmware.
it wasn't the first because phil's recovery also gives the error so if its the last I need some help
Click to expand...
Click to collapse
Are you on the latest 4.xx firmware? CM ROM are recommended to have 4.xx firmware before flashing.
And recently CM12 builds are a bit buggy, though recovery shows "error executing updater binary in zip" but in fact the ROM is installed successfully, just reboot and all is fine.
And to proof that you didn't search totally on XDA, look here
Bobbi lim said:
Are you on the latest 4.xx firmware? CM ROM are recommended to have 4.xx firmware before flashing.
And recently CM12 builds are a bit buggy, though recovery shows "error executing updater binary in zip" but in fact the ROM is installed successfully, just reboot and all is fine.
And to proof that you didn't search totally on XDA, look here
Click to expand...
Click to collapse
He is on the 3.19 hboot, should be enough and good to go
Thanks for the replies guys this is helpful, I'll check it out after work.
I thought my firmware upgrade to the 3.19 hboot must have messed something up.
But if CM12 Builds are buggy as of right now i'm gonna wait.
@Bobbi lim: Yes i did not look that up, because i assumed it was my own doing that caused the error in the first place
Related
So for some reason, I catch an error everytime I try to flash a rom to my phone. Then I am forced to restore my backup.
I have it rooted with CWM v5.5.0.4.
i747.
Not sure what other information you guys would need to assist. Would I need to re-root it? Different version of CWM?
Are you wiping data before you flash any new roms? That could be it..
Yep, always wipe data/factory.
.... i'm pretty sure that telling us what the error message says would help, too....
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
jethro650 said:
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
Click to expand...
Click to collapse
Agreed, almost undoubtedly...in every recovery flashable .zip there is an update-binary file which is the actual executable that is commanded by the update-script on what operations to perform. The newer versions of this binary are incompatible with older versions of the recoveries. This effect is not necessarily one way either, an older recovery trying to flash a new .zip or vice versa can produce this error but as a general rule using the newest recoveries should minimize this problem. The only time the reverse is a problem is when there is an update to the recovery api and there hasn't been an updated update-script built into a .zip. The easiest way to check is download the appropriate rom manager for your recovery, Clockwork Rom Manger for CWM or Goomanager for TWRP.
Hello folks,
My phone is currently rooted, running Android 4.4.2. The bootloader is 1747MVLUFNH2. It is the Telus, i747M variant of the S3.
I am using ClockworkMod Recovery, Version 6.0.4.7 and trying to flash Cyanogenmod 10.2.1 (the latest stable release for this phone).
When I flash the Zip in CWM, the installation aborts and I get a Status 7 error. I have tried earlier releases of CyanogenMod, but they have resulted in the same error. Presumably, this is because my bootloader is not listed among those in the asserts of the ROM.
I have found old threads where folks have noted that, when running bootloaders from the ICS era, you can't flash any Cyanogenmod roms past 10.1. I figured that maybe my bootloader is one of these old ones, but from my research "FNH2" appears to be the newest. In most of the lists featured online, mine doesn't even show up. I understand that reverting your bootloader back to an old one is a huge "no no", and would likely result in my phone being bricked.
I suppose all of this leaves me wondering whether I am caught in some sort of limbo, where my bootloader is in fact too "new" for a relatively old version of Cynanogenmod (10.2.). The phone was recently given to me by my brother, and I am not sure how he updated the bootloader/firmware, but it was likely through Kies.
My end goal is just to have some stable version of Cyanogenmod running, and I've run out of ideas as to how I can make it work. I have tried using Cyanogenmod's "One Click Installer", and that seemed to work well until the phone rebooted to the stock ROM that had been running before; leaving me with effectively no change at all. I have verified root access, and gapps zips seem to extract and install just fine.
Any ideas or pointers would be greatly appreciated.
Thanks.
Why not run the latest cm11 for the d2lte? CM10.2 is only JB.
audit13 said:
Why not run the latest cm11 for the d2lte? CM10.2 is only JB.
Click to expand...
Click to collapse
I've actually tried that, but I still get the Status 7 error, even with a CM-11 nightly.
I flashed back to the stock ROM, with the most current bootloader, etc. It still won't flash any CM zip from CWM, and the Installer doesn't seem to work either. It will install CWM, and say that everything went ok, but when the phone reboots, it's still the stock ROM.
p.s. the CAPTCHAs on this forum are damn near impossible.
"It will install CWM, and say that everything went ok, but when the phone reboots, it's still the stock ROM."
If you're having trouble installing CWM, try this: re-flash CWM or Philz in Odin and do not check anything except r.reset.time, flash recovery, remove the USB cable when you see reset in the status window, remove the battery, replace battery, boot into recovery.
If the latest version of CWM is working properly and you get the status 7 error, try to pull a logcat.
Hey there,
My HTC One m7 vzw HBOOT 1.56. cannot use its storage after flashing teaMSeven kernel.
I use cyanogenmod 11 last stable release and TWRP 2.8.4.0.
My device is rooted, s-on and it is "TAMPERED UNLOCKED"
When the device is in the recovery, the problem does not appear.
I tried to flash a different ROM and it says "error executing updater binary in zip sdcard...
or " unable to mount /system". I can flash CM 11 and boot into it but i cant save or download anything on the Phone.
I also tried to flash a different kernel (tinykernel-m7-cm11) -nothing changed
pls help me !
ps. yes I know my english is bad, its because i'm German
maxizocker said:
Hey there,
My HTC One m7 vzw HBOOT 1.56. cannot use its storage after flashing teaMSeven kernel.
I use cyanogenmod 11 last stable release and TWRP 2.8.4.0.
My device is rooted, s-on and it is "TAMPERED UNLOCKED"
When the device is in the recovery, the problem does not appear.
I tried to flash a different ROM and it says "error executing updater binary in zip sdcard...
or " unable to mount /system". I can flash CM 11 and boot into it but i cant save or download anything on the Phone.
I also tried to flash a different kernel (tinykernel-m7-cm11) -nothing changed
pls help me !
ps. yes I know my english is bad, its because i'm German
Click to expand...
Click to collapse
Hi, You'll need to run this RUU here. It repairs mount/partition/system problems:
http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
After running, do a factory reset, then it is 100% stock and everything will be working.
[Q] Need help in solving "Unfortunately, settings have stopped working" error
Problem: My unrooted SGH-I747 model AT&T GS3 recently gave me this error whenever trying to access the settings. The error shows up even after a full factory reset and I can no longer access my phone. Stuck a little after the language selection in the beginning stages of the setup.
Attempted fixes: Obviously, the initial factory reset. Then clearing the cache + factory reset.
After those failed to work, I tried to flash to a AT&T stock rom from this forum (http://forum.xda-developers.com/showthread.php?p=33570269#post33570269) using Odin. I tried to use the first row of downloads but the first row but it did not have a MD5 file, so I used the second row of downloads instead but this rom failed to install. My guess is that it may be too old of a version.
I would appreciate any help.
[SOLVED]
The problem may have arose from a critical error in the phone's software that had affected the OS system of the phone. I resolved the issue by flashing a new custom OS (cyanogenmod) to my phone. These are the steps that I took:
1. Installing Odin (http://forum.xda-developers.com/showthread.php?t=1722686)
2. Rooting my cellphone with CFAutoRoot using Odin (http://forum.xda-developers.com/showthread.php?t=1725839)
3. Installing a custom recovery TWRP -- highly recommended very user friendly (http://forum.xda-developers.com/showthread.php?t=1793224)
4. Installing a new custom rom through TWRP-- used Cyanogen (http://forum.xda-developers.com/showthread.php?t=1778270)
5. Installing gapps (http://opengapps.org/?api=5.1&variant=nano)
6. Identifying the correct bootloader by downloading and installing Samsung Phone Info by vndnguyen through the Play Store.
7. Installing the correct bootloader and modem (http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006)
Please refer to respective installation guides for more instructions regarding installation of any new software.
I hope this helps anyone who may have run into the same problem.
Before attempting to flash anything, confirm the bootloader on your phone. An easy way to determine if the bootloader is 4.3 or newer, boot into download mode. If you see anything about warranty bit, your phone has at least a 4.3 bootloader and no attempts should be made to flash anything from sammobile.com.
If you have a 4.3 or newer bootloader, I recommend flashing a custom recovery such as TWRP, and then flashing a stock ROM from recovery.
First off, thank you for the reply audit!
Now I have officially rooted my phone using CF-Autoroot and have installed TWRP. I have also confirmed that the bootloader is at least 4.3 because it does show the warranty bit.
Which of the stock roms are compatible with this bootloader?
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
audit13 said:
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
Click to expand...
Click to collapse
Just to be clear, cm12.1 is the cyanogenMod nightly?
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
audit13 said:
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
Click to expand...
Click to collapse
I'll try it out and see if I can get past the language screen this time.
Got the latest Cyanogenmod Zip file onto my phone. Tried flashing it through TWRP with the install option but it failed.
Log reads that no MDS file was found, detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system. Can't install this package on top of incompatible data.
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
5K posts.
"all i can really do , is stay out of my own way and let the will of heaven be done"
I'm pretty sure that CM de-unified the variants for CM 12.
From: https://wiki.cyanogenmod.org/w/D2lte_Info
Note: Unified device
Between the release of CM 11 M3 and CM11 M12, all Qualcomm-based variants of this device were merged into a single build: d2lte. The device information pages for the individual variants should be used to reference any device-specific unlock instructions, download recoveries, to build CM 10.2, or to install CM 12.1: d2att, d2cri, d2mtr, d2spr, d2tmo, d2usc, d2vzw.
Click to expand...
Click to collapse
I think this was just to make searching a bit harder/ more complicated.
audit13 said:
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
Click to expand...
Click to collapse
For d2att and running 2.8.7.0 for TWRP.
You should be good then.
The file should be left unzipped/unrared when using it right? I'm using it as such but it keeps returning the same error message saying that it won't install it.
Yes, leave it zipped. What is the TWRP error message?
The error log:
detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system.
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 '/sdcard/Download/cm-12.12015913-NIGHTLY-dtatt.zip
Error flashing zip '/sdcard/Download/cm-12.120150913-NIGHTLY-D2att.zip
Weird, did you do a full wipe before trying to install?
Can't believe it was that simple. I thought I had already made the wipe when I did it with the original recovery but making a second wipe through TWRP actually helped make it happen. I finally got through and have full access to my phone.
Unfortunately, the cell service doesn't seem to work but I'm guessing that I need to do more for the set up?
Edit: Not recognizing the sim card for some reason
Sounds like you need to update the bootloader and modem to the older KK version which I think is ne4.
Sorry for the late reply I've been busy the past week. I'm guessing the modem won't work without the proper bootloader? I've tried flashing the latest and original modem from the Modem list (http://forum.xda-developers.com/showthread.php?t=1831898). While they installed successfully I still don't get a signal.
I was worried which bootloader to take because it may lead to bricking. Which one are you referring to and are they in the Bootloader updates topic here? (http://forum.xda-developers.com/showthread.php?t=2321310)
Hi guys,
I tried to flash LineageOS 13.0 and 14.1 but it fails and I get shown the error "Error executing updater binary in zip". Since I am no professional for sure I thought I might ask you guys. How can I fix this?
If you need further information about my device dont hesitate to tell me.
imgur.com/a/64IbJ
If I missed a thread discussing this issue please excuse me.
Kind regards
-Pierasso
edit: Just noticed I posted this in the wrong forum, sorry!
edit2: Alternatively I'd be happy if someone could upload or link me a backup of the stock rom. For some reason mine got corrupted
pierasso said:
Hi guys,
I tried to flash LineageOS 13.0 and 14.1 but it fails and I get shown the error "Error executing updater binary in zip". Since I am no professional for sure I thought I might ask you guys. How can I fix this?
If you need further information about my device dont hesitate to tell me.
imgur.com/a/64IbJ
If I missed a thread discussing this issue please excuse me.
Kind regards
-Pierasso
edit: Just noticed I posted this in the wrong forum, sorry!
edit2: Alternatively I'd be happy if someone could upload or link me a backup of the stock rom. For some reason mine got corrupted
Click to expand...
Click to collapse
You need to update your TWRP if you are going to flash any rom. That is why you are getting errors... https://dl.twrp.me/hima/
You can find a stock rom here. https://forum.xda-developers.com/ve...-verizon-htc-one-m9-marshmallow-3-37-t3318605
Flyhalf205 said:
You need to update your TWRP if you are going to flash any rom. That is why you are getting errors... https://dl.twrp.me/hima/
You can find a stock rom here. https://forum.xda-developers.com/ve...-verizon-htc-one-m9-marshmallow-3-37-t3318605
Click to expand...
Click to collapse
Thanks mate, gonna try it asap!
Edit: Tried now a couple of ROMs. Most of the time I just get the same error and if it does indeed install, after rebooting it just goes directly into the bootloader again and wont boot the ROM
Weird thing is than I had it working before with that recovery and lineageOS 13
pierasso said:
Thanks mate, gonna try it asap!
Edit: Tried now a couple of ROMs. Most of the time I just get the same error and if it does indeed install, after rebooting it just goes directly into the bootloader again and wont boot the ROM
Weird thing is than I had it working before with that recovery and lineageOS 13
Click to expand...
Click to collapse
What firmware are you running? Try updating that.
Flyhalf205 said:
What firmware are you running? Try updating that.
Click to expand...
Click to collapse
Hi mate,
I updated the firmware with "3.37.605.28_NoBoot_TWRP3.1.0-0_firmware.zip" from the "★ ☆ [6.0][FIRMWARE/RUU] Verizon HTC One M9 Marshmallow 3.37.605.28 Resources ☆ ★" thread (cant post links)
I managed to update twrp to the most recent one and I can finally install LineageOS 13. But for some reason it installs the rom but after the LineageOS bootanimation it keeps shutting down and rebooting.
Any idea on how to fix this? So far you were really helpful mate!
Edit: I always got "updater process ended with error 7" when installing a ROM so I edited the file "updater-script" with this guide: forum.xda-developers.com/showthread.php?t=2522762
Edit2: Now my phone will reboot after booting no matter which ROM I use. Not even my backup will work now.
pierasso said:
Hi mate,
I updated the firmware with "3.37.605.28_NoBoot_TWRP3.1.0-0_firmware.zip" from the "★ ☆ [6.0][FIRMWARE/RUU] Verizon HTC One M9 Marshmallow 3.37.605.28 Resources ☆ ★" thread (cant post links)
I managed to update twrp to the most recent one and I can finally install LineageOS 13. But for some reason it installs the rom but after the LineageOS bootanimation it keeps shutting down and rebooting.
Any idea on how to fix this? So far you were really helpful mate!
Edit: I always got "updater process ended with error 7" when installing a ROM so I edited the file "updater-script" with this guide: forum.xda-developers.com/showthread.php?t=2522762
Edit2: Now my phone will reboot after booting no matter which ROM I use. Not even my backup will work now.
Click to expand...
Click to collapse
Something probably got ginked up in the process and I would start over with RUU at this point.
Back up anything important on your internal memory as this will wipe your device and ruu - https://forum.xda-developers.com/showpost.php?p=65358513&postcount=4 - then factory reset from stock recovery and flash 3.37.605.28_NoBoot_Twrp3.1.0-0 - https://forum.xda-developers.com/showpost.php?p=65358020&postcount=2 and you're on your way again
Flyhalf205 said:
You need to update your TWRP if you are going to flash any rom. That is why you are getting errors... https://dl.twrp.me/hima/
You can find a stock rom here. https://forum.xda-developers.com/ve...-verizon-htc-one-m9-marshmallow-3-37-t3318605
Click to expand...
Click to collapse
Thanks, it worked. i loged in just for thank you