I'm kind of new to rooting and flashing. But I was wondering how can I update my rooted at&t m8 4.4.4 (s-on) to the new lollipop update and stay rooted? Any help would be greatly appreciated.
natec806 said:
I'm kind of new to rooting and flashing. But I was wondering how can I update my rooted at&t m8 4.4.4 (s-on) to the new lollipop update and stay rooted? Any help would be greatly appreciated.
Click to expand...
Click to collapse
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Thanks redpoint73. Worked liked a charm
Redpoint -
I used the RUU to update, and now I can't get the SU Binary to update.
I think my backup of the app is messing things up. I installed the latest via zip file (TWRP), and am not really rooted yet.
I'm trying a clean install (wiped cache, dalvik), so I'll see if I can get rid of the original SU app I had installed (chainfire).
Edit: Still can't get rid of SU app.
Any ideas?
DanGeorges said:
I think my backup of the app is messing things up. I installed the latest via zip file (TWRP), and am not really rooted yet.
Click to expand...
Click to collapse
Latest being what number? I would suggest SuperSU 2.46.
redpoint73 said:
Latest being what number? I would suggest SuperSU 2.46.
Click to expand...
Click to collapse
That was, indeed, my problem. I was being directed to an older version of SuperSU update.zip.
Once i grabbed the REAL latest version, it worked like a charm!
Thanks, Redpoint.
redpoint73 said:
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Click to expand...
Click to collapse
What is required to run a RUU? I'm completely stock 4.4.4
redpoint73 said:
In short, you can't (update by official means and stay rooted). But its pretty easy to update, then just root again.
Couple options:
1) To OTA, you need stock ROM and stock recovery. Stock ROM means root is okay, but no system files can be missing or altered by you using the root permission (such as removing bloatware, frozen apps, added apps, etc.). You either need to put them back to stock, or revert to a stock nandroid of flash the stock 4.4.4 AT&T ROM. Then you need to find the stock recovery, flash it to the phone. At that time you can go into setting and look for the update. Unlocked bootloader is okay to OTA.
After the LP OTA installs, flash TWRP back to the phone and flash latest SuperSU to root again.
2) Another way, is to relock the bootloader and install the Lollipop RUU with your phone connected to a PC. RUU will then just update the phone to a stock LP image. This method is probably easier than tracking down the stock ROM and recovery, and getting them back on the phone. But the downside is that your data will be wiped by the RUU. Plus you have the added steps of relocking the bootloader; than unlocking again after the RUU. But I like RUU better as its a cleaner install than OTA and keeping user data (eliminates chance of random bugs caused by migrating user data).
After RUU, just flash TWRP and root again, same is the last part of method #1 above.
Click to expand...
Click to collapse
Would this work if i am living out side the US? i do have an AT&T simcard but still not connected to their network!
polar2792 said:
What is required to run a RUU? I'm completely stock 4.4.4
Click to expand...
Click to collapse
Backup your personal data (RUU will wipe the phone), and own a PC. That's it. RUU is intended to be run on a stock device, so nothing special is required.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Boudjelal said:
Would this work if i am living out side the US? i do have an AT&T simcard but still not connected to their network!
Click to expand...
Click to collapse
Are you saying you are still using your AT&T account while living in a foreign country? In that case, you will usually not get the OTA. I think there are a few exceptions, such as roaming in Mexico or Caribbean areas. But otherwise, not OTA.
The RUU method noted above will work anywhere.
Related
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
bloodbath said:
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
Click to expand...
Click to collapse
you need to flash the original recovery to install ota updates,, you will lose root access doing so
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
All you need to do is put the stock Tmo recovery on your one. Then go update with ota and you will still be unlocked but you do lose root.
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
bloodbath said:
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
Click to expand...
Click to collapse
I'm sorry I was wrong you will lose root after you update ota. But you can do ota while being unlocked so no need to relock bootloader just flash the stock Tmo recovery and update.
chong67 said:
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
Click to expand...
Click to collapse
U mean something like this!? https://copy.com/aSLnP
Team-Noctural.com/androidtechy.com/droidnow.com
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.
My phone is currently Rooted with TWRP installed, and im running gpe 4.4.4 stock rooted rom from the android development forums. Now, considering im s-on and have no computer at home at the moment, I was trying to figure out a way to update my firmware so that i can test out and flash one of these new lollipop roms. If I flash using twrp an at&t stock rom such as "Stock AT&T 1.58 Deodexed" from the AT&T forum,
1. Will I receive an OTA from at&T
2. Is it safe to accept the OTA
3. Will it update the firmware properly, so that i may flash a lollipop firmware.
My guess is that the answer to #2 will probably be a no. My phone is originally an at&t device btw.
Thanks for any help.
Most OTA's will fail simply cause you have a custom recovery.
If you can afford $25 just gain S-OFF using "Sunshine"
You need to be on stock ROM and stock recovery to install an OTA. Root is okay, and bootloader unlocked is okay ("okay" meaning the OTA will install, but you will lose root).
The stock ROM is normally odexed, so I don't think the deodexed will qualify as "stock" enough to allow the OTA to install (I'm thinking NO). The fastest way to return to stock ROM and recovery is probably by RUU (relock bootloader required for RUU).
Not sure what you mean by "safe" but as long as you meet the above conditions you will be able to receive and install OTAs. You will lose root as mentioned (but can easily just re-install custom recovery and root again). And your data should remain intact; although you should always backup important personal data, anyway.
But be aware there is currently no AT&T OTA that will update you to the current (3.x) firmware required for LP custom ROMs. The OTA for 4.4.4 is rumored for Dec. 29, but its already been delayed twice.
If you don't want to s-off, you will have to wait until 4.4.4 rolls out (to update the firmware). Or just s-off by sunshine and be done with it.
FOUND THE RECOVERY (See below)
Right now my goal is to go back to stock to flash the OTA Update. I am running my nandroid back up I first made when which is the 4.4.4 w/ Software # 1.58.502.1. and right now I have TWRP as my recovery.
Also can someone confirm something for me. This nandroid I am running is rooted obviously and has SuperUser on it. If I go back to the stock recovery can I still do the OTA update even though SuperUser is there and the phone is unlocked?
Also in order to get the stock recovery back on the phone I need to use ABD and the windows command prompt method correct?
Thanks
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
magicbumm328 said:
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
Click to expand...
Click to collapse
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
redpoint73 said:
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
Click to expand...
Click to collapse
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine. And as mentioned I found the stock recovery as well.
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Thanks for the help and suggestion too btw
magicbumm328 said:
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine.
Click to expand...
Click to collapse
SuperUser is same as root, and is fine.
When I say "modifed by root" that often is when a user deletes "bloatware" they don't want, or adds apps, or modifies apps in the system partition.
If you didn't explicitly do any of those things, you should be fine. You will know this is the problem when you install the OTA, as the install will fail with the error message that the "system has been modified".
magicbumm328 said:
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Click to expand...
Click to collapse
RUU = ROM update utility
RUU is super easy, you don't really need much guidance to use it. LOCKED or RELOCKED bootloader is required to run it (UNLOCKED if okay if you have s-off). PC required, and the RUU will wipe the phone (so backup any personal data you want to keep, into your PC, cloud, etc.). Aside from those points, RUU is a self-explanatory executable (.exe) program that runs from your PC, and simple to use.
Relocking the bootloader is accomplished easily with a single fastboot command (after connecting phone to PC and booting into fastboot mode): fastboot oem lock
This is also assuming you did the bootloader unlock yourself, and therefore have fastboot/adb setup on your computer.
Running the RUU itself (after relocking the bootloader) is very easy. Boot into OS (some folks have better success being booted into fastboot mode, but I think the RUU is designed to run when booted into OS), connect to PC, then just run the RUU executable on your PC. The RUU executable will then just guide you what you need to do. Its mostly automated, you just need to confirm a few dialogue screens, etc. The RUU will reboot the phone a couple times, install the needed files automatically, and that's really it.
However, since you seem confidant you already have a stock ROM and corresponding stock recovery, I suppose the RUU doesn't gain you too much. But if you hadn't done those steps already, it often saves folks the hassle of tracking down the right stock ROM and recovery for their CID and current firmware. RUU in my opinion is a cleaner install, as it installs a complete stock image (not just updating piecemeal, like an OTA often does).
Also, since OTAs typically need to be installed in sequence, you will probably need to OTA to 2.23 software, than another OTA to 3.42 software. As RUU is a complete image, it would get you to 3.42 software in one fell swoop.
One other thing to note, is that if you are for some reason not connected to AT&T's network (using another carrier, another country, etc.) you will not get any OTAs on the AT&T branded device. AT&T oddity here, most other version will still OTA, even when not connected to a specific carrier. In contrast the AT&T RUU is able to be downloaded and run by anyone with an internet connection and PC (regardless of country, carrier, etc.). I'm under the assumption that most folks on this forum section are on AT&T's network, although I know that some are not (you haven't stated either way).
RUU links are included on my Index thread under heading "RUUs": http://forum.xda-developers.com/showthread.php?t=2751432
Aside from wiping the phone (OTA keeps user data, but you may end up wiping anyway if you run into bugs after OTA), the other downside to RUU is that you need to relock the bootloader. Then you need to unlock the bootloader again (via the HTCDev.com site, or alternately sunshine) if you want to install custom recovery, install custom ROMs, root, etc.
So the choice is really yours (RUU versus OTA). I'm just giving it as an alternative.