Database Users

[VZW] XT1767: Possible Safestrap?

So, everyone remembers the VZW Samsung Galaxy Note 2 (i605)? I have one I got second hand that had already taken the fatal-final-OTA update that permalocked the bootloader down.. however, I have still rooted and installed Safestrap recovery and damn-near fully customised and tweaked it to my liking(custom boot animation, room slots active, etc)..Well, what about a possible Safestrap-style recovery that could run without root permissions by running some sort of workaround-script?....or would root access still be inevitably needed? Perhaps have the Safestrap recovery create a fully-functioning isolated with admin privileges, something similar to the Island Sandbox Experiment app?

I don't think it would be possible, bootloader's have become super secure in the past 4 years.
Sent from my Moto E4 using XDA Labs

What about possibly using ADB to manually install a superuser APK file and also using ADB commands like 'pm grant ....... WRITE_SECURE_SETTINGS' to manually enable the permissions and privileges required for installing an SU binary?

That's a good idea if it works. I was able to remove all the Verizon apps from the phone using adb commands.

chrislind said:
That's a good idea if it works. I was able to remove all the Verizon apps from the phone using adb commands.
Click to expand...
Click to collapse
You completely removed the Verizon apps and not just disabled them?
What adb commands did you use please?
Thanks.

adb shell pm uninstall -k --user 0 com.motorola.setupwizard.phoneservice
adb shell pm uninstall -k --user 0 com.vzw.hss.myverizon
adb shell pm uninstall -k --user 0 com.verizon.messaging.vzmsgs
adb shell pm uninstall -k --user 0 com.motorola.vzw.cloudsetup
adb shell pm uninstall -k --user 0 com.vzw.qualitydatalog
adb shell pm uninstall -k --user 0 com.verizon.mips.services
adb shell pm uninstall -k --user 0 com.motorola.vzw.settings.extensions
adb shell pm uninstall -k --user 0 com.vznavigator.Generic
adb shell pm uninstall -k --user 0 com.motorola.vzw.provider
adb shell pm uninstall -k --user 0 com.gotv.nflgamecenter.us.lite
adb shell pm uninstall -k --user 0 com.motorola.email
adb shell pm uninstall -k --user 0 com.vcast.mediamanager
adb shell pm uninstall -k --user 0 com.google.android.apps.tachyon
adb shell pm uninstall -k --user 0 com.google.android.videos
adb shell pm uninstall -k --user 0 com.google.android.music
adb shell pm uninstall -k --user 0 com.google.android.apps.docs
adb shell pm uninstall -k --user 0 com.lenovo.FileBrowser2

chrislind said:
adb shell pm uninstall -k --user 0 com.motorola.setupwizard.phoneservice
adb shell pm uninstall -k --user 0 com.vzw.hss.myverizon...
Click to expand...
Click to collapse
I believe that this procedure actually only disables the apps, although it appears that they are uninstalled. It is my understanding that a factory reset will re-enable/re-install all the apps. Read about half-way down this page.

mn1968 said:
I believe that this procedure actually only disables the apps, although it appears that they are uninstalled. It is my understanding that a factory reset will re-enable/re-install all the apps. Read about half-way down this page.
Click to expand...
Click to collapse
100% correct.

Debloat with ADB Shell [No Root]

See topic where package disablers are used first:
https://forum.xda-developers.com/tab-s5e/how-to/samsung-galaxy-tab-s5e-debloat-root-info-t3935010
See explained why you as a consumer should not buy or use package disablers:
https://forum.xda-developers.com/showpost.php?p=80048718&postcount=42
Thanks to TiTiB for finding many package names:
https://forum.xda-developers.com/member.php?u=6773321
The package names you can find in the original topic. That's in the topmost hyperlink in this post.
This does not void warranty, but in worse case, you need factory reset.
I recommend anyone wanting to debloat using ADB SHELL procedure, it's easy if you have a Linux USB stick or Linux installation.
First time you've been reading about ADB command? Instructions setting up your phone and computer here:
https://www.xda-developers.com/install-adb-windows-macos-linux/
In Linux, in this case a Debian based distribution like Ubuntu
Code:
sudo apt install adb
Then enable developer mode in your tablet by pressing the Kernel Build number until it says you have enabled developer mode. Learn how to control over a USB cable with ADB commands how to disable or enable packages for the current user ( which is user 0 ). This does not require root, and you will keep your warranty. In your phone settings menu the Developer section will appear and there you need to enable ADB Debugging. Then you start using ADB. See included link far below if this is your first time.
The first command after installing ADB at your Linux system is
Code:
adb shell
If you are using Windows or are new to using ADB:
https://www.xda-developers.com/disable-system-app-bloatware-android/
It's assumed you already in the adb shell with the command above.
You are then in your Tablet in a shell running at it.
For example to DISABLE Bixby you can simply do this
Code:
pm disable-user --user 0 com.samsung.android.bixby.wakeup
pm disable-user --user 0 com.samsung.android.app.spage
pm disable-user --user 0 com.samsung.android.app.routines
pm disable-user --user 0 com.samsung.android.bixby.service
pm disable-user --user 0 com.samsung.android.visionintelligence
pm disable-user --user 0 com.samsung.android.bixby.agent
pm disable-user --user 0 com.samsung.android.bixby.agent.dummy
pm disable-user --user 0 com.samsung.android.bixbyvision.framework
You can list disabled packages with this
Code:
pm list packages -d
To ENABLE Bixby again you can do this
Code:
pm enable com.samsung.android.bixby.wakeup
pm enable com.samsung.android.app.spage
pm enable com.samsung.android.app.routines
pm enable com.samsung.android.bixby.service
pm enable com.samsung.android.visionintelligence
pm enable com.samsung.android.bixby.agent
pm enable com.samsung.android.bixby.agent.dummy
pm enable com.samsung.android.bixbyvision.framework
Or this
Code:
pm enable --user 0 com.samsung.android.bixby.wakeup
pm enable --user 0 com.samsung.android.app.spage
pm enable --user 0 com.samsung.android.app.routines
pm enable --user 0 com.samsung.android.bixby.service
pm enable --user 0 com.samsung.android.visionintelligence
pm enable --user 0 com.samsung.android.bixby.agent
pm enable --user 0 com.samsung.android.bixby.agent.dummy
pm enable --user 0 com.samsung.android.bixbyvision.framework
For example to UNINSTALL Bixby PERMANENTLY, in the past for Android 6 or less, until Factory Reset you can do this [ Not recommended ?]
See supplemental code written inside this topic, you can bring back uninstalled packages without problem provided you have Android 7 or later!
Code:
pm uninstall -k --user 0 com.samsung.android.bixby.wakeup
pm uninstall -k --user 0 com.samsung.android.app.spage
pm uninstall -k --user 0 com.samsung.android.app.routines
pm uninstall -k --user 0 com.samsung.android.bixby.service
pm uninstall -k --user 0 com.samsung.android.visionintelligence
pm uninstall -k --user 0 com.samsung.android.bixby.agent
pm uninstall -k --user 0 com.samsung.android.bixby.agent.dummy
pm uninstall -k --user 0 com.samsung.android.bixbyvision.framework
There are several apps at the Google Playstore which can give you an exact package name for any given application. But simplest method is learning which options the pm in an ADB shell has.
example commands for ADB
Code:
adb shell pm list packages
pm list packages
If you uninstalled with ADB you can only Factory Reset to get the packages back, the Disable/Enable method however work fine without Factory reset to get packages back. I updated this entire post accordingly thanks to another user.
Before you remove all phone like packages, Samsung has Call and Message Continuity working for Galaxy S10, some countries since a few weeks Galaxy S9 and hopefully promised later this year also for the S8. This means you can use your phone to call with your tablet even if it only has WIFI provided you have your phone as is listed as example also connected to WIFI.
If you use ADB shell procedure, you must first write down with package you disable or enable by a text editor if you want to undo the changes. If you don't know the package name you disabled you can not enable it anymore unless you factory reset your device.
Hence the easy example of Bixby, and its package names listed in case you want Bixby back.
I am sure this tutorial I wrote uninstalls a package, but it might be safer you disable a package with ADB commands.
This XDA tutorial below might be the safest method described in following link
https://www.xda-developers.com/disable-system-app-bloatware-android/
This post had been updated to show the difference between JUST DISABLING and PERMANENTLY UNINSTALL of a given package name. The difference is once you use the uninstall method only a factory reset brings that package back, just disabling makes you able to enable it again without problem. Therefore JUST DISABLING is RECOMMENDED ONLY.
New information about ADB commands:
If you have used the UNINSTALL method, here commands to get those packages back.
https://forum.xda-developers.com/android/help/how-to-install-uninstalled-packages-t3894235
you can simply use "adb shell cmd package install-existing <package name>" in ADB and you'll get the package back .
By @Vordx
Click to expand...
Click to collapse
Good news everyone for those whom uninstalled Bixby for user 0, I was successfuly able to get Bixby back with the following commands which indeed work.
Code:
adb shell
You are now in a terminal at your computer interfacing with the tablet or phone
Code:
cmd package install-existing com.samsung.android.bixby.wakeup
cmd package install-existing com.samsung.android.app.spage
cmd package install-existing com.samsung.android.app.routines
cmd package install-existing com.samsung.android.bixby.service
cmd package install-existing com.samsung.android.visionintelligence
cmd package install-existing com.samsung.android.bixby.agent
cmd package install-existing com.samsung.android.bixby.agent.dummy
cmd package install-existing com.samsung.android.bixbyvision.framework
So you truly can uninstall Bixby or diable it and even reinstall Bixby without factory reset, that's really good news. I used Bixby as an example, since it is deep in official Samsung Rom its core. It does work to just use
Code:
cmd package install-existing <package name>
I got Bixby back with it, and that is really great since I now will uninstall it again, and You Do Not need To Factory Reset to get Uninstalled Packages back, try following procedure. I really used the uninstall commands over ADB Android Debugging Bridge and since the package was uninstalled for user 0, reinstall an existing package does work! That is great news, since it does not require a factory reset if you have to happen to uninstall for user 0 any package. The same is true but only for Android 7 and later. See the topic linked to that explains people with Android lower than 7 unable to do this. Seems Google did a good job regarding this.

If you know the package names you can use a simple script to automate it.
Post in thread '[Guide] Samsung Galaxy Tab S5e Debloat Without Root-Info' https://forum.xda-developers.com/t/...bloat-without-root-info.3935010/post-85910045

HD8 (8th gen) microphone issues

Hi all.
I've got a couple of these for the kids, bought in USA.
Google play etc installed on both.
One is running Fire 6.3.1.5 which it seems was installed yesterday. The other, for the moment, is at 6.3.1.4.
Just today, noticed YouTube Kids on the 6.3.1.5. doesn't allow mic search, yet the likes of "Talking Tom" works.
What should I do, kind folks, to fix this?
Thanks in advance.
SP

scrumpypaul said:
Hi all.
I've got a couple of these for the kids, bought in USA.
Google play etc installed on both.
One is running Fire 6.3.1.5 which it seems was installed yesterday. The other, for the moment, is at 6.3.1.4.
Just today, noticed YouTube Kids on the 6.3.1.5. doesn't allow mic search, yet the likes of "Talking Tom" works.
What should I do, kind folks, to fix this?
Thanks in advance.
SP
Click to expand...
Click to collapse
That's the problem because the microphone permission is not permitted. You can do over ADB:
Code:
//Enter ADB shell
adb shell
//Permit microphone permission
pm grant <package-name> android.permission.RECORD_AUDIO
//Example
pm grant com.facebook.orca android.permission.RECORD_AUDIO
//Disable unwanted OTA updates
pm disable-user --user 0 com.amazon.device.software.ota
pm disable-user --user 0 com.amazon.device.software.ota.override
pm disable-user --user 0 com.amazon.settings.systemupdates
pm disable-user --user 0 com.amazon.kindle.otter.oobe.forced.ota
//Disable part of Amazon services (before you do this, deregister your Fire tablet)
pm disable-user --user 0 com.amazon.dcp.contracts.library
pm disable-user --user 0 com.amazon.dcp
pm disable-user --user 0 com.amazon.kindle.otter.oobe
You can use sound meter app to test the microphone.

Thanks for that. If I get some time and some courage I may try it.

AmznUser444 Dev said:
That's the problem because the microphone permission is not permitted. You can do over ADB:
Code:
//Enter ADB shell
adb shell
//Permit microphone permission
pm grant <package-name> android.permission.RECORD_AUDIO
//Example
pm grant com.facebook.orca android.permission.RECORD_AUDIO
//Disable unwanted OTA updates
pm disable-user --user 0 com.amazon.device.software.ota
pm disable-user --user 0 com.amazon.device.software.ota.override
pm disable-user --user 0 com.amazon.settings.systemupdates
pm disable-user --user 0 com.amazon.kindle.otter.oobe.forced.ota
//Disable part of Amazon services (before you do this, deregister your Fire tablet)
pm disable-user --user 0 com.amazon.dcp.contracts.library
pm disable-user --user 0 com.amazon.dcp
pm disable-user --user 0 com.amazon.kindle.otter.oobe
You can use sound meter app to test the microphone.
Click to expand...
Click to collapse
I have the same issue, setting the permission in ADB didn't help. The microphone works fine in other apps, just not YouTube Kids. Any other thoughts?

Completely disable/remove Sprint OMA DM

Hi friends,
For various reasons, I want to completely prevent my Essential phone from launching sprint OMA DM with a Sprint SIM - not trying to provision it or communicate with Sprint provisioning at all. Does anyone know which processes I need to freeze to do that?
Thank you!

App Inspector from Play Store will give you the package name of apps to disable.
This is my list:
Stock Rom App Disable cmd:
adb shell pm disable-user --user 0 com.android.managedprovisioning
adb shell pm disable-user --user 0 com.essential.resources
adb shell pm disable-user --user 0 com.essential.legal
adb shell pm disable-user --user 0 com.ts.android.hiddenmenu
adb shell pm disable-user --user 0 com.ts.android.chameleon.chameleonprovider (Sprint OMA-DM provider)
adb shell pm disable-user --user 0 com.redbend.app (Sprint OMA-DM)
adb shell pm disable-user --user 0 com.ts.android.chameleon.systemdatahandler
adb shell pm disable-user --user 0 com.ts.android.chameleon.phonedatahandler
adb shell pm disable-user --user 0 com.ts.android.chameleon.datadispatcher
adb shell pm disable-user --user 0 com.ts.oemtelephonyapp
adb shell pm disable-user --user 0 com.essential.suw.welcome
adb shell pm disable-user --user 0 com.essential.ecore
adb shell pm disable-user --user 0 com.essential.essentialsuw
adb shell pm disable-user --user 0 com.essential.android.launcher.layouts.gms
adb shell pm disable-user --user 0 com.essential.klik (Essential Camera app)

Getting all blacklisted, system/user packages back any Fire OS version (Root only)

Hey Fire TV owners if you have an already unlocked Fire TV device whether it's .sh rooted via temp Magisk root or a fully unlockable device, you can input these commands to get all those packages back in working order and I thank @Pro-me3us for these commands from the Fire TV Cube Gen 3 (Gazelle) temp root guide.
Enable ADB debugging in Settings, My Fire TV, Developer Options.
adb connect 192.168.x.x or have it connected via USB adb.
adb devices,
su (grant root)
setenforce 0
echo '<?xml version="1.0" encoding="utf-8" standalone="yes" ?><map><set name="DenyListKeyPackages"></set></map>' > /data/system/PackageManagerDenyList
pm clear com.fireos.arcus.proxy
pm disable-user com.fireos.arcus.proxy
pm disable-user com.amazon.device.software.ota
pm clear com.amazon.device.software.ota
pm disable-user com.amazon.device.software.ota.override
pm clear com.amazon.device.software.ota.override
pm disable-user com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.tv.forcedotaupdater.v2
pm list packages -d
then reboot