First-Time Rooting - OnePlus 5 Questions & Answers

-Preface: I have never rooted an Android phone before. I really want to but I have questions/concerns that I want to address before I do so. My daily driver and the phone I want to root is a OnePlus 5 running Android 7.1.1 Nougat.
-I want to root my phone to learn how to root and gain the experience from it (one of the reasons I built my own PC, besides just having an amazing gaming PC), delete all the garbage apps that I can't uninstall or can only disable, I want access to the very useful apps only accessible with root access of a phone, etc.
-Is it safe to root an Android phone?
-How do I root my phone?
-Should I be installing any antivirus/anti-malware software to plug security problems that comes with rooting an Android device? (I currently have Malwarebytes Pro; I was grandfathered in so I don't need to pay for it.)
-Here are some apps that I plan on using with my rooted phone (these either require rooting or significantly benefit from it): Oxygen Updater, Greenify, Sixaxis Controller, SuperSU, Titanium Backup, system app remover, Flashfire, Keepass2 USB Keyboard Plugin, Flashify, Lucky Patcher, Adaway, Game hacker app (Freedom APK?)
-Are there any other apps that you can suggest that I use with a rooted Android phone?
-Will OTA updates still work? I would absolutely hate having to re-root every single time OnePlus releases an update. (I think Oxygen Updater and Flashfire might be able to solve this problem.)
-I'm not sure if all of my concerns/questions that I have are laid out here but I would love all feedback, responses, and additional concerns you may raise with rooting. Thanks so much!
This looks like the page I might be looking for as to how to root the OnePlus 5: https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877. Not sure what any of the terminology means at the moment, but when/if I'm ready to root, this seems like the place to do it.

Ah safe as houses these days xD, just make sure your on the latest OOS firmware and follow that guide you've linked. You learn from your mistakes and just remember you've got a team of people willing to help you out with any issues if you do mess up

blackcell1 said:
Ah safe as houses these days xD, just make sure your on the latest OOS firmware and follow that guide you've linked. You learn from your mistakes and just remember you've got a team of people willing to help you out with any issues if you do mess up
Click to expand...
Click to collapse
Does rooting completely wipe the phone of all its data? If so, how do I ensure it's all backed up in case something goes wrong? All my important things (my files: images, videos, etc.) are uploaded to cloud services (Google Drive and Microsoft OneDrive), so I won't lose any of that stuff, but I absolutely (1) cannot brick my phone, and (2) I don't want to have to, in case something goes wrong, reinstall all my apps, sign into them again, change the settings to the way I like, etc.

FamilyGuy0395 said:
Does rooting completely wipe the phone of all its data? If so, how do I ensure it's all backed up in case something goes wrong? All my important things (my files: images, videos, etc.) are uploaded to cloud services (Google Drive and Microsoft OneDrive), so I won't lose any of that stuff, but I absolutely (1) cannot brick my phone, and (2) I don't want to have to, in case something goes wrong, reinstall all my apps, sign into them again, change the settings to the way I like, etc.
Click to expand...
Click to collapse
The root process itself does not wipe anything. But you have to unlock your bootloader first, and this will inevitably wipe everything on your phone including internal storage.
So any apps you have installed so far (and their settings) will be lost unless that app has some export settings feature. Nothing you can do about it now.
All the steps necessary for unlocking and rooting can be found at the link you posted. I followed the same guide and I'm good to go and had no problems.
Rooted or unrooted, an antivirus is optional and it's up to you if you want one. I personally don't use one.

Pwnycorn said:
The root process itself does not wipe anything. But you have to unlock your bootloader first, and this will inevitably wipe everything on your phone including internal storage.
So any apps you have installed so far (and their settings) will be lost unless that app has some export settings feature. Nothing you can do about it now.
All the steps necessary for unlocking and rooting can be found at the link you posted. I followed the same guide and I'm good to go and had no problems.
Rooted or unrooted, an antivirus is optional and it's up to you if you want one. I personally don't use one.
Click to expand...
Click to collapse
What is SafetyNet? Does it have anything to do with Google Play apps passing some sort of security test in order for them to function/open? How do I not lose access to some apps (like Android Pay is one of them that I have heard) that fail this SafetyNet test?

FamilyGuy0395 said:
What is SafetyNet? Does it have anything to do with Google Play apps passing some sort of security test in order for them to function/open? How do I not lose access to some apps (like Android Pay is one of them that I have heard) that fail this SafetyNet test?
Click to expand...
Click to collapse
Yes, that's it. Pokémon GO and Mario Run are other two examples.
You can bypass it with Magisk, but it's never forever as SafetyNet gets updated and then you have to wait for Magisk to get updated. It's a never-ending cat and mouse game.

Ugh, that's an unbelievable pain in the ass... I don't get why people who root their phones have all these extra burdens. I want to root my phone really badly but with all these hurdles I honestly am not sure if it's worth it.
Are there any other apps I haven't mentioned or any other root benefits any of you guys can mention to persuade me in the direction of rooting?

FamilyGuy0395 said:
Ugh, that's an unbelievable pain in the ass... I don't get why people who root their phones have all these extra burdens. I want to root my phone really badly but with all these hurdles I honestly am not sure if it's worth it.
Are there any other apps I haven't mentioned or any other root benefits any of you guys can mention to persuade me in the direction of rooting?
Click to expand...
Click to collapse
Simply being able to delete applications that I don't want got me into rooting. I cannot persuade, but if the SafetyNet thing is something that is going to hold you back because you use those applications then it's up to you. I know people that have rooted phones and manage with Magisk as a workaround, but yes it's a cat and mouse deal in the end. The ability to flash custom kernels and customize the UI (through substratum or custom ROM) is also a plus! ?

I think you should root only if you have time to learn about android OS, rooting your phone will grants you the full access for everything and you'll have full control in it... Then there are some apps or mods that requires rooted phone (substratum for theming is AMAZING) but here it's up to you... The question is, what you want to do with your phone? If you like/want to have complete control over it and a lot of feature then install a custom rom

God damnit I'd love to root but the more research I do into SafetyNet rooting just seems not even worth it if I have to keep losing access to apps I use...
The reasons I want to root basically boil down to me wanting to trash garbage apps I don't use and can't uninstall and to install cool apps that require root access.

SafetyNet is not important in my opinion.. I've used Android rooted with supersu (no SafetyNet) for years and I've never miss anything..

Is that app list I have above include useful apps, in your opinion? Are any of them redundant? Any other ones I shouldn't miss out on?

A few banking apps use safetynet. If it's vitallyimportant youhave a banking app working, keep in mind you can still access through internet, then this can be a deal breaker...
I think you're going to find most people here are pro root as this is a developers forum - so saying, it opens up a world of ease with which to do things that aren't available to most people and allows you to do things they can't, nerd cool factor high...

FamilyGuy0395 said:
God damnit I'd love to root but the more research I do into SafetyNet rooting just seems not even worth it if I have to keep losing access to apps I use...
The reasons I want to root basically boil down to me wanting to trash garbage apps I don't use and can't uninstall and to install cool apps that require root access.
Click to expand...
Click to collapse
just youtube the process

FamilyGuy0395 said:
God damnit I'd love to root but the more research I do into SafetyNet rooting just seems not even worth it if I have to keep losing access to apps I use...
The reasons I want to root basically boil down to me wanting to trash garbage apps I don't use and can't uninstall and to install cool apps that require root access.
Click to expand...
Click to collapse
In the past I used to always root but to me it's not worth it anymore. To me AP is incredibly convenient. Not willing to play cat and mouse with it. This phone doesn't really have bloat and tethering works flawlessly for
me. Tethering and AP are two of the most important features for me.

Related

[Q] A few questions on rooting

Hello,
It's been a long time since I rooted a device.So please be patient.
I want to root the tablet because I need open vpn connectivity and I don't need a custom ROM because I am mainly using it as a media consumption device.
Does rooting automatically mean flashing a custom recovery(CWM) Is it possible to root without flashing one(I feel stupid asking this I remember flashing CWM every time I root a Android device.)
I have heard that there are some bugs in CWM for Nexus 10.
Thanks
siddardhab said:
Hello,
It's been a long time since I rooted a device.So please be patient.
I want to root the tablet because I need open vpn connectivity and I don't need a custom ROM because I am mainly using it as a media consumption device.
Does rooting automatically mean flashing a custom recovery(CWM) Is it possible to root without flashing one(I feel stupid asking this I remember flashing CWM every time I root a Android device.)
I have heard that there are some bugs in CWM for Nexus 10.
Thanks
Click to expand...
Click to collapse
Well I like to think Android is Linux; which it basically is. It gives you access to system files and delve deeper than what you can normally access. superuser access more or less. You can install custom ROMs AFTER you are rooted. That's pretty much it. Also, no rooting doesn't automatically flashing a custom recovery.
A custom recovery is just a custom recovery that you can flash through fastboot..for a plethora of different functions which cannot be done easily with the stock recovery. Which is..another method of customizing and accessing your phone...since this can go on for a long time I'm just going to stop and add that you're better off reading and learning stuff before trying to do any of it though.
Good luck!
I've never quite got an answer to this: does rooting automatically ends warranty? What is Samsung's official take? Does unrooting work and can I cover traces? I only want rooting for adblocking and USB OTG, but now risking warranty.
I don't think rooting a device voids any warranty. You can always lock the bootloader and reflash the stock image and it's as if nothing ever happened.
If it were to void the warranty, Google wouldn't have made it easy to unlock the bootloader and root. If you tamper with with hardware in the device then yes it will void your warranty.
So basically, what is the point of rooting the device?
realyweely said:
So basically, what is the point of rooting the device?
Click to expand...
Click to collapse
Personally I'd do that fro adblocking and external storage mounting, if it doesn't require messing with the ROM which I'd prefer not to.
what kind of adblocking just out of interest? is it possible to get something like adfender for portable devices?
AdAway is a popular app, dunno of compatible with the N10 just yet.
Rooting allows you to freeze apps that you don't want to keep them form wasting resources, freeze & hide apps you do not want the kids to use, back up apps & data plus entire system just in case you accidentally do something stupid. Then there is AdFree to block ads. Plus, if you get bored in the future you can jump into ROM flashing.
siddardhab said:
I want to root the tablet because I need open vpn connectivity and I don't need a custom ROM because I am mainly using it as a media consumption device.
Click to expand...
Click to collapse
'OpenVPN for Android' (by Arne Schwabe) does not need root (btw I do not own a nexus 10 to check if it works on it)

Has rooting been worth it to you guys?

I have a sprint s4, thinking off rooting.
Has it been worth it to do this, please tell me why you did it.
I use Nova instead of tw but I don't care for the extra programs and I want to block ads on my browser.
Thinking of a asop rom.
If you are "thinking about rooting" the phone, without clear knowledge why would you NEED it - DO NOT ROOT.
rooting is for the peoples who know what they want , why they want it and how to do it.
sah0724 said:
I have a sprint s4, thinking off rooting.
Has it been worth it to do this, please tell me why you did it.
I use Nova instead of tw but I don't care for the extra programs and I want to block ads on my browser.
Thinking of a asop rom.
Click to expand...
Click to collapse
Give a change to THIS program. It no void ur warranty (KNOX 0x0)
Yes rooting for me has been worthwhile.
I root so I can:
Disable ads in browser
Disable exchange policy so I don't get the annoying security screen all the time
XPrivacy a valuable tool to control permissions for apps
Root explorer, so I can control all aspects of the system
Tweaks using Xposed module to control and change aspects of the OS
I can control what apps start up when my phone boots using Xposed module Boot Manager
Those are just some examples. For me I've rooted all my Android devices present and past and will continue to do so in the future, :good:
11 5986438
Can't think of a life before root
I started rooting my old HTC Desire and haven't stopped yet (on a Galaxy S4 now)
The two biggest for a normal user is
Adblock
Bloatware removal
So if you feel comfortable with the process, Go for it!
/Jörgen
Just make sure you setup your favorite custom recovery ...
With it you can backup and restore within few minutes
, even you can flash superuser or what ever as a zip file to gain root access with custom recovery
And it stays even if root access removed
You can go back to stock recovery by flashing it through odin easily
Sent from dish washer
If you can't answer the question 'Why do I want to root my phone' without other people's input, you really want to consider not messing with your phone in the first place.
The most important part is (is earlier said):
Create a nand backup!
Create a nand backup!
Without that you will cry some
/Jörgen

Rooting implications?

I read that for sure you lose Android Pay. Some posts talk about losing the Fingerprint scanner too.... Is this accurate? Maybe it works for the lockscreen, but does the fp scanner work within all apps, including play store for purchases on a rooted device?
The next question I have is, is it possible to undo all of this and go back to stock, with everything functioning the way it did?
Does it matter what type of root you use? If I don't use systemless root, it's it fine?
I don't know the answer to most of your questions as I'm not one with experience, but I did run across youtube video explaining the rooting process and I also checked out the guy's site. He says that it's reversible.
/nexus-6p-root-news/why-root-the-nexus-6p (I ommitted the url of nexus6proot due to being a new member and not allowed to post links, but a simple search will get you to the page.
dreamtheater39 said:
I read that for sure you lose Android Pay. Some posts talk about losing the Fingerprint scanner too.... Is this accurate? Maybe it works for the lockscreen, but does the fp scanner work within all apps, including play store for purchases on a rooted device?
The next question I have is, is it possible to undo all of this and go back to stock, with everything functioning the way it did?
Does it matter what type of root you use? If I don't use systemless root, it's it fine?
Click to expand...
Click to collapse
Neither the traditional or systemless root method prevent the fingerprint scanner from working. You can use Android Pay with systemless root.
Going back to stock is very easy, you just flash the factory images.
The type of root your use is up to you, if you want to use Android Pay functionality then use systemless, otherwise just use traditional.
My guide contains all the instructions you'll ever need:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I just finally rooted today. I used systemless root method. Everything works just fine so far. Android pay works, encryption and fingerprint works.
Android pay will work unless you alter system partition. For now all I want is to edit doze settings and have titanium backup. So everything works great.
A custom ROM however would break android pay.
RogerPodacter said:
A custom ROM however would break android pay.
Click to expand...
Click to collapse
Cataclysm ROM will not break android pay. As long as you use the systemless root. :good: He approaches his ROM build in a whole different way.

Root first or update first?

Hello everyone,
My Moto X Pure edition is on the way on the mail. I'm already excited to root it and get twrp on it. However, I believe the phone will come with android lollipop installed, and I should get an option for an OTA update for android 6.0.
My question is: Should I root my phone and install twrp BEFORE receiving the update, or after? I plan to use WinDroid Toolkit to root my phone and install twrp (seems to be the easiest way) so have any of you done it while having 6.0 already installed?
Your phone will most likely arrive with 6.0 pre-installed on it. You can't take an OTA with TWRP installed. I can't answer the WinDroid question.
Edit: It will most likely come with 6.0 already assuming you purchased it from Motorola.
quakeaz said:
Your phone will most likely arrive with 6.0 pre-installed on it. You can't take an OTA with TWRP installed. I can't answer the WinDroid question.
Edit: It will most likely come with 6.0 already assuming you purchased it from Motorola.
Click to expand...
Click to collapse
Thanks a lot for your help! It's good that the phone will most likely come with MM. Does Motorola also offer an OTA update to 6.0.1?
I wanted to flash a pre-rooted stock-based ROM because I thought it would be easier to get root. Although, my preference really would be to get the stock update, then just root that. The only reason I wanted to flash an already rooted ROM was because it seems kind of tricky to root it haha. Is the systemless root by ivcarlos the easiest way to root MM? Or have you perhaps found another way to root it on MM?
Additionally, just to make sure before I go on with anything: I should first let the clean phone upgrade to android 6.0.1, AFTER that I should unlock the bootloader, followed by installing TWRP and root, correct? @vertigo_2_20
Thank you for any help you can give me!
Henryy97 said:
Thanks a lot for your help! It's good that the phone will most likely come with MM. Does Motorola also offer an OTA update to 6.0.1?
I wanted to flash a pre-rooted stock-based ROM because I thought it would be easier to get root. Although, my preference really would be to get the stock update, then just root that. The only reason I wanted to flash an already rooted ROM was because it seems kind of tricky to root it haha. Is the systemless root by ivcarlos the easiest way to root MM? Or have you perhaps found another way to root it on MM?
Additionally, just to make sure before I go on with anything: I should first let the clean phone upgrade to android 6.0.1, AFTER that I should unlock the bootloader, followed by installing TWRP and root, correct? @vertigo_2_20
Thank you for any help you can give me!
Click to expand...
Click to collapse
IIRC, that's how I did it (OTA 6.0.1 > unlock bootloader > flash TWRP > root), though I did miss some things along the way that I only found out about after the fact, so I've included warnings about those thing here. Before I rooted, I read the following (and a LOT more, but these are the primary ones I based how I did it on):
ivcarlos' method, which you mentioned
And this, which is what I followed for rooting, though I don't remember why. I also had to use 2.62-3 as mentioned in the instructions vs 2.65 which is mentioned at the end as verified working, since it didn't work for me.
I ran across this as well, probably when 2.65 didn't work, and there's some good tidbits in there, worth reading through.
I also found this, but only after I finished rooting with the other method, and I didn't have the time to mess with it. I don't know enough to say whether it's really a better method or not, but something worth checking out if you have the time.
Just make sure you backup anything you want to keep (phone log, texts, pictures, etc) before unlocking the bootloader. I recommend SMS Backup & Restore with Titanium Backup as a secondary backup. Then, use fastboot to back up your recovery before flashing TWRP (I didn't know to do this until too late). Also, make sure you back up your /system and /boot partitions (don't need /data, since you're dealing with a freshly wiped phone from unlocking the bootloader, so nothing there to back up) with TWRP (and store the backups on the external SD card and/or your computer) as soon as you get TWRP flashed, before you do anything else.
Remember, anything you do that modifies /system can potentially break the "systemless" aspect of this root, thereby breaking Android Pay as well as the ability to receive OTA updates. Examples of things that might do this are AdAway (there's apparently a systemless file that needs to be flashed before installing it, which I didn't realize until too late, so mine may be broken already) and battery apps like GSam and BetterBatteryStats. I've yet to get an answer on if these really do break it, though. One that definitely will is Xposed, but I just found there's a systemless version, so when I get time I plan on trying that out. I think even if you do break it you can just a) reflash your backup (/recovery, /boot, & /system) then take an OTA and reflash TWRP and re-root, or b) flash the updated partitions from the OTA then reflash recovery and re-root. Of course, any of those things that changed /system (AdAway, Xposed, battery apps, etc), will probably be broken by this, and I believe they're supposed to be uninstalled first and reinstalled after.
I wouldn't doubt if I've screwed something up, so hopefully somebody can correct me on anything I did, as well as provide more information regarding the breaking of systemless.
vertigo_2_20 said:
IIRC, that's how I did it (OTA 6.0.1 > unlock bootloader > flash TWRP > root), though I did miss some things along the way that I only found out about after the fact, so I've included warnings about those thing here. Before I rooted, I read the following (and a LOT more, but these are the primary ones I based how I did it on):
ivcarlos' method, which you mentioned
And this, which is what I followed for rooting, though I don't remember why. I also had to use 2.62-3 as mentioned in the instructions vs 2.65 which is mentioned at the end as verified working, since it didn't work for me.
I ran across this as well, probably when 2.65 didn't work, and there's some good tidbits in there, worth reading through.
I also found this, but only after I finished rooting with the other method, and I didn't have the time to mess with it. I don't know enough to say whether it's really a better method or not, but something worth checking out if you have the time.
Just make sure you backup anything you want to keep (phone log, texts, pictures, etc) before unlocking the bootloader. I recommend SMS Backup & Restore with Titanium Backup as a secondary backup. Then, use fastboot to back up your recovery before flashing TWRP (I didn't know to do this until too late). Also, make sure you back up your /system and /boot partitions (don't need /data, since you're dealing with a freshly wiped phone from unlocking the bootloader, so nothing there to back up) with TWRP (and store the backups on the external SD card and/or your computer) as soon as you get TWRP flashed, before you do anything else.
Remember, anything you do that modifies /system can potentially break the "systemless" aspect of this root, thereby breaking Android Pay as well as the ability to receive OTA updates. Examples of things that might do this are AdAway (there's apparently a systemless file that needs to be flashed before installing it, which I didn't realize until too late, so mine may be broken already) and battery apps like GSam and BetterBatteryStats. I've yet to get an answer on if these really do break it, though. One that definitely will is Xposed, but I just found there's a systemless version, so when I get time I plan on trying that out. I think even if you do break it you can just a) reflash your backup (/recovery, /boot, & /system) then take an OTA and reflash TWRP and re-root, or b) flash the updated partitions from the OTA then reflash recovery and re-root. Of course, any of those things that changed /system (AdAway, Xposed, battery apps, etc), will probably be broken by this, and I believe they're supposed to be uninstalled first and reinstalled after.
I wouldn't doubt if I've screwed something up, so hopefully somebody can correct me on anything I did, as well as provide more information regarding the breaking of systemless.
Click to expand...
Click to collapse
Thank you for your reply! I'll read the links you sent me, although from what I can see the "root done right" is for the nexus 6, and if it works for the moto x pure it doesn't seem to be overall that much beneficial over the systemless root.
What exactly is the effect of breaking the "systemless" aspect of the root? For example, if I install AdAway, what will happen? I didn't really get that from your post.
Perhaps after all this process, I'll write a how-to guide, heh
So according to your experience, SUPERSU 2.62-3 is the adequate version to use for android 6.0.1?
Thanks again!
Henryy97 said:
Thank you for your reply! I'll read the links you sent me, although from what I can see the "root done right" is for the nexus 6, and if it works for the moto x pure it doesn't seem to be overall that much beneficial over the systemless root.
What exactly is the effect of breaking the "systemless" aspect of the root? For example, if I install AdAway, what will happen? I didn't really get that from your post.
Perhaps after all this process, I'll write a how-to guide, heh
So according to your experience, SUPERSU 2.62-3 is the adequate version to use for android 6.0.1?
Thanks again!
Click to expand...
Click to collapse
My understanding is that breaking it will render Android Pay inoperable and will make it so you can't take an OTA, though as I mentioned, it seems you still can by reverting back, it's just a LOT more work. But again, as I said, I'm not completely sure and I haven't been able to get an answer.
As for the supersu version, it doesn't really matter, because you'll just update it once you're rooted and booted into the OS. I just found that, despite what that post said, 2.65 did not work for me, so I had to flash 2.62-3 which did. Not a big deal, was just a little frustrating and scary when 2.65 didn't work because I was worried that I broke something and that the method wasn't going to work.
Edit: Good catch BTW on the link having to do with the Nexus. I didn't even look at what sub-forum it was in. At least it's one less thing to worry about for now, though I do hope it spreads to more devices, because we could always use more, not to mention better (assuming it is) ways of doing things.
vertigo_2_20 said:
My understanding is that breaking it will render Android Pay inoperable and will make it so you can't take an OTA, though as I mentioned, it seems you still can by reverting back, it's just a LOT more work. But again, as I said, I'm not completely sure and I haven't been able to get an answer.
As for the supersu version, it doesn't really matter, because you'll just update it once you're rooted and booted into the OS. I just found that, despite what that post said, 2.65 did not work for me, so I had to flash 2.62-3 which did. Not a big deal, was just a little frustrating and scary when 2.65 didn't work because I was worried that I broke something and that the method wasn't going to work.
Edit: Good catch BTW on the link having to do with the Nexus. I didn't even look at what sub-forum it was in. At least it's one less thing to worry about for now, though I do hope it spreads to more devices, because we could always use more, not to mention better (assuming it is) ways of doing things.
Click to expand...
Click to collapse
Thanks. I am aware that you can revert back to lollipop, and do the update from there whenever you want to update to a newer OTA MM update. However, my real question is, what does it mean to break the systemless aspect? I know that it will prevent further OTA updates, but will xposed work as it should, etc? If I am rooting my device, it's really to get xposed. So, if it means that I must revert to an unrooted stock rom everytime I wanna update, then so be it. I just want to make sure that breaking the systemless root aspect will not make the ROM unstable. Will it?
Henryy97 said:
Thanks. I am aware that you can revert back to lollipop, and do the update from there whenever you want to update to a newer OTA MM update. However, my real question is, what does it mean to break the systemless aspect? I know that it will prevent further OTA updates, but will xposed work as it should, etc? If I am rooting my device, it's really to get xposed. So, if it means that I must revert to an unrooted stock rom everytime I wanna update, then so be it. I just want to make sure that breaking the systemless root aspect will not make the ROM unstable. Will it?
Click to expand...
Click to collapse
I think you'll find all the info you're looking for and more in those links. But in summary, as I said, AFAIK the only consequence is breaking OTAs. It does not prevent you from using xposed, rather xposed is one of the things that breaks it. Systemless is so called because it roots without affecting the /system partition, therefore preventing the breaking of Android Pay and allowing OTAs. Once /system is modified (unclear if at all or just beyond a point), these two will no longer function. So if you "break" the systemless root by doing stuff that modifies /system (i.e. xposed, etc), you basically now have a standard (non-systemless) root, which simply negates the benefits it provides. But as far as I could tell, systemless is the only option anyway, so you just do it since it works and it's easy, then you either are careful not to break it if Pay/OTAs are important to you, or if you don't care about those then you just do whatever you want just as if you were rooted in the traditional way. But as I said, once I get the time, I plan to try out the systemless xposed, though it may not matter since I might have already broken it, but may as well, and maybe it'll mean not having to uninstall it when it comes time to take an OTA. If you play with it and figure it out, let me know.
vertigo_2_20 said:
I think you'll find all the info you're looking for and more in those links. But in summary, as I said, AFAIK the only consequence is breaking OTAs. It does not prevent you from using xposed, rather xposed is one of the things that breaks it. Systemless is so called because it roots without affecting the /system partition, therefore preventing the breaking of Android Pay and allowing OTAs. Once /system is modified (unclear if at all or just beyond a point), these two will no longer function. So if you "break" the systemless root by doing stuff that modifies /system (i.e. xposed, etc), you basically now have a standard (non-systemless) root, which simply negates the benefits it provides. But as far as I could tell, systemless is the only option anyway, so you just do it since it works and it's easy, then you either are careful not to break it if Pay/OTAs are important to you, or if you don't care about those then you just do whatever you want just as if you were rooted in the traditional way. But as I said, once I get the time, I plan to try out the systemless xposed, though it may not matter since I might have already broken it, but may as well, and maybe it'll mean not having to uninstall it when it comes time to take an OTA. If you play with it and figure it out, let me know.
Click to expand...
Click to collapse
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Henryy97 said:
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Click to expand...
Click to collapse
I bought my phone ~5-6 months ago. When I got it, the MM update was waiting (released late last year). Probably ~2 months later, another update came through. Since then, nothing. So it looks like probably 3 maybe 4 a year. I'd rather be rooted with all the benefits than get a small update, though I'd really rather have both.
6.0.1 is not out yet although there is a reteu version posted which works great. Rooting is as simple flashing su 2.62-3 with twrp.
lafester said:
6.0.1 is not out yet although there is a reteu version posted which works great. Rooting is as simple flashing su 2.62-3 with twrp.
Click to expand...
Click to collapse
I'll check it out. Do you mind sharing the link to that version just in case? I am very confused now though, because @vertigo_2_20 says he has 6.0.1, and you say you didn't get it. Perhaps location matters? Can you elaborate a little bit more?
And actually, I've just realized: I think I was looking at too many outdated posts perhaps with all the complicated root procedures such as the one by ivcarlos. The guide that amit.lohar made is very simple which is the one vertigo kindly shared in this OP. One final question @vertigo_2_20 (sorry for so many questions). Does the method by amit.lohar work for 6.0 anddd 6.0.1? I would assume so since they're pretty much very similar. What is your take on this?
I assumed I was on 6.0.1 because I received a system update after being on MM, so I don't know what else it could be. Though it does just say 6.0 in settings. Regardless, I only did it a few weeks ago, so if you're fully updated, you'll be the same as what I was. Even if not, I would think it wouldn't matter. As long as you do a back up before messing with things, worse case scenario is you screw something up and restore the backup.
Henryy97 said:
I'll check it out. Do you mind sharing the link to that version just in case? I am very confused now though, because @vertigo_2_20 says he has 6.0.1, and you say you didn't get it. Perhaps location matters? Can you elaborate a little bit more?
And actually, I've just realized: I think I was looking at too many outdated posts perhaps with all the complicated root procedures such as the one by ivcarlos. The guide that amit.lohar made is very simple which is the one vertigo kindly shared in this OP. One final question @vertigo_2_20 (sorry for so many questions). Does the method by amit.lohar work for 6.0 anddd 6.0.1? I would assume so since they're pretty much very similar. What is your take on this?
Click to expand...
Click to collapse
No I don't get links for people... this forum is small and easy to read. Dev section has one pre loaded with franken and there are two threads in general.
Henryy97 said:
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Click to expand...
Click to collapse
If receiving the OTA updates is something you really want, systemless root will allow you to get them with a lot less effort. The trick is knowing which of the apps that require root privileges will end up modifying your system. Avoid the ones that will and you can enjoy root with less work to get updates. If the only root required apps you are interested in modifies the system, then it will be a matter of what you value more.
Sent from my awesome phone!
That reminds me of another thing I haven't yet figured out. If /system is modified, I'm assuming the OTA will still show up and just won't install, but I wonder if it won't even show up anymore. Anyone know?
aybarrap1 said:
If receiving the OTA updates is something you really want, systemless root will allow you to get them with a lot less effort. The trick is knowing which of the apps that require root privileges will end up modifying your system. Avoid the ones that will and you can enjoy root with less work to get updates. If the only root required apps you are interested in modifies the system, then it will be a matter of what you value more.
Sent from my awesome phone!
Click to expand...
Click to collapse
Ahhh! I guess I'll just flash ROMS to update my phone then because I need my xposed Besides, after 6.0, if we want root, we can only get the systemless one anyway, right?
Also, I did not quite understand something about systemless root. If the root is 'systemless', then how can apps still edit the system? I've read up that after a memory wipe, the root will actually go away but what happens if I have apps that already modified the system? I just don't quite get how the apps can get into the system and modify it, if the root itself cannot do that because it is systemless. Am I getting the wrong idea here? I've read, and read, and read. I can't find an answer to that :/ According to what you have said though, if I were to get an app that modifies the system, then it would essentially *break* the systemless aspect of it, right? Therefore, it just becomes a normal root?
I feel like I'm going in circles now so I hope someone will be able to explain this for me or just point me in the right direction!
Systemless root does not mean root doesn't have access to /system, it simply means a way of gaining root access without modifying the /system partition, because if you gain root with the old methods, which DO modify /system, it breaks Android Pay and OTAs. Root still has access to modify system, hence why you have to be careful in installing apps, xposed, etc, because if they have root access, they can modify it, and if they do, your systemless root just became useless. The whole point is to NOT modify it so as to keep those certain functions intact, but it doesn't prevent you from doing so after gaining root.
vertigo_2_20 said:
Systemless root does not mean root doesn't have access to /system, it simply means a way of gaining root access without modifying the /system partition, because if you gain root with the old methods, which DO modify /system, it breaks Android Pay and OTAs. Root still has access to modify system, hence why you have to be careful in installing apps, xposed, etc, because if they have root access, they can modify it, and if they do, your systemless root just became useless. The whole point is to NOT modify it so as to keep those certain functions intact, but it doesn't prevent you from doing so after gaining root.
Click to expand...
Click to collapse
My experience was rooting 5.1.1 on the new phone. I backed up at every stage. I tried a few roms, no big deal. I liked 5.1.1 better due to micro sd card usage. I stupidly allowed the OTA to attempt to install. I knew it would fail but hoped it would stop nagging. The result I did not expect was phone continually rebooting on its own, trying to complete the update. After it completed the reboot it would start to shut down and begin the reboot process again. I restored a backup and froze the Motorola Update app with Titanium Backup. Problem solved. Don't do what I did!
Why would you want to stay on L? M is so much better. Between Doze and permission control, you'll have better battery life and more privacy and security. Not to mention the increased security from having more up-to-date software. I'd recommend just taking the update.

What do I lose if I root my device?

*I know this must have been answered before, I am sorry for playing the newbie, but I couldn't find this anywhere.
I need to know exactly what is at stake for rooting my device, what would I lose access to, and what not.
I've read somewhere that you lose DRM or something like that, is that meaning I will not be able to watch Netflix download and go, or Google Play Music, etc? what does it means?
LionLorena said:
*I know this must have been answered before, I am sorry for playing the newbie, but I couldn't find this anywhere.
I need to know exactly what is at stake for rooting my device, what would I lose access to, and what not.
I've read somewhere that you lose DRM or something like that, is that meaning I will not be able to watch Netflix download and go, or Google Play Music, etc? what does it means?
Click to expand...
Click to collapse
You will lose your warranty because you have to unlock your bootloader but if anything goes wrong you can always relock your bootloader and take your phone to a service center and claim your warranty they don't even check it in most cases other than that everything works fine
Sent from my Moto G4 Plus using Tapatalk
prajwal2001 said:
You will lose your warranty because you have to unlock your bootloader but if anything goes wrong you can always relock your bootloader and take your phone to a service center and claim your warranty they don't even check it in most cases other than that everything works fine
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
LionLorena said:
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
Click to expand...
Click to collapse
Nothing else only warranty
Sent from my Moto G4 Plus using Tapatalk
LionLorena said:
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
Click to expand...
Click to collapse
Provided you're still on the stock ROM, I don't think rooting affects your anti-theft protection (I recall it's called Factory Reset Protection?). Even if you've enabled OEM unlocking in Developer Options, someone resetting your phone would still need your Google credentials to use the device. Also, if you're logged into your device at the time, you could still locate and wipe your phone via Android Device Manager.
Of course, with an unlocked bootloader and custom recovery (as is generally required to root), someone could still flash a custom ROM and bypass those protections and, also, could in theory still access your data. (but only if they have physical access to your device)
As for DRM, I'm not sure but some apps have been/are now detecting the presence of root and will refuse to work (Snapchat, Pokemon Go, some banking apps come to mind) or for other devices, Android Pay and other security dependent features may not work. I recall magisk, a root manager, does have the ability to mask root from those apps, as well as pass SafetyNet, which is Google's security/anti-tamper detection. Your experience may vary. However, some apps require root access to function properly (e.g. kernel managers, battery monitors) just as to how they function, it's entirely up to you if you see yourself using those rooted apps on a regular enough basis. The root managers available (e.g. SuperSU, magisk) are supported and work well, just ensure you're using the latest versions, and if you're on stock Nougat, to flash a custom kernel prior to rooting (since the stock kernel won't permit modifications, if I recall).
Overall, in my view, you're trading security and warranty (as mentioned by prajwal2001) for convenience/flexibility by rooting - the flexibility alone to flash what you wish is what interested me in rooting my device, if anyone else has any other comments, feel free to add.
echo92 said:
Provided you're still on the stock ROM, rooting shouldn't disable your anti-theft protection (which I recall is Factory Reset Protection). Even if you've enabled OEM unlocking in Developer Options, someone resetting your phone would still need your Google credentials to use the device. Of course, with an unlocked bootloader and custom recovery (as is generally required to root), someone could still flash a custom ROM and bypass those protections and, also, could in theory still access your data. (but only if they have physical access to your device)
As for DRM, I'm not sure but some apps have been/are now detecting the presence of root and will refuse to work (Snapchat, Pokemon Go, some banking apps come to mind) or for other devices, Android Pay and other security dependent features may not work. I recall magisk, a root manager, does have the ability to mask root from those apps, as well as pass SafetyNet, which is Google's security/anti-tamper detection. Your experience may vary. However, some apps require root access to function properly (e.g. kernel managers, battery monitors) just as to how they function, it's entirely up to you if you see yourself using those rooted apps on a regular enough basis. The root managers available (e.g. SuperSU, magisk) are supported and work well, just ensure you're using the latest versions, and if you're on stock Nougat, to flash a custom kernel prior to rooting (since the stock kernel won't permit modifications, if I recall).
Overall, in my view, you're trading security and warranty (as mentioned by prajwal2001) for convenience/flexibility by rooting - the flexibility alone to flash what you wish is what interested me in rooting my device, if anyone else has any other comments, feel free to add.
Click to expand...
Click to collapse
Hm I see.
That's a pretty big downside
I guess I will pass root for now, I was only wanting to do to use the ADB via USB OTG and boot disk creator.
Thanks everyone for all the information!
LionLorena said:
Hm I see.
That's a pretty big downside
I guess I will pass root for now, I was only wanting to do to use the ADB via USB OTG and boot disk creator.
Thanks everyone for all the information!
Click to expand...
Click to collapse
That's fair enough - there's nothing stopping you from rooting your device, then performing what you need, before unrooting your device. (Just curious, does what you want to do require root, or are there other non-root methods?)
However, this will still involve you voiding your warranty (via unlocking your bootloader), and may also involve re-flashing your stock firmware to remove the custom recovery (and relock your bootloader, if you wish, though this won't recover your warranty, sadly). Honestly though, it's your device, up to you what you wish to do
echo92 said:
That's fair enough - there's nothing stopping you from rooting your device, then performing what you need, before unrooting your device. (Just curious, does what you want to do require root, or are there other non-root methods?)
However, this will still involve you voiding your warranty (via unlocking your bootloader), and may also involve re-flashing your stock firmware to remove the custom recovery (and relock your bootloader, if you wish, though this won't recover your warranty, sadly). Honestly though, it's your device, up to you what you wish to do
Click to expand...
Click to collapse
Yeah the warranty is not on top of my mind right now, my concern are the other issues it may cause, such apps not working, and security issues.
Like, I had a Sony Xperia Play back some years and past a week I root it, and past 2 weeks it was on Cyanogenmod.
I had Bricked that device countless times and had somehow fixed, I had also replaced several internal components as well, but back then there were no DRM stuff and all, so the rooting part is not what I fear, is just this new wave of side effects regarding it.
LionLorena said:
Yeah the warranty is not on top of my mind right now, my concern are the other issues it may cause, such apps not working, and security issues.
Like, I had a Sony Xperia Play back some years and past a week I root it, and past 2 weeks it was on Cyanogenmod.
I had Bricked that device countless times and had somehow fixed, I had also replaced several internal components as well, but back then there were no DRM stuff and all, so the rooting part is not what I fear, is just this new wave of side effects regarding it.
Click to expand...
Click to collapse
There is no DRM to lose on Motorola devices. On Sony devices, what you said is applicable. As for apps that refuse to work with root access, you can simply switch to Magisk, and enabled hiding root access from all apps.
zeomal said:
There is no DRM to lose on Motorola devices. On Sony devices, what you said is applicable. As for apps that refuse to work with root access, you can simply switch to Magisk, and enabled hiding root access from all apps.
Click to expand...
Click to collapse
That's motivating.
And I've found a topic that says I don't even need to flash the custom recovery, I can simply hot boot it and do my stuff and keep the stock recovery.
LionLorena said:
That's motivating.
And I've found a topic that says I don't even need to flash the custom recovery, I can simply hot boot it and do my stuff and keep the stock recovery.
Click to expand...
Click to collapse
There's no real point of not changing the stock recovery, unless you are planning to stick with a rooted stock ROM. If you keep the stock recovery, you'll be able to enable OTA stock updates.
From a security standpoint, if your device is lost, it becomes much easier for an attacker to breach your system and much harder for you to protect it. However, according to most security principles, once your device is lost from you, it's no longer your device, anyway.
zeomal said:
There's no real point of not changing the stock recovery, unless you are planning to stick with a rooted stock ROM. If you keep the stock recovery, you'll be able to enable OTA stock updates.
From a security standpoint, if your device is lost, it becomes much easier for an attacker to breach your system and much harder for you to protect it. However, according to most security principles, once your device is lost from you, it's no longer your device, anyway.
Click to expand...
Click to collapse
The OTA updates are one of the reasons, yes.
And yes, from that point of view you are right.
I'm currently using some tracking solutions such as Cerberus, and disabling some features while the phone screen is locked, such as quick settings, and power off menu.
Also the extra layer of security imposed by Google version of iCloud, passes me some sense of safety.
The main thing that bothers me related to custom recovery is that the attacker can replace my software entirely.
While with stock I can have some time to recover the device using the tactics. Enabled.
And root could potentially aid me in that, I could add Cerberus to /system and etc.
You lose security. Every person with knowledge can access to your phone through TWRP, use the File Manager to erase files.key (this erases your gesture or PIN of lock screen) and can see all your info. If you unlock bootloader, every person can flash TWRP and do this steps.
alaindupus said:
You lose security. Every person with knowledge can access to your phone through TWRP, use the File Manager to erase files.key (this erases your gesture or PIN of lock screen) and can see all your info. If you unlock bootloader, every person can flash TWRP and do this steps.
Click to expand...
Click to collapse
thats why i'm thinking 3 times before doing it.

Categories

Resources