@Moondroid No joy with SecurityLogAgent. Titanium didn't turn it up in searching on security, log, or agent. None of the hits were close to being the bad actor.
Nice try, though.
Nice try, though.
Here's how I ROOTED Nougat on my S7 Edge G935T
- Thread starter Araltd
- Start date
First thing, I misquoted re the SuperSU binary update nag. Can't remember how to get rid of that, but it seems there is a way, as I know I've encountered it multiple times in the past. I'll ponder it.
Freezing the securitylogagent -- I assume TiBu search would've found something called com.samsung.android.securitylogagent -- is for a "system has been modified" nag. But maybe the securitylogagent is just on the T-Mobile? And the 2nd link below is for the S7, not the Edge . . .
https://forum.xda-developers.com/tmobile-s7-edge/how-to/guide-post-root-common-bugs-fixes-t3427600 (Bug #3)
https://forum.xda-developers.com/tm...ow-rooted-standard-s7-nougat-perfect-t3579892
Edit: and here's another mention, but also for the T-Mobile variant:
https://forum.xda-developers.com/tmobile-s7-edge/how-to/s7-edge-debloat-list-t3330211
I think you'd like this. Follow directions to a T.
https://forum.xda-developers.com/showpost.php?p=71700562&postcount=688
Yeah I saw this, probably about the time you were writing your post.
I noticed it uses SuperSU 2.79, which reminds me of something I've been wanting to ask: Is the 2.82 version one that chainfire built, or is it after he sold to the Chinese? I can't remember exactly, but for some reason I had it in my mind to avoid any version after 2.79. Just curious about this.
I'll probably get around to going for root sometime tonight. Will post results here.
Last edited:
I've got 2.82 from "Chainfire & CCMT" which, I guess, is associated with China. Tucked into unroot.bat, the from the last URL cited (er... no unroot, pls) are 2.79.apk, 2.79.img, and supersu.cmd (which seems to be mostly "touch this file" - how touchy feely). I don't know wha thet .img file does in the following: copy 279.apk to the phone and install it. A) Will that even work, and B) will that overwrite or displace 2.82? I assume freezing SuperSu 2.82 prior to installing 2.79 will cause Bad Things to happen.Yeah I saw this, probably about the time you were writing your post.
I noticed it uses SuperSU 2.79, which reminds me of something I've been wanting to ask: Is the 2.82 version one that chainfire built, or is it after he sold to the Chinese? I can't remember exactly, but for some reason I had it in my mind to avoid any version after 2.79. Just curious about this.
I'll probably get around to going for root sometime tonight. Will post results here.
Just to say (to all reading), I don't mean to revisit an old controversy about SuperSU, and I'm sure I was even wrong to bring up whatever differences of origin or development there might be between v2.79 and v2.82. In fact it appears that v2.76 was the last one that was purely Chainfire's work. So one might say it doesn't matter which of the SuperSU's mentioned in this thread that we use . . . yes? So my bringing it up here was pretty much irrelevant.
But to explain the question for anybody who doesn't know why I asked the question, I also reference an XDA discussion from three years ago on the subject of Chainfire vs CCMT. Again, not to stir up controversy or distract from the sole purpose of this thread's existence, which is How to Root Nougat on the S7/Edge.
(Edit: Chainfire himself had the last word in the XDA thread referenced above. Take it all with a grain of salt. The thing is, rooting and especially unlocking bootloaders carry their own inherent security risks.)
Last edited:
I've got too many things demanding my attention to get into Chainfire, China, and risk exposure. Anyone using XDA should have a realistic sense of vulnerability. "Can't happen here" thinking carries its own ...um... reward.
Onward. My initial question regarding any SuperSU i,s does updating the binary, as nagged any time SuperSU is opened, break root? My sense is the answer is "yes, it breaks root." OK, got that. The next question is "How do I remove that nag?" The suggestion is 2.79 may (or not) be the way to no more nags. I have no need to deny 2.79, say it's too old or not the latest and greatest. As long as TI, FX, and a couple of "need route" utilities work, and I don't get nagged, life is good.
Finally, I want to be sure I don't accidentally (fat finger) back into accepting an OTA, which, of course, will never work, will break root, and generally take the shine off my day. How do I keep OTA messages from showing up, waiting for my fat fingers?
My S7 is an unlocked VZW phone.
Onward. My initial question regarding any SuperSU i,s does updating the binary, as nagged any time SuperSU is opened, break root? My sense is the answer is "yes, it breaks root." OK, got that. The next question is "How do I remove that nag?" The suggestion is 2.79 may (or not) be the way to no more nags. I have no need to deny 2.79, say it's too old or not the latest and greatest. As long as TI, FX, and a couple of "need route" utilities work, and I don't get nagged, life is good.
Finally, I want to be sure I don't accidentally (fat finger) back into accepting an OTA, which, of course, will never work, will break root, and generally take the shine off my day. How do I keep OTA messages from showing up, waiting for my fat fingers?
My S7 is an unlocked VZW phone.
I'm not getting the nag, for some reason. Actually don't recall ever being nagged whenever I've installed an "older" version of SuperSU (at least never more than once), so that's a bit of a mystery to me. Wish I could offer some clue but I got nothing, sorry.
BillA's Samsung_Security+OTA_Disabler didn't take care of that? Everything I can find on my now-rooted Edge is disabled. I'm seeing this when I view Settings > Apps > Show system apps. Two in particular named "Software update" (one with a green icon and another with blue) and a third named "System updates", all show as "Not installed".
All of that just to end with I've got no help to offer. Just relaying what I've got now on my G935V phone with rooted G935U BRA1 fw.
- - -
Yep, rooted successfully as follows:
1. Flashed G935UUES4BRA1_7.0 in Odin 3.13.1 (Patched version) AP, BL, CP and CSC slots.
2. Enabled Dev Options, OEM Unlocking, USB Debugging, made sure no Security was set (not even swipe).
3. Forgot to delete the old RSA keys, so when I ran the Security+OTA_Disabler in CMD window the first time, I got errors. Then saw the "Allow" prompt on the phone, tapped that, ran the Disabler batch file again.
4. Flashed the Eng_Boot .img in Odin (3.13.1 regular version) AP slot. (Did not clear cache before it rebooted coz it was too fast for me.)
5. Powered off, booted to Recovery, cleared cache, restarted.
6. Let it set undisturbed for about 35 minutes.
7. Ran (in Cmd window) the "Root.bat.no_lag_no_kernel_editor_app_needed" bat file.
8. Let the phone set again for about 40 minutes. Rebooted, opened SuperSU 2.79. Yep, it's there (no prompt to update binary). Backed out, installed Joey Krim's Root Checker Basic . . . Root! Yes!!!
I might have a bit of lag but I haven't yet done any tweaking aside from disabling about a dozen more apps. Wifi remembers the password. Kernel Adiutor and SystemUI Tuner are installed, will have a go at both soon.
I have not activated the phone on VZW yet, so nothing to report on that.
MANY THANKS to ALL who have contributed to this thread, if even just asking questions that led to some good-to-great answers and more help and info overall.
Last edited:
I can live with the nag. If it's not going to break root, then I can say "yes, now shut up!" I guess I'll say "No, shut up anyway."
I'm not sure where the OTA paranoia started. I think it's some sort of notification. But Samsung and who knows who else all want me to load their bloatware. It may be the OTA thing is really just another "improve your life with..." from Toadsuck Systems. Yes, I followed the steps you listed, and, yes, they work. Which is why I may be clueless about that OTA thing. Short response: nevermind. [/ grin]
Great thanks for the effort and wisdom; a virtual case of Sam Adam's best for your help.
I'm not sure where the OTA paranoia started. I think it's some sort of notification. But Samsung and who knows who else all want me to load their bloatware. It may be the OTA thing is really just another "improve your life with..." from Toadsuck Systems. Yes, I followed the steps you listed, and, yes, they work. Which is why I may be clueless about that OTA thing. Short response: nevermind. [/ grin]
Great thanks for the effort and wisdom; a virtual case of Sam Adam's best for your help.
Eng-Boot for Samsung S7_G930x_QC and S7Edge_G935x_QC on BootLoader "A/10"
For bootloader Rev.A/10, simply follow this rooting method:
https://forum.xda-developers.com/showpost.php?p=81410291&postcount=1850
For bootloader Rev.A/10, simply follow this rooting method:
https://forum.xda-developers.com/showpost.php?p=81410291&postcount=1850
Last edited:
It doesn't matter which version you have, any G930x can be flashed to any carrier version, though the "U" version if preferred.
The link I posted shows that there's a newer version out with bootloader Rev.B/11, but there's no eng-boot available yet, so don't upgrade beyond RevA/10 if you want to have root.
Attachments
Last edited:
Your version is ACSH3, where the first letter "A" means it's bootloader Rev.A/10 which is rootable, just don't upgrade to the latest "B" firmware (BCTA3), currently that can't be rooted.
I think this is good news for me as I just got my hands on an att s7 (SM-G930A) flat screen with the same android 8.0 build number that I was looking to root if at all possible and or install lineage os onto (sounds like that last one isnt gonna happen). Whats the best way I could go about at least rooting it?
~SG
I think this is good news for me as I just got my hands on an att s7 (SM-G930A) flat screen with the same android 8.0 build number that I was looking to root if at all possible and or install lineage os onto (sounds like that last one isnt gonna happen). Whats the best way I could go about at least rooting it?
~SG
Do NOT update your current firmware, simply follow these step by step instructions.
Do not skip or change anything, do not try to be creative, otherwise it WILL fail.
https://forum.xda-developers.com/showpost.php?p=81410291&postcount=1850
Can someone let me know if my phone is rootable ? Here is some info:
Android: 8.0.0
Baseband : G935TUVSACSI1
Build #: R16NW.G935TUVSACSI1
kNOX: 3.1
Thanks in advance
Android: 8.0.0
Baseband : G935TUVSACSI1
Build #: R16NW.G935TUVSACSI1
kNOX: 3.1
Thanks in advance
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone