So here's my goal, to leave everything stock, with only root (su installed), so I can install a Verizon locked app, su, and perhaps busybox (I installed Terminal Emulator, but virutally no commands available).
1. Why use the one-click method over the method? As I understand it, the just unlocks the bootloader, so I'd need to install a custom recovery, to be able to flash an unsigned zip (su). I'd like to keep the stock recovery. Perhaps the process is to flash custom recovery, su, then restore stock recovery?
2. After I get root, will future OTA updates work? I'd like to not break that functionality.
3. It would be nice if would also allow you to just get root on your phone without dealing with the bootloader.
I've rooted and flashed my old Cliq, and it's nice having root when I need it. I also wanted to play around with setting the button led backlight levels, which via the command line requires root.
wrong section man
Well, perhaps I mis-understood the sections. Seems any questions having to do with roms/rooting go in this section.
Either way, questions still stands, and it seems your the resident expert for this phone.
Forgot to add, from all the other threads I've read, it seems there is/was some confusion as to whether or not the method would all you to flash a new kernel, not that I currently want to do that.
Edit: Since this is apparently in the wrong section, can one of the mods move it?
Edit 2: Thanks Binary100100 for moving this thread to the correct section.
oryan_dunn said:
Well, perhaps I mis-understood the sections. Seems any questions having to do with roms/rooting go in this section.
Either way, questions still stands, and it seems your the resident expert for this phone.
Forgot to add, from all the other threads I've read, it seems there is/was some confusion as to whether or not the method would all you to flash a new kernel, not that I currently want to do that.
Edit: Since this is apparently in the wrong section, can one of the mods move it?
Click to expand...
Click to collapse
you can flash kernels it is harder what else you need to know
How do I backup the stock recovery?
If I unlock the bootloader, do I need to flash a custom recovery to move forward? Or does unlocking the bootloader allow me to flash unsigned zips?
yes and its hard to backup stock recovery i got a backup all ready
So with an unlocked bootloader, I won't need a custom recovery? Just trying to learn, as it's a bit different than my Cliq.
you do need custom recovery sorry man i cant do much more explaing so busy butother people help you and look around read root threads etc
Well, thanks for the help so far.
If any one else is reading this thread, these are the questions I still have:
1. How do I backup the stock recovery? I know once I load a custom recovery, I will be able to backup the stock ROM.
2. Disregarding any warranty issues, why choose the method or the One-Click method?
3. Once unlocked/rooted, will DRM content still work? Will the Movies section in the Android Market still be available? It's not on my Cliq with CyanogenMod 7.
4. Once unlocked/rooted, will OTA updates apply correctly? Was anyone rooted on 1.36.531.5 and have the 1.36.531.6 update apply correctly?
5. Does the method wipe the device?
Thanks,
Ryan
oryan_dunn said:
Well, thanks for the help so far.
If any one else is reading this thread, these are the questions I still have:
1. How do I backup the stock recovery? I know once I load a custom recovery, I will be able to backup the stock ROM.
2. Disregarding any warranty issues, why choose the method or the One-Click method?
3. Once unlocked/rooted, will DRM content still work? Will the Movies section in the Android Market still be available? It's not on my Cliq with CyanogenMod 7.
4. Once unlocked/rooted, will OTA updates apply correctly? Was anyone rooted on 1.36.531.5 and have the 1.36.531.6 update apply correctly?
5. Does the method wipe the device?
Thanks,
Ryan
Click to expand...
Click to collapse
1. There is no need to backup the stock recovery. Once you flash a custom recovery there will never be a need to go back to stock. If for whatever reason you do want stock then just flash an ruu and you'll go completely back to stock.
2. You MUST use the method to get the unlock_code.bin file to unlock your bootloader before you even attempt to get root access. Once you have your bootloader unlocked you can make changes to the root of your device. With it locked you can only obtain a partial root which will reset itself after a reboot. For example, if you obtain a temporary root and remove a system app (like boatware), or two, or ten (whatever) then reboot they will re-appear. So you MUST have either s-off (not going to happen until an exploit is found and really isn't needed) or an unlocked bootloader. Once you receive the file from HTC then follow the included instructions to unlock your device. NOTE: You will lose all of your data when you unlock your bootloader so back it up first! After your bootloader is unlocked you can obtain root by one of two methods.
a) 1-Click root script.
This simply pushes an app called SuperUser.apk to the /system partition and a su binary file to the /system/bin directory which gives us root. Then download ClorckworkMod app from Market and install the custom recovery. From the app you can select "reboot to recovery" and install your custom roms.
b) Placing a custom recovery in a form of a PH85IMG.zip on the root of your external sdcard and boot into the bootloader. Then update the recovery.
Now with all of that being said I want to make something clear. The unlock method does NOT allow you to use the device for other carriers! You would still require the T-Mobile SIM to use the device.
3. Having root does have some disadvantages. Some roms may effect the ability to watch DRM movies, watch movies from Market, etc. Depends on your rom though. Check with the developer. ALWAYS make a nandroid backup prior to flashing any rom! That way if you don't like what you flashed you can always revert.
4. Okay... well I stand corrected.... this is the ONLY real reason to install the stock recovery. However installing an OTA update will cause you to lose root. Even with a custom recovery and a stock rom... if you receive a notice to install an update it will not work! The best alternative if you really really really want the update and lose all root then flash an RUU, do the update and hope that HTC didn't do anything to prevent you from getting root again. My best advice would be to wait for your favorite developer to update his/her rom with the update that you're trying to flash. That way you won't lose your data (shouldn't anyway) and no real risk of losing root.
With all that being said... I'm moving this to General because it's where all the Q&A's go.
Thanks for all the detailed info. I'd like root (installation of Superuser only) for the stock ROM. I don't plan on installing a custom ROM at this time. If I have an unlocked bootloader, how could HTC block root access? Couldn't I just flash an su zip? Ideally, I'd like to be able to swap recoveries out to apply the OTA updates. I kinda wish they had a code to just give me root access on the stock ROM.
I see the ruu thread, but am concerned about the source of the ROMs. Does HTC ever officially release a complete stock ROM?
Sent from my HTC_Amaze_4G using XDA App
oryan_dunn said:
Thanks for all the detailed info. I'd like root (installation of Superuser only) for the stock ROM. I don't plan on installing a custom ROM at this time. If I have an unlocked bootloader, how could HTC block root access? Couldn't I just flash an su zip? Ideally, I'd like to be able to swap recoveries out to apply the OTA updates. I kinda wish they had a code to just give me root access on the stock ROM.
I see the ruu thread, but am concerned about the source of the ROMs. Does HTC ever officially release a complete stock ROM?
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
This is all that you really need here.
http://forum.xda-developers.com/showthread.php?t=1324177
If you really want to be able to download and install system updates you will need the stock recovery in step 4.
oryan_dunn said:
Thanks for all the detailed info. I'd like root (installation of Superuser only) for the stock ROM. I don't plan on installing a custom ROM at this time. If I have an unlocked bootloader, how could HTC block root access? Couldn't I just flash an su zip? Ideally, I'd like to be able to swap recoveries out to apply the OTA updates. I kinda wish they had a code to just give me root access on the stock ROM.
I see the ruu thread, but am concerned about the source of the ROMs. Does HTC ever officially release a complete stock ROM?
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
IDK but I read your questions in a very slow voice like mr. mackey in southpark or something
anyways, why are you so worried about getting OTA updates?
a developer will eventually root and deodex it anyways.
You say you want to keep stock rom, but why don't you try the Custom ROMs which are basically stock ROMs on steroids?
You do realize when you apply an OTA update you lose your root access and there is a possibility that it'll be harder to even have your device rooted in the future.
For example, the mt4g, everybody got happy and updated to the gingerbread OTA, but lost root and nobody found out how to exploit it until about a month later or so.. and that is only by downgrading which is a tedious process that many, who don't know how to use ADB, have troubles with.
I believe the OTA updates comes with new bootloaders and radios, not only the rom, so it will lock your bootloader. (I think) that's what it does to other devices. Who knows if htcdev will work on all bootloaders. just my two cents, if you want full control of your device, unlock bootloader and root it. You can get every OTA update through developers here.
Teo032 said:
IDK but I read your questions in a very slow voice like mr. mackey in southpark or something
Click to expand...
Click to collapse
Man, hopefully I don't sound like that. I really appreciate all the step-by-step guides; but, unlike most people, I want to understand what I'm doing, not just run through the steps.
anyways, why are you so worried about getting OTA updates?
a developer will eventually root and deodex it anyways.
You say you want to keep stock rom, but why don't you try the Custom ROMs which are basically stock ROMs on steroids?
Click to expand...
Click to collapse
Well, I don't really want to wipe my device at this time, so that probably rules out the HTC Dev method and installing a custom ROM. I asked about the source of the ROMs in the RUU thread, but if the stock recovery would flash them, then they'd obviously have been signed by HTC. If software is available via an official source, why would I download it from a forum? If I can get Ubuntu from Canonical, I wouldn't go download the ISO from an unofficial mirror (or if I did, I'd verify with the md5sum keys posted by Canonical).
Since I am really happy with my device as it is, and the ease of updating via OTA, I didn't want to give that up, just for the couple things I want to do with root access.
You do realize when you apply an OTA update you lose your root access and there is a possibility that it'll be harder to even have your device rooted in the future.
For example, the mt4g, everybody got happy and updated to the gingerbread OTA, but lost root and nobody found out how to exploit it until about a month later or so.. and that is only by downgrading which is a tedious process that many, who don't know how to use ADB, have troubles with.
I believe the OTA updates comes with new bootloaders and radios, not only the rom, so it will lock your bootloader. (I think) that's what it does to other devices. Who knows if htcdev will work on all bootloaders. just my two cents, if you want full control of your device, unlock bootloader and root it. You can get every OTA update through developers here.
Click to expand...
Click to collapse
Hmm, unless these devices have backup/secondary bootloaders, I doubt and OTA update would flash a new one, as an error during that flash could brick the device. It would seem odd that HTC would promise to unlock bootloaders, give an OTA update that would not work with their site. I'm not saying that it couldn't happen, just seems unlikely. Was the MT4G unlock done via? If it was an exploit to gain root, then I'd understand why they'd loose root.
oryan_dunn said:
Hmm, unless these devices have backup/secondary bootloaders, I doubt and OTA update would flash a new one, as an error during that flash could brick the device. It would seem odd that HTC would promise to unlock bootloaders, give an OTA update that would not work with their site. I'm not saying that it couldn't happen, just seems unlikely. Was the MT4G unlock done via? If it was an exploit to gain root, then I'd understand why they'd loose root.
Click to expand...
Click to collapse
HTC has updated their bootloaders via OTA on a few occasions. And we know that HTC and T-Mobile (along with other carriers) read these forums as well (shout out to HTC and our wireless carriers) so almost literally the day of an exploit is discovered and if HTC isn't happy with our findings what do you suppose they will do? They will almost always look for the safest way to update the bootloader and keep us from being able to use that exploit. Seeing that we still don't have S-OFF (and may never have it) they are obviously doing all they can to make it more and more difficult. That in itself is proof that they don't want us to have it. So would they push an OTA to keep us locked to S-ON if they can? You better believe it!
I can see them patching a hole that would get you S-OFF, but seems odd that they would take back an unlocked bootloader that they themselves unlocked.
I guess I'm ok with the offical unlock method without S-OFF, if the only things I can't do are flash a new bootloader, radio, or unlock the SIM. Did I miss anything there?
I don't get it, you say you want to use root on the stock roms, and now you're saying why bother downloading a stock ROM that is prerooted when you can download stock ROM that isn't rooted ota? What is the difference? You're going to want to root the ota updates and the developers are already providing it for you. it doesn't matter where you get it, you're gonna use some 3rd party exploit to root the ROM anyways.
You my friend seems to have a indecisive problem. I understand that you want to understand the process, but if you don't want anything to do with 3rd party developing you're in the wrong place. You're making your life very hard.
And i think that's about it about being s-on. It's more of the hardware functionality that is locked.
Think about it as a locked bios kinda... Lol
Sent from my HTC_Amaze_4G using XDA App
Teo032 said:
I don't get it, you say you want to use root on the stock roms, and now you're saying why bother downloading a stock ROM that is prerooted when you can download stock ROM that isn't rooted ota? What is the difference? You're going to want to root the ota updates and the developers are already providing it for you. it doesn't matter where you get it, you're gonna use some 3rd party exploit to root the ROM anyways.
You my friend seems to have a indecisive problem. I understand that you want to understand the process, but if you don't want anything to do with 3rd party developing you're in the wrong place. You're making your life very hard.
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
I don't need to use an exploit to root the stock rom. I can unlock my bootloader direct from HTC, flash a new recovery, and then flash the superuser program. That was kinda my point in asking in the first place... why use an exploit (one-click), when an official route is available?
oryan_dunn said:
I don't need to use an exploit to root the stock rom. I can unlock my bootloader direct from HTC, flash a new recovery, and then flash the superuser program. That was kinda my point in asking in the first place... why use an exploit (one-click), when an official route is available?
Click to expand...
Click to collapse
That's considered official? It's basically the same thing..
Sent from my HTC_Amaze_4G using XDA App
Teo032 said:
That's considered official? It's basically the same thing..
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
Well, yeah, you end up at the same place, except instead of using an exploit, I go to HTC to get an unlock code. I'd consider it official since I'd go through HTC to get the ball rolling.
Ok everyone. I like to think I am efficient enough to figure things out and such but I will honestly say I am having a major n00b moment with this one.
In the past, with my older Android phones (Droid 1 and Droid Razr) I was able to root and unroot the phones by following the instructions and ensure if I ever returned my device to Verizon, it gets unrooted and such.
however, now that I have the HTC Rezound from Verizon, I feel pretty stupid when it comes to the instructions I've found.
I gotten as far as unlocking the bootloader which appeared to be fairly simple, but there are just so many instructions out there on how to root the phone I cant make heads over heals on what to do.
Essentially I just want to be able to root and unroot the phone in the event I ever were to return it to Verizon for replacement. Can someone direct me to the proper way in doing this? I'd truly appreciate the help. Thank you all
storo1975 said:
Ok everyone. I like to think I am efficient enough to figure things out and such but I will honestly say I am having a major n00b moment with this one.
In the past, with my older Android phones (Droid 1 and Droid Razr) I was able to root and unroot the phones by following the instructions and ensure if I ever returned my device to Verizon, it gets unrooted and such.
however, now that I have the HTC Rezound from Verizon, I feel pretty stupid when it comes to the instructions I've found.
I gotten as far as unlocking the bootloader which appeared to be fairly simple, but there are just so many instructions out there on how to root the phone I cant make heads over heals on what to do.
Essentially I just want to be able to root and unroot the phone in the event I ever were to return it to Verizon for replacement. Can someone direct me to the proper way in doing this? I'd truly appreciate the help. Thank you all
Click to expand...
Click to collapse
Once you have unlocked the bootloader or gotten s-off, you just need to flash a recovery (Amon ra is linked in my sig) then flash a rom. All of the ROMS are pre-rooted. To revert to uprooted, all you need to do is run the GB RUU which can be found in the development section (or google)
AshtonTS said:
Once you have unlocked the bootloader or gotten s-off, you just need to flash a recovery (Amon ra is linked in my sig) then flash a rom. All of the ROMS are pre-rooted. To revert to uprooted, all you need to do is run the GB RUU which can be found in the development section (or google)
Click to expand...
Click to collapse
am not sure if i ever had the change to thank you but thank you!
I haven't exactly rooted 100 devices before. Most of the root utilities I've used were things like Z4Root where it's one click and done. I've recently become interested in flashing my Incredible 4G LTE. On top of that, I've already rooted my Nexus 7 using instructions like this here.
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm curious if this guide, being that it's more of a manual way to do it since it involves running several commands (I ran this from my Linux desktop to root my N7) is anything like what it would be to root the Incredible manually, or any device. I guess the only device that would be different would likely be the bootloader step (grouper?) since HTC likely did their's differently than Google with the Nexus 7, no?
Just trying to get more insight on it, as I certainly don't want to brick anything but I'd like to get them done. :good:
It seems to me that we would first need a modified bootloader or /system to attempt to flash, but I doubt "fastboot erase ..." is allowed without dev unlock on the bootloader, and "fastboot flash ..." most likely needs a signed image.
Does anyone with more expertise on this topic have any input?
JaSauders said:
I haven't exactly rooted 100 devices before. Most of the root utilities I've used were things like Z4Root where it's one click and done. I've recently become interested in flashing my Incredible 4G LTE. On top of that, I've already rooted my Nexus 7 using instructions like this here.
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm curious if this guide, being that it's more of a manual way to do it since it involves running several commands (I ran this from my Linux desktop to root my N7) is anything like what it would be to root the Incredible manually, or any device. I guess the only device that would be different would likely be the bootloader step (grouper?) since HTC likely did their's differently than Google with the Nexus 7, no?
Just trying to get more insight on it, as I certainly don't want to brick anything but I'd like to get them done. :good:
Click to expand...
Click to collapse
What those tools do is use an exploit to write the su and superuser.apk to /system and/or a modified recovery for flashing ROMS and kernels on unlocked bootloader devices.
google has properly patched those exploits as they should as we don't want a malicious app installing Root and hacking data on just anyone's phone.
Some phones with locked bootloaders have had exploits to install custom recovery and/or hacked/leaked bootloaders in order to allow us to use the phone like it was unlocked. HTC fixed this issue with their latest phones.
Their bootloaders now do not run all of the adb commands until unlocked by HTC dev, which limits us a lot. They also made it so that even if we DID manage to find a software exploit and start flashing stuff, the locked bootloader would know, via a signature check, that something was modified... and refuse to boot (Bricked Phone).
HTC Dev unlock is not true unlock either. We still can't modify the HBOOT w/o triggering it to brick the phone. An unlocked HTC bootloader limits changing the kernel to HBOOT mode only, which means u need a PC and extra steps to finish flashing any ROM.
Some brilliant Dev's managed to use RUU files to update the kernel only, but that also causes issues. If one Dev uses a newer RUU, you can't use the another Dev's older RUU to flash a kernel because the unlocked HTC Bootloader doesn't allow you to "Downgrade" firmware. This leads to headaches with people ignoring the kernel step and screaming because their phone won't boot.
The ultimate Holy grail for is is what is known as "S-OFF"
This allows full access to the HBOOT Recovery and system for all of our awesome devs to work their magic. This was obtained (long after HTCDev unlock) with the Rezound only through a HARDWARE exploit. We needed root exploit (which we had on the GB stock ROM), and to physically short out a pin on the mainboard to ground at precise times while the SOFF program ran on your PC.
We have to wait for the less popular HTCDev unlock (which HTC Did give us on the rezound with a middle finger to verizon), or for some1 to find another Exploit that would bypass the signature check of the HBOOT and give us "S-OFF".
Either will give us Root, custom recoveries, and ROMs.
I am no dev, but this is my understanding of what's happening with these devices. This is my 9th android device, 5th HTC, but I am always learning more. Dev's feel free to correct me, or expand on anything I have written here ^^
Got my HTC One M8 from AT&T yesterday. Been reading these forums and all the tutorials and compilation threads have been very useful. What I've done:
Unlocked the bootloader via htc-dev
Flashed the latest Philz
Used Philz to install SuperSU for root
Achieved s-off
Used Titanium backup to freeze the "HTC DM" app and thereby disable OTA updates
Phew! After wiping the sweat from my forehead (kind of new to much of this), I find out that there have been OTA updates that add considerable functionality to the HTC One such as the Extreme Power Saving mode and a radio upgrade.
So... I'm kind of terrified, since I'd like the new features but I know that with an unlocked bootloader and S-OFF I could majorly screw myself. I've also gone to the effort of installing all my apps and configuring my settings - which took several hours to do - and I feel a bit sick at the idea that I might have to lose it all.
Is there a clear guide or tutorial out there for getting these new firmware/OTA features without losing all my work or bricking the phone? Thanks!
[Q] Unlocked bootloader, flashed Philz, rooted, s-off... Now how do I update?
Answer: You don't.
My opinion, official OTAs have no place on modded phones. You went through all the effort to enable your phone to flash custom ROMs. So the last thing you want is to install an OTA. If you want OTA, you need to go back to stock recovery. Its a big step backwards, and completely unnecessary.
The features you mentioned can all be applied without OTA. You can just flash a stock rooted version of the 1.58 ROM; or flash a custom ROM based on 1.58. Better yet, flash a custom ROM based on the (non-AT&T) "international" base as IMO they are much better than the bloated, gimped up junk AT&T gives you. In fact, Extreme Power Savings mode was available on the international ROMs a good while before the AT&T OTA started rolling out.
For a new radio, since you are S-off, just go to the radio thread, and download and flash the new radio.
This is the type of thing you did all this for (unlock the bootloader, root, S-off), is it not?
Everything mentioned above can be found on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Also, using Titanium Backup, I don't see how it could have taken "several hours" to setup the phone again. Get the paid key (which enables batch functions) if you haven't already - highly recommended if you will be flashing ROMs with any frequency. Using batch backup and restore, it should take about 5 minutes to restore you apps and app data. Then a little while longer to manually configure settings, home screens, etc. I am up and running after flashing a new ROM in 20-30 minutes. Maybe a bit longer if you have a lot of very specific settings. But we're still talking maybe an hour, tops.
Thank you for the detailed help, rep given! I'll check out the threads for the custom ROMs and follow your advice.
FOUND THE RECOVERY (See below)
Right now my goal is to go back to stock to flash the OTA Update. I am running my nandroid back up I first made when which is the 4.4.4 w/ Software # 1.58.502.1. and right now I have TWRP as my recovery.
Also can someone confirm something for me. This nandroid I am running is rooted obviously and has SuperUser on it. If I go back to the stock recovery can I still do the OTA update even though SuperUser is there and the phone is unlocked?
Also in order to get the stock recovery back on the phone I need to use ABD and the windows command prompt method correct?
Thanks
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
magicbumm328 said:
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
Click to expand...
Click to collapse
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
redpoint73 said:
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
Click to expand...
Click to collapse
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine. And as mentioned I found the stock recovery as well.
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Thanks for the help and suggestion too btw
magicbumm328 said:
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine.
Click to expand...
Click to collapse
SuperUser is same as root, and is fine.
When I say "modifed by root" that often is when a user deletes "bloatware" they don't want, or adds apps, or modifies apps in the system partition.
If you didn't explicitly do any of those things, you should be fine. You will know this is the problem when you install the OTA, as the install will fail with the error message that the "system has been modified".
magicbumm328 said:
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Click to expand...
Click to collapse
RUU = ROM update utility
RUU is super easy, you don't really need much guidance to use it. LOCKED or RELOCKED bootloader is required to run it (UNLOCKED if okay if you have s-off). PC required, and the RUU will wipe the phone (so backup any personal data you want to keep, into your PC, cloud, etc.). Aside from those points, RUU is a self-explanatory executable (.exe) program that runs from your PC, and simple to use.
Relocking the bootloader is accomplished easily with a single fastboot command (after connecting phone to PC and booting into fastboot mode): fastboot oem lock
This is also assuming you did the bootloader unlock yourself, and therefore have fastboot/adb setup on your computer.
Running the RUU itself (after relocking the bootloader) is very easy. Boot into OS (some folks have better success being booted into fastboot mode, but I think the RUU is designed to run when booted into OS), connect to PC, then just run the RUU executable on your PC. The RUU executable will then just guide you what you need to do. Its mostly automated, you just need to confirm a few dialogue screens, etc. The RUU will reboot the phone a couple times, install the needed files automatically, and that's really it.
However, since you seem confidant you already have a stock ROM and corresponding stock recovery, I suppose the RUU doesn't gain you too much. But if you hadn't done those steps already, it often saves folks the hassle of tracking down the right stock ROM and recovery for their CID and current firmware. RUU in my opinion is a cleaner install, as it installs a complete stock image (not just updating piecemeal, like an OTA often does).
Also, since OTAs typically need to be installed in sequence, you will probably need to OTA to 2.23 software, than another OTA to 3.42 software. As RUU is a complete image, it would get you to 3.42 software in one fell swoop.
One other thing to note, is that if you are for some reason not connected to AT&T's network (using another carrier, another country, etc.) you will not get any OTAs on the AT&T branded device. AT&T oddity here, most other version will still OTA, even when not connected to a specific carrier. In contrast the AT&T RUU is able to be downloaded and run by anyone with an internet connection and PC (regardless of country, carrier, etc.). I'm under the assumption that most folks on this forum section are on AT&T's network, although I know that some are not (you haven't stated either way).
RUU links are included on my Index thread under heading "RUUs": http://forum.xda-developers.com/showthread.php?t=2751432
Aside from wiping the phone (OTA keeps user data, but you may end up wiping anyway if you run into bugs after OTA), the other downside to RUU is that you need to relock the bootloader. Then you need to unlock the bootloader again (via the HTCDev.com site, or alternately sunshine) if you want to install custom recovery, install custom ROMs, root, etc.
So the choice is really yours (RUU versus OTA). I'm just giving it as an alternative.