I rooted once upon a time using Kingo Root. Worked fine, love being rooted, been doing it for years. But as everyone knows, the GPS signal is really crap on these phones. Mine keeps cutting out randomly.
Lo and behold! KitKat is now available! And among the changes AT&T is bragging about is improved GPS performance. As much as I enjoy being rooted, I need a working GPS a lot more. So I tried installing the OTA update... but it failed. I assume because the device status is listed as "Custom".
So I used Triangle Away, did a full unroot using SuperSU, rebooted... and it still says "Custom". There didn't used to be an open padlock during boot while I was rooted, but now there is, along with the word "Custom". Check the Odin mode, and sure enough it says the system status is "Custom". However Knox flag is still 0x0, and it states I'm running the Samsung Official binary. I've never flashed a ROM on this phone, all I did was root it.
Re-rooted, installed Triangle Away again. It states my system status is "Official" and the flash counter is at 0. However whenever I check the Device status in settings, it always says "Custom". There doesn't appear to be any way to get it back to "Official". Sometimes I can get it to say "Official" for a single boot, but then it always reverts back to "Custom" within a couple minutes whether the phone is rooted or not.
What am I doing wrong?
After unroot, you need to do a factory reset, then boot into your recovery, wipe cache, reboot your phone few times the pad lock and custom logo should go away. I am not sure about the "Device status in settings" showing custom, mine always shows official.
GoremanX said:
I rooted once upon a time using Kingo Root. Worked fine, love being rooted, been doing it for years. But as everyone knows, the GPS signal is really crap on these phones. Mine keeps cutting out randomly.
Lo and behold! KitKat is now available! And among the changes AT&T is bragging about is improved GPS performance. As much as I enjoy being rooted, I need a working GPS a lot more. So I tried installing the OTA update... but it failed. I assume because the device status is listed as "Custom".
So I used Triangle Away, did a full unroot using SuperSU, rebooted... and it still says "Custom". There didn't used to be an open padlock during boot while I was rooted, but now there is, along with the word "Custom". Check the Odin mode, and sure enough it says the system status is "Custom". However Knox flag is still 0x0, and it states I'm running the Samsung Official binary. I've never flashed a ROM on this phone, all I did was root it.
Re-rooted, installed Triangle Away again. It states my system status is "Official" and the flash counter is at 0. However whenever I check the Device status in settings, it always says "Custom". There doesn't appear to be any way to get it back to "Official". Sometimes I can get it to say "Official" for a single boot, but then it always reverts back to "Custom" within a couple minutes whether the phone is rooted or not.
What am I doing wrong?
Click to expand...
Click to collapse
Did you delete system (AT&T) apps?
coolmingli said:
After unroot, you need to do a factory reset, then boot into your recovery, wipe cache, reboot your phone few times the pad lock and custom logo should go away. I am not sure about the "Device status in settings" showing custom, mine always shows official.
Click to expand...
Click to collapse
Yep, I did all of that. Exact procedure:
- Reset flash counter using triangle away
- full unroot using SuperSU
- reboot immediately into Odin mode (system status says "Official")
- reboot immediately into recovery, do a factory reset
- reboot immediately into Odin mode (system status still says "Official")
- reboot immediately into recovery, do ANOTHER factory reset (because I'm anal that way)
- reboot immediately into Odin mode, (system status STILL says "Official")
- reboot normally, go through normal first-time setup, go into settings, check Device status... it says "Custom"
- reboot into Odin mode, system status now says "Custom"
- reboot normally, stupid open padlock is there again with the word "Custom"
- countless reboots later, it still says "Custom"
serpent2005 said:
Did you delete system (AT&T) apps?
Click to expand...
Click to collapse
Nope, none. They're all still there. Like I said, I'm still running the bone stock image, never flashed a ROM, and I never edited the image. I only use root for things like GMD S-pen control, Titanium Backup, and FS Trim.
What's really annoying is that damn open padlock is never there while the system really IS modified, it only shows up when I unroot and everything is back to stock. I call it irony.
Would region lock be affecting this? I disabled the region lock many moons ago using RegionLock Away. Does that survive after a factory reset, and would it cause my device status to show up as Custom?
Nope, restoring the region lock did not fix the problem. It continues to revert to "Custom" Device status no matter what I try. This is infuriating.
GoremanX said:
Nope, restoring the region lock did not fix the problem. It continues to revert to "Custom" Device status no matter what I try. This is infuriating.
Click to expand...
Click to collapse
This is what you need to do
http://forum.xda-developers.com/showthread.php?t=2559715
it fully returns your phone to stock. and you can get your OTAs again at that point.
the2rrell said:
This is what you need to do
http://forum.xda-developers.com/showthread.php?t=2559715
it fully returns your phone to stock. and you can get your OTAs again at that point.
Click to expand...
Click to collapse
I tried that too. Didn't work. Still says "Custom". However, part of those instructions failed for me, the Heimdall image upload did not work at all. Never could figure out why.
GoremanX said:
I tried that too. Didn't work. Still says "Custom". However, part of those instructions failed for me, the Heimdall image upload did not work at all. Never could figure out why.
Click to expand...
Click to collapse
they work, it maybe your PC, i know Heimdall can be a bugger at times. It DOES work though. have you tried another PC if that is an option.
the2rrell said:
they work, it maybe your PC, i know Heimdall can be a bugger at times. It DOES work though. have you tried another PC if that is an option.
Click to expand...
Click to collapse
I just tried it from my laptop, same result. The MI9_fix.img.ext4 file refuses to upload to my device. The instructions state it should fail at 95%, but it always fails immediately. I tried downloading the file multiple times from different mirrors to make sure I wasn't getting a bad one. The result is always:
Uploading SYSTEM
0%
ERROR: Failed to send file part packet!
ERROR: SYSTEM upload failed!
GoremanX said:
I just tried it from my laptop, same result. The MI9_fix.img.ext4 file refuses to upload to my device. The instructions state it should fail at 95%, but it always fails immediately. I tried downloading the file multiple times from different mirrors to make sure I wasn't getting a bad one. The result is always:
Uploading SYSTEM
0%
ERROR: Failed to send file part packet!
ERROR: SYSTEM upload failed!
Click to expand...
Click to collapse
you have all the drivers and everything loaded up?
thats odd.
Yep, everything called for in the instructions. I get the same result every time.
Did I mention how infuriating this is?
GoremanX said:
Yep, everything called for in the instructions. I get the same result every time.
Did I mention how infuriating this is?
Click to expand...
Click to collapse
Yes but it should work, another member just did the same thing you are trying to do. with success. it has to be drivers or maybe running odin as a admin.
Oh and you may want to move the Odin file to a folder on your desktop or just put them on your desktop and try that. im betting its something simple that we are just over looking.
Finally got it restored to factory. Just about everything that can go wrong did go wrong. My USB cable failed. Then my SD card failed and was spitting out garbage. And one of my downloaded files was corrupted. At one point, I got the status back to "Official", but the phone was so screwed up it was nearly unusable, spitting out error messages every 30 seconds. When this happened, I took it to a local AT&T store hoping they would just flash a new image on there (it did say "Official" in all the right places after all). But all they wanted to do was replace it with a refurb unit. Screw that! So I went home and tried AGAIN, re-downloading everything and using an all new USB wire and SD card, and this time it worked like a charm.
Now I'm attempting to install the OTA update, hopefully all goes according to plan.
Nope, complete failure. Update to NB4 worked fine, but then the update to KitKat failed at 27%. The MJ5 image being used in that thread is not a stock image. It's "fixed" to allow rooting.
Maybe I'll take that refurbished phone from AT&T after all... bastards
GoremanX said:
Nope, complete failure. Update to NB4 worked fine, but then the update to KitKat failed at 27%. The MJ5 image being used in that thread is not a stock image. It's "fixed" to allow rooting.
Maybe I'll take that refurbished phone from AT&T after all... bastards
Click to expand...
Click to collapse
That is stock. It's not prepared for root. You can choose to root or not. I have not updated so I don't know. But if you made it to nb4 why do think it would do that if the mj5 was fixed for root right
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Nah, everyone else in the same situation as me has the exact same problem:
http://forum.xda-developers.com/showthread.php?t=2686652&page=21
We're talking dozens and dozens of attempts by sozens and dozens of people here. Downgrading to the MJ5 image in that restore thread does not actually bring the phone back to stock. The NB4 upgrade apparently just doesn't have the same level of verifying in it as the KitKat update. The author of that thread specifically mentions that the MJ5 image he's listing has been modified to allow rooting using his method, but the rooting part of it is optional. Either way, the image itself has been modified. That's why it has the word "fix" in the filename.
Others have stated that going to an AT&T retail location and having them flash a real MJ5 image DID work, and allowed the KitKat update to happen without issues.
Related
Hopefully you guys know there is a software fix out from at&t and samsung that fixes gps problems and etc...
goes without saying you can't just straight update if you're rooted. That's where i'm stuck.
Before i touched anything, it would get to 50% and reboot, says the update was not applied.
Then I tried "unrooting" even though it said it was unrooted, and apps requiring SU backed this up saying my phone was unrooted.
Then during the update, it stops even sooner at "preparing".
So... how do we get around this without doing the master clear with odin3???
I DON'T want to lose all my data. I'm too lazy.
Mine said failed at 100%. I def got the jh7 update though. My phone was unable to reboot into recovery using the three button method. Now I can. My phone was rooted with stock rom.
Mine is rooted with the Voodoo fix and it failed during the update (I was at work so don't know at what step during the update).
Will have to do the voodoo-lag unfix - restore back to factory defaults and try it again..
Unless of course someone pops out a tweaked ROM before then!
check out this thread, http://forum.xda-developers.com/showthread.php?t=789546 so we can get everyone with this issue together in one thread
I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
ace_case said:
I am having difficulties updating to the newest system update on the stock rom. I am rooted and have unlocked my bootloader, so that may have something to do with it. I am also running on straight talk, but I doubt that would be an issue, as it says it's already downloaded it and it just needs to install it. When I click install now, it turns the phone off, does the little thingy, then reboots. Upon rebooting, everything loads up, and a popup appears saying that the update failed, and then every hour it pops up asking to update. Do you know why this is happening and how to fix it, or a way to permanently suppress this popup?
Click to expand...
Click to collapse
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
skeevydude said:
You need to be completely stock to take the OTA. If you haven't flashed Mex or Bell, I have a zip, maybe flashable (can't test, broke phone) that contains a completely stock /system. Or you can just backup your apps and flash the stock AT&T fastboot.
Post with link to zip.
Click to expand...
Click to collapse
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
ace_case said:
Is there a way to just suppress the update? I am a little wary of flashing etc. after the close call my first time...
Click to expand...
Click to collapse
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
palmbeach05 said:
Yes, you clear the cache. But if you want to leave yourself open to be vulnerable to the Heartbleed bug, a pretty serious security issue, then by all means, leave your front door unlocked so hackers can tap into your device and take anything they want.
Click to expand...
Click to collapse
I'd say it's more like posting on Craigslist that you're going on vacation and then leaving all the doors open with your debit/credit card on the coffee table. It's a pretty serious bug, and according to wikipedia, 1.5% of the most popular 800,000 websites are still vulnerable to the bug, not to mention running a sideloaded app or connecting to a malicious website.
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
Flashing back to completely stock may be the easiest way to get the update.
lilred91 said:
got the same issue on one of my atrix hd's but not the other. On mine that I unlocked the bootloader and rooted myself took the ota update but the other which was bought in the same condition will not and just keeps giving an error. trying to figure this out now so will update.
Click to expand...
Click to collapse
If you flash the OTA update manually using something like Philz recovery, you can see the progress on the screen and where it stops updating. For me, it kept hanging on updating the smartactions.apk, which was because I had previously (long time ago) merged updates of the app to my System partition (along with a few other apps that were updated). This will mess up any attempt to do an OTA update, because your "stock" ROM is no longer stock.
I ended up having to flash back to the real stock with Mythtools, then install the OTA zip manually.
If you can't find the zip in your cache, you can download it directly from this post (thanks @skeevydude): http://forum.xda-developers.com/showpost.php?p=52657363&postcount=13
Is it possible? I want to fully downgrade. Not sure if it's the 444 update but Bluetooth music playback is HORRIBLE, Chromecast playing is all jacked up... I want to downgrade to 442 and see if it fixes my issues
Tell us more about the problem and are you rooted? Someone may have a fix before you go back.
I've noticed a lot of issues as well. I have the regular S5. Radio is $#!+. Google+ gets activated by my alarm clock. My alarm clock causes my phone to freeze when it goes off and is locked. None if the AT&T apps work properly (so I disabled them). Uber hates me. WiFi is, at best, unstable. Add all this to network issues not present in 4.4.2, and just generally $#!tty performance.
Okay. Downgraded to NE4 and all my issues were gone. Flashed the stock rooted OA1 zip and kernel, still fine. I blame it on a jacked OTA update
joe3681 said:
Okay. Downgraded to NE4 and all my issues were gone. Flashed the stock rooted OA1 zip and kernel, still fine. I blame it on a jacked OTA update
Click to expand...
Click to collapse
brother please please give me the link of NE4 for 870A ?
I'll upload it somewhere...
http://www.sammobile.com/firmwares/download/31669/G870AUCU1ANE4_G870AATT1ANE4_ATT/
SamMobile sucks and its a PITA.
Download this, extract put in PDA slot of Odin: https://www.androidfilehost.com/?fid=23622183712467373
Install via stock recovery?
1/2 awake 1/2 asleep earlier. Tried to dump root to get ready for OTA. Now i am stuck @ padlock splashscreen. Not sure, but maybe cause I still had exposed running? Actually booted at 1st, but still had root checker and she said i was still rooted--not to mention-and open padlock k still there. That's when I said, "Oops! x-posed.
Rather than going 1 module @ a time & clear data, force stop etc....I just uninstalled the Exposed installer & hoped he developed a Pied Piper complex & take the crowd (modules)with him.
Odin seems to be working' alright. I get the blue indication saying my drivers are installed. It goes all green with 1 success/0 failures. As soon as all looks good, that damn MTP USB fail shows up like Cousin Eddy @ Christmas. The circle is complete. Right back to stuck padlock splashscreen.
The needed driver(s) got installed on laptop. When I read their properties & try to install, I get the "file already exists,would you like to overright?" Diagnoses with a right click or the like says app is fine.. Another battery pull begs to differ. If I see that error 10 while installing one more time....
Ok,my ? is, Can I put this onto my ex sd card in this tablet, unmount it & put it in in my soft bricked phone afterwards? Like another battery pull would make a big difference.
.
,
gitardan17 said:
1/2 awake 1/2 asleep earlier. Tried to dump root to get ready for OTA. Now i am stuck @ padlock splashscreen. Not sure, but maybe cause I still had exposed running? Actually booted at 1st, but still had root checker and she said i was still rooted--not to mention-and open padlock k still there. That's when I said, "Oops! x-posed.
Rather than going 1 module @ a time & clear data, force stop etc....I just uninstalled the Exposed installer & hoped he developed a Pied Piper complex & take the crowd (modules)with him.
Odin seems to be working' alright. I get the blue indication saying my drivers are installed. It goes all green with 1 success/0 failures. As soon as all looks good, that damn MTP USB fail shows up like Cousin Eddy @ Christmas. The circle is complete. Right back to stuck padlock splashscreen.
The needed driver(s) got installed on laptop. When I read their properties & try to install, I get the "file already exists,would you like to overright?" Diagnoses with a right click or the like says app is fine.. Another battery pull begs to differ. If I see that error 10 while installing one more time....
Ok,my ? is, Can I put this onto my ex sd card in this tablet, unmount it & put it in in my soft bricked phone afterwards? Like another battery pull would make a big difference.
.
,
Click to expand...
Click to collapse
In this threadhttp://forum.xda-developers.com/showthread.php?t=3025119
Did you use the tar in the troubleshooting section?
No, the tars from "how to root" . Worked the 1st time. Since it unrooted & unsafestrapped before,thought it would do tbat again. Tried to Odin down like i did about a month ago. Kept saying i was still on 4.4.4 AND still rooted with my center clock w/seconds still in my status bar. i than read to use my supersu to unroot. I uninstalled just the xposed installer. That also worked about a month ago. Then i used supersu to unroot followed by the Odin down attempt since it still said A01 & 4.4.4 & still center clock. After that Odin attempt, stuck at either padlock or grey battery indicator in the middle if i plug in after a battery pull and a try at clean cache& clean data then reboot. When that doesnt work, the Odin try again.
gitardan17 said:
No, the tars from "how to root" . Worked the 1st time. Since it unrooted & unsafestrapped before,thought it would do tbat again. Tried to Odin down like i did about a month ago. Kept saying i was still on 4.4.4 AND still rooted with my center clock w/seconds still in my status bar. i than read to use my supersu to unroot. I uninstalled just the xposed installer. That also worked about a month ago. Then i used supersu to unroot followed by the Odin down attempt since it still said A01 & 4.4.4 & still center clock. After that Odin attempt, stuck at either padlock or grey battery indicator in the middle if i plug in after a battery pull and a try at clean cache& clean data then reboot. When that doesnt work, the Odin try again.
Click to expand...
Click to collapse
Use the tar in troubleshooting section should work
Thanks Joe 3681. My SM-G 870A is up & running again. Odin actually took its time & progress bar went at a normal speed. With those tars I used about a month ago, progress bar went very fast right back into a softbrick. I could just tell it was working this time.
Any idea on why it doesn't allow me to put that file on odin, wont even show up in files when i click on the ap button and search for it? is it because its a rar file and odin only reads tar, etc. files? do i need a certain program that extracts that file?
Hello, I just today found out about the update to the Lollipop 5.0. I checked and attempted the download. It got all the way to the restart and install and then it stopped and instantly booted back up. It came up with the notification "Update Interrupted" or something very similar. I tried again after resetting the phone back to factory mode. It did the same thing. I have seen people have the problem of not enough storage but i had plenty. Especially after the factory reset. I know that this is an over wifi update and i am trying to understand why my phone isn't accepting it or why it isn't working. Thank you for any help you can offer.
Alan1727 said:
Hello, I just today found out about the update to the Lollipop 5.0. I checked and attempted the download. It got all the way to the restart and install and then it stopped and instantly booted back up. It came up with the notification "Update Interrupted" or something very similar. I tried again after resetting the phone back to factory mode. It did the same thing. I have seen people have the problem of not enough storage but i had plenty. Especially after the factory reset. I know that this is an over wifi update and i am trying to understand why my phone isn't accepting it or why it isn't working. Thank you for any help you can offer.
Click to expand...
Click to collapse
If you have rooted or modified the system apps in any way then the update is going to fail. You have 2 options:
You can wipe your phone and start with a clean stock ROM; or
You can follow the guide to retain root on OC6. You don't have to be rooted for this method, but this method will allow you to update if you've modified your system.
Devo7v said:
If you have rooted or modified the system apps in any way then the update is going to fail. You have 2 options:
You can wipe your phone and start with a clean stock ROM; or
You can follow the guide to retain root on OC6. You don't have to be rooted for this method, but this method will allow you to update if you've modified your system.
Click to expand...
Click to collapse
My system has been rooted before but it no longer has root access.
When you say wipe and start with a fresh rom, isnt that also the same as resetting the device?
Alan1727 said:
My system has been rooted before but it no longer has root access.
When you say wipe and start with a fresh rom, isnt that also the same as resetting the device?
Click to expand...
Click to collapse
To explain a bit further, the way the update works is there's a program built into the OTA. This program checks the signature of all the system files on your phone against a database included in the OTA. If all the signatures match then the update will proceed, but if even 1 of the signatures doesn't match then the update will fail as you have experienced.
When you root your phone you are exploiting a weakness in some aspect of android that allows you to modify system files. Once you modify system files by rooting you change their signature. Even if you unroot, it is impossible to change the signatures back to what they originally were. This is the reason that even if you unroot the update will fail.
By resetting the device you are essentially deleting all the user apps and settings, the system files go virtually unchanged. So if you unroot, your signatures still don't match and when you factory reset the device the system files don't get touched so the signatures still won't match. The only thing you can do to get the signatures to match is to flash the NE3 full Odin package. This will completely wipe out our phone and install everything (the bootloaders, modems, system files, etc.) from scratch.
So like I said you have 2 options:
Follow the guide I linked to above; or
Flash the NE3 Odin package and take the OTA.
Either way you have to use Odin at some point.
I have (or had) an AT&T branded S5 that was previous rooted and running Safestrap (I don't recall the BL version). Due to some EXTREME idiocy on my part, I took an OTA update two days ago, which updated and synched everything to G900AUCU2ANG3.
Naturally, this borked root. But there's some weirdness going on. Even after the OTA update, the phone's device status still says "Custom". And I still see the custom text when the phone boots. Is this Knox related?
Further oddness is that the phone keeps trying to pull down a second OTA update that looks identical to the first based on the filesize (over 400 MB). It goes through the motion, boots into recovery, and starts installing this second update, but stops partway through. Upon rebooting, the phone tells me the update was interrupted and can't be installed.
I realize I may never get root back, but I'm alarmed the phone's status still says "Custom" and that it's trying (and failing) to install this second OTA update.
I've tried factory resetting the phone, both within KitKat and via recovery, but these issues remain. Should I just reapply NG3 via Odin?
Thanks in advance!
fleggett1 said:
I have (or had) an AT&T branded S5 that was previous rooted and running Safestrap (I don't recall the BL version). Due to some EXTREME idiocy on my part, I took an OTA update two days ago, which updated and synched everything to G900AUCU2ANG3.
Naturally, this borked root. But there's some weirdness going on. Even after the OTA update, the phone's device status still says "Custom". And I still see the custom text when the phone boots. Is this Knox related?
Further oddness is that the phone keeps trying to pull down a second OTA update that looks identical to the first based on the filesize (over 400 MB). It goes through the motion, boots into recovery, and starts installing this second update, but stops partway through. Upon rebooting, the phone tells me the update was interrupted and can't be installed.
I realize I may never get root back, but I'm alarmed the phone's status still says "Custom" and that it's trying (and failing) to install this second OTA update.
I've tried factory resetting the phone, both within KitKat and via recovery, but these issues remain. Should I just reapply NG3 via Odin?
Thanks in advance!
Click to expand...
Click to collapse
What does your "android version" say in settings. If your still on 4.4.2 you can downgrade bank to nce and reroot with towel root.
dirtydodge said:
What does your "android version" say in settings. If your still on 4.4.2 you can downgrade bank to nce and reroot with towel root.
Click to expand...
Click to collapse
Yes, I'm still on 4.4.2. Like I wrote in my OP, though, I'm VERY concerned that this second OTA update keeps failing. I'm also perplexed as to why the device is still in some sort of custom state since I thought taking the OTA update would, in essence, reset everything except user data.
Is my phone borked in some way? I mean, it works just fine otherwise, but the device's inability to install this second OTA update really sticks in my craw.
I might reapply NG3 via Odin and see what happens. Couldn't hurt, right?
fleggett1 said:
Yes, I'm still on 4.4.2. Like I wrote in my OP, though, I'm VERY concerned that this second OTA update keeps failing. I'm also perplexed as to why the device is still in some sort of custom state since I thought taking the OTA update would, in essence, reset everything except user data.
Is my phone borked in some way? I mean, it works just fine otherwise, but the device's inability to install this second OTA update really sticks in my craw.
I might reapply NG3 via Odin and see what happens. Couldn't hurt, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3149146
If you want root, go to the OP in that post, scroll down to step 4 or the notes section and download the "downgrade to nce.zip" flash that in odin "ap" slot. Then root with towel root. After that you can either download titanium backup and fees the ota's or use that same thread to upgrade to the OF2 version and keep root.
Edit:
If you want to just take the OTA's and not root your phone then still download the "downgrade to nce.zip" flash in odin but don't root. The ota's will push through with no problem then. But you won't be able to downgrade and root if you take the OTA's all the way up to oc4 i believe.