bug(scope): Risky packages in recomended section/

[franekk3]

Describe the bug

I know using this app is on my own risk, and I understand it but I think apps that after delation may couse phone crushing shouldn't be at "recomended" section. On my samsung A40 it make it boot looping, luckily I it was having always accept adb to my pc and adb procces was starting even if os crushed. So i was able to boot into recovery.

Expected behavior

I think packages from recommended section should me only safe t odelete ones :)

You have a solution?

No response

Operating System

Linux

Distro version

No response

Window System + Manager

No response

Desktop Environment

No response

ADB version

No response

Provide logs

Log

Please replace this line by the log-file contents

Acknowledgements

• This issue is not a duplicate of an existing bug report.
• I have chosen an appropriate title.
• All requested information has been provided properly.

[sigma2017]

I just removed most of the recommended apps (not all) on a Samsung S10 plus and after I restarted the phone it can't boot anymore, is in infinite restart loop. The only solution is to reflash with Odin.

[qqtb]

Same here, same problem for a Samsung S10 - restart loop. I have done it a few weeks ago and it wasnt a problem back then. I did it yesterday again on a fresh device and now i get the loop. What I noticed is that a few weeks ago the total number of items recommended to remove was around ~ 189, now it is 172. So whatever has been added causes this I believe.

[slvlng]

Same here, same problem for a Samsung S10 - restart loop. I have done it a few weeks ago and it wasnt a problem back then. I did it yesterday again on a fresh device and now i get the loop. What I noticed is that a few weeks ago the total number of items recommended to remove was around ~ 189, now it is 172. So whatever has been added causes this I believe.

Post a list of uninstalled packages.

[rudhm]

Device: Samsung Galaxy A20s (SM-A207 series)

I experienced the same issue when removing packages from the Recommended section.

What happened

• I removed all packages marked as "Recommended" using Universal Android Debloater.
• After reboot, the phone got stuck in a boot loop.
• The device reached the Samsung logo but Android never finished booting.

Attempted recovery

1. I performed a factory reset from recovery.
2. The phone booted normally again.
3. I repeated the same process (removed all recommended packages again).
4. After reboot, the boot loop happened again, confirming the issue is reproducible.

Boot log investigation

I captured logs using ADB during boot:

adb wait-for-device logcat > bootlog.txt

From the logs we observed:

• PackageManager errors about missing shared libraries (Samsung framework components).
• RescueParty being triggered due to repeated system server failures.
• A crash while starting Persona / Knox services.
• Multiple service initialization failures after system_server starts.

Example patterns from the log:

PackageManager: missing shared library
RescueParty triggered
SystemServer: Starting PersonaManagerService
java.lang.NullPointerException

This suggests that one or more packages currently listed as "Recommended" may actually be dependencies for Samsung framework or Knox services.

List of packages removed

I removed all packages marked as Recommended, including:

android.autoinstalls.config.samsung
com.android.calllogbackup
com.android.egg
com.android.networkstack.tethering.inprocess
com.android.providers.partnerbookmarks
com.android.traceur
com.facebook.appmanager
com.facebook.katana
com.facebook.services
com.facebook.system
com.google.android.apps.maps
com.google.android.apps.restore
com.google.android.apps.tachyon
com.google.android.apps.youtube.music
com.google.android.feedback
com.google.android.gm
com.google.android.gms.location.history
com.google.android.projection.gearhead
com.google.android.youtube
com.microsoft.skydrive
com.netflix.mediaclient
com.netflix.partner.activation
com.qualcomm.atfwd
com.qualcomm.embms
com.samsung.android.app.omcagent
com.samsung.android.app.updatecenter
com.samsung.android.beaconmanager
com.samsung.android.da.daagent
com.samsung.android.easysetup
com.samsung.android.fmm
com.samsung.android.mdm
com.samsung.android.mdx.kit
com.samsung.android.networkdiagnostic
com.samsung.android.scloud
com.samsung.android.securitylogagent
com.samsung.android.smartcallprovider
com.samsung.android.smartswitchassistant
com.samsung.android.stickercenter
com.samsung.android.timezone.data_R
com.samsung.faceservice
com.samsung.ipservice
com.samsung.mlp
com.samsung.rcs
com.samsung.storyservice
com.sec.android.daemonapp
com.sec.android.easyMover.Agent
com.sec.android.preloadinstaller
com.sec.bcservice
com.sec.enterprise.knox.cloudmdm.smdms
com.sec.enterprise.mdm.services.simpin
...

(I removed the full recommended list.)

Observation

The device boots normally until system_server begins starting Samsung framework services, after which crashes occur and Android enters a boot loop.

Suggestion

Some Samsung framework or Qualcomm service packages in the Recommended category may actually be device-specific dependencies and should probably be moved to:

• Advanced
• or Unsafe

to prevent boot loops on certain Samsung devices.

Let me know if I can provide the full boot log or additional debugging info.

[slvlng]

I removed all packages marked as Recommended
(I removed the full recommended list.)

Suggestion

Some Samsung framework or Qualcomm service packages in the Recommended category may actually be device-specific dependencies and should probably be moved to:

• Advanced
• or Unsafe

See #1311...