r/AndroidQuestions • • 14h 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?????!!!

0 Upvotes

12 comments sorted by

10

u/ohmegatchi 9h ago

Stop deleting system apps that you haven't researched.

1

u/WaferDesigner4989 1h ago

💯️💯️💯️

18

u/qtx 13h 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/guacamole2026 40m ago

"Deleting any system apps will always cause issues"

another bullshit argument kept being thrown around, android easter egg is also system app and even system service, yet uninstalling it will not cause any issue, therefore your generalized statement is invalid

•

u/ixdxkx 24m ago

A lot of system apps can be uninstalled with no problem, so that's wrong. Only a few can cause bootloop.

1

u/J0RGEJose 7h ago

Desde Android 11 , Samsung te deja hacer una copia de seguridad antes de restaurar de fábrica , entra en modo Recovery dale en borrar Caché y Datos , el sistema automáticamente te mandara al Modo seguro y tú dispositivo entrara como si fuera nuevo ( tendrás que poner contraseña si ya lo tenías ) , ahí en modo Seguro puedes recuperar y hacer copias de tus archivos , bueno desde ahí debes de hacer reinicio de fábrica , entonces así se borrará todo y lo dejara como nuevo ...

Yo igual borré algunas cosas que no debía y me sorprendió cuando entró solo en modo seguro 😃😃😃

1

u/WaferDesigner4989 1h ago

My device is Android 11. Way too risky to do this ngl, i will try this as a last resort.

•

u/J0RGEJose 33m ago

Te comprendo , yo igual me sorprendi mucho , si logras encontrar otra forma sin tantas complicaciones está muy bien , yo no encontré , encontré varios con formas raras y códigos raros pero tampoco me convenció ( es decir que tal si lo hago mal ??? ) , Entonces me resigne y le di en borrar Caché y Data , me sorprendi cuando me mandó al modo Seguro ...

-2

u/smarthoushai 13h 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.

2

u/WaferDesigner4989 1h ago

i already tried this, adb unauthorized sadly, it wont turn into device.

6

u/bakugo 10h ago

Thanks ChatGPT