Database Users

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

[Q] New to root, but a few questions after reading

Whew! Been doing lots of reading before trying to root my Verizon Note 3 but still have a few questions that I am hoping them members here can help answer.
I have the Verizon Note 3 with the newest OTA update, running MJE
From all of the reading I have done there are currently only TWO methods of rooting?
The Kingo Method and the Vegas method using Odin.
Now to my questions.
When I got the Note 3 at launch it suffered from terrible in-call audio quality. This was fixed with the MJE update. If I root, will I loose this fix and the phone suffer from the terrible audio quality again?
The Vegas/Odin method wipes the phone and installs the MJ7 version, correct? If so, can the MJE update be applied without loosing root?
I am not terribly concerned about having to reinstall stuff I am just not sure which is the best method.
After rooting, google play, all my purchased apps, ect. will still work normally, correct?
Thanks!

At this time, there isn't a way to go back to the full MJ7 release via Odin once MJE has been installed (whether or not RDLV is involved). So, your concern about MJ7 is moot as you currently have MJE.
My understanding is that RDLV on MJ7 and MJE trips the Knox Warranty flag, & CF Autoroot is not supported on the Verizon N3 variant (SM-N900V) - somebody correct me if that is wrong. (BTW the tripping of the warranty flag has no effect on any functionality). So if that is of concern to you, you can use either Kingo or vroot for rooting.
The only functionality lost as a result of "light rooting" might be Knox container services.
good luck.

Thanks for the quick reply. So vroot or kingo would be the only options. I am mainly looking to root for the ability to remove bloatware with programs such as titanium. So as I understand it, using a root app such as these will have no impact on how I use my current apps now, playstore, ect. And will retain the MJE update?
Should I choose to root this way and want to uproot, what would be the task?
bftb0 said:
At this time, there isn't a way to go back to the full MJ7 release via Odin once MJE has been installed (whether or not RDLV is involved). So, your concern about MJ7 is moot as you currently have MJE.
My understanding is that RDLV on MJ7 and MJE trips the Knox Warranty flag, & CF Autoroot is not supported on the Verizon N3 variant (SM-N900V) - somebody correct me if that is wrong. (BTW the tripping of the warranty flag has no effect on any functionality). So if that is of concern to you, you can use either Kingo or vroot for rooting.
The only functionality lost as a result of "light rooting" might be Knox container services.
good luck.
Click to expand...
Click to collapse

ashenfang said:
Thanks for the quick reply. So vroot or kingo would be the only options. I am mainly looking to root for the ability to remove bloatware with programs such as titanium. So as I understand it, using a root app such as these will have no impact on how I use my current apps now, playstore, ect. And will retain the MJE update?
Click to expand...
Click to collapse
Yes.
But note also that in 4.3+ there is a reduced incentive to root to "remove bloatware" - preinstalled (system) apps may be disabled directly from the Applications Manager in the stock ROM. (This will be true for foreground apps like Amazon, NFL, etc, but not true for background services such as the horror which is named "Knox")
ashenfang said:
Should I choose to root this way and want to uproot, what would be the task?
Click to expand...
Click to collapse
You would perform a flash via Odin of the full stock ROM which corresponds to your current release (e.g. MJE). (This is a full factory reset which destroys all user data, BTW)
.

Ah Ok. So Odin can be used to flash an updated MJE stock ROM but can't be used to root an already updated MJE. Man that's confusing.
I do know that SOME applications can be disabled through the manager but there are still some where this option is not available. Rooting also gives the ability to run apps that block ads, which I like.
bftb0 said:
Yes.
But note also that in 4.3+ there is a reduced incentive to root to "remove bloatware" - preinstalled (system) apps may be disabled directly from the Applications Manager in the stock ROM. (This will be true for foreground apps like Amazon, NFL, etc, but not true for background services such as the horror which is named "Knox")
You would perform a flash via Odin of the full stock ROM which corresponds to your current release (e.g. MJE). (This is a full factory reset which destroys all user data, BTW)
.
Click to expand...
Click to collapse

ashenfang said:
Ah Ok. So Odin can be used to flash an updated MJE stock ROM but can't be used to root an already updated MJE. Man that's confusing.
Click to expand...
Click to collapse
Well, remember that the N3 doesn't implicitly "trust" Odin (or Heimdall), so (with the N3) Odin is limited to flashing stuff which meets the approval (signature verification) of the early-boot gearing which is already installed on the phone. This is how Samsung locks down everything and also enforces anti-rollback measures.
If you believe Samsung at their word, the anti-rollback mechanism was introduced because of Root de la Vega.
.

Ok, so basically.....
If I root my phone or were to somehow flash it with a "bad" ROM and had issues that I couldn't fix then..... Odin can be used to flash the Note 3 using a original or "verified verizon ROM" to get it back to stock?
Out of curiosity, should that happen, where does one obtain the "verified MJE ROM" to use with Odin to do the flash?
bftb0 said:
Well, remember that the N3 doesn't implicitly "trust" Odin (or Heimdall), so (with the N3) Odin is limited to flashing stuff which meets the approval (signature verification) of the early-boot gearing which is already installed on the phone. This is how Samsung locks down everything and also enforces anti-rollback measures.
If you believe Samsung at their word, the anti-rollback mechanism
.
Click to expand...
Click to collapse

by using the search function.
[Firmware][Collection] Modems, kernels, Stock Tars [Current:MJE]
[Firmware][Guide][Q&A] FIRMWARE MIRROR / OTA & ROOT GUIDE / TECHNICAL Q&A

Root without SU app?

I just rooted using towel root. Planning on staying stock just needed to make one modification. Everything is perfect including knox and flash counter. Is it okay to keep the phone rooted without having the SU app installed?
If I install supersu will it trip my flash counter? If I use it to unroot will it trip?
Thanks
Sent from my SM-G900W8 using XDA Free mobile app

Some questions are asked over and over. Which is why we can tell that you didn't do a search or take ten minutes to read a few threads - you couldn't have avoided finding the answers if you had. You'd also have gotten a quicker answer if you had tried searching.
Super SU won't increment Knox by itself. The flash counter per se can be reset. It's a widely respected and robust app and you didn't give any specific reason why you wouldn't want to use it. If you remove Super SU without manually adding more cumbersome alternatives, you won't be rooted anymore. If it is your intention to remove root, then go ahead. If you want to remain rooted, then you should do some reading as it would seem that you don't understand what Super SU does.
.

fffft said:
Some questions are asked over and over. Which is why we can tell that you didn't do a search or take ten minutes to read a few threads - you couldn't have avoided finding the answers if you had. You'd also have gotten a quicker answer if you had tried searching.
Super SU won't increment Knox by itself. The flash counter per se can be reset. It's a widely respected and robust app and you didn't give any specific reason why you wouldn't want to use it. If you remove Super SU without manually adding more cumbersome alternatives, you won't be rooted anymore. If it is your intention to remove root, then go ahead. If you want to remain rooted, then you should do some reading as it would seem that you don't understand what Super SU does.
.
Click to expand...
Click to collapse
Thanks for the quick reply. I actually Googled and read through the few rooting threads I found but couldn't find the answer for this specific question. Towelroot rooted the phone and supersu was not installed. I don't want to increase flash counter or have custom status as I want to continue to receive OTA updates. I only rooted to access a sql dB which I needed to modify.
I was never under the impression that SU will trip knox, I was wondering if it would trip my flash counter. Also, my question was based more on security. If I don't have supersu to allow root access I would assume any app can get it and would that be a security issue?
Sent from my SM-G900W8 using XDA Free mobile app

In might be a theoretical advantage to not be rooted. But you loose a lot of functionality for that security "gain". Pragmatically though there have been plenty of malware exploits that can root your device as part of their incursion. So it's hard to believe that you are gaining much security by avoiding root on your handset.
Your device will never be completely secure. Most of your risk is removed if you make a best effort to only use apps from legitimate sources and apply security updates. If you are keen you can also install a antimalware app like lookout or configure iptables.
.

fffft said:
In might be a theoretical advantage to not be rooted. But you loose a lot of functionality for that security "gain". Pragmatically though there have been plenty of malware exploits that can root your device as part of their incursion. So it's hard to believe that you are gaining much security by avoiding root on your handset.
Your device will never be completely secure. Most of your risk is removed if you make a best effort to only use apps from legitimate sources and apply security updates. If you are keen you can also install a antimalware app like lookout or configure iptables.
.
Click to expand...
Click to collapse
Agree 100%. Hence my concern about being rooted currently and not having SuperSU installed to control what apps can gain and use root access. Installation of SuperSU was a byproduct of every other root method I've used and thus I was concerned about having rooted with towelroot and not having SuperSU installed.
Sent from my SM-G900W8 using XDA Free mobile app

tawheed12 said:
Agree 100%. Hence my concern about being rooted currently and not having SuperSU installed to control what apps can gain and use root access. Installation of SuperSU was a byproduct of every other root method I've used and thus I was concerned about having rooted with towelroot and not having SuperSU installed.
Sent from my SM-G900W8 using XDA Free mobile app
Click to expand...
Click to collapse
If you choose to root your phone you should forget about OTA`s imo as this causes only issues in most cases and the loss of root. Disable/uninstall or freeze all system apps regarding OTA`s and flash an updated rom with Mobile Odin Pro and you`ll keep root BTW rooting has so much more advantages like AdAway adblocker, freezing all the unused Samsung apps/widgets, backup and restoring of apps with TB etc etc.

You dont need SuperSU for root. Its on a handler for it. It stops malware accessing root without your notice....

verizon note 4 5.1.1 root "very unstable"

Last night I was bored and tried kingroot again on 5.1.1. It had been a while since I had tried, and it always said they were looking for a method. This time, it rooted successfully, but made the system very unstable. It caused Lag, and the keyboard stopped functioning, but root checker confirmed root. Temp root of course.

Reminon said:
Last night I was bored and tried kingroot again on 5.1.1. It had been a while since I had tried, and it always said they were looking for a method. This time, it rooted successfully, but made the system very unstable. It caused Lag, and the keyboard stopped functioning, but root checker confirmed root. Temp root of course.
Click to expand...
Click to collapse
I stopped messing with KingRoot some time ago, just didn't seem worth my time considering you lose root after a reboot. Especially when certain apps require a reboot to take effect, such as Adaway, Xpose, and several others. I'm more-or-less fine without root, but that doesn't mean I wouldn't root my phone if I were to come across a stable and perm root solution.:cyclops::fingers-crossed:

will4958 said:
I stopped messing with KingRoot some time ago, just didn't seem worth my time considering you lose root after a reboot. Especially when certain apps require a reboot to take effect, such as Adaway, Xpose, and several others. I'm more-or-less fine without root, but that doesn't mean I wouldn't root my phone if I were to come across a stable and perm root solution.:cyclops::fingers-crossed:
Click to expand...
Click to collapse
I was on KK, and a friend of mine updated to 5.0.1. I said screw it and fully updated, not caring about root anymore. If this were more stable I would use it more. Temp root is annoying, but it survives hot reboots, which is sufficient for apps most of the time..

Reminon said:
I was on KK, and a friend of mine updated to 5.0.1. I said screw it and fully updated, not caring about root anymore. If this were more stable I would use it more. Temp root is annoying, but it survives hot reboots, which is sufficient for apps most of the time..
Click to expand...
Click to collapse
I tried to use the hot reboot feature of a rooted reboot app I have on my Tab 3 8.0 after installing something like Xpose, but the root didn't survive. The only real reason I tried to install Xpose was to use the Motorola hotspot app found in it. I'm currently using the paid version of FoxFi and it works great, it's just a four step activation compared to the one touch I got spoiled by on my S4. No biggie.

Over on AT&T note 4 thread someone said that they have temp root for 5.1.1
Edit: someone already posted that disregard this ..[emoji4]
Sent from my SM-N910V using Tapatalk

Temp root only will give two things uninstall bloatware, SD card fix.... I don't see any other advantage, well I'll give a shoot and put my conclusion over here

EdrickMG said:
Temp root only will give two things uninstall bloatware, SD card fix.... I don't see any other advantage, well I'll give a shoot and put my conclusion over here
Click to expand...
Click to collapse
When I was on 4.4.4, I realized I could use the default file explorer to manage my SD card, meaning copy to, delete from, or anything else I needed to do with it. I'm currently on 5.1.1 now and have been for about a few weeks now. On occasion, when I install a big game, I'll get a prompt asking me if I want to move the app to my SD card, so no need for the SD card fix app. The only thing I don't like about the 5.1.1 update, though, is that the sidebar seems to pop out a bit slower than it did on 4.4.4, but that's to big a thing for me. Since I have the two apps I use the most that can be accessed from the sidebar on my Pie Control app, I can access them much quicker. Keep the dream of root alive, people. It'll come someday, hopefully. If not, at least we have cool phones to play with.

ok i can confirm that i obtained temporary root, uninstall all bloatware... so well its not perfect cuz system its very unstable but at least its a begining, now im gonna give a try to sd card fix and other stuff...
Ok SD card fixed worked... but i dont belive it will remain after reboot, so.... well at least i uninstall that Amazon stuff and Activation Agent "Not a Verizon card" stuff

Wait What........... Are we saying we now have temp root on 5.1.1

gersrt said:
Wait What........... Are we saying we now have temp root on 5.1.1
Click to expand...
Click to collapse
That's it right, at least now you can uninstall all Verizon and Amazon crap from the system

Would it be possible to disable the ****ty Verizon logo boot screen and have it disabled after reboot. Thanks

It's important saying temporary root was achieve in BPA1 bootloader, 5.1.1

I managed to get a keyboard to open by switching from the stock keyboard to kii keyboard. Have not tried any others. Is there a mod we can do for hotspot with temp root to use the native hotspot app? I'm so tired of using foxfi.

Is there a safe upgrade yet from 5.01 to 5.1.1 Thanks. I need to know in case I need to roll back to 5.01.
Thanks

Wasn't the sole purpose of the BPA1 update to "remove pre-installed Amazon apps"?

nubleeet said:
Wasn't the sole purpose of the BPA1 update to "remove pre-installed Amazon apps"?
Click to expand...
Click to collapse
Only the appstore and its widget..

Most of bloatware remains like NFL, and even instagram, however after deleted most of it, I don't know which one.. Allow me to use Hotspot without foxfi

Unstable indded
Reminon said:
Last night I was bored and tried kingroot again on 5.1.1. It had been a while since I had tried, and it always said they were looking for a method. This time, it rooted successfully, but made the system very unstable. It caused Lag, and the keyboard stopped functioning, but root checker confirmed root. Temp root of course.
Click to expand...
Click to collapse
I tried it out and it says it root is successful, but on my phone it just locks up after the rooting. I just wanted to uninstall the crap. Bummer.

Ok So Ive been checking the ATT note 4 forum and they have been suggesting that the root exploit may have been found through the Note 4 Stock keyboard. A suggestion also made was before you root change your keyboard to Swype mode then root and it appears to be more stable. Maybe someone could try install a third party keyboard before root and see if it makes a differwnce.

Nada
gersrt said:
Ok So Ive been checking the ATT note 4 forum and they have been suggesting that the root exploit may have been found through the Note 4 Stock keyboard. A suggestion also made was before you root change your keyboard to Swype mode then root and it appears to be more stable. Maybe someone could try install a third party keyboard before root and see if it makes a differwnce.
Click to expand...
Click to collapse
So I downloaded Swype and Nada. Just keeps locking up. Kingroot even updated a few min ago to 4.8.1. I thought yes! But still false hopes. Still locks up for me and can't do a darn thing. Can't wait until my contract is up I am so dumping Samsung and Verizon. I think I am gong back to a flip phone and a laptop. So tired of no root and feel like I got duped into this phone.

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.