Hey,
I currently have a stock, rooted, s-off m8 with TWRP recovery. I have already read the thread on converting to the developer edition but I have a quick question that I could'nt find in the thread. I know that through this conversion, I will lose root so the first thing I will do after following the procedure will be to re-root the device. Since this involves installing a custom recovery, I will also lose the ability to process ota's. If I then go on to flash the stock recovery, will I still maintain root with the ability to process ota's?
Thanks!
neilmopar said:
Hey,
I currently have a stock, rooted, s-off m8 with TWRP recovery. I have already read the thread on converting to the developer edition but I have a quick question that I could'nt find in the thread. I know that through this conversion, I will lose root so the first thing I will do after following the procedure will be to re-root the device. Since this involves installing a custom recovery, I will also lose the ability to process ota's. If I then go on to flash the stock recovery, will I still maintain root with the ability to process ota's?
Thanks!
Click to expand...
Click to collapse
With S-Off, root isn't important. Yes, you will need stock recovery for OTA. Easiest way to convert is change CID to BS_0001 , run RUU from HTC, and be done with it, everything will be overwritten. I even left mine with that CID and get far better signal strength on ATT and instead of hanging on to a weak LTE like ATT does, it will switch to what it needs to. Loving it and wouldn't have it any other way.
hack14u said:
With S-Off, root isn't important. Yes, you will need stock recovery for OTA. Easiest way to convert is change CID to BS_0001 , run RUU from HTC, and be done with it, everything will be overwritten. I even left mine with that CID and get far better signal strength on ATT and instead of hanging on to a weak LTE like ATT does, it will switch to what it needs to. Loving it and wouldn't have it any other way.
Click to expand...
Click to collapse
Thanks for the response! I ended converting it earlier this evening. Could you elaborate on what you mean by saying that root doesn't matter since Im s-off? Should I just now flash a custom recovery so that I can flash the SU .zip and then reflash the stock recovery so that I can continue to get ota's?
Thanks!
S-Off is greater than root. With S-Off you can do anything. I think though that to install SU you do need root, I could be wrong though. But, once you root it again, you can unroot and reroot with a simple command. As far as the rest, yep, you got it now. You can use the custom recovery to flash / install whatever you want, and then go back to stock for OTA.
Related
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.
I have been trying to find a way to unroot my AT&T HTC One and revert back to stock, but I keep reading that I need a RUU and the AT&T one is now out. I have had success in unlocking and locking the boot loader, but in doing so, a nandroid backup was wiped. I currently have the bootloaded unlocked and twrp recovery with SuperSU installed, but I would like to remove SuperSU.
Is there any way to remove it for good or reflash my device to bring it back to stock?
Thanks
aophyz said:
I have been trying to find a way to unroot my AT&T HTC One and revert back to stock, but I keep reading that I need a RUU and the AT&T one is now out. I have had success in unlocking and locking the boot loader, but in doing so, a nandroid backup was wiped. I currently have the bootloaded unlocked and twrp recovery with SuperSU installed, but I would like to remove SuperSU.
Is there any way to remove it for good or reflash my device to bring it back to stock?
Thanks
Click to expand...
Click to collapse
http://www.andromods.com/unroot-locking/how-to-restore-to-stock-unbrick-unrooting-htc-one-m7.html
You have probably already read this, I'm not aware of the RUU being available for the AT&T variant yet. Where did you find it?
You have probably already read this, I'm not aware of the RUU being available for the AT&T variant yet. Where did you find it?
Click to expand...
Click to collapse
Terribly sorry, but I meant to write "not out" instead of "now out"
And yes I have read that and keep checking back every couple of days to see if the AT&T one ever shows up.
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
Hey everyone, I've done some research and found plenty of people trying to keep root while accepting an OTA, but couldn't find anything pertaining exactly to my question. does anyone know if i accept the next OTA from att will it unroot and remove the tampered banner on my m8? all i've done is root my device. haven't changed anything or flashed anything other than twrp recovery. just want to go back to stock as easily as possible.
thanks for any help
stumcmahan said:
Hey everyone, I've done some research and found plenty of people trying to keep root while accepting an OTA, but couldn't find anything pertaining exactly to my question. does anyone know if i accept the next OTA from att will it unroot and remove the tampered banner on my m8? all i've done is root my device. haven't changed anything or flashed anything other than twrp recovery. just want to go back to stock as easily as possible.
thanks for any help
Click to expand...
Click to collapse
You need to flash stock recovery, or the OTA won't install. In fact, you might even get stuck in a bootloop as the phone repeatedly boots into TWRP, looking for stock recovery (to install the OTA) and not finding it.
Also, if any system files have been modified by root, you need to return them to "stock" state. Otherwise the OTA will fail to install, saying the system has been modified. You can either return any system files to stock manually, or flash a stock ROM, nandroid, or RUU.
You will lose root when you OTA. But its an easy manner to just flash TWRP again, and flash SU/SuperSU to gain root. Unlocked bootloader is okay for OTA, so you don't even need to relock, unlock again, etc. to flash TWRP. But locked bootloader is required for RUU (unless you have s-off) if you choose that route in the paragraph above.
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.