Related
Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.
spynathan said:
Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed
Envious_Data said:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed
Click to expand...
Click to collapse
Awesome thanks! I'll try it first thing tomorrow after work.
Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.
spynathan said:
Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.
Click to expand...
Click to collapse
atleast on windows 10 i found that i had to disable driver signature verifacation and sometimes i had to run command prompt in admin
I have this phone and it has a very nice design. I want to play around with it, but I would much prefer a custom ROM on it because it is mostly Chinese and, you guessed it, I can't read it.
So what my goal is, to have really any custom ROM on it. I'm pretty new to this, and I've only done this to an LG G3 with Fulmics. I know the first step in the process with this. I have to "unlock the boot loader and flash a custom recovery" according to the lifehacker website I can't link because I'm a new user. (How to Flash a ROM to your Android Phone)
The thing is, how? I have no clue to do this because I (am totally guessing from my past experience) need to install TWRP so I can flash, but no root solution that I can come up with works. I am talking about Kingo Root, KingRoot, iRoot, RootGenius, and Framaroot. I am officially stuck.
If you want software configuration, tough luck. I know it runs "YunOS 3.2.0" but some root application (KingRoot?) saw it as an Android 5.1 device, which seems reliable due to the fact it can run APK files without issue. Again, the device is called the JD-PLUS. If you need more information, I'll be willing to do that.
I'm probably will be a sitting duck until KingRoot gets a strategy for this phone. 2258 people doesn't seem to be enough. Oh well. :silly:
Try asking your question here
http://forum.xda-developers.com/android/help
Good luck
First of all I need to preface this by saying I know nothing about rooting.
I have a Nokia 3, Model TA-1020, Android version 8.0.0 (which apparently is Oreo, even though I got this phone as a Nougat) and Android Security patch level May 5, 2018.
From all the research I attempted to do regarding rooting a Nokia 3, most times it would be for a specific model (which apparently is important) but never TA-1020 (the one I have).
So it makes me wonder if I can root my phone. I don't want to do anything serious, just to basically give root access to a couple of apps (from what I understand).
Any guidance would be helpful if it is possible.
MainGoldDragon said:
First of all I need to preface this by saying I know nothing about rooting.
I have a Nokia 3, Model TA-1020, Android version 8.0.0 (which apparently is Oreo, even though I got this phone as a Nougat) and Android Security patch level May 5, 2018.
From all the research I attempted to do regarding rooting a Nokia 3, most times it would be for a specific model (which apparently is important) but never TA-1020 (the one I have).
So it makes me wonder if I can root my phone. I don't want to do anything serious, just to basically give root access to a couple of apps (from what I understand).
Any guidance would be helpful if it is possible.
Click to expand...
Click to collapse
There is already a thread and tutorial on XDA for rooting the nokia 3 (TA1020 and TA1032) on Nougat 7.1.1 and Oreo 8.0.0
Here is the link.
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
The important stuff......
You have received an android 8.0 update - so your device is an Oreo device.
It does not matter what was on the device when you purchased it - for future reference, just quote your current android version - Never quote previous versions or what was on the device when you brought it, as I can guarantee someone will see NOUGAT in your post and assume you have a Nougat device.
(Things like that cause all sorts of confusion and issues here that if you was to follow the incorrect instructions you would brick your device and render it unusable)
I'm also using a Nokia 3 TA1020 on Oreo (8.0.0)
After reading the rooting thread I've decided not to proceed with rooting my own Nokia 3.
As the procedure isn't very clear and it seems many users have had issues afterwards.
If you know NOTHING about rooting I suggest you also stay well clear of trying to root your nokia 3 - it's a very complicated process that even I'm not confident enough to try - and believe me Ive rooted many devices in the past!
With the Nokia, it's not a case of flashing a file in a custom recovery to gain root - there are several things you must do using a PC and complicated button combinations and perfect timing.
You get any of this wrong or miss a step you have a rather useless paperweight rather than a Nokia phone and trying to root will invalidate and void any remaining warranty your device may have left.
Ask yourself why you need root?
If you root your device, you have to keep the system recovery as if you flash a custom recovery you won't receive any system updates.
Also if you do keep your system recovery and receive a system updates you have to go through the process of rooting all over again and system updates can then fail, as confirmed by users in the other thread......
Newer android versions (8.1 and 9.0) will also block some of things users get round using substratum and xposed.
These apps will be almost useless in android 9.0 because Google is taking away the ability for rooted devices to change system UIs and draw over any apps.
Most xposed modules will be obsolete.
Obviously what you do is your own choice, I'm just saying it's not for me and I really don't want to try.
There isn't not any real benefit from having a rooted device these days, especially on this device which looks so difficult to get rooted.
Obviously you don't have to take my word for it, just look at all the posts in the thread I've linked to you above of users who tried the rooting process and missed a step or didn't follow correct instructions or even in one case followed instructions for the wrong android version and wrong device and have now bricked their device and rendered it unusable.
In my opinion it's just not worth it as the risks involved outweigh any real benefit gained.
Regards
@bubba1601 one slight modification to your post, rooting won't stop you from receiving system updates - as long as you still have your stock recovery. That said I agree with you on everything else especially the fact that it's a lot of hassle. Even after you have rooted your phone, once you install an update you have to go through the whole process of rooting over again. Half the time, my system update fails. If you're not familiar with the process it can really be daunting
redweaver said:
@bubba1601 one slight modification to your post, rooting won't stop you from receiving system updates - as long as you still have your stock recovery. That said I agree with you on everything else especially the fact that it's a lot of hassle. Even after you have rooted your phone, once you install an update you have to go through the whole process of rooting over again. Half the time, my system update fails. If you're not familiar with the process it can really be daunting
Click to expand...
Click to collapse
Thank you for correcting me @redweaver.
I've edited my comments accordingly!
After reading the linked post It really doesn't give me any confidence to try it and I personally see no benefit from doing it.
redweaver said:
@bubba1601If you're not familiar with the process it can really be daunting
Click to expand...
Click to collapse
bubba1601 said:
In my opinion it's just not worth it as the risks involved outweigh any real benefit gained.
Click to expand...
Click to collapse
Thanks you both for all the advice you've given me and I want to ask 1 more thing:
If I mess up something during the rooting process, is my phone forever a brick or can I fix it with a factory reset of some kind ?
Because even if I can't fix it, I am still willing to give it a try since:
I got this phone for free. (literally $0, not that someone gifted it to me).
This is my secondary phone (I have a Windows Phone as my main).
I have sent this phone for repairs at least 4 times and it took 3 weeks to get it back each time and the problems return every time.
I have factory reset it 5 times so one more isn't going to be a problem.
It still has problems.
I am not really a phone person and only use it when I am outside of my house (something that doesn't happen often) and only for games.
So my biggest concern is if it is possible to reset my phone after not following an instruction properly. But even that isn't really going to stop as long as it is possible to root my phone since I had the impression that only certain models could get rooted so far.
MainGoldDragon said:
Thanks you both for all the advice you've given me and I want to ask 1 more thing:
If I mess up something during the rooting process, is my phone forever a brick or can I fix it with a factory reset of some kind ?
Because even if I can't fix it, I am still willing to give it a try since:
I got this phone for free. (literally $0, not that someone gifted it to me).
This is my secondary phone (I have a Windows Phone as my main).
I have sent this phone for repairs at least 4 times and it took 3 weeks to get it back each time and the problems return every time.
I have factory reset it 5 times so one more isn't going to be a problem.
It still has problems.
I am not really a phone person and only use it when I am outside of my house (something that doesn't happen often) and only for games.
So my biggest concern is if it is possible to reset my phone after not following an instruction properly. But even that isn't really going to stop as long as it is possible to root my phone since I had the impression that only certain models could get rooted so far.
Click to expand...
Click to collapse
Yes it's possible to restore the phone if something goes wrong, but not via the traditional factory reset proceedure.
I understand resetting if flashing goes wrong involves using PC software called "SP flash tool" to flash some system files.
This isn't done inside android from the phone, it's done with your Nokia plugged into a PC in fastboot / download mode, again, I'm not sure of this part and that's
the bit I'm not really understanding and why I'm very reluctant to do it.
As I said, the choice is yours, but bear in mind the author of the rooting thread has now moved to another device so will not be supporting the Nokia 3 or the Nokia 3 rooting thread.
Is nokia 3 TA-1020 ROOTABLE
Hello XDA Community,
I have an old tablet, the Huawei T1-701ua. In recent times I haven't used it as much, but it's because it's running slow.
I want to root it and repurpose it for something else, like a portable media device. Because this tablet is my only one with a moderately big screen. But I've been running into some issues.
The bootloader is locked with a code, that I just cannot unlock. It's argubly the dumbest system Huawei has invented for locking a bootloader. But even if I really was able to unlock it. What do I do with it? Paying a small fee for the code is okay.
And even if I went through all these roadblocks and successfully rooted my tablet, I can't see any officially supported custom roms/images for it, and I don't want to risk bricking it. I've wanted for a long time to install another OS on it, but I wasn't knowledgeable enough.
*I don't want to use Kingroot, Kingoroot, or other one tap root apps, since to me they seem unsafe, and it also makes this rooting process way less interesting*
So with this post, I am kindly asking anyone who sees this to answer a couple of questions, that will help me greatly.
1. Is it worth it to root, in order to remove all bloatware and make this tablet run better, or is there another way?
2. What do I do in order to unlock bootloader with the code?
3. Can I install a custom rom/image/OS through recovery, that isn't supported, and not get my tablet bricked? (eg. LineageOS, even if it's an older version)
I still haven't figured out how and with what exactly I will root my tablet eventually, but due to the lack of information about rooting this kind of tablet, and almost no custom rom developers including this tablet in their support list, I haven't decided.
I will greatly appreciate if anyone who does have information about this topic, link me to another forum post or etc. if this sort of stuff can be easily answered there.
Thanks in advance.
bump
Simple. No. It is not possible to install another OS. Most, if not all Huaweis, has 3 states only: EMUI, off and bricked.
Thanks for the reply! I guess Huaweis are just the worst devices for rooting/installing another OS. Bad luck I got right there.
I am not gonna root it, maybe just a factory reset and debloating wherever I can.
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!