Database Develop

Nonroot vs Root

Hey guys, im stuck on deciding whether i should root my note 4 or not. What's really bugging me is that i will trip knox and will it devalue the phone?
Any benefits of rooting it right now? vs nonroot
i've seen some threads of rooting problems with some apps and such and im not sure if i should wait or not. Im coming from a rooted s4 and i kinda miss being rooted. Come on guys post what you think here!

Belongs in the Q&A section

bipoler said:
Belongs in the Q&A section
Click to expand...
Click to collapse
You're right im sorry guys
Any possbility of a mod moving it?

marcustdu said:
Hey guys, im stuck on deciding whether i should root my note 4 or not. What's really bugging me is that i will trip knox and will it devalue the phone?
Any benefits of rooting it right now? vs nonroot
i've seen some threads of rooting problems with some apps and such and im not sure if i should wait or not. Im coming from a rooted s4 and i kinda miss being rooted. Come on guys post what you think here!
Click to expand...
Click to collapse
Root if something you want needs it, otherwise there's not any need. Do you need tomatoes? I dunno.

marcustdu said:
Hey guys, im stuck on deciding whether i should root my note 4 or not. What's really bugging me is that i will trip knox and will it devalue the phone?
Any benefits of rooting it right now? vs nonroot
i've seen some threads of rooting problems with some apps and such and im not sure if i should wait or not. Im coming from a rooted s4 and i kinda miss being rooted. Come on guys post what you think here!
Click to expand...
Click to collapse
As stated above, root if you have the NEED to root. For me, I got plenty. Smoothness, debloating, batterylife, awesome rooted apps out there (I know..only three reasons.) For others, they need a specific app they need to run on their phones and it will need root.
If non of these are an issue to you, do not root. If you cannot think of a reason to root without having the benefit of root vs non root listed out to you, I will advice you do not root because that tells me you actually do not have the need to root. Make sense?
As far as knox is concern...I will say only trip if if you have no need to send it straight to Samsung while your phone is still functioning. I say this because they will send it right back to you. Now if your phone is fried, how will they check exactly if knox is tripped? The carriers do not care, tmobile do not care. Most of the workers think nova is a rooted app. Thats how much they know about root.
You go to a carrier, simply do not give them a reason to think you are rooted. People like to take a phone with custom roms and custom kernels on there...thats not smart. They boot your phone, a message at the top most left of the phone will tell them you are rooted. Always go to the store with stock ^.^
Hope that helps!

I have the Note 4. I root it about 2 weeks later after I got it. My reason: get ride of all the bloat junk that I dont need; now I can write to my SD card; unlimited hotspot; lean machine and good battery life. Its good to have su access.

mgbotoe said:
As stated above, root if you have the NEED to root. For me, I got plenty. Smoothness, debloating, batterylife, awesome rooted apps out there (I know..only three reasons.) For others, they need a specific app they need to run on their phones and it will need root.
If non of these are an issue to you, do not root. If you cannot think of a reason to root without having the benefit of root vs non root listed out to you, I will advice you do not root because that tells me you actually do not have the need to root. Make sense?
As far as knox is concern...I will say only trip if if you have no need to send it straight to Samsung while your phone is still functioning. I say this because they will send it right back to you. Now if your phone is fried, how will they check exactly if knox is tripped? The carriers do not care, tmobile do not care. Most of the workers think nova is a rooted app. Thats how much they know about root.
You go to a carrier, simply do not give them a reason to think you are rooted. People like to take a phone with custom roms and custom kernels on there...thats not smart. They boot your phone, a message at the top most left of the phone will tell them you are rooted. Always go to the store with stock ^.^
Hope that helps!
Click to expand...
Click to collapse
Thank you for your input, yes I do have things such as you listed for rooting! Merry Christmas!
chong67 said:
I have the Note 4. I root it about 2 weeks later after I got it. My reason: get ride of all the bloat junk that I dont need; now I can write to my SD card; unlimited hotspot; lean machine and good battery life. Its good to have su access.
Click to expand...
Click to collapse
Thanks for the response! I think I know what I'm doing now [emoji14]
Merry Christmas!

Im in the same boat, sorta. Ive always rooted. Everything i had, even the old windows phones. This is the longest ive lasted non rooted. Im getting the itch. My question, if i root, flash twrp, does it erase my data? Not a big deal really, but im on level 110 on ea sports king of the course. Would suck to start over.
Sent from my SM-N910T using XDA Free mobile app

donnyp1 said:
Im in the same boat, sorta. Ive always rooted. Everything i had, even the old windows phones. This is the longest ive lasted non rooted. Im getting the itch. My question, if i root, flash twrp, does it erase my data? Not a big deal really, but im on level 110 on ea sports king of the course. Would suck to start over.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Neither rooting nor flashing a recovery will wipe your data. Some phones ship with the unlockable bootloaders and the unlocking process wipes the data (for example, on Google Nexus devices). But the bootloaders on T-Mobile Samsung phones are unlocked by default, so flash away

chenxiaolong said:
Neither rooting nor flashing a recovery will wipe your data. Some phones ship with the unlockable bootloaders and the unlocking process wipes the data (for example, on Google Nexus devices). But the bootloaders on T-Mobile Samsung phones are unlocked by default, so flash away
Click to expand...
Click to collapse
Thanks dude, im on tmobile. Root then backup!
Sent from my SM-N910T using XDA Free mobile app

Its done. I voided it!
Sent from my SM-N910T using XDA Free mobile app

Rooted is the way to go! Only reason I haven't rooted yet is because I'm waiting for Android 5.0 to drop next month hopefully ! Then I will gladly root. Phone is much better when it is under your control.
ROLL THAT SHT, LIGHT THAT SHT. SMOKKKKE THAT SHT

Those of you who rooted the Note 4, can you confirm if root disables:
Private mode - Possible fix (old fix)
S-Health (maybe only if using Xposed) - Possible fix?
Screen Mirroring (wireless) - Possible fix?
Recording calls (?)
I would want to root mainly to gain access to the external SD card, possibility to enable/disable flight mode using profiles and wouldn't mind about OTA ora Knox 0x01.
But it's annoying to lose those functions for me.

Updated previous post with some links to possible fixes.

virtualdj said:
Those of you who rooted the Note 4, can you confirm if root disables:
Private mode - Possible fix?
S-Health (maybe only if using Xposed) - Possible fix?
Screen Mirroring (wireless) - Possible fix?
Recording calls (?)
I would want to root mainly to gain access to the external SD card, possibility to enable/disable flight mode using profiles and wouldn't mind about OTA ora Knox 0x01.
But it's annoying to lose those functions for me.
Click to expand...
Click to collapse
I rooted but on a custom ROM and I have zero issues with private mode or S-health. I guess the issue is when you're only rooted on stock ROM. But apparently there's walkarounds for those issues.

shook187 said:
I rooted but on a custom ROM and I have zero issues with private mode or S-health.
Click to expand...
Click to collapse
Thanks, but actually I was interested on (possible) issues on stock ROM and, most importantly, if the walkarounds really work.

[q] [may 29]sgs5 at&t is rooting possible? Answer i am about to explode.

It is about time I get some straight-forward answers. I'm tired of Googling everything I can and it not being what I think it is.
It is about time I get some straight-forward answers. I'm tired of Googling everything I can and it not being what I think it is.
What I have come to you for, XDA, is some light in the cave.
WILL THERE BE A WAY TO ROOT THE AT&T SAMSUNG GALAXY S5 VARIANT?!
Towelroot doesn't work. And if quite frankly tired ****less of all the posts that still exist talking about it.
Is there anything in development? All I can see now is SafeStrap and Multi-Tool but if you aren't rooted these do nothing. I just want some information for God's sake. Will ANYONE tell me what is being done about the development of the device's rooting? Is anyone even trying anymore? And if so, tell me! More importantly, if there are people, why aren't they being talked about? With as many S5's as there are out there (at least to me since I know about 10 people who use them regularly) why wouldn't anyone be trying?
PLEASE people get it together!
I have come from only 3 devices, but I was able to root and mod all of them. Rooting and Modding is love and life to me and is pretty much all I sincerely love about Android. The fact that I can't afford a new phone at this stage is sad, and I have grown tired of the bloating of TouchWiz, especially with the Lollipop update. I know that a rooted S5 would be extremely awesome, but since there is nothing about it being worked on I suppose I'll just have to live with the rubbish they call TouchWiz.
And if by some chance someone who can develop something like this reads this thread, please, respond, PM me, do SOMETHING. TELL THE XDA WORLD, because I GUARANTEE there are more of me out there who have longed for this but have just lived with it. BE A GAME CHANGER A DO SOMETHING ABOUT IT.
Don't give me the, "Knox and bootloaders are hard to pass by, especially with the new more secure versions." Because guess what, geohot did it once. Not like it lasted, but the fact is is that it worked at one point. It may be harder now, but it's still possible. PLEASE DO SOMETHING. PLEASE TRY.
Anyway, best of luck to all of the users. And anyone who has read this please leave a comment and tell me what you know. Many days I'm left alone, commentless with my threads. This is one I truly need to be acknowledged.
THANK YOU FOR YOUR TIME

Well that's a big thread revealing nothing about your device other than its an s5. There are ways to root with towel root unless you have the 5.0 ota.

dirtydodge said:
Well that's a big thread revealing nothing about your device other than its an s5. There are ways to root with towel root unless you have the 5.0 ota.
Click to expand...
Click to collapse
Well it's pretty obvious that it's AT&T. 5.0 L and Towelroot has never worked before.

ElectricBiskitz said:
Well it's pretty obvious that it's AT&T. 5.0 L and Towelroot has never worked before.
Click to expand...
Click to collapse
Towel root has worked and still does on nce. If you were on OA1 towel root wouldn't work unless you downgraded to use it then go back to OA1. And no it don't work on 5.0. There are multiple kernels and builds that att has put out that it didn't work on without downgrading. But just for future reference is always helpful if you include your build, version, etc. Like i said there are multiple builds that it didn't work on unless you downgraded is only the 5.0 that you can't downgrade.

dirtydodge said:
Towel root has worked and still does on nce. If you were on OA1 towel root wouldn't work unless you downgraded to use it then go back to OA1. And no it don't work on 5.0. There are multiple kernels and builds that att has put out that it didn't work on without downgrading. But just for future reference is always helpful if you include your build, version, etc. Like i said there are multiple builds that it didn't work on unless you downgraded is only the 5.0 that you can't downgrade.
Click to expand...
Click to collapse
I said that I have Lollipop so everything you're saying won't help. Plus I know you wouldn't have known anyway but I have tried all of this way before Lollipop. I tried downgrading from OA1 at the time to NCE and I ended up in a bootloop. The kernel was faulty. I had to reset my phone in a very long, aggravating process to get it back. I NEVER want to go down that road again. And like I said in the entire post, I'm just looking for a pioneer to try again and make a geohot move on Lollipop. And no offense to you, you wouldn't have known this about me anyway, but your kind of information was exactly what I was trying to steer away from. And here it comes, right back at me. I'm just tired and sick of all the people who just do, essentially, a copy/paste of common information. When in my circumstance, am looking for something difference. Again, no harm to you, but anyone and everyone that has ever responded to my threads because it's all the same.

As someone who used to reverse engineer software, updates to said software usually patch those exploits. It's not usually easy to regain a new exploit and can take massive amounts of time. I can't speak for other devs but (at the time I did this stuff and still currently) I have a demanding full time job and a family, which come first over a hobby. I can guarantee I will never buy another Samsung phone again because of this. I know it's not always feasible, but maybe look into getting an HTC phone with developer options that is unlocked from the factory. Venting on here will get your cause nowhere.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

Forum is trying to help you!
ElectricBiskitz said:
Well it's pretty obvious that it's AT&T. 5.0 L and Towelroot has never worked before.
Click to expand...
Click to collapse
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.

Besides the fact there are already a metric ass ton of threads in this phone's forum discussing rooting the 900A.
I've been reading them for weeks now after I was overzealous and took the OTA to OC4 figuring there was a root solution already..... There wasn't, and oh well... My fault for not researching first, but it's making me keep my Note 2 until something comes up.
Hell something may already be out, but with rants like yours..... Feel free to enjoy the great advice in the links in my signature.

wwit said:
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
So wait... You have a method to get him from ota 5.0 to a muniz method 5.0? I was under the impression that was not possible once you took the ota ( i didn't, but I'm still curious)

ota 5.0 root?
wwit said:
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
Ok, so I'm sorry if i've got this wrong, but as the user above stated, I too have been scouring the web and FDA searching for a way to root an at&t galaxy s5 with an OTA u5.0 lollipop update. From all the research i have done, I have found no resolution to the locked bootloader. Are you saying that you can root the stock, unrooted, locked bootloader, sm-g900a running lollipop 5.0? If so, I will gladly donate to your Paypal for detailed instructions on how to do this! I am no noob at rooting, having rooted every galaxy since the skyrocket,. But this lollipop crap is driving me crazy. Any help is greatly appreciate!!

wwit said:
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
I need this please! I have an at&t Samsung S5 lollipop 5.0 please guide me

I have not seen any solutions for people who took Ota update. Did you make the exploit yourself? If not can you point out the source?
Thanks!

lowspeed said:
I have not seen any solutions for people who took Ota update. Did you make the exploit yourself? If not can you point out the source?
Thanks!
Click to expand...
Click to collapse
My phone just automatically downloaded the 5.0 update a few weeks ago. I attached a screenshot of my phones specs

I replied to the person who said he has instructions. ..

wwit said:
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
if you're able to root OC4 on a G900A, i'm all ears.
so far i'm unable to install TWRP (fail auth) using odin and it seems it only works for 900F or other models, not 900A specifically that has never been previously rooted. all posts on the topic suggests you cannot downgrade from OC4 and any attempt is futile at the moment.

Rooted 5.0
tmac200913 said:
My phone just automatically downloaded the 5.0 update a few weeks ago. I attached a screenshot of my phones specs
Click to expand...
Click to collapse
Hi, I'm trying to make time to create the document to show how I did it. I intend to recreate the process again on my handset and include screenshots as I go through.
Basically the only way I could get my handset to 5.0 root was to take the handset back to NCE stock firmware (by the way I have all the files on my laptop to do this) using ODIN v3.09. This took my back to G900AUCU1ANCE (4.4.2) April 2014 release. I installed Towelroot, busybox and Safestrap. Did a backup of the device (when I went back to 4.4.2 I then configured my device to look and feel how I wanted it to be because I wanted to restore the data partition once on Lollipop - but this is a required part of the upgrade). You need to use Safestrap to create a backup folder structure on the SD card so you can dump the 5.0 (OC4) rooted backup on to restore later in the upgrade process. I then installed G900AUCU2ANG3 (4.4.2) September 2014 release using Safestrap. I then installed the G900AUCU2AOA1 (4.4.4) February 2015 release and then used Safestrap to take another backup. Then I did an advanced wipe in Safestrap (excluding the SD card) and restored the OC4 rooted backup (I found online I also have this file). Once that restored I then within Safestrap selected the reboot > download mode (don't restart the handset into Lollipop before doing this process - the whole process will fail). Once the handset rebooted into Download mode I connected the handset to ODIN v.3.10.6 and installed the G900A_OC4_Stock_Partitions_wOA1_BL.tar.md5 (using the AP option in ODIN). Once that completed the handset rebooted and after 5-10 mins started to upgrade files. Once that finished the handset was on 5.0 - the same as the screenshot you've posted and it's rooted. I have SuperSU installed working fine and I used Root Checker Basic to confirm the device is rooted. More so I then went on to sideload the G900A_OC4_TetherAddOn so I could get native wifi tethering because AT&T still had this locked down in the root 5.0 I installed above.

anyone verify this?

Not sure they started out on 5.0...I don't know of anyone who has successfully downgraded once on OC4.

wwit said:
Hi, I'm trying to make time to create the document to show how I did it. I intend to recreate the process again on my handset and include screenshots as I go through.
Basically the only way I could get my handset to 5.0 root was to take the handset back to NCE stock firmware (by the way I have all the files on my laptop to do this) using ODIN v3.09. This took my back to G900AUCU1ANCE (4.4.2) April 2014 release. I installed Towelroot, busybox and Safestrap. Did a backup of the device (when I went back to 4.4.2 I then configured my device to look and feel how I wanted it to be because I wanted to restore the data partition once on Lollipop - but this is a required part of the upgrade). You need to use Safestrap to create a backup folder structure on the SD card so you can dump the 5.0 (OC4) rooted backup on to restore later in the upgrade process. I then installed G900AUCU2ANG3 (4.4.2) September 2014 release using Safestrap. I then installed the G900AUCU2AOA1 (4.4.4) February 2015 release and then used Safestrap to take another backup. Then I did an advanced wipe in Safestrap (excluding the SD card) and restored the OC4 rooted backup (I found online I also have this file). Once that restored I then within Safestrap selected the reboot > download mode (don't restart the handset into Lollipop before doing this process - the whole process will fail). Once the handset rebooted into Download mode I connected the handset to ODIN v.3.10.6 and installed the G900A_OC4_Stock_Partitions_wOA1_BL.tar.md5 (using the AP option in ODIN). Once that completed the handset rebooted and after 5-10 mins started to upgrade files. Once that finished the handset was on 5.0 - the same as the screenshot you've posted and it's rooted. I have SuperSU installed working fine and I used Root Checker Basic to confirm the device is rooted. More so I then went on to sideload the G900A_OC4_TetherAddOn so I could get native wifi tethering because AT&T still had this locked down in the root 5.0 I installed above.
Click to expand...
Click to collapse
This is funny.......there seems to be a huge disconnect between this and the actual issue in the OP which is someone that took the 5.0 OTA and wants root access. There currently is no way for him to gain root access. Instead you quoted, almost verbatim, my origina KeepRoot method and files: http://forum.xda-developers.com/showpost.php?p=59996087&postcount=4

muniz_ri said:
This is funny.......there seems to be a huge disconnect between this and the actual issue in the OP which is someone that took the 5.0 OTA and wants root access. There currently is no way for him to gain root access. Instead you quoted, almost verbatim, my origina KeepRoot method and files: http://forum.xda-developers.com/showpost.php?p=59996087&postcount=4
Click to expand...
Click to collapse
Morning, first of all if you take a look at my first post you will see I have clearly stated your name and I have not tried to take credit for your process. Secondly I have only been replying to questions from members who have read my results and have then from my post asked how I did it. I have then simply explained again in the post you have replied to how I got to a rooted version of Lollipop.
Are ypu saying that if a handset takes the ota it is not possible to go back to NCE and then forward right through to rooted Lollipop or are just annoyed thinking I am trying to take credit for your work. I'm happy to guide a member step by step through a process if they want me to but I have already said it's not my discovery.

SuperSU and SafetyNet / Android Pay

This is the place to discuss anything and everything related to SuperSU and SafetyNet / Android Pay.
To clarify, I am not currently actively doing any development on having SuperSU pass SafetyNet detection, or having Android Pay work; the same way I put no effort into beating other root detection methods such as various enterprise security tools.
In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU.
While I may not agree with Google's stance, I'm not about to go messing with payment systems. Is it possible though? Probably yes.
This thread has been created because you guys simply cannot stop talking about this, so these posts can now go here, where I don't ever have to see them.

Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?

0.0 said:
Will v2.50 cause Android Pay not to work in 6.0? If so, I am guessing there is no way around it?
Click to expand...
Click to collapse
Root is a no no with android pay and I think custom ROMs are also out at the moment
Sent from my A0001 using Tapatalk

Pure Drive GT said:
Hey, thanks for your continued support for root on Android, was just wondering, is google making it harder to achieve decent root privileges, as in they don't want rooted devices or are they just unrelatedly changing up things which forces you guys to adapt?
On another note, is there any progress on root without the modded boot? This is by no means an ETA, just wanted to know if you think it's possible or the situation looks rather dire.
Thanks again for your many efforts!
Click to expand...
Click to collapse
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Many banking and financial apps restrict access on rooted devices; it's not just Google.
It makes sense in some ways: root access allows running things in the background to either circumvent, monitor, or interrupt program transactions. They're being paranoid, and I don't blame them.
I don't like the Google Pay concept (or Apple's either); like every other encryption or security system, it's destined to eventually be hacked.

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
Yep, I was able to add my debit card but not credit.
VZW LG G4

mdamaged said:
Well, just look at Android Pay, it will not allow one to add a credit card if it detects the device is rooted. So yeah, Google definitely wants to stop root, or at least make sure there is a strong dissuasion towards same. It's not a bad thing persae, as Google is just making the devices more secure for the masses. We 'power users' are lucky to have those such as Chainfire working so hard to get us what they can.
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...hy-android-pay-doesnt-support-rooted-devices/

shaggyskunk said:
Yet the Note 5 has been rooted for at least a couple of weeks
Click to expand...
Click to collapse
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.

Srandista said:
On Lollipop... And you also have to unlock your bootloader to do that, right? If yes, then you will trip the KNOX, and that mean you will loose some of your device functionality (Samsung Pay for example), without option to take it back. On the Nexus on the other hand, when you want to use Android Pay on Nexus, you can restore your phone to completely stock condition, without any trace of previously used root.
Also, all of this is completely irrelevant to carried device users, since they have a locked bootloaders.
Click to expand...
Click to collapse
I believe that it's only at&t and Verizon that locks the bootloader - And none in Canada and many other Countries.
Sent From my SM-N910W8 Running SlimRemix V5.1

Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.

NYZack said:
Had an interesting event, on 2.52.
I unchecked "Enable Superuser" in Settings, to attempt to use Android Pay (Android Pay still wouldn't work). Then, when I rechecked "Enable Superuser", the re-installation of the binary failed, and I was prompted to reboot to try again. However, then I got a boot loop (never even got the opportunity to enter my encryption code). The only way I was able to boot was to re-flash the modified boot.img and re-install SuperSU from the zip (no idea whether both steps were necessary).
I have a Marshmallow Nexus 6, encrypted. For what it's worth, I was previously rooted on 5.1.1, and, after updating to 6.0 and until I re-rooted, I always got a "Your device is corrupt" message on startup, despite being all stock.
Click to expand...
Click to collapse
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.

Lrs121 said:
Root doesn't have to be enabled for pay to fail. Any time the system partition is modified pay will not work. There was an xda news article on it. A quick Google search involving Android pay and root should find it.
Click to expand...
Click to collapse
I also found that having an unlocked bootloader will stop Pay working. When MM released I decided to go fully back to stock but kept the bootloader unlocked so I could flash MM. Pay still failed, so I've given up and gone rooted again.
Sent from my Nexus 6 using Tapatalk

Ch3vr0n said:
@Chainfire if you actually are able to pull off fully working stable root WITHOUT modifying the /system does that mean you MIGHT have opened the door into having root AND still being able to get OTA's?
Click to expand...
Click to collapse
osm0sis said:
Yup, all you'd need to do is reflash stock kernel to pass the boot partition EMMC check, or, we could automate restoring the previous stock kernel, flashing the OTA and then injecting the new stock kernel with root after flashing (à la AnyKernel2 or MultiROM). So many exciting possibilities there where custom recoveries are concerned.
Click to expand...
Click to collapse
Chainfire said:
Honestly it's not so different from using FlashFire to flash re-flash system, then OTA, then re-root. But it is easier, yes.
Click to expand...
Click to collapse
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Andrew Morykin 12:24
This should retain Android Pay, right?
Click to expand...
Click to collapse
Chainfire 12:58
+Andrew Morykin if it does, then it's by accident and not by design, and Android Pay will be updated to block it.
Click to expand...
Click to collapse
https://plus.google.com/+Chainfire/posts/aJbqUZ8PEP4
also, I was confused by this:
Chainfire said:
- I have not tested with encrypted devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935
Aren't
Nexus 6P / angler
angler-mdb08k-boot-systemless.zip
Click to expand...
Click to collapse
and
Nexus 5X / bullhead
bullhead-mdb08i-boot-systemless.zip
Click to expand...
Click to collapse
encrypted out of the box?

dabotsonline said:
This is indeed exciting. However, I noticed that @Chainfire posted this downside on Google+ :
Click to expand...
Click to collapse
How is that a downside?
It's exactly the same with every other form of root you will ever see. They don't want to support Android Pay (and some other stuff) on rooted devices. If we find a root that allows it, they will update their system to detect and block it. That cat and mouse game will not end as long as Google doesn't want Android Pay on rooted devices.
Maybe someone will make apps/modules that help circumvent this, but it certainly will not be me.
also, I was confused by this:
Aren't
Nexus 6P / angler
and
Nexus 5X / bullhead
encrypted out of the box?
Click to expand...
Click to collapse
Still can't test what I don't have.

russlowe73 said:
Factory images
Click to expand...
Click to collapse
So basically I have to go back to 100% stock using ADB, and then flash the new SuperSU stuff with any custom ROM? If so, what are the benefits of this other than getting Android Pay while rooted?

I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of root on the Nexus 6!!

efrant said:
Starting with Android 5.0, OTA updates are now block-based rather than file-based, so any modification to the system partition will cause the OTA to fail, even mounting the system partition as r/w.
Click to expand...
Click to collapse
Just to add to this, it's a whole-partition /system patch OTA if the device launched with Lollipop or later, anything that launched with KitKat is still receiving the old file-based patch OTAs. Modifying Settings.apk would likely trip either method for a lot of OTAs though, since it's a pretty central component.
galaxyuserx said:
I use Galaxy s6 G9200 HK with Kernel compiled by me, but i have problem with root 5.1.1 and i think in future too 6.0
These root method is integrated in kernel source or i can integrate with those "boot.img systemless" my selfcompiled kernel?(repack boot.img with kernel compiled by me)
Is possible to work this new root method to android 5.1.1?
I have problem with gain root when i use kernel compiled by me ( STOCK kernel have too this problem BOOTLOOPs and FREEZEs on boot system) and i don't know how slove it :/
I found on chineese forums root integrated in boot.img it working good and isn't comunicat "KERNEL is not SEandroid enforced" but when i try integrate my kernel with this boot.img error with boot system :/
Click to expand...
Click to collapse
Yup, it's all ramdisk changes so should be workable on any version of Android. Chainfire left instructions outlining the ramdisk changes in the WIP thread if you want to give it a try.
phishfi said:
I'm not sure if anyone has specifically mentioned this, but Android Pay still works with this form of on the Nexus 6!!
Click to expand...
Click to collapse
Yup, seems to be the case with most banking and root-detecting apps... for now.

Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.

secguy said:
Can someone with the non-system SU use this app: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground and post the results?
This app is supposed to do the SafetyNet checks cleanly, the same way Android Pay does them.
Would be interesting to see if it succeeds on devices with this new supersu version.
Click to expand...
Click to collapse
Just ran it and it passed.

Went ahead and installed su on a stock nexus 5, so far working well, android pay does not work but that was me being stupid and changing the host file and dpi before setting it up
I do notice a little input lag after this, not enough to even make me consider removing root, but it is noticeable, anybody else with this?

Marshmallow (6.0) Root Walkthrough?

I'm not sure where the appropriate place for this would be, and I apologize in advance if this isn't it, but I need some assistance.
For starters, I'm an absolute n00b when it comes to anything root and I don't understand the language and procedures to it, only how to do it by following instructions. Hence why I'm currently on a 4.4 untethered root.
I'm due for an upgrade this month and am torn between getting a later device with Lollipop or a newer device with Marshmallow. The deciding point is if there's any kind of walkthrough on rooting Marshmallow, preferably a dumbed-down version for nondevs like myself.
I know there's currently an experimental one provided by Chainfire, and I skimmed through it but couldn't really understand it.
So any assistance would be greatly appreciated.
@Chainfire If you could weigh in, that would be very helpful.

What are you on about untethered root this isn't IOS. Also it's just two simple steps:
Get a recovery for your device (TWRP preferably)
Use either the stable zip from this forum or beta zip thosent matter and transfer it to your device.
Flash it in the recovery done you're rooted

@Xmaster24 I appreciate the response. I was losing hope on getting an answer as I had already gone with the newer device for my upgrade.
In jcase's pie thread for the 2013 Motorola line, that's what the 4.4 root was referred to as. Wasn't confusing Android with iOS.
And I apologize for being so n00bish, but how would I go about getting TWRP recovery? I do know how to flash the zip from there as I used Safestrap on my current device (but I already needed root access for it to work).

Kodalades said:
@Xmaster24 I appreciate the response. I was losing hope on getting an answer as I had already gone with the newer device for my upgrade.
In jcases's pie thread for the 2013 Motorola line, that's what the 4.4 root was referred to as. Wasn't confusing Android with iOS.
And I apologize for being so n00bish, but how would I go about getting TWRP recovery? I do know how to flash the zip from there as I used Safestrap on my current device (but I already needed root access for it to work).
Click to expand...
Click to collapse
Depends on your device just tell me what it is and I can send you some info. Safestrap seems to be dead for at least a year thosent sound very safe lol.

Xmaster24 said:
Depends on your device just tell me what it is and I can send you some info. Safestrap seems to be dead for at least a year thosent sound very safe lol.
Click to expand...
Click to collapse
I'm getting the Samsung Galaxy S7 Edge. Considering it's not out in the US yet (I have it on preorder), I'm not sure if you'd be able to tell me anything at the moment.

Kodalades said:
I'm getting the Samsung Galaxy S7 Edge. Considering it's not out in the US yet (I have it on preorder), I'm not sure if you'd be able to tell me anything at the moment.
Click to expand...
Click to collapse
Oh dear yes it has just been released probably no rooting info available for quite some time considering samsungs stance on root and open software. Maybe check again in a few weeks or months

Xmaster24 said:
Oh dear yes it has just been released probably no rooting info available for quite some time considering samsungs stance on root and open software. Maybe check again in a few weeks or months
Click to expand...
Click to collapse
Bummer. Kinda expected something along those lines though so I'm not surprised.
Would getting TWRP or some other kind of recovery still be possible at the very least?

Kodalades said:
Bummer. Kinda expected something along those lines though so I'm not surprised.
Would getting TWRP or some other kind of recovery still be possible at the very least?
Click to expand...
Click to collapse
Flash fire could work but it requires root already. Doubt there are any easy exploits on a flagship just released phone

Xmaster24 said:
Flash fire could work but it requires root already. Doubt there are any easy exploits on a flagship just released phone
Click to expand...
Click to collapse
Makes sense. I really appreciate the help. If you happen to learn of anything more, please let me know.

Kodalades said:
Makes sense. I really appreciate the help. If you happen to learn of anything more, please let me know.
Click to expand...
Click to collapse
Guess not kingo root seems to be working :http://www.xda-developers.com/galaxy-s7-root/

Root n900a oc3?

I'm kinda a noob at this but I'm not completely clueless. .. I've tried a couple one click apps, watched a few videos, and read countless articles without any luck. .. can someone help me? If it's even possible....

From all I've read, no, you can't. You can root NC2 (Android 4.4.2 KitKat) or OC1. You might check this post out.

An old thread, but I just wanted to leave this for others.
There aren't any public tools to directly root the OC3, OC2, or OC1 Lollipop firmwares for the N900A.
However, it is possible to achieve root by wiping the phone, installing the NC2 (KitKat) firmware, and then upgrading the OCx, while preserving root access.
I had followed the threads (at the time back then) using SafeStrap methods, but I couldn't get SafeStrap to work with OC3, so I had to abandon SafeStrap and use FlashFire to install OC3 and maintain root.
After that, I deodexed OC3, install xposed, and was up and running happy.
I'm not sure exactly what Samsung fixed, but OC3 was released a full 18 months after OC2, so I think it's a more secure software release (only 2.5 years old, instead of 4+ years, heh). I recall that on OC2, some of the stagefright CVE's still showed as vulnerable, but I just ran the Zimperium app on OC3 and see it reports that it's not vulnerable to any of the CVEs.

@digitalcandy4me thanks for the helpful info. This is one of the few times I've read this solution. It's the only one I've seen that seems promising.
Like OP I'm newb. But I've never rooted a phone. I've done plenty of other tech but I hate coding. I just want to change the dumb stock rom on this phone. Bloatware haunts me simply on principal.
I have "unlocked" att 5.0 lollipop Samsung n900a 0c3 and info on this phone is crickets. I have no idea how to downgrade to 4.4, I'm not confident it will even work but I'll try it. I paid 70$ so no big deal + it seems like I couldn't even succeed in bricking this stupid vault.
ANYWAY could you possibly give some more detail on how to do this? I know people hate getting vague questions on this board but it seems like there's no where to find answers. I really have looked.
:crying:

FluppingCrud said:
@digitalcandy4me thanks for the helpful info. This is one of the few times I've read this solution. It's the only one I've seen that seems promising.
Like OP I'm newb. But I've never rooted a phone. I've done plenty of other tech but I hate coding. I just want to change the dumb stock rom on this phone. Bloatware haunts me simply on principal.
I have "unlocked" att 5.0 lollipop Samsung n900a 0c3 and info on this phone is crickets. I have no idea how to downgrade to 4.4, I'm not confident it will even work but I'll try it. I paid 70$ so no big deal + it seems like I couldn't even succeed in bricking this stupid vault.
ANYWAY could you possibly give some more detail on how to do this? I know people hate getting vague questions on this board but it seems like there's no where to find answers. I really have looked.
:crying:
Click to expand...
Click to collapse
Flash nc1 firmware, towel root....install busybox and safe strap and flash away.

FluppingCrud said:
@digitalcandy4me thanks for the helpful info. This is one of the few times I've read this solution. It's the only one I've seen that seems promising.
Like OP I'm newb. But I've never rooted a phone. I've done plenty of other tech but I hate coding. I just want to change the dumb stock rom on this phone. Bloatware haunts me simply on principal.
I have "unlocked" att 5.0 lollipop Samsung n900a 0c3 and info on this phone is crickets. I have no idea how to downgrade to 4.4, I'm not confident it will even work but I'll try it. I paid 70$ so no big deal + it seems like I couldn't even succeed in bricking this stupid vault.
ANYWAY could you possibly give some more detail on how to do this? I know people hate getting vague questions on this board but it seems like there's no where to find answers. I really have looked.
:crying:
Click to expand...
Click to collapse
Read my answer!

chrisnice906 said:
Flash nc1 firmware, towel root....install busybox and safe strap and flash away.
Click to expand...
Click to collapse
Maybe u should not be modifying phones.