• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Here's how I ROOTED Nougat on my S7 Edge G935T

Search This thread

billa

Senior Member
Mar 30, 2006
731
356
Are you saying I should kill the adb daemon before starting a root attempt, or are you recommending restarting during the pause after the first reboot? If so, I'm not sure how I can break through the running script to kill the daemon. If I can get that far, of course I can restart it, too.

My guess is you're saying that I should kill the adb daemon before trying to root (step 5).

In any case, I'll do a fresh stock flash and start over.

---------- Post added at 09:58 PM ---------- Previous post was at 09:46 PM ----------

WTF!!! SuperSU is present and Joey Krim says I'm rooted. I have utterly no idea why this worked despite the error message which, I assumed, said I didn't reach being rooted. Very, very strange... NTL I got where I'm wanted to go, even if I haven't a clue as to why I'm there.
giphy.gif


Yes, it's better to start running the script with no adb deamon running, since the script will invoke it on its own.
On top of Task Manager > Processes make sure there are no running ADB.EXE
If there are, right click on it and kill it.
Just follow this, don't skip anything, follow it step by step, trust me it works! ;)
https://forum.xda-developers.com/showpost.php?p=75418504&postcount=2527

p.s. The only thing I can think of about your weird issue, is that you may have more then one phone plugged in to the same pc, and while the script ran fine on the S7, the other one could have thrown those strange errors. Anyway, next time make sure there's only ONE phone is plugged in, all adb's stopped, and follow the step by step instructions. A similar situation has occurred to me in the past, and it was really frustrating trying to figure out the root cause. Now, this may or may not be in your case, nonetheless it's worth taking a look at.
 
Last edited:
  • Like
Reactions: RBEmerson

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
Yes, it's better to start running the script with no adb deamon running, since the script will invoke it on its own.
On top of Task Manager > Processes make sure there are no running ADB.EXE
If there are, right click on it and kill it.
Just follow this, don't skip anything, follow it step by step, trust me it works! ;)
https://forum.xda-developers.com/showpost.php?p=75418504&postcount=2527

p.s. The only thing I can think of about your weird issue, is that you may have more then one phone plugged in to the same pc, and while the script ran fine on the S7, the other one could have thrown those strange errors. Anyway, next time make sure there's only ONE phone is plugged in, all adb's stopped, and follow the step by step instructions. A similar situation has occurred to me in the past, and it was really frustrating trying to figure out the root cause. Now, this may or may not be in your case, nonetheless it's worth taking a look at.
Trust me, I had 2527 in front of me during the whole "adventure".

Good point about killing off an existing adb daemon before starting.
Code:
adb kill-service
adb wait-for-device
That should do it, no?

There was only one phone on the PC. NTL, I wonder if the previously running adb daemon wasn't causing problems.

At this point the phone is rooted although I don't understand why. I ran Root.bat one last time, so I could collect the error message about "text file busy". When the phone rebooted at the end of the third try, there was the open padlock icon. Root Checker confirms the phone is rooted. I added Busy Box (AFAIK it wasn't loaded) and updated SuperSU. Since then I've run Ti, FX, etc. without a complaint.

Looking at the piece of Root.bat I used, maybe everything completed as it should.
Code:
:SYSTEM
echo Installing Root
adb uninstall com.topjohnwu.magisk >NUL 2>&1
adb uninstall eu.chainfire.supersu >NUL 2>&1
adb shell rm /data/su.img >NUL 2>&1
adb shell rm -r /system/etc/launch_daemonsu.sh >NUL 2>&1 
adb shell rm -r /system/xbin/su >NUL 2>&1 
adb shell rm -r /system/bin/su >NUL 2>&1 
adb push supersu/xbin /system/
adb push supersu/init.sec.boot.sh /etc/
adb push supersu/launch_daemonsu.sh /etc/
adb install -r SuperSU.apk
adb install -r flashfire.apk
adb shell chmod 0755 /system/xbin/su
adb shell chcon u:object_r:system_file:s0 /system/xbin/su
adb shell chmod 0700 /system/etc/launch_daemonsu.sh
adb shell chcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh
echo
echo NOTE: If you get the error message below during install, please reboot and try again
echo NOTE: adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Text file busy
I think the "adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Text file busy " message left me thinking an error occurred, when it's really only an advisory message. I tweaked the script slightly (see above) to, I hope, avoid the confusion. Maybe killing any adb daemon and this change will help?
 

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
Sigh... I did all of the above without a SIM in place (what difference can it possibly make, right?) Installing the SIM forced some sort of error relating to dm-verity which denied me access to the phone. I've flashed back to stock and am going back through rooting, with the SIM present.

Speaking of updates, someone (Samsung?? Google?? - it showed up even without the SIM) keeps trying to push what looks like an OTA at the phone. I assume that update will prevent rooting. I can live without the OTA. What I don't know how to do is a) delete the downloaded OTA, and b) keep it from being pushed at me again. If it's still in the phone, sooner or later it's going to install itself whether I want it or not. And being rooted, the dm-verity error will come back and, effectively, I'll be locked out of the phone yet again. >:-<
 
Last edited:

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
Sigh... no luck. Root.BAT can't write to /system/xbin/ or to /etc/ - the errors end with "read-only file system".

FWIW, I added adb kill-server at the top of the script - Root.BAT starts with a fresh instance of adb.
 

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
Yep. But I'll walk through the process from 1 to 5 all over. Again.
This is the wheels falling off...
Code:
Device reconnect ...

-------------------------------------
-  1 Install FingerPrint Fix         -
-  2 Do Not Install FingerPrint Fix  -
-------------------------------------
Please make your decision: 2

--------------------------------------------------
-  1 Install Root No Tweaks                       -
-  2 Install Root With CPU Governor Conservative  -
-  3 Install Root With CPU Governor Ondemand      -
-  4 Install Root With CPU Governor Interactive   -
-  5 Exit                                         -
--------------------------------------------------
Please make your decision: 1

-------------------------------------
-  1 Install SuperSU Root          -
-  2 Install Magisk Root           -
-  3 Install Systemless Root       -
-------------------------------------
Please make your decision: 1
Installing Root
adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Read-only file system
adb: error: failed to copy 'supersu/init.sec.boot.sh' to '/etc/init.sec.boot.sh': couldn't create file: Read-only file system
adb: error: failed to copy 'supersu/launch_daemonsu.sh' to '/etc/launch_daemonsu.sh': couldn't create file: Read-only file system
Success
Success
chmod: /system/xbin/su: No such file or directory
chcon: /system/xbin/su: No such file or directory
chmod: /system/etc/launch_daemonsu.sh: No such file or directory
chcon: /system/etc/launch_daemonsu.sh: No such file or directory
If you get this error in above script
adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Text file busy
during install please reboot and try again
Press any key to continue . . .
I don't understand who's reporting "Success".
 

billa

Senior Member
Mar 30, 2006
731
356
Are you saying I should kill the adb daemon before starting a root attempt, or are you recommending restarting during the pause after the first reboot? If so, I'm not sure how I can break through the running script to kill the daemon. If I can get that far, of course I can restart it, too.

If you get this error in above script
adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Text file busy
during install please reboot and try again
Press any key to continue . . .[/code]I don't understand who's reporting "Success".

ADB should only be stopped (2-3 times back to back) at the beginning of running the Root.bat, no need to stop it during the process.
The idea here is to start with a clean machine with no adb deamon running at all.
As far as the script, nobody had to modify it, it works just fine as is.

I can only suggest to reflash it again with stock UES4BRA1, do a full factory reset from the recovery menu then proceed to step 2.
Not judging your abilities, but it seems that some small detail is somehow being missed during the steps.
Pay close attention to where it says enable adb/oem etc, it's very important to do it multiple times EXACTLY as instructed.
Try again, because nobody else had this issues, so the question is more like "Don't understand, what am I missing here?" ;)

Looking at your log...
Installing Root
adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Read-only file system
adb: error: failed to copy 'supersu/init.sec.boot.sh' to '/etc/init.sec.boot.sh': couldn't create file: Read-only file system
adb: error: failed to copy 'supersu/launch_daemonsu.sh' to '/etc/launch_daemonsu.sh': couldn't create file: Read-only file system

It clearly shows that your system is "Read-only file system" which could indicate that the eng-boot didn't flash properly.
Again, my only suggestion is go back to step 1 and follow through 5, but don't do any workarounds, do it exactly as written to a "T".
 
Last edited:
  • Like
Reactions: RBEmerson

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
the adb offline problem (although there are several google hits on the problem) turned out to be nothing more than making sure the S7 screen was unlocked (not enough to just be booted to "Swipe screen to unlock" - gotta do the swipe and PIN). That goes into the bit bucket.

Something odd happens when I flash XAA-G930UUEU4BQD2-20170428165520.zip. The boot splash screen still has the padlock icon. When flashing back to stock (step 2.), I use CSC_OYM_G930UOYM4BQD2_CL10860000_QB13198947_REV02_user_low_ship_MULTI_CERT.tar.md5 not HOME_CSC_yada yada Also, if there's a PIT file around (see step 2. in the how-to), I don't see it. It's not in the .zip - just the bl, ap, cp, and two csc files.

Step 3. the "block out boot loops" step, runs with the expected mix of success and fails. A puzzle shows up here. After step 2., there's the padlock in the boot splash. After step 3., it's gone. Why is that? Do I care?

Step 4., the ENG flash. I'm using the patched odin, which hasn't shown any problems. I'm guessing that Samsung_G930_QC_Eng_Boot_Root_v2017-03-01.TAR goes into odin's AP spot. Unlike step 2., where odin does an md5 checksum check for bl, ap, cp, csc, it doesn't do anything with the ENG tar. Just for curiousity's sake, I tried putting it in BL. Clicking BL showed me the same file. (I did not hit start) Questions: does Samsung_G930_QC_Eng_Boot_Root_v2017-03-01.TAR go to the AP slot? Should odin do any checking on this file? If the "read-only" error points to the ENG file not being properly flashed, what did I not do, or do incorrectly?
 

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
I deleted the work space (folders and files) I was using, made sure I had current files, replaced the old workspace with folders Step2, Step3, Step4, Step5. The zip(s) appropriate to the step go in the folder. I Tweaked Root.BAT to start with adb kill-server to avoid problems with a running adb daemon, and to save the time needed to open a command window and type cd /d... and adb... Yes, there is a running adb server when Root.BAT starts running.

This is the ENG file name: Samsung_G930_QC_Eng_Boot_Root_v2017-03-01.TAR - where does it belong in odin (BL, AP, CP, or CSC)?

I stepped through the folders and still get "read-only" at the end of step 5. Remember I was able to root this phone earlier but had to re-do it after adding the SIM.

I'm out of ideas.
 

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
I tried 2-5 again this morning (might as well do it when I'm awake and not doing an all-nighter). I was obsessive about letting the kernel settle (over 45 min. wait). All files came from the links in the how-to. I put each step's files in their own folders. Each folder got an unzipped patched odin and adb. I did an adb kill-server before each batch file ran. I verified the developer USB settings were right. I verified that the RSA stuff for the PC was set to "always allow" - ditto for MTP. I used a different USB port and a different USB cable.

Aside from step 5, the bat file step outputs look OK. The two uses of odin produce PASS.

Fail. "Read-only file system".

In step 4, where should the ENG file be opened in odin? Is there an .md5 version to get a checksum test?
 
Last edited:

freeop

Senior Member
Aug 30, 2011
381
160
US
I tried 2-5 again this morning (might as well do it when I'm awake and not doing an all-nighter). I was obsessive about letting the kernel settle (over 45 min. wait). All files came from the links in the how-to. I put each step's files in their own folders. Each folder got an unzipped patched odin and adb. I did an adb kill-server before each batch file ran. I verified the developer USB settings were right. I verified that the RSA stuff for the PC was set to "always allow" - ditto for MTP. I used a different USB port and a different USB cable.

Aside from step 5, the bat file step outputs look OK. The two uses of odin produce PASS.

Fail. "Read-only file system".

In step 4, where should the ENG file be opened in odin? Is there an .md5 version to get a checksum test?
Place the ENG file in the AP section of Odin.

Sent from my SAMSUNG-SM-G935A using Tapatalk
 
Last edited:
  • Like
Reactions: RBEmerson

billa

Senior Member
Mar 30, 2006
731
356
I tried 2-5 again this morning (might as well do it when I'm awake and not doing an all-nighter). I was obsessive about letting the kernel settle (over 45 min. wait). All files came from the links in the how-to. I put each step's files in their own folders. Each folder got an unzipped patched odin and adb. I did an adb kill-server before each batch file ran. I verified the developer USB settings were right. I verified that the RSA stuff for the PC was set to "always allow" - ditto for MTP. I used a different USB port and a different USB cable.

Aside from step 5, the bat file step outputs look OK. The two uses of odin produce PASS.

Fail. "Read-only file system".

In step 4, where should the ENG file be opened in odin? Is there an .md5 version to get a checksum test?


No idea what's going wrong with your process, nobody else has reported any issues... what I did notice is that you're not using the BRA1 firmware as in the instructions, not sure if that has anything to with it. Try again with the BRA1 firmware and see what happens. The eng-boot had to be in the AP tab, and there are no md5 checksums in any of the files.
 
  • Like
Reactions: RBEmerson

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
Place the ENG file in the AP section of Odin.
[/snip]
Gotit - that's what I thought. TNX

---------- Post added at 07:58 PM ---------- Previous post was at 07:27 PM ----------

No idea what's going wrong with your process, nobody else has reported any issues... what I did notice is that you're not using the BRA1 firmware as in the instructions, not sure if that has anything to with it. Try again with the BRA1 firmware and see what happens. The eng-boot had to be in the AP tab, and there are no md5 checksums in any of the files.
I'm confused - isn't step 2 where a stock UES4BRA1 is flashed? I haven't done an FDR from recovery. I'll do it with this iteration of trying to root.
Pay close attention to where it says enable adb/oem etc, it's very important to do it multiple times EXACTLY as instructed.
You're talking about the settings in Developer options, right? I check them before every time I use a .bat file. In any case, I'll recheck during this iteration.
Trust me, "Don't understand, what am I missing here?" is running around and around in my head, and has gone around often enough to leave groove there. LOL
Step 2 - I'm using ...\Foo (instead of ...\Step2) only to be 100% sure I'm using BRA1:
i-x2BhbRJ-L.png

Step 3:
i-hRR9PbG-XL.png

Step 4:
i-8dkPmt8-XL.png

Step 5:
i-xSk6KCn-XL.png
 

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
Step 2 - flashing from the files shown earlier and doing an FDR didn't change anything. Step 3 looked reasonable - a lot of lines get "not installed", a few get success. Step 4, using ENG from AP passed. Once again, step 5 failed.
Code:
Waiting for the phone to be connected ...

adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
Device connected ...

Removing FlashFire ...

Removing SuperSU ...


Removing Fingerprints ...

Resetting Lockscreen Security ...

rm: /system/priv-app/Chameleon2: No such file or directory

Removing Any SuperSu Images ...


Removing Knox Stuff...


Preparing For Root ...

Phone will reboot and continue do not unplug...

Waiting for the phone to reconnect ...

After device is reconnected and recognized by the computer
Press any key to continue . . .

Device reconnect ...




-------------------------------------
-  1 Install FingerPrint Fix         -
-  2 Do Not Install FingerPrint Fix  -
-------------------------------------
Please make your decision: 2


--------------------------------------------------
-  1 Install Root No Tweaks                       -
-  2 Install Root With CPU Governor Conservative  -
-  3 Install Root With CPU Governor Ondemand      -
-  4 Install Root With CPU Governor Interactive   -
-  5 Exit                                         -
--------------------------------------------------
Please make your decision: 1


-------------------------------------
-  1 Install SuperSU Root          -
-  2 Install Magisk Root           -
-  3 Install Systemless Root       -
-------------------------------------
Please make your decision: 1
Installing Root
adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Read-only file system
adb: error: failed to copy 'supersu/init.sec.boot.sh' to '/etc/init.sec.boot.sh': couldn't create file: Read-only file system
adb: error: failed to copy 'supersu/launch_daemonsu.sh' to '/etc/launch_daemonsu.sh': couldn't create file: Read-only file system
Success
Success
chmod: /system/xbin/su: No such file or directory
chcon: /system/xbin/su: No such file or directory
chmod: /system/etc/launch_daemonsu.sh: No such file or directory
chcon: /system/etc/launch_daemonsu.sh: No such file or directory
If you get this error in above script
adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Text file busy
during install please reboot and try again
Press any key to continue . . .

After flashing the stock system, there's a brief blue screen with a spinning arrow in the middle of the Andy figure (no more 3D Andy - bummer) and something about a system update. I've seen this before (with 3D Andy and a blue ball spinning away), while flashing other phones. Is this update event a problem? Since I'm using the stock BRA1 files, I assume this event is normal. Or is it?
 

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
Decided to bring my S7 back to stock. I flashed BRA1 (step 2 files) and then opened up recovery. At the bottom of the screen, I found this...
Code:
No Support SINGLE-SKU
Supported API: 3

# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC
What is VZW doing here??? The phone is unbranded and unlocked. Is this mess being caused by the VZW SIM???
(BTW the screen really does show "Appling", not "Applying")
 

billa

Senior Member
Mar 30, 2006
731
356
Decided to bring my S7 back to stock. I flashed BRA1 (step 2 files) and then opened up recovery. At the bottom of the screen, I found this...
Code:
No Support SINGLE-SKU
Supported API: 3

# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC
What is VZW doing here??? The phone is unbranded and unlocked. Is this mess being caused by the VZW SIM???
(BTW the screen really does show "Appling", not "Applying")

It's normal to see the carrier's name of last sim card your have or had inserted, which brings up another suggestion, do not insert a sim during the flashing and rooting process to avoid any interference (not a critical issue but do it anyway). You can insert it after it's all done and verified, at which point it's normal for the "unbranded" firmware to boot into a blue screen for auto-configuration.
Look, this is my last message about your issue, all I can suggest is to ALWAYS start the rooting process with a clean stock flash, AND a full factory reset form recovery, then proceed to the rest of the steps. Keep trying, and you will succeed ;)
Last, but not least even though you see xbin read-only error, yet your phone is rooted, well then just leave it at that I guess.


How do I navigate to supersu file using cmd because I have no idea how use it?

Not sure what you're trying to do by navigating to the supersu file, can you describe your aim please?
 
Last edited:
  • Like
Reactions: RBEmerson

RBEmerson

Senior Member
Jul 15, 2012
594
59
SE PA
It's normal to see the carrier's name of last sim card your have or had inserted, which brings up another suggestion, do not insert a sim during the flashing and rooting process to avoid any interference (not a critical issue but do it anyway). You can insert it after it's all done and verified, at which point it's normal for the "unbranded" firmware to boot into a blue screen for auto-configuration.
Look, this is my last message about your issue, all I can suggest is to ALWAYS start the rooting process with a clean stock flash, AND a full factory reset form recovery, then proceed to the rest of the steps. Keep trying, and you will succeed ;)
For this iteration, I downloaded everything all over - except BRA1. Updato has me throttled back to about a day to d/l. The version I used is 1 day old and came from updato.

I pulled the SIM/SD carrier altogether - nothing in the phone. BRA1 flashed as usual. I did an FDR. I let the full setup process run to the end. In Developer I enabled OEM, USB, and cleared the RSA keys.

I used File Explorer to browse Phone to be sure MTP was working. I ran the fresh security+OTA script. It failed because this was the point where "allow this computer access this device" finally showed up. After the script end, I approved the request and checked the "no need to ask again" box. I ran the script a second time and it ran as usual: lots of files not found, a few found.

I flashed Samsung_G930_QC_Eng_Boot_Root_v2017-03-01. odin reported PASS. After rebooting, I left phone alone for 45 minutes.

I verified the OEM and USB options in Developer and ran Root.BAT from Samsung_G93x_QC_CF-SU_v2.82_2018-02-01_SSU+MGK. I chose no fingerprint fix, root w/ no tweaks, and SuperSu Root. The same read-only messages came back.
I checked OEM and USB options in Developer and ran Root.BAT from Samsung_G93x_QC_CF-SU_v2.82_2018-02-01_SSU+MGK. I chose no fingerprint fix, root w/ no tweaks, and SuperSu Root. The same read-only messages came back.

SuperSu 2.82-SR5 Root S7 was installed. It reports permission denied to access /sbin/su. FlashFire is present but, of course, reports it can't run - not rooted.
I used a terminal to look around, in some of the directories involved. There is not hint of what should be there, installed by the step 5 script.

All of the above brings me to thinking ENG didn't flash as it should. Even though odin says it did (PASS). Something's gone wrong here but I don't know what.

Last, but not least even though you see xbin read-only error, yet your phone is rooted, well then just leave it at that I guess.
RootChecker says the phone's not rooted and it lists all the possible directories where SuperSu should be. SuperSu isn't in any of them. supersu/init.sec.boot.sh and supersu/launch_daemonsu.sh aren't in /etc/. There is no supersu in /etc. Trying to use SuperSu doesn't work. FlashFire doesn't work (no SuperSu to grant permission). I can't invoke su from Material Terminal (no SuperSu to grant permission). If the phone's rooted, nothing I've tried confirms it.

I'm not a total idiot about phones and Linux. I've been using Linux, one way or another, from prior to the 1.0 kernel, when Linus was very hands on. What I don't have is understanding the hacks, tweaks, and general magic to get around roadblocks in Android.
 
Last edited:

kimber45

Senior Member
Apr 9, 2011
84
28
Mizzery
For this iteration, I downloaded everything all over - except BRA1. Updato has me throttled back to about a day to d/l. The version I used is 1 day old and came from updato.

I pulled the SIM/SD carrier altogether - nothing in the phone. BRA1 flashed as usual. I did an FDR. I let the full setup process run to the end. In Developer I enabled OEM, USB, and cleared the RSA keys.

I used File Explorer to browse Phone to be sure MTP was working. I ran the fresh security+OTA script. It failed because this was the point where "allow this computer access this device" finally showed up. After the script end, I approved the request and checked the "no need to ask again" box. I ran the script a second time and it ran as usual: lots of files not found, a few found.

I flashed Samsung_G930_QC_Eng_Boot_Root_v2017-03-01. odin reported PASS. After rebooting, I left phone alone for 45 minutes.

I verified the OEM and USB options in Developer and ran Root.BAT from Samsung_G93x_QC_CF-SU_v2.82_2018-02-01_SSU+MGK. I chose no fingerprint fix, root w/ no tweaks, and SuperSu Root. The same read-only messages came back.
I checked OEM and USB options in Developer and ran Root.BAT from Samsung_G93x_QC_CF-SU_v2.82_2018-02-01_SSU+MGK. I chose no fingerprint fix, root w/ no tweaks, and SuperSu Root. The same read-only messages came back.

SuperSu 2.82-SR5 Root S7 was installed. It reports permission denied to access /sbin/su. FlashFire is present but, of course, reports it can't run - not rooted.
I used a terminal to look around, in some of the directories involved. There is not hint of what should be there, installed by the step 5 script.

All of the above brings me to thinking ENG didn't flash as it should. Even though odin says it did (PASS). Something's gone wrong here but I don't know what.

RootChecker says the phone's not rooted and it lists all the possible directories where SuperSu should be. SuperSu isn't in any of them. supersu/init.sec.boot.sh and supersu/launch_daemonsu.sh aren't in /etc/. There is no supersu in /etc. Trying to use SuperSu doesn't work. FlashFire doesn't work (no SuperSu to grant permission). I can't invoke su from Material Terminal (no SuperSu to grant permission). If the phone's rooted, nothing I've tried confirms it.

I'm not a total idiot about phones and Linux. I've been using Linux, one way or another, from prior to the 1.0 kernel, when Linus was very hands on. What I don't have is understanding the hacks, tweaks, and general magic to get around roadblocks in Android.
Just looking back through your posts(in case i decide to re-root and have issues) and noticed you said you used odin to flash the eng kernel, but did you use the prince comesy(sp) version? Just a thought I had, maybe a dumb one.

Sent from my SM-G935R4 using Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 239
    Root Android 7.0 Nougat on Galaxy S7 & S7 Edge devices. YES! Supports all USA Qualcomm variants. T-mobile, AT&T, Verizon and *Sprint (*Note: Some people have reported problems with the Sprint device after root, while others have had success. As always, read the thread for detail and use at your own risk)
    ** THIS IS NOT FOR THE EXYNOS VERSION OF THE S7! **

    A few answers to common questions:
    YES - this breaks Samsung Pay and probably Android Pay (you will NOT be able to use Samsung Pay after root)
    YES - this process is reversible by several methods, one of which would be simply doing a factory reset and re-flashing the complete Nougat Android 7.0 Firmware files in Odin, More details on this below.
    NO - this process does NOT trip the KNOX counter
    NO - there is no TWRP or custom recovery for this method of rooting
    NO - there is no XPOSED framwork for Android 7.0 currently (as of today's date)
    YES - There is a Android 7.0 custom rom! Thanks to @jrkruse https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739



    Many thanks to the people who released the files! I am only posting the file's in a single easy to find post along with my experience and instructions which may or may not work for you! these instructions may or may not be right. these instruction may or may not be missing crucial steps. USE AND PROCEED AT YOUR OWN RISK! No one is responsible if you damage your device. CERTAINLY NOT ME!

    PLEASE GIVE THANKS WHERE ITS DESERVED! Thank you :good:

    MANY THANKS TO
    @
    JUSMEJOSE https://forum.xda-developers.com/member.php?u=1113488
    @
    princecomsy https://forum.xda-developers.com/member.php?u=5028474
    @jrkruse https://forum.xda-developers.com/member.php?u=1949695
    @jrkruse for his awesome job for making a custom flashable Android 7.0 Nougat ROM https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
    @Chainfire for creating SuperSU and other great android utilities.
    I'm sure there are many others, but I don't know who all created what, so I'm only listing those who I know - if I messed this up, I'm sorry in advance.

    ENG (AP) files for S7 and S7E (from this post https://forum.xda-developers.com/showpost.php?p=71271898&postcount=28 )
    https://www.androidfilehost.com/?fid=457095661767141717
    (This is the ENGINEER boot kernel boot.tar file you'll be flashing in the special modified Odin software from your PC)

    *edit: newer method available!*
    SuperSU 2.79 root.bat file (from this post https://forum.xda-developers.com/showpost.php?p=71281527&postcount=50 )
    https://www.androidfilehost.com/?fid=817550096634750763
    (This is the command prompt script you'll execute from a CMD prompt from a windows PC that installs the needed files for root access like SuperSU)

    **EDIT: @jrkruse on 5/29/17 has created a new ROOT.BAT including SuperSU v2.82, it has been outlined in this post #480 of his custom rom thread. As always, please take a moment to hit the thanks button! Without the work of these amazing dev's we would NOT have root PERIOD! It is free for you, and mean's a lot to everyone involved in bringing these releases to you the public!!!

    Here is latest root zip with SuperSU 2.82 (5/29/2017)
    Nougat_S7_Root_2_82_All_Carriers_V1.zip


    jrkruse said:
    This root method will reset your fingerprints and lockscreen security it will also fix fingerprint issue this should help with issues of not recognizing your fingerprint after you root. I had to modify the latest SuperSu to get root to stick on SuperSU 2.82.
    Here is a what I did:
    The new supolicy from 2.82 Version was causing root not to stick. So I used the supolicy from 2.81 Version. I modded the SuperSu.apk to ingnore the supolicy not being 2.82 Version So you wont get asked to update the SuperSU binaries.
    The SU binary is updated to 2.82 and all other files.
    If you delete SuperSU apk dont reinstall it from playstore use the one in Above zip

    **Alternative** Many thanks to active contributor of this thread @Quickvic30 for the info in post #688
    https://forum.xda-developers.com/showpost.php?p=71700562&postcount=688
    Who offer's another root.bat alternative which gave him better performance. Please check out that post for the file, and click the thanks button.
    PLEASE REMEMBER: Results for rooting vary on each and every device. Lag, Performance, Heat - These things vary from device to device. YOUR MILEAGE WILL VARY!
    ** You will use either the originally posted SuperSU 2.79 root.bat, or the ALTERNATE version posted by Quickvic30 - DO NOT USE BOTH - CHOOSE ONE METHOD OR THE OTHER ** OR TRY EACH INDIVIDUALLY AND SEE WHICH GIVES YOU ACCEPTABLE RESULTS **

    VoLTE VMM - IMservice hurricane icon fix thanks to jrkruse post #453
    https://www.androidfilehost.com/?fid=457095661767144116
    jrkruse said:
    Sorry about all the VOLTE Icon problems
    If your having FC issues your going to have to copy the original imsservice folder with imsservice.apk and oat folder to system/priv-app before you can flash this fix

    This new zip should fix fc problems as no apk is replaced no more just the icons are replaced inside the apk

    Volte Icon Fix Is now one zip for all S7 Variants. No more flashing wrong zip and getting FC. The zip only replaces Icons in imsservice apk. This zip will work on odex or deodex roms
    S7_VOLTE_ICON_FIX_ALL_VARIANTS.zip

    YOU MUST MOUNT SYSTEM IN FLASHFIRE WHEN FLASHING!!!

    ALTERNATIVE SOLUTION from Post #413: Thanks to @sabresfan post #413

    You will need to download and use only the PrinceComsy modified Odin which I got from https://www.androidfilehost.com/?fid=24591023225177749

    Kernel Adiutor can be downloaded from Play Store
    https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor

    Original stock firmware files can be found on these sites or searching XDA
    https://www.sammobile.com/firmwares/
    http://updato.com/
    ** Edit: More information about returning to STOCK below on this first post **

    **EDIT: Samsung USB driver's direct from Samsung web site http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe

    I'm not sure if you need the ADB files installed system wide or not? But you can also download and install the 15 minute ADB drivers. (use google or search XDA)

    AGAIN: I did this to my Samsung Galaxy S7 Edge on T-mobile G935T RUNNING ANDROID 7.0 NOUGAT I believe this will work with other USA released carrier variants using Qualcomm chipset (T-mobile, AT&T, Verizon and Sprint)... BUT YOU DO THIS AT YOUR OWN RISK.

    EDIT: MAKE SURE YOU ARE ON ANDROID 7.0 NOUGAT - OBVIOUSLY. (Baseband Version: G935TUVU4BQB1 in the case of a G935T S7 Edge) :fingers-crossed:
    This process did NOT cause any data or application loss for me. I did this procedure from an OTA upgrade to N from MM.

    Obviously, Download all needed files in advance and unzip accordingly.
    Put your phone in download mode (Volume Down, Home and Power) then click home again to continue to download mode
    Launch the modified ODIN on your PC
    Unzip ENG BOOT file and get the boot.tar for your device (in my case it was the S7edge_qualcomm.tar was the file I needed for the S7 Edge) DO NOT UNZIP THE TAR FILE.
    Put that .tar file in AP section of ODIN
    Connect your phone, you should see a lighted COM port selected in ODIN meaning your good to go.
    CLICK START in Odin. You Phone will flash the file quickly and restart.
    Let it boot up fully and wait until you can unlock the phone (go to desktop of the phone)
    Now open a CMD prompt on the computer and navigate to where you downloaded and unzipped the SuperSU 2.79 earlier
    in the CMD prompt type root.bat this will push the required files to the phone and it will be rooted when its completed.
    After a few minutes your phone will restart, and you will have SuperSU and root access on Android 7.0 Nougat.

    This is how I rooted my SM-G935T Samsung Galaxy S7 Edge on Android 7.0 Nougat. Yes this is a bootloader locked T-mobile branded device.

    Please feel free to add or correct anything here in the posts below!

    EDIT: You'll want to install Kernel Auditor from the Play store, grant it supersu permission, and set both cpu govenors to ONDEMAND and set apply on boot. (core 1&2 default to performance and core 3&4 default to interactive - set both to ondemand and apply on boot)
    EDIT2: You may want to experiment with the CPU governors in Kernel Adiutor (that's actually the correct spelling according to the author). It's been suggested CONSERVATIVE will give you better battery life than ONDEMAND. So you'll want to try the available options and see which results in acceptable balance of performance and battery life for you.

    GOOD LUCK! AND THANK YOU!
    I HOPE THIS HELPS PEOPLE GET ROOT ON THEIR USA QUALCOMM DEVICES
    PLEASE TAKE A MOMENT TO THANK THE PEOPLE WHO BROUGHT THIS INFORMATION TO YOU.

    Returning to STOCK Android 7.0 Nougat

    You will need to have Odin installed (same modified Odin linked above should work fine)
    You can download stock Android 7.0 Nougat firmware from
    https://www.sammobile.com/firmwares/
    http://updato.com/

    For the T-mobile S7 Edge G935T ONLY
    File: SM-G935T_G935TUVU4BQB1.zip
    Google Drive Link: https://drive.google.com/file/d/0B9QvmNs9dpD-LTdwQUgzejk5ZGM/view
    From thread (thanks to it's OP): https://forum.xda-developers.com/tmobile-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3558242

    Thanks to @Krog18 for linking to Verizon firmware files in post https://forum.xda-developers.com/showpost.php?p=71383942&postcount=359
    G930V QA2 Stock fw: https://www.androidfilehost.com/?fid=529152257862709174
    G935V QA2 Stock fw: https://www.androidfilehost.com/?fid=817550096634752305

    Thanks to @Quickvic30 for linking to the AT&T firmware files in post https://forum.xda-developers.com/showpost.php?p=71601821&postcount=608
    G935A QA6 https://www.androidfilehost.com/?fid=745425885120713605

    When you extract the .zip file for your device, you have 2 options for the CSC section. One file will erase all existing data and apps, reverting your phone to a like new state. The other will preserve your currently installed apps and data.

    CSC_TMB_G935TTMB4BQB1_CL10376601_QB12449118_REV02_user_low_ship_MULTI_CERT.tar USING THIS FILE WILL ERASE ALL EXISTING DATA ON THE DEVICE
    HOME_CSC_TMB_G935TTMB4BQB1_CL10376601_QB12449118_REV02_user_low_ship_MULTI_CERT.tar USING THIS FILE WILL PRESERVE (*NOT ERASE) ANY EXISTING DATA FROM THE DEVICE

    Obviously you can only choose 1 of the CSC files. Using the HOME_CSC keeps your existing data, and the other CSC formats your phone.

    Thanks to @billa (https://forum.xda-developers.com/member.php?u=293193) for taking taking the time to put these tips together for everyone.
    Slightly edited by me ;)
    billa said:
    Note (and suggestions)
    ----
    Before and after rooting wipe the cache.
    For tweak settings to stick, must reboot multiple times.


    Security Updates OFF
    --------------------
    Settings > Lock Screen > Security > Other Security > Security Policy Updates > OFF and Wi-Fi only


    Disable (things to disable after root - Use Titanium Backup or Package Disabler Pro for Samsung, both available from the Play Store - Worth the price to buy!)
    -------
    Samsung DM Phone Interface
    Samsung DM Service
    SecurityLogAgent
    com.sec.android.soagent
    com.wssyncmldm
    tethering.automation
    tethering.provisions


    After Eng-Boot (root is complete)
    --------------
    Install Kernel Auditor, and set both CPU govenors to "OnDemand" and set apply on boot.
    Set cores 1&2/3&4 to "OnDemand" and apply on boot.
    EDIT: Experiment with governor settings until a balance of power and performance is reached. Kernel Adiutor is available from the Play Store


    Performance tweaks
    ------------------
    GovTuner - set to interactive and performance
    Kernel Auditor
    Kernel Toolkit
    LSpeeds
    SSD Boost


    SHealth fix
    -----------
    Set ro.config.tima to 0 in build.prop


    WiFi passwords fix
    ------------------
    Set ro.securestorage.support to false in build.prop


    VOLTE/RCS icons OFF
    -------------------
    Copy the imsservice.apk from the root zip to
    /system/priv-app/imsservice/
    and set permissions to -rw-r--r--


    Data toggle
    -----------
    Use SQLite editor and add MobileData to a string in settings.db



    Busybox fix
    -----------
    Install busybox to /system/xbin instead of /su/xbin


    Sprint LTE fix
    --------------
    In Build.Prop change the following:
    ro.cdma.default_numeric=310000 to 310120
    ro.cdma.default_alpha=Chameleon to Sprint
    ro.build.characteristics=Chameleon to Sprint

    OR

    Go into settings
    Click Connections
    Click Wi-Fi Calling
    Click Cellular Network Preferred
    Go back two times and click on Mobile networks
    Select Network mode and select 3G/2G (auto connect)
    Restart your phone and call 611 just to make sure the call goes through
    Hangup and go back to Network mode and switch back to LTE mode

    As always THANKS to all the users who continue to contribute to this thread, and to all the people involved in bringing you this information so you can ROOT your Samsung Galaxy S7 or Samsung Galaxy S7 Edge on Android 7.0 Nougat!

    I will continue to update this first page with relevant links, details and information in an attempt to keep the information easier to find for everyone.

    Take a moment to press the THANKS button!
    50
    So I've been running awesome here and I need you guys to try this root.bat file for me. This is the one I use and I DONT use any kernel editor apps or make any adjustments what so ever.

    Do NOT have any kernel editors or Lspeed installed when installing this please. Make sure you have the eng kernel installed. On your PC just unzip the file and double click the root.bat file to install.

    After phone reboots instantly power off phone and reboot to recovery and wipe cache partition then reboot.

    After power up let phone sit for 5-10 mins DON'T TOUCH IT, I KNOW ITS HARD BUT JUST DON'T DO IT!!!

    Reboot one last time

    Once it boots up open to home screen and just let it settle for a minute. DO NOT go into super su app, just leave it be!!! Open a app you know needs root permission and make sure the root prompt pops up. Let me know how the phone runs.

    Thanks
    9
    Sorry about all the VOLTE Icon problems
    If your having FC issues your going to have to copy the original imsservice folder with imsservice.apk and oat folder to system/priv-app before you can flash this fix

    This new zip should fix fc problems as no apk is replaced no more just the icons are replaced inside the apk

    Volte Icon Fix Is now one zip for all S7 Variants. No more flashing wrong zip and getting FC. The zip only replaces Icons in imsservice apk. This zip will work on odex or deodex roms
    S7_VOLTE_ICON_FIX_ALL_VARIANTS.zip

    YOU MUST MOUNT SYSTEM IN FLASHFIRE WHEN FLASHING!!!
    9
    I have a fix for the fingerprint scanner not working. Download the attached zip and replace the respective libs in /system and reboot. Make sure permissions are -rw-r-r-- (644)
    8
    I guess I never really thought about that or looked into it but seems feasible. The eng.img does have some numbers for the description but not really like our firmware and BL identification sequence. I bet nougat for the regular S7 edge would flash on that active, you would be minus the active key. But it is kinda risky business if your only on BL 2.

    I'm pretty sure the original poster of the eng.img has the eng.img for the active, he said he has all the firmware for them anyways. Maybe try PMing him about it.

    Sent from my SM-G935T Running R.A.W root.bat! Buttery smooth, fast, no heat issues and great battery life!!!

    Wonder why it wasn't posted, when post for other devices. Besides I pm who I thought was original poster, but haven't heard anything as of yet. Been 24 hours so far. He might be busy.

    The engineering kernels and files are not meant to be released to the public, certain people have access to them for testing, coding, repair, etc... read between the lines. That's one of the reasons rooting using this method has such varied success... there is no 1 "cure-all" solution. Those files aren't really meant to be run for the life of the device by "users" on a daily driver phone. The files that are getting released, are more a less being leaked... not "released". So while "I agree" I hope they do surface sooner rather than later, I completely understand his/their hesitation in releasing them... Just read thru this thread.... some people have had great success, others have had complete failure... Most people don't even want to read thru the OP for details, let alone the thread to gather information.... they just post a question that's been answered before - sometimes right above their post. :( or people complain the instructions aren't labelled clearly enough, or links to files aren't easy to find, or using this method cause batteries and screens to burn out... One poster even said his rooted phone worked fine in the house with the AC but failed miserably outside in 80f heat... :crying:

    We all try to assist, we all try to help, we all try to contribute.... but at the end of the day - each user HAS TO PUT IN SOME EFFORT. And everybody HAS to realize, rooting (by any method imho) is always done at the users own risk. There is no guarantee given or implied. Results are obviously going to vary - and for guys who don't understand what they're doing - the results are ALWAYS going to be questionable. ** I AM NOT COMPLAINING ON ANYONE ** I'm just saying having root on this device period has been a stroke of luck with a touch of genuine genius thrown in for good measure (NOT BY ME - BY THE GUYS DOING THE HEAVY LIFTING - THEY KNOW WHO THEY ARE)

    I truly hope everyone is able to obtain an acceptable level of performance and usability while gaining root access. That's the goal for everyone in this thread.