6.1 has bricked my S21 5G

[SassanEC]

The update before (16/08) and now 6.1 have completely bricked my S21. Since installing pre6.1 it was bad and since 6.1, maybe 10 minutes pass between each restart. I've reported the error every time on the app and no resolution has come back to me. My phone is literally usuable and Samsung refuse to fix it. I've had a support rep tell me that Samsung is not responsible for what happens to Samsung phones when they force an update. They then won't help diagnose the problem. Terrible customer service and software. If you haven't installed 6.1, don't, it will ruin your phone! 

[Piper123]

Hey there

Sorry to hear of your troubles here.

When was the last time (if ever) that you performed a Wipe Partition Cache on your device?

It is the first step to understanding the issue.

If this doesn't work, you'll need to go into safe mode to identify which app or apps are conflicting with your device and remove them.

[Piper123]

1. Turn off the device.
2. Connect To Computer USBC to USBC (you may also connect to another Samsung mobile via USBC). Press and hold the Volume Up key and then press and hold the Power key
3. When the Android logo displays, release both keys.
4. Wait until the Android system recovery menu options appear.
5. Press the Volume down key several times to highlight wipe cache partition.
6. Press Power key to select.
7. Press the Volume down key to highlight yes, them and press the Power key to select.
8. When the wipe cache partition is complete, Reboot system now is highlighted.
9. Press the Power key to restart the device.

[SassanEC]

I've performed a partition wipe, factory reset all within the last 2 weeks to no success. Even trying with a completely wiped phone, with no apps installed, the phone was still having the restart issue. There isn't an app conflict it's something to do with the default software/OS.

[Piper123]

Ok. Sorry to hear this.

Your post didn't mention any of this hence the suggestion to try to help you through the issue.

If a factory data reset hasn't fixed it then in my view as Samsung rolled out the update, Samsung are responsible to fix it (regardless of what Customer Service who have no idea of UK laws say).

[SassanEC]

Sorry Im just a bit fed up and rushed my post a bit without adding in all my attempts at a solution. When I last spoke to consumer service I said something similar and they just said they're not going to do anything and ended the chat with me. Despite me saying the error still occurs with a completely blank phone with no apps. They said it's not their responsibility to fix any issues caused by their software rollout.

[Piper123]

If they won't help (which is typical for Samsung Customer Service sadly) then you may have to take legal action through the Small Claims Court for the value of your device.

Not ideal but if they won't help......

I've been there work a company who wouldn't help. They were quick to respond when the legal documents arrived from the Courts. 👌

[Piper123]

And no apology needed 👌🤗👌

[BrickedS21Ultra]

I have the same issue (and ironically couldn't logon here with my main account because 2FA required a working phone... So I've logged on with an account I once used to sign in to my TV with.

Now, I've never had to tech-fix my phone before, so all this stuff about wiping partition cache and factory resetting is all new to me, so... How can I make brokeybroke phone go work-work again?

(context - this morning I saw there was an update available. It weirdly took over an hour to download despite only being 488mb so I forgot about it, then when I next needed to use my phone (quite urgently) I had found it was bricked. Half an hour later it managed to switch on again, but later on when bricky once more. Now it's not even switching on. Last time I managed it, it did the "OneUI 0-100%" screen. It reached 100% then bricked once more. Hasn't been on since. Have plugged it into laptop with USBC, tried the power keys/volume up-down combos... nothing)

[DottyD]

Mine has restarted for the past 2 years each update. Customer service extremely poor!