yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
Thanks man!

Finally we got some answers:

1. KNOX will be NOT TRIPPED (it SEEMS)

2. Phone NORMALLY BOOTS

3. There are NO LAGS

Thanks for your full log!!

Seeing it I can affirm that finally

WE HAVE SOLVED READ-ONLY FILE-SYSTEM PROBLEM!

But this isn't enought..

It happened a really strange thing: "adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh" and "touch /system/xbin/su" return NO PROBLEM (the first resturns also a confirmation..).. BUT CHMOD COMMANDS SAYS THAT THESE FILES DOESN'T EXIST.. and this is really strange..

So, please, if you want to help us:

1. Download ES File Explorer , go in /system/etc (you do NOT need root permissions to do this) and SEE IF THERE IS A FILE CALLED

launch_daemonsu.sh

, write here if yes or not

2. Go in /system/xbin and SEE IF THERE IS A FILE CALLED

su

, write here if yes or not

3. Download Terminal Emulator from Play Store, open it and (when you opened the app), MAKE A SCREENSHOT AND POST IT HERE

4. Type *#1234# into Phone dialer and POST HERE A SCREENSHOT OF RESULTS.

Really thanks again for your feedback and log and thanks in advance for your answers. These are VERY IMPORTANT FOR US[emoji6]

Thanks
[Samsung Galaxy S7 Guides, News, & Discussion] ninohs:
Does anyone post a guide?
[Samsung Galaxy S7 Guides, News, & Discussion] :
Hi! The boot stuck on samsung logo, after execute the bat file.

This is the log:

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell mount -w /
Usage: mount [-r] [-w] [-o options] [-t type] device directory

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell mount -w /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell mount -o rw,remount /

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb push SuperSU-v2.74-2.img /data/su.img
5233 KB/s (33554432 bytes in 6.261s)

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell mount -w /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell mount -o rw,remount /system

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh
414 KB/s (4686 bytes in 0.011s)

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb install -r SuperSU-v2.74-2.apk
protocol failure
- waiting for device -

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell 0<supersu.cmds
root@hero2lte:/ # mount -w /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|root@hero2lte:/ # mount -o rw,remount /system
root@hero2lte:/ # touch /system/xbin/su
root@hero2lte:/ # mount -o rw,remount /system

SM-G935F

EDIT: I disconnected the cable and the phone did boot normally. Oo
[Samsung Galaxy S7 Guides, News, & Discussion] kersian:
Possible to check this for [MENTION=7119432]lucadalba[/MENTION]?

So, please, if you want to help us:

1. Download ES File Explorer , go in /system/etc (you do NOT need root permissions to do this) and SEE IF THERE IS A FILE CALLED launch_daemonsu.sh , write here if yes or not

2. Go in /system/xbin and SEE IF THERE IS A FILE CALLED su , write here if yes or not

3. Download Terminal Emulator from Play Store, open it and (when you opened the app), MAKE A SCREENSHOT AND POST IT HERE

4. Type *#1234# into Phone dialer and POST HERE A SCREENSHOT OF RESULTS.
[Samsung Galaxy S7 Guides, News, & Discussion] :
I remade the whole procedure again.

1) No

2) No

New log:

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb wait-for-device

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell mount -w /
Usage: mount [-r] [-w] [-o options] [-t type] device directory

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell mount -w /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell mount -o rw,remount /

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb push SuperSU-v2.74-2.img /data/su.img
4166 KB/s (33554432 bytes in 7.865s)

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell mount -w /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell mount -o rw,remount /system

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh
error: protocol fault (no status)

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb install -r SuperSU-v2.74-2.apk
4203 KB/s (6348638 bytes in 1.474s)
pkg: /data/local/tmp/SuperSU-v2.74-2.apk
Success

C:\Users\Administrator\Downloads\Samsung_Root_All_S7_EX_models_(BillA+lucadalba_edit)\Samsung_Root_All_S7_EX_models>adb shell 0/dev/null 2>&1; echo $?` -ne 0 ]; then
echo '/system/etc/launch_daemonsu.sh' >> /system/etc/init.sec.boot.sh
fi
syncroot@hero2lte:/ # mount -w /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|root@hero2lte:/ # mount -o rw,remount /system
_

Enviado de meu SM-G935F usando Tapatalk
[Samsung Galaxy S7 Guides, News, & Discussion] Indirect:
It looks like your eng kernel still has dm-verity enabled and erases it on reboot. You could try symlinking it or finding a different way to bypass it.
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
Thanks for your important feedback!!

Ok the really strange thing is that needed files are pushed into system but it seems they have been deleted just after moment..

Anyway I can tell again that we have totally solved system read-only file-system problem and we have done another step..

Thanks for your really useful advice!

I will follow it and I will update the method (when I get free time)! Thanks again!!
[Samsung Galaxy S7 Guides, News, & Discussion] :
And for go back to stock kernel? I need flash CP rom file? :confused:

EDIT: I already solve! :P
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
Now have you reflashed stock kernel or firmware?
[Samsung Galaxy S7 Guides, News, & Discussion] :
Stock kernel. :)
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
Ok please can you do another thing please?

This does NOT require root but it will comfirm if su.img has been pushed into /data (also if /data is accessible only with root, this command will check for su.img existence without root..)..

If you do this, then I can begin to work on new commands that could finally work..

So:

1. Download this file on the PHONE and move it into /sdcard : https://mega.nz/#!qwM1zazD!GfJCh3WzD5vktTxcMM5C_lODqDxanVY-ePfXA-eH7Jo

2. Open Terminal Emulator and type this command:

sh /sdcard/suimg.sh

3. Press enter

4. Make a screenshot and post it here.

Thanks in advance and really thanks for your tests!
[Samsung Galaxy S7 Guides, News, & Discussion] kersian:
Just curious, Will there be a g935fd engkernel since the one given might create bootloops?
[Samsung Galaxy S7 Guides, News, & Discussion] :
This need a engineer kernel, right?

Enviado de meu SM-G935F usando Tapatalk
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
NO, it doesn't;)

Just follow steps..

EDIT: [MENTION=4773035]mariojuniorjp[/MENTION] the "Terminal Emulator" is the ANDROID APP that you have downloaded following my previous post..

[MENTION=4773035]mariojuniorjp[/MENTION] this app:

[emoji6]

EDIT2:

Sorry screen corrected[emoji23]
[Samsung Galaxy S7 Guides, News, & Discussion] sendhiloo7:
Is that trip the knox ?
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
NO.. it only check if su.img is installed in /data .. but only who has executed Root.BAT can do this test.. else it would be useless..
[Samsung Galaxy S7 Guides, News, & Discussion] :
Enviado de meu SM-G935F usando Tapatalk
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
Oh YEAHHH!

This means that the script works and the dm-verity doesn't touch /data!

Now I will begin to work on new commands and symlinks!!

Thanks again to [MENTION=3854041]Indirect[/MENTION] for his advice and to [MENTION=4773035]mariojuniorjp[/MENTION] for tests!
[Samsung Galaxy S7 Guides, News, & Discussion] :
Thank you for your excellent work! ?

Enviado de meu SM-G935F usando Tapatalk
[Samsung Galaxy S7 Guides, News, & Discussion] ikinkyxd:
I can understand that this means root but what happens if you flash twrp? Will it then trip knox?
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
YES, IF YOU FLASH TWRP YOU WILL TRIP KNOX.. because this method is for ROOTING and it uses engKERNEL , NOT engBOOTLOADER..
[Samsung Galaxy S7 Guides, News, & Discussion] ikinkyxd:
Ahh okay. Thanks for the clarification.
[Samsung Galaxy S7 Guides, News, & Discussion] yebin21314:
g935w8 doesn't work

i tried already with my G935W8 ...IT'S trip knox ..... 0x1 now...:D:D:D
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
I will add G935W8 and G930W8 in a blacklist of this method.. probably kernel is not made for G935W8 because flashing the engKernel on G935F KNOX REMAINS 0x0..

I'm sorry for your knox :(

Anyway thanks for the feedback[emoji106]
[Samsung Galaxy S7 Guides, News, & Discussion] jonlad1:
I will be happy to make a donation for your work once this is confirmed to work and is easily reproducible.

Thanks
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
You can found donate button at the left of all my posts in xda desktop site..

But WORK IS

NOT FINISHED YET

.. we have to found a way to bypass DM-verity.. because if we don't bypass it, root will be useless because all system modifications will be lost on reboot.

Anyway REMEMBER I'M ONLY TRYING TO FIX SOME ERRORS..

THE METHOD AND KERNEL HAS BEEN CREATED BY [MENTION=293193]billa[/MENTION] , [MENTION=5028474]princecomsy[/MENTION] , [MENTION=4911585]br3w3r[/MENTION] and [MENTION=631273]Chainfire[/MENTION] , so THANK THEM

Now I'm trying to get more info on dm-verity..
[Samsung Galaxy S7 Guides, News, & Discussion] jonlad1:
Thanks for your work
[Samsung Galaxy S7 Guides, News, & Discussion] sujaanj:
So, just to be clear, I tried the engkernel root method on my 930FD when billa first posted it. Yes, the script wouldn't run because of system not mounting rw, but the phone did actually boot thereafter.
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
Ok.. I'm basing to this comment.. http://xdaforums.com/showthread.php?p=68207625

Anyway if you tell that with engKernel G930FD will boot I will correct the post[emoji6]

Thanks
[Samsung Galaxy S7 Guides, News, & Discussion] Thunderica:
I also tried this method on my G930F but no succes on root script. It remains stuck on mounting system.
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
This method must be tried immediately after the beginning of the bootanimtion.. and it should be tried more than one time if the script doesn't work.. anyway as I wrote before, this method is incomplete else and you will not get your device rooted..
[Samsung Galaxy S7 Guides, News, & Discussion] Thunderica:
So i mannaged to finish with succes but still no superuser app on phone. I only want to obtain a temp root so i can use z3x tool to read sim lock code from my phone without knox voiding. Is this a way to obtain root or not? What am i missing? I have security notice bot i can't see a supersu app and if i use root cheker it's not rooted.
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
You cannot get root for now.. read well my announcement..
[Samsung Galaxy S7 Guides, News, & Discussion] Thunderica:
Ok. I can confirm that will not trip knox on G930f with latest BTU firmware. Tried 3 times and knox still 0.
[Samsung Galaxy S7 Guides, News, & Discussion] navis83:
Hello, I found this thread that in such way explain how to fix dm- verity error:

http://xdaforums.com/note-4/orig-development/fix-drk-dm-verity-factory-csc-serial-t3422965

I'm a newbie but I can understand that dm- verity check is linked to firmware that you are using, so the eng one at moment. Did you try to update system files and also flash original firmware (if it's feasible)?
[Samsung Galaxy S7 Guides, News, & Discussion] mauricewal:
I am really keen on rooting my device without tripping Knox.

So will keep an close eye on this topic! Hope you will have an breakthrough soon
[Samsung Galaxy S7 Guides, News, & Discussion] web-9g2Ifw:
test

I dont own a s7

I got a j7

Will this work on j700f ?

It has Exynos 7580
[Samsung Galaxy S7 Guides, News, & Discussion] nitrous²:
No.
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
Thanks but we need to disable.. not to fix dm-verity error.. but thanks anyway[emoji106] all helps are appreciated

No
[Samsung Galaxy S7 Guides, News, & Discussion] web-9g2Ifw:
Thank you for replying seniors.

So eng kernel is only for s7 exynos cpu
[Samsung Galaxy S7 Guides, News, & Discussion] nitrous²:
Amateur question: The SD S7(Edge) and the Exynos S6(+ & Edge) also achieved root without tripping Knox (using engBootloader though). Didn't they had to deal with dm-verity? How'd they got around it?
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
They haven't this problem.. thay also haven't read only file system problem..
[Samsung Galaxy S7 Guides, News, & Discussion] 1jn14r:
Sorry if this has been said before, but couldn't you use a systemless root to get around dm verity?
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
This root method is mostly systemless.. but anyway we must put some strings into system files..

And we can't use completely systemless root because it would trip knox..

And anyway having root with dm-verity is totally useless: you could NOT change even a build.prop string because dm-verity would see it and revert changes..
[Samsung Galaxy S7 Guides, News, & Discussion] nitrous²:
Man, I'm getting depressed here. Looking at old xda threads, looking for something helpful regarding disabling dm-verity, came across the AT&T Galaxy Note 4 thread. They're in a similar situation. They're almost there but are stuck at a way to disable dm-verity....for more than a year now...

Nevermind; their situation is more different than I though it to be.
[Samsung Galaxy S7 Guides, News, & Discussion] mauricewal:
Is the s7 edge so much different that they can root without tripping Knox?
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
It seems to have not dm-verity..
[Samsung Galaxy S7 Guides, News, & Discussion] navis83:
This is an update on the current analysis me and lucadalba are performing: the available engineering boot.img allows us to connect within the phone using ADB as it allows debugging mode, but whenever we try to change the content of system partition, on restart we have it "verified" because inside boot.img fstab.* configuration file there is the Verify flag enabled. It means that, in order to avoid the verification, we might remove such flag from fstab.* files, but they are inside the bootloader partition. Two possible ways to proceed:

a) we modify externally (using AndroidKitchen) the engineering boot.img and we flash it using odin

b) we modify internally (using a script pushed via adb shell) the bootloader partition

In both cases, I personally don't know if knox will be triggered, so I want wait for your comments about these solutions.
[Samsung Galaxy S7 Guides, News, & Discussion] :
Send me the script and boot.img modified.

I'll test it.
[Samsung Galaxy S7 Guides, News, & Discussion] navis83:
I'm going to prepare a script, starting from current version, that will do all the necessary steps to modify the boot.img internally. Let's hope in an answer before the testing :).

---------- Post added at 06:52 PM ---------- Previous post was at 05:58 PM ----------

Guys I was trying my best to make the patching script but I assume it would be better if we try to involve the original developer who made the patch for boot that is [MENTION=5672995]jcadduono[/MENTION] . I will send him a PM to try to involve in this work: it's better to make a good and well done script, otherwise we might brick our phones.
[Samsung Galaxy S7 Guides, News, & Discussion] jcadduono:
Trying to understand now what you guys are trying to accomplish. If it's root without tripping the knox flag to keep Samsung Pay & Knox, S-Health, Gear Fit, Secure Storage related functions then any modifications to a boot image (yes, even eng boot has a signature that is broken with any modifications) will result in tripping the flag, taking any of my or Chainfire's boot patching methods out of the question.

If you have some form of shell root access (ex. adb root + adb shell) from the engineering boot you can effectively run a script to set up su daemons that run from data partition or memory without modifying system partition, and set this to run each time your device boots. This is the ideal method when a device is bootloader locked but has a kernel exploit available.

Otherwise an engineering boot image with dm-verity enabled and no root shell access isn't much different from a non-engineering boot image?

BTW: If this were an engineering boot image with verity enabled, then wouldn't you need the matching engineering system partition (ROM) to boot it?

It would seem unusual to build an engineering boot image with the verity signatures of a release ROM?

I forgot to also mention that post BPH6 Samsung will probably be adding the same anti-live-root protection to the S7 kernel that they did with the Note 7 kernel.

This will cause the device to reboot whenever an untrusted process obtains root access, effectively killing live root exploits.
[Samsung Galaxy S7 Guides, News, & Discussion] :
Yes, makes sense.
[Samsung Galaxy S7 Guides, News, & Discussion] tetsuo55:
I think this would be fine for our purposes. How can we make this happen?

ping [MENTION=7119432]lucadalba[/MENTION] [MENTION=2976080]navis83[/MENTION]
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
Yes we have root via ADB but also dm-verity enabled with engKernel..

We are trying to ROOT THE PHONE VIA SUPERSU (edited script buly Chainfire. Made FOR THIS MOD) and DISABLE DM-VERITY

WITHOUT TRIPPING KNOX

to DON'T LOSE SAMSUNG WARRANTY.

We don't know if there is also an engSystem.. we also don't know where has been token the engKernel.. we only know who has shared it and tried to contact.. but he doesn't reply to messages..

So we are waiting for an answer by the person who has shared engKernel, because he is the only person that could disable dm-verity without tripping knox
[Samsung Galaxy S7 Guides, News, & Discussion] jcadduono:
they can't disable dm-verity, the whole point of dm-verity is that it prevents modifications to the system partition, and dm-verity can only be disabled by removing the flag from the boot image, which IF you modify you break the signature of the image, meaning it can't be booted without tripping knox.

if no one's actually tried running this engineering kernel, then you don't know if it's verity signed for an engineering system which you don't have, ex. the image is completely useless. if it boots up fine on some release system then you're pretty lucky because it's hard to imagine someone would build an engineering boot image specifically signed for a release system.

so unless someone leaks a ANY boot image (eng, userdebug, or release), with dm-verity DISABLED, i don't think this thread can really go anywhere.

the alternative, which is a bit less useful, is for someone to leak the engineering system image that goes with this engineering boot image. at least then you'd have your root shell access.

still, you'd have to deal with su-killer in the kernel code which can't be modified. yikes.
[Samsung Galaxy S7 Guides, News, & Discussion] lucadalba:
The first engKernek was for Snapdragon.. than A USER PORTED IT FOR EXYNOS, and if this user succees to port it on exynos, it means that HE EDITED BOOT.IMG AND HE KNOWED HOW TO RESIGN (maybe he is a Samsung technic.. I don't know).. because we have testers that can confirm that they have FLASHED EXYNOS ENGKERNEL (

EDITED

VERSION of SNAPDRAGON KERNEL) and their KNOX REMAINED 0x0.

So THE PERSON WHO PORTED engKernel to EXYNOS (because FIRST ENGKERNEL WAS FOR SNAPDRAGON) SHOULS BE

ABLE TO EDIT KERNEL AND RESIGN IT

(or anyway he should know the way to wdit kernel without tripping knox..) else it would be impossible that our testers noticed knox remains 0x0 (because, I repeat, this is a ported kerne from snapdragon..)..

I don't know if I'm explaining well..

And it's obvious that if WE edit kernel we trip knox.. but this person should know the method to skip this problem.. (because he ported snapdragon kernel on exynos.. and his kernel doesn't trip knox.. here is why I'm really hoping he answers to my messages..)
[Samsung Galaxy S7 Guides, News, & Discussion] jcadduono:
no, you can't just port a kernel between the two, editing modifies checksum which breaks signature, if they really did just shove snapdragon kernel inside exynos boot image then you're getting nowhere at all lol, kernels control hardware and those are two completely different chipsets hahah

if knox remained 0x0 then the boot image wasn't even valid enough for aboot to continue :| (or just didn't flash at all)
[Samsung Galaxy S7 Guides, News, & Discussion] nitrous²:
[MENTION=5672995]jcadduono[/MENTION] I don't understand what's going on right now. The Exynos S7E did boot this kernel already (Cic3ro Post #46).

EDIT: OK, I think you meant that ODIN didn't even successfully flashed the boot.img.
[Samsung Galaxy S7 Guides, News, & Discussion] mgigantoregistros:
If ODIN didn't flash it at all, it would means we are able to get live root without requiring to flash...

Is it not even better?
[Samsung Galaxy S7 Guides, News, & Discussion] navis83:
Analysing better your log seems that some commands were not taken into account because of bad format (mount commands in details).

At same time I see that into the script there are many remounts, that means "reload" the partition to its original state.. so I modified the root.bat script to take care of such considerations, but now I need that someone test it following the complete procedure.

https://mega.nz/#!nI801RwB!pa5cwiNR6g_N4pQUq3o78pAZb7XUxbC9wqW3DjDIPDg

S7 (G930F) and S7 Edge (G935F) testers are welcome ;). The procedure can be tested also by guys that have knox already tripped, just restarting from original Rom: this procedure will not restore the knox to 0x0 for them but at least we verify that root is obtained. Thanks
[Samsung Galaxy S7 Guides, News, & Discussion] navis83:
Try this new one

https://mega.nz/#!WQN1kCwZ!-Qr6ZZVCo9Iyt_TuPt245r98P8me_6zad_g_kKoaNWE

Thanks

---------- Post added at 06:18 PM ---------- Previous post was at 06:13 PM ----------

If it doesn't work, try with this one

https://mega.nz/#!qVVQTBYA!45L3YdB_CNgFjtcG6mHQyabeQd3fGCDc0datImFWF2E

Thanks ;)
[Samsung Galaxy S7 Guides, News, & Discussion] navis83:
This is latest version, number 4: it will reboot the phone during the process, don't worry about that.

https://mega.nz/#!zRk2RIjT!8h4LLwWfkm9fKLdj5rFC2MGBNXKp6j9wyE2PUEI059U