Hi everyone!

​I’m looking to buy my very first chainsaw for simple work around the house (cutting some firewood, pruning branches, and basic yard cleanup).

​To be honest, I don't know much about chainsaws and how they work. I just want a reliable tool. I've narrowed it down to two entry-level models that fit my budget (240 dollars):

- ​Stihl MS 172

- ​Husqvarna 130

​Since I'm a complete beginner, I am looking for something that is easy to start, safe, and not overly complicated to maintain.

​Which of these two is the better choice for someone just starting out? Any basic tips for a newbie are also highly appreciated!

IMPORTANT NOTE: My absolute main priority is keeping/recovering my data (photos, videos, etc.). I want to avoid a Factory Reset at all costs unless there is absolutely no other way!

Hi everyone, I was trying to debloat my Motorola phone using ADB commands (adb shell pm uninstall --user 0 [PACKAGE_NAME]). I did this in two separate batches to be safe. After the first batch, I restarted the phone and everything worked perfectly. However, after the second batch and another restart, the phone completely crashed/soft-bricked (stuck in a bootloop/won't boot up).

Since professional repair is quite expensive in my area, I want to try and fix this myself via software. Here is the exact breakdown of what I did:

Batch 1 (Safe - Phone restarted and worked fine)

These are the apps I uninstalled/disabled without any issues:

• com.google.android.adservices.api, com.google.android.marvin.talkback, com.google.android.projection.gearhead
• com.motorola.mykey, com.motorola.att.phone.extensions, com.motorola.enterprice.adapter.service, com.motorola.bach.modemstats, com.motorola.account, com.motorola.help.extlog, com.motorola.iotservice, com.motorola.mobiledesktop.core, com.motorola.smartfeed, com.dti.motorola
• com.ironsource.appcloud.oobe.hutchison, com.aura.oobe.vodafone, com.aura.oobe.motorola, de.telekom.tsc, com.indus.appstore, com.glance.lockscreenM
• com.android.dreams.basic, com.android.bookmarkprovider, com.google.android.apps.work.clouddpc
• Note: I also disabled com.amazon.appmanager and com.motorola.installer by using appops set RUN_IN_BACKGROUND ignore / WAKE_LOCK ignore (and INSTALL_PACKAGES deny for the installer).

(Important core apps like com.google.android.verifier, com.motorola.omadm.service, com.motorola.entitlement were left intact).

Batch 2 (Phone crashed after restarting)

This is the list of packages I removed right before the crash. I grouped them to make it easier to read:

• Bloat/Ads: com.inmobi.installer, com.taboola.mip, com.motorola.playautoinstallext
• Motorola Services: com.motorola.bug2go, com.motorola.lifetimedata, com.motorola.paks, com.motorola.nfwlocationattribution, com.motorola.spectrum.setup.extensions, com.motorola.contacts.preloadcontacts, com.motorola.mobiledesktop.core, com.motorola.easyprefix, com.motorola.motosignature.app, com.motorola.motosignature2.app, com.motorola.attvowifi, com.motorola.hiddenmenuapp, com.motorola.sstservice, com.motorola.securevault, com.motorola.ccc.devicemanagement, com.motorola.ccc.ota, com.motorola.paks.notification, com.motorola.omadm.vzw, com.motorola.vzw.pco.extensions.pcoreceiver
• System/Google: com.google.ar.core, com.android.bips, com.android.printspooler,
• com.google.android.printservice.recommendation, com.android.providers.partnerbookmarks, com.google.ambient.streaming, com.motorola.wifi.motowifimetrics, com.motorola.android.nativedropboxagent, com.motorola.android.providers.chromehomepage, com.google.android.apps.carrier.carrierwifi, com.google.mainline.telemetry, com.android.devicediagnostics, com.google.android.uwb.resources, com.android.traceur, com.google.android.onetimeinitializer, com.android.htmlviewer, com.google.android.apps.turbo, com.google.android.apps.setupwizard.searchselector
• Qualcomm: com.qualcomm.qti.uimGbaApp, com.qualcomm.qti.uceShimService, com.qualcomm.atfwd2
• UI & System Overlays (Probably the cause): com.motorola.android.launcher.overlay.telus, com.motorola.android.launcher.overlay.vivo, com.motorola.android.launcher.overlay.koodo, com.motorola.android.systemui.overlay.sprint, com.motorola.android.systemui.overlay.att, com.motorola.android.systemui.overlay.tmo, com.motorola.android.systemui.overlay.usc, com.motorola.android.systemui.overlay.vzw, com.motorola.systemui.overlay.jp, com.motorola.systemui.overlay.dcm, com.motorola.launcherconfig.overlay.altice, com.motorola.launcherconfig.overlay.retin, com.oem.euiccpartnerapp.overlay.tmo, com.oem.euiccpartnerapp.overlay.att, com.oem.euiccpartnerapp.overlay.vzw, com.oem.euiccpartnerapp.overlay.cc, com.oem.euiccpartnerapp.overlay.br, com.oem.euiccpartnerapp.overlay.retca, com.oem.euiccpartnerapp.overlay.na, com.motorola.contacts.preloadcontacts.overlay.vzw, com.motorola.android.launcher.overlay.retail.global, com.motorola.android.server.telecom.overlay.jp, com.motorola.android.networkstack.overlay.mcc460, com.motorola.setup.overlay.pai, com.android.internal.display.cutout.emulation.double, com.android.internal.display.cutout.emulation.hole, com.android.internal.display.cutout.emulation.tall, com.android.internal.display.cutout.emulation.waterfall.

I highly suspect the crash was triggered by either messing with the UI Overlays / display cutouts, or one of these specific packages:

• com.motorola.securevault (sounds critical)
• com.motorola.sstservice
• com.motorola.paks
• com.google.android.apps.setupwizard.searchselector
• com.google.android.apps.turbo (not sure if I uninstalled this one, I think not)

Current Bootloop Behavior

When I let the phone boot, I noticed a very specific behavior that might help diagnose the issue:

• My custom display settings are actually loading (the screen colors visibly shift from the default "Dynamic" to my custom "Natural" setting).
• After that, it shows the first "Android" screen, then the "ThinkShield" logo.
• From there, it just infinitely cycles back and forth between these two logos. The phone does not physically reboot or lose power; it's just the boot animation looping endlessly, suggesting that the core OS boots but the UI/Launcher is crashing.

Questions

1. Can anyone pinpoint exactly which package(s) from Batch 2 caused the soft-brick?
2. Since USB Debugging was already enabled, is there any way to bypass the authorization or connect via ADB while it's in this animation loop (or from Recovery) to run cmd package install-existing <package_name>? Note: When connected during this loop, the PC recognizes it, but ADB lists the device as "unauthorized" (and I obviously can't tap "Allow" on the screen).
3. If a wipe/reflash is inevitable, what is the best/safest tool? Should I just use Motorola's official Rescue and Smart Assistant (RSA) tool? (I really don't want to do this...)

Forgot to mention: the phone that I have is an Motorola Edge 50 Fusion

IMPORTANT NOTE: My absolute main priority is keeping/recovering my data (photos, videos, etc.). I want to avoid a Factory Reset at all costs unless there is absolutely no other way!

Hi everyone, I was trying to debloat my Motorola phone using ADB commands (adb shell pm uninstall --user 0 [PACKAGE_NAME]). I did this in two separate batches to be safe. After the first batch, I restarted the phone and everything worked perfectly. However, after the second batch and another restart, the phone completely crashed/soft-bricked (stuck in a bootloop/won't boot up).

Since professional repair is quite expensive in my area, I want to try and fix this myself via software. Here is the exact breakdown of what I did:

Batch 1 (Safe - Phone restarted and worked fine)

These are the apps I uninstalled/disabled without any issues:

• com.google.android.adservices.api, com.google.android.marvin.talkback, com.google.android.projection.gearhead
• com.motorola.mykey, com.motorola.att.phone.extensions, com.motorola.enterprice.adapter.service, com.motorola.bach.modemstats, com.motorola.account, com.motorola.help.extlog, com.motorola.iotservice, com.motorola.mobiledesktop.core, com.motorola.smartfeed, com.dti.motorola
• com.ironsource.appcloud.oobe.hutchison, com.aura.oobe.vodafone, com.aura.oobe.motorola, de.telekom.tsc, com.indus.appstore, com.glance.lockscreenM
• com.android.dreams.basic, com.android.bookmarkprovider, com.google.android.apps.work.clouddpc
• Note: I also disabled com.amazon.appmanager and com.motorola.installer by using appops set RUN_IN_BACKGROUND ignore / WAKE_LOCK ignore (and INSTALL_PACKAGES deny for the installer).

(Important core apps like com.google.android.verifier, com.motorola.omadm.service, com.motorola.entitlement were left intact).

Batch 2 (Phone crashed after restarting)

This is the list of packages I removed right before the crash. I grouped them to make it easier to read:

• Bloat/Ads: com.inmobi.installer, com.taboola.mip, com.motorola.playautoinstallext
• Motorola Services: com.motorola.bug2go, com.motorola.lifetimedata, com.motorola.paks, com.motorola.nfwlocationattribution, com.motorola.spectrum.setup.extensions, com.motorola.contacts.preloadcontacts, com.motorola.mobiledesktop.core, com.motorola.easyprefix, com.motorola.motosignature.app, com.motorola.motosignature2.app, com.motorola.attvowifi, com.motorola.hiddenmenuapp, com.motorola.sstservice, com.motorola.securevault, com.motorola.ccc.devicemanagement, com.motorola.ccc.ota, com.motorola.paks.notification, com.motorola.omadm.vzw, com.motorola.vzw.pco.extensions.pcoreceiver
• System/Google: com.google.ar.core, com.android.bips, com.android.printspooler,
• com.google.android.printservice.recommendation, com.android.providers.partnerbookmarks, com.google.ambient.streaming, com.motorola.wifi.motowifimetrics, com.motorola.android.nativedropboxagent, com.motorola.android.providers.chromehomepage, com.google.android.apps.carrier.carrierwifi, com.google.mainline.telemetry, com.android.devicediagnostics, com.google.android.uwb.resources, com.android.traceur, com.google.android.onetimeinitializer, com.android.htmlviewer, com.google.android.apps.turbo, com.google.android.apps.setupwizard.searchselector
• Qualcomm: com.qualcomm.qti.uimGbaApp, com.qualcomm.qti.uceShimService, com.qualcomm.atfwd2
• UI & System Overlays (Probably the cause): com.motorola.android.launcher.overlay.telus, com.motorola.android.launcher.overlay.vivo, com.motorola.android.launcher.overlay.koodo, com.motorola.android.systemui.overlay.sprint, com.motorola.android.systemui.overlay.att, com.motorola.android.systemui.overlay.tmo, com.motorola.android.systemui.overlay.usc, com.motorola.android.systemui.overlay.vzw, com.motorola.systemui.overlay.jp, com.motorola.systemui.overlay.dcm, com.motorola.launcherconfig.overlay.altice, com.motorola.launcherconfig.overlay.retin, com.oem.euiccpartnerapp.overlay.tmo, com.oem.euiccpartnerapp.overlay.att, com.oem.euiccpartnerapp.overlay.vzw, com.oem.euiccpartnerapp.overlay.cc, com.oem.euiccpartnerapp.overlay.br, com.oem.euiccpartnerapp.overlay.retca, com.oem.euiccpartnerapp.overlay.na, com.motorola.contacts.preloadcontacts.overlay.vzw, com.motorola.android.launcher.overlay.retail.global, com.motorola.android.server.telecom.overlay.jp, com.motorola.android.networkstack.overlay.mcc460, com.motorola.setup.overlay.pai, com.android.internal.display.cutout.emulation.double, com.android.internal.display.cutout.emulation.hole, com.android.internal.display.cutout.emulation.tall, com.android.internal.display.cutout.emulation.waterfall.

I highly suspect the crash was triggered by either messing with the UI Overlays / display cutouts, or one of these specific packages:

• com.motorola.securevault (sounds critical)
• com.motorola.sstservice
• com.motorola.paks
• com.google.android.apps.setupwizard.searchselector
• com.google.android.apps.turbo (not sure if I uninstalled this one, I think not)

Current Bootloop Behavior

When I let the phone boot, I noticed a very specific behavior that might help diagnose the issue:

• My custom display settings are actually loading (the screen colors visibly shift from the default "Dynamic" to my custom "Natural" setting).
• After that, it shows the first "Android" screen, then the "ThinkShield" logo.
• From there, it just infinitely cycles back and forth between these two logos. The phone does not physically reboot or lose power; it's just the boot animation looping endlessly, suggesting that the core OS boots but the UI/Launcher is crashing.

Questions

1. Can anyone pinpoint exactly which package(s) from Batch 2 caused the soft-brick?
2. Since USB Debugging was already enabled, is there any way to bypass the authorization or connect via ADB while it's in this animation loop (or from Recovery) to run cmd package install-existing <package_name>? Note: When connected during this loop, the PC recognizes it, but ADB lists the device as "unauthorized" (and I obviously can't tap "Allow" on the screen).
3. If a wipe/reflash is inevitable, what is the best/safest tool? Should I just use Motorola's official Rescue and Smart Assistant (RSA) tool? (I really don't want to do this...)

Forgot to mention: the phone that I have is an Motorola Edge 50 Fusion

IMPORTANT NOTE: My absolute main priority is keeping/recovering my data (photos, videos, etc.). I want to avoid a Factory Reset at all costs unless there is absolutely no other way!

Hi everyone, I was trying to debloat my Motorola phone using ADB commands (adb shell pm uninstall --user 0 [PACKAGE_NAME]). I did this in two separate batches to be safe. After the first batch, I restarted the phone and everything worked perfectly. However, after the second batch and another restart, the phone completely crashed/soft-bricked (stuck in a bootloop/won't boot up).

Since professional repair is quite expensive in my area, I want to try and fix this myself via software. Here is the exact breakdown of what I did:

Batch 1 (Safe - Phone restarted and worked fine)

These are the apps I uninstalled/disabled without any issues:

• com.google.android.adservices.api, com.google.android.marvin.talkback, com.google.android.projection.gearhead
• com.motorola.mykey, com.motorola.att.phone.extensions, com.motorola.enterprice.adapter.service, com.motorola.bach.modemstats, com.motorola.account, com.motorola.help.extlog, com.motorola.iotservice, com.motorola.mobiledesktop.core, com.motorola.smartfeed, com.dti.motorola
• com.ironsource.appcloud.oobe.hutchison, com.aura.oobe.vodafone, com.aura.oobe.motorola, de.telekom.tsc, com.indus.appstore, com.glance.lockscreenM
• com.android.dreams.basic, com.android.bookmarkprovider, com.google.android.apps.work.clouddpc
• Note: I also disabled com.amazon.appmanager and com.motorola.installer by using appops set RUN_IN_BACKGROUND ignore / WAKE_LOCK ignore (and INSTALL_PACKAGES deny for the installer).

(Important core apps like com.google.android.verifier, com.motorola.omadm.service, com.motorola.entitlement were left intact).

Batch 2 (Phone crashed after restarting)

This is the list of packages I removed right before the crash. I grouped them to make it easier to read:

• Bloat/Ads: com.inmobi.installer, com.taboola.mip, com.motorola.playautoinstallext
• Motorola Services: com.motorola.bug2go, com.motorola.lifetimedata, com.motorola.paks, com.motorola.nfwlocationattribution, com.motorola.spectrum.setup.extensions, com.motorola.contacts.preloadcontacts, com.motorola.mobiledesktop.core, com.motorola.easyprefix, com.motorola.motosignature.app, com.motorola.motosignature2.app, com.motorola.attvowifi, com.motorola.hiddenmenuapp, com.motorola.sstservice, com.motorola.securevault, com.motorola.ccc.devicemanagement, com.motorola.ccc.ota, com.motorola.paks.notification, com.motorola.omadm.vzw, com.motorola.vzw.pco.extensions.pcoreceiver
• System/Google: com.google.ar.core, com.android.bips, com.android.printspooler,
• com.google.android.printservice.recommendation, com.android.providers.partnerbookmarks, com.google.ambient.streaming, com.motorola.wifi.motowifimetrics, com.motorola.android.nativedropboxagent, com.motorola.android.providers.chromehomepage, com.google.android.apps.carrier.carrierwifi, com.google.mainline.telemetry, com.android.devicediagnostics, com.google.android.uwb.resources, com.android.traceur, com.google.android.onetimeinitializer, com.android.htmlviewer, com.google.android.apps.turbo, com.google.android.apps.setupwizard.searchselector
• Qualcomm: com.qualcomm.qti.uimGbaApp, com.qualcomm.qti.uceShimService, com.qualcomm.atfwd2
• UI & System Overlays (Probably the cause): com.motorola.android.launcher.overlay.telus, com.motorola.android.launcher.overlay.vivo, com.motorola.android.launcher.overlay.koodo, com.motorola.android.systemui.overlay.sprint, com.motorola.android.systemui.overlay.att, com.motorola.android.systemui.overlay.tmo, com.motorola.android.systemui.overlay.usc, com.motorola.android.systemui.overlay.vzw, com.motorola.systemui.overlay.jp, com.motorola.systemui.overlay.dcm, com.motorola.launcherconfig.overlay.altice, com.motorola.launcherconfig.overlay.retin, com.oem.euiccpartnerapp.overlay.tmo, com.oem.euiccpartnerapp.overlay.att, com.oem.euiccpartnerapp.overlay.vzw, com.oem.euiccpartnerapp.overlay.cc, com.oem.euiccpartnerapp.overlay.br, com.oem.euiccpartnerapp.overlay.retca, com.oem.euiccpartnerapp.overlay.na, com.motorola.contacts.preloadcontacts.overlay.vzw, com.motorola.android.launcher.overlay.retail.global, com.motorola.android.server.telecom.overlay.jp, com.motorola.android.networkstack.overlay.mcc460, com.motorola.setup.overlay.pai, com.android.internal.display.cutout.emulation.double, com.android.internal.display.cutout.emulation.hole, com.android.internal.display.cutout.emulation.tall, com.android.internal.display.cutout.emulation.waterfall.

I highly suspect the crash was triggered by either messing with the UI Overlays / display cutouts, or one of these specific packages:

• com.motorola.securevault (sounds critical)
• com.motorola.sstservice
• com.motorola.paks
• com.google.android.apps.setupwizard.searchselector
• com.google.android.apps.turbo (not sure if I uninstalled this one, I think not)

Current Bootloop Behavior

When I let the phone boot, I noticed a very specific behavior that might help diagnose the issue:

• My custom display settings are actually loading (the screen colors visibly shift from the default "Dynamic" to my custom "Natural" setting).
• After that, it shows the first "Android" screen, then the "ThinkShield" logo.
• From there, it just infinitely cycles back and forth between these two logos. The phone does not physically reboot or lose power; it's just the boot animation looping endlessly, suggesting that the core OS boots but the UI/Launcher is crashing.

Questions

1. Can anyone pinpoint exactly which package(s) from Batch 2 caused the soft-brick?
2. Since USB Debugging was already enabled, is there any way to bypass the authorization or connect via ADB while it's in this animation loop (or from Recovery) to run cmd package install-existing <package_name>? Note: When connected during this loop, the PC recognizes it, but ADB lists the device as "unauthorized" (and I obviously can't tap "Allow" on the screen).
3. If a wipe/reflash is inevitable, what is the best/safest tool? Should I just use Motorola's official Rescue and Smart Assistant (RSA) tool? (I really don't want to do this...)

Forgot to mention: the phone that I have is an Motorola Edge 50 Fusion

https://preview.redd.it/73u61z4q6zyg1.png?width=506&format=png&auto=webp&s=fd13d40ab74d4c536bfb6dd384efb7d1b3b1c777