Related
I've been searching these forums for the last few hours and there seem to be many mixed answers about this. Will it hard brick my phone?
It's probably an incredibly stupid thing to do, but I'm willing to do whatever (other than returning to stock) to get more security. I've lost too many phones
Anyway, I have a feeling changing the recovery.img will cause a locked bootloader to reject boot, but what about boot.img (which is used for root, magisk, etc)?
Is there anyone here that knows how the boot process works in detail? would appreciate the feedback and I'm sure people will appreciate it. Thanks
htko89 said:
I've been searching these forums for the last few hours and there seem to be many mixed answers about this. Will it hard brick my phone?
It's probably an incredibly stupid thing to do, but I'm willing to do whatever (other than returning to stock) to get more security. I've lost too many phones
Anyway, I have a feeling changing the recovery.img will cause a locked bootloader to reject boot, but what about boot.img (which is used for root, magisk, etc)?
Is there anyone here that knows how the boot process works in detail? would appreciate the feedback and I'm sure people will appreciate it. Thanks
Click to expand...
Click to collapse
How will relocking the bootloader add security? Are you secretly the President asking this question?
Jokes aside. Apparently it will cause you to brick because the boot.img needs to be secure. Having twrp or any other form of custom anything I assume has to have an unsecured boot. So when the bootloader lock command is processed and the boot isn't able to be secured, brick occurs?
htko89 said:
I've been searching these forums for the last few hours and there seem to be many mixed answers about this. Will it hard brick my phone?
It's probably an incredibly stupid thing to do, but I'm willing to do whatever (other than returning to stock) to get more security. I've lost too many phones
Anyway, I have a feeling changing the recovery.img will cause a locked bootloader to reject boot, but what about boot.img (which is used for root, magisk, etc)?
Is there anyone here that knows how the boot process works in detail? would appreciate the feedback and I'm sure people will appreciate it. Thanks
Click to expand...
Click to collapse
No offense, but this would be an incredibly stupid thing to do. There is always a trade off between convenience and features (i.e. root, etc.) and security. It's always either or, at least to a very large extent. Pick full stock or pick root/unlocked. The trade-off is highly weighted towards root as.long as you use reasonable care with your device, but feel free go for it if you're needing a new metal doorstop!
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
I don't think there is a revert method (inside or outside the store). I know it's after the fact, but on your next device, you may want to figure out exactly what you'd want to do with root before you go through with it. I typically only do it for TB backup purposes and XPOSED, but I've found that I can back up in other ways, and I dig stock enough not to risk rooting. I don't knock you for rooting (there are plenty of good reasons to), this is just my advice going forward. In the meantime, you should look around XDA, you may find your golden goose app that you can leverage root for. Good luck.
bgibson72 said:
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
Click to expand...
Click to collapse
hey sorry to hear that your having issues,
but you and the other poster are correct, sprint never released a restore file that wasn't encrypted.
And to my knowledge the repair centers would not be able to fix this issues, and sadly lg would more then likely deny a
warranty claim as this was modifications done by the end user.
A good chance in the future that we will get the files needed or a process to revert back to stock, but currently there is no SAFE method to try, and pushing the stock aboot and system.img back to the device WILL hard brick the device.. @me2151 attempted the restore process once, and failed, so please be careful as you may have issues.. The red warning triangle is due to your aboot "bootloader" being swapped for the debug version and will never go away, unless we get a dev willing to risk his device for a .png swap of the warning RED img. Other wise its there forever.
The static on boot up can be removed using a custom kernel but be aware it WILL break things in return. Typically update to prl and profile
fm radio, comfort view and a few other little things..
Hey, thanks for the reply. I can deal with the red warning screen, I just get a little anxious when I can't use the touchscreen or my cellular data gets hosed. As long as there are fixes here (which there have been--thanks to all) and I can use my phone, we're good. I figured if someone could break encryption on government files then why would an encrypted KDZ file be such a challenge? At any rate, I appreciate the help. I'll just keep my fingers crossed for a PNG swap!
*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.
I have a 6p, and I've had many issues with it. I joined the Android beta program hoping the beta might help, and it did somewhat, then broke it again.
I'm considering rooting the phone so I can adjust noise cancellation and switch to a power optimized kernel, to fix the two major problems with the device.
Can anyone suggest the best way to do this while minimizing security risks, and what are the risks compared to just keeping stock unrooted? FYI I have rooted and flashed ROMs on phones before, so not a total noob.
Thanks!
sashby said:
I have a 6p, and I've had many issues with it. I joined the Android beta program hoping the beta might help, and it did somewhat, then broke it again.
I'm considering rooting the phone so I can adjust noise cancellation and switch to a power optimized kernel, to fix the two major problems with the device.
Can anyone suggest the best way to do this while minimizing security risks, and what are the risks compared to just keeping stock unrooted? FYI I have rooted and flashed ROMs on phones before, so not a total noob.
Thanks!
Click to expand...
Click to collapse
Hello...
Working method:
Unlock bootloader
Flash TWRP.img : https://dl.twrp.me/angler/twrp-3.1.0-0-angler.img
Boot into TWRP
Install SuperSU: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Reboot. Done.
From here you can install the kernel of your choice. Recommended kernels: ElementalX or Franco's Kernel.
Well, rooting a phone always.involve risks. Depending what you do with your phone. As long as you don't install apps from bad sources and don't allow root access before you know what it does.
Also, you don't need Root to install a custom kernel if you want.
Just fastboot boot TWRP.img and install kernel zip from TWRP. It may lack some features that need Root to work though...
Good luck...
sashby said:
I have a 6p, and I've had many issues with it. I joined the Android beta program hoping the beta might help, and it did somewhat, then broke it again.
I'm considering rooting the phone so I can adjust noise cancellation and switch to a power optimized kernel, to fix the two major problems with the device.
Can anyone suggest the best way to do this while minimizing security risks, and what are the risks compared to just keeping stock unrooted? FYI I have rooted and flashed ROMs on phones before, so not a total noob.
Thanks!
Click to expand...
Click to collapse
If you unlock your bootloader and root you will get a nag screen saying Android can't ensure that your device is safe. It isn't really dangerous as long as you only download apps from trusted sources and are careful about what apps you give root access to. However, Android Pay and some banking apps won't work on a rooted phone unless you use Magisk and PhilsSu which are currently able to pass Androids Safety Net security measures by hiding root from those apps.
I should add that a handful of games like Pokemon Go require the device to pass safety net to work so again you would need to use the Magisk and PhilsSu combo to play them. If you are going to go to the trouble of rooting I would consider trying a custom rom (other than Pure Nexus) as well as flashing a custom kernel like ElementalEx or The Flash's kernel. It's easy enough to go back to stock of you want to. Cortex is a very good stock based Rom with Pixel features, a responsive developer and very few bugs. I'm currently on Dirty Unicorns (which is not on XDA) because I wanted OMS support for Substratum theming. The Rom is fast and smooth and all my apps work perfectly on it--unlike PN where I encountered some problem or another every time I tried it.
Hello,
No issues at all with Pure Nexus here... :good:
Cheers...
5.1 said:
Hello,
No issues at all with Pure Nexus here... :good:
Cheers...
Click to expand...
Click to collapse
I ran Pure Nexus 5 separate times, always a completely clean install and never once did I not have issues with it. I think the people who use that Rom have been brainwashed.
jhs39 said:
I ran Pure Nexus 5 separate times, always a completely clean install and never once did I not have issues with it. I think the people who use that Rom have been brainwashed.
Click to expand...
Click to collapse
Hello,
Thank you very much, have a nice day to you too... :good:
Cheers...
Thank you everyone for your input. I think I'm going to need to do this soon, as the phone is almost unusable sometimes - and battery life is downright awful on stock with this phone. It's now dozing correctly again, but when I'm actually using it I can literally watch the battery gauge drop, even with screen brightness turned way down.
It used to be that when flashing a ROM you were wiping the entire phone - i.e. even personal data has to be reloaded on the phone. Is that still true, or are they on separate partitions?
sashby said:
It used to be that when flashing a ROM you were wiping the entire phone - i.e. even personal data has to be reloaded on the phone. Is that still true, or are they on separate partitions?
Click to expand...
Click to collapse
Hello,
To install a custom ROM you need to unlock the bootloader. When unlock it, the userdata partition is entirely wiped. The internal storage (personal data's: photos,, videos, etc...) is part of it.
So be sure to backup your photos, videos, etc... Before you do it...
Good luck...
sashby said:
I have a 6p, and I've had many issues with it. I joined the Android beta program hoping the beta might help, and it did somewhat, then broke it again.
I'm considering rooting the phone so I can adjust noise cancellation and switch to a power optimized kernel, to fix the two major problems with the device.
Can anyone suggest the best way to do this while minimizing security risks, and what are the risks compared to just keeping stock unrooted? FYI I have rooted and flashed ROMs on phones before, so not a total noob.
Thanks!
Click to expand...
Click to collapse
The full risk is this.
If I can boot your phone into TWRP and you don't have encryption enabled, I can unlock your phone by deleting the correct files.
Once the correct files are deleted I own the phone and your data.
So I've come to the conclusion in the last day while restoring my phone that encryption is a must with an unlocked bootloader.
I wish to root my phone(XT1686) but intend to keep the stock ROM(no bootloader unlock).
Is there any advantage in doing so? And will OTA updates be affected?
yourSAS said:
I wish to root my phone(XT1686) but intend to keep the stock ROM(no bootloader unlock).
Is there any advantage in doing so? And will OTA updates be affected?
Click to expand...
Click to collapse
It is not possible to root without unlocking the bootloader on this device...
If you don't have a specific reason to root, don't do it.
And once rooted, you cannot accept any OTA... most likely case if you do it will just fail, worst possible case it bricks (which can happen but is extremely rare).
To answer the question in your title, about the advantages of rooting...
Rooting gives you near full access to your device, and thus the ability to customize it beyond the options provided to you via the default interface. Also, some apps provide additional features on rooted phones. For example, some security programs recommend rooting your device so that it can more forcefully integrate itself with the device to protect against malware, hacking, etc. I tend to install a security package that works better on a rooted device, as well as make use of features that tend to only work on a rooted device, such as folder mounting from the internal SD card to the external one. Also, allows me to access system files that are unavailable otherwise, allowing me to customize certain sounds (or copy them at least).
If you decide you want to root your device, make sure you understand the steps to take BEFORE trying it. That means when you come across a guide on how to do it, make sure you get all the files that will be required and reading through the instructions step by step. If any of the steps sound like it will leave you lost on what to do, then DO NOT do any of it. Also, make sure you read the comments for the guide as well, looking for any mention of issues encountered and consider if you might encounter those issues as well. For example, if it causes issues for devices that use a particular carrier and you use that same carrier, you might want to leave well enough alone. Compare your phone version numbers with what others report having issues with (kernel, baseband, build, etc). Anything that someone has an issue with where their phone somehow matches up with yours in some way, take that as a sign to investigate deeper, so as to avoid having any issues yourself.
For the most part, unless you have a need or desire for a feature/function that requires rooting your device, don't mess with it. I'm not kidding, as one mistake can leave you without a working phone and without any options for returning/replacing it.
Thanks for the replies & warnings.
I'm not a noob so I know the risks of rooting. So maybe I should have rephrased it-
What are the advantages of rooting Moto G5 plus specifically?
Say like in terms of mods and other stuff? Also, is it possible to unroot once rooted- I mean to ask if it's possible to revert the state to factory mode with bootloader locked and stock ROM so that device will be eligible for OTA updates again?
yourSAS said:
Thanks for the replies & warnings.
I'm not a noob so I know the risks of rooting. So maybe I should have rephrased it-
What are the advantages of rooting Moto G5 plus specifically?
Say like in terms of mods and other stuff? Also, is it possible to unroot once rooted- I mean to ask if it's possible to revert the state to factory mode with bootloader locked and stock ROM so that device will be eligible for OTA updates again?
Click to expand...
Click to collapse
Bootloader lock is not relevant to OTA's. You might be able to relock, but the fact it was once unlocked cannot be hidden, it will always be very clear that it was unlocked.
Unrooting is easy, the issue arises undoing what you did with root, undoing them all depends what you changed.
I don't know of any reasons specific to this device to root.
acejavelin said:
Bootloader lock is not relevant to OTA's. You might be able to relock, but the fact it was once unlocked cannot be hidden, it will always be very clear that it was unlocked.
Click to expand...
Click to collapse
If the OEM knows I've unlocked bootloader, why will it push OTAs to my phone even though I've locked bootloader on my end? So isn't bootloader lock status relevant for OTA?
yourSAS said:
If the OEM knows I've unlocked bootloader, why will it push OTAs to my phone even though I've locked bootloader on my end? So isn't bootloader lock status relevant for OTA?
Click to expand...
Click to collapse
No, the status of your bootloader is not relevant... Moto will notify you of an available update and happily attempt to apply it regardless if your bootloader is locked or not.
What matters is if the boot or system partitions is changed, if there is ANY change to those, among other things like if the radio version or recovery versions don't match or the partition table is changed, the update will fail. If you flash any custom recovery it will fail as well.
On this subject I mention a slight con which is that some banking or financial apps might complain to you if they detect root. I have maybe 10 different bank and credit apps installed and all work flawlessly except 1. The Huntington Bank app wont allow me to use fingerprint login but otherwise the app is fully functional like mobile deposits. Just wanted to mention to be aware.