Database Info

How To UN ROOT. TUTORIAL. Your Problems are solved!

UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....

Thanks op.

Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.

arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.

Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?

sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!

Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...

sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!

Well, worry even less! Special thanks to Calkulin!

thankssssss

Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop

I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...

I'm getting error 155 running Ava Froyo and trying to go back.

blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.

How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?

joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.

tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.

Yes. I have .79, thanks!
Sent from my PC36100 using XDA App

Help! Need to root updated 2.47.507.7

I got a new phone today from AT&T. I upgraded to the new ATT Gingerbread using their update button (I wasn't thinking). I like the stock rom...will probably keep it...but I need to be rooted so I can sideload! Help!
I tried Bubby's tool...it just said something about update version being older than what was currently in the system...so it wouldn't work for me! I'm about to try ace-hack-kit...hopefully that'll work for me!

gallogj said:
I got a new phone today from AT&T. I upgraded to the new ATT Gingerbread using their update button (I wasn't thinking). I like the stock rom...will probably keep it...but I need to be rooted so I can sideload! Help!
I tried Bubby's tool...it just said something about update version being older than what was currently in the system...so it wouldn't work for me! I'm about to try ace-hack-kit...hopefully that'll work for me!
Click to expand...
Click to collapse
I was able to root with attn1's hack kit just this morning with Gingerbread. btw. Sideloading is now "legal" unknown sources checkbox is in the stock GB rom.

Unknown sources
Strange...I didn't see unknown sources in the stock unrooted gb upgrade. I saw mock locations...but not unknown sources. Update...the Hack Kit seemed to work. Now I'm working on S-off.

gallogj said:
Strange...I didn't see unknown sources in the stock unrooted gb upgrade. I saw mock locations...but not unknown sources. Update...the Hack Kit seemed to work. Now I'm working on S-off.
Click to expand...
Click to collapse
its there...just under Applications.

Ya its in stock gingerbread I got it without root right under applications in settings

Just a little side note:
I flashed today the new Inspire ROM provided through the HTC site. There are 2 things I found.
1. If you flash over a custom ROM using the PC method (using file RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio _12.56.60.25_26.10.04.03_M_release_200368_signed hosted on HTC's site) you will go back to total stock, loosing all rooting ENG-OFF etc. You will have a plain ATT ROM. Even recovery will be reset to HTC. No CMR anymore. It might be good to know that you get full stock if you want to return your unit....
2. Good news is, the old method is still working except that the USB drivers act up. I got back to rooted by reinstalling HTC SYNC and leaving it on. ADB only worked for me (Windows 7 32bit) when phone was set to sync and not to "charge only".
Hope this helps somebody.

anjini said:
Just a little side note:
I flashed today the new Inspire ROM provided through the HTC site. There are 2 things I found.
1. If you flash over a custom ROM using the PC method (using file RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio _12.56.60.25_26.10.04.03_M_release_200368_signed hosted on HTC's site) you will go back to total stock, loosing all rooting ENG-OFF etc. You will have a plain ATT ROM. Even recovery will be reset to HTC. No CMR anymore. It might be good to know that you get full stock if you want to return your unit....
2. Good news is, the old method is still working except that the USB drivers act up. I got back to rooted by reinstalling HTC SYNC and leaving it on. ADB only worked for me (Windows 7 32bit) when phone was set to sync and not to "charge only".
Hope this helps somebody.
Click to expand...
Click to collapse
If you have ENG S-OFF, then that is strictly a function of the engineering HBOOT image and flashing a new HBOOT will clear it, but if you have Radio S-OFF (which is typical of most of the rooting methods available for Inspire/DHD) then flashing a new HBOOT (or any or all other images from an RUU) won't clear radio S-OFF.

T-Mobile Branded Desire S Rooting

Hi all
I just wanted to make this post to make sure I know the exact process before I go ahead with this. Let me give you a little background....
I got a T-Mobile branded Desire S about 8 months ago and left it completely stock, after a while had an OTA update and from then on had constant problems with not receiving txts etc. So I S-offed and rooted with the RevX website and manually updated the radio to the latest version I could find. This fixed all my problems and everything was fine for months but then one day the phone just froze and without reading up too much I just started pressing buttons to reset/pulled the battery etc and ended up killing the phone completely.
Fast forward to now and I've just got a replacement phone but it has the older software on again so I'm not receiving txt messages again. I guess I need to update the radio image again to sort it but was hoping someone could let me know the exact process.
I assume I should use the RevX website again to S-Off/root then install CWM and the updates but which order and which versions should I be installing? I want to get it right up to date with 3.3.5 and sense 3.0 but not one of the custom ROMs.
Really appreciate anyone who takes the time to answer so thanks in advance.

First of all, please post stuff like this in Q&A. Secondly alpharevx is outdated now. Use revolutionary to S-OFF.
But now I'm confused. Do you want to update the radio and then S-ON again and get the latest update, or install a stock rom?
Sent from my Desire S using xda premium

Well ideally I'd like to not need to do anything! but at the moment I don't receive txt messages so I need to get it working. I don't want to use custom roms anyway so just need to upgrade to the latest official version.
If I understand correctly from what I've read I should use revolutionary to s-off then a program to root the phone. Then I could install 4ext and then install one of the 3.3.5 versions that works on a s-off/rooted phone and then finally update the radio to the version that works with 3.3.5?

Been reading up a little more and I will be using revolutionary to s-off the phone but should I install the recovery that comes with that? I assume this is CWM? Can I then overwrite it with 4ext if I want to?

rlzzzz said:
Been reading up a little more and I will be using revolutionary to s-off the phone but should I install the recovery that comes with that? I assume this is CWM? Can I then overwrite it with 4ext if I want to?
Click to expand...
Click to collapse
Yes, you can.

Help with restoring back to stock???

Hey Guys!!!
I've been looking around for a straightforward tutorial on how to flash back to stock.
If anyone could point me to the right thread that would be helpful, I'd would just like to set everything back to normal since I need to send the phone back.
I just want to know what the process is, like 1. Relock Bootloader 2. Flash Stock T-Mobile ROM 3. Flash Stock Recovery, something to that effect, so if any of you can point me to the right direction that would be greatly appreciated.
Thanks in advance guys:fingers-crossed:
!!!!!!--UPDATE---!!!!!!!!
So it worked everyone like a charm, so much thanks to baseballfanz, jdizzle316, and Senzune
So here's the breakdown on what I did, and again !!! This is for TMOUS and I tested with the 1.84.531.2 software !!!!
1. Re-locked the bootloader
- You can use the All in one tool from http://forum.xda-developers.com/showthread.php?t=1604677
- Or boot into fastboot and enter fastboot oem lock
2. Reboot the phone, check everything is ok
- no need to go back to bootloader or recovery
3. Boot back into bootloader
4. Go into fastboot
5. Run TMOUS RUU, go through the process and then just let it run, don't touch anything
- I found it from this forum http://forum.xda-developers.com/showthread.php?t=1744177&page=3
- If anyone needs another dropbox link let me know
6. Once it's all set you'll be back in the bootloader and all you have to do is just reboot the phone
And again thanks everyone for the help :fingers-crossed::fingers-crossed:

Are you on stock but rooted ROM or a custom ROM?

baseballfanz said:
Are you on stock but rooted ROM or a custom ROM?
Click to expand...
Click to collapse
I'm on Trickdroid like you are it seems, so I think that's considered custom no?

Just lock the bootloader and run the T mobile RUU

Use the all in one root kit in order to lock your bootloader(this can be found in the development section)
Once you bootloader is locked, download the TMOUS RUU, also found in the development section. This is an exe file you run on your pc.
Boot your phone into bootloader, then choose fast boot. Attach your phone to the USB connected to your PC and then run the ruu and from then it will take your device to completely stock.
Sent from my EVO using xda app-developers app

jdizzle316 said:
Use the all in one root kit in order to lock your bootloader(this can be found in the development section)
Once you bootloader is locked, download the TMOUS RUU, also found in the development section. This is an exe file you run on your pc.
Boot your phone into bootloader, then choose fast boot. Attach your phone to the USB connected to your PC and then run the ruu and from then it will take your device to completely stock.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Ok great
Now not sure if either you or baseballfanz have read anything about this on the forums, but I've downloaded both:
- RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed
- RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed
Which one of these RUUs would allow for regular OTA updates, I'm not sure if either of you would know but I'm just curious
Thanks again guys for you help by the way:laugh::victory:

dbo87 said:
Ok great
Now not sure if either you or baseballfanz have read anything about this on the forums, but I've downloaded both:
- RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed
- RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed
Which one of these RUUs would allow for regular OTA updates, I'm not sure if either of you would know but I'm just curious
Thanks again guys for you help by the way:laugh::victory:
Click to expand...
Click to collapse
You need to check in your settings which one applies to your device - at least I hope that's the way to decide which one to use. I have an RUU downloaded myself, just incase I ever do decide to get a custom ROM (waiting for a JB one which actually works). I found the proper one by checking which one has the same Baseband version, which in the stock ROM is found under About > Software information > More.
Since you seem to be on a TMOUS version of the One S, I believe it to be highly likely the 1.84 one is the way to go, as most updated to that version, including custom ROMs. You'd have to check that at Software number, I believe, if that's not altered by the custom ROM.

Senzune said:
You need to check in your settings which one applies to your device - at least I hope that's the way to decide which one to use. I have an RUU downloaded myself, just incase I ever do decide to get a custom ROM (waiting for a JB one which actually works). I found the proper one by checking which one has the same Baseband version, which in the stock ROM is found under About > Software information > More.
Since you seem to be on a TMOUS version of the One S, I believe it to be highly likely the 1.84 one is the way to go, as most updated to that version, including custom ROMs. You'd have to check that at Software number, I believe, if that's not altered by the custom ROM.
Click to expand...
Click to collapse
Yeah, I think you're right my build number is 1.84.531.2 so I assuming that I have to use the 1.84RUU, we'll see what the others have to say, but I'll be sure to keep you all posted once I run through the process.

1.84 is the latest and has latest radio
1.53 was previous version

[Q] Bought a rooted phone by accident, in over my head

First android phone it's a AT&T One X, i'll be using it on the Bell network. Got a good deal on Kijiji and I didn't ask enough questions apparently, lol.
The phone is clearly not stock, took me several hours to piece that together. I get it, I'm a noob. I can tell it's running Cleanrom 4.5. I want to get it back to something close to stock. I plan to learn all about rooting/roms but I want to do it from a vanilla phone so that I get to actually do it myself.
I googled and found a tutorial (link). I deleted the 'su' file and superuser.apk. I followed the rest of the steps and it didn't seem to do anything, just rebooted back into cleanrom.
I kept googling and now I'm following this guide: http://forum.xda-developers.com/showthread.php?t=1859714
I guess i'm going to flash from an RUU now ? My CID is 11111111, so I've read that means I have superCID and any RUU will work. I want to get to JB eventually, so can I just flash direct to the Europe 3.14 JB from HTCRUU? Or go with one of the ICS versions?
Am I doing this right?

No no no!
Edit: still writing but wanted to say don't flash that ruu
If you want completely stock you need to use fast boot and boot into hboot and run fastboot OEM lock
(You may need to search around to learn how do that)
Then run this ruu. http://beta.androidfilehost.com/?fid=9390077933525139511
Sent from my One X using Tapatalk 2

that is for the wrong phone
only place you should look at is here AT&T, Rogers HTC One X, Telstra One XL

Its good your asking the questions now if you want to go completely stock run an ruu which means relicking the bootloader and running it ill link you to some guides in a sec
---------- Post added at 07:43 AM ---------- Previous post was at 07:43 AM ----------
Oh and like others said don't use that ruu! We have the one XL

cleanrom 4.5 is pretty good and close to stock but adds quick settings, debloated, power menu and some other tweaks. i would keep it how it is and just learn about how custom roms work. you can learn how to use twrp in its current state and maybe learn how to use some root apps.
just so you know your phone is the evita not the endeavoru.

Thanks for the replies.
I haven't tried flashing anything yet so don't worry. I'm taking it slow.
I've already been into fastboot. Figured that out because it was a required step in the guides I said I was trying to use. I have all the drivers installed and I'm able to talk to the phone via fastboot at the comand prompt.
LOL, thanks for letting me know my phone is Evita. I guess I can delete the 600mb RUU I downloaded
I'm a little unclear about HBOOT vs. fastboot. I can get into the bootloader and go to the fastboot USB mode... is this analogous to HBOOT?
So my steps right now are:
1) Download correct RUU, Evita 2.20 ICS - I've also seen people discussing 1.85 vs 2.20, why chose one over another?
2) fastboot oem lock
3) Install RUU while phone is in bootloader mode
That right?

I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit. You lose the ability to do all sorts of mods to your phone, flash custom ROMs, use apps that require root like Adaway and Titanium Backup (and many others), remove carrier bloatware, activate tethering, and much more.
People have gone through great pains to find root methods for our device (and other Android devices). Many come on here looking for these root methods, for the awesome benefits that root means. I've seen very few, if any, people before you that have said "crap I accidentally got a rooted device, and don't want root". Think about that one for a while.
Plus, CleanROM 4.5 is already based on a more updated firmware version than any of the official AT&T RUUs. Plus it includes a lot of cool features and optimizations. Again, going from CleanROM to stock is a step backwards, not forwards, and you are gaining nothing, and losing quite a bit. Another thing about CleanROM, is that it is devoid of the AT&T bloatware (and there is a lot). Keep in mind that on the stock AT&T ROM, the bloat is not removable without root, so you are stuck with quite a few crappy apps that you will never use. That alone is a huge reason to have a rooted device. Also bear in mind that stock AT&T does not allow tethering (unless you have a data plan that allows it) and has other stock HTC apps (like FM radio) disabled. These cannot be enabled unless you have root.
Another thing, is that you will not get Jellybean any faster on stock than rooted. While its true that rooted, this phone will not be able to take the OTA when it rolls out (hasn't happened yet). But a stock rooted JB firmware will almost certainly be posted here on XDA, that is safely flashable on a rooted device. This often happens within a couple days of the OTA starting to roll out, if not faster. Sometimes even before the OTA, as sometimes the official RUUs get leaked before the OTA. All it takes is for a dev to get his hands on the files, apply root, and upload it here. Learning how to flash such a file to your device is very simple. Not much more than: download the file to your phone, boot into recovery, and press "install". So yet again, stock gains nothing over being rooted.
While its true that root is not for everyone. But if you've already found this place, and learned what things like RUU, bootloader, and fastboot are, then you probably already know more than most folks do about Android. You may feel in over your head, but it really just takes a few hours of reading to learn the fundamentals. And with that knowledge, you can do so much more with your phone than you can without root.

redpoint73 said:
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit....
Click to expand...
Click to collapse
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Sent from my HTC One X using xda app-developers app

echoboomer said:
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Click to expand...
Click to collapse
You should have said so from the start, then. This pretty much negates everything I just typed above.
Its admirable that you want to learn the process from scratch, and its the opposite attitude of most n00bs here.
My advice, as another mentioned above, is stick to XDA, and don't follow instructions from random Googled sites. Most of those sites don't clearly delineate between our phone (Snapdragon S4) and the international (Tegra3) version, and following instructions for the international version is a great way to brick your phone.
Other than that, lock the bootloader, run the RUU, and have fun. Also check your hboot version. If its anything but 1.14, don't run the 2.20 RUU. You will want the 1.73 or 1.85 RUU instead, as the 2.20 RUU will update the hboot to 1.14, which plugs the holes by which boot.img and radios can be flashed from recovery. Unless you want to create ever MORE work for yourself, as the hboot can be downgraded using a Linux computer, lol!
Be sure to check out my index thread, as most anything you will need is here: http://forum.xda-developers.com/showthread.php?t=1671237

Thanks, sounds like I'm on the right track.
Also check back to my OP, I did say that I wanted to learn the whole process but I wanted to do it from stock. sorry you typed all that out but in sure it will help some other noob down the line.
Last thing, 1.85 vs 2.20?
Sent from my HTC One X using xda app-developers app

ChummyDays said:
2.20 has the new hboot, and that means that you have to extract the boot.IMG out of the ROM and flash it through fast boot. With 1.85 you just flash the ROM.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Cool thanks, I found a tutorial last night on how to extract boot.IMG from the ruu exe. I think I'm good to go.
Sent from my HTC One X using xda app-developers app

You might be confused. You shouldn't have to pull a boot.img from an RUU typically, only from a custom ROM zip. And only if you are on boot 1.14.
Sent from my HTC One X using xda app-developers app

Probably confused. Here's what I see in the boot loader.
***
Tampered
Unlocked
Evita PVT Ship S-ON RL
HBOOT-1.09.0000
Radio-0.19as.32.09.09_L
OpenDSP-v28.1.0.32.0504
eMMC-boot
***
Sent from my HTC One X using xda app-developers app

echoboomer said:
HBOOT-1.09.0000
Click to expand...
Click to collapse
This is what you want to see, and why you need to be sure to use the 1.85 RUU.