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
Related
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
So, I had Asia 5.0.2 and I saw a FIUI ROM for our device at the MIUI forums. I decided to give this a go and first downgraded to KK and then tried to flash the zip from TWRP and Philz recovery but got this error:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I thought it might be a ROM specific error, but I also tried to flash CM11 but got the same error. How can I get around this? Is this an issue with the updater script or something?
Any help will be appreciated.
prateektaneja said:
So, I had Asia 5.0.2 and I saw a FIUI ROM for our device at the MIUI forums. I decided to give this a go and first downgraded to KK and then tried to flash the zip from TWRP and Philz recovery but got this error:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I thought it might be a ROM specific error, but I also tried to flash CM11 but got the same error. How can I get around this? Is this an issue with the updater script or something?
Any help will be appreciated.
Click to expand...
Click to collapse
Did you do a factory reset from the recovery menu?
I've used CM12.1 based ROMs for a while now, and with my talent have managed to brick my bacon (oneplus one global 64GB), and unbrick it (using this guide)
I've restored it to stock with no problem using this tool.
my problem begins when i try to update to any LP ROM - flashing such ROMs' zip files in TWRP returned "E: error executing updater binary in zip". i found two solutions to this error:
1. first one is described in this thread. i ditched this method after it got me stuck in bootloop every time after flashing a ROM
2. second one (probably the way it should be done) is to update device firmware like described in this oneplus forums thread. flashing this zip indeed allowed me to successfully install my ROM but with one big problem - the SIM card is detected for a few seconds (even then the device wont find any networks) and then drops to "no SIM card detected - emergency calls only" then it gets detected again and so on...
I've also tried flashing some different modems like described here but it didn't change anything
have anyone encountered any network related problem after upgrading to a CM12.1 based ROM or have any idea how to solve my problem (mobile network connections won't function after upgrading to cm12 firmware)?
help would be very appreciated!
edit: if it helps, i also found that OTA updating to the latest build XNPH44S also breaks the phone's ability to connect to a mobile network
Get the oneplus one build which was released as a fix to ghost touch.. It is nothing but oxygenOS!! Backup ur data and follow the instructions and flash the oxygen rom then wait for the first boot after first boot just update ur recovery to latest twrp and get the bacon firmware update zip file from any of the major rom threads like blisspop or exodus then flash that then flash the latest cm12.1 nightly and AK kernel(optional) then boot it up!!!
Transmitted via Bacon
yashshan said:
Get the oneplus one build which was released as a fix to ghost touch.. It is nothing but oxygenOS!! Backup ur data and follow the instructions and flash the oxygen rom then wait for the first boot after first boot just update ur recovery to latest twrp and get the bacon firmware update zip file from any of the major rom threads like blisspop or exodus then flash that then flash the latest cm12.1 nightly and AK kernel(optional) then boot it up!!!
Transmitted via Bacon
Click to expand...
Click to collapse
1. TWRP must be installed before installing OxygenOS as it comes as a flashable zip and not an OTA/Cyanodgen update...
2. installing OxygenOS was no problem without the firmware, however after it booted i noticed it broke my mobile communications in a very similar way, so no luck with that one.
3.even after installing oxygen the firmware update is required to install anything like a CM nightly or a CM based LP ROM, and my problem was that this firmware upgrade broke my network connection, so i don't see how that could help me in any way
3.1 after flashing OxygenOS not even the firmware update would allow me to install a different ROM...
4. i linked the forum thread my firmware update came from (also found a similar suggestion in a YouTube video) and couldn't find any reference to it in any of the main ROMs' threads like you suggested, they all just say to install TWRP wipe everything and flash their zip (some say to flash a nightly before)
any other ideas? I'm starting to get desperate around my suddenly not-so-functional bacon :crying:
!!SOLVED!!
steps:
1. flash the latest CM12S fastboot image
2 .delete line 2 "aassert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");" from the updater-script file in the custom ROM's ZIP installation file
3. flash the "hacked" zip file with no problem
4. enjoy your custom ROM installed bacon, WITH your mobile connection.
thanks for the help anyway!
Hey, so i formatted the boot partition by accident today and could not boot anymore.
I was on a 5.1.1 Custom ROM before that. So i googled a bit and found a fix by flashing the Stock Firmware. Downloaded a 4.4.4 Stock Firmware here (RETAIL-DE) and flashed it using the commands here (as described in 3b). The second command failed with "Preflash validation failed". I believe thats because i had bootloader version 4.1.19 already and its not possible to flash an older one over that.
After that i could boot the phone again into the Stock Android 4.4.4. So i wanted to go back to an Lollipop or Marshmallow ROM. Using fastboot i flashed the latest TWRP Recovery and used it to flash a Custom ROM. I've tried several ROMs but every ROM results in an bootloop. Also tried using TWRP 2.6.0.0 and 2.7.0.0, but it didnt change sth.
I hope someone can help me solving this issue. Thanks.
You should probably full-flash the latest original Motorola firmware (GPE 5.1 or stock 5.0.2) before putting TWRP and custom roms based on Android L or M.
Hey there.
So, my 6045 was on that awful MM update filled with ads, so I changed the firmware to the Panasonic one in order to be able to install TWRP and next flash either Lineage or RR.
I have no problem installing TWRP using the Idol 3 suite (Here), however, whenever I try to flash the Lineage zip, or the RR zip, it gets stuck on the Powered by Android screen.
I always wipe everything before flashing the zips.
I have tried wiping cache/dalvik after flashing them, and also not wiping. Either way, and with both roms, the phone gets stuck, and I need to use the Panasonic tool again to restore the phone to a functioning state.
Please help, I've been repeating this process about 10 times, and it's getting very frustrating.
Thanks.
EDIT: Is the version of TWRP somehow relevant for this? The latest version I can install is 3.0, from the link provided. If I try to install this one I get a bootloop. Please help.
Hi, u need to flash the MM partitons zip first then the rom . Look on AlekDev customs roms threads, he usualy has the MM partition file.