Question How do you run an ADB command on a bootlooping device?

[ZenDeveloper]

I have uninstalled a system app that I shouldn't have (something to do with network conectivity according to the recovery log) and everything was fine until I updated my device. I hadn't restarted it since removing the system app but after tyhe update it will no longer go past the Samsung galaxy logo. I remember doing something similar to either this device or another and I remember that I was abler to get into the system enough to be able to reinstall the neccessary app and fix the problem. However, this time I cannot get into adb at all. adb won't show any devices when in recovery, download mode, or at any of the three stages of the boot screen. I have tried wiping the cache and everything but factory resetting it as I have data that I can't lose. Any help would be appreciated whether getting adb install-existing to work or to pull important files off of the device before a reset. The device runs android 12 not rooted.

 

[ze7zez]

(...)
Go back via odin to the original firmware including the correct BIT.
(...)

 

[GeeAyeZee]

Flash in Odin using home CSC file, simple

 

[Misterjunky]

You only need to run ADB in Windows PC terminal or DOS mode in order to Odin flash firmware. No need to run ADB commands in the phone.
Just be sure that you install the "Samsung ADB Driver" into your PC before
you try Odin flashing firmware.

Just be sure you download the proper firmware for your phone.

Good luck, have a great day and have fun!

 

[ZenDeveloper]

Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode. From here, the phone goes through the initial setup screens but all data is still intact, just not apps. Concerningly, it doesn't ask for you to enter your password, it just puts you on the homescreen, which seems bad from a privacy perspective as any samsung repair tech can easily cause the phone to boot loop. From here, you can back up anything important and factory reset. There is no way to exit safe mode once you've gotten this far.

I don't remember why odin didn't work, it may have been that I couldn't get the firmware to download as Samsung likes to change that stuff all the time or it may not have reinstalled the system app neccessary.

I should've been more clear in the original post but I have not flashed any unofficial firmware just the U1 firmware to remove carrier bloat, but that was way before this occurred. In case it wasn't clear, the problem happened because through

adb shell uninstall --user 0 package.name

an important system app was removed (something network related) which caused android to crash when trying to start the service. In short: be careful what you remove when using adb and, for all you forum members: read the whole post instead of jumping to conclusions about the user's mistake and if it isn't clear, ask for more details. Again, thank you to all the helpful comments even if they didn't end up working.

 

[hatoxda]

Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode.

May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.

Thanks

 

[ZenDeveloper]

May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.

Thanks

Sorry for the late reply,
I don't know how many times it needs to reboot to go into safe mode but it seemed like quite a bit maybe 20-30 times possibly like 100. But once it does it'll go through the initial setup screens and let you in without a password. It's very important to backup everything on your device before you mess with any system apps or update especially if you've previously messed with system apps. I however don't use google hence I didn't have a backup of anything and needed to get it off before hand.
It could also be possible that Samsung removed this back door in android 13 and just the act of trying to update it gets rid of it. I don't know I'm just throwing around ideas.

 

[blackhawk]

Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be! Firmware upgrades/updates can and do break Samsung's.