For mods: please move this discussion to the section where it belongs to, if this isn't the section for this
Chainfire's supersu was the best super user app and binary but there is no way to flash it without having a TWRP for these new devices like Samsung galaxy M02 SM-M022G. Chainfire's CF Auto root is also not ported for these devices. Even if i flash that out dated supersu.zip using TWRP on this device, i don't think it will work. So it's painful.
When it comes to magisk systemless root, it is just something that named as a root method or app but it's not. Magisk is just a app for me because that magisk never let us to modify system files or flash things into the system. So it's not a root access tool. That's why i call it useless than saying systemless.
Those old days with chainfire's super su was the greatest. But today, It is sad to say this there is no such perfect method to gain root access as those old days. I'm tired of this. I think we should be together and make some new rooting method for these new devices to gain full root access through it.
Thanks to those who reading this.
I don't have a current Samsung device, though I have used one in the distant past. Magisk IS a root method. The issue you are encountering is the protections put in place for the system partitions. I'm fairly sure Samsung does the same thing as Google does for its Pixel devices in that the system partitions are not only set to read-only, but are also dynamically resized so as to prevent read-only from ever being removed (search for "dedup" flag for more details).
Chainfire's SuperSU stopped being updated because he no longer owned the software. It was sold to a Chinese company that essentially screwed the entire community over with their antics. It wouldn't have mattered anyway, as all the old Superuser apps injected a modified su binary into the system, which cannot be done on newer devices (see above for why). If Chainfire had continued updating SuperSU the app would have eventually had to adopt a systemless root in order to continue being functional.
I won't disagree with your opinion that there is no perfect method for root access, but it isn't because of us, but because of Google ramping up the security of Android. I do agree that there needs to be alternatives to root other than Magisk, as if something catastrophic happens to Magisk itself root will still be possible. However any root solution proposed from this point on will not be able to modify the system, and that is simply something you will have to get used to.
P. S. This really isn't about a Samsung phone so perhaps it should be moved into the Magisk forum, but that's a moderator's call.
I won't buy their android devices anymore.
Strephon Alkhalikoi said:
I don't have a current Samsung device, though I have used one in the distant past. Magisk IS a root method. The issue you are encountering is the protections put in place for the system partitions. I'm fairly sure Samsung does the same thing as Google does for its Pixel devices in that the system partitions are not only set to read-only, but are also dynamically resized so as to prevent read-only from ever being removed (search for "dedup" flag for more details).
Chainfire's SuperSU stopped being updated because he no longer owned the software. It was sold to a Chinese company that essentially screwed the entire community over with their antics. It wouldn't have mattered anyway, as all the old Superuser apps injected a modified su binary into the system, which cannot be done on newer devices (see above for why). If Chainfire had continued updating SuperSU the app would have eventually had to adopt a systemless root in order to continue being functional.
I won't disagree with your opinion that there is no perfect method for root access, but it isn't because of us, but because of Google ramping up the security of Android. I do agree that there needs to be alternatives to root other than Magisk, as if something catastrophic happens to Magisk itself root will still be possible. However any root solution proposed from this point on will not be able to modify the system, and that is simply something you will have to get used to.
P. S. This really isn't about a Samsung phone so perhaps it should be moved into the Magisk forum, but that's a moderator's call.
Click to expand...
Click to collapse
Yes. that's the truth.
Related
I need to actually write it when I get to my desktop in the next coue days.
GN2Rabbit said:
Please read entire post before trying this. You have been warned.
This is a guide on how to root your phone without tripping the modified status on Android or breaking your camera. A lot of people want to be able to have root without tripping the modified status so you can still use over the air updates. This is going to be a step by step guide on how to do this. Please keep in mind that you should only do this if you tend to have a set list of apps that you use and do not download applications from developers who are not well known or do not have a lot of apps out there or that might be a security risk.
Note: This requires factory everything. Also make sure you are starting from a fresh factory image. If you have already installed the exploit and patched it will not work.
1. First thing you need to do is download the root exploit APK.
2. Then run the exploit however do not apply any of the patches at all. If you do you will set off the modified status.
3. Do not do any of the following : install busybox, use the multi window or any other modification to the UI, etc. These will trip modified status. The modified status happens when permissions get changed for certain system files and folders.
What I would call this is limited root. You can use things like CPU master, titanium backup, and battery saver. Things that need root privilege in order to function correctly. However you cannot use things that will modify the system in any way as described above. If you do not care about modified status or OTA updates then using kies or Odin the only steps you need to follow are steps 1&2 with a fresh factory image.
This had been tested on my personal device and I have been able to replicate it many times but I do not guarantee that it will work on your device. This guide only applies to the note 2 on T-Mobile using the update from December 19th. If it works with a different device please let me know via PM.
Sent from my SGH-T889
Click to expand...
Click to collapse
Sorry dude, this is pointless. You do not name specifics (exynos abuse is the apk) and give no credit to the original exploit's founder, our very own Chainfire. I can appreciate your effort, but there is plenty of guides on here and the method you named does trip the flash counter.
I'm sure I'm like the last person here to understand this but why do we need to FLASH xposed? Can't we just replace system files, change the permissions, and reboot? When I install xposed on my other devices, I've never had to FLASH it, it just writes to the system partition. However I've seen some people blame xposed for not being able to fully "unroot" their devices so I haven't even tried it myself yet. Seems like the thinking was that it did something to other partitions either directly or indirectly to trip a security flag, I think more specifically it was the /persist partition they were talking about. Anyway, sorry I'm sure everyone else here must already know the reason behind this, but in all my reading through posts I've not yet found it. Thanks!
Because a lot of changed since 4.4 in android and currently the framework has to be flashed (or you can place manually) separately from the xposed installer .apk.
Regarding your unroot part, I never experienced that, flashing back stock on the OPO and S6 returned them completely to stock.
petermg said:
I'm sure I'm like the last person here to understand this but why do we need to FLASH xposed? Can't we just replace system files, change the permissions, and reboot? When I install xposed on my other devices, I've never had to FLASH it, it just writes to the system partition. However I've seen some people blame xposed for not being able to fully "unroot" their devices so I haven't even tried it myself yet. Seems like the thinking was that it did something to other partitions either directly or indirectly to trip a security flag, I think more specifically it was the /persist partition they were talking about. Anyway, sorry I'm sure everyone else here must already know the reason behind this, but in all my reading through posts I've not yet found it. Thanks!
Click to expand...
Click to collapse
No, I for one don't know the reason. Would you be so kind and provide a link to where the issue with Xposed and root is described? AFAIK, Xposed shouldn't prevent an unrooting process unless you've used some shady a*s app or toolkit to root. I unrooted many devices, many times running Xposed I've previously rooted with SuperSu without issues.
nitrous² said:
No, I for one don't know the reason. Would you be so kind and provide a link to where the issue with Xposed and root is described? AFAIK, Xposed shouldn't prevent an unrooting process unless you've used some shady a*s app or toolkit to root. I unrooted many devices, many times running Xposed I've previously rooted with SuperSu without issues.
Click to expand...
Click to collapse
No, it shouldn't but a lot of people who are having the "device suspected of rooting" when trying to update after going back to stock have been speculating it's related to xposed, HOWEVER!!! It is in the forums for the devices that do NOT have a KDZ file to flash. For example, the ATT variant. ONE of the threads is here where it is speculated. I don't think this matters for those who can just flash a KDZ file onto their device. Sadly, I have no KDZ/TOT file for my ATT H810 G4
I need some help and I've looked all over but the information is fragmented and there is too many unfamiliar acronyms used which make it incredibly difficult for some like myself to catch up. So for the benefit of others who may be new I wanted to get some additional guidance.
I got the Pixel XL Google Version
Objectives:
1. Root with the ability to hide root so other apps will work
2. Native Mobile Hotspot
3. The ability to easily receive android updates without having to reflash etc..
4. Stay close to stock if possible, but willing to explore other options as long as security is trusted, and has good
compatibility.
5. Security is a concern, I tried a rom in the past with a Galaxy S4 and swear it had a backdoor installed in the rom.
What do you guys recommend? And how do I go about doing it?
Thank you!
If security is truly a concern you will not unlock your bootloader and root your phone.
Otherwise it all depends on which version phone you have, Verizon or Google?
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
mikaole said:
1. You need magisk root for that.
3. No updates when you are rooted
4.5. Never heard of any custom rom with a backdoor. That's absolutely bull****. More likely it was an app you installed.
Unlocked bootloader is a security issue, so better to stay on full stock.
Root is a big security issue so better stay on full stock.
I have the Pixel XL - Google Version
Jokes aside the only security issue is your phone gets stolen or you install apps outside playstore.
If you stay encrypted and use a hard pattern with fingerprint you are fine and there is always the way to delete your phone when it gets stolen.
Click to expand...
Click to collapse
My point about security really was that it's quite possible a ROM could have a backdoor. That a side..
Root is not a big security issue for me as long as the rom is trusted etc..
Shouldn't I be able to turn root off then be able to update and turn it back on again?
jadensmith said:
1. Root with the ability to hide root so other apps will work
Click to expand...
Click to collapse
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
3. The ability to easily receive android updates without having to reflash etc.
Click to expand...
Click to collapse
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
jadensmith said:
Shouldn't I be able to turn root off then be able to update and turn it back on again?
Click to expand...
Click to collapse
While reading I got the impression that I might be able to uninstall SuperSU and use the OTA update, but that didn't work with SuperSU the times I tried it, so I presume something SuperSU changed or something I did with root must have caused the update to fail. I haven't read the Magisk threads as much, yet I've seen that other SuperSU users also indicate that OTA updates no longer worked for them after rooting the phone.
alluringreality said:
It's possible to root to one slot with SuperSU while the other slot remains unrooted, and then the phone can be switched between slots with TWRP or fastboot commands. Kernels have been posted with safetynet patches, to hide that the bootloader is unlocked, but I'm not sure if any are available with the software version on my phone's current slot. As noted, Magisk can also hide root and that the bootloader is unlocked, so it's probably less hassle than trying to root and hide using SuperSU.
FlashFire can use the OTA to update and stay rooted with SuperSU. The past couple months I've used FlashFire to update my phone, and it seems quicker and easier than the sideloading and reinstalling process I had been using. I'm not aware of anything similar to FlashFire for Magisk users, so to me it seems like you would have to decide if 1 or 3 is more personally important.
That didn't work with SuperSU the times I tried it, so I presumed that something I did with root must have caused the update to fail to install.
Click to expand...
Click to collapse
Wow thanks for the great reply! It's so refreshing!
What do you mean by root one slot?
The phone has two "slots" for Android. The basic idea is that you have two copies of Android on the phone that share the same user data. On a stock phone it's intended to allow for less noticeable updates, and it also can allow the phone to fall back to the previous software version if something goes wrong with an update. On the May update my phone did automatically switch between slots, due to what is discussed in the second link below. The first link below gives some information and additional links to discussion about the slots on these phones.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Is it possible to keep stock or near stock and just have root with the ability to hide root, and hotspot?
That's all I really need. What would be the best way to to do this?
Hey is tethering possible without root on oreo? Verizon grandfathered plan, get error when I do it on stock.
thanks
Nblufire12 said:
Hey is tethering possible without root on oreo? Verizon grandfathered plan, get error when I do it on stock.
thanks
Click to expand...
Click to collapse
I don't believe so. (Other than paying for the addition of tethering to your plan) At one time there was a rootless "method" that required removal/insertion of the SIM card and specific timing of launching the hotspot - but not sure if those work anymore. With root, I believe the current method requires editing the build.prop file. That's what I'm currently using and it is working fine - but I am rooted. Good luck.
S
sb1893 said:
I don't believe so. (Other than paying for the addition of tethering to your plan) At one time there was a rootless "method" that required removal/insertion of the SIM card and specific timing of launching the hotspot - but not sure if those work anymore. With root, I believe the current method requires editing the build.prop file. That's what I'm currently using and it is working fine - but I am rooted. Good luck.
S
Click to expand...
Click to collapse
do you still receive OTA's with root??
I usually root and ROM on all my previous phones but this pixel is so damn smooth i figured just KISS
Nblufire12 said:
do you still receive OTA's with root??
I usually root and ROM on all my previous phones but this pixel is so damn smooth i figured just KISS
Click to expand...
Click to collapse
OTA's attempted within android will fail with any modifications to system even "systemless" root. However, it is very easy to simply sideload the OTA that is readily available from Google. This bypasses those "checks" that prevent the OTA from installing from within Android. Essentially, you are just manually installing the OTA via sideloading from within ADB. Entire process is very simple and straightforward. I've been updating my Pixel XL monthly since last December using this method. I did flash factory image (removing -w from flashall.bat) for the upgrade to Oreo. After upgrading via either method, you do need to reinstall root and any mods - but this is fairly quick as well. Other than root, suhide (to allow android pay to work) and the build.prop edit to enable tethering - I am completely stock.
sb1893 said:
OTA's attempted within android will fail with any modifications to system even "systemless" root. However, it is very easy to simply sideload the OTA that is readily available from Google. This bypasses those "checks" that prevent the OTA from installing from within Android. Essentially, you are just manually installing the OTA via sideloading from within ADB. Entire process is very simple and straightforward. I've been updating my Pixel XL monthly since last December using this method. I did flash factory image (removing -w from flashall.bat) for the upgrade to Oreo. After upgrading via either method, you do need to reinstall root and any mods - but this is fairly quick as well. Other than root, suhide (to allow android pay to work) and the build.prop edit to enable tethering - I am completely stock.
Click to expand...
Click to collapse
is your build.prop edit still working on oreo for og pixel xl 1?
Nblufire12 said:
is your build.prop edit still working on oreo for og pixel xl 1?
Click to expand...
Click to collapse
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
sb1893 said:
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
Click to expand...
Click to collapse
thanks so much for this detailed post! So basically, root my phone, install magisk, install the tether module, profit?!
sb1893 said:
With the January Security update on 8.1, SuperSu 2.82 SR5 / suhide failed to install. It appears that SuperSu requires some changes to allow it to continue working on Jan 2018 Security Update and for whatever reason that work hasn't been completed yet and it is unclear if it is planned to occur. (Chainfire has retired from SuperSu development. And the company he sold the SuperSu and related assets to has not been very communicative on their plans to support going forward.) So based on that, I pulled the trigger to migrate from SuperSu to Magisk/MagiskHide. It was a fairly painless process and I have been pleased with Magisk thus far. I am still able to use Android Pay and hide root as needed from other apps. I am not able to directly edit build.prop (at least haven't figured out how), but Magisk has a tether module which essentially inserts settings contained in build.prop at boot-time and that allows the net.tethering.noprovisioning=true setting to be added and I can confirm that my tethering does work using this method. (That is my layman's understanding of what that module does - apologies if it isn't technically accurate).
Good luck!
S
Click to expand...
Click to collapse
I've been considering switching to the Pixel XL or the 2XL and this is a critical factor for me. From what I gathered from the 2XL forum, this wasn't working. I'm going to see if I can track down if the same Magisk tether module exists for the 2XL. If anyone knows ahead of time, I'd like to know.
Nblufire12 said:
thanks so much for this detailed post! So basically, root my phone, install magisk, install the tether module, profit?!
Click to expand...
Click to collapse
Yes. Installing magisk will root your phone and then you can install the tether module. Good luck!
sb1893 said:
Yes. Installing magisk will root your phone and then you can install the tether module. Good luck!
Click to expand...
Click to collapse
ah ok so we dont have to root before! Just install the apk and itll do all of it for us?!
Nblufire12 said:
ah ok so we dont have to root before! Just install the apk and itll do all of it for us?!
Click to expand...
Click to collapse
I'd recommend following one of the many guides found on XDA. Here is the one I used to get up and running on magisk...you will need to determine which portions of the guide are relevant to your situation and needs.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Good luck!
S
I switched from SuperSU to Magisk and it seems that Magisk is way more stable. I kept losing root with SuperSU. I am also able to edit my build.prop with root explorer.
scoobysnack said:
I switched from SuperSU to Magisk and it seems that Magisk is way more stable. I kept losing root with SuperSU. I am also able to edit my build.prop with root explorer.
Click to expand...
Click to collapse
Interesting. I am unable to edit build.prop with Root Explorer (which does have Root Privs). Whenever I open the file for edit in Text Editor within Root Explorer, it allows me to edit the file, but when I "Save Changes and Exit" or "Save Changes" and then exit...those changes are not retained. The timestamp on the build.prop file is unaltered as is the file size. I wonder what the difference is that allows you to edit your build.prop but prevents me from changing mine...I have poked around on the forums and the magisk threads and haven't been able to figure it out. I stopped researching when I discovered the ability to insert those settings at boot time via the magisk modules and decided that was a viable solution (maybe better as it leaves build.prop stock and unchanged.)
Thanks,
S
I click "Save Changes" then I click "Save and Exit" it will say the original file is name .bak
Hello,
Yesterday, I successfully rooted my Samsung Galaxy S10+. But since I still had some questions about it, I went on and posted a thread here. User Spaceminer then pointed out that my original post was in the wrong subforum and linked me here. Naturally, I looked at some of the most popular posts in hopes to find answers to my questions. But what I found confused me more than it gave me answers.
Since 2014 with the Samsung Galaxy S5 I got used to rooting in order to disable bloatware, protect my data and customize my phone. I continued doing that with the S8+ until I recently got my hands on the S10. Now, my main reason for rooting are still the same; I want disable (not necessarily uninstall) bloatware, protect my privacy and customize my phone (such as changing the background of the dial when calling someone). But that thread made me wonder if it is even essential to root. I also found a similar post on reddit and most answers seem to agree that it is not necessary to root your phones.
Now, my situation is a bit different. For one, I already rooted my phone. Second, I don't care about warranty nor custom ROMs. But I do want to install a banking app. Also, it is a bit cumbersome to not only have to manually update your phone with every update but the booting requirements with the warning screen are also a bit annoying. So, my question is the following:
What are the advantages of rooting that are not possible without? I have 3 main concerns: Bloatware, Privacy and Customization.
The reason why I posted this in a separate threat is that I was not able to come to a definitive conclusion on my own and most discussion threads are over a year old. By now, the whole process of rooting and what is possible changed since then, so I want to get a more recent insight. I hope you can help me out.
With kind regards,
DasMalzbier
Tbh root is not needed, unless you want to use a custom rom. Most things are already in the android now.
Calyx os not make for samsung Galaxy series and 12 update also comes this year so i think rooting is unnecessary for s10 series
Root is 100%, absolutely necessary for using the phone. I cannot use any phone without it. Critical root-only capabilities:
full system backups (in twrp)
titanium backup
disable updates permanently (update ONLY when want to)
app freezers (app quarantine)
disable/remove bloatware
disable google play services/google play
automate/tasker
cf lumen
adblockers
wifi tether
busybox
superuser
ssh tunnel
update android to later version / install custom roms
optimize system
button mapper
custom theming / substratum
nav gestures
tidypanel
xposed
root explorer
app privacy customizations
3c all-in-one toolbox
more
Without root, the phone is unusable to me. I will never buy any phone without root capability. I am willing to go to different carriers just to get root on the device, or go to different manufacturers if root is blocked. For example, I will never buy a huawei device - they are locked.
I would like to say yes but I can't. the stock apps are very well designed.
The biggest concern is that custom Roms are released faster than modded apps.
For example I tried about ten GCAMs and all of them have a bug... and it becomes more complicated with Exynos.
OpenGcam is not worth samsung app.
Unable to get voice match to work.
Alarms that you can't set to a specific day with the google app.
And so on.
Root is useful when the manufacturer no longer updates the devices.
I regret having Root mine because I lost Samsung Pay and other things.
DemotionFR said:
I would like to say yes but I can't. the stock apps are very well designed.
The biggest concern is that custom Roms are released faster than modded apps.
For example I tried about ten GCAMs and all of them have a bug... and it becomes more complicated with Exynos.
OpenGcam is not worth samsung app.
Unable to get voice match to work.
Alarms that you can't set to a specific day with the google app.
And so on.
Root is useful when the manufacturer no longer updates the devices.
I regret having Root mine because I lost Samsung Pay and other things.
Click to expand...
Click to collapse
The only one that would have any consequence of rooting is Samsung Pay.
xbt- said:
Root is 100%, absolutely necessary for using the phone. I cannot use any phone without it. Critical root-only capabilities:
full system backups (in twrp)
titanium backup
disable updates permanently (update ONLY when want to)
app freezers (app quarantine)
disable/remove bloatware
disable google play services/google play
automate/tasker
cf lumen
adblockers
wifi tether
busybox
superuser
ssh tunnel
update android to later version / install custom roms
optimize system
button mapper
custom theming / substratum
nav gestures
tidypanel
xposed
root explorer
app privacy customizations
3c all-in-one toolbox
more
Without root, the phone is unusable to me. I will never buy any phone without root capability. I am willing to go to different carriers just to get root on the device, or go to different manufacturers if root is blocked. For example, I will never buy a huawei device - they are locked.
Click to expand...
Click to collapse
can you carrier /network unlock with the root >?
NickosD said:
Tbh root is not needed, unless you want to use a custom rom. Most things are already in the android now.
Click to expand...
Click to collapse
No, even if you wanna use custom rom you don't need to root. Just pick the rom with the apps you want or just use the gapps packages you want, if want essential to work gapps then use pico or nano. If there is still something you want to remove and the romdoesn't allow, just use adb shell commands and thats it. Less issues with banks not working because of Magisk (root). I know Magisk has a feature to hide itself, change its name but depending on the app, the libs can be found and know that is Magisk, so for security purposes some apps don't work and some aren't even shown in the Google Play Store just because you rooted the device.
logandavid said:
maybe now the root is not needed but later down the road when your phone will get obsolete and newer android OS updates will be halted for S10+ then you'll be more attracted towards custom roms. Actually it is just personal preference.
Click to expand...
Click to collapse
It's happening right now, I doubt S10+ will receive Android 13 and now just security and bug fix updates are being shipped by Samsung.
Haknor said:
It's happening right now, I doubt S10+ will receive Android 13 and now just security and bug fix updates are being shipped by Samsung.
Click to expand...
Click to collapse
It won't get any new Android upgrades AFAIK.
But appart from tripping knox, what else do I lose if I unlock my bootloader? I read once, quite a while ago, that the battery is limited to 80% of its full capacity. Is that true?
io_gh0st said:
It won't get any new Android upgrades AFAIK.
But appart from tripping knox, what else do I lose if I unlock my bootloader? I read once, quite a while ago, that the battery is limited to 80% of its full capacity. Is that true?
Click to expand...
Click to collapse
Depending on the version, you'll notice stock camera to be limited or not work as expected, secure folder, dual messenger either not working, it can trigger some banks or payment apps (especially if you root), no more ota updates (if you keep using stock rom), drm content can stop working, samsung pay, Play Store might limited the apps you see and so on... Not sure about the battery, for me unlocking the bootloader and switching to another rom made my battery last more than stock, but it depends on the rom, the device, it's not a rule of thumb.