Android Alliance

I have had Package Disabler Pro and Alliance Shield on for a while.

I just looked on here today and notice something is going on with Knox and The Shield may not work or may not update or something.

I thought that once the Shield was installed the services would be blocked, for good.

Can someone explain whether folks in my position need to do anything at this point?

If the script is the only protection, why screw around with the Shield?

I'm confused...

I was kind of in the same boat as you; had Package Disabler Pro...
1.) I did not yet have Shield; thought I was safe with Package Disabler Pro.
2.) The Knox issue also knocked out my Package Disabler Pro. If you try to open it (I had the good version, 6.3) it won't activate the license. I'm guessing that's because of the same reason you can't get a *new* Shield install.
3.) If your Shield is still green, you're OK. But if you don't have Shield, try the Solid Explorer or ADB methods described.
4.) Because of the apparent success of all these different methods, now Verizon is implementing changes on *their* end to individually shut us off... that has nothing to do with the Shield or anything else.
5.) At this point, I've read that Verizon is shutting off some folks, as of today. (my text said 1/31.) There may or may not be answers to this, and the Alliance crew are trying to find answers.

My suggestion? You *can* also do the ADB or Solid Explorer procedure, even with Shield. Just don't accidentally uninstall / remove admin privileges from the Shield or you won't be able to reinstall it at this time. Why? Because they'll still kill you that way if they can...

Me? Right now, I've only done the Solid Explorer procedure, and I also have a firewall. I did not get the Shield in time. I've been safe from the updates (other than the nag dialog), but just waiting for Big Red to shut me down...

If you're a Verizon customer, your bigger problem is them individually just shutting you off...

Please, anyone, correct me if I'm mistaken on any point. Thanks.

My shield and Disabler Pro are still working it seems.

I am on ATT

I paid cash for my phone, so if they kill it, I might be pissed a bit...

Since the Original Note, I've only had Notes, and only want Notes.

I got rid of a Flawless N5 and lost money on that, it wasn't real old.

The only thing I am Interested in is a Note8, I would take a S7 as a loaner in the meantime, which is what they originally said they would do. Then changed their tune.

So it seems like if the Shield is working, they shouldn't be able to do anything, is that correct?

@LesGarten:

I think it's only those who either Factory reset their devices, or people who are just now finding out about the shield application that are sort of screwed. Especially now that when a device tries to download and install the app you'll get Authentication error or something similar. Devices that had it previously, before Samsung played around with Knox should be fine.

Now I"m on ATT as well and haven't heard anything from them. Not a single text message since their last battery crippling update. No thinly veiled threats about charging full price, or blocking our phones from the network. But I'm thinking if that's exactly what Verizon is going to try and do, then it won't take long before the other cell networks start doing the same. Which is going to suck since like many people on this forum, there aren't really any decent alternatives to the note7 on the market currently. Not to mention if you do decide to switch to another device, regardless of it being older than the note7, it'll still use your upgrade option. (Which isn't waved from ATT now, nor was it at the very beginning of the recall sadly.) So now you're stuck with an older device until you pay it off or the contract wraps up. But I'm guessing we'll hear from ATT once Samsung releases their findings, if it truly is hardware related, they'll be pressed to make sure the phones are off the networks.

That's good I guess.

I was planning to wait for the N8 and do a swap out.

It looks like they are trying to avoid that, unless you're in Korea.