Database Info

unrevoked 2 is out with rooted (and full radio) EVO 4G 1.47.651.1-1.32.651.6 OTA

looks like the unrevoked team has done it, got the rom OTA update WITH the new radio and baseband version reading 1.47.651.1..i think the other root methods got the rom, kernel etc but not the full radio..
http://unrevoked.com/rootwiki/doku.php/public/evo_ota_2_patch#evo_4g_1476511-1326516_ota_fix
from their twitter
unrevoked
1. Patched #evo4g OTA ready: http://unrevoked.com/rootwiki/doku.php/public/evo_ota_2_patch . For those of you who updated already, stay tuned.

its not a quick root like teh first.
thats what I want

Yup looks like an actual root method that u can flash roms through and uses the ClockworkMod recovery menu...so although its a few extra steps... its worth it.

Yeah...Don't think I'm going to stick with unrevoked. While I'm very into the homebrew community, I can't see myself rooting until 2.2 is leaked or released from HTC/Sprint. I'll wait for a few days, but I need that boosted 4G radio since 4G just started here yesterday and I get a poor signal.

*Increases bitrate for MPEG4 videos recorded from 6MBit to 8MBit.
Interesting

Is their file corrupt or something cause everytime I go to do the update in recovery it fails.

just did the unrevoked 2 method, worked great, easy to do!

When I try to install the update from unrevoked2 I get a status 7 error and the installation aborts. Anyone have any clue as to why this is?

mysterioustko said:
When I try to install the update from unrevoked2 I get a status 7 error and the installation aborts. Anyone have any clue as to why this is?
Click to expand...
Click to collapse
I am having the same issue.
I have have a custom recovery courtesy of unrevoked2. I'm running Joeykrim's 1.0.8 odexed ROM, and Joeykrim's kitchen to remove some Sprint bloatware.

After fully rooting and installing Stock (1.32.651.6) with root odex v1.0.8 (06/25/2010) by joeykrim,
(the Shipped (1.32.651.6) with root (06/08/2010) by flipzmode failed to install for some reason),
then trying to update from Amon_RA recovery,
get the following message -
Verifying current system...
assert failed: apply_patch_check(/system/bin/reboot -blah blah blah)
E:Error in /sdcard/update.zip
(status 7)
Installation aborted
Click to expand...
Click to collapse

Seems like the download is currently bad. I'm getting the same error from clockwork recovery, and it appears to be a package verification.

That's the same problem I'm running into as well. Anyone have any insight how to fix this?
Sent from my PC36100 using XDA App

acrh2 said:
After fully rooting and installing Stock (1.32.651.6) with root odex v1.0.8 (06/25/2010) by joeykrim,
(the Shipped (1.32.651.6) with root (06/08/2010) by flipzmode failed to install for some reason),
then trying to update from Amon_RA recovery,
get the following message -
Click to expand...
Click to collapse
Same as the rest of us. There must be something wrong with the zip they posted.

acrh2 said:
After fully rooting and installing Stock (1.32.651.6) with root odex v1.0.8 (06/25/2010) by joeykrim,
(the Shipped (1.32.651.6) with root (06/08/2010) by flipzmode failed to install for some reason),
then trying to update from Amon_RA recovery,
get the following message -
Verifying current system...
assert failed: apply_patch_check(/system/bin/reboot -blah blah blah)
E:Error in /sdcard/update.zip
(status 7)
Installation aborted
Click to expand...
Click to collapse
i havent had a chance to thoroughly research this. this is the first thread ive read about unrevoked stuff, but we used a modified version of /system/bin/reboot because the stock version wouldnt allow the "reboot recovery" command.
i appreciate your support by using my ROM and according to the error posted above, put this version of reboot into your system/bin folder and rename to reboot.
after you've replaced the reboot binary in /system/bin with the linked one below, attempt the update again.
let me know if there are any other issues!
http://www.joeyconway.me/evo/stock/reboot-ruu6
basic adb command:
adb push c:\downloads\reboot-ruu6 /system/bin/reboot

joeykrim said:
i havent had a chance to thoroughly research this. this is the first thread ive read about unrevoked stuff, but we used a modified version of /system/bin/reboot because the stock version wouldnt allow the reboot recovery command.
i appreciate your support by using my ROM and according to the error posted above, put this version of reboot into your system/bin folder and rename to reboot.
after you've replaced the reboot binary in /system/app with the linked one below, attempt the update again.
let me know if there are any other issues!
http://www.joeyconway.me/evo/stock/reboot-ruu6
basic adb command:
adb push c:\downloads\reboot-ruu6 /system/bin/reboot
Click to expand...
Click to collapse
This worked for me! Thanks so much!

personally im going to hold off on applying their method because of a big red flag they note at the very bottom of their page:
Radio update (as of yet undissected).
*
Behavior unexpected; anticipated upgrade to baseband 2.05.00.06.10, but on one EVO resulted in 1.39.00.05.31, and on another resulted in 1.39.00.04.26.
Click to expand...
Click to collapse
the radio is not something to lightly mess around with and since they can't seem to accurately update it to show the correct version number, something is not being done properly.
in addition to sprint pulling the OTA due to a bug where if the radio is updated twice too quickly the phone won't turn on again, make me very hesitant to update the radio. these are only my opinions, but i will wait.
for those who are a bit more adventurous than me and have done this update, what version does your radio show?

Hmm, well the update installed after pushing joeykrim's file, but I'm not sure if everything went through because I am still showing the same baseband...

I did not do the update from HTC yesterday because I wanted to keep unrevoked and WiFi Tether working.
what I'd like to know is if I install THIS new unrevoked patched with the OTA from yesterday, if this will wipe my phone? is this like flashing a rom where your phone gets wiped completely or more like the first unrevoked where everything stayed the same on the EVO?

markdt098 said:
Hmm, well the update installed after pushing joeykrim's file, but I'm not sure if everything went through because I am still showing the same baseband...
Click to expand...
Click to collapse
as i quoted above in my previous post, unrevoked says the radio baseband version doesn't update. on two phones they tried, one shows the original baseband the other shows the last OTA baseband...
to me, this is a red flag and i will wait.
another method for you to check if this update was applied successfully is to check your build version, it should read, "1.47.651.1 CL195459 unrevoked"
PLESTIUC said:
I did not do the update from HTC yesterday because I wanted to keep unrevoked and WiFi Tether working.
what I'd like to know is if I install THIS new unrevoked patched with the OTA from yesterday, if this will wipe my phone? is this like flashing a rom where your phone gets wiped completely or more like the first unrevoked where everything stayed the same on the EVO?
Click to expand...
Click to collapse
short answer, no this will not wipe your phone.
longer more technical answer:looking through the updater-script file in their .zip file, only files in /system are patched, wimax radio updated, kernel updated and radio updated. nothing in /data so no settings or 3rd party apps are touched.

joeykrim said:
as i quoted above in my previous post, unrevoked says the radio baseband version doesn't update. on two phones they tried, one shows the original baseband the other shows the last OTA baseband...
to me, this is a red flag and i will wait.
another method for you to check if this update was applied successfully is to check your build version, it should read, "1.47.651.1 CL195459 unrevoked"
short answer, no this will not wipe your phone.
longer more technical answer:looking through the updater-script file in their .zip file, only files in /system are patched, wimax radio updated, kernel updated and radio updated. nothing in /data so no settings or 3rd party apps are touched.
Click to expand...
Click to collapse
thanks. so don't bother with this yet? corrupted?

*Root-safe* stock OTA 1.47.651.1 *incremental* update w/ radio+WiMAX

IMPORTANT: The process described in this post breaks WiMAX, so I have removed the download links, and I recommend that no one attempt it. Please see this thread for a way to get from the original stock everything all the way up to the latest rooted OTA with the latest radio+WiMAX firmwares without even needing adb.
~~~ remainder of this post retained for historical interest only ~~~
Background: I didn't want to flash a full /system partition to upgrade my EVO 4G from Flipz's rooted stock 1.32.651.6 ROM to the latest 1.47.651.1, and I feel better using a barely modified "official" update from Sprint/HTC, so here's what I did:
Allowed the phone to download the update from Sprint/HTC. (It downloads into /cache.)
Copied the update to my computer and unzipped it.
Edited the META_INF/com/google/android/updater-script. (See below for a diff.)
Removed the recovery.img from the firmware.zip. (I don't want to go back to a stock recovery.)
Deleted the patch files for Sprint_Qik.apk and Sprint_TV.apk, since I've deleted those apps from my phone.
Edited the /system/build.prop file on the phone to remove the line that Flipz added at the bottom, thus restoring it to its stock condition (sha1=ee40d5143cf1089af2575045a9db9061f0d0dca9).
Zipped the update back up and signed it.
Download the update here:
OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe.zip
(md5=913c7594ca8ca94594a2c8e1ec9b5564)
Download the original build.prop file here:
build.prop-1.32.651.6
(md5=a29ab0ec25ad976bd12bc8bad5a97063)
Alternate: If you kept Sprint TV and Sprint Qik, use this update zip instead:
OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(md5=410f57feeaebcf89c5497cd6e599a807)
Before you begin: You MUST be using a rooted stock 1.32.651.6 ROM, such as this one released by Flipz. Because this update is an incremental update, it cannot apply to any other ROM, even custom ROMs having the same base system version.
How to install this update:
Caution: There has been a report that updating using this method breaks the WiMAX. If that's true, it can only be because HTC must have added some new function to their recovery program that the custom recoveries don't have. It is recommended that you run a Nandroid backup in case you need to revert.
Download the two files linked above.
adb push OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe.zip /sdcard/ (Or copy the update zip to your SD card by some other means.)
adb remount
adb push build.prop-1.32.651.6 /system/build.prop (See below for what to do if this step fails.)
adb reboot recovery
Run a Nandroid backup just in case.
Flash from the update zip and reboot.
The radio+WiMAX updates will install. This takes a while. Don't touch it. When it's finished, it will reboot on its own.
You'll find yourself in recovery one last time. Reboot.
It'll sit on the "4G" splash for a long time. Don't panic.
Once the home screen appears, go to Settings, About Phone, and verify that your "Software number" is 1.47.651.1 and your "Baseband version" is 2.05.00.06.10.
You may need to remove and re-add some home screen widgets.
If you're still using su and Superuser.apk from Flipz's stock rooted ROM, you will need to install the su-2.1-e-unsecure-signed.zip from this thread. It's a much, much newer version than the one Flipz included. It's an update zip, so install it via recovery.
Enjoy!
What to do if pushing build.prop fails:
This probably means you haven't unlocked NAND by flashing the engineering SPL. That's okay. Your custom recovery program probably supports adb while in recovery mode. If so, you can simply reboot the phone into recovery, perform step #4 from above, skip step #5, and continue from step #6.
For the curious, here's the diff of the updater-script from the stock update to mine: updater-script-1.47.651.1.diff
Troubleshooting
If you're getting an error that says assert failed: apply_patch_check, it means something about your system is different from a totally stock 1.32.651.6 system. Most likely you're running a custom ROM, not a rooted stock ROM, you've already applied the update, or you've installed some kind of hack like QuickBoot. Because this update is an incremental update, it can only be applied to a rooted (but otherwise unaltered) stock 1.32.651.6 ROM. Try flashing Flipz's stock rooted 1.32.651.6 ROM and then proceeding with the steps above under "How to install this update."
If Wireless Tether gets stuck when starting tethering, it probably means you still have the old and crusty su and Superuser.apk. Install the su-2.1-e-unsecure-signed.zip update mentioned above to get the latest set of superuser tools. Then Wi-Fi Tether should work fine.

Thank you. Will see if this fixes my broken 4G.

wsantiagow said:
Links Please?
Click to expand...
Click to collapse
The forum wouldn't let me post links. Apparently it's an anti-spam policy. As soon as a moderator is nice enough to bless my account, I'll turn those URLs into links.

please add back in Qik and TV... let users delete that after? many people use those programs.
either way, nice work

Does this include all of the contents of the original update, including the change to the Bit Rate of the Camera?

blehzz said:
please add back in Qik and TV... let users delete that after? many people use those programs.
either way, nice work
Click to expand...
Click to collapse
Get the rootsafe-Sprint.zip instead. The only differences between it and the stock update are that it doesn't include the recovery image and it preserves setuid+setgid root for /system/xbin/su.

wsantiagow said:
Thank you. Will see if this fixes my broken 4G.
Click to expand...
Click to collapse
I'm assuming broken as in you ran the unrevoked update?
Any luck?
Also, OP:
Does 4G work for you after this? I remember reading in some other threads that 4G wasn't working for images flashed without the default recovery. Not sure if I'm taking it out of context or if this is an issue.

wphend00 said:
Does this include all of the contents of the original update, including the change to the Bit Rate of the Camera?
Click to expand...
Click to collapse
It's exactly the update package furnished from Sprint over-the-air (the 30.2 MiB one), but with one line added to the updater script so that the update doesn't kill the setuid permissions on /system/xbin/su.
That means it changes everything Sprint changed in the latest update, including kernel, radio, WiMAX, and anything else.

So can I use this over a rooted Fresh .53 without breaking the root? Is this what you are running?

whitslack said:
The forum wouldn't let me post links. Apparently it's an anti-spam policy. As soon as a moderator is nice enough to bless my account, I'll turn those URLs into links.
Click to expand...
Click to collapse
..........

ViViDboarder said:
Also, OP:
Does 4G work for you after this? I remember reading in some other threads that 4G wasn't working for images flashed without the default recovery. Not sure if I'm taking it out of context or if this is an issue.
Click to expand...
Click to collapse
There's no 4G coverage in my area, so I can't know whether it works for sure. I can turn on 4G, though, and it says "Scanning." Also, the ip link command shows the wimax0 network interface is present, so I would assume that means the kernel module loaded successfully.
FWIW, I flashed the update using toast's recovery (md5=0ba574fe3a8d82e4e796cc306efa63a7). It definitely goes through the extra reboot cycle for flashing the firmwares. I see no reason why it wouldn't flash the WiMAX firmware, given that it's essentially the stock update process.
bjrmd said:
So can I use this over a rooted Fresh .53 without breaking the root? Is this what you are running?
Click to expand...
Click to collapse
I can't guarantee the patches will apply cleanly against anything other than the stock 1.32.651.6. It won't hurt to try it. The updater script has checks to be sure everything will apply cleanly before it touches anything, so the worst that can happen to you is that it will politely refuse to apply.

whitslack said:
I can't guarantee the patches will apply cleanly against anything other than the stock 1.32.651.6. It won't hurt to try it. The updater script has checks to be sure everything will apply cleanly before it touches anything, so the worst that can happen to you is that it will politely refuse to apply.
Click to expand...
Click to collapse
Only a stock 1.32.651.6? What if I'm running a stock ROOTED 1.32.651.6?
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Thanks, btw!

whitslack said:
There's no 4G coverage in my area, so I can't know whether it works for sure. I can turn on 4G, though, and it says "Scanning." Also, the ip link command shows the wimax0 network interface is present, so I would assume that means the kernel module loaded successfully.
FWIW, I flashed the update using toast's recovery (md5=0ba574fe3a8d82e4e796cc306efa63a7). It definitely goes through the extra reboot cycle for flashing the firmwares. I see no reason why it wouldn't flash the WiMAX firmware, given that it's essentially the stock update process.
Click to expand...
Click to collapse
Right... Well, here it scans and then turns off wimax and then turns it back on and keeps doing that. Working with joshua_ last night I got it to keep scanning... It never did get an IP though but the interface was definitely present. I could see it with netcfg from the adb shell.
I pointed joshua_ to this thread to see what he things of these patches. I had been trying to help him use my phone to debug this issue so I don't want to mess things up too much for him.

I get an install aborted when trying to run the update zip. Starts the install then just stops and give an install aborted.
BTW I am now using a Fresh and not DC on my phone. And I am fully rooted(NAND unlocked) and have been able to run several other updates.zip without issue, currently using Clockwork MOD for recovery and not RA

rugedraw said:
Only a stock 1.32.651.6? What if I'm running a stock ROOTED 1.32.651.6?
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Thanks, btw!
Click to expand...
Click to collapse
It will probably fail if you don't have a file at /system/xbin/su, which only rooted ROMs have. If you're running totally stock, you should just use the automatic OTA update from Sprint. If you're running rooted stock, you should use this. (I was using Flipz's rooted stock initially, so that's what I tested against.)

Badious said:
I get an install aborted when trying to run the update zip. Starts the install then just stops and give an install aborted.
Click to expand...
Click to collapse
What recovery are you using? Amon RA 1.7.0.1 wouldn't work for me. It kept complaining about no signatures, even though I had signed the update. I used toast's recovery successfully.
If that's not the problem, then it can only be that some file on your phone is not identical to the version from the stock 1.32.651.6. Did you replace the /system/build.prop file with the stock one linked in the OP? In particular, this update will not apply against Flipz's stock rooted ROM unless you replace that file with the really stock one.

Yep downloaded the buildprop in the OP and copied that over via ADB successfully(checked softwar version and it shows stock buildprop info)
Let me try it one more time and see exactly what it is bawking about.
Ok. Error Reads as Such:
Verifying Current System....assert failed: apply_patch_check ("system/app/AccountandSyncSettings.apk" . TWO LONG SETS OF HEX NUMBERS[if you need them I can provide them])
E: Error in /sdcard/OTA..(name of full file)
(status 7)
Installation Aborted.

ERROR:
Verifying current system...
assert failed: apply_patch_check ("/system/app/AccountAndSyncSettings.apE:unknown command [k",]
E:unknown command [56479c22c")]
E:Error in /sdcard/OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(Status 7)
Installation aborted.
Can someone assist please, would like to get this new Radio OTA flashed....
Edit: Running DC 3.2.1 with Aloyisus Theme

whitslack said:
It will probably fail if you don't have a file at /system/xbin/su, which only rooted ROMs have. If you're running totally stock, you should just use the automatic OTA update from Sprint. If you're running rooted stock, you should use this. (I was using Flipz's rooted stock initially, so that's what I tested against.)
Click to expand...
Click to collapse
Thanks for the quick response! I am running a rooted version of 1.32.651.6 and I've been waiting for something like this. So I should be OK using clockwork recovery to run this?

rugedraw said:
Also, can I just drop it in my SD card and flash it from there using Clockwork Recovery, or does it have to go through via the commands?
Click to expand...
Click to collapse
You can put it on your SD card by any means available to you. The only requirement is that your recovery program does not care that it's signed by someone other than HTC.
TheMike1 said:
ERROR:
Verifying current system...
assert failed: apply_patch_check ("/system/app/AccountAndSyncSettings.apE:unknown command [k",]
E:unknown command [56479c22c")]
E:Error in /sdcard/OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe-Sprint.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
That can only mean that you're not using the stock ROM (w/ root added). This is an incremental update straight from the official sources with one slight tweak to preserve root access, so you must be using a stock system in order for it to apply.
Users of custom ROMs should be flashing new versions of those custom ROMs. The incremental upgrade path here will not work on custom ROMs.

E:Error executing updater binary in zip

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

Updating Nexus 5

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

[RIL] Data Fixes for the 6.0.1 bootloader [Nougat][Marshmallow]

Praise God! The TBLTETMO data fix finally works!
What is this for?
-These data fix zips allow you to use a TBLTEXX rom on your phone (provided that you can flash it, see "flashing tbltexx roms" for details on that). If you edit a TBLTEXX rom and flash it to your phone, you will not be able to use the cellular, but now you can with these data fix zips!
THIS IS FOR THE 6.0.1 BOOTLOADER ONLY! THIS ONLY WORKS ON ROMS BUILT FOR THE TBLTEXX ON THE 6.0.1 BOOTLOADER! PLEASE USE WITH CAUTION!
Flashing TBLTEXX roms:
You have two choices, either flash a TBLTEXX recovery, so you can flash TBLTEXX roms, or you can use a TBLTETMO recovery and follow the steps below.
Steps
1. Download the TBLTEXX rom that was built using the 6.0.1 bootloader.
2. Unzip the rom.
3. Open ./META-INF/com/google/android/updater-script in gedit or notepad++.
4. Delete the first line - should say something like
Code:
assert(getprop("ro.product.device") == "tblte" || getprop("ro.build.product") == "tblte" || getprop("ro.product.device") == "tbltexx" || getprop("ro.build.product") == "tbltexx" || getprop("ro.product.device") == "tbltedt" || getprop("ro.build.product") == "tbltedt" || abort("E3004: This package is for device: tblte,tbltexx,tbltedt; this device is " + getprop("ro.product.device") + "."););
5. Save the file.
6. zip the contents back up.
7. Flash!
Post #1: Introduction and editing TBLTEXX roms.
Post #2: Thanks and a list of known working TBLTEXX roms, with links!
Post #3: The data zips.

Thanks!
@Mickey387 - For continued development for the TBLTEXX!
@louforgiveno - For making the 5.1.1 bootloader data zips for the trlte, which inspired this set of datazips. (Same principle, different files.)
Known working TBLTEXX roms:
[ROM][7.1.1] AOKP Nougat with built in sidebar launcher! [tbltexx]
This rom is available in the T-Mobile thread also for direct use on the T-Mobile phones!
https://forum.xda-developers.com/no...m-aokp-nougat-built-sidebar-launcher-t3558296
Instructions: After downloading this, you do not need to edit the zip, it is ready for flashing, flash rom, gapps. Reboot, let it settle, then, go back into recovery and flash datazip #1. Reboot. Now you will see your cell phone signal as empty, select your apn, and set your phone to 3g mode. Then, after you get the H+ by your cell signal, you can switch back to LTE.
[ROM][OFFICIAL]NOUGAT Resurrection remix 5.8.0 (7.1.1)
https://forum.xda-developers.com/no...-nougat-resurrection-remix-5-8-0-7-1-t3509295
Instructions: After making it flashable, flash rom, gapps. Reboot, let it settle, then, go back into recovery and flash datazip #1. Reboot. Now you will see your cell phone signal as empty, select your apn, and set your phone to 3g mode. Then, after you get the H+ by your cell signal, you can switch back to LTE.
[rom][6.0.1] aokp mm [n915t/n915f/n915fy/n915g]
https://forum.xda-developers.com/note-edge/development/rom-aokp-mm-t3484354
Instructions: After downloading the 6.0.1 bootloader version, you do not need to edit the zip, it is ready for flashing. Flash the rom, the gapps, and reboot. After it boots up the first time, go back to recovery and flash data zip #1. You should be good to go! If you have trouble, choose your apn, cycle between 3g and lte!
@finnigen2 found that this also works with Resurrection remix 5.8.1 (7.1.1) with the data fix with Mickey's TWRP 3.0.3.1_915F, see post #11 for details!
@unimatrix725 found that this also works with TekX EPE2 [6.0.1] on a SM-N915R4 (U.S. Cellular), see post #13 for details!
@JeremySS found that if you upgrade from TBLTEXX RR 5.8.0 to 5.8.1, you can flash data zip 2 to fix your issues, see post #15 for details!

Post #3. The data zips.
Data Zip #1:
http://www.mediafire.com/file/12bi5tf16dx2jiy/601_915T_datazip1_20170127.zip
Data Zip #2:
http://www.mediafire.com/file/ct843vgvcco6v8k/601_915T_datazip2_20170127.zip
Data Zip #3 for W8 models:
https://www.mediafire.com/file/bo4t4omjihbm898/W8_datazip_601.zip/file

Also, if you try this out on anything, be sure to let me know if it worked, so we can update the list!

Just to clarify Alaksa. What's the difference between the two datafix zips? Do both need to be flashed?

Aaren11 said:
Just to clarify Alaksa. What's the difference between the two datafix zips? Do both need to be flashed?
Click to expand...
Click to collapse
Great question!
At this time, you only need #1 for the two mentioned ROMs. #2 has the same files, but in slightly different folders, which may work on other ROMs, which keep them in different places. #2 MAY work better for TW roms, but you'll have to test it out sometime....
I tested out both ROMs, but only some initial testing, like rebooting. When you reboot, the cellular keeps working, so it is persistent, which is good!
I did notice one problem, which needs investigation: with Mickey's 3.0.2-0 TWRP, backing up works fine, but after a restore, the cellular doesn't work. Something like titanium backup, or some other app data backup and restore might be needed for backing up your data.
My wife is due Monday, so I will be taking a break for a little while, but don't worry, I'll be back. Be sure to post anything here as you try things out!
Sent from my GT-I9505 using XDA-Developers Legacy app

Congrats on the inbound baby and thank you for all your work here.

I posted in the RR thread but am bringing here for discussion. I initially had trouble connecting to secured routers but after connecting to an open wifi network it will now connect with no trouble to my wps2 secured network... So in summary everything is working well after the initial unexplainable hiccup.

Tested out both data1 and data2 on MickeysROM (TW 6.01) and it caused systemphone error on either one. Couldnt fix so I am going to another ROM for now.

JeremySS said:
Tested out both data1 and data2 on MickeysROM (TW 6.01) and it caused systemphone error on either one. Couldnt fix so I am going to another ROM for now.
Click to expand...
Click to collapse
JeremySS,
Thanks for the feedback!
Sent from my GT-I9505 using XDA-Developers Legacy app

Thank you for this. I'm running Resurrection remix 5.8.1 (7.1.1) with your data fix with Mickey's TWRP 3.0.3.1_915F on my N915T runs beautifully!

Finnigan2 said:
Thank you for this. I'm running Resurrection remix 5.8.1 (7.1.1) with your data fix with Mickey's TWRP 3.0.3.1_915F on my N915T runs beautifully!
Click to expand...
Click to collapse
No problem Finnigan2! I am glad that my work could be useful!
Sent from my GT-I9505 using XDA-Developers Legacy app

Working on SM-N915R4 (U.S. Cellular) With:
CPL1 BaseBand [Latest 6.0.1USC]
&
Emotion TW MM r26 Kernel
&
TekX EPE2 [6.0.1] Release (currently using).
I Install ROM(s), Kernel, DataFix, then SuperSu SR3 after 1st boot. (su is present in ROM, but missing from drawer).
DataFix provides access to Verizon, T-mobile, and AT&T.
Freaky in a good Universal Way.
Thanks!

unimatrix725 said:
Working on SM-N915R4 (U.S. Cellular) With:
CPL1 BaseBand [Latest 6.0.1USC]
&
Emotion TW MM r26 Kernel
&
TekX EPE2 [6.0.1] Release (currently using).
I Install ROM(s), Kernel, DataFix, then SuperSu SR3 after 1st boot. (su is present in ROM, but missing from drawer).
DataFix provides access to Verizon, T-mobile, and AT&T.
Freaky in a good Universal Way.
Thanks!
Click to expand...
Click to collapse
Wow! That is surprising news indeed! Thanks for the feedback!
Sent from my SM-N915F using XDA-Developers Legacy app

Quick update...After flashing the latest RR build (01/31/2017) data quit. It had been working well with the data1 fix but now the cellular connection was still there but it always said connecting in the status area and would never get 3g or LTE. I went into recovery and flashed the data2 file and now all is working perfectly again.

JeremySS said:
Quick update...After flashing the latest RR build (01/31/2017) data quit. It had been working well with the data1 fix but now the cellular connection was still there but it always said connecting in the status area and would never get 3g or LTE. I went into recovery and flashed the data2 file and now all is working perfectly again.
Click to expand...
Click to collapse
Excellent troubleshooting and feedback! Thanks!
Sent from my GT-I9505 using XDA-Developers Legacy app

UPDATE!
Check out the OP for new information! AOKP Nougat ROM has been added to the list! Keep in mind though, that there is now a T-Mobile variant in the T-Mobile thread, but the option is still there to use the tbltexx version.

F2fs???
is there a way to make this data fix work on a f2fs file system rom???

ckelley1989 said:
is there a way to make this data fix work on a f2fs file system rom???
Click to expand...
Click to collapse
I don't know if that would matter. Did it fail to work on an f2fs filesystem ROM?

AlaskaLinuxUser said:
I don't know if that would matter. Did it fail to work on an f2fs filesystem ROM?
Click to expand...
Click to collapse
Yes. On mickey387 super fast and famous mm rom. Tried every different version and woukd fail during flash in twrp with a error 7 message....