OneUI 7 beta causing me to fail safetynet & attestation!

[Ricketypumpkin]

Hey everyone, I'm obviously encountering a huge issue here in terms of handicapping myself after uploading this beta to my S24 Ultra. It started the very second the beta was released I was already running it within 10 minutes of it being released I just happen to be on the app when I saw the first person post that it was rolling out so I forced an update through the members app and made it show the banner to me instead of having to wait since it was rolling out relatively slow and the hype was huge. Nothing I did though was anything that would break any functions of safety net nor device attestation components. No knox tripping, no system partition touching, no build prop editing like literally nothing aside from using Samsung's own tools and that's it. Oh, and pushing one file via ADB(not the firmware itself. All firmwares and betas are downloaded and received via OTA just like everyone else there is just a slight bug You can exploit to force members at to show something that's been released on it but maybe not for your specific serial number of the phone or maybe they dropped on the west coast but you live on the east coast.) 

Calling it hacking is literally just to simplify everything but it's not in any way actual hacking and does not even break any rules or terms of service I am for certain it is not that since now the beta is released for every S24 Ultra, I updated the normal way that everyone does via OTA when it was released in my phone, after booting up and running the good guardians app booster/optimizer, I still haven't unknown failing of device attestation. No single app nor can Google themselves Tell me which part of my phone is failing or causing the fail. The Google Play Store just has me marked as not certified but running a check from any of the downloaded Play Store safety net and attestation API checkers, my phone fully passes. 

what I've tried already to fix it; 

• I've cleared app data for all apps involved in safety net checking, not just cleared their cache, but literally cleared the data so full reset on those apps all at once, that did nothing.
• In The Play Store under settings, you can check if you're certified at the bottom of the page and if you're not certified it will offer you a new button saying fix my issue. This is supposed to at the minimum tell you what is causing your device to fail but could potentially even fix the issue, well when I press it, I get an unknown error and it tells me it cannot identify the problem nor can it fix it and it gives me a useless link to explaining what device attestation is, not how to diagnose and fix a phone that inherently cannot fail by default since the bootloader is eternally locked. Nor have I made any attempts at unlocking or playing with any partitions I shouldn't because you can't without very limited success and a ton of work for absolutely minimal gain and even then you can't touch system, so once again to reiterate I have a completely stock as 24 ultra it is a paid off carrier financed model so it is the Sm-928U model but has the unlocked to capabilities of the U1 version. 
• I cannot remember where or how but I came across one possibly helpful piece of information on one of the device checking apps that mentioned something about my region possibly causing the problem. I live in the US and is far as I can see, there is no manual toggle to set device region however my Galaxy tab does have a regional selection under developer settings but that is an entirely different product so I won't mention anything else about that. My clocks and time and date are all set to auto so it does know where I am, all of Google's essentials have full access to my location and every other permission 

Basically what I'm saying is I did literally every single diagnostic I could think of myself and I couldn't fix it so I'm now posting about it to see if there's a brilliant mind in here that can think of something whether it's simply something that gets me on the right track or they have a good idea of what happened, and a device or help is appreciated. As an end-all be all if nothing can fix this, I will completely wipe the device and reflash via Odin/Frijahowever I would really like to not have to use either of those tools since I've had not had to do a factory reset let alone a complete firmware reflash in probably a decade almost. Last time was back when custom ROMs were mainstream and every phone was root friendly. 

If any more information is needed, just ask for whatever you'd like and I'll make sure to get it to you I can update this thread with whatever it needs to be seen. I've also been in the engineering menu by the way both well before this incident and after and there is nothing in there that I can see that has changed for that I know would cause this like there is a toggle for turning on and off secure boot flag in the build prop, but obviously I never have touched that This is my daily phone, and I generally don't ever even run betas on my daily, however I made an exception for OneUI 7. I love the update itself literally the only thing that was lacking from Samsungs department overall was the dynamic animations that Android inherently lacks. I never understood why they decided to stick with the pre-timed animations for every scenario. Versus the iPhone who's pretty much always had a variable and situational dependent animation which is a huge contributor to why iPhones feel so much smoother than Androids. Samsung absolutely closed the ***** out of that gap in smoothness but my performance profile is also messed up somehow. I can never put the phone into light mode otherwise it will become like a Galaxy j3 prime trying to run one UI 7. It will almost instantaneously lock the screen up then it will lock all software up and end up force closing system UI or fully rebooting itself. There's obviously something on a software level that I'm not able to touch that is going on and I'm thinking that I just need to get it over with and factory reset my phone. Does anyone know how that works in regards to being on the beta? If I boot to recovery now after backing everything up manually to the clouds and also to my dedicated 1Tb USBC SSD not flash drive it's an actual SSD that you put in the enclosure and the enclosure has an adapter to adapt the M.2 to USBC. I just want to make sure that I will not have any issues with the phone trying to revert back to 6.1 or me getting kicked out of the beta because of resets triggering something server side to go ahead and force you back to a stable firmware. If that's the case I will have no choice but to be unethical in the way I keep one UI 7 on the phone. Sorry about the long post I just tried to include as much info as possible and all remedies that I've already tried. Thank you in advance for anyone's help! 

[Glenntech]

If an update was not available for your phone, but you somehow made it to be available.
It's likely the issue you are getting is because of network provider added software thats causing issues.
Only certain devices were eligible to participate.

Here is not really the best place to ask and if you have access to the Beta Forum. It will be better to provide feedback there.

Unfortunately going back to previous software can create issues as well.

But ask on the Beta forum and see if anyone there has any ideas

[arianwen27]

I'm just going off the title as there's some info I can give about that. The rest I'm sure someone else will pop in to comment on. Beta updates aren't classed as official so safetynet and attestation errors I'd assume are the phone assuming you have modded software. This is why I say not to use beta software. That's why Google pay breaks.

[Hudz]

To Summarise...
The user is experiencing issues with their Samsung S24 Ultra after installing the One UI 7 beta. They believe the issue is related to device attestation, which is preventing certain apps and features from working properly. They have tried various troubleshooting steps, including clearing app data and checking for regional settings, but the problem persists. They are considering a factory reset or reflashing the firmware as a last resort, but are seeking advice on whether this will resolve the issue or potentially cause further complications with the beta version.
... your welcome.

[Ricketypumpkin]

Lol thank you I attempted to run what I did right normally, through the AI grammar and spelling checker after copying and pasting my post into Samsung Notes.

Obviously the results speak for themselves and I just posted it anyway because at that point, I was like 40 minutes deep into making that post, and it was an nearing midnight. I appreciate you summarizing it as you summarized my issue perfectly! 

[Hudz]

To Summarise...
They tried to use a grammar and spell checker but it didn't work, and they were too tired to fix it manually so they posted it anyway. You understood their issue correctly.
... 😂