Android Alliance

1.) I did not have Shield, but another package disabler.
2.) It quit working the exact time new Shield installations started failing last night (I happened to be online here).
3.) Knowing that the Knox change likely affected all package disablers, I installed a VPN Firewall called Netguard, and disabled internet access for all the same files as were blocked in my package disabler. I can provide a list if that would be helpful. That was late last night.
4.) As of just a half hour ago, no packages had downloaded to my phone, still at 100%, no notifications of updates.
5.) To protect my phone further, I followed the instructions for the Solid Explorer protection, but first I uninstalled my Package Disabler as it was not working anyway.
6.) Being on Verizon, only the first file was located of the three, and I ran it with Package Installer per Instruction.
7.) The device tried to update several times and failed, just like the tutorial said it would.
8.) I shut device down, cleared cache and rebooted. I thought I was safe.
9.) Within a minute of restarting, I got the UPDATE dialog (which had just failed several times...) stating the update was ready to install. This may be a fluke of timing. It may be that even though I couldn't open my old package disabler, it was somehow still working. It may be that I somehow messed up the Solid Explorer procedure. (kind of doubt that, however, as it was really super simple.) Maybe the update had been there for some time and the package disabler kept it from trying to run. IDK... super frustrated at these sum-b****es.
10.) I put off the update until 5pm tomorrow, and I did not check the Start Automatically box.

Since this update is forced and will eventually run, and considering everything with Knox ... am I toast?

Your help will be greatly appreciated.

update;
verizon login, vzwaves, and samsung push service just attempted to access the internet. that access was stopped by firewall... just fyi if it helps.

Affected users MUST prevent the update from running as it appears to introduce the latest Samsung degradation/bricking code that may not be able to be over-ridden
IF you can check the OS version that a factory resET will revert your NOTE 7 to, then performing the factory reset where THAT VERSION is an earlier version should protect you and blow-away the 'update'.
I did that two weeks ago when an update was able to sneak through my defences, and I was able to reset to the pre-green battery indicator and installed the green-battery update as it brought the latest (safe) September update and (I think from other's comments) some core-OS change that better manages CPU/GPU to reduce heat release.

Once the factory reset completed, I quickly did a minimal set up with no google/Samsung account activity -AND- then selected 'flight mode' and set up through WiFi.

HOWEVER given that Samsung may have updated the Knox Samsung-Server authentication this week to block changes that disable degradation/bricking Samsung updates, you may not be able to safely apply the Alliance update... I'd wait for a Forum update that the Alliance update package is working.

This may be difficult if you don't have a backup mobile - I moved to an ageing Note 1 which I use as a fall-back mobile whilst I watch the Forum posts to see how wild things have become this week.

Juliesdroidsync I have provided more detail via private message