Samsung Worst One UI beta

[uigoku]

I owned S22 Ultra which is currently being used by my wife and tested One UI 5 and 6 beta versions on it. Everything was so stable that I got belief that Samsung's One UI beta versions can be used as daily drivers.

This kind of software support from Saumsung made me buy A54 and later upgrade it to S24 Ultra. But this One UI 7 beta version has messed up my S24 Ultra.

After Beta 1 I stopped getting calls and make calls from one of my 2 eSIMs however I found a workaround to it. Turn off and turn back on eSIM after every reboot.

Now I am in a big trouble since Beta 2 roll out I am getting messages from Samsung Health, Pass, Secure folder and not sure what else "Unauthorised changes were made to your phone". My phone also keep getting reset as soon as battery done learning my usage pattern.

Need urgent belp.

[IndiaBetaTeam]

Dear Samsung Member,

Greetings from India Beta Team!

We acknowledge your feedback. However, we request you to please report this feedback on the Error section, along with the logs. This would help us analyze your issue in a better way.

The path to report error is as below: Open Samsung Members -> Click on beta banner -> Switch to beta mode-> Beta feedback -> Send feedback -> Error report.

Thank you for being our valued customer.

Warm Regards,
India Beta Team

[uigoku]

I am getting this message on feedback

[uigoku]

It seems something has messed up big time. Please help 🙏

[vorion]

Possible Reason: That error shows up because the phone has been bootloader unlocked + flashed something unofficial. Knox tripped. This was always been the case for all my previous Samsung phones after I rooted or had custom ROM. Did you flash the Beta manually? and somehow triggered the security protocols which tripped the Knox? Just go to About Phone. Software section. Check everything is official. Also boot into Bootloader/download mode and check the warranty void line. If it's 0 / 0x0, then the hardware/eFuse is intact. If it shows any other number other than 0, then it's tripped. You can't do anything about it other than replacing the motherboard.

[uigoku]

Everything is official. No bootloader unlock, no custom rom flashing

[vorion]

That part looks good. Boot into download mode and check the code of Warranty Void. If that is also fine, then it's basically some issue with firmware flash or downgrade. In that case, the error can be resolved by a clean firmware flash.