Database Users

Help updating from 2.3.15

So I've been on rubix focused for a while and I didn't really want to update to 2.3.320 (leak) but now I heard we have 2.3.340 (official). Can someone explain how I can get to this from 2.3.15. And will I have to update the rom I'm using or would it work? Sorry I tried to figure this out myself and almost bricked my phone. So now I'm kinda stuck and need some help
Thanks!

I am in the same boat. I am on 2.3.20 . I'm not really sure how I got to this version in the first place. I'm on rubiX 1.8.6 . How do I update to the latest and greatest, and what version is that actually?
Thanks in advance.

There are going to be plenty of people here that will chime in to help...but I just got done (literally) doing this today. I was on 2.3.15 OTA (rooted) running ApeX and wasn't even going to go through the hassle. But...ever since the Gingerbread sdk was released and all of these fresh new roms & themes are popping up...I finally said F it and did it. The basics of it go like this:
1. Backup everything etc...
2. You need to find yourself a copy of 2.2 ota stock, download to pc and flash that to your phone using rsd lite 4.9
3. Then you can pull the update down from your phone (takes 5 minutes from beginning to end)
4. Use Z4root and root your phone (was able to get root on my first try in under a minute)
5. Create another backup and be sure to name it 2.2.1 stock so you now have a starting point to fall back on when you start tweaking your phone.
This is my personal fave go to page that I use as a guide to any and all of my X mods. It doesn't get much better than this if you ask me!
Roooler's Guide to All Things X

If you don't have a stock backup with all bloatware intact, it'll be easier to SBF. If you have a stock backup, flash it, ensure all bloat is there, and download update and install. I removed bootstrap to be on the safe side.

Droid-Xer said:
If you don't have a stock backup with all bloatware intact, it'll be easier to SBF. If you have a stock backup, flash it, ensure all bloat is there, and download update and install. I removed bootstrap to be on the safe side.
Click to expand...
Click to collapse
Am I correct in assuming that once weve updated to 2.3.34 we cannot flash back to a backup that we were running 2.3.15 on, nor can we SBF back to 2.3.15?

ElephantGlue said:
Am I correct in assuming that once weve updated to 2.3.34 we cannot flash back to a backup that we were running 2.3.15 on, nor can we SBF back to 2.3.15?
Click to expand...
Click to collapse
DO NOT GO BACK !!!
why would you anyways???

okay, after all the reading i've decided that i should sbf instead of trying to figure out all the bloat that may or may not have been removed from my wife's X. That being said, once in bootloader, is it possible to get out of the bootloader without flashing anything? I want to verify the bootloader version to make certain that i have to proper .sbf file.
yes, i do have a backup of the original 2.2.....does that help?
i made this process more difficult than i had anticipated by installing another rom before trying the .340 update. now it starts the install then reboots and says "update failed". anyway, any tips or pointers that can be given are greatly appreciated....thx

I have a question I'm running 2.3.15, rooted with rubix ROM+theme---- already at 2.2.1 / what are the benifits of updating to. 340, and I'm guessing i can't just flash the sbf without starting over, rooting, ROM etc. Just not sure what of a difference there is for going to. 340 when I'm already at 2.2.1 anyone? ?
Sent from my DROIDX using XDA App

How would I update from 2.3.13
Thanks Mike

What have i done!

Ive got a Samsung Galaxy S unlocked on 3 Network using Gingerbread 2.3.3. What ive done is i tried to gain access to the SuperUser account using the CF-Root method. All went well until i wanted to see if i could remove the SuperUser account because when it comes to Christmas i am wanting to sell the phone to a Friend. When i used GingerBreak 1.2 to UnRoot the Phone the SuperUser app uninstalled it self but the CWM and Tweaks app was still on the Phone. I attempted to remove the Apps going through Settings > Applications > Manage Applications but then i noticed it was locked into the phone unable to delete (FACEPALM). So i tried to Re-Root the phone using the CF-Root method again but it didnt give me back SuperUser access nor did it install the SuperUser app but the Odin Application claimed that it was successfully installed.
So what i am wanting to do is remove them two applications from my phone (CWM and Tweaks).
The Plan was to Root the phone and then install Darkys Rom since it looks Cool and Green But since ive never done anything like Rooting the phone or Jailbreaking an Ipod i really didnt have a clue what i was doing. Youtube help me to root it but then i messed it up.
Hope someone will know how to fix this phone and maybe get back on track on installing Darkys Rom

the tweaks and cwm apps are baked into the kernel.
If you want to get rid of them you'll have to flash a stock kernel

2 questions.
1) How do i flash it back to a Stock Firmware
2) How do i find the Stock Firmware right for my phone

grahamn95 said:
2 questions.
1) How do i flash it back to a Stock Firmware
2) How do i find the Stock Firmware right for my phone
Click to expand...
Click to collapse
www.samfirmware.com
it has all the stock firmwares and also has instructions on how to flash them
good luck !

Well flashing the stock firmware is actually quite easy but there's loads of them out there depending on what country you're in and network. If you're in the UK I'd go for I9000XXJVQ which I think is still the latest, I'm using it anyway.
Sign yourself up at http://www.samfirmware.com and you can go in to the firmware section, then in to android and then the I9000 and there's a whole list of them there.
They've also got guides in there to follow on how to use Odin which is the flashing software, oh and bit of advice I'd go for Odin V1.3 if I were you. I've heard a few rumors about problems with V1.8. I alway use 1.3
Good news is its actually quite difficult to really kill a galaxy S so take it nice and easy and follow the instructions and you'll be fine. Anyway the best way to learn is fixing it after its gone wrong he he.

Dudes, JVR is the latest
Sent using geek power

Sorry I wasn't very clear there.
The latest stock firmware in the UK according to Kies on my phone was JVQ.
I took it right back to the original JM1 it came with and that's as far as it went for me.

i am amused how do you try to help not knowing what is going on, thank god noone said put the phone to fridge for 5 minutes
to regain su flash cfroot for example and then via cwm this http://forum.xda-developers.com/showpost.php?p=14900939&postcount=311
but cfroot untouched itdelf should give you su as long as you will not try to update it via market - if you will lose su after that or due flashing some newb kernels use above link to regain it

[Q] rooted LG G2 update OTA

how to do you update a rooted lg g2 over the air. everything is stock on the phone.

MAGICEA_EA said:
how to do you update a rooted lg g2 over the air. everything is stock on the phone.
Click to expand...
Click to collapse
From what I understand, you will still be able to get updates thru OTA.

hd-renegade said:
From what I understand, you will still be able to get updates thru OTA.
Click to expand...
Click to collapse
the recovery "kill" the otas, not the root.
so you have costom recovery you will get the ota but you will be unable to install it, if you use jest a root and have stock recovery - you fine and will get the ota.

So i can update rooted lg g2 over the air when a new update comes out

liorra3 said:
the recovery "kill" the otas, not the root.
so you have costom recovery you will get the ota but you will be unable to install it, if you use jest a root and have stock recovery - you fine and will get the ota.
Click to expand...
Click to collapse
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.

ota
hd-renegade said:
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.
Click to expand...
Click to collapse
Im new to this, so if you have rooted lg g2, will ota still work. Everything is stock on the phone

hd-renegade said:
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.
Click to expand...
Click to collapse
you right.
if you use stock recovery you will get OTAs

if its stock and merely rooted then OTA should work

For the OTA to be accepted, you'll need the stock recovery for your device. Rename it to recovery.img (if it already isn't named that) and then move it to sdcard root (/sdcard).
Now, use a terminal emulator (https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en) and open a command prompt. The command we're using has two parameters. The the "if" parameter refers to your input file, in this case, this is the recovery.img file you moved to your sdcard root to flash. This could be any recovery (TWRP, CWM, stock, etc). The "of" parameter is the output file and is the actual physical path to the recovery image your device uses. At the command prompt type this:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
If you already have the stock recovery then all you need to do is press "Accept" or "OK" or whatever the dialog asks when it pops up letting you know about the update. I'm not sure if the stock recoveries are different for each carrier, so you'll have to find that yourself.
Edit: By the time I finished typing this I see that you already are on stock recovery, so you should be good to go

Idk mines flashed to stock and rooted
Sent from my LG-D800 using Tapatalk

Just bought a g2 and am thinking of rooting to enable the auto hide of the on screen menu buttons. So correct me if im wrong but if all i do is root, leave the stock rom and do nothing apart from root i will still get ota updates.

But the update can remove root right? So is there any way I can keep my phone from automatically updating and losing root? I don't want to lose root... Mainly cuz i love not having software keys.
Sent from my LG-LS980 using xda app-developers app

SuperSU Pro has an OTA survival Mode. You can try it out, it should work

o0adam0o said:
But the update can remove root right? So is there any way I can keep my phone from automatically updating and losing root? I don't want to lose root... Mainly cuz i love not having software keys.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Try the above or remove/freeze whatever the apk your carrier uses for the OTA. There's a couple threads around with more info.
Sent from my LG-D800

Another question: (don't want to start a thread for this)
If you have custom recovery (In my case TWRP) when an OTA lands, obviously I won't be able to accept it.
I'll need to flash it through TWRP correct?
If this is the case will this simply apply as OTA's do and not delete any of my data on the phone etc?
Also is there a stock recovery I can download just to make things easier??
First time I've had a phone rooted and with recoverybefore it's update cycle is over, and Google isn't really being all that helpful

How to backup stock recovery?

I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.

m4570d0n said:
I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.
Click to expand...
Click to collapse
Nice to see you here dude.. may remember me from the rocket? Anyways, i'd just skip the OTA. It's nothing life changing. I'm still stock/rooted on 10d. Waiting for bugs to get squashed on 4.4.2 before I start flashing. Rather enjoying stock for the time being. Not really sure why 10o won't take. Haven't seen anyone else mention this. The only thing that has been brought up repeatedly is bootloops in twrp after taking the 10o OTA.

m4570d0n said:
I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.
Click to expand...
Click to collapse
I am having the same error but don't remember seeing the same pop-up, just says install failed or something like that. I'm on Verizon stock Rom rooted. I've done plenty of mods by manually pushing them through, but I have the stock recovery and no custom recovery.... So safe to say, looks like you can't update with root. Gonna start searching for unroot then re root after update is installed. Doesn't seem like there is another way to do it. Anybody know if the temp unroot via superuser apk will work?
Sent from my VS980 4G using Tapatalk

thricerocks86 said:
I am having the same error but don't remember seeing the same pop-up, just says install failed or something like that. I'm on Verizon stock Rom rooted. I've done plenty of mods by manually pushing them through, but I have the stock recovery and no custom recovery.... So safe to say, looks like you can't update with root. Gonna start searching for unroot then re root after update is installed. Doesn't seem like there is another way to do it. Anybody know if the temp unroot via superuser apk will work?
Click to expand...
Click to collapse
I am still investigating. I've unrooted via Voodoo OTA Rootkeeper and a little extra housekeeping, and the Rooting Status does show "unrooted" in the About Phone section. However I still get 0x1117008 when trying to install the OTA. So perhaps the "unrooted" in About Phone may be a prerequisite, but is not sufficient for a successful OTA update. Maybe either the update is doing more checks for rooting evidence than the RCT daemon, or perhaps there is some other change that is triggering the error.

Need help with proper way to update.

I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you

Nizzoball said:
I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you
Click to expand...
Click to collapse
Use the ODIN MF3 files....ODIN your phone back to stock. This is what I did. I also rooted MF3 via SDCard method....restored my phone to how i want it. Used Supersu to do full unroot, then go to OTA update and wait 5+ hours to download the 727 mb file from the horrible AT&T servers, then install update.
Instead of "unrooting" you can try survival mode which has been said to keep root for some, but not for others.
Good luck!

Tremulant1 said:
Use the ODIN MF3 files....ODIN your phone back to stock. This is what I did. I also rooted MF3 via SDCard method....restored my phone to how i want it. Used Supersu to do full unroot, then go to OTA update and wait 5+ hours to download the 727 mb file from the horrible AT&T servers, then install update.
Instead of "unrooting" you can try survival mode which has been said to keep root for some, but not for others.
Good luck!
Click to expand...
Click to collapse
Thank you. Thats the method i was looking into but i was hoping there was an easier way. I've never used odin on any of my phones but i'll give it a shot. I appreciate your feedback.

rooted with update
Nizzoball said:
I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you
Click to expand...
Click to collapse
I was also stock rooted with MF3 and i used SuperSU survival mode to keep root after the update ... but i wasn't getting the OTA so I did a sideload of the update.

Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM

JCrawMil said:
I was also stock rooted with MF3 and i used SuperSU survival mode to keep root after the update ... but i wasn't getting the OTA so I did a sideload of the update.
Click to expand...
Click to collapse
How did you sideload? Ext. SD Card or ADB.

bigube said:
How did you sideload? Ext. SD Card or ADB.
Click to expand...
Click to collapse
ADB sideload pushes the package from your laptop to your phone.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

bigube said:
How did you sideload? Ext. SD Card or ADB.
Click to expand...
Click to collapse
I did an ADB sideload

Error while trying to update to 4.4 (D800)

Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?

This is my problem too. Hopefully there is a way.
Sent from my LG-D800 using xda app-developers app

Maybe doing a factory reset from stock recovery?
Sent from my LG-D805 using xda app-developers app

rohan611 said:
Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
Click to expand...
Click to collapse
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help

antawnm26 said:
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
Click to expand...
Click to collapse
nope. as i said in the OP< i have a stock recovery.

rohan611 said:
nope. as i said in the OP< i have a stock recovery.
Click to expand...
Click to collapse
then try root keeper it will disable root but back up root path and reinstate it once the update is done

antawnm26 said:
then try root keeper it will disable root but back up root path and reinstate it once the update is done
Click to expand...
Click to collapse
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.

rohan611 said:
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
Click to expand...
Click to collapse
lol..yeah i read each statement in your OP just wanted to get to that last part of you saying your going back to stock and going from there, because thats your next option....

Let us know if you went back to stock then did the update and it worked.

I've read that some people kept root through their OTA. Why are some people able to update and others aren't. I've been reading up on this for the VZW update whenever that happens. I hope I haven't kept all this bloatware on my phone for no reason!!
Sent from my VS980 4G using Tapatalk

hinduboy74 said:
Let us know if you went back to stock then did the update and it worked.
Click to expand...
Click to collapse
I reverted back to stock using the instructions in the Stickied post. I was then able to update to D80010o. I had to call to request a rep to push out the D80010q update again though. They're calling it a "security update" so you should use that phrase when talking to the rep so that they don't get confused and think that you're just requesting that they push out the KitKat update.
Once I got the D80010q update, the KitKat update was available and I was able to update. Unfortunately, I didn't try to root it prior to updating - though to be honest, I don't really feel the need to root anymore. Only reason I had it rooted before was to get the multitasking button, but I'm okay with using an S3 layout (Menu, Home, Back) since that's the phone I'm coming from.

I have posted this in Other thread too.. may be this helps (Or save some time)
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.

streetsmart999 said:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o

rohan611 said:
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
Click to expand...
Click to collapse
That is correct. I was on D80010o all four times I updated to Kit-kat and kept root everytime.

streetsmart999 said:
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
Same thing happened to me. I followed your advice in the other thread and did a reset using the LG flash tool, following rootjunky's guide on youtube and using the files from his website. Everything went smoothly except for at the end I got the same check flag error thing, but it completed the reset perfectly.
I then chatted with ATT and had him push the update to my phone which brought me up to d80010o. It finally went through the update and didn't get me the root error. So I think I'm in the green now. He said that he didn't have an option to push the kit kat update to my phone but it told him to have me do it through the software update in the settings. Which I tried and it said it was up to date. But he said that since they roll out in batches my phone might just not be ready for it yet. I will keep trying though and I'm one step further than I was before. At least it let me update. Shout out to ATT though, chat service is on point.