Android Alliance

Hi all, first post here.

I'm with AT&T, and until today I've had Package Disabler Premium 6.3 doing my blocking for me. After realizing it was saying license invalid, I decided it would be best to follow the Ultimate Guide to Blocking Samsung OTA Updates thread on here. I followed method 1, for AT&T. Since the license was saying invalid on Package Disabler, I wasn't able to re-enable everything before I uninstalled it. So I uninstalled it anyway, following the rest of the guide all the way through running the Disable_ABD.

About an hour after completing the guide, I got a notice on my phone that said "Urgent Samsung Update!" I was able to swipe it away, and haven't seen it again (that was an hour or two ago). Is that supposed to happen, or did I botch something? Considering I was safe from the 60% updaye, I don't want to have screwed myself just before the killer update.

Thanks for any help you can give me.

Skorcher wrote:1968 Hi all, first post here.

I'm with AT&T, and until today I've had Package Disabler Premium 6.3 doing my blocking for me. After realizing it was saying license invalid, I decided it would be best to follow the Ultimate Guide to Blocking Samsung OTA Updates thread on here. I followed method 1, for AT&T. Since the license was saying invalid on Package Disabler, I wasn't able to re-enable everything before I uninstalled it. So I uninstalled it anyway, following the rest of the guide all the way through running the Disable_ABD.

About an hour after completing the guide, I got a notice on my phone that said "Urgent Samsung Update!" I was able to swipe it away, and haven't seen it again (that was an hour or two ago). Is that supposed to happen, or did I botch something? Considering I was safe from the 60% updaye, I don't want to have screwed myself just before the killer update.

Thanks for any help you can give me.

Do you remember the complete text of the notice?

The notice was on the lock screen, Urgent Samsung Update is all it said, I swiped right and dismissed it without unlocking the phone. I didn't want to get into it any further in case it tried to do something.

It's the one from SAMSUNG that's got the blue and white Samsung avatar and the notice. I know because I had the EXACT same set of circumstances happen to me as Skorcher reported. I'm on Tmobile though. I never had the 60% update installed, and had an old version of Package Disabler Pro with auto updates turned off, so I wasn't getting the pushes either. However, once I began following the steps on note7alliance to install OTA update blocks, I went to re-enable the package disabler pro files, and it gave me the license warning at that time. I just uninstalled it, and continued with the steps on this site. It seems that it worked as intended since I get "software update failed" messages each restart now, but as with OP above, I too received the Samsung warning push notice about yadda yadda "beginning December 19, something something, power down and return". I also, just swiped the notice away, and the phone is still charging to 100% and doesn't seem to have forced any Tmobile death patch.

Fingers crossed so far....
~7~

Seems to be an effect of samsung push service. Maybe using pdp you had disabled this one too.
It is not contained in the tutorial yet, because it's also used to get notifications from gear and watch. So if you disable this you won't get information from this stuff pushed to your device. If you don't want to use such things you can disable this package too ot try to go to the settings of samsung push service and switch all options to off.

Glad to know I wasn't the only one who had this happen, thanks for the notice Se7en. Beowulf, how would I disable this package as well? I didn't see any way to manually pick and choose, I just ran the script.

Skorcher wrote:1990 Glad to know I wasn't the only one who had this happen, thanks for the notice Se7en. Beowulf, how would I disable this package as well? I didn't see any way to manually pick and choose, I just ran the script.

You can edit the script named Disable_ADB.cmd using an editor like notepad or notepad++. Right click Disable_ADB.cmd and chose edit (NOT open),
then change the line:

adb shell pm unhide com.sec.spp.push

to

adb shell pm hide com.sec.spp.push

Save the file, run the script again like described in tutorial.

Fantastic, thanks!