• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Updates

https://www.gsmarena.com/samsung_galaxy_j7-7185.php
The problem isn't necessarily Samsung not providing that Nougat upgrade for you, your disdain needs to be re-directed to your carrier. If your carrier hasn't upgraded your phone by now, it's not going to happen.
You might want to use Samsung's Smart Switch utility to try to manually apply the version 7 upgrade yourself.
https://www.samsung.com/us/apps/smart-switch/

https://www.howtogeek.com/347831/how-to-use-samsung-smart-switch-to-update-your-galaxy-phone/
(Just a minor caveat but I've only had limited success using Smart Switch to actually work at applying version upgrades on various phones so as the saying goes, your mileage may vary. Don't be too surprised if this doesn't work out.)

But Smart Switch is Samsung's multi-function utility and it also has a backup feature too. If you don't already have some kind of comprehensive backup solution set up, use Smart Switch. t makes restoring a user account a lot less of a hassle should you need to. If you have files and things that only reside on your phone, it's vital bot backup your data, smartphones are simply not reliable for long-term storage. Backups are important.

Help Cleaning bloatware

I decided to clean some of the bloatware off of my rooted Pixel 3XL. The first bloatware I removed using ‘adb shell pm uninstall --user 0 <package>’ and there were no problems. However, it was pointed out that I should have TWRP installed in case something goes wrong. While I can do this, the phone is actively used and I am concerned about making a mistake. So, a bit more looking and I found something that suggested using ‘adb shell pm disable --user 0 <package>’.

The problem is that this didn’t work. When I tried ‘adb shell pm disable --user 0 com.verizon.obdm_permissions’, I got the error message ‘Security exception: Shell cannot change component state for com.verizon.obdm_permissions/null to 2’. Did some searching, but nothing indicated how to resolve this issue.

My question: Can 'pm disable' be used (and what should I do to avoid the error) or is ‘pm disable’ not a viable option for non-system bloatware?
You're using the old adb command which is unreliable. Try the new command instead.

Code:
adb shell pm disable-user --user 0 <package>

Filter

Back
Top Bottom