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.
Related
As reported here and on SU, the maintenance update from Sprint/HTC is being rolled out over the air. Can people with Root and/or a custom ROM tell us what happens if you update? I doubt you'll loose root but I'm just curious and I'm sure other are too.
This is only for rooted users. No need to post if the update isn't available to you yet. IF it works for you and you're rooted/rom'ed, post.
Root: Yes or No
ROM: Tell us which
Reuslts: Still rooted, working fine?
As for me, the update isn't available yet but I want to know what I'm getting in to before I allow it.
EDIT: So far it looks like the update won't even install for rooted users - Recovery image gets in the way...
EDIT2: freshlyill has provided a direct download of the update pkg file in post #7
EDIT3: This update definitely cannot be made on rooted Heros but doesn't hurt the phone if you try. No risk.
EDIT4: UPDATE: SUCCESS! thecodemonk has confirmed that root is still available on page 4. Process: Use stock RUU to bring it back to stock, download and apply update, re-root like normal!
EDIT5: Satinkzo has also confirmed that the above works. Now, somebody ROM this sucker up
Im rooted on Fresh ROM. Dl the update now, at about 20%...
I cannot get it to install on rooted phone. Looks like the recovery image or something gets in the way.
freshlyill (from fresh rom) got the update and also said it seemed to error out because of the recovery image. But he rebooted again and it appeared to work. He still has root but has no signs that the update applied. Still getting wake lock on stock messaging app.
No firmware update available for my phone yet.
Decided to take the plunge since I nandroided recently...whee! (going about 1%/second ^_^)
same here. Rooted with no custom rom. Won't take the update.
here's the update..
http://rapidshare.com/files/308943608/update.pkg
Rooted: Yes
Custom ROM: No
Results: Failed to update with the following message:
Welcome
Build : RA-heroc-v1.2.3
Finding Update Package
Opening Update Package
Verifying Update Package
E:No signature (265 files)
E: Verification failed
Installation aborted
At this point I select reboot system now and it boots normally to the old firmware.
ElAguila said:
Rooted: Yes
Custom ROM: No
Results: Failed to update with the following message:
Welcome
Build : RA-heroc-v1.2.3
Finding Update Package
Opening Update Package
Verifying Update Package
E:No signature (265 files)
E: Verification failed
Installation aborted
At this point I select reboot system now and it boots normally to the old firmware.
Click to expand...
Click to collapse
Same here, but using Fresh ROM
@Fresh: how did you get the update to take?
Same as ElAguila
ElAguila said:
Rooted: Yes
Custom ROM: No
Results: Failed to update with the following message:
Welcome
Build : RA-heroc-v1.2.3
Finding Update Package
Opening Update Package
Verifying Update Package
E:No signature (265 files)
E: Verification failed
Installation aborted
At this point I select reboot system now and it boots normally to the old firmware.
Click to expand...
Click to collapse
Ditto...I'm going to nandroid, RUU, then apply the update and see if I can re-root from there. I'll let ya know (assuming someone doesn't beat me to it)
Verification failed here as well.
thecodemonk said:
Ditto...I'm going to nandroid, RUU, then apply the update and see if I can re-root from there. I'll let ya know (assuming someone doesn't beat me to it)
Click to expand...
Click to collapse
I'm in that process right now just to test. You might beat me though
thecodemonk said:
Ditto...I'm going to nandroid, RUU, then apply the update and see if I can re-root from there. I'll let ya know (assuming someone doesn't beat me to it)
Click to expand...
Click to collapse
Good luck solder lol i would not risk loosing root.
shouldn't we wait to include this in a custom rom? Sense no one rooted has this update we cant get a Nand backup of it
Satinkzo said:
I'm in that process right now just to test. You might beat me though
Click to expand...
Click to collapse
The reason it won't work is that the rooted image has testkeys and the stock image has release keys. You don't want to apply the maintenance update on a rooted phone in any manner. The purpose of the maintenance release, from what I've heard, is to fill the hole that makes root possible.
I downloaded and opened the update.pkg and it is just a zipped file. I wonder if it would be possible to push it with adb?
Negrito said:
Same here.
@Fresh: how did you get the update to take?
Click to expand...
Click to collapse
i didn't.. i just found the update.pkg after downloading, update didnt install though. i'm facing same problems. looking like we will have to flash back to stock then root again..
kylez64 said:
Good luck solder lol i would not risk loosing root.
shouldn't we wait to include this in a custom rom? Sense no one rooted has this update we cant get a Nand backup of it
Click to expand...
Click to collapse
It's actually not as dangerous as it sounds since I can always RUU back to the vulnerable version and nandroid restore.
EDIT: Status...RUU complete, applying update now.
chicojd said:
The reason it won't work is that the rooted image has testkeys and the stock image has release keys. You don't want to apply the maintenance update on a rooted phone in any manner. The purpose of the maintenance release, from what I've heard, is to fill the hole that makes root possible.
Click to expand...
Click to collapse
If that is the case then you don't want this MR if you want to stay rooted then. I was kind of hoping that wasn't the case with this MR.
freshlyill said:
i didn't.. i just found the update.pkg after downloading, update didnt install though. i'm facing same problems. looking like we will have to flash back to stock then root again..
Click to expand...
Click to collapse
My mistake, i misread 'flipz' post.
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?
thanks go to damien667 for the method, brswattt and ladios for being brave and testing.
DOWNLOAD:
View attachment clockworkmod-2.5.1.7-liberty-offmode-charging.zip
Instructions:
unzip the recovery image and use your specific devices installation procedure for recovery.
This is a custom clockworkmod recovery 2.5.1.7 that allows you to finally turn off your phone and allow it to charge instead of it booting right back into clockwork.
a detailed explanation on how this is acheived is HERE
This recovery only has a modified ramdisk, functionality and use is the same as clockworkmod 2.5.1.7 official.
enjoy.
now i'm off to fix the DHD recovery.
EDIT: manually installing is the only option at the moment, thanks gruss.
stupid s-on.
ROM MANAGER should have the latest recovery image available with a fix for powering off and charging, thread will stay up for hostorical reference but these images are no longer required, it is always recommended to upgrade to the current version of rom manager and cwm that your rom requires
amazinglarry311 said:
I need one experienced user to test this recovery image.
The mod performed is the same one done to the the g2 and mt4g and works flawlessly on the recovery images I have posted altering recovery to allow charge while the phone is off and not boot to clockworkmod.
If you do not know how to flash recovery images manually through fastboot or from a rom do not continue.
If you do not know how to recover from a bad recovery flash do not continue.
This image is untested as I do not have access to an aria. Be warned.
Danger should be low, please understand I do not accept liability in the very very small chance something goes horribly wrong.
If you are not sufficiently scared yet, please test and let me know if it works, if not working please stand by, flash back to your previous recovery image, and I will post a fix.
Thanks go to damien667 for figuring it out.
View attachment 562769
if people are using cwm 3.x i can modify that as well.
Click to expand...
Click to collapse
Lots of views - no takers yet...
I'm sure many would find this very useful. If anyone has a "spare" Aria, or is really brave (I have neither a spare nor the guts), please check it out.
.
Bad recovery flash won't kill your phone.
Oh well.
we cant replace the recovery with out unrooting and redoing unrevoked
still need s-off
I thought you could do a temporary flash that doesn't stick. I suppose that's problematic as the device has to be turned off to test the mod. Go figure. The threads here for when someone wants to try it out, I can only think of two potential issues that would cause this not to work. Does anyone have a link to an OTA recovery image in img form for the aria? I'll google it, but if anyone knows please answer.
Flashed, not working. When it booted into recovey, it stayed on the htc screen, no menu was shown. `adb devices` showed that it's in recovery mode, though. Used adb shell to look around, everything's there but no /etc/fstab... can't mount anything.
hk-froyo-ota-recovery-image.zip md5sum: 0d44b10cbb8f1d6d40e68b522e578042
Although I did unroot in order to flash it, I think it might be ok to run unrevoked on sense 2.1 or 2.2 rom to do the job.
edit: wow, ota pops up! never throught i would see that again.
INFO/htcCheckinService(80): Started a new update download: http://fotadl.htc.com/OTA_Liberty_F...4_P_release_138425_15969388mnzxpm7szkle1k.zip
ladios said:
Flashed, not working. When it booted into recovey, it stayed on the htc screen, no menu was shown. `adb devices` showed that it's in recovery mode, though. Used adb shell to look around, everything's there but no /etc/fstab... can't mount anything.
hk-froyo-ota-recovery-image.zip md5sum: 0d44b10cbb8f1d6d40e68b522e578042
Although I did unroot in order to flash it, I think it might be ok to run unrevoked on sense 2.1 or 2.2 rom to do the job.
Click to expand...
Click to collapse
Thank you for testing this, Ladios!
Awesome, thanks for the test. I'm guessing it's the ueventd binary that isnt needed. i'll know in about five seconds after i pull apart the OTA recovery.
Thanks for testing, i'll have another one up in a jiffy.
yup. init.rc was calling a binary (ueventd) that isnt required.
try this one out:
EDIT: removed see bottom of the post
Sorry guys, this would be way easier if i had one.
These are the same changes aligned with the other mods i've done:
basically the OTA recovery contains four binaries not found in CWM
detect_key
power_test
offmode_charging
choice_fn
the init.rc on the original OTA recovery calls these binaries when plugged in and off, the recovery kernel should load but keeping the phone off and in a charging state. adb will should available in this mode as well.
a better explanation was in the mt4g thread: http://forum.xda-developers.com/showpost.php?p=12513699&postcount=3
EDIT: removed, found resources needed.
please test. and thank you. this mod is in response to a request by gruss at the CM forum to see if the same mod could be applied.
EDIT: the OTA recovery that was posted did not contain some resources, give me five minutes... i found the original RUU and the recovery image there has everything i need. filesize increase is due to inclusion of offmode_charging_images that i found in the original OTA recovery.
EDIT: REMOVED - test succesful see first post.
this one really should work. i have pretty good faith in it..
If not, it looks like the mod works with some recoveries and not all. i may attempt one more time, but i dont want to waste people's time here.
amazinglarry311 said:
yup. init.rc was calling a binary (ueventd) that isnt required.
try this one out:
EDIT: removed see bottom of the post
Sorry guys, this would be way easier if i had one.
These are the same changes aligned with the other mods i've done:
basically the OTA recovery contains four binaries not found in CWM
detect_key
power_test
offmode_charging
choice_fn
the init.rc on the original OTA recovery calls these binaries when plugged in and off, the recovery kernel should load but keeping the phone off and in a charging state. adb will should available in this mode as well.
a better explanation was in the mt4g thread: http://forum.xda-developers.com/showpost.php?p=12513699&postcount=3
EDIT: removed, found resources needed.
please test. and thank you. this mod is in response to a request by gruss at the CM forum to see if the same mod could be applied.
EDIT: the OTA recovery that was posted did not contain some resources, give me five minutes... i found the original RUU and the recovery image there has everything i need. filesize increase is due to inclusion of offmode_charging_images that i found in the original OTA recovery.
View attachment 563263
this one really should work. i have pretty good faith in it..
If not, it looks like the mod works with some recoveries and not all. i may attempt one more time, but i dont want to waste people's time here.
Click to expand...
Click to collapse
This does indeed work The screen is a little dim though when it's charging.
brswattt said:
This does indeed work The screen is a little dim though when it's charging.
Click to expand...
Click to collapse
Excellent, I will update the first post. About the screen being slightly dim - the stock aria recovery image used to actually load pictures showing the charging status while the phone is off, this would draw the images on the phone and the background was never a solid black, go figure. Cwm doesn't display them correctly as the resources are there but it was never written into the recovery itself or it's a frame buffer issue our something along those lines.
EDIT: see first post for download.
amazinglarry311 said:
thanks go to damien667 for the method, brswattt and ladios for being brave and testing.
DOWNLOAD:
View attachment 563834
Instructions:
unzip the recovery image and use your specific devices installation procedure for recovery. TESTERS - see below.
This is a custom clockworkmod recovery 2.5.1.7 that allows you to finally turn off your phone and allow it to charge instead of it booting right back inot clockwork.
a detailed explanation on how this is acheived is HERE
This recovery only has a modified ramdisk, functionality and use is the same as clockworkmod 2.5.1.7 official.
enjoy.
now i'm off to fix the DHD recovery.
TESTER NEEDED: Now the instructions to install the recovery are to do it manually and unzip the file. the zip itself is actually flashable, i just need to know if the capability exists for the aria to flash a recovery image while booted into recovery. The way that some OTA updates usually work (or used to) allowed raw images to be flashed while in recovery. I know the nand is locked when you are booted, but does the same apply to recovery? My assumption is no. if someone would like to test the zip from their current recovery and flash it, and reboot to recovery, turn off and try to charge to see if it sticks. possible things that can happen testing this: it doesnt stick and you keep your old recovery and flash manually, or you lose your recovery image (doubtful and highly unlikely)
it occurs to me that the flashable might not work, are your devices the kind that write the recovery image every time the phone is turned off?
Click to expand...
Click to collapse
Cannot flash the zip:
Code:
-- Installing: SDCARD:2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
Opening update package...
I:Update file path: /sdcard/2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
Installing update...
I:Trying update-binary.
E:Error in /sdcard/2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
(Status 0)
Installation aborted.
I tried to use flash_image before, it can't be read/write. Except one time, unrevoked failed its attempt and stopped right before its last couple of stages, flash_image worked for once. In other times, it failed and then rebooted, left me no chance to run flash_image.
for now manual flash looks like the way to go. you can check the OP again, there's a slim possibility a LIBEIMG.zip will load from hboot. it's in the first post. this kind of thing works for mt3g/dream/g2/mt4g but these suckers are all s-off as well. sigh. lame.
amazinglarry311 said:
for now manual flash looks like the way to go. you can check the OP again, there's a slim possibility a LIBEIMG.zip will load from hboot. it's in the first post. this kind of thing works for mt3g/dream/g2/mt4g but these suckers are all s-off as well. sigh. lame.
Click to expand...
Click to collapse
Hboot loaded the zip, showed a vertical status bar on the top-right corner, said checking the zip, and then stopped.
Seems unrevoked is the only way...
yeah i just finished updating the original post. thanks to everyone who tested.
s-on sucks big time.
just to be clear though the image is reported to work and charge while off.
Thanks for all the work.
Sent from my Liberty using XDA Premium App
amazinglarry311 said:
yeah i just finished updating the original post. thanks to everyone who tested.
s-on sucks big time.
just to be clear though the image is reported to work and charge while off.
Click to expand...
Click to collapse
So if I understand this correctly:
1. Connect phone to computer whilst booted up
2. Run Unerevoked, but use the included ".img" file from the OP file
3. Install the new recovery image
4. Reboot phone (if it doesn't do it on its own)
Or do I flash the entire .zip file from the phone's recovery menu?
Sorry if these are "dummy" questions...
Thanks for this little modification of the recovery! I actually see a little battery on the screen when charging now. However, Recovery still says 2.5.0.7, but charging while off works with no problems. I also flashed CM7 using the recovery I downloaded in this thread, so the recovery has no issues as well! Thanks again!
DanGeorges said:
So if I understand this correctly:
1. Connect phone to computer whilst booted up
2. Run Unerevoked, but use the included ".img" file from the OP file
3. Install the new recovery image
4. Reboot phone (if it doesn't do it on its own)
Or do I flash the entire .zip file from the phone's recovery menu?
Sorry if these are "dummy" questions...
Click to expand...
Click to collapse
I actually had to first unroot before Unrevoked actually installed the new recovery image. Something is weird about the Aria about not flashing recoveries directly...
foreign_legion said:
I actually had to first unroot before Unrevoked actually installed the new recovery image. Something is weird about the Aria about not flashing recoveries directly...
Click to expand...
Click to collapse
So if I unroot, then use Unrevoked, how do I get unrevoked to use the new recovery? Is there a file somewhere on my computer that should be swapped out first?
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
microi said:
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
Click to expand...
Click to collapse
How about reverting to stock 3.0.1, then OTA updating to 3.2 and then rooting/flashing recovery and custom rom/kernel. I would think the issue is with the 3.2.1 OTA update itself.
I'm not completely sure I understand but if u can try this,
Download the universal root update zip and put it on your xoom
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Flash the universal root.zip and boot up and use a root file manager to delete those two file and clockwork should stick through a reboot
Sent from my ADR6400L using Tapatalk
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
bandit197 said:
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
Click to expand...
Click to collapse
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
okantomi said:
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
Click to expand...
Click to collapse
Cheers, I went ahead with it and it worked out no problems, unlocked, rooted and I can access recovery. Ill post the details in the guide thread to keep everything in the one place.
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Click to expand...
Click to collapse
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
microi said:
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
Click to expand...
Click to collapse
by not letting it boot I mean don't let it boot into the rom, and both of those methods u stated will work just fine to reboot
And flash it using whatever method you desire, but I forgot to mention that you may need to flash clockwork again after you boot and delete those files because the install recovery.sh obviously flashes the stock recovery and the point of my method is to keep a custom recovery on your device
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Sent from my Xoom using Tapatalk
superchilpil said:
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Click to expand...
Click to collapse
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
teameos said:
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
Click to expand...
Click to collapse
I'm getting more and more confused the more times I read this.!!
I have done the update then unlocked to find I now have the green bot!!!!!
Someone please send a simple step by step with some file links to revert back to stock 3.2!
Thanks
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
willysp said:
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
Click to expand...
Click to collapse
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
okantomi said:
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Click to expand...
Click to collapse
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
bwcorvus said:
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
willysp said:
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
ydaraishy said:
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
Click to expand...
Click to collapse
Thanks, that helps explain what they are. So, if an OTA (like 3.2 apparently) wants to patch/replace stock recovery, those are the files that do it on next boot. Would be nice if they deleted themselves when done (from a hacker's POV), but for people running stock, I guess it makes sense for the OS to check the recovery partition at each boot and overwrite it with stock recovery if needed.
willysp said:
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
okantomi said:
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
Click to expand...
Click to collapse
Sure - glad to.
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
bwcorvus said:
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Thanks for the info.
I am trying to install ota 1.84 from 1.53 stock backup I made when I 1st rooted-after I flashed the stock rom to my device I was prompted for the ota update which I downloaded I fastboot flash stock recovery used ota rootkeeper to protect root when I went to install the update it went about 25% then this message appeared,epic fail I rechecked my rom to make sure there wasn't any rooted apps on it just plain stock I know it something I have missed along the way but I stuck atm -went ahead and reflashed cwm and restored backup -Can anyone help point me in the right direction on this one??I apoligized in advance if its been posted somewhere on here I have failed to locate and answer
jmcdonald58 said:
I am trying to install ota 1.84 from 1.53 stock backup I made when I 1st rooted-after I flashed the stock rom to my device I was prompted for the ota update which I downloaded I fastboot flash stock recovery used ota rootkeeper to protect root when I went to install the update it went about 25% then this message appeared,epic fail I rechecked my rom to make sure there wasn't any rooted apps on it just plain stock I know it something I have missed along the way but I stuck atm -went ahead and reflashed cwm and restored backup -Can anyone help point me in the right direction on this one??I apoligized in advance if its been posted somewhere on here I have failed to locate and answer
Click to expand...
Click to collapse
hopefully better image
Geeze best image i have
I never apply ota update but hope this help you out.
http://www.jbhale.com/2012/06/09/dev-how-to-apply-ota-htc-tested-on-one-s/
Sent from my HTC One S using Tapatalk 2
It says Error in file, have you tried redownloading it? Did you manually download the OTA file or did you get it the usual way (search for updates in phone).
x1tyme said:
I never apply ota update but hope this help you out.
http://www.jbhale.com/2012/06/09/dev-how-to-apply-ota-htc-tested-on-one-s/
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Thanks will give it a look
frdd said:
It says Error in file, have you tried redownloading it? Did you manually download the OTA file or did you get it the usual way (search for updates in phone).
Click to expand...
Click to collapse
I downloaded it directly from device
It says:
Code:
Verifying current system...
assert failed: blablabla
To me, this means:
It checks the system on your device to see if it can take this OTA, but the hash of your build.prop file does not match what it expects.
Maybe this OTA is not for your device or you're not on truly stock 1.53.
-Jobo
touch of jobo said:
It says:
Code:
Verifying current system...
assert failed: blablabla
To me, this means:
It checks the system on your device to see if it can take this OTA, but the hash of your build.prop file does not match what it expects.
Maybe this OTA is not for your device or you're not on truly stock 1.53.
-Jobo
Click to expand...
Click to collapse
Yeah going take a look at it later that's kinda what I was thinking anyhow I appreciate the help