Related
Hi, tomorrow I'm getting a nexus 7 (2013), and it's going to be my first android device, the thing is, as the first android device, I don't want to screw it up as soon as I get it.
There are some apps which I would like to get for it, for example the sixaxis controller app and anti ads apps but they require rooting, so the question is, should I root it and how safe is rooting. As my first tablet I want to be kinda safe about it, the thing which worries me the most is "bricking" and the fact that the warranty turns void, so I want to know how actually safe it is to root, I know there are different kinds of bricking, I already asked a guy on a youtube video and he said that it's unusual to get a nexus device bricked, expecially hard bricked, but he said that if it's hard bricked I'm kinda stuck, so is there no actual solution for some kind of bricking, please give me some advice, also this is my first post on the xda-developers forums, I was going to put links to the things I mentioned but I need to have at least 10 posts to put outside links :/.
MadJohny said:
Hi, tomorrow I'm getting a nexus 7 (2013), and it's going to be my first android device, the thing is, as the first android device, I don't want to screw it up as soon as I get it.
There are some apps which I would like to get for it, for example the sixaxis controller app and anti ads apps but they require rooting, so the question is, should I root it and how safe is rooting. As my first tablet I want to be kinda safe about it, the thing which worries me the most is "bricking" and the fact that the warranty turns void, so I want to know how actually safe it is to root, I know there are different kinds of bricking, I already asked a guy on a youtube video and he said that it's unusual to get a nexus device bricked, expecially hard bricked, but he said that if it's hard bricked I'm kinda stuck, so is there no actual solution for some kind of bricking, please give me some advice, also this is my first post on the xda-developers forums, I was going to put links to the things I mentioned but I need to have at least 10 posts to put outside links :/.
Click to expand...
Click to collapse
Welcome to the forum!
Rooting is safe, as long as you don't do stupid things, if you stay responsible, nothing bad could ever happen. Responsible means Googling if you don't know something, and if something looks risky, don't do it and maybe search for an alternative.
I have rooted 8 devices, so far, never has one been bricked.
The rooting proces alone is really easy, even someone with no Android experience, like you, can do that.
But with rooting you'll have to unlock the bootloader of your device, that means all data of your Nexus will be erased, so it's good to root the Nexus 7 right after you buy it, so you'll lose no important data.
This thread will give you a toolkit for Windows, in which you can root and unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=2430708 (use option 3 in the root section, everything is automatic)
Before doing anything, please read really good, and if you don't know what something means, Google it first.
With a custom recovery, you can make a full backup of the current state of your device, so if it's bricked, you can access the custom recovery and restore the backup.
So what you have to do when you buy the Nexus 7, download and install the toolkit, go to the root section, click action 3 (unlocked bootloader, root and custom recovery). You're rooted. Then go to custom recovery (Google it if you don't know how to get there), and make a backup, so if anything happens and you are bricked, use a key combination to get in recovery and restore the backup, just like nothing happened
Hope this is enough for you!
Don't forget, if you have a question, feel free to PM me or to reply on this thread
Ibrahim9999 said:
Welcome to the forum!
Rooting is safe, as long as you don't do stupid things, if you stay responsible, nothing bad could ever happen. Responsible means Googling if you don't know something, and if something looks risky, don't do it and maybe search for an alternative.
I have rooted 8 devices, so far, never has one been bricked.
The rooting proces alone is really easy, even someone with no Android experience, like you, can do that.
But with rooting you'll have to unlock the bootloader of your device, that means all data of your Nexus will be erased, so it's good to root the Nexus 7 right after you buy it, so you'll lose no important data.
This thread will give you a toolkit for Windows, in which you can root and unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=2430708 (use option 3 in the root section, everything is automatic)
Before doing anything, please read really good, and if you don't know what something means, Google it first.
With a custom recovery, you can make a full backup of the current state of your device, so if it's bricked, you can access the custom recovery and restore the backup.
So what you have to do when you buy the Nexus 7, download and install the toolkit, go to the root section, click action 3 (unlocked bootloader, root and custom recovery). You're rooted. Then go to custom recovery (Google it if you don't know how to get there), and make a backup, so if anything happens and you are bricked, use a key combination to get in recovery and restore the backup, just like nothing happened
Hope this is enough for you!
Don't forget, if you have a question, feel free to PM me or to reply on this thread
Click to expand...
Click to collapse
Ok, thanks for the information, I was going to update the nexus to kitkat when I get it, so if I root it with kitkat I will still have the kitkat version right? I still don't think I'll root it when I get it, but this makes me feel safer about it, and when you say lose important data what do you mean? basically it will delete all the files I have on my nexus that weren't there in the first place(when I buy it) right?
MadJohny said:
Ok, thanks for the information, I was going to update the nexus to kitkat when I get it, so if I root it with kitkat I will still have the kitkat version right? I still don't think I'll root it when I get it, but this makes me feel safer about it, and when you say lose important data what do you mean? basically it will delete all the files I have on my nexus that weren't there in the first place(when I buy it) right?
Click to expand...
Click to collapse
Yes, you're right about the last question.
When you root it, the KitKat version stays the same, don't worry.
Can you please thank my posts? Little effort from you and it really helps me
Ibrahim9999 said:
Yes, you're right about the last question.
When you root it, the KitKat version stays the same, don't worry.
Can you please thank my posts? Little effort from you and it really helps me
Click to expand...
Click to collapse
Ok I thanked the posts, I already have my nexus 7, udpating it to kitkat right now, I will think about rooting later, I can do other stuff without it
edit: one more thing, does some of the apps that come with nexus get deleted on rooting? for example play store
that's right, rooting is safe if you know what you do, and do read first tutorials before doing it...goodluck
MadJohny said:
Ok I thanked the posts, I already have my nexus 7, udpating it to kitkat right now, I will think about rooting later, I can do other stuff without it
edit: one more thing, does some of the apps that come with nexus get deleted on rooting? for example play store
Click to expand...
Click to collapse
No, literally nothing changes in your Nexus 7 with rooting, except for 1 extra app being added. That's it.
actually it is depends on your own
if you are going to use some apps which are needed to root then you have no choice but to root
like Titanium Backup, Greenify, Autostarts, AdAway, etc
Rooting
Rooting is fine but it comes with great consequences like bad security and you can brick it, there's many things that can go wrong. But if you get thru that daunting, annoying and sometimes scary process of rooting you open a world of freedom and fun.
So I finally pulled the trigger and ordered a G930F. Sorry for the noob question, but when it arrives, what should I do with it and in what order? End goal would be to be able to install custom roms easily when new roms are released.
I was thinking:
1. Flash new firmware
2. Enable OEM unlock from settings
3. Disable auto updates
4. Flash recovery TWRP
5. Wipe data
6. Root
7. Setup phone
Thoughts?
Also for the firmware, I'm going to be using this on US T-mobile. Should I do UK firmware or German T-Mobile?
Thanks
Any suggestions guys?
Sorry if this question sounds stupid. I've had my current phone (HTC One M7) for 3 years now and it's at a state where I can just flash a new rom whenever I want. It's been a long time since I did the initial setup of unlocking, installing the custom recovery and initial rooting that I can't really remember what I did and what order they have to be done. I just want to make sure I don't do them in the wrong order and have to redo any of the previous steps again.
Thanks
johnusesandroid said:
So I finally pulled the trigger and ordered a G930F. Sorry for the noob question, but when it arrives, what should I do with it and in what order? End goal would be to be able to install custom roms easily when new roms are released.
I was thinking:
1. Flash new firmware
2. Enable OEM unlock from settings
3. Disable auto updates
4. Flash recovery TWRP
5. Wipe data
6. Root
7. Setup phone
Thoughts?
Also for the firmware, I'm going to be using this on US T-mobile. Should I do UK firmware or German T-Mobile?
Thanks
Click to expand...
Click to collapse
I love root as well, but the S7 is so good, really doesn't require root at this point. If root is what you desire, you can look in the S7 forums, and they should walk you through what you should do, but your set-up doesn't seem bad. I still suggest sticking to the S7 at least for a week and see if you really need root. With Samsung's Theme store, launchers, and etc, besides removing bloat, having exposed and etc, not sure why its important to root at least at this point.
I'm not clear on whether the bootloader on the 930F can be unlocked; you might want to check on that first.
In terms of root, I still use Xposed and Titanium Backup. Yes, you can already hide the quick-connect icon, but the brightness slider is locked on there (SQL Editor needed to get rid of it, another root app). You can also use the fun features of root - I use Tasker to turn NFC on only for those apps that need it and turn it off when I don't, use Keepass2Android's automatic keyboard switching, etc.). I rooted mine within the first hour of having the phone home and turned on. The phone still isn't perfect, and honestly still not as flexible as many of us would like, but it's not a do or die situation anymore either.
Truth6199 said:
I love root as well, but the S7 is so good, really doesn't require root at this point. If root is what you desire, you can look in the S7 forums, and they should walk you through what you should do, but your set-up doesn't seem bad. I still suggest sticking to the S7 at least for a week and see if you really need root. With Samsung's Theme store, launchers, and etc, besides removing bloat, having exposed and etc, not sure why its important to root at least at this point.
Click to expand...
Click to collapse
yeah I'm just the kind of guy who can't stand not having admin/root rights on my stuff :laugh:
but yeah a couple root only apps that I can't live without are xposed (and the hold power button to turn on flashlight mod), titanium backup, f.lux, etc...
databoy2k said:
I'm not clear on whether the bootloader on the 930F can be unlocked; you might want to check on that first.
In terms of root, I still use Xposed and Titanium Backup. Yes, you can already hide the quick-connect icon, but the brightness slider is locked on there (SQL Editor needed to get rid of it, another root app). You can also use the fun features of root - I use Tasker to turn NFC on only for those apps that need it and turn it off when I don't, use Keepass2Android's automatic keyboard switching, etc.). I rooted mine within the first hour of having the phone home and turned on. The phone still isn't perfect, and honestly still not as flexible as many of us would like, but it's not a do or die situation anymore either.
Click to expand...
Click to collapse
awesome sounds like the kind of setup I would do, thanks
but the order of what I'm planning on doing is correct though, right? If I'm understanding them correctly, I need to do firmware before root since firmware flash would get me back to root-less stock I think. I need to do root right after twrp and data wipe because of that boot loop issue they described in the twrp thread. so firmware first, twrp second, then root third?
johnusesandroid said:
yeah I'm just the kind of guy who can't stand not having admin/root rights on my stuff :laugh:
but yeah a couple root only apps that I can't live without are xposed (and the hold power button to turn on flashlight mod), titanium backup, f.lux, etc...
awesome sounds like the kind of setup I would do, thanks
but the order of what I'm planning on doing is correct though, right? If I'm understanding them correctly, I need to do firmware before root since firmware flash would get me back to root-less stock I think. I need to do root right after twrp and data wipe because of that boot loop issue they described in the twrp thread. so firmware first, twrp second, then root third?
Click to expand...
Click to collapse
Seems right. Plug your SIM in first by the way; the phone does a wipe when it gets a sim for the first time (not sure about thereafter; don't have a second sim to test with). But yes, your process is essentially what I did.
Hello. Im new here and I have Motorola Photon Q with SIM mod and custom ROM Mokee (Android 6.0.1).
I want to know if I want to instal CM11/12 (or CM13) on my phone i need to get back to Stock ROM and than do all of the rom stuff?
Also i trying playing PoGO with Mygisk but when i turn off root it gets back on. Any solution?
And one more, is there a big chance to I change my phone to a ussles brick?
Thanks for help.
There's always the potential to brick a device, if you do something incorrect.
While the chances are less likely nowadays, the issue is still possible. If you are afraid of this potential, stop now.
Otherwise, you can flash any ROM you want - no need to go back to stock.
As for the root comment, no clue - I'm guessing you didn't truly disable root (perhaps you can't disable it in Mokee? Never used it myself. Never wanted to disable root either...).
Good luck.
arrrghhh said:
There's always the potential to brick a device, if you do something incorrect.
While the chances are less likely nowadays, the issue is still possible. If you are afraid of this potential, stop now.
Otherwise, you can flash any ROM you want - no need to go back to stock.
As for the root comment, no clue - I'm guessing you didn't truly disable root (perhaps you can't disable it in Mokee? Never used it myself. Never wanted to disable root either...).
Good luck.
Click to expand...
Click to collapse
I sucessly upgrade my phone to CM12, its nightly in fact but everything is ok for now. :good:
In Mokee I have a option to dislabe root in developer options but this didn't give anything, PoGO still won't start.
I was wondering about it and I think I shouldn't risk to brick my phone for one silly game.
Thank You very much for help
I realize this is way old so you probably figured out a way, but to play PoGo one easy way (that works for me) is to use TWRP to rename the 'su' binaries to something else. There are a couple of them and I don't recall exactly where they are but I found the info on this site. Of course then you won't have root automatically, but can still run your renamed su from a terminal if needed, or use twrp to rename them back to su. Every time you update builds su gets restored, so have to rename again for PoGo.
Does anyone have any idea if we'll ever get the ability to do a DRM key backup, root and DRM key restore on on XZP?
I absolutely love this phone but not having root is killing me...
Unlocking the bootloader and getting root has been achievable since day one.
You can forget about the DRM keys backup though.
I was going to ask you how you missed the thread called "Root Achieved" but then I saw you were on mobile so eh.
Thanks for the reply. I know root has been achievable for ages but I'm not gong to root without a way to backup the DRM keys or patch around them. I'm not losing camera functionality on a $800 phone.
So still waiting for Tobias or someone else to make a method like on the Z5.
Have fun waiting I guess.
Also, the backup tool doesn't even work on Nougat so there's another problem.
Two problems that is unlikely to be solved in the near future.
leijonasisu said:
Does anyone have any idea if we'll ever get the ability to do a DRM key backup, root and DRM key restore on on XZP?
I absolutely love this phone but not having root is killing me...
Click to expand...
Click to collapse
When I got my X Performance last year, I waited about three months to unlock it, due to the lack of temporary root exploit to run the backup of TA partition, but the tool for that was developed, and finally I was able to do things the right way!
Xperia devices, imo, are "camera phones", also, I do not like to lose their main functionality/differential (root can wait).
It sounds like now sony has just changed the way drm keys are stored and wiped after the device is unlocked, so it will be a bit difficult to achieve this, but not impossible!
Anyway, it's up to you mate. For now, enjoy your powerful device with stock camera!!
serajr said:
When I got my X Performance last year, I waited about three months to unlock it, due to the lack of temporary root exploit to run the backup of TA partition, but the tool for that was developed, and finally I was able to do things the right way!
Xperia devices, imo, are "camera phones", also, I do not like to lose their main functionality/differential (root can wait).
It sounds like now sony has just changed the way drm keys are stored and wiped after the device is unlocked, so it will be a bit difficult to achieve this, but not impossible!
Anyway, it's up to you mate. For now, enjoy your powerful device with stock camera!!
Click to expand...
Click to collapse
Missed your updated xposed modules on my x. They were crucial for Z and Z3 haha. You're right, this beast is not that bad without root. Some non root tweaks here and there make the experience bearable.
But when root becomes a win win solution for XZp and xposed available for n / o, I'm expecting to see some of that quality work of yours on the repo. I'll be within the firsts to bootloop... I mean test haha ?
Glad you're on XZp dev side.
I'm definitely not rooting just to lose the camera. It's one of the main reasons why I bought this phone. Hopefully someone works out how to root the phone and keep the DRM keys intact. I'll come back every month and see how things go.
Now with recovery we can flash all the amazing sound mods, magisk + modules.
Root <3.
I'm also holding out on getting new Sony devices to replace my Z5P, I refuse to use a phone without Adaway (and friends).
In my opinion keeping the DRM keys so we can enjoy the camera on this great phone is really important. We have DRM backups for the Z, Z1, Z3, Z+ etc. I hope we can get them for the XZP. There has to be a way someone can work out to backup the TA partition before rooting. I'll cross my fingers, because I know that there's never been a case where a device hasn't ended up being totally bypassed. I just hope it won't take too long.
It would be so easy to backup the DRM on this device.
Too bad I'm not really a developer.
Now you have to wait until I learn programming.
lebigmac said:
It would be so easy to backup the DRM on this device.
Too bad I'm not really a developer.
Now you have to wait until I learn programming.
Click to expand...
Click to collapse
If it was "too easy" now we would have the backup. As you can see it isn't.
FartyParty said:
Now with recovery we can flash all the amazing sound mods, magisk + modules.
Root <3.
Click to expand...
Click to collapse
Is it possible to do these without loosing the dm and having to root?
I dont understand why would people wait for DRM backup... I mean even if you do backup your DRM keys, once you restore them your bootloader automatically relocks so you lose root...
if you want aosp roms with google camera, nothing would change because once you root you lose they keys, and only way you can restore them is when you reflash the stock FW version you backed up the DRM keys from.
so yeah, devs already got a drm fix so if your problem is the camera functionality its not gonna work on root even with back up, so you might wanna go back to stock with working camera thats ok, you can flash a stock rom and flash a fix and it works just as good.
unless its warranty thats your problem, then yah you gotta wait for backup, but besides that its really pointless to wait, i mean with drm fix you get full camera functionality on a stock rom plus you got root, plus you get to modify the device as you like so its really not a big deal here, as for AOSP roms with or without backup, camera functionality is not gonna be at its best (unless kernel supports its full potential) again, you can not restore DRM keys to AOSP, you can only restore them once you reflash the FTF you had when you backed up the keys...
madshark2009 said:
unless its warranty thats your problem, then yah you gotta wait for backup, but besides that its really pointless to wait
Click to expand...
Click to collapse
For me, it would be warranty, and resale-value.
You'll have hard times reselling a device that needs special care with every software update released.
Hi Folks,
I hope you guys can shed some light into this, sorry if this is long and if this has been asked I'm sorry but I could not find the answers I was looking for, as some results they sound almost the same and some had not specified enough. So I hope the clever people here can explain a few things before I go ahead.
Background on my Phone (don't know if its relevant or not)
I own an Exynos SM-G970F, on One UI 3.1, June 2021 Update, this was purchased in Australia. Now that my phone is out of warranty I was thinking of installing a custom ROM. The main motivation was to reduce CPU usage and improve battery life.
I have installed a custom ROM and rooted my tablet for practice and it was easy to follow. I gotta say it was phenomenal how it brought back ancient hardware to buttery smooth performance of newer android versions. I wanted this same experience on my daily driver phone and there are some security based questions I would like to know.
Questions
1. First off unlocking the bootloader, I have read that it reduces your security of the phone as this allows hackers to gain access to your phone unlike a locked bootloader. As far as I understand the bootloader is to check if the system partition is a Samsung ROM. So in an unlocked state it will still load the kernel and run the system regardless if the ROM is Samsung or not, am I correct in this?
1a. If that's the case and if I installed the custom ROM and then locked the bootloader I would brick my phone right? as the bootloader is looking for a Samsung ROM but since it can't recognize the ROM it will boot loop.
1b. So in this case how would an unlocked bootloader make it vulnerable apart from accessing the OS? I'm thinking in a real word scenario if I were to lose my phone and someone found it, they could have means of access from an unlocked bootloader? but then again they could have access through custom recovery?
1c. Would it be necessary to lock a bootloader once you install a custom ROM? Do some custom ROM support signing bootloaders?
2. SafetyNet, as far as I understand this is a Google thing? like the app from Play store will check your system for any tampered software before functioning or at least warning the consequences of using the app in a custom ROM, is this right?
2a. So this could lead to some banking apps not working as it requires a SafetyNet pass on your device. But this only happens if you end up rooting your device? I understand Magisk is systemless root so the SafetyNet should pass in theory?
Primarily I'm concerned of the security and privacy of the phone but nothing is perfect, so there has to be some give and take with privacy and security? Though I will lose some privacy as I will install OpenGApps for some applications to work. So security would be the most important thing. What would be some best practices for a daily driver phone on custom ROM?
I imagine that hackers are not interested attacking an individual as this takes a lot of time and energy, unless they are bored or something like that.
Thanks for taking the time to read all this and if you can shed more information that would be great! I would like to learn more before giving the green light for custom ROM on my Samsung S10e.
With the caveat that I'm really bad at Samsung, I'll try to give a couple of answers. Sounds like you have the gist of it though...
Unlocking the bootloader is necessary to install anything custom, yes, and it does reduce the security of the device but mainly if someone has physical access to it. Keeping the device encrypted can help protecting your data though. There are some devices that allow locking the bootloader with custom firmware installed, but those are few. General rule: don't even try. I've seen some talk from people at Google about letting custom ROMs be certified, so that you could lock the bootloader with them, but currently there's nothing like that (that I know of). Once in a while I see people talking about trying to sign their images to lock the bootloader, but IMHBCO it's not worth the effort (if it's possible). If you're going custom, keep the bootloader unlocked.
About SafetyNet, it's an API provided with Google's play services and can be used by apps to check if a device's security has been compromised. Far from all bank apps will be using this and many instead have their own ways of detecting a "tampered" device (more on that below). SafetyNet will trigger from a number of things:
Unlocked bootloader
Custom ROM
Root
Etc...
So, as you see it's not only rooting that will cause you problems. There are ways around it though, mainly with the help of Magisk.
When it comes to what bank apps will detect, that could include a custom ROM, root apps, files on your device, Magisk, etc. They're often much more picky than SafetyNet even...
If you need help with getting SafetyNet and banking apps working on a custom ROM, with Magisk, I've got a few resources and tips collected here:
https://www.didgeridoohan.com/magisk/HomePage
Regarding security and custom ROMs it's pretty much the same as on a stock device. Don't install weird apps from outside the Play Store, don't click links in emails, etc. On to of that, another thing to look out for is SELinux. Don't use a ROM that has it disabled. It's quite important for the security of the OS... And if you do root, be careful with what apps you give root access, since an app with root access can do whatever it wants.
No idea if this cleared anything up or just created more questions. If there are Samsung specific stuff I've gotten wrong or missed I hope that someone that actually knows what they're talking about shows up...
Didgeridoohan said:
With the caveat that I'm really bad at Samsung, I'll try to give a couple of answers. Sounds like you have the gist of it though...
Unlocking the bootloader is necessary to install anything custom, yes, and it does reduce the security of the device but mainly if someone has physical access to it. Keeping the device encrypted can help protecting your data though. There are some devices that allow locking the bootloader with custom firmware installed, but those are few. General rule: don't even try. I've seen some talk from people at Google about letting custom ROMs be certified, so that you could lock the bootloader with them, but currently there's nothing like that (that I know of). Once in a while I see people talking about trying to sign their images to lock the bootloader, but IMHBCO it's not worth the effort (if it's possible). If you're going custom, keep the bootloader unlocked.
About SafetyNet, it's an API provided with Google's play services and can be used by apps to check if a device's security has been compromised. Far from all bank apps will be using this and many instead have their own ways of detecting a "tampered" device (more on that below). SafetyNet will trigger from a number of things:
Unlocked bootloader
Custom ROM
Root
Etc...
So, as you see it's not only rooting that will cause you problems. There are ways around it though, mainly with the help of Magisk.
When it comes to what bank apps will detect, that could include a custom ROM, root apps, files on your device, Magisk, etc. They're often much more picky than SafetyNet even...
If you need help with getting SafetyNet and banking apps working on a custom ROM, with Magisk, I've got a few resources and tips collected here:
https://www.didgeridoohan.com/magisk/HomePage
Regarding security and custom ROMs it's pretty much the same as on a stock device. Don't install weird apps from outside the Play Store, don't click links in emails, etc. On to of that, another thing to look out for is SELinux. Don't use a ROM that has it disabled. It's quite important for the security of the OS... And if you do root, be careful with what apps you give root access, since an app with root access can do whatever it wants.
No idea if this cleared anything up or just created more questions. If there are Samsung specific stuff I've gotten wrong or missed I hope that someone that actually knows what they're talking about shows up...
Click to expand...
Click to collapse
Hi Didgeridoohan,
Thank you for taking the time to comb through my queries and I believe you have answered what I was looking for. So it has dispelled any myths and misconceptions of custom roms.
Personally I use the phone most and my significant other uses my phone for some games. So physical access is not likely to fall in the hands of someone else unless I lost it. Encrypting the phone is a good safety measure, I assume this is something that can be done in the settings of the OS?
With banking I guess I will have to install and see if it works out, otherwise I don't mind going to a phone web browser and do it that way.
I appreciate your link for further info of Magisk, I will be reading through the page to get better insight.
Regarding SELinux, I had seen this on my phone though it says SE for Android Status and says 'Enforcing' and on the Custom ROM on my tablet in the settings it also says 'Enforcing'. So I can assume that its ensuring the security of the OS.
I didn't have the intention of rooting as I thought I can root at any point in time but if its good practice to do it when flashing the custom ROM please let me know.
I had planned on installing TWRP and use either Lineage or crDroid (kinda leaning to this one). They both are supported on their website so I don't think I will run into issues.
Once again thanks for your help and advice on the custom ROM, I think my questions were broad and it may not be Samsung specific as there are features I know I will lose but have never used when I had the original ROM.
dude777 said:
Encrypting the phone is a good safety measure, I assume this is something that can be done in the settings of the OS?
Click to expand...
Click to collapse
Yes. Just make sure that any ROM you choose is compatible with encryption. And remember that if you ever want to remove the encryption you'll have to wipe the device.
Regarding SELinux, I had seen this on my phone though it says SE for Android Status and says 'Enforcing' and on the Custom ROM on my tablet in the settings it also says 'Enforcing'. So I can assume that its ensuring the security of the OS.
Click to expand...
Click to collapse
Correct. That's the way it should be if you want to keep some security on your device.
I didn't have the intention of rooting as I thought I can root at any point in time but if its good practice to do it when flashing the custom ROM please let me know.
Click to expand...
Click to collapse
You can wait with rooting. If you don't have any need for it, why bother? I use Magisk to hide the fact that I have an unlocked bootloader (and to hide Magisk from some apps), to use a custom hosts file (for adblocking) and for app backups (I use Swift Backup, works great).
Once again thanks for your help and advice on the custom ROM, I think my questions were broad and it may not be Samsung specific as there are features I know I will lose but have never used when I had the original ROM.
Click to expand...
Click to collapse
There are some things you'll lose when unlocking the bootloader on a Samsung, due to the tripped Knox fuse. I can't say much about that though, since I don't do Samsung...
Have fun!
Thanks Didgeridoohan,
This has given me some confidence in going forward with custom ROM. I will make some backups and take measures and if it doesn't work out I can go back but I probably wont .
I've been running LineageOS on my Exynos S10e for a few days now and it's great, better battery life than on Samsung's firmware too from what I can see.
Settings say encryption is enabled. I'm assuming on /data only, I'll have to poke around as I've been away from Android for a while and I haven't been keeping up with what's going on.
I had to use the Magisk props module (selected the same phone model) to pass SafetyNet and enable Google Pay. Banking apps here in Australia don't seem to care, at least CommBank, Bendigo, AMP by I did select them in MagiskHide just in case.
If you decide to go for it, remove all your accounts before flashing the LineageOS recovery. I didn't and wasn't able to flash recovery until I re-added and removed them (Factory Reset Protection kicked in apparently). Smooth ride after I did this.
If you don't like the LOS gestures use Fluid (FNG), I love how customizable it is. You can hide the navigation bar in Termux by running:
su
props qemu.hw.mainkeys 1
Good luck and feel free to ask me questions if you have any!