This is an app made by a reddit user to manage the ESSENTIAL_LAYOUT_WHITELIST setting.
You can use this app to only whitelist apps that you need, instead of whitelisting all apps.
Note that you will still need ADB to grant permission to this app:
adb shell pm grant in.tsdo.elw android.permission.WRITE_SECURE_SETTINGS
You only need to do this once, then you can use the app normally.
This app only shows user apps. Please do give feedback if you find any system app that behaves differently than it was.
Google Play
Download(Github)
edit: credits to oracleicom
All credit for this app goes to /u/TsFreddie over on the /r/essential subreddit.
Yes. First up Nova!!!
Sent from my PH-1 using Tapatalk
This is now on Google Play: https://play.google.com/store/apps/details?id=in.tsdo.elw
But you still MUST run that permissions code in ADB.
adb shell pm grant in.tsdo.elw android.permission.WRITE_SECURE_SETTINGS
Click to expand...
Click to collapse
I was wondering when will this get posted here since I can't post link.
But, just a heads up: the old package name got suspended by google. So the package name changed, and the ADB command should change correspondingly.
Code:
adb shell pm grant in.tsdo.elw android.permission.WRITE_SECURE_SETTINGS
TsFreddie said:
I was wondering when will this get posted here since I can't post link.
But, just a heads up: the old package name got suspended by google. So the package name changed, and the ADB command should change correspondingly.
Code:
adb shell pm grant in.tsdo.elw android.permission.WRITE_SECURE_SETTINGS
Click to expand...
Click to collapse
I updated the OP with this :good:
This is great !! Is there a reason why essential didn't do this out of the box?
How'd you guys get ADB drivers to work. I can't locate any that'll work for some reason. Could be my current adb drivers are messing with it. It works fine for my LG and Samsung phones but my adb won't show the Essential phone...
gqukyo said:
How'd you guys get ADB drivers to work. I can't locate any that'll work for some reason. Could be my current adb drivers are messing with it. It works fine for my LG and Samsung phones but my adb won't show the Essential phone...
Click to expand...
Click to collapse
Assuming you're on Windows, reboot with driver signing disabled and force update drivers to the one Google distributes with the sdk.
I got some universal ones to work. However, now my issue is that the authorize PC pop up doesn't actually pop up when I connect. I've google and none of the solutions worked... I just want to swap out the app switcher and back buttons... :T
gqukyo said:
How'd you guys get ADB drivers to work. I can't locate any that'll work for some reason. Could be my current adb drivers are messing with it. It works fine for my LG and Samsung phones but my adb won't show the Essential phone...
Click to expand...
Click to collapse
The older minimal adb packages won't work, and the failures look like driver issues.
Get the new adb and try again.
I got it working now. Just had to use another PC.
Deleted
---------- Post added at 06:28 AM ---------- Previous post was at 05:47 AM ----------
this app worked perfectly! Love it when it's using the extra room! Thanks for the help!
So, my question. Since I did the whitelist all (with the *) what's the remove command for that line? so that I can actually use this selective whitelist?
vexx109 said:
So, my question. Since I did the whitelist all (with the *) what's the remove command for that line? so that I can actually use this selective whitelist?
Click to expand...
Click to collapse
Uploading the new list will over write the existing values.
If you want return the value to stock use,
adb shell settings delete global ESSENTIAL_LAYOUT_WHITELIST
After you guys changed permissions, did you get the OTA update no problem? Did the hack stick or did you need to reapply the shell command?
I did the mods via ADB and they have stuck after the upgrade, either that or Essential has added apps to their whitelist as part of this upgrade.
Thank you so much for this easy way to whitelist without having to wait for Essential!!
Curious what other apps you all have white-listed to full screen (I have only done Nova Prime) with good results...
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
TsFreddie said:
I was wondering when will this get posted here since I can't post link.
But, just a heads up: the old package name got suspended by google. So the package name changed, and the ADB command should change correspondingly.
Code:
adb shell pm grant in.tsdo.elw android.permission.WRITE_SECURE_SETTINGS
Click to expand...
Click to collapse
Thank you!
I whitelisted Nova, Textra, calander and instapaper. Thinking of switching to the global whitelist, but haven't done that yet.
This is so much nicer than fighting with the ADB permissions. I kept missing an app here or there editing it manually. Thank you brilliant lovely folks.
bugsy said:
I whitelisted Nova, Textra, calander and instapaper. Thinking of switching to the global whitelist, but haven't done that yet.
Click to expand...
Click to collapse
A few apps don't work properly. Personally I would just use this app and select all by default, then turn off any apps that you notice has glitches as you see them.
(NOTE: this post is a duplicate of a similar thread I started on the Android Central user forum)
Hello everyone,
In the continuing saga of the Leagoo T5C i bought before the holidays from GearBest, I've seen the good (the price and overall build quality, along with a reasonably good user experience), the bad (some notifications that I just can't get rid of, among other things), and I now present you the ugly: after watching a review video on YouTube about my device, I learned that it came loaded with a Trojan called "Gorilla.AM"...
***EDIT: apparently, the Trojan's name could actually be "Guerrilla.AM", I'm not sure.***
Needless to say, I did as the tester had, and installed Malwarebytes, which, sure enough, found the exact same Trojan on my device.
You can watch the video here: https://www.youtube.com/watch?v=R5l3z7BvBtk
It so happens that it's embedded in Leagoo's own application launcher, called Sujet (in French; maybe it's called "Subject" in English, I don't know). I can force quit the application, since I use another launcher called Apex (good pick, by the way), but Malwarebytes can't seem to shake the Trojan off my device nonetheless.
A quick search on Google gives very little in the way of information about this malware, but I'd like to be on the safe side, so I came here.
Any contribution would be welcome at this stage.
Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.
Lannig said:
Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.
Click to expand...
Click to collapse
Hi,
OK, first off, thanks for the reply. Secondly, as I've stated before, I'm new to Android, and though I know my way around the command line in both Windows, Linux et OS X (not so much macOS: my MacBook Pro is 12-years old...), I suppose there are some things to set up first, before you can actually do what you suggest.
I understand that ADB stands for Android Debug Bridge, so is it an existing functionality in, say, Windows, that you can trigger from the command line, or a third-party software you have to install first?
On the Android side, what action should I take? Any Developer command to enable/disable to let ADB interact with my device the way it's supposed to?
Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help
Lannig said:
Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help
Click to expand...
Click to collapse
OK, thanks for the heads-up; I've already installed a Terminal emulator on the phone, so I'm gonna give it a go in a moment. I concur about Phoneandroid, alas: I've just received flak from one of the moderators because I'd double-posted on the same subject, whereas I'd just posted one thread, in the wrong part of the forum, according to him. Go figure...
OK, please feed back on your attempts, both from terminal emulator and through ADB.
Alas, I suspect that root will be required. It was for me on my Z5 and M5 to get rid of Leagoo's crapware.
Phonandroid is a bunch of losers with bloated egos posing as experts when 2/3 of the replies given are total BS.
"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...
"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...
(Additional question, not quite related: Aida64 indicates that my device runs a 4.4.49 version of the Android kernel, when the current version for Android 7.x is supposed to be 4.4.1; how does that compute--no pun intended--with my issue?)
Missing adb command is because the adb.exe (Windows) or adb (Mac) file is not in the command path. Either make the folder that contains the adb[.exe] file the current folder using the cd command or use whatever context menu for opening a command line window within the currently selected folder works, or even add that folder to the PATH variable. Google "add directory to path" for Windows and MacOS.
No idea about the kernel version. Minor kernel versions may vary within an Android release. Not surprising and most definitely unrelated to your problem. The crapware certainly isn't part of the kernel. It's most likely a system app i.e. a folder within either /system/app or /system/priv-app folders. You can't delete it without root, but you might be able to disable (freeze) it with the commands I gave you.
OK, thanks. I did "cd" to the folder where I had unzipped ADB on Windows (on the Mac, when I tried to open the ADB executable, I got a "cpu not supported" error message in the Terminal, as I feared, since my MBP is 32-bit-only, and most Mac applications nowadays only support 64-bit CPUs), and still got the "adb unrecognized command" error in PowerShell.
The phone was plugged in, and the right USB mode, so I'm still a bit baffled here. Gonna try it again with a different approach. Will keep you posted.
Over and out...
OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?
UglyStuff said:
OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?
Click to expand...
Click to collapse
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
rhn19 said:
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
Click to expand...
Click to collapse
If you are new to this, use an app from play store for uninstalling and integrating apps.
Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!
UglyStuff said:
Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!
Click to expand...
Click to collapse
Jailbreaking vs Rooting is like 5-1 on difficulty level. Because Android is Open source while IOS is not. I would highly suggest you Root it if your phone does not have warranty. After all something that is on /system partition like your launcher will need superuser access to modify it. I cannot think of a way that wont void your warranty.
You can flash TWRP and then boot into aroma-fm but that will void your warranty. Rooting is the preferred option here.
Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.
UglyStuff said:
Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.
Click to expand...
Click to collapse
Why do you want a new firmware? I don't get you man, do you want to clear out the malware or try a new ROM? Because i think you would have to build a new ROM, there is not one available i guess.
That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...
UglyStuff said:
That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...
Click to expand...
Click to collapse
If you use malwarebytes after root that thing wont happen. And almost all of the OEMs have a trigger which voids when rooting or flashing firmware. After that the OEM wont give you updates unless you use the A/B partitioning system.
OK, I understand how rooting my phone would void the warranty: after all, it's a substantial change in the phone software, and the OEM can't be made responsible for any mishap that occurs after I've rooted the phone.
What's the A/B partitioning system (I suppose it helps partition your storage space)? I don't have a microSD card installed (I use the slot for my second SIM), but I do have 32 Gb of storage space, minus what's already used up.
Do you know KingRoot? Is it as good and (reasonably) safe a rooting tool as they say it is?
I remember I was able to do this previously on some galaxy phones/tablets I owned, by flashing stock recovery and factory resetting the phone.
I ask because I was given brand new s10e by my company and I am a no-gapps lineage user currently. I wish to retain such a setup, but I am afraid of tampering with the phone and possibly being charged money if/when I decide to leave the company in the future?
By bone stock I mean to exactly the same state as when I received it- stock system, stock recovery, nothing noticably different? Or how far can I get, at least?
Thank you in advance for any guidance
Depending on your model, you might not even be able to do what you want.
But i see no reason to worry if you can by using Odin and correct firmware after.
But there can be issues such as Snapdragons not exceeding 80% charge (if you even can unlock the bootloader).
Chances are you have to keep it stock and ADB out the apps you don't like.
The phone is going to work better without Lineage unless i've missed that volte is now a go.
mindlery said:
Depending on your model, you might not even be able to do what you want.
But i see no reason to worry if you can by using Odin and correct firmware after.
But there can be issues such as Snapdragons not exceeding 80% charge (if you even can unlock the bootloader).
Chances are you have to keep it stock and ADB out the apps you don't like.
The phone is going to work better without Lineage unless i've missed that volte is now a go.
Click to expand...
Click to collapse
Hi!
I forgot to mention the model- its sm-g970f (exynos)
Can I remove google and samsung apps with adb and return them later without compromising the android system? Do you know of any good guide on how to do this?
As far as I understand you will trip Knox irreversibly if you unlock the bootloader. Hence you cannot get back anymore. The closest you can get to your needs is by disabling most Google and Samsung apps by ADB and install a theme that mimics AOSP. Then, a factory reset will get your device back to its original state. Check https://forum.xda-developers.com/galaxy-s10/how-to/galaxy-s10-s10-debloat-bloatware-t3912073/page40 for more info.
macchio said:
Hi!
I forgot to mention the model- its sm-g970f (exynos)
Can I remove google and samsung apps with adb and return them later without compromising the android system? Do you know of any good guide on how to do this?
Click to expand...
Click to collapse
You can disable any app, including systems apps WITHOUT root by following this guide.
First, make a make a backup list of all your currently installed apps via ADB:
adb shell pm list packages -f >C:\AppList.txt
For example, let's "uninstall" the Samsung Smart Switch app which can be found in the above AppList.txt file as
/system/preload/SmartSwitch/SmartSwitch.apk=com.sec.android.easyMover
Sometimes the app's name matches the package/file name perfectly, sometimes they are a little different and takes a bit of guessing.
The package name of the Samsung Smart Switch app is "com.sec.android.easyMover", with its path and file name "/system/preload/SmartSwitch/SmartSwitch.apk", as you can see at least the path and file name contains the name of the app.
To disable it via the "uninstall" command, enter:
adb shell pm uninstall -k --user 0 <package_name>
Example:
adb shell pm uninstall -k --user 0 com.sec.android.easyMover
OR
adb shell cmd package uninstall -k --user 0 com.sec.android.easyMover
Now, to re-enable the above "uninstalled" apps or any other specific one without a factory reset, simply copy and paste the app's package name from the AppList.txt into this command:
adb shell cmd package install-existing <package_name>
Example:
adb shell cmd package install-existing com.sec.android.easyMover
Simple as that!
Is it possible to install a different (older) version of a S Health app – without rooting and patching system with Lucky Patcher or else?
WHY? - Older version of S Health has a feature of SpO2 measurement (oximeter) on S5 while Marshmallow preinstalled S Health does not.
I tried uninstalling the app through adb shell via pm uninstall user 0 yada-yada but even though it looked like it did, I still couldn't install older version
Code:
adb shell via pm uninstall user 0 yada-yada
doesn't physically remove an app, but only hides it to user.
Knowing app's package name you can physically remove it by running
Code:
adb shell "rm -r '/data/app/<PKG-NAME>*'"
But I have a locked non-rooted device... or can I still do it that?
Code:
adb devices
adb shell "rm -r '/data/app/com.sec.android.app.shealth*'"
Also, is the end of the 2nd line correct or there is some typo? (*)
As I can see you have either none at all or only very little knowledge of Linux what Android is based on: the asterisk in the code-line of course isn't a typo, in Linux it represents a wildcard.
I see nothing bad in not knowing deeply Linux for average user. Anyway, thanks. It says "No such file or directory", also tried app-priv folder to no avail. Wherever preinstalled apps hide themselves on Marshmallow, it's not there.
Maybe will need to go asking to Samsung forum on XDA, maybe developers there know more knowledge in Samsung firmwares/ROMs.
AjvarXX said:
I see nothing bad in not knowing deeply Linux for average user. Anyway, thanks. It says "No such file or directory", also tried app-priv folder to no avail. Wherever preinstalled apps hide themselves on Marshmallow, it's not there.
Maybe will need to go asking to Samsung forum on XDA, maybe developers there know more knowledge in Samsung firmwares/ROMs.
Click to expand...
Click to collapse
Exactly, we all start at the beginning.
This might be helpful:
`adb pull` from app data directory without root access
`adb pull` from app data directory without root access - readme.md
gist.github.com
AjvarXX said:
It says "No such file or directory", also tried app-priv folder to no avail. Wherever preinstalled apps hide themselves on Marshmallow, it's not there.
Click to expand...
Click to collapse
My last 2 cents here:
You may check for the app in question is a user-app or not. You do this by running
Code:
adb devices
adb shell "pm list packages -3"
If the app isn't in the list returned then it's not an user-app but a system-app what can't get uninstalled without superuser rights, will say Android must be rooted.
**SOLVED - I restared the phone and everything works as it should. Follow trouble shooting lesson #1 - Unplug and plug it back in**
I'm looking for help to troubleshoot my text messaging after using ADB to uninstall some packages.
The phone is a Oneplus 9 from Tmobile, and I have a verizon account/SIM card. My original intention was to completely delete the bloatware / unused applications from my phone but the script I was running (Tomatot's script) is not updated for Android 11 and I ended up abandoning that route and instead just used the ADB commands to uninstall. As such, I did unlock the bootloader, installed TWRP, and used TWRP to run a version of the Tomatot script. I noted nothing changed, and did not try to revert or undo the Tomatot script.
I then went to ADB commands and uninstalled the below list of packages:
package:com.oneplus.calculatorpackage:com.android.cts.priv.ctsshimpackage:com.oneplus.gamespacepackage:com.sprint.ecidpackage:com.google.android.cellbroadcastservicepackage:com.sprint.w.installerpackage:cn.oneplus.photospackage:com.tmobile.m1package:com.qualcomm.uimremoteclientpackage:com.oneplus.brickmodepackage:com.netflix.partner.activationpackage:com.tmobile.pr.mytmobilepackage:com.oneplus.factorymode.specialtestpackage:com.google.ar.corepackage:com.oneplus.android.cellbroadcast.overlaypackage:com.google.android.marvin.talkbackpackage:com.oneplus.factorymodepackage:com.android.eggpackage:com.google.android.apps.tachyonpackage:com.sprint.ms.cdmpackage:net.oneplus.pushpackage:com.android.dreams.basicpackage:com.google.android.apps.wellbeingpackage:com.tmobile.pr.adaptpackage:com.android.bipspackage:com.android.cellbroadcastreceiverpackage:cn.oneplus.oemtcmapackage:com.oneplus.filemanagerpackage:com.google.android.ttspackage:com.sprint.ce.updaterpackage:com.google.android.videospackage:com.oneplus.faceunlockpackage:com.google.android.feedbackpackage:com.oneplus.opbugreportlitepackage:com.tmobile.rsuadapter.qualcommpackage:com.oneplus.screenrecordpackage:com.android.providers.partnerbookmarkspackage:com.android.wallpaper.livepickerpackage:com.oneplus.bttestmodepackage:net.oneplus.commonlogtoolpackage:com.android.bookmarkproviderpackage:com.android.cts.ctsshimpackage:com.android.wallpaperbackuppackage:com.sprint.ms.smf.servicespackage:com.google.android.apps.youtube.musicpackage:com.android.traceurpackage:com.google.android.cellbroadcastreceiverpackage:com.tmobile.rsuapppackage:com.tmobile.rsusrvpackage:com.android.cellbroadcastreceiver.overlay.common
Can anyone here take a look at my uninstalled packages and easily tell which one is related to text messaging? I would hope to easily find the one or two from this list instead of re-enabling each one and see if texting is restored.
At this point my options are - start enabling packages via ADB commands to see if texting is fixed, or factory reset -> verify texting and other functionality works -> use ADB to uninstall packages and test texting/other functions after each package.
Thanks for any help in advance!
(I did find a thread about using Magisk Debloater to remove bloat and will look into that method since the Tomatot script with TWRP did not work for me. First I need to fix texting or my wife will kill me)
RonnieDoitch said:
I'm looking for help to troubleshoot my text messaging after using ADB to uninstall some packages.
The phone is a Oneplus 9 from Tmobile, and I have a verizon account/SIM card. My original intention was to completely delete the bloatware / unused applications from my phone but the script I was running (Tomatot's script) is not updated for Android 11 and I ended up abandoning that route and instead just used the ADB commands to uninstall. As such, I did unlock the bootloader, installed TWRP, and used TWRP to run a version of the Tomatot script. I noted nothing changed, and did not try to revert or undo the Tomatot script.
I then went to ADB commands and uninstalled the below list of packages:
package:com.oneplus.calculatorpackage:com.android.cts.priv.ctsshimpackage:com.oneplus.gamespacepackage:com.sprint.ecidpackage:com.google.android.cellbroadcastservicepackage:com.sprint.w.installerpackage:cn.oneplus.photospackage:com.tmobile.m1package:com.qualcomm.uimremoteclientpackage:com.oneplus.brickmodepackage:com.netflix.partner.activationpackage:com.tmobile.pr.mytmobilepackage:com.oneplus.factorymode.specialtestpackage:com.google.ar.corepackage:com.oneplus.android.cellbroadcast.overlaypackage:com.google.android.marvin.talkbackpackage:com.oneplus.factorymodepackage:com.android.eggpackage:com.google.android.apps.tachyonpackage:com.sprint.ms.cdmpackage:net.oneplus.pushpackage:com.android.dreams.basicpackage:com.google.android.apps.wellbeingpackage:com.tmobile.pr.adaptpackage:com.android.bipspackage:com.android.cellbroadcastreceiverpackage:cn.oneplus.oemtcmapackage:com.oneplus.filemanagerpackage:com.google.android.ttspackage:com.sprint.ce.updaterpackage:com.google.android.videospackage:com.oneplus.faceunlockpackage:com.google.android.feedbackpackage:com.oneplus.opbugreportlitepackage:com.tmobile.rsuadapter.qualcommpackage:com.oneplus.screenrecordpackage:com.android.providers.partnerbookmarkspackage:com.android.wallpaper.livepickerpackage:com.oneplus.bttestmodepackage:net.oneplus.commonlogtoolpackage:com.android.bookmarkproviderpackage:com.android.cts.ctsshimpackage:com.android.wallpaperbackuppackage:com.sprint.ms.smf.servicespackage:com.google.android.apps.youtube.musicpackage:com.android.traceurpackage:com.google.android.cellbroadcastreceiverpackage:com.tmobile.rsuapppackage:com.tmobile.rsusrvpackage:com.android.cellbroadcastreceiver.overlay.common
Can anyone here take a look at my uninstalled packages and easily tell which one is related to text messaging? I would hope to easily find the one or two from this list instead of re-enabling each one and see if texting is restored.
At this point my options are - start enabling packages via ADB commands to see if texting is fixed, or factory reset -> verify texting and other functionality works -> use ADB to uninstall packages and test texting/other functions after each package.
Thanks for any help in advance!
(I did find a thread about using Magisk Debloater to remove bloat and will look into that method since the Tomatot script with TWRP did not work for me. First I need to fix texting or my wife will kill me)
Click to expand...
Click to collapse
You def removed brickmode and unsure if you can still connect through edl to msm tool. Btw this would be your only option is to restore everything with msm tool for your variant. Or fastboot flash whatever build your on back to device.
Index of /list/Unbrick_Tools
mattie_49 said:
You def removed brickmode and unsure if you can still connect through edl to msm tool. Btw this would be your only option is to restore everything with msm tool for your variant. Or fastboot flash whatever build your on back to device.
Index of /list/Unbrick_Tools
Click to expand...
Click to collapse
Thank you for the response. Brickmode, as far as I can tell from internet searching, is related to Oneplus's 'Zen Mode' which I do not need or want. If I am mistaken please point me to a discussion about this particular package so I can reinstall it if its required for recovering from bricking a phone. I think its a deceptively named package.
I started re-enabling the packages above and after a phone restart all my texts came back. I then un-installed the packages one by one and none of them affect texting. Soooo I think it was the phone restart that fixed it. As always, turn it off and back on first to see if that fixes the problem.
RonnieDoitch said:
Thank you for the response. Brickmode, as far as I can tell from internet searching, is related to Oneplus's 'Zen Mode' which I do not need or want. If I am mistaken please point me to a discussion about this particular package so I can reinstall it if its required for recovering from bricking a phone. I think its a deceptively named package.
I started re-enabling the packages above and after a phone restart all my texts came back. I then un-installed the packages one by one and none of them affect texting. Soooo I think it was the phone restart that fixed it. As always, turn it off and back on first to see if that fixes the problem.
Click to expand...
Click to collapse
Glad you got it worked out.
RonnieDoitch said:
Thank you for the response. Brickmode, as far as I can tell from internet searching, is related to Oneplus's 'Zen Mode' which I do not need or want. If I am mistaken please point me to a discussion about this particular package so I can reinstall it if its required for recovering from bricking a phone. I think its a deceptively named package.
I started re-enabling the packages above and after a phone restart all my texts came back. I then un-installed the packages one by one and none of them affect texting. Soooo I think it was the phone restart that fixed it. As always, turn it off and back on first to see if that fixes the problem.
Click to expand...
Click to collapse
Glad you got it worked out. Maybe try looking into this thread.
Thread '[ADB DEBLOAT] [OOS 12, 11 & Custom ROMs] [2021.12.20 - v2.0] Extreme debloat your OnePlus 9' https://forum.xda-developers.com/t/...-v2-0-extreme-debloat-your-oneplus-9.4283263/