Related
I've been "out of the loop" for quite some time and much has happened to Samsung devices since my last one (Samsung i9000). Basically it is the terror stories about this Knox security thing that mostly concern me and brought me here...
I mean I like this tablet, I trully do, but if I'm robbed by android's main advantage (modifying the thing to suit your needs) then I have absolutely no reason to choose this.
I have already read a a couple of stuff but they are all concerned about s4 and note 3. What about this tablet (the WiFi version), is it ... secured too? Also I'm a bit unclear of what this Knox thing achieves, at first it voids your warranty, second does not let you to flash certain ROMs, but I'm unclear from/on which ROMs this is enabled or even if merely rooting your device would enable this. I mean someone may not be interested in aosp ROMs but still love some "optimized stock + custom kernel" will this Knox thing prevent him even from that?
If this is proved an unmodifiable device I'd think twice for it's usefulness, android's only edge is its "modifiability" remove it and you buy sth 2nd or 3rd tier...
Stevethegreat said:
I've been "out of the loop" for quite some time and much has happened to Samsung devices since my last one (Samsung i9000). Basically it is the terror stories about this Knox security thing that mostly concern me and brought me here...
I mean I like this tablet, I trully do, but if I'm robbed by android's main advantage (modifying the thing to suit your needs) then I have absolutely no reason to choose this.
I have already read a a couple of stuff but they are all concerned about s4 and note 3. What about this tablet (the WiFi version), is it ... secured too? Also I'm a bit unclear of what this Knox thing achieves, at first it voids your warranty, second does not let you to flash certain ROMs, but I'm unclear from/on which ROMs this is enabled or even if merely rooting your device would enable this. I mean someone may not be interested in aosp ROMs but still love some "optimized stock + custom kernel" will this Knox thing prevent him even from that?
If this is proved an unmodifiable device I'd think twice for it's usefulness, android's only edge is its "modifiability" remove it and you buy sth 2nd or 3rd tier...
Click to expand...
Click to collapse
You can still root and modify things, however, Samsung has taken the stance that since Knox has been tripped you must've been running Custom firmware/apps that can "potentially" damage the hardware so all warranties (at least from Samsung) are void....
The other issue is Samsung are updating bootloaders when you install firmware updates. If you happen to get a new bootloader then you CAN'T go back to a lower version of firmware, period... Doing so generally results in bootloops or stuck on Samsung logo until you update to the newer firmware again...
The downside to this is the nandroid backup you took just before updating in case of a problem is rendered useless, and in the case of the Note 3, Kies no longer recognises the new bootloaders so emergency firmware restore doesn't work...
Knox also tries to deny any app root access, some messenger programs were denied access as their permissions required root access. SuperSu has been updated now to work with no problems, until Samsung decide to interfere again....
Knox is also a secure container for your data, it was meant for security agencies and such to have a secure passworded partition in the software that doesn't allow anyone but the person with the passcode to access it. This is disabled after rooting as the system has been modified and can no longer be deemed secure....
ultramag69 said:
You can still root and modify things, however, Samsung has taken the stance that since Knox has been tripped you must've been running Custom firmware/apps that can "potentially" damage the hardware so all warranties (at least from Samsung) are void....
The other issue is Samsung are updating bootloaders when you install firmware updates. If you happen to get a new bootloader then you CAN'T go back to a lower version of firmware, period... Doing so generally results in bootloops or stuck on Samsung logo until you update to the newer firmware again...
The downside to this is the nandroid backup you took just before updating in case of a problem is rendered useless, and in the case of the Note 3, Kies no longer recognises the new bootloaders so emergency firmware restore doesn't work...
Knox also tries to deny any app root access, some messenger programs were denied access as their permissions required root access. SuperSu has been updated now to work with no problems, until Samsung decide to interfere again....
Knox is also a secure container for your data, it was meant for security agencies and such to have a secure passworded partition in the software that doesn't allow anyone but the person with the passcode to access it. This is disabled after rooting as the system has been modified and can no longer be deemed secure....
Click to expand...
Click to collapse
So Knox is more about controlling your device than security as it is not optional (you cannot turn it off , right). Also about losing the warranty, well I was hoping to buy it from a reputable store in my country, even if Samsung voids my warranty can't the store itself honor it?
If not, if in fact merely rooting your device voids my warranty whatsoever than I'm most certain that this is not a device for me and I'm not sure for whom it is, I don't think android is a good os when decoupled from rooted apps (no xposed framework, no adblock, no virtual buttons, no gestures, no greenify), the experience is basically killed...
Even jail breaking your iPad doesn't kill the warranty as long as you install non jail broken iOS version on top... Bad Samsung, bad
OK, since I actually want to give this tablet a go I came up with a new idea. What if I trip up the Knox counter but then get back to stock firmware and *then* my tablet gets damaged? Would then my warranty be honored? The Knox counter can only tell you that it was tripped *once* but not what is/was happening at the time you got a defect.
Maybe my battery died, or more than a handful pixels died on me, all having nothing to do with me rooting my device at some point. Can my rooting still be grounds for samsung to dismiss my warranty? Because if so that is quite a scheme that Samsung runs.
Do any people had their warranty honored even though the Knox counter was tripped?
If you have a squaretrade warranty you should be fine with that excuse. However, Samsung will say that they cannot tell if the damaged occurred before or after the rooting occurred, thus denying you your warranty. Once the counter is tripped, from that point on the warranty is gone. My recommendation, get a squaretrade for 100 with a 2 year warranty and you will be fine.
Sent from my SM-P600 using Tapatalk
Probably been asked thousand times before but I want to get a samsung A7050FN specific answer to this query.
What features and functions would stop working once I unlock bootloader and root with the mentioned procedure on A70 thread?
This phone is near perfect for everyday driver except It needs some Titanium backup and viper4android along with few minor UI tweaks.
If some nice smartsian provide a list, I can peace fully proceed with rooting and bootloader unlocking
secure folder will stop working, also you will need to update your device with Odin.
Since Knox will be tripped, you won't be able to use "Knox features" like Secure Folder (there's 3rd party apps that do the same), Samsung Flox, Samsung Pay (if applicable), Samsung Pass, Samsung Health (there's a workaround for this one?). I've also read there could be problems with some apps like banking and Netflix. (Magisk hide root status feature is your friend) . If you're outside the EU tripping Knox will also void warranty.
xomikron said:
Since Knox will be tripped, you won't be able to use "Knox features" like Secure Folder (there's 3rd party apps that do the same), Samsung Flox, Samsung Pay (if applicable), Samsung Pass, Samsung Health (there's a workaround for this one?). I've also read there could be problems with some apps like banking and Netflix. (Magisk hide root status feature is your friend) . If you're outside the EU tripping Knox will also void warranty.
Click to expand...
Click to collapse
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
I rooted my A705MN. Samsung health does not work for me after tima change to 0. I read somewhere that you would have to modify the apk somehow. Never looked into it too much. You can read about it here https://forum.xda-developers.com/s10-plus/how-to/guide-samsung-health-root-device-t3946881
I am bummed that about the secure folder. I used it a lot with my unrooted S8. You can modify the build.prop to pass the SafetyNet check to be able to use banking and Netflix apps again.
Edit: here is another place to read https://forum.xda-developers.com/galaxy-s9/how-to/guide-s-health-knox-0x1-t3843483
fizzingbees said:
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
Click to expand...
Click to collapse
Samsung Pass uses biometrics to log-in and such, it won't work if the device is rooted. I don't know of any bypasses but I've found this https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977
I don't see why emoji and general camera features would stop working, they're not really security features, not that the stock camera is very useful. GCam is a better option for photography.
For now, I haven't rooted my device. From my understanding to enter a rooted state with Magisk you need to turn on your phone with a certain key combination, otherwise I don't think anything is displayed when the phone boots, why is that important?
banking? so like logging on to chase online app may not work if i unlock boot and root? that would be just dumb, i mean my nexus 6 was rooted and custom rom-ed and chase worked
xomikron said:
Samsung Pass uses biometrics to log-in and such, it won't work if the device is rooted. I don't know of any bypasses but I've found this https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977
I don't see why emoji and general camera features would stop working, they're not really security features, not that the stock camera is very useful. GCam is a better option for photography.
For now, I haven't rooted my device. From my understanding to enter a rooted state with Magisk you need to turn on your phone with a certain key combination, otherwise I don't think anything is displayed when the phone boots, why is that important?
Click to expand...
Click to collapse
Our Samsung A70 is very finicky with root and unlocked bootloader. And the rooting method we use is not so very official and stable for us.
So we need to use a certain key combination to keep root and magisk app when rebooting phone.
You mentioned gcam. Which version and config file are you using?
leo5111 said:
banking? so like logging on to chase online app may not work if i unlock boot and root? that would be just dumb, i mean my nexus 6 was rooted and custom rom-ed and chase worked
Click to expand...
Click to collapse
Actually its a security feature.
Many banking and enterprise applications don't work if your bootloader is compromised and your system rooted. They believe that by rooting and gaining administrative status, any hacker can bypass banking app security thereby compromising consumer safety
cealaska said:
I rooted my A705MN. Samsung health does not work for me after tima change to 0. I read somewhere that you would have to modify the apk somehow. Never looked into it too much. You can read about it here https://forum.xda-developers.com/s10-plus/how-to/guide-samsung-health-root-device-t3946881
I am bummed that about the secure folder. I used it a lot with my unrooted S8. You can modify the build.prop to pass the SafetyNet check to be able to use banking and Netflix apps again.
Edit: here is another place to read https://forum.xda-developers.com/galaxy-s9/how-to/guide-s-health-knox-0x1-t3843483
Click to expand...
Click to collapse
It's not like a70 has heart rate sensor and oximeter that I will. Be mad about Samsung health.
Still Samsung makes very stupid decision sometimes.
back to previous statement i NEVER have rooted my phone and then Chase app didnt work, so trying to see before bothering to try and root...EDIT...anyone here with rooted a70 and chase mobile app does it work? that and paypal
fizzingbees said:
It's not like a70 has heart rate sensor and oximeter that I will. Be mad about Samsung health.
Still Samsung makes very stupid decision sometimes.
Click to expand...
Click to collapse
I never really used Samsung Health with my unrooted S8. Fingerprint reader does not work to unlock my rooted A70 on Q (Android 10). It accepts the fingerprint but does not unlock the phone. It goes into a loop where it locks the phone again even I press the fingerprint sensor. I hate the ultrasonic reader lol. Does not work with screen protectors to prevent it from being scratched.
Can't use private mode in Samsung Internet anymore A lot of the features from Samsung seems to be disabled after tripping Knox. I used to love Samsung but with rooting now is a pain in the neck. The build.prop is different than 9 which sucks because I liked "overclocking" kind of making the CPU use all cores, it is not there anymore in Q. I am not sure that the Net improvements hacks for the build prop works anymore. Internet connection does not seem to be as fast for me as 9 was. Edit: I am not sure why the hell we can't use them because it erases the phone when we unlock the bootloader. Even if we re-flash stock they will not work because efuse is already tripped.
back to previous statement i NEVER have rooted my phone and then Chase app didnt work, so trying to see before bothering to try and root...EDIT...anyone here with rooted a70 and chase mobile app does it work? that and paypal
Click to expand...
Click to collapse
I am sorry I do not use those apps. You will have to edit your build.prop to get it to pass the SafetyCheck most likely. If Chase still does not work for you unrooted try contact their support and see if they can help you make it work. I am not liking rooted Q as much as rooted 9 was.
Okay so it means that t rooting and unlocking bootloader leads to Samsung secure folder, Samsung health, Samsung pay, secure login, banking apps and Netflix not working anymore.
Moreover specifically for A70, rebooting phone require specific key combination.
What about boot screen? Does it show any new text after rooting?
My note 4 after rooting shows kernal booting system or kernal booting recovery which is indication thst device has been tempered with.
I have a problem with the making phone calls after rooting. The sounds leak out as if it's on speaker (when it's not) and when on speaker it makes a very shape echo in the back ground.
P.S. havoc os
M.Sam90 said:
I have a problem with the making phone calls after rooting. The sounds leak out as if it's on speaker (when it's not) and when on speaker it makes a very shape echo in the back ground.
P.S. havoc os
Click to expand...
Click to collapse
Turn off voice enhancement in call settings. Or noise reduction in call settings
These settings are known to cause echo or static noise issues during call.
Also try turning off any sound mods you may have done after rooting
Report this issue at hovac os thread. Maybe it's a known issue with that Rom
Headset and sound issues
fizzingbees said:
Turn off voice enhancement in call settings. Or noise reduction in call settings
These settings are known to cause echo or static noise issues during call.
Also try turning off any sound mods you may have done after rooting
Report this issue at hovac os thread. Maybe it's a known issue with that Rom
Click to expand...
Click to collapse
Thanks for the reply but the issues is still the same any other adjustments to recommend ?
fizzingbees said:
Don't care about secure folder or Samsung pay or warranty or loosing ability to update OTA. I can use odin for that
Can samsung pass and health be bypassed via the technique of changing ro.xxxx.tima= 1 to 0 in build prop file?
Don't use Netflix so don't care. Nor use any banking apps
Would fingerprint, face unlock, ar emoji and other camera features and Samsung themes kepp working?
Once you are rooted and your bootloader is unlocked does your boot screen changes to show tripped knox etc?
Click to expand...
Click to collapse
fizzingbees said:
Our Samsung A70 is very finicky with root and unlocked bootloader. And the rooting method we use is not so very official and stable for us.
So we need to use a certain key combination to keep root and magisk app when rebooting phone.
You mentioned gcam. Which version and config file are you using?
Click to expand...
Click to collapse
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
xomikron said:
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
Click to expand...
Click to collapse
Can you kindly post direct link to gcam apk here along with config file as attachment
M.Sam90 said:
Thanks for the reply but the issues is still the same any other adjustments to recommend ?
Click to expand...
Click to collapse
Ask this question in havoc OS thread.
They can help you better than us
xomikron said:
Sorry for the late reply. I'm using GCam version 7.3.018 by Urnx05 (v1.4) with the config file by dotsx, you can check the file in Telegram by joining the group from this link.
Click to expand...
Click to collapse
I found your version but the auxiliary cameras cause the app to crash.
How do you fix this. Any help
Can i modify my g988u from verizon in anyway? And if so how? Im new to this kind of stuff. I know i should probably leave verizon
You might be able to disable some packages with ADB , but beyond that, if your phone has been receiving OTA updates, it's likely hopeless. Substantial customization requires root, and that is precluded by locked bootloaders. There are paid services that can unlock bootloaders in S20s with older software, but my understanding is this isn't an option for devices with newer software
I actually just switched to Verizon, entirely motivated by AT&T's hostiliity towards most unlocked devices (that they don't sell). So, if you leave, who are you going to go to? T-Mobile is the most permissive of the big 3, but tends to lag in infrastructure.
Right didnt even look into that. Probably going to stay with verizon now that ya said that lol. Just curious What do people get out of from rooting their phone? I want to learn how and dont know where to start.
CainD5 said:
Right didnt even look into that. Probably going to stay with verizon now that ya said that lol. Just curious What do people get out of from rooting their phone? I want to learn how and dont know where to start.
Click to expand...
Click to collapse
A lot. Android phones have come a long way in past decade and change that they have been available, but root access, which is typically associated with at least an unlocked bootloader and possibly also a custom ROM, remains the single most powerful customization tool. A short non-exhaustive list of what you can do:
Use Magisk (See Magisk Module Repo for ideas of capabilties).
Use EdXposed or LSPosed (See Xposed Module Repo for ideas of capabilities).
Install a custom kernel (natively mount CIFS/NFS filesystems, overclock your device, and all sorts of other options).
Permanently debloat your ROM (survives hard reset).
Enjoy the best ad blocking experience.
View/backup/edit private application data.
There are also downsides to root, such as tripping the warranty void bit (and disabling Knox-related functionality like Samsung Pay, likely losing filesystem encryption, and greatly increasing your odds of a malware infestation. That said, the XDA site is largely powered by the modding/root access community, so those risks aren't discussed much.
https://www.xda-developers.com/dirty-pipe-root-demo-samsung-galaxy-s22-google-pixel-6-pro/
March 15, 2022 7:40am Comment Skanda Hazarika
PSA: Dirty Pipe, the Linux kernel root vulnerability, can be abused on the Samsung Galaxy S22 and Google Pixel 6 Pro
What happens when a Linux privilege-escalation vulnerability that also affects Android gets disclosed publicly? You got it! Security researchers and Android enthusiasts around the world try to take advantage of the newly found problem to create an exploit, which can be used to gain advanced access to your device (such as root or the ability to flash custom images). On the other hand, device makers and a few determined third-party developers quickly take the responsibility to patch the backdoor as soon as possible.
This is exactly what happened to CVE-2022-0847, a vulnerability dubbed “Dirty Pipe” in Linux kernel version 5.8 and later. We talked about the exploit in detail last week but didn’t explicitly cover the potential abusing scenarios on Android. Now, XDA Member Fire30 has demonstrated an exploit implementation around the kernel flaw that can give the attacker a root shell on the Samsung Galaxy S22 and the Google Pixel 6 Pro.
The key point here is that you don’t need any kind of unlocking or other trickery to make it work – the Dirty Pipe exploit allows the attacker to gain root-level access on the target device through a reverse shell via a specially crafted rogue app. At the time of writing, flagships like the Google Pixel 6 Pro and the Samsung Galaxy S22 are vulnerable to the attack vector even on their latest software releases, which shows the exploit’s potential. Since it can also set SELinux to permissive, there is virtually no hurdle against unauthorized control over the device.
From the perspective of the Android modding scene, Dirty Pipe might be useful to gain temporary root access on otherwise difficult-to-root Android smartphones, e.g., some regional Snapdragon variants of the Samsung Galaxy flagships. However, the window won’t last long as the vulnerability has already been patched in the mainline Linux kernel, and OEMs will probably roll out the fix as part of the upcoming monthly security updates. Nonetheless, stay away from installing apps from random sources for the time being to protect yourself. In the meantime, we expect that Google will push an update to the Play Protect to prevent the vulnerability from being exploited via rogue apps.
Source: Fire30 on Twitter
Via: Mishaal Rahman
Click to expand...
Click to collapse
This isn't necessarily bad news if the exploit is used non-maliciously. Could be beneficial for Verizon customers looking for a way to gain root.
westhaking said:
This isn't necessarily bad news if the exploit is used non-maliciously. Could be beneficial for Verizon customers looking for a way to gain root.
Click to expand...
Click to collapse
Could, yes. I'll remain pessimistic that it'll actually happen, and of course, it'll take someone willing to actually do the work. A very limited time to do it doesn't help unless someone with a spare Verizon device keeps it off the network/internet until something is implemented.
westhaking said:
This isn't necessarily bad news if the exploit is used non-maliciously. Could be beneficial for Verizon customers looking for a way to gain root.
Click to expand...
Click to collapse
I was just reading about this & that exact thought came to mind. The root access gained seems to be temporary, but if you can write to usually read only file system, could you not theoretically write a Magisk boot image (using dd, or in Magisk Manager itself?) or even toggle the OEM unlock switch via a SU shell command unlock the phone?
I'm not very well versed on how the mechanics behind OEM unlock switch in developer settings works & or how Verizon locks these phones down (UK based), but I would assume that it could be useful to help find a exploit for phones running any pre-April 22 update.
Edit: from my limited knowledge, can you not sideload a earlier OTA on Verizon devices? I know you could do so with Pixel 3 and earlier, but I haven't been following it too closely with later devices.
DanielF50 said:
or even toggle the OEM unlock switch via a SU shell command unlock the phone?
Click to expand...
Click to collapse
I've never heard of a shell command that could toggle the OEM unlock. That doesn't mean it hasn't existed, but I doubt it, otherwise, I would think on all the Verizon devices I used to have, and just root threads in general I should remember anyone making the suggestion, even if it required temporary root first.
DanielF50 said:
Edit: from my limited knowledge, can you not sideload a earlier OTA on Verizon devices? I know you could do so with Pixel 3 and earlier, but I haven't been following it too closely with later devices.
Click to expand...
Click to collapse
I was under the impression that all phones with the bootloader locked that you could never, ever downgrade via any method. Also, OTAs generally use deltas/differencing to patch known good files of version A to version B, and B to C, so applying a version B OTA to a device that's on version C would fail because the files on the device are the wrong version.
Like (let version A be represented with the value 1, B with 4, and C with 9):
Device is on version B, so "4".
OTA to go from B to C comes.
OTA says is device file "4"?
Yes! Add 5 to the file, it's now "9".
and then
Device is on version C, so "9".
Try to put the B to C OTA on the device.
OTA says is device file "4"?
No! It's "9", quit OTA process.
This might be simplified, and anyone correct me if I'm wrong, but this has definitely been the case some and I believe almost all, if not all, the time. The OTA files can be smaller that way because they don't contain replacement files. They only contain what the difference is between the old file and the new, which is usually much smaller than the entire file.
(Please don't vote before reading the whole thread!)
I have recently acquired a second hand A52s, and I'm looking into rooting it as well as it's drawbacks.
The phone's Knox Warrany Bit is not triggered yet, so I'm looking for some advice on wheter I should cross the rooting Rubicon, or if going with an unrooted phone is sufficient for my threat model.
My percieved threats are as follows:
- Security: I want total security should anyone get a hold of my phone, even if they have advanced tools. I know in older android versions the whole partition could be encrypted so that no-one could access any of the data without the password if the phone was turned off. However in the current Android 13 I haven't found a way to do this.
- Privacy: I want some control over what information corporations are getting about me. I wouldn't consider going as far as to disable Google Play Services, but some level of control would be preferable.
- Anonymity: I want to be able to hide my identity occasionally. Tor will mostly take care of my needs, but having multiple cloned social media apps is desired too.
- Usability: I want to get rid of the useless bloatware Samsung and Google include in the stock android. Extending battery life would be preferable too. I also have a Samsung Galaxy Watch5 and I would like to use it's ECG feature.
From this arrises the question: Is rooting what I'm looking for? Will rooting negatively impact my security should anyone take my phone and plug it into a computer (can the bootloader be re-locked after rooting)? Are there any other drawbacks specific to this model that I should be aware of (camera, Samsung vendor apps, etc)?
cluckduck said:
- Security: I want total security should anyone get a hold of my phone, even if they have advanced tools. I know in older android versions the whole partition could be encrypted so that no-one could access any of the data without the password if the phone was turned off. However in the current Android 13 I haven't found a way to do this.
Click to expand...
Click to collapse
Recent Android versions automatically encrypt your data partition, so doing it manually is kinda not needed.
cluckduck said:
- Privacy: I want some control over what information corporations are getting about me. I wouldn't consider going as far as to disable Google Play Services, but some level of control would be preferable.
Click to expand...
Click to collapse
The latest Android version (13) has been getting better at limiting what access your apps get like location. I think by default all apps have no permissions until you manually give it to them so I think you should be good here.
cluckduck said:
- Anonymity: I want to be able to hide my identity occasionally. Tor will mostly take care of my needs, but having multiple cloned social media apps is desired too.
Click to expand...
Click to collapse
Secure Folder is a good option to do this. It sandboxes an environment that has all accounts (including Google's) unlinked so I think this is a good option
cluckduck said:
- Usability: I want to get rid of the useless bloatware Samsung and Google include in the stock android. Extending battery life would be preferable too. I also have a Samsung Galaxy Watch5 and I would like to use it's ECG feature.
Click to expand...
Click to collapse
You can debloat with adb commands without an issue
cluckduck said:
From this arrises the question: Is rooting what I'm looking for? Will rooting negatively impact my security should anyone take my phone and plug it into a computer (can the bootloader be re-locked after rooting)? Are there any other drawbacks specific to this model that I should be aware of (camera, Samsung vendor apps, etc)?
Click to expand...
Click to collapse
You're covered with stock, no need to root imo.
What root apps are you going to use? I just root my alt phone for the sake of adblocking and revanced.
chocowilliam said:
What root apps are you going to use? I just root my alt phone for the sake of adblocking and revanced.
Click to expand...
Click to collapse
I hadn't considered that those aren't an option without a rooted phone. I might consider rooting just for these.
No root ! Benefits are much under android native functionality at least on latest android OS . More then that is considerably sure to brake , bootloop , freeze etc the system , lack of system updates , loose garanty , not mentioning the bank payments which are blocked by the safety permissions . Long time ago on android 5...6...7 root was for fun and improvement the system apk and battery but now I don't see the point .... Regarding the tracking features , you can minimize this but not eliminate cause of Google policy
muppetz said:
No root ! Benefits are much under android native functionality at least on latest android OS . More then that is considerably sure to brake , bootloop , freeze etc the system , lack of system updates , loose garanty , not mentioning the bank payments which are blocked by the safety permissions . Long time ago on android 5...6...7 root was for fun and improvement the system apk and battery but now I don't see the point .... Regarding the tracking features , you can minimize this but not eliminate cause of Google policy
Click to expand...
Click to collapse
Are you saying stock Android 13 won't receive OTA updates if it's rooted?
cluckduck said:
Are you saying stock Android 13 won't receive OTA updates if it's rooted?
Click to expand...
Click to collapse
Is not a rule but certainly there are some problems with manually update especially under major updates where you need to flash stock.img , then stock.img patched and so on . Somehow Magisk is not perfect , modules installed also so all the process will lead to a broken phone (maybe) .