So last night I went about installing a new custom ROM on my HTC One S, proceeded to unlock via the official app, and completed that step.
Upon attempting to install the custom ROM (that I got from the official CM site, the ROM being CM12, made sure it's for my device), I also deleted the backup I made of the system and now I am stuck with a bricked phone.
The problem is : I have a ROM and a custom recovery, BUT whenever I try to install the ROM, I keep getting this error message
E:Error executing updater binary in zip
Error flashing zip
The phone has been flashed before to android 4.4 with HTC Sense 6, if that information helps.
As I said, the custom ROM is from the official site, stable version, and the phone is bootloader unlocked.
Solution
Solved, had to install a ROM that complied to the HBOOT version (i.e. 2.16.0)
Related
Hi guys! So I'm obviously new here, the HTC One X being my first Android phone. I have rooted and unlocked my One X's bootloader (AT&T) and installed the ClockWork Recovery Tool. I decided that I wanted to install the Android Revolution HD ROM (First Custom ROM, was on the Stock Sense), and so I followed the instructions, first I put the Super Wipe files and the ROM intself on the SD Card, then I flashed the boot.img to my phone through fastboot, then I went to Recovery from the bootloader screen and tried to install the Super Wipe zip file...
This is when things began to fail, the Install was aborted, giving me "Status Code 0." When I tried to Install the ROM Itself after this, the install for that was aborted, too. "Status Code 1." Does anyone have any advice? Thanks Guys!
My advice would be to post the question in the Clockwork or Revolution forums.
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Download latest recovery from http://forum.xda-developers.com/nexus-s/development/crespo-philz-touch-t2284670
Then try to flash the ROM. It seems your recovery is very old.
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
@smit.sanghavi is right.
You need KitKat compatible Recovery. Update your recovery and then try to flash the ROM.
K guys, wanted to try all you said, but there's another problem.
I discovered my nexus isn't rooted. Bootloader unlocked, but any root checker says its unrooted (of course it was before...). So I'm trying to reroot it but when im connecting my phone via usb in bootloader windows 7 doesn't recognize the device. When the phone is connected in recovery or in normal usb debugging mode it recognizes it as adb android, looks good to me. I go back to booloader and i get "Windows has stopped this device because it has reported problems. (Code 43)" in Devices.
Installed the drivers on few different ways.
So.... what now ?
UPDATE: solved
Hi,
I wonder if anyone could offer me a little assistance please ? I have a UK Tesco Moto G 16GB (2013) that I have successfully unlocked the bootloader and rooted and CWM recovery installed. Currently, it's running 4.4.4 Kitkat. I gave up with the OTA update as I was getting the 'preflash validation failed' message. More recently, I have tried following the guide on here to flash the XT1032_GPE_5.1_Optimized_v1.1.zip file using CWM. However, this resulted in what I believe is termed a bootloop - i.e. the coloured dots animation just never stopped - I waited half an hour and it was still going.
I've managed to restore it back to my previous 4.4.4 for the moment, but I would like to move to Lollipop at some point - if I could !
Could someone suggest a method I could try please ?
Many thanks !
Kev.
Hi there.
Well, my device is a XT1032 Retail US but I may have been through the problems you're facing right now.
Here we go:
Go full stock (don't know if you revocer from a backup or already did this but in any case you'd know what to do: This guide helped me a lot. http://forum.xda-developers.com/showthread.php?t=2542219.
Do not install any official update using a custom recovery
Make sure you got the actual latest recovery version. If you went stock from the latest firmware you should have already got it.
If you have your OTA, Install it manually from the stock recovery
This method should work. It is the one I followed.
I got two errors: 1st was because was using custom recovery.
2nd was because my rom was stock but had deleted system apps, so the install failed always at some point.
Once I flashed the latest stock firmware including the stock recovery, I was able to install my OTA update.
Let me know if this works.
So I've had a chinese version of the opo since last summer, first thing I did was root it and unlock bootloader etc. I've been running a rom for quite a while (really embarrassing, but can't remember what rom). And I tried to flash a new one, but I got greeted with the message "error executing updater binary in zip". I've tried most things, updating firmware, updating to latest recovery, wiped everything, then trying to install, then rebooting and trying again, but no luck. Running CM12 nightlies work, so does oxygenos, however they're not that good tbh. Would love any help
Roxkyp said:
So I've had a chinese version of the opo since last summer, first thing I did was root it and unlock bootloader etc. I've been running a rom for quite a while (really embarrassing, but can't remember what rom). And I tried to flash a new one, but I got greeted with the message "error executing updater binary in zip". I've tried most things, updating firmware, updating to latest recovery, wiped everything, then trying to install, then rebooting and trying again, but no luck. Running CM12 nightlies work, so does oxygenos, however they're not that good tbh. Would love any help
Click to expand...
Click to collapse
Flash latest CM12.1 nightly first
And then flash your desired ROM
Or else
Flash factory images of latest version Cyanogen OS 12.1 and then flash TWRP and then your desired ROM
Guide to flash ROMs and factory images >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Mr hOaX said:
Flash latest CM12.1 nightly first
And then flash your desired ROM
Or else
Flash factory images of latest version Cyanogen OS 12.1 and then flash TWRP and then your desired ROM
Guide to flash ROMs and factory images >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Unfortunately these methods did not work for me, I can get on 12.1, but when I want to flash something else (resurection rom in this case) I get the error.
Its a firmware issue you need the correct firmware
I am having a problem installing customs ROM on stock LG G2. My phone was bricked so I reverted to stock AT&G firmware using LG flash tool (Android version - 4.4.2, Kernel version - 3.4.0).
I then perform the following steps:
(1) Enable developer mode with USB debugging
(2) Use Kingo Root to root phone
(3) Install TWRP using AutoRec
(4) Update TWRP to latest version (3.2.1)
This is where the problems start. I get the same result when I try installing crDroid 7.1.2 or Resurrection Remix 5.7.4 custom ROMs.
The installation of the custom ROM (and gapps) succeeds in TWRP and then I reboot the system. However, the reboot always results in the "LG" logo showing for 1/2 seconds and then a constant black screen.
I am able to recover the phone from this by putting it into firmware update and then using LG Flash tool however I would still like to successfully install and use the custom ROMs. Not sure why this is happening (I am sure it might have been treated with in the forums however I cant find anything). Any help would be appreciated here as I really do not want to be stuck on stock AT&T firmware.
Update
randyesh said:
I am having a problem installing customs ROM on stock LG G2. My phone was bricked so I reverted to stock AT&G firmware using LG flash tool (Android version - 4.4.2, Kernel version - 3.4.0).
I then perform the following steps:
(1) Enable developer mode with USB debugging
(2) Use Kingo Root to root phone
(3) Install TWRP using AutoRec
(4) Update TWRP to latest version (3.2.1)
This is where the problems start. I get the same result when I try installing crDroid 7.1.2 or Resurrection Remix 5.7.4 custom ROMs.
The installation of the custom ROM (and gapps) succeeds in TWRP and then I reboot the system. However, the reboot always results in the "LG" logo showing for 1/2 seconds and then a constant black screen.
I am able to recover the phone from this by putting it into firmware update and then using LG Flash tool however I would still like to successfully install and use the custom ROMs. Not sure why this is happening (I am sure it might have been treated with in the forums however I cant find anything). Any help would be appreciated here as I really do not want to be stuck on stock AT&T firmware.
Click to expand...
Click to collapse
Update: It seems as if older ROMs can be installed with no issues. I got a copy of Cyanogen 12 and it installed perfectly and works fine. However, trying to install new ROMs still give issues. Don't know if I am missing something here and/or someone had a similar previous experience.