New to the forum as a member but I have been learning a lot from the people that post here.
I have now come to a point where I am now needing help.
I would like to install the Cyanogenmod OnePlus One stock ROM and I am being prevented by the updater binary.
I have tried using the latest version of TWRP (2.8.0.1), TWRP (2.7.0.0) as well as an older version (2.6.3.3) and to no avail.
Can anyone highlight to me what I must do to fix this issue?
martay777 said:
New to the forum as a member but I have been learning a lot from the people that post here.
I have now come to a point where I am now needing help.
I would like to install the Cyanogenmod OnePlus One stock ROM and I am being prevented by the updater binary.
I have tried using the latest version of TWRP (2.8.0.1), TWRP (2.7.0.0) as well as an older version (2.6.3.3) and to no avail.
Can anyone highlight to me what I must do to fix this issue?
Click to expand...
Click to collapse
This is a recovery issue. use version 2.7.0.8
zelendel said:
This is a recovery issue. use version 2.7.0.8
Click to expand...
Click to collapse
Thanks zelendel, I ended up trying with 2.7.1.1 and it worked.
Related
Anybody figure out how to fix this? I can find people having this problem flashing 4.4 but I can't flash anything. I've tried to flash mf1 firmware, a 4.3 carbon nightly, and a 4.3 pac nightly. All with the same results. Here is exactly what I did -
I flashed PhilZ recovery earlier on a earlier version of TWRP.
kept getting a "failed" in PhilZ
Flashed latest TWRP via Odin
Tried flashing the above mentioned zips all with the error message.
Restored my hyper drive rls16 backup (4.1.2)
Installed latest TWRP via goomanager app
Edit : my phone is flashed to PagePlus so I kinda have to be careful I'm afraid of using Odin to go back to stock/rooted but my luck that's what it'll take. When I get home I'm going to try it with a older version of TWRP that's the only other thing I can think to try.
Any suggestions or info is appreciated.
delete
anyone ? please ?
Supposedly the update binary here is generic, you could try replacing the one in the rom zip with it
http://forum.xda-developers.com/showthread.php?t=2492496
Sent from my SCH-I535 using XDA Premium 4 mobile app
I've tried CWM PhilZ and TWRP all latest versions, and still can't get rid of this.
I Cannot install any rom, whatsoever. I did manage to install a MF1 radio zip, but that's it. I can't install 4.3 or even 4.2 ..
I've replaced the update-binary inside the zips, and edited the update-script and removed the stuff used for recognizing the device, still no dice ..
I ended up flashing a full mf1 img via Odin and then used casual to root/unlock/recovery install - and I STILL get the error. Not sure where to go from here. Seems like nobody else is having this problem unless they're not on the latest recovery and trying to flash KitKat.
Thought I'd share the rest of my story ..
edit: I was able to restore a old backup of 1.7 carbon ...lol. better than nothing or a TW rom, that's for sure.
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
dpeeps74 said:
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
cjmcsw87 said:
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
OK, I have one for you to try, use the original rom zip (don't edit the update-script), when you flash in recovery and it failed, select boot and boot back into recovery, then reflash again. Try it with the latest TWRP 2.6.3.2.
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
cjmcsw87 said:
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
Click to expand...
Click to collapse
Nice, glad you have a happy ending!!
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
Me too buddy, let me tell ya ..
I appreciate the advice along the way. Thank you.
now I just have to decide if I want carbon or pac as my daily driver for awhile.. Carbon is what i've almost always used after I figured out how bloated and laggy TW is.. Best of all my PagePlus flash is perfectly fine, didn't have to add APN's or mess with anything else to get data to work.
I hope this thread helps somebody else.
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
umka83 said:
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
Click to expand...
Click to collapse
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
BadUsername said:
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
Click to expand...
Click to collapse
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
It's a recovery version problem, so either update your recovery or use an older one until you find something that works.
Problem Solved
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
After conducting my own research with this same problem I discovered a much simpler method of correcting the issue. When flashing KK roms with older versions of custom recoveries, the recoveries did not have sufficient instructions to to handle some of the file system changes in KK. I tried replacing the updater binaries from multiple ROMs to no avail. After about 24 hours of trial and error I managed to successfully flash Cyanogenmod cm-11-20140709-NIGHTLY-d801 and GAPPs aokp_gapps-kk-20140517 to my LG G2 D801. All that had to be done is to update TWRP from 2.6.3.2 to version 2.7.1. This version of TWRP had the necessary instructions to support a KK version custom ROM.
Good Job
Sent from my SM-G900F using XDA Free mobile app
Fixed
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
I had same issue, installed newest TWRP. Fixed! Used Odin to install.
I had the same issue as the OP. I was trying to flash a rom from the external SD card. I moved it to the Internal SD and it worked.
J
Hi all, I tried to install this rom without success several times:
"http://download.mokeedev.com/?device=saga&type=unofficial" (I found it her "http://forum.xda-developers.com/htc-desire-s/development/rom-mokee-opensource-project-t2817875")
I downloaded the zip several times and the result is always the same:
"set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard
Error flashing zip 'sdcard/MK44.4-saga-20140722
Updating, partition details..."
I have Team Win Recovery v2.6.3.0 an HBOOT-2.00.0002
I can install other roms like flinny 4.2.2 however with the alpha 5 failure also occurs
Could anyone help me?
Thanks!
You need to update your recovery to flash 4.4 Roms.
Either twrp 2.7 or latest 4ext touch will work
teadrinker said:
You need to update your recovery to flash 4.4 Roms.
Either twrp 2.7 or latest 4ext touch will work
Click to expand...
Click to collapse
Hi, thanks for your answer.
I updated recovery (TWRP 2.7.1.0 from, "http://forum.xda-developers.com/showthread.php?t=2248688") and I get to finish the installation without errors. But I have a new problem, when I reboot the phone, the screen goes black with small flashes (display go off and on at intervals of 3/4 seconds, but always black).
What may be happening now? Is this still a problem caused by recovery?
Thanks
Are u S-On.. if yes Flash boot.img file which came with the zip file... it may help also check if yrs is a hitachi panel, there a thread in development Section for it...
zeus.lny said:
Are u S-On.. if yes Flash boot.img file which came with the zip file... it may help also check if yrs is a hitachi panel, there a thread in development Section for it...
Click to expand...
Click to collapse
Thanks, you were right, I had s-on and therefore I had to use fastboot to flash boot.img, and now runs the rom on my phone and I tested without problems, only minor bugs that comes standard so I will use 4.2.2 because it gives me the feeling that 4.4.4 is still not stable for desire s
Thanks again!
zeus.lny said:
it may help also check if yrs is a hitachi panel, there a thread in development Section for it...
Click to expand...
Click to collapse
What would happen if I have that panel?. Would it affect the performance of the rom?
It wouldn't even boot
It has been initiated MMDI kernel project in HTC Desire S Rebirth Project thread, since then no progress had been made.
I have the latest nightly and GAPP zips, but it fails to install with the following message:
E: error executing updater binary in zip '/sdcard/download/cm-12-20150314-nightly-XT926.zip
Any ideas on what the problem might be? Current phone info is Droid RAZR MAXX HD XT926 on Android ver 4.1.2 with TWRP recovery ver 2.8.0.0
System ver 9.18.94.xt926.Verizon.en.US
Thanks for your help guys!
Were u probably trying to install The kkbl Version and not jbbl one?
esok44 said:
Were u probably trying to install The kkbl Version and not jbbl one?
Click to expand...
Click to collapse
Ahh...I think you may be correct. Can you link me to the correct jbbl ver and the proper gapps files.
Many thanks...I'm pretty new at this as you can probably tell
kico42 said:
Ahh...I think you may be correct. Can you link me to the correct jbbl ver and the proper gapps files.
Many thanks...I'm pretty new at this as you can probably tell
Click to expand...
Click to collapse
Well I haven't found cm12 for JBBl XT926 but this rom should be Working, it's cm based and for JBBL, also it's unified, so it should run on your device.
GZR Validus
Maybe just give this one a try or search by yourself a cm12 build for JBBL
Greetz Esok
esok44 said:
Well I haven't found cm12 for JBBl XT926 but this rom should be Working, it's cm based and for JBBL, also it's unified, so it should run on your device.
GZR Validus
Maybe just give this one a try or search by yourself a cm12 build for JBBL
Greetz Esok
Click to expand...
Click to collapse
Esok,
Thanks for your help. I did try the suggested ROM but I get the same message---E: error executing updater binary in zip
Also tried a couple of the JBBL CM's and get the same message for them. I'm at a loss as to what the message means as it pertains to installing a different ROM or how to correct the issue.
Any other ideas? Sure would like to try out a different ROM
kico42 said:
Esok,
Thanks for your help. I did try the suggested ROM but I get the same message---E: error executing updater binary in zip
Also tried a couple of the JBBL CM's and get the same message for them. I'm at a loss as to what the message means as it pertains to installing a different ROM or how to correct the issue.
Any other ideas? Sure would like to try out a different ROM
Click to expand...
Click to collapse
Have you thought about using a different Recovery?
Like the most recent TWRP (2.8.5.x) or CWM?
That could be a reason for your problem.
Good Luck dude,
greetz Esok
kico42 said:
Esok,
Thanks for your help. I did try the suggested ROM but I get the same message---E: error executing updater binary in zip
Also tried a couple of the JBBL CM's and get the same message for them. I'm at a loss as to what the message means as it pertains to installing a different ROM or how to correct the issue.
Any other ideas? Sure would like to try out a different ROM
Click to expand...
Click to collapse
I second the suggestion of trying another recovery. That fixed it for me.
failed to install cm 21 lolipop on motorola xt 926
i tried many roms like cm12 2014,15 and 16 but due to entries in updater script it does not start. is there any way to adit values in updater script to match properties of xt926 .or any rom designed for the same mobile.
First of all sorry if there are some solution in other thread but i was searching a lot and found nothing. Also i cannot ask this on the twrp thread because of the xda system that don't allow me to write there or on some other development thread because my account have few than 10 messages (very frustrating this).
I tried to install the twrp 2.8.6.0 and it's impossible to have it working, when i install it always i have a bootloop that don't allow the phone to enter to the recovery.
I tried all the ways to install it (app flashify, app twrp manager, app kernel adiutor, cmd, toolkit, through twrp 2.8.7.0, 2.8.4.0, 2.8.7 multirom) and still without luck. It's very strange because is THAT specific version (2.8.6.0) that don't work, when i flash other version like 2.8.7 works perfectly.
Anyone knows what's the problem?
mustang_ssc said:
First of all sorry if there are some solution in other thread but i was searching a lot and found nothing. Also i cannot ask this on the twrp thread because of the xda system that don't allow me to write there or on some other development thread because my account have few than 10 messages (very frustrating this).
I tried to install the twrp 2.8.6.0 and it's impossible to have it working, when i install it always i have a bootloop that don't allow the phone to enter to the recovery.
I tried all the ways to install it (app flashify, app twrp manager, app kernel adiutor, cmd, toolkit, through twrp 2.8.7.0, 2.8.4.0, 2.8.7 multirom) and still without luck. It's very strange because is THAT specific version (2.8.6.0) that don't work, when i flash other version like 2.8.7 works perfectly.
Anyone knows what's the problem?
Click to expand...
Click to collapse
Install either TWRP 2.8.6.0.6 materialised (personally tested works perfect) or the latest 2.8.7.0.5 materialised other users say it works with flashing firmware and works with encrypted systems
https://www.androidfilehost.com/?w=files&flid=30332
Sent from my A0001 using Tapatalk
Renosh said:
Install either TWRP 2.8.6.0.6 materialised (personally tested works perfect) or the latest 2.8.7.0.5 materialised other users say it works with flashing firmware and works with encrypted systems
https://www.androidfilehost.com/?w=files&flid=30332
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
And do you know if works well with the new Sultan CM13 versions? That's the problem i have, the other TWRP versions cannot flash correctly that rom and also i heard that the TWRP 2.8.6.0.6 don't flash the rom correctly, maybe I'm wrong.
Me and many people have this strange problem that don't allow us to flash the 2.8.6.0. Hope someone can help us.
Thanks anyway.
mustang_ssc said:
And do you know if works well with the new Sultan CM13 versions? That's the problem i have, the other TWRP versions cannot flash correctly that rom and also i heard that the TWRP 2.8.6.0.6 don't flash the rom correctly, maybe I'm wrong.
Me and many people have this strange problem that don't allow us to flash the 2.8.6.0. Hope someone can help us.
Thanks anyway.
Click to expand...
Click to collapse
The problem isn't flashing the ROM correctly its that you don't have the correct firmware so it gives an error and refuses to flash the latest Sultan builds. TWRP 2.8.6.0.6 or 2.8.7.0.5 both in that directory I posted earlier can flash the correct firmware. You'll need to download the latest CM13 flash that wipe again and then flash Sultan to have the latest baseband version
Renosh said:
The problem isn't flashing the ROM correctly its that you don't have the correct firmware so it gives an error and refuses to flash the latest Sultan builds. TWRP 2.8.6.0.6 or 2.8.7.0.5 both in that directory I posted earlier can flash the correct firmware. You'll need to download the latest CM13 flash that wipe again and then flash Sultan to have the latest baseband version
Click to expand...
Click to collapse
I did that you told me and now i have the Sultan cm13 working perfectly.
I didn't know that, thanks.
Just got bored and browsed AFH for files related on our phone, and just saw this link which I think is for our device, since it's named D850... Has anyone tried this as well?
souler456 said:
Just got bored and browsed AFH for files related on our phone, and just saw this link which I think is for our device, since it's named D850... Has anyone tried this as well?
Click to expand...
Click to collapse
You better use TWRP 3.0.2-0. On newer versions aroma causes reboot to recovery, so you can't install any aroma roms with it.
MESA said:
You better use TWRP 3.0.2-0. On newer versions aroma causes reboot to recovery, so you can't install any aroma roms with it.
Click to expand...
Click to collapse
Wow, thanks for the heads-up. Almost flashed this, wanting for an updated TWRP and such. Thank you, sir
what version of twrp that you're running right now ?
root?
souler456 said:
Just got bored and browsed AFH for files related on our phone, and just saw this link which I think is for our device, since it's named D850... Has anyone tried this as well?
Click to expand...
Click to collapse
Hello
I am new with this cell
What method have you done to be root? and have twrp