Well for people who had a brick caused by VISIONary that was fixed by flashing the leaked Gingerbread update, I think I have an idea that might work on rooting it.
Why not replace the stock bootloader and recoveries that come in the PC10IMG.zip file with Clockworkmod recovery and the Engineering SPL. That way you can have S-OFF, which allows you to use to use Gingerbreak to root and CWM recovery which allows you to flash a different ROM on the G2.
Does this make sense, or did someone already try this and failed? I got the idea from the method I used to root my G1.
teh5abiking said:
Well for people who had a brick caused by VISIONary that was fixed by flashing the leaked Gingerbread update, I think I have an idea that might work on rooting it.
Why not replace the stock bootloader and recoveries with Clockworkmod recovery and the Engineering SPL. That way you can have S-OFF, which allows you to use to use Gingerbreak to root and CWM recovery which allows you to flash a different ROM on the G2.
Does this make sense, or did someone already try this and failed? I got the idea from the method I used to root my G1.
Click to expand...
Click to collapse
Best bet to find out if this would work or not is to ask the guys over at #G2ROOT irc.
And this doesn't really belong in the dev section, should be in Q&A
CRAP!!! I hit the wrong link! Sorry, moving my post.
And where's the link to the #G2ROOT IRC channel?
If I'm not mistaken, there's no way to get thoes items on the phone as the package won't pass signatue validation.
If we had thoes items, then we wouldn't need to root the leak rom, we could simply bypass it by flashing a new pre-rooted rom..
Perhaps you misunderstood how the process works?
Sent from my HTC Vision using XDA Premium App
teh5abiking said:
CRAP!!! I hit the wrong link! Sorry, moving my post.
And where's the link to the #G2ROOT IRC channel?
Click to expand...
Click to collapse
Can't provide a link, just use your preferred IRC client
wilnotdie said:
If I'm not mistaken, there's no way to get thoes items on the phone as the package won't pass signatue validation.
If we had thoes items, then we wouldn't need to root the leak rom, we could simply bypass it by flashing a new pre-rooted rom..
Perhaps you misunderstood how the process works?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
perhaps i have, but what exactly is hindering the problem? did htc patch the hole in the firmware that allowed scotty2 to powercycle the eMMC chip?
Do u know what an md5 sum is? If anything is modified, even ONE BYTE, the sum changes. That is how u know if a file is corrupted/tampered. Signature verification is the same thing different name. The fact that you can't change the recovery because its not rooted means that you cannot bypass the sig verification. End of story. This idea will never work.
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
Do u know what an md5 sum is? If anything is modified, even ONE BYTE, the sum changes. That is how u know if a file is corrupted/tampered. Signature verification is the same thing different name. The fact that you can't change the recovery because its not rooted means that you cannot bypass the sig verification. End of story. This idea will never work.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
ouch. . .
no need to be harsh.
xsteven77x said:
Do u know what an md5 sum is? If anything is modified, even ONE BYTE, the sum changes. That is how u know if a file is corrupted/tampered. Signature verification is the same thing different name. The fact that you can't change the recovery because its not rooted means that you cannot bypass the sig verification. End of story. This idea will never work.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Signature verification is not the "same thing different name" -- look up public key cryptography for more information.
teh5abiking said:
perhaps i have, but what exactly is hindering the problem? did htc patch the hole in the firmware that allowed scotty2 to powercycle the eMMC chip?
Click to expand...
Click to collapse
Pretty much yes. I don't remember the exact details....but it was the hole that allowed temp root, which than allowed us to modify the hboot. Giving us s-off, in turn allowing us full access...I think you get the picture.
Or someone please correct me if I'm wrong. Its been a long time since thoes days
Sent from my HTC Vision using XDA Premium App
You seek Irc.Freenode.net, #G2Root. While you're at it, drop into #Msid and #cyanogenmod ;-)
Sent via Tapatalk on CyanogenMod 7.1.0-RC1 on Vision
Related
Okay so im willing to bet that this has already been covered but im new here.
What if, in theory, it was possible to create a higher hboot version than 1.49 and put it into a ROM. Would it require signing? and would that even be possible?
I tried putting the v3 leak hboot file into the OTA update.zip and it failed the verification test.
But any ideas?
You answered your own question, it wont pass verification.
Okay..
but would it be possible to create a higher version than 1.49 and put it into a file?
I'm guessing no (i dont know for sure) but as far as I know the devs tried everything they could think of and I remember them talking about replacing hboot but it failing.
I sadly dont see root at the end of the tunnel for leakers.
Yeah i figured they probably tried something like that already. oh well, maybe that exploit will pull through
It is not possible for us to replace/update the HBOOT version because we could not resign the file for it to pass verification.
Is there another device with a higher hboot version than our own that has been rooted? If so could we install that hboot on our device
-------------------------------------
Sent via the XDA Tapatalk App
ahjee said:
Is there another device with a higher hboot version than our own that has been rooted? If so could we install that hboot on our device
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
This doesn't work that way.
It would have to be a signed image, for the eris, with an engineering bootloader.
or
A root exploit.
Makes sense, im still new to all this. I more or less lurk and wait to enjoy fruits of your labor. I Should just keep quiet like i have Nd let you ill developers work your magic.
Excited in this exploit though, i read about it but am not savvy enough to contribute, good luck to those working on it and much appreciated no matter the turn out
-------------------------------------
Sent via the XDA Tapatalk App
No need to stay quiet. Asking questions is how you learn and who knows...you may just spit something out that noone else has really thought of...
Good to see a positive vibe.
So how are these packages signed.....any chance of signiong up to be a developer with google and maybe being able to sign them ourselves?
ssgtob1 said:
So how are these packages signed.....any chance of signiong up to be a developer with google and maybe being able to sign them ourselves?
Click to expand...
Click to collapse
They are signed using RSA and an SHA1 hash to ensure validity. So we can sign up to be a developer but that doesn't get us either of HTC's keys.
Has anyone experimented with MM yet? I have seen quite a few themes and addons for other handhelds... most have stuff with MetaMorph. We have a growing community, shame there aren't themers out there!
Sent from my Liberty using XDA App
I can never get the initial setup to finish. Always says not enough system space to extract files or something. Happens with liberated or cm6.
Sent from my HTC Liberty using XDA App
Has anyone else experimented with MM?
Sent from my Liberty using XDA App
I believe metamorph tries to write to the system partition, which won't work without an S-OFF (security off) SPL. The Aria SPL is S-ON.
attn1 said:
I believe metamorph tries to write to the system partition, which won't work without an S-OFF (security off) SPL. The Aria SPL is S-ON.
Click to expand...
Click to collapse
Well turn it S-OFF!
kaschenberg said:
Well turn it S-OFF!
Click to expand...
Click to collapse
How you do that?!?!
Sent from my Aria usung XDA android app. (Good stuff)
I do all my editing by hand... safer that way, then you know exactly what's happening. You could also create your own zip file with modified textures/images/etc, make it flashable, and then sign it and you wouldn't have to worry about MM.
I've worked on this a few weeks ago with Attn1. It would be better to talk with Metamorph's dev(s) or getting a different SPL, which there is none at the moment. It seems we will need to find a work around allowing us to write to the system partition.
ioft said:
I do all my editing by hand... safer that way, then you know exactly what's happening. You could also create your own zip file with modified textures/images/etc, make it flashable, and then sign it and you wouldn't have to worry about MM.
Click to expand...
Click to collapse
I agree, if we can get the dev(s) to create a version that's can be installed from recovery it could work. However I'm no dev and have no knowlegde of the inner works but it sounds good.
I was thinking of flashing a new radio to my phone,I do have s-off,running cm 7.0 . I know you can flash a radio through adb,but I don't have a computer. Which leads me to why Im writing this topic.
Sent from my HTC Glacier using XDA Premium App
Edit:Got it working.
Mr.Highway said:
I was thinking of flashing a new radio to my phone,I do have s-off,running cm 7.0 . I know you can flash a radio through adb,but I don't have a computer. Which leads me to why Im writing this topic.
Click to expand...
Click to collapse
Did you read the radio thread? You don't flash radios through ADB. They're flashed in the bootloader, so you don't need a computer for anything. The instructions say to verify the MD5 checksum with ADB, but you can just as easily do that with an app like ManD5. And no, since the radio files in that thread are not "flashable", you cannot flash them in recovery.
What radios are able to flash,that will give better connection. Not trying to be a noob,kinda hard to type with two semi-broken wrists
Sent from my HTC Glacier using XDA Premium App
Mr.Highway said:
What radios are able to flash,that will give better connection. Not trying to be a noob,kinda hard to type with two semi-broken wrists
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
No one can be sure, you have to try it for yourself. Results vary by location. Person A may get astounding results with a GB radio, while person B may get ****ty results with the same radio.
Alright, what radios are flashable. Btw nice roms
Sent from my HTC Glacier using XDA Premium App
GazaIan said:
No one can be sure, you have to try it for yourself. Results vary by location. Person A may get astounding results with a GB radio, while person B may get ****ty results with the same radio.
Click to expand...
Click to collapse
Alright,what' radios are flashable. Btw nice roms
Sent from my HTC Glacier using XDA Premium App
Mr.Highway said:
Alright,what' radios are flashable. Btw nice roms
Click to expand...
Click to collapse
What are you talking about? All four are valid, working radios...
Do I need to change the file name to the pd15(not sure if that's the correct one)
Sent from my HTC Glacier using XDA Premium App
Mr.Highway said:
Do I need to change the file name to the pd15(not sure if that's the correct one)
Click to expand...
Click to collapse
Just follow the guide in the radio thread. The files do have to be named exactly PD15IMG.zip, but they come that way when downloaded, so there is nothing to change.
So I just download them,go into the bootloader,an let it run it. I just want to make sure on this.
Sent from my HTC Glacier using XDA Premium App
Mr.Highway said:
So I just download them,go into the bootloader,an let it run it. I just want to make sure on this.
Click to expand...
Click to collapse
Essentially, but never flash a radio without verifying the MD5 after downloading. That's VERY important.
TeeJay3800 said:
Essentially, but never flash a radio without verifying the MD5 after downloading. That's VERY important.
Click to expand...
Click to collapse
Thanks, I just wanted to get more info on it before I decide on it,its the way I am. Ill give it a shot,hopefully everything goes well. Btw I just downloaded a md5 checker
Sent from my HTC Glacier using XDA Premium App
Mr.Highway said:
Thanks, I just wanted to get more info on it before I decide on it,its the way I am. Ill give it a shot,hopefully everything goes well. Btw I just downloaded a md5 checker
Click to expand...
Click to collapse
I hear you. As long as the MD5 matches up, there isn't much risk of anything bad happening. It's as simple as moving the file to the root of your SD and booting into the bootloader. Good luck.
TeeJay3800 said:
I hear you. As long as the MD5 matches up, there isn't much risk of anything bad happening. It's as simple as moving the file to the root of your SD and booting into the bootloader. Good luck.
Click to expand...
Click to collapse
Well I just flashed a new radio,I'm still alive,the world is an so is my phone. I was sketched out the entire time till I got to writing this. Thank you so much for your help. God I love XDA.
Sent from my HTC Glacier using XDA Premium App
TeeJay3800 said:
Essentially, but never flash a radio without verifying the MD5 after downloading. That's VERY important.
Click to expand...
Click to collapse
what exactly does it mean to verify the MD5. i was over at the radio thread, but some of the English isn't clear at some points and I don't know if they are crucial or not.
Its the serial number of the file, if it changes, you will brink your phone when you flash it
Sent from my HTC Glacier using XDA Premium App
milestide25 said:
what exactly does it mean to verify the MD5. i was over at the radio thread, but some of the English isn't clear at some points and I don't know if they are crucial or not.
Click to expand...
Click to collapse
In the posts with each download for the Radios (and sometimes ROMs), you will see something that says "md5sum". In layman terms, its basically a confirmation number to make sure the file you downloaded is the exact same one that was originally posted. It's a safety measure to make sure you didn't get a bad download and then tried to flash a defective file onto your phone.
To verify it you can just download the app call "ManD5" and have it scan the file in question after you put it in your sdcard. It'll read the file and give you an MD5 number for you to compare with the one in the post you downloaded from. If the two match, you're safe.
If they don't match though, DO NOT FLASH THE FILE. IT COULD BRICK YOUR PHONE. Re-download it and check the md5 again. It's just a good safety practice when messing with things that could potentially destroy your expensive electronics.
PLEASE COULD ANY BODY TELL ME HOW TO UN-ROOT MY EVO FROM GINGER BREAD?
VANDOME said:
PLEASE COULD ANY BODY TELL ME HOW TO UN-ROOT MY EVO FROM GINGER BREAD?
Click to expand...
Click to collapse
MAKE SURE YOU BACKUP ANY USEFUL INFORMATION OR APPS FROM YOUR PHONE, BECAUSE YOUR ROM IS GOING TO BE WIPED.
First download the attachment. Remove the numbers from the name of the file so that it is renamed PC36IMG and place this on the root of your SD card. Power off the phone, then boot into your bootloader by holding the volume down and power buttons at the same time. Accept the update. If everything went OK, that should get rid of that Revolutionary at the top of your bootloader and flash the phone back to S-ON.
Next remove the file from your SD card by either rebooting your phone or going into your RECOVERY. I'm not going to give all the details for this.
Next, download this file.
http://www.megaupload.com/?d=VSFLE9CD
Rename it PC36IMG, place it on your SD card and follow the same steps as you did with the first PC36IMG file.
Let me know if that worked, because how to unroot the phone has seemed to be forgotten around here. Everyone is just happy to root.
http://forum.xda-developers.com/showthread.php?t=780141
That took me 5 seconds to find with a quick search.
sitlet said:
http://forum.xda-developers.com/showthread.php?t=780141
That took me 5 seconds to find with a quick search.
Click to expand...
Click to collapse
That doesn't work completely for Gingerbread.
You can downgrade the ROM back to Froyo, but the S-ON tool will not work with the new bootloader, and the bootloader will not downgrade by running any of the PC36IMG Froyo files or RUUs if Revolutionary was used to turn S-OFF.
Assuming that you mean to unroot and regain S-OFF on an Evo 4G that was rooted using Revolutionary...
It seems that this has been worked out.
Check out this post.
m20120 said:
Assuming that you mean to unroot and regain S-OFF on an Evo 4G that was rooted using Revolutionary...
It seems that this has been worked out.
Check out this post.
Click to expand...
Click to collapse
Same thing that I posted, just thought I'd make it a little less detailed.
shortydoggg said:
Same thing that I posted, just thought I'd make it a little less detailed.
Click to expand...
Click to collapse
Good idea.
Maybe someone can create a guide, to put this question to rest? (I mean, since we finally have a working solution)
Captain_Throwback said:
Good idea.
Maybe someone can create a guide, to put this question to rest? (I mean, since we finally have a working solution)
Click to expand...
Click to collapse
Oh by the way, thanks for the S-ON solution Captain. I thought of your idea about a week ago with the bootloader, and have a hex editor, but did not think it all the way through at the time.
this worked great but one prob. now when i try to re root with revolutionary it says im already s off but on bootloader im not. wassup with that?
EarnyBaller said:
this worked great but one prob. now when i try to re root with revolutionary it says im already s off but on bootloader im not. wassup with that?
Click to expand...
Click to collapse
if ur s-off then you are rooted. flash a recovery.
That's my issue. Revolutionary says I'm s off but on my bootloader it says s on
Sent from my PC36100 using XDA App
EarnyBaller said:
That's my issue. Revolutionary says I'm s off but on my bootloader it says s on
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
OK so try and flash a recovery to check for sure. Maybe the hex edit fix may only be visual..... give it a shot man....go for it
Sent from my Xoom using xda premium
I tried flashing cwm and anon ra yesterday as pc36img's but no luck . I'm just gonna try to partition my SD card and hard reset . Hopefully itll work then
Sent from my PC36100 using XDA App
EarnyBaller said:
That's my issue. Revolutionary says I'm s off but on my bootloader it says s on
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You need to flash an unrooted stock ROM to roll back your HBOOT to an upgradable version. I assume you used the modded 6.17 HBOOT to S-ON, but didn't flash a stock ROM to restore your HBOOT to stock?
Because the modded HBOOT is a higher version number than Revolutionary, most likely it believes you're already rooted.
I used RUU to update my phone to latest stock Rom and flashed the attachment on this thread
http://forum.xda-developers.com/showthread.php?p=17501533 . But i do believe you're right sir and ill be trying this as soon as I get home
Sent from my PC36100 using XDA App
Which Rom/version do you reccommend
Sent from my PC36100 using XDA App
EarnyBaller said:
Which Rom/version do you reccommend
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You essentially have two options:
- Run the RUU (ROM Update Utility) for the latest stock ROM on your PC
- Flash the latest stock ROM, in PC36IMG.zip format through FastBoot
Files for either/both of those can be found in my post here: http://forum.xda-developers.com/showpost.php?p=17206283&postcount=5
"I hope you brought an umbrella, 'cause it's raining cold hard facts up in here."
Ahh thanks so much you're a lifesaver. And do I download the hboot in your link or just flash Rom
Sent from my PC36100 using XDA App
EarnyBaller said:
Ahh thanks so much you're a lifesaver. And do I download the hboot in your link or just flash Rom
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just flash the ROM. That should restore your HBOOT to 2.16, which is rootable with Revolutionary.
root acquired! you sir are the ****ing man lol
Now you can download the latest stock Android 4.4 KitKat with Sense 5.5 RUU.exe files on:
http://androidruu.com/?developer=M7
Greetz
There's already a specific thread for M7 RUU's.
http://forum.xda-developers.com/showthread.php?t=2428276
herwegan said:
There's already a specific thread for M7 RUU's.
http://forum.xda-developers.com/showthread.php?t=2428276
Click to expand...
Click to collapse
But there are no Android 4.4 KitKat RUU.exe files on.
i've already told it crushalot, i'm sure he'll add them asap. further i've already provided the link you offer here in his thread, so no reason for another RUU thread
I have send them a message to about a week ago but there is no respons.
Sent from my HTC One using xda app-developers app
Justin2003 said:
I have send them a message to about a week ago but there is no respons.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the link man. Some people get way to butt-hurt around here lol.
Sent from my HTC One using xda app-developers app
Thanks for link noticed that there is a ruu.exe for O2 UK do I still need to down grade hboot to use the .exe
You do not have to downgrade the hboot.
Sent from my HTC One using xda app-developers app
Justin2003 said:
I have send them a message to about a week ago but there is no respons.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
troby86 said:
Thanks for the link man. Some people get way to butt-hurt around here lol.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
lol man, it's not that i want to steal his "thanks" or something. i just think it's better to keep the forum clean and keep the equal stuff together in one thread, so it's better to find for everyone. and if there's already a specific and usualy well maintained thread for this topic. so i think it's best to just post the link there (@justin2003) and not open up a new thread (just to get attention/thanks or whatever the reason was).
people that are looking out for 4.19 RUUs will search in the RUU thread and find the link and thank you. and as soon as crushalot has some time to add it, he'll do it. that's it.
Until the RUU thread gets updated, this thread is fine.
I'm a little concerned with the community spirit shown here. @Justin2003 has done nothing wrong, by posting this, he even stated that he PM'd @crushalot but with no response.
..(just to get attention/thanks or whatever the reason was)..
Click to expand...
Click to collapse
This is a little concerning, just because someone posts something doesn't mean they're hunting for thanks (which are worthless, just look at mine ) or attention (this is the internet, who cares ).
Save the hate for the iPhone crowd.
Andy said:
Until the RUU thread gets updated, this thread is fine.
I'm a little concerned with the community spirit shown here. @Justin2003 has done nothing wrong, by posting this, he even stated that he PM'd @crushalot but with no response.
This is a little concerning, just because someone posts something doesn't mean they're hunting for thanks (which are worthless, just look at mine ) or attention (this is the internet, who cares ).
Save the hate for the iPhone crowd.
Click to expand...
Click to collapse
Nothing to be concerned about! i just thought to do the right thing by indicating to keep the forum clean based on my own experiences with thread openings.. not all mods think the way you do but nvm, let's stop here.
Cheers
herwegan said:
lol man, it's not that i want to steal his "thanks" or something. i just think it's better to keep the forum clean and keep the equal stuff together in one thread, so it's better to find for everyone. and if there's already a specific and usualy well maintained thread for this topic. so i think it's best to just post the link there (@justin2003) and not open up a new thread (just to get attention/thanks or whatever the reason was).
people that are looking out for 4.19 RUUs will search in the RUU thread and find the link and thank you. and as soon as crushalot has some time to add it, he'll do it. that's it.
Click to expand...
Click to collapse
Look at Bugsy Lawsons RUU thread...all download links are removed. I think, the thread can also be removed. It´s better to have one more chance for a download, if something like this happens again.
Sorry everyone, I can't dedicate nearly as much time to the threads I used too due to a new demanding job with no access to post during the day and more family duties in the evening.
I will work on downloading the updated RUU files and get them posted on my site and on the collection thread I started.
I am not purposely trying to ignore anyone, but I get at least 20 support request emails and 5-6 PM's per day and as I stated I just don't have the time to answer them all.
Thanks to Justin2003 for creating the thread with the links.
I do not need attentions or thanks but i know that there are a lot of people who wants back to stock without first s-off the phone to downgrade the hboot.
Sent from my HTC One using xda app-developers app
Thank you Justin, the official RUU helped me restoring the device in pseudo original state (still unlocked, with supercid and S-off ofcouse) but without having to mess with reconstructed, dumped and/or skeletonized ROMs.
Sorry for the noobish question but after reading through the myriad of "Help Me!" threads, I've gotten a bit confused on what can/can't be used with all the different security & lock states. If I'm S-OFF w/ unlocked bootloader, can I run the ruu.exe? Or am I better off waiting for a decrypted ruu.zip?
As far as I understand it, I believe I can pretty much run anything w/ S-OFF and it's up to me to make sure that what I run is compatible with my device, lest I risk bricking it. Is that an accurate assessment? Are there any avenues to restore that cannot or should not be used while S-OFF? Are there any that would require relocking the bootloader while S-OFF?
Sent from my HTC One using xda app-developers app
sharksfan7 said:
Sorry for the noobish question but after reading through the myriad of "Help Me!" threads, I've gotten a bit confused on what can/can't be used with all the different security & lock states. If I'm S-OFF w/ unlocked bootloader, can I run the ruu.exe? Or am I better off waiting for a decrypted ruu.zip?
As far as I understand it, I believe I can pretty much run anything w/ S-OFF and it's up to me to make sure that what I run is compatible with my device, lest I risk bricking it. Is that an accurate assessment? Are there any avenues to restore that cannot or should not be used while S-OFF? Are there any that would require relocking the bootloader while S-OFF?
Click to expand...
Click to collapse
You understand correctly.
You can do anything. With great power comes great responsibility.
Occasionally an RUU won't work because your HBOOT is incompatible or your HTC drivers aren't current or your CID or MID is incompatible. Generally you can fix these things and try again.
The two most common things that brick phones are a failed HBOOT flash or trying to S-ON with a non-stock HBOOT.
Justin2003 said:
Now you can download the latest stock Android 4.4 KitKat with Sense 5.5 RUU.exe files on:
Click to expand...
Click to collapse
Thanks for this link.
(downloading right now)
Sorry for the noob question but I'm facing a bug with my HTC One running 4.3, so I want to try 4.4.2.
My phone is rooted/unlocked and I've installed CWM recovery. All of which I want to keep !!
OTA 4.4.2 update would not install due to CWM recovery.
Will this .exe file allow me tu upgrade to 4.4.2 without the need to remove CWM recovery and SuperUser ?
Thanks for your help here.
Sounds like what you want can be accomplished by either reverting to a stock recovery and accepting the OTA before putting CWM back, or just flashing a 4.4.2 ROM in your custom recovery- either way this discussion probably doesn't belong in this thread.
Note flashing Kit Kat manually requires a compatible recovery and S-OFF, I believe.
The OTA should preserve your settings and data.
You may or may not be able to keep your settings and data intact if you go the manual route.
If you do an RUU you *definitely* won't be able to keep data:
Real, complete, signed RUU's from HTC rewrite everything. The erase your pictures, they install a stock recovery, they touch every partition.
(There are some firmware-only and other hybrid packages posted various places in this forum that behave like RUU's but are more selective in which partitions are touched.)
Merely flashing a ROM only really touches /system (it also touches /boot and /cache technically). Depending on how stable the result is, you may also choose to erase /data in a separate action.
To clear up a point about terminology, root access is something that is usually baked into the ROM you are flashing. RUU always leaves you with a stock, unooted ROM. Flashing almost any custom ROM automatically gives you root as a side benefit. Root is not the same as S-OFF.
Anyway, you probably don't need an RUU unless you get into serious trouble. Until then, you might want to ask for more help over in Q&A...
Sent from my HTC One using xda app-developers app