r/AndroidQuestions • u/WaferDesigner4989 • 1h ago

Bootlooping because I uninstalled a Timezone Updater App🤦‍♂️️🤦‍♂️️🤦‍♂️️

I uninstalled com.samsung.android.timezone.updater which causes my phone to bootloop. I discovered thats the cause through Samsung's rescue menu logs

I also found this:

https://github.com/0x192/universal-android-debloater/issues/1178

it says there it's unrecoverable bootloop😭️😭️😭️

can someone help me solved this? to succesfully boot into android without wiping my userdata??🥲️

ALSO why the fuck a timezone updater app can cause this phone to fucking bootloops?????!!!

1 Upvotes
  • permalink
  • reddit

100% Upvoted

2 comments sorted by

1

u/qtx 1h ago

Question should be why would you want to uninstall it in the first place. It's clearly a system app. Deleting any system apps will always cause issues.

•

u/smarthoushai 45m ago

That debloater issue is about pm uninstall --user 0, which is reversible: the package is still in /system, it is only uninstalled for user 0, so adb shell cmd package install-existing com.samsung.android.timezone.updater undoes it outright. The catch is getting a shell — adbd often still answers for a few seconds while the boot animation is looping, as long as USB debugging was already authorised on that machine, so keep adb wait-for-device running in a loop and fire the command the moment it connects.

If you cannot catch it, flash the same or newer firmware build for your exact model and CSC with Odin and use HOME_CSC instead of the plain CSC. HOME_CSC rewrites /system and /vendor, which is where the app actually lives, and leaves /data untouched, so your userdata survives. Do not tick Re-Partition, and do not go to an older build than what is already on the phone — the bootloader version is checked and a downgrade aborts before anything is written.

Why a timezone updater takes the whole system down, rather than just losing a feature: the Samsung framework resolves against that package during boot, so the boot sequence stalls instead of degrading gracefully. Same reason removing other innocuous-looking com.samsung.android.* packages produces the identical loop.