[Samsung Galaxy A32 5G] GalaxyA325G:
Thank you for that suggestion, where I really don't know that much about Android, which I openly admit. I can research if pointed in the right direction though. :)

I am told the bootloader for the T-Mobile A32-5G needs to be version 5 or below (maybe even 3 or below) in order to root the Samsung Galaxy A32-5G, and mine is currently version 8.

I don't know how to roll back a bootloader, but even so, I'm not sure I understand your suggestion of rolling back the Android version from 12 to 11.

How would changing the OS change the bootloader version?

I very much appreciate your kind and thoughtful advice that pointed me in the direction of the two packages that I needed to disable, which is what I needed to research in the right direction.

I also much appreciate that you mentioned adb will do the job of disabling those packages without me being rooted, as that too was a required datapoint that I didn't know until you told me.

Thank you very much for your kind advice, where I do agree with you this hype about having the latest security patches isn't something I'm all that worried about.

However....

There is this "nagging concern" that, as of Google's Project Mainline and Project Treble (both since renamed), the way that the 25 core modules update is no longer via carrier updates but over the air with Google Framework Services updates (not to be confused with Google Play Services updates).

AdServices multi-package multi-type Android 13

adbd com.android.adbd APEX Android 11

AppSearch com.android.appsearch APEX Android 13

ART com.android.art APEX Android 12

Bluetooth APEX Android 13

CellBroadcast com.android.cellbroadcast APEX Android 11

Conscrypt com.android.conscrypt APEX Android 10

Device Scheduling com.android.scheduling APEX Android 12

DNS Resolver com.android.resolv APEX Android 10

DocumentsUI com.android.documentsui APK Android 10

ExtServices com.android.ext.services APK (Android 10)

ExtServices com.android.ext.services APEX (Android 11)

IPsec/IKEv2 Library com.android.ipsec APEX Android 11

Media Media: com.android.media Android 10 (extractors)

Media Codecs: com.android.media.swcodec APEX Android 10 (extractors, MediaSession API) Android 11 (MediaParser API)

MediaProvider com.android.mediaprovider APEX Android 11

ModuleMetadata com.android.modulemetadata APK Android 10

Network Stack Network Stack Permission Configuration: com.android.networkstack.permissionconfig

Captive Portal Login: com.android.captiveportallogin

Network Components: com.android.networkstack APK Android 10

NNAPI Runtime com.android.neuralnetworks APK Android 11

OnDevicePersonalization Runtime Multiple Multiple Android 13

PermissionController com.android.permissioncontroller APK Android 10

SDK Extensions com.android.sdkext APEX Android 11

Statsd com.android.os.statsd APEX Android 11

Tethering com.android.tethering APK Android 11

Time Zone Data com.android.tzdata APEX Android 10

UWB com.android.uwb APEX Android 13

Wi-Fi com.android.wifi APEX Android 11

It's all very confusing HOW Android updates nowadays.

Some updates are over the air by the carrier

Other updates are done separately for the 25 core modules

Still others are done over a Google Play Store app Activity

(These last app updates are not really part of the Google Play Store app but the Activity for app updates appears in the settings for the Google Play Store app so a lot of people associate those app updates with the Google Play Store app).

In short, does this method of disabling two packages "really" work to stop all updates?

Or does it just work for the Project Mainline updates?

Or just the carrier supplied security updates?

I don't know.