Database Info

Restoring to stock

Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?

None of the 130 viewers have any advice on this one?

HB489 said:
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
Click to expand...
Click to collapse
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock

elvisypi said:
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
Click to expand...
Click to collapse
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.

HB489 said:
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
Click to expand...
Click to collapse
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case

elvisypi said:
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
Click to expand...
Click to collapse
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.

HB489 said:
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
Click to expand...
Click to collapse
No HTCdev is not a recovery, it's the only way of unlocking your bootloader, which you have done for sure. But don't worry I assure you they don't go so deep. There's nothing wrong in flashing manually the recovery. Good luck

[Q] 1.85 rooted to scottsrom JB rooted

Ok, I know this is probably already all documented somewhere, but the problem is, there is also lots of out of date info, and I'm not sure how to tell which info is current, and which isn't. This is my first Android phone, so I'm not completely up to speed on the meanings of everything.
I have an AT&T (evita) HOX. Its on 1.8.5 stock, and is rooted. I also set supercid some time ago, in preparation for unlocking it. I didn't proceed with the unlock at that time because I wasn't yet comfortable that everything I wanted backed up was backed up, and everything said unlock would wipe all user data.
I believe I have backup under control now, and I'd like to get to where I can put the "Scottsroms" rooted JB on, and do whatever I need to ensure that I can keep root. I want to stay as close to stock as possible, but with root, and that seems to be the best path for that.
I've been doing a bit of reading (including stuff linked from the rollup thread) and I have some questions I haven't been able to answer.
- Do I need to unlock the BL in order to get S-off? Or, if I S-off, do I not need to unlock the bootloader?
- I see the note about htc blocking supercid unlocking and using all 2's instead - is this still valid?
- I had read CWM didn't support this phone, but now I see something that contradicts that.
Basically, while I understand that there are no guarantees, I'd like to at least avoid doing things that are KNOWN not to work.
FWIW, I am a long time linux user. I have the Android sdk installed with adb and fastboot programs... I'm very comfortable at the command line.
If anyone can suggest what the recommended procedure is, which steps I need, which I should avoid, which info is current, which is out of date, I'd be very thankful.
If more info from me is needed, just let me know...

Megadave123 said:
Ok, I know this is probably already all documented somewhere, but the problem is, there is also lots of out of date info, and I'm not sure how to tell which info is current, and which isn't. This is my first Android phone, so I'm not completely up to speed on the meanings of everything.
I have an AT&T (evita) HOX. Its on 1.8.5 stock, and is rooted. I also set supercid some time ago, in preparation for unlocking it. I didn't proceed with the unlock at that time because I wasn't yet comfortable that everything I wanted backed up was backed up, and everything said unlock would wipe all user data.
I believe I have backup under control now, and I'd like to get to where I can put the "Scottsroms" rooted JB on, and do whatever I need to ensure that I can keep root. I want to stay as close to stock as possible, but with root, and that seems to be the best path for that.
I've been doing a bit of reading (including stuff linked from the rollup thread) and I have some questions I haven't been able to answer.
- Do I need to unlock the BL in order to get S-off? Or, if I S-off, do I not need to unlock the bootloader?
- I see the note about htc blocking supercid unlocking and using all 2's instead - is this still valid?
- I had read CWM didn't support this phone, but now I see something that contradicts that.
Basically, while I understand that there are no guarantees, I'd like to at least avoid doing things that are KNOWN not to work.
FWIW, I am a long time linux user. I have the Android sdk installed with adb and fastboot programs... I'm very comfortable at the command line.
If anyone can suggest what the recommended procedure is, which steps I need, which I should avoid, which info is current, which is out of date, I'd be very thankful.
If more info from me is needed, just let me know...
Click to expand...
Click to collapse
Finish unlocking bootloader
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Backup your current Rom via recovery.
Copy Rom of choice to sd card
Wipe everything except sd card. Wipe cache,dalvik, system, factory reset.
Flash Rom.
If you are on hboot 1.14 or higher you will need to extract boot.img from Rom.zip and flash via fastboot, flash boot boot.img
Good luck
Sent from my HTC One X using xda app-developers app

31ken31 said:
Finish unlocking bootloader
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Backup your current Rom via recovery.
Copy Rom of choice to sd card
Wipe everything but sd card, cache,dalvik, system, factory reset.
Flash Rom. If you are on hboot 1.14 or higher you will need to extract boot.img from Rom.zip and flash via fastboot, flash boot boot.img
Good luck
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Regarding unlocking - can I do it with supercid set, or do I need to change to all 2's ?
Should I do s-off?
I'm on whatever versions of everything are stock for a device shipped with 1.85 - ok, the bootloader screen says hboot is 1.09.0000
I'll search around but are there docs on the specific steps for flashing roms?
BTW, thanks for the quick reply...

Hit install from recovery pick Rom and flash.. don't worry about s-off being on hboot 1.09 u can flash whatever from recovery. Htcdev has 1111111 blocked I think if it is use all 2's
Sent from my HTC One X using xda app-developers app

FWIW supercid seemed to work for unlock just fine...

31ken31 said:
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Click to expand...
Click to collapse
Ok, looking for a bit of an expansion on this, and possibly some second opinions?
Looks like TWRP is up to 2.5.0.0 now, and the changelog shows a number of bugfixes since 2.3.x
Goomanager puts 2.5.0.0 on by default, I installed ROM Manager and it puts CWM..
The rollup page on the HOX says CWM officially supports it now..
The ROM I want says CWM "not supported" - I'm wondering if that is a holdover from when CWM didnt support HOX..

Megadave123 said:
Ok, looking for a bit of an expansion on this, and possibly some second opinions?
Looks like TWRP is up to 2.5.0.0 now, and the changelog shows a number of bugfixes since 2.3.x
Goomanager puts 2.5.0.0 on by default, I installed ROM Manager and it puts CWM..
The rollup page on the HOX says CWM officially supports it now..
The ROM I want says CWM "not supported" - I'm wondering if that is a holdover from when CWM didnt support HOX..
Click to expand...
Click to collapse
It's says bugs fixed but it's not fixed.. I don't recommend cwm for this device. Go to twrp website and download 2.3.3.1 and flash it
Sent from my HTC One X using xda app-developers app

[Q] KGS1992 Utility error

This post should be inside of this thread, but I do not have 10 posts so I cannot post in the Dev forum
I own a Sensation (4G) and achieved S-OFF with HTCDev and Juopunutbear wire method. I then installed KGS1992 Utility to my desktop (wasn't working when installed in Program Files) and made sure all other windows were closed. I successfully used the utility to install 4EXT recovery. I then tried to Root and this is what happened [screenshot attached]:
On my phone it opens the recovery, opens another program (rooting tools by mike1986), and reboots my phone to the normal screen. I then hit [Enter] because the installation looked complete. The KGS1992 utility prompted me again if I'm sure the installation was completed. I hit [Enter] again but received the error:
"goto was unexpected at this time"
Am I good to go? It seems as though the installation was complete. I haven't closed the command prompt window, and haven't disconnected my phone since the incident. Any help is appreciated. Thank you.
EDIT:
Just checked with a root checker app on the marketplace and it says that I do not have root.

Hi
What do you intend to do with your phone? If you want to install a custom ROM, then forget about rooting. You have s-off plus 4ext recovery; and custom ROMs are normally pre-rooted.
Otherwise, try simply rooting your stock ROM with ERoot, a program for windows.
Sent from whatever isn't something to be locked at, the thing is that it is sent.

ashkan-khatar said:
Hi
What do you intend to do with your phone? If you want to install a custom ROM, then forget about rooting. You have s-off plus 4ext recovery; and custom ROMs are normally pre-rooted.
Otherwise, try simply rooting your stock ROM with ERoot, a program for windows.
Click to expand...
Click to collapse
I am very new to rooting, but I've been reading threads for a while now trying to understand. And yeah, I would like to install a custom ROM.
Thank you for the help, I am fairly sure I understand now. Is my understanding right that I can go into 4EXT, make a backup of my current factory ROM, download a custom ROM, and replace factory with custom. If this is right, I'll browse for which custom ROM I want now I dislike the factory bloat.

gpops said:
I am very new to rooting, but I've been reading threads for a while now trying to understand. And yeah, I would like to install a custom ROM.
Thank you for the help, I am fairly sure I understand now. Is my understanding right that I can go into 4EXT, make a backup of my current factory ROM, download a custom ROM, and replace factory with custom. If this is right, I'll browse for which custom ROM I want now I dislike the factory bloat.
Click to expand...
Click to collapse
Yeah, that's exactly the way.
Sent from whatever isn't something to be locked at, the thing is that it is sent.

[Q] Stock Recovery

Hi all,
I apologize if this has been answered before, but I had trouble finding it here. I am currently rooted on a stock backup, but I am running a custom recovery. I am not sure where to find the stock recovery image for my device. I am using the HTC One M8 through Verizon, and I know that the new firmware update is coming out soon, and I'd like to be able to just OTA update my phone so that I can reflash a custom recovery and install the newest VenomROM. I have flashed a custom recovery before (obviously), but I didn't know if it mattered which firmware base you are running. I read somewhere that the recovery is totally separate from the OS, and it is meant to be an alternative to booting into the OS in case of a problem, but I want to be sure. If there is a specific recovery I need to use and someone here knows where I can find it, that'd be great. I found the collection of stock recoveries, but I'm having trouble figuring out which one I need to use. Any and all help is appreciated, thanks.
EDIT: My CID is VZW__001
My VERSION-MAIN is nothing. There's is just nothing next to this label.
I tried locating it on the collection of stock recoveries, but couldn't find it. I'm not sure why this is.

It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....

hgoldner said:
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Hi there,
I actually just used the psuedo RUU tool (I assume this is the one you are talking about? http://forum.xda-developers.com/showthread.php?t=2727831)
I just finished using this tool, but when I went to check the recovery, all I get is a big red triangle with an exclamation point in the middle. Nothing else. So, I'm guessing that recovery didn't flash properly? But I'm honestly not completely sure. I would screenshot it, but I can't do that. Any help is appreciated.
EDIT: I found out that pressing volume up and power gives more options. I assume I am all good to go now? I am still rooted, and I'm not sure if that is a problem. I am stock, s-off and rooted, but I don't have any mods installed.

You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....

hgoldner said:
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.

ChuckFinley1992 said:
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
Click to expand...
Click to collapse
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.

hgoldner said:
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?

ChuckFinley1992 said:
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
Click to expand...
Click to collapse
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.

hgoldner said:
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
Click to expand...
Click to collapse
Okay, I may look into that. I've only seen an RUU flashed via hboot, so I'd have to look into it. At the very least though, I'd imagine someone will post the instructions on how to flash the firmware when it comes out.
Thanks so much for your help!

hgoldner said:
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
+100 for this!
I am reading dozens of posts in all kinds of threads of people just dying to take that OTA...
Why???
I would not touch that new firmware with a 100 foot pole until the devs have figured out what it breaks!!!
I predict a flood of posts in the line of:
"I flashed back to stock to take the OTA and now weaksauce is not working - how do I get root back?"
What's the hurry?????

What should I do after Sunshine?

So I just upgraded from an iphone, this is my first android. Obviously I want to get rid of the Verizon crap... but what else should I do? And how? What's the first thing I do after Sunshine? And what do you recommend I do?

Read. Read more. And even more. Seriously.
Congrats on throwing off the i-Shackles!!
But if this is your first Android device you have a steep learning curve ahead of you.
If you ran Sunshine successfully you are now S-off, allowing you to truly and irreversibly brick your phone if you go about customizing it to your liking the wrong way.
Read a lot, use the serach function here on XDA and Google in general with abandon! Ask if you diligently searched for hours but cannot find an answer.
Flash only if you really understand what you are getting yourself into.
Always make backups before you try something new and research how to reverse what you are about to do!
Here are a few terms for you start with:
What is:
fastboot, fastboot tutorial
ADB (Android Debug Bridge), basic adb commands
recovery, custom recovery, TWRP recovery
"root" in Android, SuperSU, how to obtain it and what to do with it
Hboot
RUU
custom rom - peruse the Development section here for a plethora of them, read at least the OP of each very carefully
That should keep you busy for a week or so
Have fun

berndblb said:
Read. Read more. And even more. Seriously.
Congrats on throwing off the i-Shackles!!
But if this is your first Android device you have a steep learning curve ahead of you.
If you ran Sunshine successfully you are now S-off, allowing you to truly and irreversibly brick your phone if you go about customizing it to your liking the wrong way.
Read a lot, use the serach function here on XDA and Google in general with abandon! Ask if you diligently searched for hours but cannot find an answer.
Flash only if you really understand what you are getting yourself into.
Always make backups before you try something new and research how to reverse what you are about to do!
Here are a few terms for you start with:
What is:
fastboot, fastboot tutorial
ADB (Android Debug Bridge), basic adb commands
recovery, custom recovery, TWRP recovery
"root" in Android, SuperSU, how to obtain it and what to do with it
Hboot
RUU
custom rom - peruse the Development section here for a plethora of them, read at least the OP of each very carefully
That should keep you busy for a week or so
Have fun
Click to expand...
Click to collapse
Thanks! I've done enough poking around to see most of these terms before. I gather I can't do anything after Sunshine without SuperSU, and that TWRP is the next step. Is that right?
1. Sunshine
2. SuperSU
3. TWRP
?

nogginhead said:
Thanks! I've done enough poking around to see most of these terms before. I gather I can't do anything after Sunshine without SuperSU, and that TWRP is the next step. Is that right?
1. Sunshine
2. SuperSU
3. TWRP
?
Click to expand...
Click to collapse
With S-OFF and an unlocked boot loader the first step for root would be to flash TWRP recovery via fastboot on your PC. Navagate your way on the phone to boot twrp. After that you can flash superSU. With root you can permanatly uninstall all vzw apps via an app like titanium backup. If you want to go a step further you could flash Clean Rom(pre debloated ROM).
At some point soon your phone will get a OTA(over the air) update if you have twrp installed on your phone you won't be able to update. You will need to backup in twrp. factory RUU your phone(100% back to stock) keep your bootloader unlocked and S-OFF. Take the OTA, flash TWRP, restore your backup..profit! Its a good idea to make a backup in TWRP right when you install it TWRP(that way you have the option to flash the stock recovery and take the OTA)You can't have a modified system when taking an OTA.
Make sure any backup you make is saved on something other than the phone storage. You could lose everything.

PioneerMonster said:
With S-OFF and an unlocked boot loader the first step for root would be to flash TWRP recovery via fastboot on your PC. Navagate your way on the phone to boot twrp. After that you can flash superSU. With root you can permanatly uninstall all vzw apps via an app like titanium backup. If you want to go a step further you could flash Clean Rom(pre debloated ROM).
At some point soon your phone will get a OTA(over the air) update if you have twrp installed on your phone you won't be able to update. You will need to backup in twrp. factory RUU your phone(100% back to stock) keep your bootloader unlocked and S-OFF. Take the OTA, flash TWRP, restore your backup..profit! Its a good idea to make a backup in TWRP right when you install it TWRP(that way you have the option to flash the stock recovery and take the OTA)You can't have a modified system when taking an OTA.
Make sure any backup you make is saved on something other than the phone storage. You could lose everything.
Click to expand...
Click to collapse
Perfect for me, many thanks! So:
1. Sunshine
2. TWRP (and make a backup)
3. superSU
4. Titanium backup to get rid of VZW crap.
5. What apps currently unavailable to me am I sure to want? xprivacy? (I'll skip the ROMs for now, I think.)

nogginhead said:
Thanks! I've done enough poking around to see most of these terms before. I gather I can't do anything after Sunshine without SuperSU, and that TWRP is the next step. Is that right?
1. Sunshine
2. SuperSU
3. TWRP
?
Click to expand...
Click to collapse
well, with the Sunshine method you are S-OFF which stands for Security Off - AKA Unlocked bootloader.
You can actually control you entire device now that you are sunshine S-OFF. Anything you want - which for new people to HTC and S-OFF can be a disaster. Please make sure to follow everything to a T for instructions as with S-OFF it removes the blocking of things that aren't suppose to be flashed on the phone. With S-ON you can't flash say, an HTC One X Hboot on an HTC One M8, however with S-OFF you can, so be VERY careful and make sure that whatever you flash is 110% for the device you have, and that you check the MD5-checksum.
SuperSU is root. S-OFF = permanent root.
so since you are sunshine S-OFF you can just install the SuperSU and now you have a stock rooted ROM.(I suggest making a nandroid before editing the stock ROM).
If you want to go ahead and mess around with flashing of ROMs, then you would need to flash a custom recovery (I also suggest TWRP)
command is fastboot flash recovery name-of-recovery.img
hope this is helpful.