Related
I am new to dealing with DRM keys and Sony's TA partition and I ask for a little understanding with my dumb questions.
I bought a white Z3 Dual (D6633) for my wife and immediately unlocked bootloader and rooted the phone. She is super happy with it since speed of the phone and camera quality is a big upgrade from HTC Sensations we both own and used until now.
Reading all this stuff about camera issues after unlocking bootloader + other things that stop working makes me really concerned that I have inadvertently and significantly crippled her phone... On the other hand having a root is absolutely critical for me and so far all phones in our household ended up with custom ROM eventually since manufacturers don't support phones with the new software forewer.
To be honest, I think I've missed saving TA partition option completely while following root guide at http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794 and I've began to wonder if it would be possible to transplant DRM keys from other Z3 with locked bootloader? I am assuming that each phone has an unique set of keys but if I were to move them from one device to a second identical one and therefore there would be no two phones using same keys, would it work or are they locked to the specific IMEI? Although Z3 Dual has 2 IMEIs and only one was asked for while unlocking bootloader.
What I plan to do is to get a second Z3 Dual for myself now but with copper finish and transplant ALL software to my wife's phone. I am quite sure that she will be fine with stock ROM forever but I tend to mess with hardware I own a lot and reflash ROMs very often and I am willing to give up a little bit for these reasons, although while learning how much one needs to give up with Sony, essentially significantly crippling the phone in the process I begin to question if I should give Sony any more of my money...
I am really hoping that some developer will be able to create a ROM restoring most of those lost features in the process.
czguy said:
I am new to dealing with DRM keys and Sony's TA partition and I ask for a little understanding with my dumb questions.
I bought a white Z3 Dual (D6633) for my wife and immediately unlocked bootloader and rooted the phone. She is super happy with it since speed of the phone and camera quality is a big upgrade from HTC Sensations we both own and used until now.
Reading all this stuff about camera issues after unlocking bootloader + other things that stop working makes me really concerned that I have inadvertently and significantly crippled her phone... On the other hand having a root is absolutely critical for me and so far all phones in our household ended up with custom ROM eventually since manufacturers don't support phones with the new software forewer.
To be honest, I think I've missed saving TA partition option completely while following root guide at http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794 and I've began to wonder if it would be possible to transplant DRM keys from other Z3 with locked bootloader? I am assuming that each phone has an unique set of keys but if I were to move them from one device to a second identical one and therefore there would be no two phones using same keys, would it work or are they locked to the specific IMEI? Although Z3 Dual has 2 IMEIs and only one was asked for while unlocking bootloader.
What I plan to do is to get a second Z3 Dual for myself now but with copper finish and transplant ALL software to my wife's phone. I am quite sure that she will be fine with stock ROM forever but I tend to mess with hardware I own a lot and reflash ROMs very often and I am willing to give up a little bit for these reasons, although while learning how much one needs to give up with Sony, essentially significantly crippling the phone in the process I begin to question if I should give Sony any more of my money...
I am really hoping that some developer will be able to create a ROM restoring most of those lost features in the process.
Click to expand...
Click to collapse
If you have read enough, you will know that taking other's TA to restore will result a HARD BRICK of your wife's phone.
Anyhow, I am also interested to know if there's another way out to restore those lost functions. Do update if you found any alternative method
The best thing you can do now is to give her your Z3 and take hers instead. She might not be happy when she finds out you accidentally crippled her phone.
There is no way, and there will not be way to restore DRM keys which you didn't backup.
Even if you send it to Sony.
We had fight with this since xperia arc (me personal) and without hope.
Just give up, change your new phone with her and learn something from this.
Wait couple of months for proper root.
Sent from my C6903 using XDA Free mobile app
I may give up on Sony
Well, it seems that there is nothing I can do now. As I've mentioned I've never dealt with DRM (I get clean content only - years of ripping CDs/DVDs, etc.) and that's one of the reasons I would never buy Apple products for example.
I don't think my wife will ever realize that she is missing anything because I gave her modified phone already, therefor she has no way to compare and as I've mentioned she is super happy with it as it is.
As far I am concerned, I think I will have to seriously reconsider buying another Sony product ever again. I could not care less about DRM and no access to Sony store, however, inadvertently crippling unrelated functionality by unlocking the phone so I can truly own hardware I've paid for is not acceptable.
As it has been said, it is a lesson for me. It's really disappointing because I have believed that I have finally found a truly flagship product with dual SIM functionality...
Well, I can only point out that Sony do tell you this
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
I get that from a first hit of a google search on "Sony unlock bootloader"
I understand your frustration, but I have been with Sony for years and I was aware of this potential problem. If I ever change OEMs I will ensure I treat myself as a noob again and do all the legwork and research I should do before diving in.
I know this does not help you, but I am just trying to get across that the information is out there.
If she doesn't know then what's the issue? Crippling means that the user is hampered by a loss. Her phone isn't crippled by any stretch of the imagination. Now if she tries to use miracast and it doesn't work, then you can say it was crippled, but if she never uses the feature then she's no worse off.
As far as restoring the TA partition, that's null and double null. The keys are encrypted using the hardware of the phone (likely the IMEI) so other signed items will not work. Your best bet is Android L. A completely rewritten Camera stack will be introduced where devs have complete control over the camera's hardware. So some enterprising dev might be able to write a camera app that exceeds the stock camera anyways. As far as anything else, that can be added via opensource alternatives that work fine.
You should be able to return it to the store and swap it for another.
czguy said:
Well, it seems that there is nothing I can do now. As I've mentioned I've never dealt with DRM (I get clean content only - years of ripping CDs/DVDs, etc.) and that's one of the reasons I would never buy Apple products for example.
I don't think my wife will ever realize that she is missing anything because I gave her modified phone already, therefor she has no way to compare and as I've mentioned she is super happy with it as it is.
As far I am concerned, I think I will have to seriously reconsider buying another Sony product ever again. I could not care less about DRM and no access to Sony store, however, inadvertently crippling unrelated functionality by unlocking the phone so I can truly own hardware I've paid for is not acceptable.
As it has been said, it is a lesson for me. It's really disappointing because I have believed that I have finally found a truly flagship product with dual SIM functionality...
Click to expand...
Click to collapse
This is not a personal attack but I'm getting a little bit fed up with reading all these posts about how it's Sony's fault that people f****d up. They clearly advise against unlocking and state that features will be lost. Ok they don't list exactly which but you accepted the risk when choosing to unlock.
I have had a Z3 since release day and I haven't unlocked the bootloader because I read up on it and found that the loss of DRM keys breaks too many things. I had no more information available than you so don't blame Sony for your lack of caution.
I always used Nexus devices before so, like you, I normally unlock and root straight away BUT I exercise due diligence when I get a new device and look into any potential problems first.
This is not Sony's fault, it is yours. Chalk it up to experience.
While we're on that subject, you really ought to give your phone (assuming it's still locked) to your wife. Leaving her a device you have degraded on the basis that she probably won't realise is pretty lousy thing to do.
Thank you guys for your responses. I must admit that I have neglected in-depth research about this issue beforehand. I never cared about loosing access to a specific OEM store and giving up guaranty. After years of unlocking phones and messing with custom ROMs I became overconfident and did not consider degrading so much functionality while keeping stock ROM... Obviously putting a custom ROM on it would be an entirely different story.
I guess this thread may serve as cautionary tale for others
In any case, coming from HTC phones where ROM cookers managed to shoehorn Bravia engine and also some Sony audio enhancements in to it, I really have a high hopes that some custom ROM will restore most of the features...
3Shirts said:
While we're on that subject, you really ought to give your phone (assuming it's still locked) to your wife. Leaving her a device you have degraded on the basis that she probably won't realise is pretty lousy thing to do.
Click to expand...
Click to collapse
This is a bit personal, however, it really depends how you look at it and I don't feel that it was a lousy thing to do. Her having zero technical inclination or understanding and using phone mainly to chat and post some pictures on Facebook, I don't think there was any great harm done. Besides, while wasting too much time with Facebook she has many other exceptional qualities
I am the person who deals with anything electronics related in our home and by messing with phones we own I have managed to extend their functionality far beyond OEMs contribution. And as I have mentioned before, I do hope to continue to do so when Sony stops releasing a new software for this particular model.
This is a definitely a good lesson for me, it was a rush job, I've got her this phone for her birthday and it was delivered the same day I gave it to her. I needed to to obtain the root ASAP as she uses the specific software that does not work without root access.
Yeah, that bit was personal, lol!
I just meant that if you still have a locked one, it would be the chivalrous thing to do to give her that and root it with later when an exploit is found that doesn't kill the low light camera performance. If she's happy though, no harm down I suppose.
3Shirts said:
Yeah, that bit was personal, lol!
I just meant that if you still have a locked one, it would be the chivalrous thing to do to give her that and root it with later when an exploit is found that doesn't kill the low light camera performance. If she's happy though, no harm down I suppose.
Click to expand...
Click to collapse
I am currently really reconsidering if I should go with Sony for my personal phone as well. I am still a big HTC believer (not a fan anymore, they sucked for a few years) and I may stick with HTC Sensation for a little bit longer. By flashing a custom ROM on it, it does everything I need it to do and easily compares with features to todays phones while being 3-4 years old model (antique).
There is a bit more being affected by unlocking bootloader than just low light performance.
http://forum.xda-developers.com/z3-compact/general/loss-drm-keys-t2890936
It's more than I would expect: Bravia Engine (X-Reality, Super Vivid), S-Force Front Surround...
What attracted me to Sony was definitely dual SIM capability (there are practically no other phones with this feature that would work with North American frequencies), waterproofing and having quite impressive guts. HTC has some catching up to do still.
Well, there is still hope. On the Z1 focus on the camera was lost when unlocking the boot on 4.2 with no way to get it back if you had not backed up the TA.
However, once 4.3 came along that fixed the issue for people unlocking and for those who had previously unlocked and lost the ability for the camera to focus.
So, in a future update Sony may fix this issue, or they may not. But hope is not lost
gregbradley said:
Well, there is still hope. On the Z1 focus on the camera was lost when unlocking the boot on 4.2 with no way to get it back if you had not backed up the TA.
However, once 4.3 came along that fixed the issue for people unlocking and for those who had previously unlocked and lost the ability for the camera to focus.
So, in a future update Sony may fix this issue, or they may not. But hope is not lost
Click to expand...
Click to collapse
That was an actual bug though, so they fixed it. This is due to loss of DRM keys so is by design. They might do something but it's unlikely, the DRM keys are there to protect their algorithms
3Shirts said:
That was an actual bug though, so they fixed it. This is due to loss of DRM keys so is by design. They might do something but it's unlikely, the DRM keys are there to protect their algorithms
Click to expand...
Click to collapse
Still weird if you ask me, one reason I am in trouble is because I have never experienced and never expected reduced functionality with other OEMs.
If you unlock HTC you loose hardly anything except guaranty...
I had to write an essay for a class, and I wanted to post it here. Please correct me on anything I'm wrong on, or recommend anything I should add. But please be nice.
Samsung and LG have locked the bootloader - the part of the phone that checks the phone to make sure the code has not been modified or corrupted - almost since the beginning of android smartphone devices. This prevents people who want to modify their phones or write their own code for them from doing so. From the beginning, it was a wise move. Google had not implemented any security protocols like this in the early days of Android, and this kept people’s data safe and secure. The problem now is that Google has implemented security protocols now yet Samsung and LG still lock their phones down - hard. Even a device as old as the Galaxy Note III, about a 5 year old device, Still cannot be modified or changed. People have been trying for years. The issue now is that Samsung and LG are now overdoing it. They do not need that much security in this respect.
Phone manufacturers should not lock their phones bootloader for two reasons, It shortens product life, and it reduces security. Locking bootloaders shorten product life.
If Samsung or LG lock their bootloaders, it does not allow developers to create updates for that phone. If the bootloaders were unlocked, then developers could take the latest android versions on their own time and create updated versions of Android that LG or Samsung do not want to hassle with. This is good, as security updates, new features, and software improvements could be integrated into these custom versions of Android, allowing consumers to add features and tweaks to their phones that would otherwise be unavailable. This is a great extension of the product life, adding years to the operation time. This has already been proven on multiple handsets, for example, the Nexus series of phones. They have been discontinued and unsupported for nearly 3 years, but they still can be upgraded to the latest android version.
The second reason that Android phones should not be locked is it reduces security. The way Google has the unlocking procedure set up on their phones is you first have to understand how to reboot your phone to fastboot mode, which quickly reduces the number of people who could break their phone, then you have to install the fastboot client on your computer, then you have to run the “fastboot oem-unlock” command to unlock the phone. This also wipes all data off the phone, making it act like it is brand new, to protect whatever data is on the phone. One more step is also implemented, if a Google account was signed into the device, the phone remembers that and during the setup process it will lock you out until you enter the credentials of the previous account. This is an incredibly secure process, using a hardware implemented chip on the board, meaning it is physically impossible to break past, giving your data and phone a very tight security. Where phones are now, however, is not secure. The phone I use every day is an LG V20, which you can hack very easily, all you have to do is plug the phone into a computer and run a script I downloaded of the internet. I wanted my phone modded, so it is my problem if the phone breaks. That process is extremely easy. It also did not clear ANY of my data. I also could have deleted the password, allowing me access to all of the data on my phone. This is incredibly insecure, as you can probably see. The phone manufacturers should use Google’s method of locking, as then you do not have hundreds of people working to break the security of a phone, they already have what they want, an unlocked bootloader.
These two problems with locking bootloaders, or more specifically not letting us unlock bootloaders can be catastrophic to the safety of your data. The shortened product life means you keep having to move your data every time you upgrade your phone, and the fact that most of the workarounds for locking bootloaders decrease security drastically, makes allowing us to unlock bootloaders a very beneficial and secure design for new android phones from manufacturers. They should listen to us and give us what we want.
That's it. Any thoughts or suggestions?
Sadly I think we are getting near the end of bootloader unlocking and rooting the next few years. With so many handsets being released so fast. Android finally putting customizations in people want...the days of great Roms that are maintained are fading fast.
Since HTC has gone down the toilet, great Roms like Viper and LeeDroid are gone since they cant maintain so many different platforms since HTC phones are just run of the mill garbage now.
Hope I'm wrong, but I rarely have a desire except for a kernel and a few minor things that requiring rooting personally. Every custom Roms I've tried for OP something that is critical and basic doest work and I end up back on the Beta and now Q again. As a Verizon customer as well, this adds to the problem.
And then companies like Samsung have pulled an Apple so bootloader unlocking or rooting makes your phone whatever they decide it should be, and void your warranty.
Sorry mods, off topic. Been around a long time and did WinMo dev 10yrs ago on here...we know how that ended....haha
Android is an operating system based on Linux. Linux is distributed under the GNU GPL v2 License. The GPL v2 grants some rights to the user, in particular requesting source code and/or being able to modify a program licensed under it.
Even tho there has been an idea of license v3 because of some controversies, Still, it is not possible for any manufacturer TOS (terms of service) and EULA (end user license agreement) to negate the rights guaranteed by GNU GPL (general public license), as that would be a GPL violation on the part of the manufacturer, who'd lose the right to use the Linux kernel.
All I'm saying is any android device manufacturer is obligated to provide you with a way to unlock bootloader, you just have to demand it the correct way. They can't possibly deny your demand.
They'll lock phones more and more because it helps the security state to keep access to your data.
Google and most tech companies are pretty much part of the intelligence complex and serve the state oligarchy as we have seen with censorship of search results and social media.
I remember before this pandemic, it was not hard to find information about treatments and health. Nowadays, everything is focused on "official sources" like the government agencies that serve big pharma, big war, etc.
I'm one of those guys that always roots everything. I used to do it for xposed and piracy, however two devices ago I had the sony xperia x2, and when I rooted that I got major issues which were simply something that happens on that device (camera can't take pics anymore, miracast fails to mirror content due to tripped DRM). My next phone was a galaxy s10e, and I was too scared to root that, plus with all Samsung's features I didn't feel the need to root. (and I started paying for apps instead of pirating them)
Now I'm on the moto g100, using Macrodroid and Termux, and there are some things that I want to do that require root access.
My question is, will rooting affect the g100 in specific, known ways, (beyond standard possibilities of bricking that exist on all devices)? For example, will Ready For suddenly not work?
I rooted my Edge S on stock, I didn't lose anything. Others report losing L1 but I didn't so
Hello I was wondering if there was a way to secure an Android device after unlocking it and installing a custom rom, maybe somebody has a thread or something.
Theoretically speaking anybody can take the device and do whatever he wants with fastboot or twrp.
Relocking it can have unforeseen consequences as some here have learned. I may be incorrect (depends on the variant too) as I don't root but the more you do, the more can go wrong.
I don't screen lock my device or encrypt my data because I don't want to be locked out, ever.
Physical possession is the only real security, relocking it isn't needed or desirable.
Anyone that tries to take my device is headed to the hurt locker. Consequences.
@fdor
Once an Android device's bootloader got unlocked ( disabling AVB included ) the device's Android is vulnerable.
blackhawk said:
Relocking it can have unforeseen consequences as some here have learned. I may be incorrect (depends on the variant too) as I don't root but the more you do, the more can go wrong.
I don't screen lock my device or encrypt my data because I don't want to be locked out, ever.
Physical possession is the only real security, relocking it isn't needed or desirable.
Anyone that tries to take my device is headed to the hurt locker. Consequences.
Click to expand...
Click to collapse
Thanks for the information, could you elaborate on screen locking? or link a thread I'm not sure what you speak of.
fdor said:
Thanks for the information, could you elaborate on screen locking? or link a thread I'm not sure what you speak of.
Click to expand...
Click to collapse
That's a separate subject but the concept is they same. Anything you lock especially will a password, you can get locked out yourself. Many times through no fault of your own as in a hardware failure.
An unlocked boot loader is a security risk... a bricked device much less so
On a stock Android Pie or higher (even not updated) security isn't an issue unless you do something stupid.
One reason I don't root.
Anytime you load unofficial firmware you're talking a risk plus it's distribution volume is much lower so if any malware is present it doesn't have as much exposure. Meaning it's likely to take longer to be detected.
Hey! So, I wanted to know what exactly trips the knox efuse:
-The unlock of the bootloader,
-The installation of a custom recovery, or
-The rooting
Also, what exactly do I lose if I trip it (aside from warranty)?
Just in case: I have a S908E
Thanks in advance
What is a Knox Warranty Bit and how is it triggered?
Features lost when Rooting?
I asked in one of the root threads and didn't get a reply. From looking through the existing threads I understand that you lose samsung pay and the hidden folder feature. I can live with those but is there any other features lost when unlocking...
forum.xda-developers.com
affigne said:
Hey! So, I wanted to know what exactly trips the knox efuse:
-The unlock of the bootloader,
-The installation of a custom recovery, or
-The rooting
Also, what exactly do I lose if I trip it (aside from warranty)?
Just in case: I have a S908E
Thanks in advance
Click to expand...
Click to collapse
I believe it's the rooting.
In my case the moment, I flashed something that hadn't the official signature (TWRP), it tripped.
blackhawk said:
What is a Knox Warranty Bit and how is it triggered?
Features lost when Rooting?
I asked in one of the root threads and didn't get a reply. From looking through the existing threads I understand that you lose samsung pay and the hidden folder feature. I can live with those but is there any other features lost when unlocking...
forum.xda-developers.com
Click to expand...
Click to collapse
You lose anything that relies on Knox. Samsung Wallet, Samsung Pass, Samsung Health, most banking apps, Secure Folder, and IT management tools like Intune,
So we can agree that unlocking the bootloader doesn't trip knox, right?
Correct.
affigne said:
So we can agree that unlocking the bootloader doesn't trip knox, right?
Click to expand...
Click to collapse
Probably not. It's a Snapdragon right? Notoriously hard to root; what's to be gained by unlocking the bootloader?
I leave the firmware alone and use work arounds. It's to the point where I won't even do any upgrades or updates especially OTA. My devices are fulfilling their mission and as such are too valuable to risk losing. Stock loads once optimized can run well, be very stable and long lived with little maintenance.
This N10+ N975U/Pie current load is over 2 yo, still running like a bat out of hell. There was a time it was a stuttering hot running hog... a real pig. I conservatively disabled about 80 apks, mucked extensively with the settings and used a few third party apps for work arounds, to enhanced operation and security. This is what a stock Samsung is capable of.
My other N975U1 runs on 10, it's setup profile is nearly identical in spite of the many dozens of new small Samsung system apks, I left almost all untouched. If it's not resource hog, or a security risk, or crapware like Device Wellness crowding my settings menu I leave it be. I started with the worst offenders and worked my way down.
Android 11 and especially 12 will offer some new very annoying challenges which is why I bypassed them entirely. I loathe the bootloader rollback protection that locks you into 10 and 11 on my device. Moral of the story, look very carefully before you leap. Lol, let Mikey try it first. Where there's little to gain there's a lot to lose.
I still prefer the simplicity, functionality and usability of 9. However I haven't evaluated camera image quality of the 10 variant; it's more of pain to use though is my first impression. Other than possible that and better dark mode there are few tangible improvements and some annoying downsides that will need workarounds.
Scoped storage, some of the rude surprises.
Android 12, dirty pipe... older kernels not effected.
Android 13, if all goes to plan...
blackhawk said:
Probably not. It's a Snapdragon right? Notoriously hard to root; what's to be gained by unlocking the bootloader?
I leave the firmware alone and use work arounds. It's to the point where I won't even do any upgrades or updates especially OTA. My devices are fulfilling their mission and as such are too valuable to risk losing. Stock loads once optimized can run well, be very stable and long lived with little maintenance.
This N10+ N975U/Pie current load is over 2 yo, still running like a bat out of hell. There was a time it was a stuttering hot running hog... a real pig. I conservatively disabled about 80 apks, mucked extensively with the settings and used a few third party apps for work arounds, to enhanced operation and security. This is what a stock Samsung is capable of.
My other N975U1 runs on 10, it's setup profile is nearly identical in spite of the many dozens of new small Samsung system apks, I left almost all untouched. If it's not resource hog, or a security risk, or crapware like Device Wellness crowding my settings menu I leave it be. I started with the worst offenders and worked my way down.
Android 11 and especially 12 will offer some new very annoying challenges which is why I bypassed them entirely. I loathe the bootloader rollback protection that locks you into 10 and 11 on my device. Moral of the story, look very carefully before you leap. Lol, let Mikey try it first. Where there's little to gain there's a lot to lose.
I still prefer the simplicity, functionality and usability of 9. However I haven't evaluated camera image quality of the 10 variant; it's more of pain to use though is my first impression. Other than possible that and better dark mode there are few tangible improvements and some annoying downsides that will need workarounds.
Scoped storage, some of the rude surprises.
Android 12, dirty pipe... older kernels not effected.
Android 13, if all goes to plan...
Click to expand...
Click to collapse
I get you. Ever since I've got my S7 I haven't rooted any other phone I had (s10+ SD and this S22U SD as well). This is why I am not updated on the knox thing - Last time I rooted a phone was a S5 exynos). But when I searched for rooting my s22u I stumbled across this knox thing. Researched a bit but still couldn't find the answers to my questions, hence this thread.
Now don't get me wrong, I'm currently not too sold in the idea of rooting my s22u due to the benefits still not outweighing the caveats, but I'm not entirely shut down from the idea. Custom recovery, full access to my folders (I hate scoped storage), enhanced android auto experience... these are some of the things I'd like to have, but then tripping the knox means void warranty, knox-relying apps not working, encryption kissed bye-bye, and half-priced trade-in for the next S23U, if any (I'd like to upgrade it just so I can enjoy full SoC power without the known heating issues of this phone, plus more powerful chip). So, kind of in a dilemma right now.
affigne said:
I get you. Ever since I've got my S7 I haven't rooted any other phone I had (s10+ SD and this S22U SD as well). This is why I am not updated on the knox thing - Last time I rooted a phone was a S5 exynos). But when I searched for rooting my s22u I stumbled across this knox thing. Researched a bit but still couldn't find the answers to my questions, hence this thread.
Now don't get me wrong, I'm currently not too sold in the idea of rooting my s22u due to the benefits still not outweighing the caveats, but I'm not entirely shut down from the idea. Custom recovery, full access to my folders (I hate scoped storage), enhanced android auto experience... these are some of the things I'd like to have, but then tripping the knox means void warranty, knox-relying apps not working, encryption kissed bye-bye, and half-priced trade-in for the next S23U, if any (I'd like to upgrade it just so I can enjoy full SoC power without the known heating issues of this phone, plus more powerful chip). So, kind of in a dilemma right now.
Click to expand...
Click to collapse
I hear you. Not even sure you can root it. For my N10+'s because they are Snapdragon's the only way to root them is giving a 3rd party vendors complete access to the device to unlock the bootloader, I believe. If that service is even available for the S22U yet. Do know 100% as this is a passing curiosity for me so I haven't looked that hard. I doubt Samsung have made it any easier in the last 3 years especially for the Snap variants.
You can use adb edits to tone it down a bit. Not sure my favorite package disabler works on 12, someone told me it didn't. Again that's a passing curiosity because I have no plans to upgrade these older phones unless they would run better, which I highly doubt.