Related
Hello
I have a Lenovo P2a42 UK version on 3 mobile.
I haven't rooted a phone before and would like to know how to root my phone.
Firstly, should I root to stock android first and then consider other ROMs?
Secondly, should I root from the UK version (SO56) to the ROW version (S232)?
Finally, what is the best way of rooting to LineageOS in a secure way? What is the best site to download the necessary files?
Sorry for all the questions but any help would be really appreciated.
Thanks in advance!
Firstly, should I root to stock android first and then consider other ROMs?
A. My opinion move to custom rom unless you need led notification light.
Finally, what is the best way of rooting to LineageOS in a secure way? What is the best site to download the necessary files?
A. see the comment 1,2,3,4 on any custom rom thread or simply download aad on su from :- https://download.lineageos.org/extras
and flash it using twrp (remember change data to ext4 otherwise root may not work)
Secondly, should I root from the UK version (SO56) to the ROW version (S232)?
A. i didnt understand what is rooting s056uk to s232
Hit thanks if i've helped
Sent from my Lenovo P2 using Tapatalk
Entirely up to you, but I'd upgrade to the newer stock ROM for now rather than using a custom ROM. You will lose VOLTE support and some other features, like the battery saving switch / LED notifications.
If you do plan on rooting, use the guide in the TWRP post here on the Lenovo P2 forums. However, it'd be wise to read up on what you can actually do with root. Myself, I rooted in order to install a custom boot animation (tricky and not the standard method on Lenovo stock ROM), change fonts (a little frivolous considering you're losing warranty for it), and mainly to add a hosts file for system wide ad blocking. You can use magisk to root (there's a forum dedicated to it) but I have had quite a few problems with it.
Also, if you root, you lose access to some apps such as android pay, and lose access to features in certain apps (banking apps for example). Magisk claims to work around these problems, but it's tricky to install and upgrade and doesn't always work. I almost got stuck in a bootloop using the default uninstaller, and had to modify the installer by hand in order to get newer versions to install. On top of that, the magisk module system doesn't seem to work, at least on my device.
Whatever happens, let us know what you choose to do and how you get on.
Hi,
I recently had to return my phone back to stock because of a warranty issue. (battery dying between 25% and 40%)
So chances are high that I will get the phone back with Marshmallow instead of Lollipop.
is there a guide or can anyone give some pointers how to root this device? After a bit of reading I still have a few specific questions, so maybe someone here can help.
A) What TWRP version will I need for the M8s on Marsmallow?
B) Will Magisk systemless root work on this device?
C) If the rooting has succeeded and I remove some bloatware apps from /system/vendor and /privapp and such. Will this trip the Google safety net? Or is safety net not yet applied to our M8s devices?
Thanks!
I don't personally have the M8s version specifically. But as the device forum sections for all the M8 versions in general are becoming pretty quiet; I'll try to help you to the best of my knowledge.
A) The TWRP recovery posted in this (M8s) forum section should work fine on Marshmallow. Looks like it's only updated to 2.8.6
B) Should work, yes. I would suggest the current stable Magisk version, which is 14.0
Backup your stock (unrooted) ROM before trying to root (as you always should - this is best practice and just good common sense). Then if anything goes wrong, you can easily restore to stock.
C) Not sure. But I can tell you on my current device (OnePlus 3T) that removing system (bloat) apps does not trip safety net.
Hi @redpoint73,
Thanks. That takes away some worries and gives me some confidence for giving it a third shot . Nandroid's don't work on the M8s unfortunately, I've tried this once since I botched something up during my first root attempt, put back the Nandroid and my Bluetooth was dead. (and probably more, but I didn't investigate it further back then.)
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Thanks so far and I'll report back my results in this topic. Now I first have to wait to see if they give me my warranty, since the bootloader said relocked and the firm I had to send it to is notorious for blaming factory faults on rooting of the phone. Fingers crossed!
Thijs_Rallye said:
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Click to expand...
Click to collapse
Should be the same, yes.
The reason for this, is that the system is write-protected, even with root. On the M8, there is a kernel mod which disables the write protection (allows you to modify system while booted to OS), but I don't know if there is such a mod for the M8s. But if you were able to do it in TWRP, the same should apply on Marshmallow.
So I finally got my phone back, or well, to be accurate, I got another phone (albeit another M8s) back under warranty. I guess they f'd it up during repairs or something. And as expected my phone was upgraded to Marshmallow.
Anyhow, the more I read about Magisk and systemless rooting the more lost I seem to get lost. Is there somewhere a step by step guide for obtaining root on this phone?
Let me recap from what I've understood so far (SOURCE 1, SOURCE 2 and SOURCE 3)
1) Backup my boot partition, I am still searching how to accomplish this without rooting the phone first. Booting to TWRP without installing resulted in mangling some data in the boot partition, so unfortunately that is not an option. (blanks the OS version)
2) Boot to TWRP and flash the Magisk zip file. There should be an option somewhere in TWRP to enable systemless rooting.
3) ?
So if anyone knows if I am on the right (or wrong) track please let me know .
Thijs
Edit: I can't seem to get the phone boot TWRP for some reason (from my harddrive htc_fastboot boot twrp.img). This used to be possible on my old M8s which I had send in for repairs. Do I really have to flash it because I have no way of backing up the old original recovery .
Okay, since it is kinda dead in here let me bump this for anyone in the same situation. I've managed to install Magisk successfully. The steps involved
1) unlock bootloader
2) flash twrp (htc_fastboot flash recovery twrp.img) I've used the latest version from Captain Throwback which I've found in the OP of the Void_Zero Lineage OS thread.
3) boot the phone and copy magisk systemless root zip and the apk file to your internal storage Grab the uninstaller as well in the topic.
4) reboot to recovery (adb reboot bootloader)
5) flash the zip from within recovery
6) reboot the phone and install the Magisk app.
7) done
Use this guide on your own risk. It worked flawlessly for me but no guarantees .
Hi XDA
I have a son with Asperger syndrome and that give parents sometimes unusual task to solve.
He got a Sony xz2 compact, but he refuses to use a phone until the camera and google services are disabled, do to security lags. He wants to remove the system camera software to make sure no one can exploit the camera.
In other words, he wants to be so anonymous and hacker free as possible - and the camera is a big issue for him.
And yes, I know is possible to disable the camera in Sony configuration (and it's done) but that is not enough.
I hope getting some help to find a solution this two tasks:
1) How to get or make an image of the phone to store/save in my pc so it can be restored if needed.
2) How to root the xz2 compact and uninstall the camera
I will really appreciate some help in this issue.
(sorry my English)
Regards.
1. There is not much you can do, backup related on a Sony phone with locked bootloader. You can use google backup, if you want, but even Sony's solution won't work on a phone with Android Pie, after bootloader is unlocked (it would, if you are on Oreo and you would apply drm-fix after unlocking). Almost all other solutions need root, which you don't have on a locked phone.
2. In this thread you will find a step-by-step guide to install twrp recovery and root (by flashing Magisk) and the download for twrp recovery, made by @MartinX3
I won't link the recovery file itself, because it depends on the way you want to proceed. You can use Sonys stock rom or you can install aosp/omnirom.
In your case i would use aosp or omnirom, because it comes without google crap and it is pure Android. You only need to delete/rename the camera with a root explorer and you are good to go.
But i'm sure, @MartinX3 can tell you more about aosp or omnirom and how to flash it, because i have not used it yet. Anyway, camera is not finished on aosp/omni, so you won't loose very much.
old.splatterhand said:
1. There is not much you can do, backup related on a Sony phone with locked bootloader. You can use google backup, if you want, but even Sony's solution won't work on a phone with Android Pie, after bootloader is unlocked (it would, if you are on Oreo and you would apply drm-fix after unlocking). Almost all other solutions need root, which you don't have on a locked phone.
2. In this thread you will find a step-by-step guide to install twrp recovery and root (by flashing Magisk) and the download for twrp recovery, made by @MartinX3
I won't link the recovery file itself, because it depends on the way you want to proceed. You can use Sonys stock rom or you can install aosp/omnirom.
In your case i would use aosp or omnirom, because it comes without google crap and it is pure Android. You only need to delete/rename the camera with a root explorer and you are good to go.
But i'm sure, @MartinX3 can tell you more about aosp or omnirom and how to flash it, because i have not used it yet. Anyway, camera is not finished on aosp/omni, so you won't loose very much.
Click to expand...
Click to collapse
Thanks for the useful information. I'm not very firm at the Android version (oreo or pie) - but the phone is a Sony Experia xz2 model H8324 and Android ver. 8.0.0 (patch level april 1, 2018). Hope this make sense
This is my first sony, so i'm not the "most helpful hand", i think.
Backup related, if you use sony backup before unlock on oreo, you can flash drmfix after unlock and then you should be able to use sony backup to restore your data.
If this is successful, you are rooted and you should be able to use Titanium Backup.
But as sony newbie i don't know how far sonys backup solution goes.
Anyway, i'll recommend in your case a rom like aosp or omni, because there are no Google things in it.
Why not cover the cameras with stickers if that's the biggest issue? You'll have to root the phone to completely disable all the G Apps, some of the firmware versions allow you to completely disable the G services - if you trust it.
You can use pm uninstall command thru adb shell. This way the app gets removed for the user, and thus seems totally removed. The apk itself do still remain in the system folder, and can be reinstalled if wanted, but can't be launched. This method do not need rooting either.
You can't make and image of the phone, at least not without rooting it first. But that will break some stuff, like camera, and that can NOT be restored in ANY way (drm keys are lost forever). For most (all?) Xperia devices there are images available for flashing with FlashTool/Xperifirm, but note that this will not recover the lost drm keys if you unlocked the bootloader in the first place.
Hello,
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked out without problems.
Now I have two questions:
1. Does the bootloader have to be unlocked because I read in other forums that you only have to unlock it if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the stock and only give apps root rights. I also want to keep getting OTA-updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" at the end unlike my modell number). Now to my question: Can I use one of these or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards,
Shademaster639
It's an English forum
I hope i am right but translated from german to english using google translate.
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked without problems.
Now I have two questions:
1. Must the bootloader be deactivated because I read in other forums that you only have to deactivate the bootloader if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the floor and only give apps root rights. I also want to keep getting OTA updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" on End, as with my model number). Now to my question: Can I use it or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards
Shademaster639
Lol, just recognized that the forum is english. I didn't think about this as I wrote the entry. The translation @spawnlives gave fits my question. Sorry for my mistake!
EDIT: I've edited my entry now to english.
Shademaster639 said:
Hello,
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked out without problems.
Now I have two questions:
1. Does the bootloader have to be deactivated because I read in other forums that you only have to deactivate the bootloader if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the stock and only give apps root rights. I also want to keep getting OTA-updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" at the end unlike my modell number). Now to my question: Can I use one of these or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards,
Shademaster639
Click to expand...
Click to collapse
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
spawnlives said:
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
Click to expand...
Click to collapse
Thank you for your quick answer.
I am a newbie regarding rooting as I rooted my phone years ago and I just followed some instructions by chainfire.
1. It would be kind if you could explain a bit more detailed what you mean with "flashing with odin then root again".
2. How do I backup my phone optimally?
Kind regards
Shademaster639
Shademaster639 said:
Thank you for your quick answer.
I am a newbie regarding rooting as I rooted my phone years ago and I just followed some instructions by chainfire.
1. It would be kind if you could explain a bit more detailed what you mean with "flashing with odin then root again".
2. How do I backup my phone optimally?
Kind regards
Shademaster639
Click to expand...
Click to collapse
Samsung firmware can be downloaded from the internet or using PC apps. Generally if needed to flash firmware with Odin it will revert back to stock rom.So generally any modifications done to the phone ( ie: custom recovery,root,customs Rom's etc ) will be reverted back to stock firmware.
So if the phone is modifiied and you want upgrade to lastest firmware you would flash with Odin and then you would have to modify you phone again.
From a backup point of view I don't really have any non root method that I use. I mainly use custom recovery ( TWRP ) to backup when making changes to the phone ( except for firmware upgrades ). You could try something like a cloud backup service or try Samsung Smart Switch. There are also apps ( like on play store ) that will do backups up as well ( keep/copy backup's on SD card or PC ).
spawnlives said:
Samsung firmware can be downloaded from the internet or using PC apps. Generally if needed to flash firmware with Odin it will revert back to stock rom.So generally any modifications done to the phone ( ie: custom recovery,root,customs Rom's etc ) will be reverted back to stock firmware.
So if the phone is modifiied and you want upgrade to lastest firmware you would flash with Odin and then you would have to modify you phone again.
From a backup point of view I don't really have any non root method that I use. I mainly use custom recovery ( TWRP ) to backup when making changes to the phone ( except for firmware upgrades ). You could try something like a cloud backup service or try Samsung Smart Switch. There are also apps ( like on play store ) that will do backups up as well ( keep/copy backup's on SD card or PC ).
Click to expand...
Click to collapse
If I got it right, you root your phone by flashing a modified AP-file with Odin, so if I want stock firmware back, I have to flash the original firmware?
Shademaster639 said:
If I got it right, you root your phone by flashing a modified AP-file with Odin, so if I want stock firmware back, I have to flash the original firmware?
Click to expand...
Click to collapse
Basically yes. Stock firmware will generally replace any modifications done to the phone.
spawnlives said:
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
Click to expand...
Click to collapse
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
elliwigy said:
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
Click to expand...
Click to collapse
Thanks.
Appreciate the insight and the clarification.
Hopefully @Shademaster639 will pay attention to your post.
O/T: should say thanks also to the exploits made even though I don't have a ( US ) snapdragon variant on other devices.
elliwigy said:
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
Click to expand...
Click to collapse
I have unlocked my bootloader now since I had to do it nevertheless. I couldn't use cf-auto-root since there was no modified firmware for my device (sm-a505fn) listed on firmware.mobi. I tried rooting my phone using the latest version of magisk (v20.x) now, got random bootloops though. So I flashed my device back to stock with the original samsung firmware.
@spawnlives
1. Could you suggest me a video/forum entry/method that worked for rooting the a50 (SM-A505FN)? Is it recommended to install TWRP or just root with Magisk?
2. Are the newer devices protected with something like a "hidden OEM unlock" as I saw some videos about it how to deactive it? You are supposed to see this if this appears in your download mode: "KG STATE: Prenormal"?
Thank you in advance for future answers!
Kind regards
Shademaster639
EDIT: I have tried to root my phone now with latest Magisk version v20.x, but I got random bootloops. Same with version v19.3, which should work stable on a50 referring to this post: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271
Kind regards
Shademaster639
Shademaster639 said:
@spawnlives
1. Could you suggest me a video/forum entry/method that worked for rooting the a50 (SM-A505FN)? Is it recommended to install TWRP or just root with Magisk?
2. Are the newer devices protected with something like a "hidden OEM unlock" as I saw some videos about it how to deactive it? You are supposed to see this if this appears in your download mode: "KG STATE: Prenormal"?
Thank you in advance for future answers!
Kind regards
Shademaster639
EDIT: I have tried to root my phone now with latest Magisk version v20.x, but I got random bootloops. Same with version v19.3, which should work stable on a50 referring to this post: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271
Kind regards
Shademaster639
Click to expand...
Click to collapse
From you private message
Magisk has 2 parts to it.
Magisk- root method
Magisk Manager - control panel for magisk.
Magisk Manager is an apk app so it will show up regardless whether you phone is rooted or not ( except safe mode ).
Not having your device I not sure about you reboot issues. While doing a quick search there are issues posted here on xda and on Google about it. If i see anything useful I let you know.
KG and RMM states ( checked in download mode ) is a extra lock to prevent modifying your phone. I don't know if it effects every Samsung device though. So basically if KG and/or RMM state is showing Prenormal it will prevent modifying your phone.
Some more info from here
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
spawnlives said:
From you private message
Magisk has 2 parts to it.
Magisk- root method
Magisk Manager - control panel for magisk.
Magisk Manager is an apk app so it will show up regardless whether you phone is rooted or not ( except safe mode ).
Not having your device I not sure about you reboot issues. While doing a quick search there are issues posted here on xda and on Google about it. If i see anything useful I let you know.
KG and RMM states ( checked in download mode ) is a extra lock to prevent modifying your phone. I don't know if it effects every Samsung device though. So basically if KG and/or RMM state is showing Prenormal it will prevent modifying your phone.
Click to expand...
Click to collapse
I know that Magisk Manager will show up regardless whether my phone is rooted as I just installed it on my phone (like any other apk/app). I was asking if there was a way to fix the bootloop with the manager.
I checked if the bootloader is unlocked by going into the odin/download mode [VOLUME UP] + [VOLUME DOWN] and it showed: KG STATE: checking.
(Comment under a video of @AndroidHowTo: https://www.youtube.com/watch?v=zqbu7jCmeMY
@AndroidHowTo OK But Now I Have Another Problem
your video ( KG STATE:Checking) but its Must be (KG STATE:NORMAL)
Until it is solved
AndroidHowTo:
If your device KG State = Checking it means the status is normal / unlocked bootloader. it different with RMM State)
Shademaster639 said:
I know that Magisk Manager will show up regardless whether my phone is rooted as I just installed it on my phone (like any other apk/app). I was asking if there was a way to fix the bootloop with the manager.
I checked if the bootloader is unlocked by going into the odin/download mode [VOLUME UP] + [VOLUME DOWN] and it showed: KG STATE: checking.
(Comment under a video of @AndroidHowTo:
@AndroidHowTo OK But Now I Have Another Problem
your video ( KG STATE:Checking) but its Must be (KG STATE:NORMAL)
Until it is solved
AndroidHowTo:
If your device KG State = Checking it means the status is normal / unlocked bootloader. it different with RMM State)
Click to expand...
Click to collapse
KG state - prenormal
and / or
RMM state - prenornal
Problems with modifying phone.
KG state - checking
RMM state - normal or disappeared
Allows modifying phone.
For want of better terminology they are separate keys to the same lock.
There are plenty of sites regarding this:
https://chimeratool.com/fr/docs/sam...onitoring-and-management-rmm-unlock-functions
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.