Same as the title.
Sent from my DROID2 GLOBAL using XDA App
from what i remember it is not
Our bootloaders are NOT signed, our bootlaoders are locked down, and SIGNATURE checking, ie they check kernel and recovery's sigantures
jcase said:
Our bootloaders are NOT signed, our bootlaoders are locked down, and SIGNATURE checking, ie they check kernel and recovery's sigantures
Click to expand...
Click to collapse
When you say "our" bootloaders what do you mean? Community developed bootloaders or bootloaders used on the Thunderbolt in general?
So, is it possible for me to load a modified bootloader onto a Thunderbolt without it being rejected?
Master Melab said:
When you say "our" bootloaders what do you mean? Community developed bootloaders or bootloaders used on the Thunderbolt in general?
So, is it possible for me to load a modified bootloader onto a Thunderbolt without it being rejected?
Click to expand...
Click to collapse
Thunderbolt bootliaders, yes we could load a modified one, but why at this point?
Sent from my Verizon Samsung Fascinated II
Master Melab said:
When you say "our" bootloaders what do you mean? Community developed bootloaders or bootloaders used on the Thunderbolt in general?
Click to expand...
Click to collapse
Which community developed ones are you referring to? Are there any bootloaders available for the TB, other than the original one and the engineering one which allowed rooting? What do you mean?
I don't know if there are any community developed bootloaders for it. I just mean in general.
Sent from my DROID2 GLOBAL using XDA App
A little off-topic, but since HTC has pledged not to encrypt them, I've been wondering: could they, if they changed their minds, replace our current bootloader to an encrypted one, or would that also necessitate hardware to support encrypted bootloaders?
nerozehl said:
A little off-topic, but since HTC has pledged not to encrypt them, I've been wondering: could they, if they changed their minds, replace our current bootloader to an encrypted one, or would that also necessitate hardware to support encrypted bootloaders?
Click to expand...
Click to collapse
Good question...... is encryption hardware, or software based? Or both???
nerozehl said:
A little off-topic, but since HTC has pledged not to encrypt them, I've been wondering: could they, if they changed their minds, replace our current bootloader to an encrypted one, or would that also necessitate hardware to support encrypted bootloaders?
Click to expand...
Click to collapse
Could they? Sure. Will they? Don't hold your breath. They will more than likely only leave future devices unlocked. Either way, it doesn't effect us in any way, seeing as we can flash the engineering bootloader.
Sent from my HTC Thunderbolt
nerozehl said:
A little off-topic, but since HTC has pledged not to encrypt them, I've been wondering: could they, if they changed their minds, replace our current bootloader to an encrypted one, or would that also necessitate hardware to support encrypted bootloaders?
Click to expand...
Click to collapse
This is a misconception that drives me nuts. If the bootloader were encrypted it could not function because it just be gibberish to the processor. This is what encryption would do (using 128 bit AES, values are in hexadecimal, test value from FIPS-197):
Code:
Key: 000102030405060708090a0b0c0d0e0f
Plaintext: 00112233445566778899aabbccddeeff
Ciphertext: [COLOR="Blue"]69c4e0d86a7b0430d8cdb78070b4c55a[/COLOR]
On the iPhone, the iPod touch, and the iPhone 3G, the first-stage bootloader (LLB) checked the one above it. But, the LLB was not signature checked by the hardware in those models as it is now in the iPhone 3GS and up, the iPod touch 2G and up, and the iPad and up. What I want to know is if the Thunderbolt's hardware does this, too?
Master Melab said:
This is a misconception that drives me nuts. If the bootloader were encrypted it could not function because it just be gibberish to the processor. This is what encryption would do (using 128 bit AES, values are in hexadecimal, test value from FIPS-197):
Code:
Key: 000102030405060708090a0b0c0d0e0f
Plaintext: 00112233445566778899aabbccddeeff
Ciphertext: [COLOR="Blue"]69c4e0d86a7b0430d8cdb78070b4c55a[/COLOR]
Click to expand...
Click to collapse
After our discussion in Bada section I look once in a while at your threads.
Sure that people tend to confuse authentication and confidentiality cryptographic services, but your understanding of the digital electronics is also less than scarce. The higher stages of the bootloader may be encrypted as they are often loaded to RAM before execution and there's no problem with decrypting it in the loading process. Specialized uCs may use some form of encryption in the pipelining process. Additional important factor is the difference between bootloader stored and downloaded - the bootloader before being stored to the flash (ergo the file containing the bootloader you may have) may be encrypted (as it is with the Wave bootloader we've discussed in the Bada section).
mijoma said:
After our discussion in Bada section I look once in a while at your threads.
Sure that people tend to confuse authentication and confidentiality cryptographic services, but your understanding of the digital electronics is also less than scarce. The higher stages of the bootloader may be encrypted as they are often loaded to RAM before execution and there's no problem with decrypting it in the loading process. Specialized uCs may use some form of encryption in the pipelining process. Additional important factor is the difference between bootloader stored and downloaded - the bootloader before being stored to the flash (ergo the file containing the bootloader you may have) may be encrypted (as it is with the Wave bootloader we've discussed in the Bada section).
Click to expand...
Click to collapse
So then where would the decryption of the payload take place? On the phone?
Master Melab said:
So then where would the decryption of the payload take place? On the phone?
Click to expand...
Click to collapse
Yes, on the phone.
Is this what the Thunderbolt does? And what low level stages the booting process would not be encrypted?
Related
Okay, so. Rogers One XL and AT&T One X are basically the same device right? Same essentially all the way through? Would it be super farfetched to think that if one were to take the file that is modified by the HTCdev unlock for the Rogers One XL, and push it to the AT&T One X, that it would unlock it? I'm sure there's something making this completely illogical and impossible but I figured maybe I'd mention it, though I'm sure it's been thought of.
Unless I'm mistaken your unlock is directly related to your phone's iemi number.
I had a feeling that would be the case.
gunnyman said:
Unless I'm mistaken your unlock is directly related to your phone's iemi number.
Click to expand...
Click to collapse
I suppose you can't change something like that?
Sent from my HTC One X
ECEXCURSION said:
I suppose you can't change something like that?
Sent from my HTC One X
Click to expand...
Click to collapse
No sir.. the unlock code is unique to each device :-\
Sent from my GT-P3113 using xda premium
I've proposed this several times in the last week or so and nobody has paid attention. I've yet to hear somebody say, for certain, what the unlock code is based on and I'm sure that we haven't fully investigated whether the code is really unique or whether that's just what we have been led to believe.
What we should do is start making a table of numbers (IMEIs, Device ID Tokens, Serial Numbers, Unlock Codes, etc) to see if a pattern emerges. Even if it is based on IMEI numbers, if we figure out how the number is arrived at (could it be as easy as md5(IMEI) or something???), we may be able to bypass HTCDev.
Billy
If I was a betting man I'd say the code is heavily encrypted.
Maybe HTC made it simple and easy for us to crack on purpose because they embrace the android community and despise AT&T as much as we do... Never know till you try.
Sent from my HTC One X
One idea that I've had bouncing around is using the onboard storage as a virtual goldcard. Use it to load a phone image that has unlocked bootloader. I have no idea if such a thing is even possible
gunnyman said:
One idea that I've had bouncing around is using the onboard storage as a virtual goldcard. Use it to load a phone image that has unlocked bootloader. I have no idea if such a thing is even possible
Click to expand...
Click to collapse
But the gold card needs to be separate from the actual storage and be able to be mounted and unmounted at will like a true gold card I would think]
gunnyman said:
If I was a betting man I'd say the code is heavily encrypted.
Click to expand...
Click to collapse
Depending on how they encrypted it... it might not be so hard to work around though.
That said - it's probably public key encryption, with the phone having one half of it.
We really should get a couple examples of the inputs and outputs of HTCDev to look at though - you never know! People smarter than me may be able to deduce a pattern.
After 5.0 hits all the Z3 devices i wonder if its actually possible to have a locked bootloader with functional DRM Keys on a Custom rom like CM12?
Sorry for this dumb question i am actually really new on all this android stuff! switched from an iphone 5 but i love my xperia Z3
greetings and thanks for the reply
n1ete said:
After 5.0 hits all the Z3 devices i wonder if its actually possible to have a locked bootloader with functional DRM Keys on a Custom rom like CM12?
Sorry for this dumb question i am actually really new on all this android stuff! switched from an iphone 5 but i love my xperia Z3
greetings and thanks for the reply
Click to expand...
Click to collapse
In short no. It requires a working kexec and that has not been able for about 18 months now
OK, thank you for this answer! so how hard will it be to archive this goal? any possibilities ?
n1ete said:
After 5.0 hits all the Z3 devices i wonder if its actually possible to have a locked bootloader with functional DRM Keys on a Custom rom like CM12?
Sorry for this dumb question i am actually really new on all this android stuff! switched from an iphone 5 but i love my xperia Z3
greetings and thanks for the reply
Click to expand...
Click to collapse
There are no need for features protected by DRM keys.
CM don't have those things...
That's the whole purposes of DRM keys...to hide Sonys features and innovations from third parties..
When you are using CM ROM or something that's not stock or stock based you don't have X-reality or stock camera app with low light processing, at least not developed by Sony...
DRM keys are overrated...That's just mechanism to protect code...nothing special...
So when you unlock bootloader system will wipe some of parts so other manufacturers or developers can't see what's under the hood and can't take that and implement them into their work...
Z3 powered by Tapatalk
True about DRM
But as for getting a working kexec, a lot of good people have tried and seem to keep getting stuck with the problem that we just do not have Sony's keys. Without them its impossible*. I would not hold out any hopes for anything soon....
*Obviously nothing is impossible, I could break RSA code given a powerful enough computer and few thousand years...
If you can backup the TA partition with a root exploit before unlocking the bootloader can you not extract the keys from that partition?
Sent from my D6603 using XDA Free mobile app
Bansheleh said:
If you can backup the TA partition with a root exploit before unlocking the bootloader can you not extract the keys from that partition?
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
The TA partition is signed such that if you restore a TA partition with valid DRM keys, you also restore the bootloader lock. If you try to alter it in order to have an unlocked bootloader and DRM keys, the signature check fails and you've got a hardbrick.
Entropy512 said:
The TA partition is signed such that if you restore a TA partition with valid DRM keys, you also restore the bootloader lock. If you try to alter it in order to have an unlocked bootloader and DRM keys, the signature check fails and you've got a hardbrick.
Click to expand...
Click to collapse
The DRM keys seems to be endless mantra here... I will make an educated guess... People who invested almost 600€ into top notch phone and are keen on Sony bells and whistles will prefer to stay on stock with possibility to root on locked bootloader. People who develop CM or AOSP have other motivation than keeping on Sony proprietary code. They want they excellent hardware to run open and clean system. So they will not invest their time and efforts into breaking DRM for couple of low-light picture and X-reality frenzy. Not to speak about legal implications.. So in my opinion we are not going to see DRM protected code running on CM or elsewhere. And that's right. What is Cesar's belongs to Cesar.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
The DRM keys seems to be endless mantra here... I will make an educated guess... People who invested almost 600€ into top notch phone and are keen on Sony bells and whistles will prefer to stay on stock with possibility to root on locked bootloader. People who develop CM or AOSP have other motivation than keeping on Sony proprietary code. They want they excellent hardware to run open and clean system. So they will not invest their time and efforts into breaking DRM for couple of low-light picture and X-reality frenzy. Not to speak about legal implications.. So in my opinion we are not going to see DRM protected code running on CM or elsewhere. And that's right. What is Cesar's belongs to Cesar.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, the only real "loss" from losing the DRM keys for many of us is that frequently Sony's cam blobs outright fail without DRM keys - and our approach to that is more political - we're trying to cooperate with Sony's devrel team to get their production firmware teams to stop making cam HALs that break catastrophically on unlocked devices.
A lot of us were REALLY annoyed when a GPE device (ZU GPE) had the camera break on unlocked devices. The problem is, working with the TA partition is fundamentally dangerous, and Sony does a GREAT job of bootloader security. Over the years, bootloader unlock exploits have become rarer and rarer and it just isn't worth the effort. There's a lot less effort and risk in unbreaking the cam HALs.
Entropy512 said:
Yeah, the only real "loss" from losing the DRM keys for many of us is that frequently Sony's cam blobs outright fail without DRM keys - and our approach to that is more political - we're trying to cooperate with Sony's devrel team to get their production firmware teams to stop making cam HALs that break catastrophically on unlocked devices.
A lot of us were REALLY annoyed when a GPE device (ZU GPE) had the camera break on unlocked devices. The problem is, working with the TA partition is fundamentally dangerous, and Sony does a GREAT job of bootloader security. Over the years, bootloader unlock exploits have become rarer and rarer and it just isn't worth the effort. There's a lot less effort and risk in unbreaking the cam HALs.
Click to expand...
Click to collapse
I understand the Sony politics but I am honestly convinced that they would greatly benefit from Open Source development community of they wouldn't make such big obstructions on codebase. Z series are amazing devices and would be even better with clean open high performance bloat free system.
Sent from my D6603 using XDA Free mobile app
It was just reported that OnePlus has been leaking a devtool by Qualcomm that can be used to root Qualcomm devices without unlocking the bootloader. It got me to wondering if it could somehow be used to obtain root on the Verizon version of the Pixel 2.
https://www.xda-developers.com/oneplus-root-access-backdoor/
It's not installed on the Pixel, as best I can determine, so no go.
Well yes...I wouldn't expect it to be installed on the Pixel by Google, but perhaps it can be sideloaded.
If it were to be installed on the Pixel, I think it would need to be given system write permissions, which I know is possible to some degree via ADB without root.
Am interested to see where this leads. It's probably a dead end but at least worth poking at.
I wonder if @jcase has any thoughts on this.
Krunk_Kracker said:
I wonder if @jcase has any thoughts on this.
Click to expand...
Click to collapse
It was a development app, not anything new. It is specific to the device it was built for.
jcase said:
It was a development app, not anything new. It is specific to the device it was built for.
Click to expand...
Click to collapse
Welp, that settles that. I assumed that it was compatible with Qualcomm SoC's in general, and not device specific. Thanks!
It's not device specific in that sense, it's device specific in that unless it's pre-loaded with system privileges, you won't be able to side-load and use it for root.
Telperion said:
It's not device specific in that sense, it's device specific in that unless it's pre-loaded with system privileges, you won't be able to side-load and use it for root.
Click to expand...
Click to collapse
Ahh, I see. Even if we got it on the Pixel 2, there's no way to give it the access that it needs. Gotcha.
I'm going to start this by saying that I believe I have the ability to unlock the bootloader. There's a script that (in theory) allows you to bruteforce the unlock code. You do have to downgrade to EMUI 9.1 using HiSuite though that is at least possible even if you're currently on 10.1 like I am. Multiple downgrades is required.
While this is going on, I have gone ahead and created a Github repository under the username sackmaniac for my device (LYA-L09, 128GB storage, I have given codename as rickastley and I promise that isn't a joke) so assistance with what needs to be in the repository would also be appreciated. I'm quite new to this. LINK
Eventual goal to me personally is a LineageOS build.
Preparation for device rickastley:
1. Downgrade to EMUI 9.1.
2. Use programminghoch10 / SkyEmie bruteforce method. Expect it to take a long time LINK
3. There's a TWRP build somewhere on the Internet, I'm on mobile right now so cannot currently find the link.
4. Extract proprietary blobs. Someone will need to tell me how to do this on a stock ROM because that's I have.
5. The actual process of building whatever is needed.
Hint - there's OpenKirin for our device
OpenKirin
openkirin.net
Builds on AEX/LOS. Developers however refuse to share any details of internal components (sketchy). EMUI 10.1 might be also containing new drivers for certain phone features for new android version compatibly, and possibly cannot be extracted on non-rooted phone. (no root - no way to get it out), so that sadly makes EMUI 9/9.1 the only driver source.
A lineage os stable build for emui 9.1 would still be awesome !!!
dimon222 said:
Hint - there's OpenKirin for our device
OpenKirin
openkirin.net
Builds on AEX/LOS. Developers however refuse to share any details of internal components (sketchy). EMUI 10.1 might be also containing new drivers for certain phone features for new android version compatibly, and possibly cannot be extracted on non-rooted phone. (no root - no way to get it out), so that sadly makes EMUI 9/9.1 the only driver source.
Click to expand...
Click to collapse
That's a shame. Still though, having no luck with the bootloader unlock either so we can't even try this
flyl0 said:
A lineage os stable build for emui 9.1 would still be awesome !!!
Click to expand...
Click to collapse
Yeah... Bruteforce tool isn't going to happen. Any ideas?
K14_Deploy said:
Yeah... Bruteforce tool isn't going to happen. Any ideas?
Click to expand...
Click to collapse
No there is no way that I know to have a bootloader unlock code now, but I got my code here by an xda member back in the days.
flyl0 said:
No there is no way that I know to have a bootloader unlock code now, but I got my code here by an xda member back in the days.
Click to expand...
Click to collapse
I heard Huawei disabled the unlock command on 10.1, so I rolled back to 9.1. Can you please put me in contact with this person?
K14_Deploy said:
I heard Huawei disabled the unlock command on 10.1, so I rolled back to 9.1. Can you please put me in contact with this person?
Click to expand...
Click to collapse
It was 2 years ago I believe now, I do not remember who it is and I think that it is no longer possible to have codes even through this person, He gave it to me for free and I just sent my imei.
flyl0 said:
It was 2 years ago I believe now, I do not remember who it is and I think that it is no longer possible to have codes even through this person
Click to expand...
Click to collapse
Thanks anyway. Btw if this person is watching this thread, @ me.
All unlock codes were going from centralized technical database on Huawei side. Huawei did shutdown it, but opened it rarely for unknown reason (perhaps, someone had to fix something?). Database is down for long time now, it might never come back online. I would suggest to forget about this option altogether.
Instead, consider A/B Android builds for different experience of non-Huawei OS. Tho, I'm not sure how realistic it is on this device. (Haven't bothered trying)
dimon222 said:
All unlock codes were going from centralized technical database on Huawei side. Huawei did shutdown it, but opened it rarely for unknown reason (perhaps, someone had to fix something?). Database is down for long time now, it might never come back online. I would suggest to forget about this option altogether.
Instead, consider A/B Android builds for different experience of non-Huawei OS. Tho, I'm not sure how realistic it is on this device. (Haven't bothered trying)
Click to expand...
Click to collapse
This database... Was it made public? Is there an internet archive somewhere?
A/B is a non starter, Huawei devices barely support Treble. It seems like bootloader is the only option, however it would be nice if it's easy for anyone who wants to be able to unlock their bootloader. Mostly from a right to repair standpoint.
K14_Deploy said:
This database... Was it made public? Is there an internet archive somewhere?
A/B is a non starter, Huawei devices barely support Treble.
Click to expand...
Click to collapse
No. It was only accessible by technical personnel of Huawei (I guess that's who was leaking those codes afterall... Some insider). And it worked more like "enter IMEI" and wait 25 minutes to get unlock code back. Not a simple search/exportable database. Afterall, IMEI leaking might be problematic for such bases.
dimon222 said:
No. It was only accessible by technical personnel of Huawei (I guess that's who was leaking those codes afterall... Some insider). And it worked more like "enter IMEI" and wait 25 minutes to get unlock code back. Not a simple search/exportable database. Afterall, IMEI leaking might be problematic for such bases.
Click to expand...
Click to collapse
Makes sense.
K14_Deploy said:
Makes sense.
Click to expand...
Click to collapse
Theoretically if you're good with such kind of things, you could try with testpoint, however, I have no idea where it will lead.
This is where its located on our device (expand spoiler on + sign)
Huawei Mate 20 Pro - Прошивки - 4PDA
Huawei Mate 20 Pro - Прошивки
4pda.ru
dimon222 said:
Theoretically if you're good with such kind of things, you could try with testpoint, however, I have no idea where it will lead.
This is where its located on our device (expand spoiler on + sign)
Huawei Mate 20 Pro - Прошивки - 4PDA
Huawei Mate 20 Pro - Прошивки
4pda.ru
Click to expand...
Click to collapse
I shall open Google translate and take a look. Thank you.
Edit: had a look. Its based off a paid service, would rather avoid them if possible but that is seeming less and less possible. I have contacted DC Unlocker to see if they can unlock our devices. I still don't think it should cost 4 EURO to look through a database but there you go.
K14_Deploy said:
I shall open Google translate and take a look. Thank you.
Edit: had a look. Its based off a paid service, would rather avoid them if possible but that is seeming less and less possible. I have contacted DC Unlocker to see if they can unlock our devices. I still don't think it should cost 4 EURO to look through a database but there you go.
Click to expand...
Click to collapse
Test point has nothing to do with DC unlocker. It's a way to physically shorten device to load engineering bootloader with potentially more permissions available. It's just DC unlocker and such tools previously had a way to read bootloader code directly via loopholes in devices with old firmwares. It's not longer the case for devices of past decade I believe. Test point is available, but what it leads to - is a question. At least it might be possible to dump everything from device, including potentially encrypted bootloader key.
Link above - don't read top post, look at last post in page that has attachment with test point location to be shortened.
dimon222 said:
Test point has nothing to do with DC unlocker. It's a way to physically shorten device to load engineering bootloader with potentially more permissions available. It's just DC unlocker and such tools previously had a way to read bootloader code directly via loopholes in devices with old firmwares. It's not longer the case for devices of past decade I believe. Test point is available, but what it leads to - is a question. At least it might be possible to dump everything from device, including potentially encrypted bootloader key.
Link above - don't read top post, look at last post in page that has attachment with test point location to be shortened.
Click to expand...
Click to collapse
Ah. That makes more sense. Obvious downside of this method (if I can read correctly) is needing to open the device up, which isn't exactly easy. Or if it's the engineering build, then that seems to only be for the dual sim device (I believe they have different firmwares, if that isn't true I shall try using DLOAD with it)
UPDATE: Posted a rant / open letter about this on the official Huawei forums, let's see how long until someone from Huawei deletes it.
Good to know!
Do you have a link to the post so we can follow the discussion there?
TheLostOne said:
Good to know!
Do you have a link to the post so we can follow the discussion there?
Click to expand...
Click to collapse
Here you go. Also to be clear, being reported for hate speech from this would be less than ideal.
Could there be any downside to root my phone now (with Magisk) as if I were doing it later?
Is it possible that future versions of Magisk (or any other rooting method) will retain more original factory features (Google Pay, Samsung Pay, Widevien DRM etc...?
Or is this very unlikely?
At least everything related to Knox (e.g. Samsung Pay, Secure Folder....) will not work any more once unlocked and rooted - even if relocking and going back to full stock.
GPay should work now..... but this is judging from my experience with other current phones, still waiting for Samsung to deliver my S22U
s3axel said:
At least everything related to Knox (e.g. Samsung Pay, Secure Folder....) will not work any more once unlocked and rooted - even if relocking and going back to full stock.
GPay should work now..... but this is judging from my experience with other current phones, still waiting for Samsung to deliver my S22U
Click to expand...
Click to collapse
What about warranty ? does unlocking bootloader or rooting or flashing custom rom break he warranty ?
nabil427 said:
What about warranty ? does unlocking bootloader or rooting or flashing custom rom break he warranty ?
Click to expand...
Click to collapse
Yes
Does relocking your bootloader revert to allowing you to use bank apps once again?
nabil427 said:
What about warranty ? does unlocking bootloader or rooting or flashing custom rom break he warranty ?
Click to expand...
Click to collapse
I definitely want to root my phone to gain maximum control over it.
The conrol over my phone is more important to me than the warranty.
As far as I know sadly until now Knox was never bypassed.
s3axel said:
Yes
Click to expand...
Click to collapse
I wish someone could find a solution to bypass Knox.
dj24 said:
Does relocking your bootloader revert to allowing you to use bank apps once again?
Click to expand...
Click to collapse
I have read that banking apps work on rooted devices. You do not need to relock your bootloader.
Alibab said:
I have read that banking apps work on rooted devices. You do not need to relock your bootloader.
Click to expand...
Click to collapse
They do, at least on my recently rooted phones and for the apps I use.... Safetynet passes, Gpay ist working fine....
But this is the usual cat&mouse game , actually for the S22U my intention is to try going unrooted - we'll see how long this holds
Alibab said:
Is it possible that future versions of Magisk ...?
Or is this very unlikely?
Click to expand...
Click to collapse
Indeed we have no idea about "future of magisk" so don't rely on future verion of magisk
If you want to root, just look into current scenario and decide you want to root or not. As of now (On OneUI 4.0 on other devices) Samsung Pay & Samung Pass (and Knox thingy) doesn't work. Though it doen't mean everything other works, still you needs to patch multiple things like Samsung Health, Secure folder, Private sharing and may be more. Also many apps may not work but you needs to hide them with magisk (Still no guarantee it will work)
So my pesonal advice is to before jumping to rooting, read as much possible rooting and magisk thread. Rooting is one way, once you trip knox, it's for forever and some stuff never work again even after relocking bootloader.
Alibab said:
I definitely want to root my phone to gain maximum control over it.
The conrol over my phone is more important to me than the warranty.
As far as I know sadly until now Knox was never bypassed.
Click to expand...
Click to collapse
There have been ongoing issues and failures with the variable rate displays going back to the N20U, it could to be an expensive gamble.
There's zero track record for this model but expect more of the same...
Relatively little display failures with the N10+ fixed rate display even after over 2 years.
The resale value will be diminished and forget a trade-in. Rooting will destroy some of its core functionality, forever. Too many "I bricked my phone" threads here already... at least take a few months to start to get to know your stock new phone. Better have deep pockets if you decide to root this Samsung...
dr.ketan said:
Indeed we have no idea about "future of magisk" so don't rely on future verion of magisk
If you want to root, just look into current scenario and decide you want to root or not. As of now (On OneUI 4.0 on other devices) Samsung Pay & Samung Pass (and Knox thingy) doesn't work. Though it doen't mean everything other works, still you needs to patch multiple things like Samsung Health, Secure folder, Private sharing and may be more. Also many apps may not work but you needs to hide them with magisk (Still no guarantee it will work)
So my pesonal advice is to before jumping to rooting, read as much possible rooting and magisk thread. Rooting is one way, once you trip knox, it's for forever and some stuff never work again even after relocking bootloader.
Click to expand...
Click to collapse
dr.keaton you are my android guru!
Will you get your S22 next week?
What will you do with it? Will you root your device as soon as you have it?
On previous Note devices, I always waited for your first custom rom before I rooted my devices.
blackhawk said:
at least take a few months to start to get to know your stock new phone.
Click to expand...
Click to collapse
I just love the sexy hardware of this phone.
I have nausea from the original software-stack of this device.
I would never use it with factory software in everyday life.
If it would be possible I would wipe everything from it and would install some GNU/Linux distro on it.
s3axel said:
They do, at least on my recently rooted phones and for the apps I use.... Safetynet passes, Gpay ist working fine....
But this is the usual cat&mouse game , actually for the S22U my intention is to try going unrooted - we'll see how long this holds
Click to expand...
Click to collapse
It’s pretty annoying that you have to play such a cat & mouse game after you paid the hefty price of this device.
It is annoying how much Samsung, Google et al. are trying to restrict users freedom.
The kind of topic that makes me want to leave Android and go iPhone.
DoKaTSuYa said:
The kind of topic that makes me want to leave Android and go iPhone.
Click to expand...
Click to collapse
I can't see any reason why iphone/apple ecosystem would be better than Android.
I wish the Linux phone ecosystem was more mature.
Alibab said:
I just love the sexy hardware of this phone.
I have nausea from the original software-stack of this device.
I would never use it with factory software in everyday life.
If it would be possible I would wipe everything from it and would install some GNU/Linux distro on it.
Click to expand...
Click to collapse
Doesn't make much sense to buy this phone than if the native UI pukes you out.
The hardware is lacking; no SD card slot. A poorer form factor/layout than the N10+ as well and 1 mm thicker. No APTX HD and no 3.5 mm jack. Meh.
The most outrageous insult comes from Google Android itself; scoped storage is fully active. Nullifying some of the speed and efficiency; the old Intel/MS paradox reincarnates itself once again. With scoped storage come a slew of 3rd party app issues not create by Samsung at all.
Alibab said:
It’s pretty annoying that you have to play such a cat & mouse game after you paid the hefty price of this device.
It is annoying how much Samsung, Google et al. are trying to restrict users freedom.
Click to expand...
Click to collapse
Hmm, honestly speaking nobody is forcing anybody to unlock and root his device
From an IT security standpoint there is a reason for preventing modifications to a phone used by many for things like paying, storing sensitive data, having access to restricted data via specific apps, to corporate email accounts for BYOD etc etc
I am among the first to embrace tweaking options but in the end it all depends on what I use root access for: easy backup/restore of apps including user data, adblocking, UI +system tweaking, limiting of (for me) unnecessary system processes to optimize battery - all of this could easily be integrated by the manufacturers ....
In the end the good thing about Android is that you have a choice and maybe for rooting/tweaking Samsung isn't the best due to Knox and it's irreversibility....
Alibab said:
dr.keaton you are my android guru!
Will you get your S22 next week?
What will you do with it? Will you root your device as soon as you have it?
On previous Note devices, I always waited for your first custom rom before I rooted my devices.
Click to expand...
Click to collapse
Hopefully I am getting in couple of days.
First I will setup device and look if any hardware issue. If everything fine, will root same day.
dr.ketan said:
Hopefully I am getting in couple of days.
First I will setup device and look if any hardware issue. If everything fine, will root same day.
Click to expand...
Click to collapse
What tests do you use to check hardware issues?