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

Search This thread

Soldier_Rocks_08

Senior Member
Jul 26, 2011
322
57
Just wanted to let everyone know that this procedure still works with the ATT latest update, G935AUCS4BRC1 with the March 1, 2018 Security Update. Installed the Update and rooted the phone after that. Still works great. No sluggish operations, but will have to wait for a couple of days for the battery report.
Did you use the method from the first post?

Sent from my SM-G935U using Tapatalk
 

Soldier_Rocks_08

Senior Member
Jul 26, 2011
322
57
Yes pretty much. I used the eng.img from the first post and then used the Quickvic-Craz_root.bat. Worked just fine and no problems. Just make sure you let it sit for as long as possible (1 hour) after rooting. Let it settle.

Good luck.
Do you have a link to that root. Bat?

Sent from my SM-G935U using Tapatalk
 

goko855

New member
Apr 29, 2018
1
0
i did everything as said and when it rebooted theres no supersu and i keep getting signed out of my samsung account, i also tried installing supersu since root.bat didn't install it and supersu says my device isnt rooted despite my phone telling me my device is rooted
 

Craz Basics

Senior Member
Jul 2, 2015
1,546
617

Levi4cyber

Senior Member
Apr 26, 2018
153
37
OnePlus 9 Pro
I flashed the stock rom (nougat 7.0) mentioned in the first post with Odin but since the phone rebooted I already received 9 software updates from the mobile!!
Every time the software update finished and and the phone reboots the phone Is connecting to the server and automatically downloading another software update !
(I already downloaded and installed 9 updates ranging between 32 - 336 mb).
IS THIS NORMAL? OR SHOULD I FLASH A DIFFERENT ROM?
 

an531

Member
Feb 16, 2018
12
0
Has anyone tried to apply this root method to the BRD1 baseband version yet (e.g. G935UUEU4BRD1 for S7 Edge)?
 

an531

Member
Feb 16, 2018
12
0
Just wanted to let everyone know that this procedure still works with the ATT latest update, G935AUCS4BRC1 with the March 1, 2018 Security Update. Installed the Update and rooted the phone after that. Still works great. No sluggish operations, but will have to wait for a couple of days for the battery report.

Thanks for the info. How's the battery life on BRC1?
 

freeop

Senior Member
Aug 30, 2011
381
160
US
Thanks for the info. How's the battery life on BRC1?

Not bad at all. I can get around 24 hours on a full charge and that is with normal use all day. Phone calls, texting, navigating, email, etc. About the same as I was getting before. Pleased with the performance and battery with this update/root.
 
  • Like
Reactions: billa

devinalonzo

Member
Aug 29, 2013
42
16
Can't remember what build I was on but I had the December 1st security update. Updated to BRC1 with the March 1st security updates. The install went smooth for the most part. Used odin patched version to brc1. But the patched version failed to install the eng kernel so used the original for that. Performance seems better compared to past rooted builds. Samsung account keeps logging out? I feel like this happened on a past rooted build but I can't remember how I fixed it and haven't had time to read the comments here to see if someone has a solution. Will report back on issues/battery life/performance/etc.

Sent from my SM-G935U using Tapatalk
 
  • Like
Reactions: Craz Basics

billdauterive23

Senior Member
Jun 4, 2017
155
39
Moses Lake, Washington
Can't remember what build I was on but I had the December 1st security update. Updated to BRC1 with the March 1st security updates. The install went smooth for the most part. Used odin patched version to brc1. But the patched version failed to install the eng kernel so used the original for that. Performance seems better compared to past rooted builds. Samsung account keeps logging out? I feel like this happened on a past rooted build but I can't remember how I fixed it and haven't had time to read the comments here to see if someone has a solution. Will report back on issues/battery life/performance/etc.
Download titanium backup and wipe data for the Samsung accounts app
 
  • Like
Reactions: devinalonzo

m4xhp0w3r

New member
May 24, 2018
4
1
Portland, OR
Has anyone tried updating to BRC1 excluding the AP file and using the home csc? I know I can update and then reroot flashing the original engineering boot tar (as stated above) but I'm feeling lazy heh.

I've flashed my phone probably ten different times in the last couple of days and don't want to go through the trouble of setting things back up. It took me a while to get to the combo of files and firmware to a point where it was stable and not dropping root or getting the binary is occupied issue.

Actually, eff it :laugh:. I'll try to upgrade and report what happens. If it gets stuck on the Samsung boot screen (like I think it will), I'll have to do it again anyway.

Also, thanks to all who've contributed to this thread. Until a couple of days ago, it had been many moons since I flashed the last custom rom on my T-Moblie G1.

---------- Post added at 02:26 AM ---------- Previous post was at 01:32 AM ----------

I'm interested in this as well. Just flashed to this firmware and haven't gotten the ENG boot image to flash properly. It'll flash but after booting to the home screen, it'll reboot a few seconds later.

I had roughly the same problem after flashing the current no carrier G935UUEU4BRD1 BL, AP, and CSC firmware files and the T-Mobile modem CP file. Got stuck on the Samsung boot screen.
 

m4xhp0w3r

New member
May 24, 2018
4
1
Portland, OR
Has anyone tried updating to BRC1 excluding the AP file and using the home csc? I know I can update and then reroot flashing the original engineering boot tar (as stated above) but I'm feeling lazy heh.

I've flashed my phone probably ten different times in the last couple of days and don't want to go through the trouble of setting things back up. It took me a while to get to the combo of files and firmware to a point where it was stable and not dropping root or getting the binary is occupied issue.

Actually, eff it :laugh:. I'll try to upgrade and report what happens. If it gets stuck on the Samsung boot screen (like I think it will), I'll have to do it again anyway.

Also, thanks to all who've contributed to this thread. Until a couple of days ago, it had been many moons since I flashed the last custom rom on my T-Moblie G1.

---------- Post added at 02:26 AM ---------- Previous post was at 01:32 AM ----------



I had roughly the same problem after flashing the current no carrier G935UUEU4BRD1 BL, AP, and CSC firmware files and the T-Mobile modem CP file. Got stuck on the Samsung boot screen.

edit: So I got it to root on BRD1 with the AP left out and a Home CSC file and it was pretty stable for about 2 hours. And then it rebooted on its own and got stuck at the samsung boot screen and eventually lost all its battery life and turned off.

But then I happened upon
https://xdaforums.com/tmobile-s7-edge/how-to/5-12-17-stable-method-g935u-bqd2-quick-t3605516
And it seemed to worked for BRD1.

Thanks to @qwewqa for finding it and @purotijuana for doing the steps.

I started from a fresh install of all the SM-G935U BRD1 non-carrier using the T-Mobile CP file instead of the non-carrier version (from https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/) and let it sit for an hour to settle.

Bought the Package Disabler Pro and wiped data/disabled the Chameleon package. It is com.samsung.sprint.chameleon but it showed as 'Chameleon' in the list. So search for that instead of the actual package.

Did a wipe of cache (have to leave system to keep the package disabled), then flashed the engineering boot and got it to reboot, and then let it sit again for a bit. I was able to use the Samsung_G935_QC_Eng_Boot_Root_v2017-08-29.TAR with no problems this time.

Then I ran the Samsung_Security+OTA_Disabler_(BillA_v2018-01-01).BAT from @billa (thanks!) and then Samsung_G93x_QC_CF-SU_v2.82_2018-02-01_SSU+MGK.BAT from @jkruse (thanks!) with the fingerprint fix and a CPU governor tweek, and then the SU (since Magisk doesn't work with the locked bootloader).

File links for the engineering bootloader and the security and root bats are at https://xdaforums.com/showpost.php?p=75418504&postcount=2527 along with @billa's steps.

Then wiped cache again.

Everything looks good so far. its been sitting for a couple hours with no reboots.

I'm not sure how stable it is or what the battery life looks like. Its 2:30 am and I need to sleep now. I'll post another edit tomorrow.

Second edit: root is stable so far. I shut the phone off overnight so I could watch it.
No reboots in the last 6 hours.
Root is staying rooted.
Phone has zero lag so far. This BRD1 firmware is excellent.
Battery life is pretty good. It's dropping about 3% per hour with CPU governor set to on demand. I played around with the other governor settings and none made any difference.

Over all I'm very pleased.
 
Last edited:

Craz Basics

Senior Member
Jul 2, 2015
1,546
617
Has anyone tried updating to BRC1 excluding the AP file and using the home csc? I know I can update and then reroot flashing the original engineering boot tar (as stated above) but I'm feeling lazy heh.

I've flashed my phone probably ten different times in the last couple of days and don't want to go through the trouble of setting things back up. It took me a while to get to the combo of files and firmware to a point where it was stable and not dropping root or getting the binary is occupied issue.

Actually, eff it :laugh:. I'll try to upgrade and report what happens. If it gets stuck on the Samsung boot screen (like I think it will), I'll have to do it again anyway.

Also, thanks to all who've contributed to this thread. Until a couple of days ago, it had been many moons since I flashed the last custom rom on my T-Moblie G1.

---------- Post added at 02:26 AM ---------- Previous post was at 01:32 AM ----------



I had roughly the same problem after flashing the current no carrier G935UUEU4BRD1 BL, AP, and CSC firmware files and the T-Mobile modem CP file. Got stuck on the Samsung boot screen.
It's Knox making it reboot, run the root.bat asap after flashing eng to remove it ;)

And that camelion app should be removed as well with the root.bat
 
  • Like
Reactions: m4xhp0w3r

billa

Senior Member
Mar 30, 2006
864
389
It's Knox making it reboot, run the root.bat asap after flashing eng to remove it ;)

And that camelion app should be removed as well with the root.bat

Buying and using Package Disabler Pro is complete waste of time and money, since I have already posted a completely free and much better security disabler / un-branding solution. Seem like people don't search and read anymore... oh well... :D
 
Last edited:
  • Like
Reactions: austinu90

Top Liked Posts

  • There are no posts matching your filters.
  • 240
    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://xdaforums.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://xdaforums.com/member.php?u=1113488
    @
    princecomsy https://xdaforums.com/member.php?u=5028474
    @jrkruse https://xdaforums.com/member.php?u=1949695
    @jrkruse for his awesome job for making a custom flashable Android 7.0 Nougat ROM https://xdaforums.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://xdaforums.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://xdaforums.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://xdaforums.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://xdaforums.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://xdaforums.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://xdaforums.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://xdaforums.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.