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

billa

Senior Member
Mar 30, 2006
716
351
83
Complete rooting guide for the Samsung S7 (G930x) / S7Edge (G935x) QC

Follow this rooting guide carefully, do not skip any steps!!
And the usual disclaimer: Proceed at your own risk!!
Warning: All your data will be erased, so back up anything important!!
This guide contains the latest version files as of today.

1.
First, turn on ADB-Debug and OEM-Unlock in the Developer Options menu in order to avoid being locked out later on (search for it if you need help).

2.
Next, it's best to start by flashing a full stock, bloat-free, unbranded firmware "U".
Use the patched Odin at the end of this post to flash AP, BL, CP, CSC (select the non-Home file), and the PIT file in the PIT tab.
Due to implementation of the new RMM security, I would not recommend flashing anything newer than Jan. 2018 as outlined here.
https://forum.xda-developers.com/showpost.php?p=75402467&postcount=2483
Full stock unbranded "U" firmwares
Samsung_G930U_UES4BRA1_v7.0.0.ZIP
https://updato.com/firmware-archive-select-model?record=C3BB0B480B0F11E89F15FA163EE8F90B
Samsung_G935U_UES4BRA1_v7.0.0.ZIP
https://updato.com/firmware-archive-select-model?record=61E5E57D020011E8ACA1FA163EE8F90B

3.
Next, in order to avoid the annoying boot-loop issue, run this script before flashing the eng-boot to disable Samsung's Security+OTA.
Some commands may show an error, which is fine since this is a generic script for many different models.
Turn on ADB-Debug and OEM-Unlock in the Developer Options menu in order to avoid being locked out later on (search for it if you need help).
Unzip it and run the _Samsung_Security+OTA_Disabler_(BillA_v2018-01-01).BAT file which should be at top of the folder.
https://www.androidfilehost.com/?fid=818070582850489746

4.
Next, use the patched Odin at the end of this post to flash your phone's matching eng-boot file.
Samsung_G930_QC_Eng_Boot_Root_v2017-03-01.TAR
https://www.androidfilehost.com/?fid=457095661767142259
Samsung_G935_QC_Eng_Boot_Root_v2017-08-29.TAR
https://www.androidfilehost.com/?fid=817906626617954238

5.
At this point leave the phone untouched for about half an hour to stabilize the kernel, don't touch it and just wait patiently.
Turn on ADB-Debug and OEM-Unlock in the Developer Options menu in order to avoid being locked out later on (search for it if you need help).
Finally, to complete the rooting process, unzip and run the Root.bat file to install SuperSU (Magisk in not recommended at this time, courtesy of JRKruse).
Samsung_G93x_QC_CF-SU_v2.82_2018-02-01_SSU+MGK.ZIP
https://www.androidfilehost.com/?fid=673956719939816727


Use the patched Odin flasher first, if it fails then try the regular version.
Samsung_Odin_v3.12.3_Patched.ZIP
https://www.androidfilehost.com/?fid=745425885120715012
Samsung_Odin_v3.12.7.ZIP
https://www.androidfilehost.com/?fid=889764386195917520
 
Last edited:

freeop

Senior Member
Aug 30, 2011
381
160
0
US
Follow this rooting guide carefully, do not skip any steps!!
And the usual disclaimer: Proceed at your own risk!!
Warning: All your data will be erased, so back up anything important!!
This guide contains the latest version files as of today.

1.
First, turn on ADB-Debug and OEM-Unlock in the Developer Options menu in order to avoid being locked out later on (search for it if you need help).
One thing I would add to this is to make sure you disable any security locks before rooting/flashing files. If you don't it will cause a boot loop.

And if you flash any stock firmware, make sure you go back and turn on the ADB-Debug and OEM-Unlock in the Developer Options. Anytime you flash new stock file, it will turn those off.

Just adding from experience :)
 
  • Like
Reactions: Craz Basics

billa

Senior Member
Mar 30, 2006
716
351
83
One thing I would add to this is to make sure you disable any security locks before rooting/flashing files. If you don't it will cause a boot loop.
And if you flash any stock firmware, make sure you go back and turn on the ADB-Debug and OEM-Unlock in the Developer Options. Anytime you flash new stock file, it will turn those off. Just adding from experience :)
In fact the same line has already been included in steps 1, 3, and 5, basically before and after every operation to enable ADB+OEM ;)
No need to disable user locks, because those would be wiped away by the full stock flash.

"Turn on ADB-Debug and OEM-Unlock in the Developer Options menu in order to avoid being locked out later on (search for it if you need help)."
 
Last edited:
  • Like
Reactions: freeop

freeop

Senior Member
Aug 30, 2011
381
160
0
US
In fact the same line has already been included in steps 1, 3, and 5, basically before and after every operation to enable ADB+OEM ;)
No need to disable user locks, because those would be wiped away by the full stock flash.

"Turn on ADB-Debug and OEM-Unlock in the Developer Options menu in order to avoid being locked out later on (search for it if you need help)."
Thanks for pointing that out. And I forgot the locks were reset with the installation of the firmware. Sorry...

Now here's a question for you, @Craz Basics, or anyone else that might know.

Can you just flash the eng_img without having to go back to the initial firmware?

I am on the 1 Dec 2017 firmware, G935UUES4BQL1, but on the earlier ENG_IMG and would like to install the Aug 2017 version. I don't want to do anything to go past the 1 Dec 2017 updates because of the RMM lock. I also am on the @Quickvic30/Craz Basics ROOT.BAT. So if I just flash the ENG_IMG should I update the ROOT.BAT also?

Just wondering if it was possible doing it that way instead of going through the whole process of installing stock, eng_img, root.bat, etc.

I guess I could install the full U-Firm Stock files, but use the HOME_CSC and not wipe anything, but I have always heard using the HOME_CSC could cause problems. Oh well will see what you al have to say before attempting this.
 

Craz Basics

Senior Member
Jul 2, 2015
1,546
612
0
Thanks for pointing that out. And I forgot the locks were reset with the installation of the firmware. Sorry...

Now here's a question for you, @Craz Basics, or anyone else that might know.

Can you just flash the eng_img without having to go back to the initial firmware?

I am on the 1 Dec 2017 firmware, G935UUES4BQL1, but on the earlier ENG_IMG and would like to install the Aug 2017 version. I don't want to do anything to go past the 1 Dec 2017 updates because of the RMM lock. I also am on the @Quickvic30/Craz Basics ROOT.BAT. So if I just flash the ENG_IMG should I update the ROOT.BAT also?

Just wondering if it was possible doing it that way instead of going through the whole process of installing stock, eng_img, root.bat, etc.

I guess I could install the full U-Firm Stock files, but use the HOME_CSC and not wipe anything, but I have always heard using the HOME_CSC could cause problems. Oh well will see what you al have to say before attempting this.
You're wanting to flash the newer eng? I don't have problems flashing the August one over January. Make sure you're on the August patch or later though.

Also, RMM lock is not present on January patch. Tested myself and rooted with August. And yes, it's a bit faster ;)
 
  • Like
Reactions: freeop

billa

Senior Member
Mar 30, 2006
716
351
83
Question, this G935x QC dont work for G930P?
The G935x will only work on the G935P/A/T/V (+ some other variants), and the G930x only on the G930P/A/T/V (+ some other variants).
You probably wanted to use the newer G935x eng-boot on the G930P but no can do, it's no compatible.


Please no posting of PAY sites on here, it's against XDA's rules/terms of use.


Thanks for pointing that out. And I forgot the locks were reset with the installation of the firmware. Sorry...
Now here's a question for you, @Craz Basics, or anyone else that might know.
Can you just flash the eng_img without having to go back to the initial firmware?
Just wondering if it was possible doing it that way instead of going through the whole process of installing stock, eng_img, root.bat, etc.
It's possible to flash the new eng-boot and even run the new Root.bat over the old installation, but it tends to run smoother on a new clean install.
Like Craz mentioned "Make sure you're on the August patch or later though."
As far as RMM security, the Jan. update may or may not have it, but I'm simply not taking any chances, because just in case it kicks in somehow, unfortunately there's no going back. It's always better to let others be the guinea pigs. ;)
 
Last edited: