Related
I have rooted other devices, and I understand the benefits...but there is a bit of a pain. Once you root your device, the way I understand it, you need to wait for an OTA update to be made available via a developer here. Now that usually happens pretty quickly, so that's not the issue. However, usually when you get an update OTA, you don't have to reinstall all your apps again, set up your screens, etc. When you take an update from here, you usually do need to reinstall everything.
If I want to avoid that, and let OTAs happen as they should, is there an easy and right way for me to get Titanium Backup to restore but keep that ability? Do I unlock the bootloader and root, then unroot but leave the bootloader unlocked? It isn't clear, and there seems a lot of noise when people ask, about what you can do that would still allow OTAs. Some seem to say you can take them, others suggest you can't. I have searched, and it is confusing. I would love to know if someone really knows, or could cite a post or article that I may have missed. I know I could loose root in that process, I get that risk. I just want to understand my options.
It is, as an aside, so painful that Android has not properly dealt with backup and restore and migrating apps/data from one device to another in the OS. That seems such a gaping hole that Apple has filed, and one big reason (not always the only one) I seem to end up rooting a device right away. I suspect I would root eventually, but probably wait a bit except for this.
Thanks
RoboCuz said:
I have rooted other devices, and I understand the benefits...but there is a bit of a pain. Once you root your device, the way I understand it, you need to wait for an OTA update to be made available via a developer here. Now that usually happens pretty quickly, so that's not the issue. However, usually when you get an update OTA, you don't have to reinstall all your apps again, set up your screens, etc. When you take an update from here, you usually do need to reinstall everything.
If I want to avoid that, and let OTAs happen as they should, is there an easy and right way for me to get Titanium Backup to restore but keep that ability? Do I unlock the bootloader and root, then unroot but leave the bootloader unlocked? It isn't clear, and there seems a lot of noise when people ask, about what you can do that would still allow OTAs. Some seem to say you can take them, others suggest you can't. I have searched, and it is confusing. I would love to know if someone really knows, or could cite a post or article that I may have missed. I know I could loose root in that process, I get that risk. I just want to understand my options.
It is, as an aside, so painful that Android has not properly dealt with backup and restore and migrating apps/data from one device to another in the OS. That seems such a gaping hole that Apple has filed, and one big reason (not always the only one) I seem to end up rooting a device right away. I suspect I would root eventually, but probably wait a bit except for this.
Thanks
Click to expand...
Click to collapse
Why not just unroot get the OTA and reboot? It's so easy with the toolkit you could even relock and unlock at the same time if necessary
Sent from my Nexus 7 using Tapatalk 2
That's a good idea...I guess I hadn't thought of that...but unlocking and relocking would wipe the device, no? If I am going to wipe the device to get the OTA, then I would just proceed through the "normal" way of waiting for someone to release the update in a ROM and flash it. I would just like, in some way, to treat this device like an appliance, and not worry about OTAs bricking my phone, or needing to reinstall everything to get the latest...I just want to start off restoring some of my apps from another device, and then (maybe) just let the updates take their course. I know I could change my mind later and start ROMing, but I just wanted to understand my options....I know I wipe the device when I unlock, so assumed that would happen each time. And I wasn't sure if I needed to unlock to JUST get root, if I am not planning on flashing ROMs. And can I just root,and then use OTA rootkeeper if necessary, and allow updates?
So I guess the questions are:
- Do I need to unlock to root?
- Once I have done what I need to use Titanium (unlock and root or just root), can I take an OTA update, or do I need to undo some or all?
- If I undo some or all, will that incur a wipe?
I think I figured this out...I found the manual for the Nexus Root Toolkit (www.wugfresh.com/dev/nexus-root-toolkit/), and that spells out a LOT of really clear information.
I think I would:
- unlock
- root and install CWM
- use Titanium, etc.
Later, if an OTA comes out I want to allow:
- probably do full CWM backup
- flash stock recovery
- install and run OTA Rootkeeper
- allow the OTA, knowing I might loose root
- reflash CWM
I think this shouldn't cause any issues. This assumes I am basically running stock, and just using root for backup/restore app stuff with Titanium and maybe Root Explorer.
Make sense?
Okay so I just have a few questions about rooting my phone before I do it, since I saw the root here that works for the most recent OTA update.
1) If someone happens with my phone (either bricking it from rooting or something inconsequential) will they not replace my phone due to it being rooted?
2) If they won't replace it due to being rooted (if it wasn't bricking), is there an easy way to unroot the phone?
3) I can't tell from the instructions, but I'm pretty sure some others have said that it might require you to restore factory settings, does this one require that?
4) The thread says that it is now impossible to unlock the bootloader, does this also mean that you can't use a custom ROM? How exactly do you add a ROM?
Sorry for all the questions, I've never rooted an android device before, and I don't have the time or energy to go running around Google/forums trying to find these answers.
Thanks in advance!
EDIT: yes I know i've already asked 2 of these questions, but I'm a stupid poop who needs validation.
wholocked10 said:
Okay so I just have a few questions about rooting my phone before I do it, since I saw the root here that works for the most recent OTA update.
1) If someone happens with my phone (either bricking it from rooting or something inconsequential) will they not replace my phone due to it being rooted?
2) If they won't replace it due to being rooted (if it wasn't bricking), is there an easy way to unroot the phone?
3) I can't tell from the instructions, but I'm pretty sure some others have said that it might require you to restore factory settings, does this one require that?
4) The thread says that it is now impossible to unlock the bootloader, does this also mean that you can't use a custom ROM? How exactly do you add a ROM?
Sorry for all the questions, I've never rooted an android device before, and I don't have the time or energy to go running around Google/forums trying to find these answers.
Thanks in advance!
EDIT: yes I know i've already asked 2 of these questions, but I'm a stupid poop who needs validation.
Click to expand...
Click to collapse
first, rooting your voids the warranty, so technically, they (either VZW or Motorola) are not obligated to replace it. that being said, you can always play dumb and say that you accepted some OTA install, and now the phone won't boot up. usually, VZW will try to restore the phone, and if not, they'll replace it - no worries.
2.) I believe there is an unroot method, but I have not explored this. try doing a search on this forum for "unroot razr m"
3.) restore factory settings could unroot - check the threads
4.) you can still install a custom ROM, but you'll need to install Safestrap first. however, the custom ROMs available for SS are out-dated, and I don't think that any devs will be providing any going forward. however, I would not be too discouraged by this, as the phone is very solid stock. so rooting is the key to remove the bloatware to help increase battery life, increase performance, and reduce excess data usage.
hope this helps.
HI, I have an LG G2 that I want to root, mainly so that I can get rid of some of the stock apps that are running in the back ground and using system resources however before I even venture down the rooting road I need some of the basics explaining to me. I am computer literate in the windows environment so am quite happy to have a go at rooting my device however I would like to get a better understanding of the terminology etc first, I also have a number of rooting specific questions if anyone can answer them. Ok here goes:-
1) ROM - What is it, my understanding is that this is basically the operating system shipped with the phone and therefore it follows that a custom ROM is one made by a third party that can be installed on the phone instead of the standard one. Am I correct on this.
2) Recovery - I have no idea what this is but am guessing that it is some way of recovering the device / re-setting it to its default factory settings if the phone goes completely wrong, I would therefore guess that a custom recovery is a third party recovery that does different things to the one provided by the manufacturer. Again am I correct in this or not.
3) Is it possible to gain root access on the device and keep the standard ROM. As I said before I want root access so that I can control the default apps and get rid of the ones that I don't use or run in the background, at this stage I don't want to install a custom ROM until I have had a go at just rooting the device (I suspect this will change as I love tinkering)
4) I am aware of the issue around warranty being void if a device is rooted, is there anyway to restore the device so that it is un-rooted and the repair centre etc will never know that it has been rooted. I understand that this is something to do with a counter needing re-setting but have no idea how to do this.
5) What software do I need to root the device.
I appreciate I have a lot of questions, most on the very basic side of things but I would be very grateful any help offered.
Thanks
Ben
Monkeyhands said:
HI, I have an LG G2 that I want to root, mainly so that I can get rid of some of the stock apps that are running in the back ground and using system resources however before I even venture down the rooting road I need some of the basics explaining to me. I am computer literate in the windows environment so am quite happy to have a go at rooting my device however I would like to get a better understanding of the terminology etc first, I also have a number of rooting specific questions if anyone can answer them. Ok here goes:-
1) ROM - What is it, my understanding is that this is basically the operating system shipped with the phone and therefore it follows that a custom ROM is one made by a third party that can be installed on the phone instead of the standard one. Am I correct on this.
2) Recovery - I have no idea what this is but am guessing that it is some way of recovering the device / re-setting it to its default factory settings if the phone goes completely wrong, I would therefore guess that a custom recovery is a third party recovery that does different things to the one provided by the manufacturer. Again am I correct in this or not.
3) Is it possible to gain root access on the device and keep the standard ROM. As I said before I want root access so that I can control the default apps and get rid of the ones that I don't use or run in the background, at this stage I don't want to install a custom ROM until I have had a go at just rooting the device (I suspect this will change as I love tinkering)
4) I am aware of the issue around warranty being void if a device is rooted, is there anyway to restore the device so that it is un-rooted and the repair centre etc will never know that it has been rooted. I understand that this is something to do with a counter needing re-setting but have no idea how to do this.
5) What software do I need to root the device.
I appreciate I have a lot of questions, most on the very basic side of things but I would be very grateful any help offered.
Thanks
Ben
Click to expand...
Click to collapse
1 Yes it is the operating system, AOSP means its full on custom. While STOCK based roms are the basic OS the phone came with but with multiple tweaks to improve performance and the system in general but keeping features that are not released publicly and drivers. For example camera performance etc.
2 Yes. The manufacturer recovery only resets the RoM to factory default. Custom Recoveries let you Backup your entire System (except files) to exactly the way it was before so if you do something wrong you can go exactly to the way it was before down to apps installed and messages.
so Stock is a Restore partition. Custom needs you to backup system first unless you store a Rom on Memory or external to *flash*
Custom actually gives you more options to recover a broken phone than stock.
3. Yes you can. http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
4. The samsung Galaxys had counters to check root and flashes etc i believe LG G2 Doesnt you can remove root and also flash back to complete STOCK firmware for returning to manufacters.
5. http://forum.xda-developers.com/showthread.php?p=45692679#post45692679 GL read into it
squee666 said:
1 Yes it is the operating system, AOSP means its full on custom. While STOCK based roms are the basic OS the phone came with but with multiple tweaks to improve performance and the system in general but keeping features that are not released publicly and drivers. For example camera performance etc.
2 Yes. The manufacturer recovery only resets the RoM to factory default. Custom Recoveries let you Backup your entire System (except files) to exactly the way it was before so if you do something wrong you can go exactly to the way it was before down to apps installed and messages.
so Stock is a Restore partition. Custom needs you to backup system first unless you store a Rom on Memory or external to *flash*
Custom actually gives you more options to recover a broken phone than stock.
3. Yes you can. http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
4. The samsung Galaxys had counters to check root and flashes etc i believe LG G2 Doesnt you can remove root and also flash back to complete STOCK firmware for returning to manufacters.
5. http://forum.xda-developers.com/showthread.php?p=45692679#post45692679 GL read into it
Click to expand...
Click to collapse
HI,
Thanks for the info, I have now rooted my phone and as anticipated now have a whole load of new questions. Firstly I installed an app Root Checker Basic by joeykrim, just to make sure the phone was rooted and the app reported back that it was not rooted despite the fact that esfileexplorer now has root access and I have been able to install SuperSU by Chainfire so whats going on, is my phone rooted, not rooted or partialy rooted (if that's possible). Also I am not exactly sure why I need to use the SuperSU app, it doesn't appear to have any options for uninstalling system apps or changing previously restricted settings etc which I was expecting once I got root access, the stock ROM hasn't given me access to this stuff either so the question is how do I now get access to it, from other apps I presume. One thing that I do need SuperSU for is to use it in combination with hidemyroot so that SKYGO will still work as this app will not work on rooted devices, if there is another way to get SKYGO to work on rooted apps then I will happily give it a go as it means I wont need SuperSU then.
Thanks
Ben
Be careful wich apps from system you want to uninstall, you can brick your device.
Do not remove anything from /system, ever. Use Settings->Disable on the apps that allow that, anything else you absolutely thing you need to disable use (as root) pm disable com.package.name.
Google it for more details.
Hey I believe many people have questions around the KNOX and warranty void if you root/install custom recovery.
So I woud like to know:
Is there any software besided KingOroot (doesn't work in A5 510M) or Kingroot (I'm not installing that thing because plenty of people says it steal your data or are impossible to remove) which can root without messing with partitions / custom recovery, meaning it won't trigger the knox counter?
Has anyone confirmed that by only having the KNOX counter triggered samsung has denied to give warranty? Even if the phone is unroot?
Is there any method that roots the device without KNOX tripping?
Thanks
if you are on a 5.1.x device, you might wanna give systemless root a try, i think they ported it to 5.1.x as it was a Marshmallow solution initially.
aside of that, nope.
also, a few regions, like Europe, do not accept root, and especially knox triggering as a warranty void.
and my personal two cents, trigger it, no worth at all, if your device ends up unbootable, there is no way they are going to bother reading through your chip of what you have done, most of the time you'll win the procedures if you need warranty
PlutoDelic said:
if you are on a 5.1.x device, you might wanna give systemless root a try, i think they ported it to 5.1.x as it was a Marshmallow solution initially.
aside of that, nope.
also, a few regions, like Europe, do not accept root, and especially knox triggering as a warranty void.
and my personal two cents, trigger it, no worth at all, if your device ends up unbootable, there is no way they are going to bother reading through your chip of what you have done, most of the time you'll win the procedures if you need warranty
Click to expand...
Click to collapse
thanks pal! I believe samsung has made it very easy for support to check whether the knox is triggered or not, otherwise how would it help anything with them fixing less phones?
In germany (its in europe,lol) knox counter on 1 is not a problem when in warranty,just look my thread in q/a section.
The only way they would know that is through going in Download Mode... So, this is just a crazy thought, but I always planned that if something went so wrong that I couldn't fix it myself (I mean if I can go to Download I can probably still fix whatever is wrong unless the device is bricked), I would just break the volume buttons, so that they can't get to Download Mode either. I know, a rash decision, but just food for thought.
Kingroot is easily removed. Don't believe all the silly scare mongering.
It's the most successful root exploit available without tripping knox.
ashyx said:
Kingroot is easily removed. Don't believe all the silly scare mongering.
It's the most successful root exploit available without tripping knox.
Click to expand...
Click to collapse
I have read plenty of cases of the thing working like a virus, sending data to china, making it impossible to remove. I will not put that in my phone. I have tried kinOroot and it didn't work. But sent stuff outside anyways...
fscussel said:
I have read plenty of cases of the thing working like a virus, sending data to china, making it impossible to remove. I will not put that in my phone. I have tried kinOroot and it didn't work. But sent stuff outside anyways...
Click to expand...
Click to collapse
So you just go from what read rather than try it yourself and you think KingOroot is different? It does contact servers in China, that's how it works.
It's easily removed by simply uninstalling or using SuperSume.
Millions of people have used it and I don't know of one documented case of someone being hacked after using it lol.
KingRoot contacts servers in China because it takes little-to-no space. A version of it that doesn't have to contact any server, and still grant you root access... Well, such an app would be over 3GB big, and would be of the same size, even after it finishes the job and gets you root access. It would be extremely inefficient, and that is an understatement. The servers in China contain the exploits that can be used to grant access to root without using a custom recovery (as a custom recovery would trip KNOX). There are thousands and thousands of files in those servers. As I said, it would be possible to make a one-click-root app that can root thousands of devices and that doesn't make contact with any server, but you would have to include all those thousands of files in the app, in order for it to work. No one is crazy enough to do such a thing.
ashyx said:
So you just go from what read rather than try it yourself and you think KingOroot is different? It does contact servers in China, that's how it works.
It's easily removed by simply uninstalling or using SuperSume.
Millions of people have used it and I don't know of one documented case of someone being hacked after using it lol.
Click to expand...
Click to collapse
King-V said:
KingRoot contacts servers in China because it takes little-to-no space. A version of it that doesn't have to contact any server, and still grant you root access... Well, such an app would be over 3GB big, and would be of the same size, even after it finishes the job and gets you root access. It would be extremely inefficient, and that is an understatement. The servers in China contain the exploits that can be used to grant access to root without using a custom recovery (as a custom recovery would trip KNOX). There are thousands and thousands of files in those servers. As I said, it would be possible to make a one-click-root app that can root thousands of devices and that doesn't make contact with any server, but you would have to include all those thousands of files in the app, in order for it to work. No one is crazy enough to do such a thing.
Click to expand...
Click to collapse
I have read that if you try to remove it you can in fact brick your cell...
fscussel said:
I have read that if you try to remove it you can in fact brick your cell...
Click to expand...
Click to collapse
Holy smokes...is this serious? :sly:
ashyx said:
Holy smokes...is this serious? :sly:
Click to expand...
Click to collapse
why so funny? Reson is simple:
After people install kingroot it add many unwanted programs, and also refuses to be uninstalled. People then try to use SuperSU ME to remove it and leave just supersu, and in this process many have got a bricked device. They say this happens because of the kingroot's code to fight anything that tries to remove it.
Now, are you some sort of associate of kingroot?
PlutoDelic said:
if you are on a 5.1.x device, you might wanna give systemless root a try, i think they ported it to 5.1.x as it was a Marshmallow solution initially.
aside of that, nope.
also, a few regions, like Europe, do not accept root, and especially knox triggering as a warranty void.
and my personal two cents, trigger it, no worth at all, if your device ends up unbootable, there is no way they are going to bother reading through your chip of what you have done, most of the time you'll win the procedures if you need warranty
Click to expand...
Click to collapse
systemless root needs custom recovery installed as far as I can tell. So knox counter already 0x1 because of custom recovery.
Also I would like to know, if I install custom recovery, and the an OTA update comes, for 6.0, I would have to first remove TWRP, as so to use the OTA, after that, reinstall TWRP, would that trigger the knox again?
0x2 ??
fscussel said:
why so funny? Reson is simple:
After people install kingroot it add many unwanted programs, and also refuses to be uninstalled. People then try to use SuperSU ME to remove it and leave just supersu, and in this process many have got a bricked device. They say this happens because of the kingroot's code to fight anything that tries to remove it.
Now, are you some sort of associate of kingroot?
Click to expand...
Click to collapse
They say, he says, she says, do you actually have a clue what you are talking about?
I'm pretty sure I do.
It can be removed like any other app.
If you actually knew what you were talking about you'd know that.
It wont allow another root exploit to easily replace it, this is down to some silliness between Chainfire and King team. It is a pain but it can still be removed or replaced no problem. I wrote a whole guide how to do it.
Literally millions have achieved root with KingRoot and for many is the only way they can.
I dont advocate it nor am I against it.
Dont judge something until you've tried it.
I'll say no more on the matter now as I'm getting dizzy.
ashyx said:
They say, he says, she says, do you actually have a clue what you are talking about?
I'm pretty sure I do.
It can be removed like any other app.
If you actually knew what you were talking about you'd know that.
It wont allow another root exploit to easily replace it, this is down to some silliness between Chainfire and King team. It is a pain but it can still be removed or replaced no problem. I wrote a whole guide how to do it.
Literally millions have achieved root with KingRoot and for many is the only way they can.
I dont advocate it nor am I against it.
Dont judge something until you've tried it.
I'll say no more on the matter now as I'm getting dizzy.
Click to expand...
Click to collapse
1) I don't know if it works in my A5 2016 510M, can't find a compatible list or a report.
2) I have read reports of problems uninstalling it.
3) I have read reports of problems uninstalling it with SuperSU Me, including bricking.
4) I find you very arrogant.
fscussel said:
1) I don't know if it works in my A5 2016 510M, can't find a compatible list or a report.
2) I have read reports of problems uninstalling it.
3) I have read reports of problems uninstalling it with SuperSU Me, including bricking.
4) I find you very arrogant.
Click to expand...
Click to collapse
You are obviously learning what you know from other misinformed users.
1. Just try it if it doesn't work it doesn't work just uninstall it.
2. As I have said, no such issue.
3. There's a reason why replacing it with SuperSU bricks some devices and it has absolutely nothing to do with kingroot.
If you attempt to replace it with SuperSU on anything above 5.0.2 on a Samsung device it's likely to soft brick it and cause a boot loop.
This is due to Samsungs root restriction policy in the kernel. The same goes for Android 6.0 devices.
To root with supersu on these devices you need a patched boot.img to remove the selinux restriction.
4. I find you very misinformed.
ashyx said:
You are obviously learning what you know from other misinformed users.
1. Just try it if it doesn't work it doesn't work just uninstall it.
2. As I have said, no such issue.
3. There's a reason why replacing it with SuperSU bricks some devices and it has absolutely nothing to do with kingroot.
If you attempt to replace it with SuperSU on anything above 5.0.2 on a Samsung device it's likely to soft brick it.
This is due to Samsungs root restriction policy in the kernel. The same goes for Android 6.0 devices.
To root with supersu on these devices you need a patched boot.img to remove the selinux restriction.
4. I find you very misinformed.
Click to expand...
Click to collapse
very misinformed but I have just saved my device from brick, because if you did your work your would see it's android 5.1.1 and it's samsung.
Now let me know if it works with a samsung 5.1.1 with KNOX and perhaps I will try it.
Also let me know how to remove it and install SuperSU over it.
fscussel said:
very misinformed but I have just saved my device from brick, because if you did your work your would see it's android 5.1.1 and it's samsung.
Now let me know if it works with a samsung 5.1.1 with KNOX and perhaps I will try it.
Also let me know how to remove it and install SuperSU over it.
Click to expand...
Click to collapse
Kingroot won't brick your device, replacing it with supersu will. Not sure where in this discussion I said anything to the contrary? :what:
ashyx said:
Kingroot won't brick your device, replacing it with supersu will. Not sure where in this discussion I said anything to the contrary? :what:
Click to expand...
Click to collapse
very non-productive answer... please check again
*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.