Hello,
I have a Nexus 5 with root, stock rom, Franco Kernel and the custom recovery is TWRP. I accomplished this by following a guide around this forum, I know very little about Android. The Android version i'm running is the 4.4.2 and the phone keeps asking me to update do the newer version, however, when I try to do it, it takes me to the TWRP menu, and when I try to install it there, I get this error:
"/system/bin/thermal-engine-hh" has unexpected contents
E: Error executing updater binary in zip
Error flashing zip
How can I update the phone to the newer version of android? Can anyone help me? Thanks.
Start here, then still questions in that thread
http://forum.xda-developers.com/showthread.php?p=69234
Sent from my Nexus 5 using XDA Free mobile app
Hello,
Thanks for your reply. I can't access your link though.
D5R said:
Hello,
Thanks for your reply. I can't access your link though.
Click to expand...
Click to collapse
Something is goofed up with xda. It's the ota help in the general forum. Look for it there. Should have everything you need
Sent from my Nexus 5 using XDA Free mobile app
D5R said:
Hello,
Thanks for your reply. I can't access your link though.
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
D5R said:
Hello,
I have a Nexus 5 with root, stock rom, Franco Kernel and the custom recovery is TWRP. I accomplished this by following a guide around this forum, I know very little about Android. The Android version i'm running is the 4.4.2 and the phone keeps asking me to update do the newer version, however, when I try to do it, it takes me to the TWRP menu, and when I try to install it there, I get this error:
"/system/bin/thermal-engine-hh" has unexpected contents
E: Error executing updater binary in zip
Error flashing zip
How can I update the phone to the newer version of android? Can anyone help me? Thanks.
Click to expand...
Click to collapse
First thing, turn off mobile data. Your phone may try re-download it over and over again and use up your mobile data plan.
To install the ota via the ota update on the stock rom you will need to return to stock recovery and maybe stock kernel (not sure about this one).
NOTE: Before trying the below steps as I haven't tested them myself, please backup your ROM first. Better safe than sorry.
You can try installing the OTA updates manually from TWRP. You can find the links in the post - http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327.
If you are running 4.4.2 KRT16M you will need to download three updates.
1. KTU84M from KOT49H (4.4.2 update to 4.4.3)
2.KTU84P from KTU84M (4.4.3 update to 4.4.4)
Download them together and also put on a flashable zip of TWRP in the same location as it looks like it will reinstall the stock recovery.
You can even put on one of Franco kernel just in case too.
In TWRP select install zip and install number 1 first, then install 2. and finally install TWRP again. You should be updated to 4.4.4.
You can then install Franco kernel again just in case.
I hope this makes it easier.
EDIT: follow the link in the previous post as it has different scenarios and the steps needed.
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes and/or kernel, reboot into recovery, flash the OTA , boot to bootloader, connect to pc, fastboot flash recovery, reboot into recovery, flash supersu.
Rooted stock = reboot into recovery, flash the ROM.
No brainer really. Flashing an OTA if rooted is a fool's errand.
Sent from my Nexus 5 using Tapatalk
Related
I manually sideloaded 4.4.2 onto my nexus 5 all was good and root appeared to be working as nova,lightflow,adblock all asked for permission upon reauthentication. However when i went into supersu it prompted for a updated. Which I continued as normal but it fails. Even after reboot.
I've even tried using cf-autoroot again to no luck.
Whats the best solution for me.
Nexus 5 - 4.4.2 KOT49H from 4.4 KRT16M
Root : Supersu by chainfire using cf-autoroot.
Nova launcher seems to be able to use root as does lightflow and root explorer.
Adblock asks but cannot change the files it needs.
Any extra information needed I will gladly produce
Try flashing su zip? - https://mega.co.nz/#!xk92nAZI!t2-Mhj_BbBMlYVj6OLC6xT2ycAMixnETqnUdqFXkr9w
Sent from my Nexus 5 using Tapatalk
Ben36 said:
Try flashing su zip?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have a custom recovery and sideloading this fails.
brichardson1991 said:
I don't have a custom recovery and sideloading this fails.
Click to expand...
Click to collapse
use fastboot to flash a custom recovery?
basic stuff man.
Zepius said:
use fastboot to flash a custom recovery?
basic stuff man.
Click to expand...
Click to collapse
I thought not having a custom recovery was the way to ensure OTA updates?
But if I'm not going to be getting OTA then I'll go for it.
Whats the best one for Nexus 5, as i used to use Clockworkmod on Galaxy S2 but i've read TWRP is better ?
brichardson1991 said:
I thought not having a custom recovery was the way to ensure OTA updates?
But if I'm not going to be getting OTA then I'll go for it.
Whats the best one for Nexus 5, as i used to use Clockworkmod on Galaxy S2 but i've read TWRP is better ?
Click to expand...
Click to collapse
custom recoveries in themselves do not stop a OTA. what stops a OTA is the fact that people do system mods and that breaks the OTA.
as for which is best, that falls under best rom/kernel type stuff. pick one.
brichardson1991 said:
I thought not having a custom recovery was the way to ensure OTA updates?
But if I'm not going to be getting OTA then I'll go for it.
Whats the best one for Nexus 5, as i used to use Clockworkmod on Galaxy S2 but i've read TWRP is better ?
Click to expand...
Click to collapse
OTA only check the system partiiton, custom recovery won't spoil OTA.
and stock recovery = no recovery
I prefer TWRP.
If you currently have root access, download teh TWRP app from the Play Store and it'll install itself
brichardson1991 said:
I thought not having a custom recovery was the way to ensure OTA updates?
But if I'm not going to be getting OTA then I'll go for it.
Whats the best one for Nexus 5, as i used to use Clockworkmod on Galaxy S2 but i've read TWRP is better ?
Click to expand...
Click to collapse
You can't have ANY modification. Recovery, Kernel, Binaries(Xposed), factory apps all have to be in tact for the official OTA to work. You'll need to find to flashable version, or flash clean back to absolute stock.
Decimation said:
You can't have ANY modification. Recovery, Kernel, Binaries(Xposed), factory apps all have to be in tact for the official OTA to work. You'll need to find to flashable version, or flash clean back to absolute stock.
Click to expand...
Click to collapse
So I flashed TWRP using the app.
and now supersu is up to date.
So in future all OTA updates won't work and i will just have to sideload them like i did with these 2 ?
If that's the case I'm fine with that.
For future OTA you can flash the OTA after the download is provided here, then flash SuperSU immediately after. Also just double check if SuperSU is updated so you have the most recent version.
Thats what I did for the 4.4.1 and 4.4.2 OTAs and I never lost root. All done via TWRP
Thanks all. I've sorted it out. Can close this topic now.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hi everyone,
Las week the OTA update appeared in my phone. I tried to use the google-automatic procedure, but as I have my Nexus 5 rooted, the install was aborted as soon as the device was restarted.
I read the helpdesk thread, trying to update the device manually, but I can't be able to.
I have the 4.4 to 4.4.2 .zip file inside the downloads folder, I restart the device to recovery mode (I've installed TWRP), and after writing the decrypt password and mount the volume, When I try to apply the zip file
"/system/app/EmailGoogle.apk" has unexpected co
E: Error executing update binary in zip '/sdcar
Error flashing zip '/sdcard/Download/b3d1f30762
Updating partition details..
Note that the senteces is cut due to the lenght of the screen.
Before flashing, I go to mount option, and mount all the folder (system, firmware, sdcard)
Any ideas?
Now I'm thinking that when I rooted the device, I used ES File Explorer to delete some apps directly from /sys/apps, maybe is that the error, that some GApps has been removed from the device.
Thank you!
Yes Google has nicely written in app checks. If these apps are not present on check the update is aborted
Sent from my Nexus 5 using Tapatalk
So I have to reinstall the GApps package, and try to apply de update?
http://forum.xda-developers.com/showthread.php?p=26914
Sent from my Nexus 5 using Tapatalk
you modified the system apps.. what did you think was going to happen? everything would update fine?
this has been documented all over the forums. if you want the OTA, stop modifying your system or keep backups of what you modified.
Ben36 said:
http://forum.xda-developers.com/showthread.php?p=26914
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Link not valid, but thank you, I will install GApps
Zepius said:
you modified the system apps.. what did you think was going to happen? everything would update fine?
this has been documented all over the forums. if you want the OTA, stop modifying your system or keep backups of what you modified.
Click to expand...
Click to collapse
That's true, sorry... Well I gonna reinstall GApps and try to update OTA.
Thank you for fast reply!
Deiwor said:
Link not valid, but thank you, I will install GApps
That's true, sorry... Well I gonna reinstall GApps and try to update OTA.
Thank you for fast reply!
Click to expand...
Click to collapse
Flashing gapps is not going to help you. You need to fastboot flash the system and boot image from the factory image
jd1639 said:
Flashing gapps is not going to help you. You need to fastboot flash the system and boot image from the factory image
Click to expand...
Click to collapse
Oh, really? Damn.... Well then I will start from scratch next weekend, or find the way to hide the update.
Thank you jd1639
Deiwor said:
Oh, really? Damn.... Well then I will start from scratch next weekend, or find the way to hide the update.
Thank you jd1639
Click to expand...
Click to collapse
Flashing the system and boot images isn't starting from scratch... you can keep your userdata as long as you aren't using a custom ROM. Flashing those just gives you back a clean stock OS without any of your mods. No need to start from scratch. Should only take a couple minutes.
Also, your mods are the reason it failed in the first place, not because you were rooted. Rooting itself does not prevent OTA updates.
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
I have a rooted Nexus 5 on KTU84p and I'm following the steps outline in this thread to try to update to 5.0
I fall under Scenario 3, and went ahead an uninstalled Xposed. I then downloaded the OTA zip and tried to update it in TWRP. I've now tried multiple versions (currently v2.8.2.0, tried v2.8.1.0 and a v2.6..), however, all have failed with the following error:
TWRP:
E: Error executing updater binary in zip '/sdcard/ROMs/c1a33561be84a8a6a7d5a4c8e3463c4db9352ce6.signed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip'
I'm stuck and unsure what to do next - suggestions?
Nt sure bt ota is meant to be flashed in stock recovery not twrp
doctor_droid said:
Nt sure bt ota is meant to be flashed in stock recovery not twrp
Click to expand...
Click to collapse
The OTA thread has steps on how to flash via custom recovery, which is what I was following, so I'm assuming (hoping) that I don't need to go back to stock recovery...
shikhan said:
I have a rooted Nexus 5 on KTU84p and I'm following the steps outline in this thread to try to update to 5.0
I fall under Scenario 3, and went ahead an uninstalled Xposed. I then downloaded the OTA zip and tried to update it in TWRP. I've now tried multiple versions (currently v2.8.2.0, tried v2.8.1.0 and a v2.6..), however, all have failed with the following error:
TWRP:
E: Error executing updater binary in zip '/sdcard/ROMs/c1a33561be84a8a6a7d5a4c8e3463c4db9352ce6.signed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip'
I'm stuck and unsure what to do next - suggestions?
Click to expand...
Click to collapse
You have to have the stock recovery, kernel and system. You can flash those in fastboot using the 4.4.4 factory image. Then either take the ota from your device or sideload it in the stock recovery using adb.
Sent from my Nexus 9 using XDA Free mobile app
shikhan said:
The OTA thread has steps on how to flash via custom recovery, which is what I was following, so I'm assuming (hoping) that I don't need to go back to stock recovery...
Click to expand...
Click to collapse
Custom recoveries cant flash ota ....afaik
Thanks guys - I'll revert to the stock recovery then.
Can someone confirm that all I need to do is to do run the following adb cmd (using the stock recovery from here):
fastboot flash recovery "jjd-stock ktu84p-recovery.zip"
Or download wugfresh n5 toolkit
Sent from my Nexus 5 using XDA Free mobile app
shikhan said:
Thanks guys - I'll revert to the stock recovery then.
Can someone confirm that all I need to do is to do run the following adb cmd (using the stock recovery from here):
fastboot flash recovery "jjd-stock ktu84p-recovery.zip"
Click to expand...
Click to collapse
I believe that file is meant to be flashed via recovery, not fastboot. If you want to be 100% certain, just grab the factory image from HERE,
unzip it and flash the recovery.img with this command-
Code:
fastboot flash recovery recovery.img
You should be good to go after that.
rickballs said:
Or download wugfresh n5 toolkit
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No. Do not use or recommend toolkits.
Twrp was able to flash OTAs. If that's not the case anymore, then it's more than likely that a update to work with L is needed.
Pretty sure has something to do with the security that was implemented in android 5.0 that prevents this from custom recovery.
Every time there is an OTA update I have this problem.
My Nexus 5 is unlocked and rooted. Every time there is an OTA I get the Android laying down red error message.
Ok fine, I'll manually update with Sideload.
Then I get this error:
"/system/bin/install-recovery.sh" has unexpected contents.
E: Error in /sideload/package.zip
(Status 7)
The last time this happened I had to fully unroot and wipe my phone.
My question is this: Do I have to fully unroot and wipe my phone every single time there is an update? If so, what's the point? Is there a workaround for this that doesn't include wiping my phone every few months when there is an incremental update?
you cannot apply an OTA to a phone that is rooted, you *must* unroot and also undo *every* modification.
save yourself the trouble and just download the factory image and manually flash the new bootloader, radio, system images then you will be up to date. After that just re-root
Lots of tutorials all over the internet for this
Is that flashing via computer?
orthonovum said:
you cannot apply an OTA to a phone that is rooted, you *must* unroot and also undo *every* modification.
save yourself the trouble and just download the factory image and manually flash the new bootloader, radio, system images then you will be up to date. After that just re-root
Lots of tutorials all over the internet for this
Click to expand...
Click to collapse
Ok, then if I don't want to wipe my phone every couple of months I should just not root it, is that safe to assume?
orthonovum said:
you cannot apply an OTA to a phone that is rooted, you *must* unroot and also undo *every* modification.
save yourself the trouble and just download the factory image and manually flash the new bootloader, radio, system images then you will be up to date. After that just re-root
Lots of tutorials all over the internet for this
Click to expand...
Click to collapse
I apologize as I think I misunderstood you.
You're saying that I can download the official OTA, extract the bootloader, radio, and system images using the Nexus Toolbox?
At that point I'll be good to go with the OTA?
Skullpuck said:
You're saying that I can download the official OTA, extract the bootloader, radio, and system images using the Nexus Toolbox?
At that point I'll be good to go with the OTA?
Click to expand...
Click to collapse
No. You download the official 5.0 factory image. Then you extract those files to a computer. And you flash them to your phone using fastboot.
Then after booting up you will be good to go with the OTA.
I just wanted everyone to know that I have fixed the problem with orthonovum's advice.
In case anyone needs step by step advice, check the comment section of this site for Tom's comment on December 19, 2014 at 22:08: http://aaronhastings.me/updating-to-android-5-0-1-on-rooted-nexus-5/
Basically, download the full stock image for 5.0.1, extract it, then just flash the radio, boot, and system images using the NRT.
radio-hammerhead-m8974a-2.0.50.2.22.img
boot.img
system.img
Or just follow the many guides here and use fastboot.
Sent from my Nexus 5 using XDA Premium App
iirc.. This happened because supersu uses/modifies that install-recovery script to exploit stuff.
a maguro wrote this.