S22 Ultra Boot Loop Issues after 6.1 UI / Firmware update.

[FixMyS22Ultra]

Hi everyone,

I’m posting because the boot loop issue after the One UI 6.1 update is clearly widespread, and I want to gauge just how big this problem really is.

Is anyone else dealing with a bricked Galaxy S22 or a constant boot loop since the update? I keep seeing new posts about it almost every day.

My phone was working perfectly fine before the update. After installing it, it suddenly stopped working. Now, it’s stuck in a boot loop, and on the rare occasion it gets to the home screen, it crashes and starts looping again.

I’ve tried everything Samsung suggested: clearing the cache, factory resets—you name it. Nothing worked. I even had a Samsung repair tech come to my house. They suggested my motherboard needs to be replaced but refused to fix it under warranty because of a small, superficial crack on my screen (which can barely even be picked up by a camera).

This hairline crack has been there for over a year. It has nothing to do with the motherboard issue, and my touchscreen is working perfectly fine.

What’s even more frustrating is seeing countless others on Reddit, Samsung forums, Twitter, and beyond reporting the same problem—yet Samsung keeps denying responsibility and is shifting the blame onto the consumer.

If Samsung wants to argue that my phone’s reboot loop is caused by a tiny screen crack, then what about everyone else? What about all the other phones with the exact same issue across the globe with 0 screen and cosmetic damage - and the numerous motherboards they’ve already replaced? 

The pattern is obvious: this update has caused widespread failures and they are now charging for repairs wherever possible. I even have logs showing the update in question followed by recovery reboots immediately afterward.

It’s outrageous that a £1300 phone has failed in 23 months, and Samsung’s response is a £500+ repair quote for a phone which is laughably now only worth ~£400 brand-new. 

That said, I’d really like to hear from others, especially those in the UK but also worldwide, about how you’re handling this situation.

If your phone is out of warranty, you’ve been denied a warranty claim, or you’re experiencing this issue, please share your story. Adding your voice helps build a stronger case and puts more pressure on Samsung to finally take responsibility for this widespread problem.

P.S. If you’re experiencing this issue, and have read this far down - clicking “I have this problem too” under the title of this post may help raise awareness

[Members_lRO61oL]

I have exactly the same issue endless boot loops since the update and it gets worse when the wifi is on. it works sometimes for a weeks and suddenly it keeps rebooting. extremely frustrating! 

[Berenice14]

Of course, that's what I did!

[Shlink]

I'm having the same problems a few days after updating the os my s22 ultra froze, rebooted and made it to  optimising apps screen then stopped and entered a continuous loop of rebooting it made it to a safe start briefly once then straight back to  bootloop and eventually to a blue screen with a "hyp" and " vemeta" codes wish I'd read up on the update beforehand. 

Went to a samsung service just to be bushed off and told it's the motherboard and would cost around aud$500 to swap it with no diagnostics even being run

[st8angel]

Yep!  Same here!!!

[bsadams]

Having the same issue here in the US.  Been going on now for about 3 weeks.  Stuck in boot loop, opens up to the Samsung screen, then Android powered by Knox then starts over.  Very frustrating as I am unable to use my phone at all.  Already wiped the cache, and did a factory reset.  Now nothing is able to be done to it, phone is useless.  Samsung come on you can do better than this.  Flagship phone and only 3 years of use, really sad.  Apple phones last much longer.  

[Members_hG0fhIu]

I LITERALLY had the exact same situation as you, on the exact time, with a similar hairline crack. My repair company quotes €715 to replace motherboard. 

Today I dragged my s22U out the drawer to check it again. I reboot without WiFi on and it works fine, however as soon as I switch WiFi on its back into the boot loop again. 

I want a replacement, when I went to get it fixed it was still in warranty, but as I had my hairline crack they refused to pay for it. 

[bernard_bonello]

Happened exactly same to me, was using the phone, it switched off and now:

- Won't charge (with PC or charger)

- won't boot with just power on button

- Will boot with power and volume down, but till second screen and never actually boots up

- Will not boot in safe mode

Had S4, S6, S7 Edge, Note 9, S10+, S22 Ultra. Time to change from Samsung?

TIA, 

Bernard

[Members_dZy853q]

I have this problem too.Firstly My S22 Ultra, 8/12GBRAM/512GB ROM has no cosmetic or other damage but after the UI 6.1update I regularly find that access to my app folders and storage via touch screen is frozen out and the only solution is to carry out a soft restart/ reboot of my device. After which functionality returns for a while but then after a few hours once again the lock out returns and I need to re start to overcome. This is highly frustrating on a device running Android 14.0 UI 6.1, which is the same software found in the S24 and S25 devices. Is this the same issue being discussed in this thread. I've not experienced (touch wood) the reboot loop I've seen discussed.

[Members_IGD7aMQ]

i I have the same issue suffering since last three weeks, now its more terrible cant even use my phone because its keep rebooting its self and all app are crushing it self.

[Punnyabrata]

My phone updated its software last week, and ever since, it's been plagued with performance issues. It crashed and restarted a few times before ending up in a bootloop yesterday. Before the update, everything was working perfectly. I attempted to access Safe Mode but had no success. I also reached out to Samsung chat support, but the representative was unhelpful and simply advised me to visit a service center. Unfortunately, the service center was equally unhelpful. I even let the battery drain completely, but now the phone vibrates repeatedly whenever I try to charge it.

Has anyone had any success booting into the OS without losing their data? Beyond the issue of planned obsolescence, I think Samsung needs to be held accountable for taking their customers' loyalty for granted. If car manufacturers can issue recalls, why not phone companies? I currently own four Samsung phones and a Samsung TV, but their customer support is worse than Google’s. I'm in Canada and if anyone is pursuing a class-action lawsuit, count me in.