Database Info

Rooted users: Results After Installing Maintenance Update?

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.

*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.

[Q] MyTouch 4G Slide Root question (hboot 1.45.0013/bootloader unlocked/S-On)

Alright, so I got this phone a week ago. First off, I am loving it. Screw Apple.
Anyway, first thing I wanted to do was root it so I can debloat all of T-Mobile's poop applications they cram inside of it.
I've read places that HBOOT 1.45.0013 isn't rootable. I've read it IS rootable, but only with S-OFF on a previous HBOOT. And I've read that it is rootable, but you can't get S-OFF after root.
I've used HTC's unlock tool, which went successful because I flashed CWM through fastboot. I've tried HTC Supertool, MrRoot, and Revolutionary (which says it isn't compatible)
My question then is, which of the above statements is true? If it is rootable, I don't care about S-OFF too much. But I can't ever find a guide that tells me how to root it with this current HBOOT.
Halp pl0x? <3

If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.

Limewirelord said:
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Click to expand...
Click to collapse
What's the difference in flashing Superuser, and downloading it from the Market?
Sent from my myTouch_4G_Slide using xda premium

It won't install correctly if you do it while the system is on and live (through the market) you have to do it while the operating system is not running (through clockworkmod)
Afterwards, it's fine to update through the market, but the initial install will fail if done on a running version of Android.

Blue6IX said:
It won't install correctly if you do it while the system is on and live (through the market) you have to do it while the operating system is not running (through clockworkmod)
Afterwards, it's fine to update through the market, but the initial install will fail if done on a running version of Android.
Click to expand...
Click to collapse
..Huh, just flashed Superuser. Weird that it's that easy. All the other threads were like "omg HBOOT 1.45.0013 can't be rooted hnnnnnggg"
So, now onto ROMs, are there any ICS based ones you reccomend?

Btw I see tht your question has been answered but in Mr Root's next update will include a Rooter/Unrooter for the newest H-Boot (Without S-Off)

MewTech said:
..Huh, just flashed Superuser. Weird that it's that easy. All the other threads were like "omg HBOOT 1.45.0013 can't be rooted hnnnnnggg"
So, now onto ROMs, are there any ICS based ones you reccomend?
Click to expand...
Click to collapse
For a while it was so - you couldn't do anything with 1.45.0013, HTC broke the OTA so you couldn't unlock it.
In my quest for s-on to s-off (still ongoing) I found a leaked copy of the OTA as a signed HTC package so now we can actually unlock them, and people can work with them and they are now rootable.
Still stuck with s-on though, which is unfortunate - we're working on it and hopefully can crack it soon. Got some leads we're chasing down, each layer we unravel shows us another that has to be solved below it.
ICS? Dunno - i'm not interested in ICS yet, still trying to learn gingerbread through and through (i'm an android newbie) before moving up to ICS. That's on hold right now because of the s-on issue i'm working on. tbalden has been leading the charge on ICS and I would recommend looking into his works if that is your interest.

Limewirelord said:
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Click to expand...
Click to collapse
can you explain in detail how to flash it to rom?????

Using CWM to flash it, you will need the super user ZIP file. Find it somewhere (it's everywhere, no doubt) and put it on your SD card. Reboot the phone to recovery mode, and using CWM recovery, select "flash any zip from SD card" (I'd look up the exact wording, except that my phone has been running a solid 24 days without reboot and I really wanna see how long it goes). Navigate to where your super user ZIP file is, and select it. Follow prompts, et voila, root on reboot.
Assuming all works. If something didn't work, you messed up. Try again from step 1, make sure you have a zip file and not an APK file, make sure you select the correct "flash zip" option (there are two, one specifically for update.zip and another for whatever zip you choose).
HIH

ok this is my huge problem i have the same hboot with s-on
i have the full stock stupid t-mobile mt4gs AOS 2.3.4 software# 1.55.531.3 and i DONT have CWM or any of the extras in only thing i succeeded is getting the bootloader unlocked so what should i do?

Install clockworkmod then flash either superuser pr a ROM - if staying stocl with root, be a good time to do some spring cleaning on all the junk it comes with pre-installed.

Blue6IX said:
Install clockworkmod then flash either superuser pr a ROM - if staying stocl with root, be a good time to do some spring cleaning on all the junk it comes with pre-installed.
Click to expand...
Click to collapse
ok i download this now i try flash CWM recovery and i get this
an error occurred while attempting to run privileged commands!
??????
what do i do next??

We love to title our posts here
crimedave1987 said:
ok i download this now i try flash CWM recovery and i get this
an error occurred while attempting to run privileged commands!
??????
what do i do next??
Click to expand...
Click to collapse
Well,
What exactly did you do that returned this error (mainly because I don't remember if fastboot or adb returns that)? What tutorial/guide were you following? Were you in adb trying to "dd" the CWM recovery image or were you trying to flash an img file from within fastboot? Either way, what was the exact command you typed?
Your other thread (sorry, didn't realize I had replied to you in two different places) received an answer as well. After looking around to get the info you need for this post, I see now you've posted in quite a few threads to which I'm subscribed (guess I just never noticed the name, sorry).
So I see you have an unlocked bootloader. At this point, yes, flash CWM. Blue6ix gave an excellent post on how to do this. Is this the one you are currently trying to follow in order to install CWM?

tried to use superuser
I tried to load the superuser zip file in recovery with cwm. installation aborted. any suggestions? I have mytouch4gslide with s on unlocked with HBoot 1.45.0013

wesomatic said:
I tried to load the superuser zip file in recovery with cwm. installation aborted. any suggestion? I have mytouch4g with s on unlocked with HBoot 1.45.0013
Click to expand...
Click to collapse
From my earlier post:
cj chitwood said:
Using CWM to flash it, you will need the super user ZIP file. Find it somewhere (it's everywhere, no doubt) and put it on your SD card. Reboot the phone to recovery mode, and using CWM recovery, select "flash any zip from SD Card”. Navigate to where your super user ZIP file is, and select it. Follow prompts, et voila, root on reboot.
Assuming all works. If something didn't work, you messed up. Try again from step 1, make sure you have a zip file and not an APK file, make sure you select the correct "flash zip" option (there are two, one specifically for update.zip and another for whatever zip you choose).
HIH
Click to expand...
Click to collapse
Did this help? Only things I can think of are (1) using ”flash update.zip” instead of ”flash [any] zip file” or, less likely, (2) trying to flash an apk instead of a zip.
--
Sent from my Android ”phone”:
HTC DoubleShot /T-Mobile MyTouch 4G Slide running Bulletproof

Yes, that thread did help me. I used your instructions. I even have a new sd card. I have read some threads about formating it first. I did not do that. Also where can I get a good zip file? I down loaded it from some file sharing program 2share I think... Tried again ROOTED!!!! It was so easy!!! Been doing this for a week!!! Wow!!!!!!!!!!!!!!!!!!!

bricked my phone!!!
Just want to add... Do not use ROM Manager from The Market. Bricked my phone. Just stays in start up. Had it rooted and everything!!!!

NO BRICK
Thank God For CWM!!!!!

I am stuck someplace in betweem
Hi:
I too have a MyTouch Slidwe 4G with the hboot 1.45.0013. All the contrary information I have found lead me to go to the professionals. I purchased the root-android.org software. It seemed to run fine - I got no errors and it said that the phone was rooted. I see the superuser app on the phone. However, when I try to run Titanium Backup, it says that the phone is not rooted. The people at root-android.org are not answering my emails (I did get my money back). Any ideas of where I should go from here?
Thanks!

You should never have to purchase root for any android, if it has been done once then chances are it is plastered how to all over the internet, if the phone has a thread on xda then it will be there. Being you got yourself this far I'll help you out a bit more
http://forum.xda-developers.com/showthread.php?p=29439712
Read and understand is my advice, always read until you understand, then search if you have questions, then finally ask questions here if you are still stumped.
For the most part every question you can ask is already answered by one of the super helpful xda folk here, and chances are it is the right information.
I do advice to gain radio soff with the wire trick, it will make life easier... Read up and happy flashing!
Sent from my Nexus 7 using xda premium

OTA update

Phone has just told me that an update; 'System enhancement 59.02 MB' is available, I've downloaded it, installed it and the phone has rebooted.
However... it reboots into Clockworkmod recovery so I have to select 'Reboot now'.
Aswell as producing an 'abnormal reset' error, the update is still available; it doesnt seem to have installed.
Phone has been rooted with superoneclick following HTC bootloader unlocking. As nandroid backup was not available from recovery, I installed clockworkmod recovery. Is this causing the issue? Can I stop the phone booting into recovery every time?
Help?
Please?!

you need stock recovery to get OTA updates.. flash the stock recovery and you will be fine

Thanks.
erm. How?

azzledazzle said:
you need stock recovery to get OTA updates.. flash the stock recovery and you will be fine
Click to expand...
Click to collapse
Allow me to say it better: You need a stock recovery to implement the OTA updates - you can download w/o it but must have it to install it.

How do I get stock recovery or disable/uninstall clockworkmod?

Badmiker said:
How do I get stock recovery or disable/uninstall clockworkmod?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1604677

Thanks so much! That has solved the CWM issue and phone is now trying to update.
1st attempt failed. Is now downloading update again. Maybe a different update now the firmware has changed?
Installing again....
Arg! assert failed: apply_patch_check
?

orenfl said:
Allow me to say it better: You need a stock recovery to implement the OTA updates - you can download w/o it but must have it to install it.
Click to expand...
Click to collapse
I used the all-in-one toolkit to unlock bootloader and all that good stuff. But i never flashed a recovery. Phone is rooted and everything. Is it absolutely necessary to flash the recoveries in that toolkit? What are the purposes for it? (noob status >_>) I know what the stock one is but was always wondering about the rest and if you really needed them.

ToterPunkt said:
I used the all-in-one toolkit to unlock bootloader and all that good stuff. But i never flashed a recovery. Phone is rooted and everything. Is it absolutely necessary to flash the recoveries in that toolkit? What are the purposes for it? (noob status >_>) I know what the stock one is but was always wondering about the rest and if you really needed them.
Click to expand...
Click to collapse
Actually, I haven't done root yet to this specific phone, just for my previous ones.
Try to look in that linked thread to search for an answer.

Is this a TMO US update?

ive just got my update for my sim free carrier free one s. Im in the uk.
Not sure what the changes are supposed to bring...cant say ive noticed any difference at all yet.

This is very frustrating, it's really not happening for me.
I've unrooted & reflashed with stock recovery then downloaded update but it's still failing to install.
assert failed: apply_patch_check ("SystemUI.apk", big code)
E:Error in /internal sdcard/download/OTA)Ville_U_HTC_Europe....
Status 7
Installation aborted.
Dammit. Is the phone getting the wrong update? Can anyone help please?

Badmiker said:
This is very frustrating, it's really not happening for me.
I've unrooted & reflashed with stock recovery then downloaded update but it's still failing to install.
assert failed: apply_patch_check ("SystemUI.apk", big code)
E:Error in /internal sdcard/download/OTA)Ville_U_HTC_Europe....
Status 7
Installation aborted.
Dammit. Is the phone getting the wrong update? Can anyone help please?
Click to expand...
Click to collapse
For the OTA update you will nedd to have stock recovery on your phone, bootloader relocked and a stock rom without any apps uninstalled.

Relock the bootloader?!
Why?!
HTC allow me to unlock it, so surely they should support an unlocked bootloader?
Locked with AIO toolkit and trying update again...

Badmiker said:
Locked with AIO toolkit and trying update again...
Click to expand...
Click to collapse
Thats most important for a sucessfull update. Had this problem with TMO Germany and after relocking the bootloader everything went fine. I used the RUU instead the OTA.
My update always stopped upon a checksum failure as long as the bootloader was unlocked. It was gone after relocking.

Someone please try skype video chat
Hello,
Can someone please see if the video chat in Skype is fixed.
Preferably someone who has already seen how bad it is before the update.
Thanks,
~Eric

I finally got my update HTC One S simfree in Canada to 1.78
incase anyone cares
I got my update yesterday...maybe it's wishful thinking, but my battery seems to have improved...this moring i was left with 26% after playing all night...normally I would be down to 5%

Here's the OTA update I got today:
OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2_release_258562piuubd9lrapskwje.zip

radio
does this update contain a radio update?
Can someone separate it and post it.
If you do please state which carrier/country you got the update from.

So far no t-mo usa update. Non usa customers claim the update solves the mutitasking issue reported on engadget.com for htc one x (s)

[Q] Anyone know what I am doing wrong by looking at this picture

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