Odds of update breaking hardware Samsung S22

[Haszumarius]

There is now widespread awareness that the Samsung S22 S901B experiences a bootloop issue after installing update S901BXXUDEXK5. The key question is whether this software update could have caused hardware damage, potentially rendering the device non-functional even after a future ONE UI 7.0 update is released.

[smiley]

To be completely honest, I don't think anyone can really give you this advice one way or the other. Or to quantify the chances of this issue happening to you.

It has been read on this community and the other communities such as reddit about this issue that has occurred after updating to a later software and causing a reported bootloop issue.

What I would say is that forums will always paint a picture of pessimistic responses. Where one person comments on their issue, it is very easy for many others to say 'yes this happened to me as well.' Very rarely do people say 'no problems for me' and in fact many people only join communities to report their issues... not necessarily to say how great their phone is.

Millions of S22 phones have been sold, and a small minority have seen issues. It is a very small percentage in reality.

However by saying this I am not advising you one way or the other. Only you can choose.

There are many people and forum members that have installed the very same update, and not suffered the same problems.

Personally I like my phone up to date, and particularly to be secure. So therefore I always update to schedule. However I own an S23u and not an S22... so that is easily said.

If this was me, then personally with the OneUI7 software likely being released in the next couple of months, then I would consider waiting for oneUI7. I would probably also do a full backup, a full factory reset, and then install the new software. I wouldnt use smartswitch to synchronise apps.

In my mind this would represent the least risk of all... especially if it is something like a rogue application that is causing the reported issues that are known to bootloop.

Good luck with whatever you decide.

Smiley

[Members_2eKoj97]

Your response reflects relativism about the problem, coming from a fanboy who has no skin in the game. Just don’t say anything if you’ve already decided what you’ll say, no matter the problems others face.

Millions of phones were affected, but many are already out of service, some were replaced in one way or another, and very few people have taken it this far to share their issues. Yet you dare to discourage even those who do. So don’t bring up numbers.

One thing is certain: it was a software update from Samsung that ruined perfectly fine phones overnight and bricked them!

This is unacceptable, no matter what!

[smiley]

Thankyou for your insightful response. I think we have clashed before on this forum.

I give up my own free time on this community to help others... I neither get paid for this and nor do I expect anything.

As I have a like for Samsung devices, I guess you can call me a fanboy. I haven't suffered any issues like you have with any devices, and I find the hardware and Samsung experience just about as good as any phone on the market.

I truly am sorry for your experience. If I had this issue happen to me then perhaps I might have had a different perspective. Perhaps also if you had not had this experience happen to you, then you may also have had a very different perspective of Samsung and with less aggression too.

I am not a magician, but I try and provide helpful information to the best of my knowledge. I am sorry if you do not like what I have to say in my advice and in which case I would suggest you just ignore any other advice that I choose to offer... during my own time... during my evenings... for free to people that ask for help.

Once again, I am sorry you have had a bad experience with your own Samsung device. I am certainly not shutting down your issue, but rather saying that this is a less common occurrence. Your quote of 'millions of phones affected' i do not believe is accurate, and I have seen no facts on the Android publications or forums that would signify these kind of numbers. I do however recognise that some people have suffered this issue. If you really do believe you have a firm case then why not seek legal advice ?

Perhaps rather than jumping on someone else's post that is genuinely asking for advice from the forum, you should create your own.

Smiley.

[Tourbillon De La Vie]

Widespread luckily only in this forum. Not to detract from the fact that bunch of units failed due to hardware malfunction which in turn coincided with some update. Unfortunately it seems most of the those were out of the warranty. Here in UK that warranty lasts for 2 years but that's not so in the other parts of the world 

[aswin suresh]

My s22 plus dead after the update. Visiting the service center was of no use. They told the motherboard was faulty and asked me to pay to repair the faulty mobo.

[BandOfBrothers]

Hello 👋 @Haszumarius and may I extend a Warm Welcome to the Samsung Community Forum.

I'm disheartened to hear about your issue and indeed other people's issues that do appear to have arisen from a software update. 

What is would say is the more people that also send this as feedback the better which goes directly to Samsung for assessment.

@aswin suresh if this was my predicament I would ask for Samsung Customer Services to reassess the situation to bring this to a mutual resolvement.

I'm a customer like you and in no shape or from a phone engineer, or software programmer so am unable to make comment if software has caused this.

In the Uk we have the Consumer-Rights-Act-2015  which is in place to support both the consumer and merchant. 

If i can be of any further help please don't hesitate to ask  😎 

[Haszumarius]

I have found a temporary solution, at least until ONE UI 7.0.

Here is what I did:

When the phone is charged and experiencing a bootloop, place it in a cold environment - in my case, this was the freezer. After approximately 20 minutes, the phone should boot into the system. Disable WiFi, enable power saving mode, and limit CPU power. (I also restricted background applications in developer options.) If successful, power off the phone, connect a USB cable between the computer and phone, then enter recovery mode (Press power button and volume up) and clear the cache partition.

If the phone continues to bootloop, press and hold the power and volume down buttons until the Samsung logo appears.

From this point, the phone operates stably, though network access is only possible through mobile data. Enabling WiFi will cause the phone to reboot.

I will inform you if I find any other solutions.

[Schillerr]

This is not an option. When using it, it will hang at the most inopportune moment. I'm tired of worrying that you'll press a button and it will break. I've been using a Motorola smartphone for $200 for a few days. I'm impressed.

I don't plan to buy Samsung anymore for $1,000. I think many people will do the same.

[Schillerr]

You write that your phone is not broken yet. If you're lucky, that's good. I've never had a broken smartphone in my life.and even more so. Unexpected and just terrible. And now I got this. Brick.

And imagine if you were also caught up in this story. Would you continue to fan and enjoy?