Galaxy S10 and Note 10 were unusable after the latest Samsung app update

Samsung stands out among all Android manufacturers for its excellent software support. Although the company has a strong QA and testing team, every now and then there are bugs in an update, leading to unintended problems. Recently, Samsung pulled the Galaxy S23 Ultra's One UI 6.1.1 firmware after complaints about a bug that caused ghosting in images when zoomed in. Things are even worse for some older Galaxy owners as the latest Samsung SmartThings app causes their phone to get stuck in a bootloop.

Several Galaxy S10, Note 10, Galaxy A90 and M51 users have complained on Reddit (2) about their devices getting stuck in a bootloop (via Droid Life). The issue appears to occur when installing the latest SmartThings Framework build (v2.2.02.11) released on the Galaxy Store on October 2nd.

Currently, Samsung's entire Galaxy S10 and Note 10 lineup appears to be affected, with the exception of the Lite models. The issue is also not limited to a specific region, as users from the US, Korea, Europe and parts of Asia are affected.

If your old Galaxy phone is already stuck in a bootloop, your only option is to restore it to factory settings. However, this will delete all data stored on it. You may not like this solution, but currently there doesn't seem to be any other solution to get your old Galaxy back to working condition.

Now disable auto-update on your old Galaxy phone

If your phone still works, you should go to the Galaxy Store Settings and turn that off Automatically update apps Option. This ensures that no attempt is made to automatically update the Samsung SmartThings Framework in the background. Even if you are using another old Galaxy device, you should disable auto-update for now to ensure you don't encounter a similar bootloop issue.

Even if Samsung releases a fix, it can't seem to solve the problem on devices that are already in a bootloop. However, if you don't mind having a non-working phone and important data, you can wait for an official solution from Samsung. Many affected users contacted Samsung support for help, but were instead redirected to the nearest service center.