Develop Bugs

How to clear pending OTA's/OTA status messages?

I'm using the stock ROM rooted (don't know who distributed this one) and I'm getting a T-Mobile Update Service New Firmware Is Available message.
How do I not make this pop-up every day? Is the procedure different for each ROM? I thought most, if not all custom ROMs blocked these updates by default.
Searched but couldn't find a solution. Thanks.

For me it got to a point where I wasn't allowed to click cancel. I had to click download and after it downloaded it rebooted the phone and went to the flashing screen. Of course, not wanting to lose root, I didn't want it to apply. So I held down the Power button on the top of the phone and the update did not apply, but I would suggest you do it quick because it's not a very large update to apply. I don't know if the Power button to cancel an update is a real thing or if it just happened to work with me. But after I booted up my phone, the update notice was gone and I was worried that I had lost root as well, but I still have superuser permissions.

Go into Applications/ running services/ kill Htc Update and Tmobile update
Gets rid of it most of the time until reboot.

Anyone know how to make it not come up after rebooting? mines at the same point with the not letting me postpone but I rather not risk it and update and postpone

I'm assuming you guys are on SMR5 or 5r1...all you hafta do is get CR's OTA mod, its basically SMR5r1 with the OTA incorporated into it, so you'll never get that notfication cus you'll already have the OTA, and still have root and a2sd on the latest stock espresso. Plus bootanims work!
-BMFC
Sent from my T-Mobile myTouch 3G Slide using XDA App

by stock ROM rooted I thought he ment just that . the stock rom rooted ..meaning we just did the first root process ever and didnt flash anything over that

try updating the radio (check 3rd post in the slide rom bible; its the 8-5-10 one), that might work
there is also a new OTA coming up so there might be a new radio with that.
to flash radio... dload and put into sd card. boot into clockwork. DO A NANDROID BACKUP. then "apply to sd card". install zip from sd. click the zip for radio. install and reboot. there'll be an awkward image before reboot (normal).
also, next time PLEASE use the Q&A section.

[Q] LG Ally rooting with Froyo

Tried looking around but I haven't had much luck on this one. Since Froyo became available sometime around the 18th via the LG updater I have yet to see a way to root this thing. z4 and universal just don't work. Anyone have a method to this madness?
Note: This isn't my phone but really a work phone. The one my co workers and myself use is not really in need of root but my manager uses wifi tether like a crack addict and needs it. Right now I told him to just say no to the update since it's now being pushed via OTA.

Rooted Ally Froyo OTA update
I also have the same question kind of.. OTA Froyo update came this morning but we (my girls phone)have denied it because we use tether more than we want Flash someone Please let me know when Ally Froyo is Rooted. THX.

Well my wife has the LG Ally and since she's had it I've been playing with it. It actually took a bit to get the update to load, but once it did I realized I lost root. I didn't think much of it because I had backups, but restoring them didn't work which meant that I wasn't able to downgrade and try installing a rooted version.
I then found that I could download the Superuser app in a zip file and use it in a custom recovery to install as root.
First get the latest Superuser zip file for froyo, su-2.3.6.1-ef-signed.zip,here and put it on the root of your sdcard.
Then reboot into your recovery. The easiest way to get into the recovery is to power off the phone and then press SEND + MENU + tap END, keep tapping END until you see the LG screen. Once you see the LG screen you can let go.
Now you need to navigate through your custom recovery to use the zip file.
Amon-ra: Flash zip menu > Flash zip from sdcard > su-2.3.6.1-ef-signed.zip.
ClockWork: Install zip from sdcard > choose zip from sdcard > su-2.3.6.1-ef-signed.zip.
Once it is done loading reset and you should be good to go!
Credit goes to ChainsDD for the awesome app!

I am stuck at the reboot into recovery, since I did not have root prior to the upgrade to 2.2.1, I cannot install a custom recovery to finish this method. Any ideas? This version locks out the files I need to push to!!!

Well so far z4root no matter what version doesn't work, think it has to do with the patch they applied in 2.2.1 Superoneclick just gets stuck in a loop on rageagainstthecage so I'm at a loss. Android Forums has the long route on how to root but to be honest I know I will screw something up. Anyone have a solution? I was rooted before but I never installed a custom recovery as this a work phone.

If you turn off the phone and then plug it into the computer and hold SEND + MENU + hit END to turn it on does it stay with the screen that shows a white triangle, a !, and the android guy? If so see if you can use adb shell and have it connect with the phone. I'm not ever sure if after the update you can get into it. You can use either VOL-DOWN + HOME + tap END or the previous method. The last one should get you the bootloader and if you connect your phone here to your computer you should get a "fastboot" device installed, or something like that. If you can get here you can flash a custom recovery. I think there is a way to do it via the recovery as well. Once you can get into either of those we can get you root.

Rambler509 said:
I am stuck at the reboot into recovery, since I did not have root prior to the upgrade to 2.2.1, I cannot install a custom recovery to finish this method. Any ideas? This version locks out the files I need to push to!!!
Click to expand...
Click to collapse
try to re flash the phone with it again, if all else fails..... factory reset

lg ally wont root
Apparently I got my phone when verizon figured out a way to block all rooting apps. My LG Ally won't root using any of the suggested apps such as z4 root any version, superuser nor universal androot and I refuse 2 do that long drawn out process provided in newer manuals that's just ridiculous. We shouldn't b force 2 keep applications tht we don't want.

I didn't hv 2 update my phone it came with the 2.21 version alreayd installed. I did a factory reset twice and my phone won't work until I call verizon for them 2 reactivate it and once I do that all of the preinstall crap is already on phone as soon as its activated

It's too bad we don't have a method to root like on the Nook Color where you take a formatted SD card and boot from it...

c0ldburn3r said:
Tried looking around but I haven't had much luck on this one. Since Froyo became available sometime around the 18th via the LG updater I have yet to see a way to root this thing. z4 and universal just don't work. Anyone have a method to this madness?
Note: This isn't my phone but really a work phone. The one my co workers and myself use is not really in need of root but my manager uses wifi tether like a crack addict and needs it. Right now I told him to just say no to the update since it's now being pushed via OTA.
Click to expand...
Click to collapse
I haven't figured out how to re-root yet but I did find a suggestion somewhere in a forum that worked for tethering. Download the Quick Settings app (with the green gear icon) from the market and it gives you and option to turn on wifi hotspot without rooting. It'll bypass the fee Verizon charges while using the app they added in Froyo.

allywrecked said:
I refuse 2 do that long drawn out process provided in newer manuals that's just ridiculous. We shouldn't b force 2 keep applications tht we don't want.
Click to expand...
Click to collapse
While I agree that we should not have to keep apps on our devices that we do want or intend to use-if you want them gone-you MUST follow the "long drawn out process" to root the device and remove those apps. Otherwise-just deal with the apps being there.
JL

Also having issues
Having problems with z4mod application also. I tried rooting it with/without SD card in, connected/disconnected from the computer. The app runs, but it gets as far as "acquiring root shell" and then goes back to my home screen. No superuser app or busybox. I even tried installing busybox from the market and it just says Phone not rooted. Its kinda aggravating me. I'm kinda tired of tethering because of the net timeouts. Can't chat on IRC.
Android vers: 2.2.1

Rooted S-off and still getting ota update

My Dinc is rooted S-off and I'm still getting ota update notification. I tried to run the update and it does nothing....

If you're on a stock (even rooted) ROM, you'll get the ota notification. But it requires stock recovery to flash. I haven't looked into the actual zip, so I don't know if it'll flash via CWM or not. It used to not, and I doubt it's changed.

PonsAsinorem said:
If you're on a stock (even rooted) ROM, you'll get the ota notification. But it requires stock recovery to flash. I haven't looked into the actual zip, so I don't know if it'll flash via CWM or not. It used to not, and I doubt it's changed.
Click to expand...
Click to collapse
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.

I need to get the latest OTA update, but can I only get it through a new Rom or can I just gets new OTA update to work with my current Rom?
Sent from my PC36100 using xda app-developers app

Richard6292 said:
I need to get the latest OTA update, but can I only get it through a new Rom or can I just gets new OTA update to work with my current Rom?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
You have to be complete stock to sucessfully update ota. Just flash the stock 4.08.605.15 rom in the dev section. You'd be getting the same thing, without all the hastle of ruu'ing, updating ota, and then rerooting.

Thanks for the info! But after that, if I were to relfash my current Rom I'd just be back in the same situation right?:/ I wish my current Rom would be update but the dev'r went away..
Sent from my PC36100 using xda app-developers app

Richard6292 said:
Thanks for the info! But after that, if I were to relfash my current Rom I'd just be back in the same situation right?:/ I wish my current Rom would be update but the dev'r went away..
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Right, if your current rom is not based on 4.08.605.15, then you will get the ota notification. Even if you got the actuall ota to install, it would more than likley mess up the rom, and then you would have to reflash the rom and you would be right back where you started. If you want to stay on your current rom but stop the ota notification, do as i said a couple posts above and edit the build.prop file to make the update server think you already have the latest ota. What rom are you currently on?

Ok, thanks for the help!!
Sent from my PC36100 using xda app-developers app

I am using TOB so can I install the update without messing things up?

joeyz400 said:
I am using TOB so can I install the update without messing things up?
Click to expand...
Click to collapse
No tob has stock apps removed and is deodexed. The ota checks to make sure all original apps and files are present and unchanged. If you wabt to get the actuall ota tou need to ruu to stock 4.06.605.3 and then ota to 4.08.695.2 and then ota to 4.08.605.15. However tob V2.1 has been updated to 4.08.605.15 already.

Experience with this OTA update
I can't post yet to the development forums and I saw that cmlusco was on here so just wanted to share my experience. I have an SMOLED Droid Incredible and I'm rooted, S-OFF on the latest CWM recovery and I was using wildstang's stock ROM from the last update back in November 2011. I got the notification, searched the forums, and ended up installing cmlusco's stock deodexed ROM, after doing all the requisite wipes and checking the md5. My initial experience was great, apart from once when the phone simply died with a black screen and was completely unresponsive. Battery pull solved that. After I was done getting all my apps back on there (mostly via downloading and then for some of them just restoring the data from Titanium Backup), I did a Titanium Backup and a nandroid backup in the recovery. After all of these were done, I started having quite a few freeze issues. I think I had three in a row before I had one while in the process of connecting the phone to my computer. Had to do the battery pull method each time but the last time, the phone must have been right in the middle of mounting to my laptop because all of my downloaded apps were "gone". As in, they were not in the app drawer and all the icons were the default Android icon on the home screens. I think something happened with the freeze in the middle of the mount. If I reinstalled an app from the market and tried to restart it, it force closed. Then, if I uninstalled and reinstalled it, it did work. But I was still getting some force closes so I figured it might just be easier to flash the ROM again, which is what I did.
So now I'm back up and running, and mostly everything is okay. I did get another freeze while installing an app and waited for a while but since the phone was still unresponsive, I did the battery pull again. Stuff is working but I thought I'd share my experience and see if anyone else had something similar happen. Oh, by the way, I also updated to the latest radio but hadn't the first time I used this ROM. And cmlusco, thanks a lot for posting that and being very patient in the forums. If this ROM fails again, I might try Touch of Blue.

cmlusco said:
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
Click to expand...
Click to collapse
Thanks, I changed that line and the annoying system update is gone

cmlusco said:
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
Click to expand...
Click to collapse
So, I edited the "ro.build.fingerprint" line, and I'm still getting the notification... I've tried the "fix" of renaming the /etc/security/otacerts.zip file to otacerts.zip.bak, which some suggest. Hell, I even ended up deleting the whole file. When that didn't work, I froze /system/app/updater.apk. Still nothing, so I deleted that file as well. Nothing is listed in my /cache folder, where some people have noted that the download stores itself. I had the 4.08.605.15 update before, and it caused my phone to freeze a lot, and randomly reboot over and over for hours. During those reboots, half my apps got deleted as well.
Needless to say, I don't want the stupid update!! But nothing I can find on any forum is stopping my phone from getting the notification every 15-20 minutes. I've tried flashing a few different ROMs, but my phone gets stuck in a boot cycle with any of them. Just the other day, I went to flash the newest CyanogenMod through CWM, and it just kept showing the blue android guy on a skateboard for (no joke) about 3 hours. I ended up pulling the battery and flashing my stock recovery.
Please let me know if there's anything else anyone can think of that might stop the notification. I'm still 3 months out from being eligible to upgrade my phone, and I'd rather not deal with the notification popping up over and over and over for that time
Thanks

ggoodman1022 said:
So, I edited the "ro.build.fingerprint" line, and I'm still getting the notification... I've tried the "fix" of renaming the /etc/security/otacerts.zip file to otacerts.zip.bak, which some suggest. Hell, I even ended up deleting the whole file. When that didn't work, I froze /system/app/updater.apk. Still nothing, so I deleted that file as well. Nothing is listed in my /cache folder, where some people have noted that the download stores itself. I had the 4.08.605.15 update before, and it caused my phone to freeze a lot, and randomly reboot over and over for hours. During those reboots, half my apps got deleted as well.
Needless to say, I don't want the stupid update!! But nothing I can find on any forum is stopping my phone from getting the notification every 15-20 minutes. I've tried flashing a few different ROMs, but my phone gets stuck in a boot cycle with any of them. Just the other day, I went to flash the newest CyanogenMod through CWM, and it just kept showing the blue android guy on a skateboard for (no joke) about 3 hours. I ended up pulling the battery and flashing my stock recovery.
Please let me know if there's anything else anyone can think of that might stop the notification. I'm still 3 months out from being eligible to upgrade my phone, and I'd rather not deal with the notification popping up over and over and over for that time
Thanks
Click to expand...
Click to collapse
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.

nschiwy said:
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
Click to expand...
Click to collapse
Also you must be s-off, or adb pull edit and push the file while in recovery.

Try flashing this. Got rid of the nagging when I was on GB. Should take care of it.
http://db.tt/zPhTShuA
sorry...I was on the phone...

nschiwy said:
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
Click to expand...
Click to collapse
It is definitely in r/w mode. I restarted the phone, cleared cache, then checked the file again to make sure the edit was still there. And it was...
cmlusco said:
Also you must be s-off, or adb pull edit and push the file while in recovery.
Click to expand...
Click to collapse
I've had s-off since a few days after I got the phone last year.
omniatic said:
Try flashing this. Got rid of the nagging when I was on GB. Should take care of it.
http://db.tt/zPhTShuA
sorry...I was on the phone...
Click to expand...
Click to collapse
I restored from a prior backup to undo all the changes I made, so I'm going to try each of the methods again, and if nothing works, I'll flash this.
Thank you all. I've been relying too much on "one-click" solutions in the past, but I'm now trying to get more into the actual dev side of things, so I can help out with this kind of stuff as well

ggoodman1022 said:
It is definitely in r/w mode. I restarted the phone, cleared cache, then checked the file again to make sure the edit was still there. And it was...
I've had s-off since a few days after I got the phone last year.
I restored from a prior backup to undo all the changes I made, so I'm going to try each of the methods again, and if nothing works, I'll flash this.
Thank you all. I've been relying too much on "one-click" solutions in the past, but I'm now trying to get more into the actual dev side of things, so I can help out with this kind of stuff as well
Click to expand...
Click to collapse
I retried all the methods, and flashed the file mentioned above. Still no luck
Stupid notification pops up over and over and over... Guess I may either have to update, or deal with the notification until October when I can upgrade my phone. Or try flashing a custom ROM, even though I like the stock ROM

You could always flash cmlusco's touch of blue ROM which is an optimized version of the latest OTA, so you wouldn't have to worry about update notifications on that one for sure (at least on the latest version).
http://forum.xda-developers.com/showthread.php?t=1492720
but there are lots of options here
http://forum.xda-developers.com/forumdisplay.php?f=638

Android update!

Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend

Throws a signature verification failed error.

Try again with the new method

Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.

Why go to 2.3.6? It´s better than 2.3.5 customized?

Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara

AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.

narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.

narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.

Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.

can't update to 4.4.2 OTA

Hello, my phone recently notified me that a 4.4.2 android OTA update is available (i have a AT&T SGH-i747) however once it reboots, it will get to about 29% complete, then i get the "Update failed" message, and it reboots back into android (4.3) and i was wondering how i could get it to work?
(i'm using stock rom, i've NEVER flashed anything on it before, only thing i've done is root it to use titanium backup, however i used the saferoot thing so as to not flip the knox security stuff)

You need to unroot.

audit13 said:
You need to unroot.
Click to expand...
Click to collapse
do i have to do something special to do that? or can i just click the "Full unroot" button in the SuperSU settings tab to unroot my phone

You also need stock recovery and, preferably, all of the ATT apps on your phone. I have read that removing too many ATT apps will prevent the OTA update from completing.
I have never tried removing root that way so I cannot comment.
You should also make note of the fact that it is possible to have something go wrong during the OTA process which may result in the loss of your data. I recommend at least backing everything up to your external SD card and removing the SD card during the OTA update process.

like i said, i only rooted to use titanium backup to restore a backup for a game save, that's all i've ever done (so if that undid stock recovery, or removed AT&T apps without me telling it to, then how would i fix that)

In that case, just unroot and then run the OTA update. Titanium backup would not alter the recovery or remove apps.

well, i have 5 hours to wait before doing so, after unrooting (using the saferoot unroot.bat file, then using supersu's unroot after that to finish the process as the saferoot program said to do) i went to click check for updates, and instead got "Your device is running the latest version" and "you may check again in 5 Hours 0 Minuties" which i'm assuming is because it failed last night when i tried to update it?

So everything is completely stock? Does it say custom on the download screen or anywhere in the About section of the phone.

audit13 said:
So everything is completely stock? Does it say custom on the download screen or anywhere in the About section of the phone.
Click to expand...
Click to collapse
nope, doesn't say custom anywhere on the about phone screen, will check the download mode now

logoster said:
nope, doesn't say custom anywhere on the about phone screen, will check the download mode now
Click to expand...
Click to collapse
sorry for double post, just checked download mode, says i'm completely stock and official
also thought i'd mention that the check again later timer is going down, it's at 4 hrs and 3 minutes

You could also try booting into recovery and wiping cache and Dalvik. Don't wipe data.

nope, still has a timer, but it's fine as it is going down, i have about 2hrs and 47 Mins left according to it

Sorry for double post again, but timer finished, and update worked flawlessly, so unrooting did work, thanks
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app