yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
I tried this and get the same error. :( Any other ideas? Please?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amfractal:
OTA 4.3 Rooting problem with Knox

I have AT&T Galaxy S3 and I am having problem with rooting since knox keeps blocking it after installing OTA 4.3.

I updated to the OTA yesterday. I was on a stock rom 4.1.2 and the latest temwin recovery.The update failed so I flashed an original recovery and got the update to work.

In hindsight I should have flashed the CF-Autoroot for the OTA update. Anyway, since then I have tried using teamwin, cwm, and cf-autoroot with superuser and supersu and none of them have worked.

Anyway I suspect I have messed up my system files as well since now even google playstore sometimes gets blocked (image below). I have updated the security policies and tried enabling disabling different security options but nothing works. It's running a process in the background and downloading apparently.

imgur album is here but I am not allowed to post URLs yet:

imgur.com/a/kMTeq

Another thing is that every time I reboot I get the message that Android is upgrading my apps. It tried to upgrade all the apps installed everytime which tells me I guess it can't because it gets blocked.

Anyway I need a way to cleanup my system files and have a clean 4.3 ROM installed. Anyone has any ideas?

Can knox be disabled in recovery (e.g. adb commands in teamwin)? how?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
Read my posts there : http://xdaforums.com/showthread.php?t=2535665
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amfractal:
Thanks. But could you please give more detailed instructions on how to remove those files? I don't have root right now. Are you doing it in the recovery? which recovery? And how?

Do you know if renaming also works?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
Did you try to root with CF-Auto? if you do open SU and if you see FC slide down notification and see if you have new security policy there. If you do cklick on it and agree to upgrate. Then your SU should work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
On the idea of using kies to downgrade, would it be the old kies or kies3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Haven't finished the thread yet, but when a similar thing happened to the S4 bricking with custom recoveries being put on, the suggestion was you could take it to the samsung tech store within best buy, and their computer could resurrect it. Is it worth a try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
I will think old. Kies 3 are for 4.3 and up software. Also we can wait and see if att realise 4.3 software for kies
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
But if you did the ota, you will be on 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
But kies3 don't carry 4.1.1 software
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amfractal:
I did try CF-Autoroot but it didn't work. I just tried again (phone was factory reset a few minutes ago and just playstore had updated stuff). I'm using the latest version posted on chainfire's page:

"CF-Auto-Root-d2att-d2uc-samsungsghi747.zip"

I have added a couple of screenshots to the album on imgur to document the process I'm doing:

imgur.com/a/mBzxl

cf-autoroot flashes and says everything is fine but after reboot knox still blocks. On the first boot after factory reset the policies had been updated (like half an hour before this new flash). so they should've been up to date when supersu tries to run after this new flash. Am I missing something? Is there currently anyway to restore everything (including system files) to a 4.3 "factory state" (I don't care about the boot counter for now)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ali3n8:
I have been using this method:

1. Copy the update to your external sdcard

2. Reboot into download mode and cf-autoroot (this will flash stock recovery back)

3. Boot into recovery and select update from external card.

4. Boot into recovery again and flash the update again (this will format your internal sd card you will also notice recovery has been updated again also)

First boot will take some time but if it does not boot just flash again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amfractal:
Thanks. I want to make sure I got it correctly since I'm not clear on these steps:

1. Copy the update to your external sdcard (by update you mean the 620MB file posted by loserskater, renamed to update.zip and put on the external sd, correct?)

2. Reboot into download mode and cf-autoroot (I am currently on the latest cf-autoroot, I don't need to flash it again? Should I try another method of flashing cf-autoroot? ...?)

3. Boot into recovery and select update from external card. (the full update.zip...)

4. Boot into recovery again and flash the update again (so I just flashed the update.zip and it finished, before it reboots I pull out the battery or something, and go to recovery again and say flash from external sd again? am I missing something?)

Sorry If any of the questions are novice.

Is there a chance of bricking using this?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
So I can't odin back to 4.1.2 if I did the 4.3 OTA update, correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
NOYou will brick your phone !!!!

---------- Post added at 05:56 PM ---------- Previous post was at 05:54 PM ----------

Seems to me like this security update is only for SU or some unknown app run. If you agree you validate waranty .. i will try find out more info.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Crap! So I'm pretty much stuck on 4.3 until there's root method for it?

I just need to flash a custom recovery so I can switch ROMS.

Should have read more about it before updating. Aghhhh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
I root by CF-Auto, but some people having problem with KNOX security... I can't find out why is the problem. So DO NOT root yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
Those having issues with root, try this:

Root using CF Auto Root

Download KNOX REMOVAL SCRIPT from here: http://xdaforums.com/showthread.php?t=2507931

Flash in recovery

Update SuperSU

Update su binary
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
Willthis script work in stock recovery? If you can't root and or run SU how you will install custom recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
TWRP has a ODIN flashable tar
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
Has anyone tried using Kies to restore to stock firmware after updating to 4.3? My phone is soft-bricked and I am stuck without a phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Interesting. In Odin, do you use the PDA option to flash it?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
Try then if you can get in to download mode. Follow guide : http://xdaforums.com/showthread.php?t=1984717

---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------

Yes in PDA.. I just brick my phone using ODIN...i even put pit file becouse i this how you can downgrate S4 from 4.3 firmware.. :)

Try if you brave...:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Sorry to hear that. I would try it but I'm leaving town for the weekend so I can't risk it.

Battery in stock 4.3 is horrible!

I want root, I want root! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
Is there any way I can get the contents of the /system folder back into my phone? That is the only error I am getting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
How fare you can go if you start your phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
I can get in to recovery and download mode. If I start my phone, I can get only till the Galaxy S3 splash screen. I erased my /system folder by mistake when I tried to reinstall the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amfractal:
Whoa. I did install teamwin in one of my tries without a problem. it didn't fix my root problem though. Now I'm afraid to try it again. Which version did you use (I think I used 2.6.3)? If it works I'm not sure how to use the Knox removal script in the teamwin recovery...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lestaat:
[

BTW did anybody notice you can uninstall all AT&T/some Samsung crap tru app drawer..?[/QUOTE]

Yea I saw that. I don't think it actually uninstalls them, just hides them. It doesn't ask for an ok to delete data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
So, I've got a feeling 4.3 is going to be a ***** to work with. I was able to root with CF-Autoroot. After reboot I am no longer rooted, SU app is gone, and now CF-Auto can not root the device again. And...I am tripping the crap out of my counters (not that I care).

Someone had wondered if the partitions had changed, but they did not.

C:\Users\Me>adb shell
shell@d2att:/ $ ls -al /dev/block/platform
ls -al /dev/block/platform
drwxr-xr-x root root 1970-01-01 07:36 msm_sdcc.1
drwxr-xr-x root root 1970-01-01 07:36 msm_sdcc.3
shell@d2att:/ $ls -al /dev/block/platform/msm_sdcc.1/by-name

lrwxrwxrwx root root 1970-01-01 07:36 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 07:36 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 07:36 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 07:36 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 07:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 07:36 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 07:36 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 07:36 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 07:36 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 07:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 07:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 07:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 07:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 07:36 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 07:36 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 07:36 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 07:36 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 07:36 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 07:36 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 07:36 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 07:36 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 07:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 07:36 userdata -> /dev/block/mmcblk0p15
shell@d2att:/ $
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbayer:
We can flash a custom recovery with odin and not brick the phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
Hmmm.. i did root my phone on 4.3 OTA with CF-autoroot and restart hunderds time still had root and working SU, but i lost phone trying to restore to 4.1.1 by odin... I did all my updates tru ADB sideload and i had no problem with rooting and Su after i accept samsung security polices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
So then....shouldn't you be able to flash a custom recovery and install a different ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
I tried using Kies 3 (the one for the 4.3 version of phones) and I am getting the following messages :

http://i.imgur.com/sbFfmCT.png

http://i.imgur.com/rtlkMLC.png

Is it still safe to go through with it? Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
I had custom recovery. I tried to back to 4.1.1 by odin and i brick my phone . I will get another one and root again , install CMW and see what happen.

---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------

It is your decision.. I personaly will try.. :) NOT telling you to try huh...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
Thank you. I just want to be sure because I am a poor student and can't afford to buy another phone if this one bricks. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
STOP!!! i'm not sure now again... if you can go to recovery you can try to install other rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
I didn't go through with it. Will I still be able to install CM 10.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
I have new S3. Just update by ADB sideload all the way to 4.3 , will root with CF-auto and see where I can go from there.

---------- Post added at 09:14 PM ---------- Previous post was at 09:13 PM ----------

Do you still have custom recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamsledd:
I got the I747 in July, and it came with 4.1.1. I rooted it to get rid of bloatware but kept running the stock; I have not been able to get an ATT update since, so I am not sure what they are pushing. The updates fail when the reboot goes into the Teamwin recovery. *(if anyone knows how to get around this, I'd appreciate it)

Now, my wife just ditched her iPhone after months of being told how much better my phone is, and she got an I747 in the mail 2 days ago. It is running 4.3, build UCUEMJB.

So, as I said, I don't know if they are pushing it in updates; but apparently it is coming loaded on new I747s. I am about to flash the leaked UCUEMJ2 found in another thread.

Still would love to find a way to get the ATT updates through...where do they go when my phone downloads them, and what is the filename? Are these flashable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
Yes I do. I can still get into TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Nice! Please keep us posted.

I can't wait to get rid of stock 4.3...ha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
Put rom of your choice to exrernal sdcard using pc. Insert card in phone, reboot in recovery and install as developer of rom guide you to do so.

---------- Post added at 09:27 PM ---------- Previous post was at 09:25 PM ----------

I will tomorow...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
Yes it is quite the pain. Every time I try to build it bootloops. I've narrowed it down to system and not boot.img. I've tried about a dozen different things today and nothing has worked. It's quite frustrating.

Yes, but only recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
You are lucky, and I'm confused. :cyclops:

Just trying to build a stock ROM, or doing mods?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
I tried this, and got an assert failed error. Something wrong with the bootloader. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
Completely stock. The boot animation just barely starts and then reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
Yikes. Not good.

I am so close to selling my S3 and my S4 and being done with Sammy forever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
I'm in the same boat! I have a feeling by the end of next year the Samsung forums are going to be desolate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Has anybody managed to produce a system dump of 4.3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
Yeah. I've been trying to create a flashable zip from it, but it's not playing nicely
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
That's strange. Is it happening with all the partitions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RockRatt:
Loser when trying to make the ROM did you try to remove every last bit of Knox from everywhere inside the files? Not just the apps. I believe on the S4 most if not all the Knox files have to be removed.

Also on the S4 those of us that have been rooted with the original firmwares before the MF3 update have not flashed bootloaders at all. I originally had mdb firmware so I still have the mdb bootloaders. I have been able to flash MF3 4.2.2 without bootloaders and not be further locked down. Then I have flashed many of the MF9 4.3 firmwares without bootloaders. I have been able to flash back to any of the older firmwares with no problems.

The issues arise when users flash the bootloaders. Those that flashed the MF3 firmware with bootloaders were stuck for quite a while until safestrap came out. The downfall for safestrap was that now they could not flash ANY 4.3 firmwares through safestrap. Then we had a MF6 4.3 leak which when flashed blew a qfuse so you couldn't even flash back to MF3. Next was the official MF9 firmware which seems to have blown ANOTHER qfuse so those users are now stuck on 4.3 MJ9 without root or recovery.

Sammy is making it VERY DIFFICULT to enjoy our phones lately, especially with ATT and Verizon Locking the bootloaders. So I am thinking the same as you and feel I am already seeing the effects. The Samsung forums are going to be ghost towns soon.

I also think I read that the International Variants of i9505 once flashed to 4.3 are having issues as well and cannot downgrade to older firmwares. Maybe this is the beginning of the end for Samsung Galaxy S phones. Too locked down. Users slowly left CrApple because its the same ole same ole things and I can see that happening to Samsung if they keep it up.

Hopefully you can get a fully UnKnoxed ROM to work without flashing bootloaders to work for our S3... Thanks for taking one for the Team Enewman and Loser and I HOPE you will succeed.

Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidBH:
Hey. I use Android 4.3 from luserskater root no knox. I deleted super user yestarday, turn off root options.. my phone now is not rooted.. How do the new update? This update must be root your phone?

First root?

Download cfg file and rename in update.zip

Copy in ext card

Flash update.zip

Reboot..

?

Sorry for my english.. i dont understand all posts..

I use loserskater rom 4.3 root no knox. But my phone restart every day..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
I'm out of ideas now. Don't know what to tell you.

Like i said they did to S3 same think is done to S4.. Maybe they lock bootloader.

Edit: I did root 4.3 OTA with CF-Auto and everything is working just fine... Like i said just update security policy and SU will work.

I made video as proff SU working

https://www.youtube.com/watch?v=d_VEpbnXLec
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
norbarb, have you been able to flash a custom recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] norbarb:
On my last phone I did. But I bricked phone trying to downgrade to 4.1.1.

I will try on this one later today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
Ok here's what I did. Since my problem was I wiped /system by mistake, I couldn't boot into the OS anymore and was getting stuck at the boot logo. I still have recovery and download. My friend's S3 got updated to 4.3 through OTA, so I decided to try copying the /system folder from his phone into mine via external sd. I did this via TWRP. Then I tried to flash the update43.zip. Now I am getting a different error.

assert failed: apply_patch_check ("/system/bin/ru
E: Error executing updated binary in zip '/extern
Error flashing zip

Any help? :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
Seems that the update is a patch. Since you already have the update install, you can't patch. might have to take it to the ATT store and try to get them to warranty the phone since the upgrade killed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
I am out of warranty now so I don't think the folks at ATT will look into this. :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
Still worth a shot since their software update screwed up your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
I have a custom recovery installed and I also rooted the phone. Will they check and tell me they can't handle a rooted phone?

I know someone here exchanged their bricked phone with ATT and got a new one. Any tips?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Try the unofficial cm11 thread, at the end of it (yesterday sometime 11/21), there is a prerelease hack of the tmobile version with the assert checks removed. Try that, it will not check the correct bootloader and should pass that check and get past the error 7. You will also need 4.4 gapps.

Alternatively, there is some instruction in it about how to remove the assert checks from an archive.

DO NOT try to downgrade the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
Is this the one you're talking about - http://xdaforums.com/showpost.php?p=47680332&postcount=1113
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Yes, use it with the PA Gapps from post 1. I think the latest is 11/19..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Evilweasel47:
Okay trying that now. Thanks!

---------- Post added at 10:39 AM ---------- Previous post was at 10:30 AM ----------

Tried it, getting an error.

set_metadata_recursive: some changes failed

---------- Post added at 10:42 AM ---------- Previous post was at 10:39 AM ----------

Looks like I need CWM instead of TWRP. Anyway to flash CWM via TWRP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Yes, same add a Rom. See its thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scottmcm:
Has ATT killed the OTA update? I finally got it to download last night then it said installing, rebooted into recovery for a bit then rebooted and I am still on 4.1.2. There were no messages although the recovery screens went so fast if there was an error in there I never would have seen it. I checked for updates again this morning and now it says I am up to date. I was expecting it to tell me to wait until the 24 hours from my past attempt had elapsed like it did before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Naddict:
Thread cleaned of fraud discussion. We don't do that here folks. Anything that you do to your device has risk. You knew that coming into this, fraud is a crime.

Consider this your final warning in here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mattsternc:
Do you have a custom recovery installed? Rooted? If you have a custom recovery installed, you'll need to ODIN back to stock for this to work. I had rooted and CWM recovery installed. The OTA will not work with a custom recovery and will error out. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
I hope so and it wouldn't surprise me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tyrantsbane:
Knox files

Does anyone know the com. files for Knox. I want to give it a go in removing them through ADB.

Just I can't find the package names to do it.

I tried pm diable com.sec.knox.seandroid but it didn't do anything

Anyone else got some ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ali3n8:
http://xdaforums.com/showthread.php?t=2535665
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shortydoggg:
No, it's still being pushed. My phone says that an update is available, and I'm currently on 4.1.2.

Now that, that is done, I'm going to refreeze that "AT&T Software update V4..." app and clear again that data with titanium, as I have no intentions on accepting that update.