I think I may have messed myself up in regards to the new OTA for the Rezound. Here is the story...
My phone is currently unlocked and perm-rooted enough to use Titanium Backup on a regular basis.
Not thinking, I backed up and uninstalled some system apps (bloat) using Titanium Backup in December:
Backup Assistant
Mobile Hotspot
Mobile IM
Mobile Instant Messenger
My phone downloaded the OTA last night and attempted to install. It gets about 1/4 of the way through and stops (picture of a phone and <!> ). I have to battery pull to get it to restart. The only error message I get is: "Update Failed, Code 410"
I have tried multiple times to run the OTA and get the same result each time.
The only thing I can think is that the OTA will not install because there are system apps missing (Mobile Hotspot specifically).
I have been unsuccessful in restoring the apps via Titanium Backup. It just hangs and doesn't actually do anything.
Is there anything else I can try? Did I permanently mess things up by uninstalling those system apps? Is there other issues I may be missing?
I'm open to ideas...
if i remember correctly, it won't update if the bootloader is unlocked. all you may need to do is "relock" it. Search for "OTA" or "update" and "bootloader" and you may get some info.
or wait for someone with a better memory than i
just noticed mine tried to force the update... for anyone who hasn't updated in some capacity, looks like it will auto-update Feb 5
i do believe you need to install stock recovery for the update to install.
best bet is to install a stock rom that someone has already rooted, deodexed, etc.
You don't need to relock the bootloader. You need to unfreeze any software, or reinstall it if removed. You also need to install stock recovery.
Requirements to take the ota:
- stock os
- stock recovery
- all stock programs not frozen or uninstalled
Things that don't seem to matter:
- rooted
- unlocked bootloader
Use OTA Rootkeeper if you wish to preserve root through the OTA(make sure to use it to make the backup first)
esheesle said:
You don't need to relock the bootloader. You need to unfreeze any software, or reinstall it if removed. You also need to install stock recovery.
Requirements to take the ota:
- stock os
- stock recovery
- all stock programs not frozen or uninstalled
Things that don't seem to matter:
- rooted
- unlocked bootloader
Use OTA Rootkeeper if you wish to preserve root through the OTA(make sure to use it to make the backup first)
Click to expand...
Click to collapse
This is exactly what I was looking for! I.am running stock, rooted with apps frozen.
I can easily unfreeze the ones with titanium back up.
How do I get and uninstall stock.recovery?
Boy do I feel stupid lil
Sent from my Kindle Fire using Tapatalk
you can find a link for the stock recovery in the first post.
http://forum.xda-developers.com/showthread.php?t=1466474&highlight=stock+recovery
I did everything in that thread, but still got the red triangle with the exclaimation mark...
Thanks for the tips everyone...
I'm still running the stock os and recovery, but I am missing the apps I listed above:
Backup Assistant
Mobile Hotspot
Mobile IM
Mobile Instant Messenger
Problem is, that I uninstalled them using Titanium Backup (I know now that I should have frozen them).
I will try re-locking the bootloader and seeing if it will let me run the OTA. If not, is there a way to force Titanium Backup to re-install those system apps? I have been unsuccessful so far.
Looks like this is not my lucky day...
I relocked the bootloader using the instructions on HTCdev and tried the update again. Same issue as before. It gets about 1/4 of the way through and stops.
While I was trying this all out, it got me thinking... Could this be due to the perm-root? Titanium backup still shows that it has root access even though my phone is relocked.
sdlucky7 said:
Looks like this is not my lucky day...
I relocked the bootloader using the instructions on HTCdev and tried the update again. Same issue as before. It gets about 1/4 of the way through and stops.
While I was trying this all out, it got me thinking... Could this be due to the perm-root? Titanium backup still shows that it has root access even though my phone is relocked.
Click to expand...
Click to collapse
As much effort as you are expending trying to get an OTA update for GB, why don't you just use a custom ROM, like CleanROM ICS. At least for me I get better performance and battery life to boot.
Yea... A custom rom has crossed my mind quite a few times. For this OTA, I'm more interested in the firmware included (radio, etc) to maybe fix this earphone static I have. If we had S-Off, I could just flash the radio and then use a custom rom.
Con put out a Rom that updates the radio and I believe the hboot too
sent from my newly unlocked Rezound
http://forum.xda-developers.com/showthread.php?p=21880389
sent from my newly unlocked Rezound
You do need to be back to stock so maybe there's something you missed since you were rooted?
You can relock and then run the RUU to get you there and then accept the OTA and it should work. Then just unlock again and flash Amon Ra, and then either run stock or restore a nand or flash a new ROM. If you go with an older ROM without the new kernel and you want to use the new kernel you might need to update that. You can do that by following this thread:
http://forum.xda-developers.com/showthread.php?t=1467793
ATERNATIVE METHOD:
You can also use con247's Stock OTA ROM instead of running the RUU.
http://forum.xda-developers.com/showthread.php?p=21880389
Here are the steps to take to accomplish that:
1) use Amon Ra to flash con's vigorStock OTA ROM. It will do its thing then reboot to hboot. I think it then asks you if you want to update. Don't do it yet.
2) At this point you want to relock. So go into fastboot on the phone. Using adb/fastboot type the following at the cmd prompt:
fastboot oem lock
3) Reboot phone and let it flash the PHzip file. It should reboot completely when it's finished.
4) delete the PHzip file using a file explorer app like ES File Explorer or Root Explorer.
5) get the phone back into fastboot. Unlock again using adb/fastboot. I don't remember the exact command but you can find that in the guide for unlocking.
6) reinstall su using Amon Ra.
Now you should be stock OTA rooted with the new goodies.
Check in Settings > About phone > Software info > More to see that you got all the new stuff.
Thanks for the help everyone.
I ended up just flashing the new RUU using the exe found here:
http://forum.xda-developers.com/showthread.php?t=1472606
I didn't mind setting up my phone again, and everything seems to be working fine.
I am going to try to hold out rooting until the ICS OTA update comes out (whenever that might be) so that I can avoid this same issue... We'll see how long that lasts.
Related
Okay, so I haven't as of yet seen a thread that appears to spell out this process. Most of you are talking about applying developer-modified patches to get to DI01, using Clockwork recovery, and things like that. For various reasons, some of us prefer to remain a bit closer to stock, and not worry about bricking with custom recovery software and whatnot. I'm one of those people, and I've seen questions here and there on how to go back to stock, and if root can be maintained or redone afterward, etc., so I decided to document here what I did to apply the official update to my rooted and lag-fixed Fascinate. Without further ado, here's the process I followed:
Ran the unlagfixme.bat script from http://forum.xda-developers.com/showthread.php?t=779597, which automatically reboots the phone
Used Root Explorer to remove the ".old" extension I had added to all system .apk files I considered bloatware (I chose to disable them, not delete them)
Rebooted the phone again for good measure
Downloaded the update, and let it install normally, after which root access was gone as expected (Superuser.apk and other apps that required root access were still present, but they wouldn't function)
Rooted my Fascinate again per the instructions in http://forum.xda-developers.com/showthread.php?t=779238, just like I did the first time (only had to do it once, not twice like some here have said); note that I followed all instructions except for the final one, which is installing Superuser.apk, as that application was still installed, and still worked fine after applying the proper permissions to su and busybox
Opened Root Explorer, and once again added .old to all .apk files that I wanted to disable and remove from sight
Rebooted again
Ran the lagfixme.bat from http://forum.xda-developers.com/showthread.php?t=779597 to re-apply the lag fix
Rebooted one final time to make sure everything was in still good working order
So there it is. I'm still running stock ROM, stock recovery, etc. I should be able to easily repeat this process any time there's a new OTA update, with minimal risk of bricking.
Helpful thanks, but I think I screwed up.
SO I got the OTA update message this morning. I have root and lagfix installed, and I ran the OTA. Everything works but I no longer have root access. SO I think I screwed up. Newb right. SO do I have to go back to the stock image? What do I need to do to recover while retaining my contacts apps etcetera. Thanks
propylene22 said:
SO I got the OTA update message this morning. I have root and lagfix installed, and I ran the OTA. Everything works but I no longer have root access. SO I think I screwed up. Newb right. SO do I have to go back to the stock image? What do I need to do to recover while retaining my contacts apps etcetera. Thanks
Click to expand...
Click to collapse
Just re-root, either through adb or there was a one-click out there.
Yeah, just re-root using the original procedure you used (except no need to reinstall superuser.apk), and you should be good to go.
Sent from my SCH-I500 using XDA App
Thanks for taking the time to write that up Ivorycruncher!
How would this process differ when the Froyo update is released, also having ClockworkMod Recovery installed instead of stock recovery?
I, like you, would like to have legitimate updates installed while keeping root.
I've never installed Clockwork, so I can't comment on that. When Froyo comes out, I imagine the process will be much the same, though at this point there's no way to know if the original rooting method will still work or not after the upgrade. Also, depending on what they do with Froyo, the lag fix may not be necessary anymore, and might not work without some tweaking even if it is still needed.
Sent from my SCH-I500 using XDA App
I have a rooted Amaze with just some bloatware removed. Yesterday I received a notification in the status bar that a system update was available. When I try to run the update the phone reboots and then freezes with a big green X on the screen. Doesn't look like something official. Has anyone seen this before or know what it's about? I'm thinking maybe it's just failing to run the update because of being rooted or a related issue but can't find any info on Google about the green X.
I finally pulled the battery out because it wouldn't respond and then turned the phone on again. It booted fine and I still have the notice about the update. I'm reluctant to try again until I find out what's going on. Thanks.
I don't think you're able to install an update through a custom recovery..There should be a ROM with that update already in it.
If you have a Custom ROM you can't take the update that is intended for stock unrooted ROMS.
Sent from my HTC Amaze 4G using xda premium
Thanks for the feedback. I don't have a custom rom - just the stock minus some bloat. I can see how the custom recovery, however, might interfere.
I can't find any info on the update and what it includes or why I might want/need it but assuming it would be good to install then is there an easy way to remove the custom recovery? Would running the stock update.zip do this or do I need to go through the full un-root process?
If you have CWM recovery already,
1. Go to /downloads folder inside the internal Storage. You can find the OTA.
2. Rename it to "update.zip" and copy to External SD.
3. Reboot the device to recovery.
4. Select update.zip and update manually.
5. After update & reboot, delete both original files to get rid of notification.
Thanks for the directions. Tried and got this error
Code:
verifying current system...
assert failed: apply_patch_check("/system/app/FriendStream.odex", "some very long hex number", "some other long hex number")
E:Error in /sdcard/update.zip
(stage 7)
Installation aborted.
droidux said:
Thanks for the directions. Tried and got this error
Code:
verifying current system...
assert failed: apply_patch_check("/system/app/FriendStream.odex", "some very long hex number", "some other long hex number")
E:Error in /sdcard/update.zip
(stage 7)
Installation aborted.
Click to expand...
Click to collapse
Seems its not possible as you have removed some programs
Think you removed friendstream also.
It seems to work only if the ROM is unmodded
skr_xd said:
Seems its not possible as you have removed some programs
Think you removed friendstream also.
It seems to work only if the ROM is unmodded
Click to expand...
Click to collapse
Yes, I removed facebook and friendstream. Not sure why those would be necessary to run a system update but you may be right about not being able to update a modified phone. Maybe the update isn't anything I need anyway if it wants to update an app I don't want.
Thanks for the help.
In case anyone has a similar issue, here is what I've figured out.
The update won't run on a modified system - even if it's a stock, but changed, rom. In the interest of exploration, I restored my backup using clockwork and then ran the update. It still didn't work, but following skr_xd's advice above I was able to run the update manually. The result was a more or less stock phone without root but with the most current software. I then re-rooted the phone and re-removed all the bloat with no apparent ill effects.
Thanks for the help.
Btw, I didn't know what the green X was all about, but I think it's related to clockwork mod. Could be wrong though.
droidux said:
In case anyone has a similar issue, here is what I've figured out.
The update won't run on a modified system - even if it's a stock, but changed, rom. In the interest of exploration, I restored my backup using clockwork and then ran the update. It still didn't work, but following skr_xd's advice above I was able to run the update manually. The result was a more or less stock phone without root but with the most current software. I then re-rooted the phone and re-removed all the bloat with no apparent ill effects.
Thanks for the help.
Btw, I didn't know what the green X was all about, but I think it's related to clockwork mod. Could be wrong though.
Click to expand...
Click to collapse
yes its the custom clockworkmod i made
xboarder56 said:
yes its the custom clockworkmod i made
Click to expand...
Click to collapse
Thanks for the confirmation and awesome software. I noticed there is work on version 5.0.2.7. Assuming it would be wise to update once released.
Same issue here. I have stock rom without any bloatware removal.
I just unlocked the bootloader than installed CWM and rooted the phone.
when I try to update phone OTA it stucks in splash screen (With Big Green X logo)
Flash prerooted rom you good to go
Sent from my HTC Amaze 4G using xda premium
I just spent abut 4 hours trying t figure this out...
This is my journey..
Relock bootloader
Flash one of the stock tmobile ruby rom in development section
Did the OTA update on stock
Unlocked my bootloader again
Then i tried to root using one click zerg method but it didnt work
So i flashed clockwork mod using fast boot
Then applied a su binary update i found in the development section.
In less than a minute i got root back.
Then i restored my data from nandroid backup.
My phone is pretty much rooted, bootloader unlocked, bloatware free alongside having the ota update that enabled wifi calling installed.
You don't need to relock your phone to do the update. If you do xboarder's recover to stock method just skip the relock part you can update your phone. So far going back to stock is the only way to get the radio updated as well which I am noticing way better 4g coverage than before!
bmbrad said:
You don't need to relock your phone to do the update. If you do xboarder's recover to stock method just skip the relock part you can update your phone. So far going back to stock is the only way to get the radio updated as well which I am noticing way better 4g coverage than before!
Click to expand...
Click to collapse
working on a way maybe this weekend will have it ready
xboarder56 said:
working on a way maybe this weekend will have it ready
Click to expand...
Click to collapse
NICE! Dude you must never sleep! Always the first to get something done!
I figured out what to do. You just need to rename this update file to update.zip. then reboot in recovery and choose install update from sd card. Next navigate to download folder and install update.zip file. You will be updated and stay rooted at the same time.
This worked for you because you didn't remove any of the t-mobile bloatware from your phone.. This will not work for people who messed with the pre-installed bloatware.
darll said:
This worked for you because you didn't remove any of the t-mobile bloatware from your phone.. This will not work for people who messed with the pre-installed bloatware.
Click to expand...
Click to collapse
Maybe, but 8m I've got another problem after updating this way. Wifi doesn't work anymore. I receive an error while trying to switch on wifi.
Hi all,
My AT&T Atrix is running 4.5.91. I unrooted it to update to 4.5.141 OTA (I understood it was risky to do an OTA update while rooted).
After I finished downloading the update, I started installing but during installation, the package icon changed to a warning icon (with no error message) and the phone rebooted on 4.5.91 with a message saying the update failed
I think the package may have been corrupted in the download as it was interrupted. Although, I did try this 3 times (redownloading each time)
Any tips?
Thanks
You must have frozen and/or deleted some Blur apps as well as being rooted. Unless you have all the stock files from the firmware you are updating from, the install will fail.
I have unrooted the phone
However, I did use the "integrate system apps updates into ROM" option on TB.
I did not freeze anything
Will this work:
http://www.motorola.com/Support/US-EN/Atrix+Upgrade/Atrix-Gingerbread-Update
If not, what must I do?
Edit: Oh, and I also have AdFree installed and enabled. Should I revert?
mickeycohen said:
I have unrooted the phone
However, I did use the "integrate system apps updates into ROM" option on TB.
I did not freeze anything
Will this work:
http://www.motorola.com/Support/US-EN/Atrix+Upgrade/Atrix-Gingerbread-Update
If not, what must I do?
Edit: Oh, and I also have AdFree installed and enabled. Should I revert?
Click to expand...
Click to collapse
The sd card method will fail for you as well. Undo everything that required root access, including adfree...not sure if it will restore the modified files back to stock though, never used that app.
Exactly what happened to me. Successfully updated using Motorola Software Update
Hi
You have succeeded?
I am stuck for months trying to do this update...
It's absolutely frustrating...
I actually stopped trying. I got a RAZR a few weeks after I started this thread...
I might unlock the BL and install some ROMs to play with the Atrix but basically I don't use it anymore...
Anyway, I think the problem I was having was because I integrated updates into the ROM and I don't think it can be undone
Bootloader Unlocked?
If your bootloader is unlocked the update will most likely not work. Regardless, the link below has some useful information.
http://forum.xda-developers.com/showthread.php?t=1501532
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
scott500 said:
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
Click to expand...
Click to collapse
This is merely a rumor. The ATT link is to the old May 2014 update.
Pay no attention.
The link to the att sight yes is for old 1.58 build, does not mean there isnt an update coming...as its being reported with a build number by more and more sights, could just be a rumour but it could also be rolling out.
Well, they finally released the update today. Finally have 4.4.4. On my m8. Now to wait for lollipop
Does anybody know where the OTAPkg file gets downloaded to? I'm trying to preserve the file and not have to download it again and again after a fail update. Thanks.
Edit: n/m found it, it's under the FUMO folder within the internal SD.
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
johnnyutah22 said:
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
bford152 said:
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
Click to expand...
Click to collapse
I can't help you with CM12, but I just installed Viper One and it seems to work fine.
I updated to the 4.4.4 via OTA yesterday, and Viper installed without a hitch.
NB: Make a Nandroid Backup before flashing please.
Whats the best way to update my girlfriend's rooted M8? Currently running 4.4.2 rooted S-ON. Can she just take OTA and then will have to re-root?
I'm S-OFF on my phone so I haven't had to deal with this. Already updated my firmware months ago and have been running 4.4.4 roms.
Thanks!!
Downloading it now.
You'll have to re-flash stock recovery, take the OTA update, then restore twrp (or other custom recovery) and re-root.
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
jeremyenos said:
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
Click to expand...
Click to collapse
Yeah just manually change the date one day ahead and try it again. It might take a couple of secs for it to prompt that there is an update.
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Click to expand...
Click to collapse
There's a boot loader flashable twrp in the dev section posted by jball
dottat said:
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
Click to expand...
Click to collapse
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
johnnyutah22 said:
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
Click to expand...
Click to collapse
You can flash whichever you use.
I thought I read where this update would include the EYE Experience. Did I read that wrong or do I just not know how to use my camera anymore?
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Click to expand...
Click to collapse
I don't think root changes are the issue; as typically it will fail before it even goes into recovery with a message that the system has been modified. It might just be a bad download.
Setting up your phone again is really not that bad a proposition; especially if you use Titanium to restore apps. And it will also restore your Xposed installer and modules. Using Titanium, I can easily be up and fully configured again in about a half hour after a factory reset or RUU. Although, of course this will depend on the amount of customization in settings, etc.
You might consider updating with the new RUU (relocking bootloader required if s-on). Not only will this bypass the OTA install issue you are having, but makes for a cleaner install. Yes, you will have to set the phone up again; and you will also need to backup any data on internal storage, as it will be wiped by RUU.
Also, since it was previously rooted, can I immediately get to installing the OTA updates/most recent At&t updates for my device? Will they even be there? If not, can anyone leave me a link and explain how to do so after I finish the unrooting process? Thank you.
Also, I just found the rom page on HTC, and I think this is correct. I'm still on 4.4.2 anyways That, or 4.2.2 Not quite sure. Is it possible for me to just download this from the website? If that's the case, then I won't unroot it. My only gripe is that I can't uninstall anything on my phone even though it's rooted. When I restart, the app still remains. This is only with stock apps, of course. Anyways, with the HTC rom, if I have to flash this or something, etc., I'd need this to be explained.
Edit: I did find a youtube video in which I can get OTA updates on my phone, but it says that I need to have a twrp custom recovery. All I really did was root my phone and I have the super su app.
You need to relock the boot loader and then select unroot in super su options. You will also need to flash stock recovery if you want to receive OTAs.
This shouldn't delete any data.
I would recommend going s-off and flashing dev edition Rom. Quicker updates and no bloatware to deal with. Worked great for me.
Before doing so, just copy your contacts and messages to ext SD card. Reinstalling your apps isn't too much of an inconvenience considering you get out from under AT&T restrictions.
Sent from my HTC One_M8 in a van down by the river.
chevyjohn01 said:
You need to relock the boot loader and then select unroot in super su options. You will also need to flash stock recovery if you want to receive OTAs.
Click to expand...
Click to collapse
Relocking the bootloader typically wipes data and renders the phone unbootable (expect the RUU).
Also, it seems like you are suggesting the method or return to stock for OTAs. In that case, relocking the bootloader is not necessary. Relocking the bootloader is only required to RUU (not for OTA).
---------- Post added at 02:56 PM ---------- Previous post was at 02:50 PM ----------
Tiffianie said:
Also, since it was previously rooted, can I immediately get to installing the OTA updates/most recent At&t updates for my device? Will they even be there? If not, can anyone leave me a link and explain how to do so after I finish the unrooting process? Thank you.
Click to expand...
Click to collapse
For OTA, you need stock ROM (nothing modified in system partition - but from your subsequent statement it sounds like you were never able to, anyway) and stock recovery.
From there, and also as long as you are on AT&T's network, you should be able to get OTA updates. Root is okay (does not prevent OTA updates in itself). Unlocked bootloader is also ok.
You should be able to return to stock and OTA update without losing your data. However, you should always be backing up your data (and be able to restore it accordingly), if its that important to you. Your data is never guaranteed to be safe, even with normal day to day usage (much less OTA updates or rooting) and you should backup to avoid regret.
Tiffianie said:
My only gripe is that I can't uninstall anything on my phone even though it's rooted. When I restart, the app still remains. This is only with stock apps, of course. Anyways, with the HTC rom, if I have to flash this or something, etc., I'd need this to be explained.
Click to expand...
Click to collapse
Could have easily searched these forums for that answer. System partition (where the stock apps are stored) on this phone is write protected. Even with root, you need to install a kernel mod to disable write protection.
Tiffianie said:
Edit: I did find a youtube video in which I can get OTA updates on my phone, but it says that I need to have a twrp custom recovery. All I really did was root my phone and I have the super su app.
Click to expand...
Click to collapse
If you didn't install custom recovery, how did you root?
chevyjohn01 said:
You will also need to flash stock recovery if you want to receive OTAs.
This shouldn't delete any data.
I would recommend going s-off and flashing dev edition Rom. Quicker updates and no bloatware to deal with.
Click to expand...
Click to collapse
I probably won't unroot if I can try to get ota updates. How can I check what recovery I have installed? I downloaded flashify and backed up the current kernel through my drop box, so I'm not sure if that did a damned thing.