Galaxy S22 Ultra Reboot Loop

[Members_LIeRlfS]

Dear all, 

Creating one more post on this widely known issue on the S22 Ultra. Samsung customer service managed to keep me waiting for over 2 months to finally decide they will not repair my phone.

It's pretty difficult to comprehend how a company like Samsung can that obviously destroy my property with the software update and seems to get away with just not saying anything. Even in dozens of back and forth emails with customer service, they managed not to say anything. Not that it was not Samsungs fault (which would be absurd) but neither one statement acknowledging what has happened. There are dozens of newspaper reports and dozens of forum entries here. 

I've been with Samsung for over 15 years, and they probably know I will not sue them over a 2 years old phone. But be ensured, I will stay miles away from any Samsung product in the future. 

[BandOfBrothers]

I totally understand and appreciate your and others viewpoints on this ongoing situation.

I have the Samsung Galaxy s²² Ultra which hasn't been affected by this issue , so can understand the frustration if it did. 

[keith30]

You must be one of the few who have issues.

[JAMES4578]

@Members_LIeRlfS Has the Device been inspected and has Samsung given you a reason why they cannot repair your phone?   Obviously at this stage your Device will out of warranty,  I do agree that Samsung need to addresss the Boot Loop issue on the S22 series though the problems will not always be due to software.

[Members_LIeRlfS]

Yes, they have concluded that the main board is defect. My understanding of the issue is that the update caused constant overheating of the device which damaged the main board. First, the reboots were fast and "just" once a day until the phone stopped working completely after a few weeks. But support apparently didn't connect the dots between software update and damaged main board. 

[Reylob]

I fail to see how the problem is not software. If it is the motherboard, then quite likely a faulty batch which in my opinion Samsung should address.

In all the reported cases, the phones were working and the issue happened after the update. I cannot see how many different users did something wrong to get that many phones in the same state.

It is an expensive repair, but these are premium products which should not have this sort of issue within two years of use.

It is also a matter of reputation. Flagship devices which breaks just after the two year warranty, due to update or subpar component and company does nothing about it is not a good story for any company.

[Tourbillon De La Vie]

I disagree it is some software update, supposedly, causing it. Poor quality hardware component(s), yes. Failing soon after warranty expired and bad for company reputation, yes

Unfortunately and in my opinion, lots of copycat posts attempting to create a "situation" 

[Reylob]

You might be right about the software. However, the software is a possible culprit. Why were the reboots not happening before the update? It could be a coincidence, but the software could have put the hardware in the state that becomes faulty.

I respect your opinion and again you might well be right about copycats. However, the situation is created by the problem not the users posting. I take the posts at face value. If I were in their situation, I would be as upset as they are. These are premium products and consumers expect premium quality.

In any case, if it was the update or faulty batch of motherboards, a good story will help sell more devices.

[Members_Gy1XHwS]

Is there any fix yet ? There alot of poeple affected due to this issue. And it is definitely due to the software update pushed by SAMSUNG. Its been almost a month now the phone is useless, cant even backup the data from it

[Mikehurst95]

Glad this is a widely known issue and not just me then. I'm an s22 and this issue plagues my phone with random boot loop bouts since the update, I've been told a factory reset should sort it but after reading here I don't think I'll bother! I also cannot switch on WiFi feature is this issue present for anyone else?