Samsung is well-known for its commitment to pushing regular updates even to devices that are 4 or 5 years old. In fact, for the Galaxy S24 series, Z Fold 6, and Z Flip 6, the company has promised a record-breaking update policy of 7 major OS updates and 7 years of security patches.
However, despite their commitment to updates, a lot remains to be desired in terms of the stability of the updates. Users regularly report bugs and issues like camera and performance degradation on their older Samsung phones after updates.
Now, users of some older Galaxy flagships (via Reddit) are reporting boot looping issues on their phones, allegedly after an update to a system app.
The affected devices are said to be the following:
- Galaxy S10e
- Galaxy A10
- Galaxy S10 Plus
- Galaxy S10 5G
- Galaxy Note 10
- Galaxy Note 10 Plus
- Galaxy Note 10 Plus 5G
- Galaxy M51
- Galaxy A90
Hence, it seems that the entire Galaxy S10 and Note 10 series from 2019 are affected by this recent issue, which has been linked to an update to the SmartThings Framework app, which helps control a wide variety of IoT devices made by Samsung.
The issue is seemingly global, affecting a large number of countries, and the reports of this boot looping issue started pouring in barely 2 hours after the update was pushed on October 2nd, 2024.
If you own any Galaxy S10 series or Note 10 series and haven’t yet faced this issue, it would be wise to turn off auto updates on your phone, which can be performed as follows:
- Open your phone’s settings app
- Scroll down and open the Apps menu
- Search for Galaxy Store and open its app settings
- Within the app settings for Galaxy Store, turn off auto-updates by setting the “Auto Update apps” option to “Never.”
I would suggest you back up your data from the device because boot looping issues are generally solved only via a proper factory reset, resulting in data loss.
Alternatively, you can try visiting a Samsung service center because they have the knowledge to repair the devices without any data loss.
Samsung has not acknowledged this issue so far, and the company seems to be silent. It could be that they simply do not care because the aforementioned devices are nearly at EOL, but we hope that changes and the company issues a proper response soon enough.
