yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Umm.... Do you have stock recovery? If so, then booting into it and then just leaving it through selecting Reboot to System should make the DM-Verity verify the hash-tree if it is enabled.

Otherwise, I honestly don't know at this point, this question seems to be pretty rarely asked. :confused: (which is of course why you asked it :( )
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Hmm... Do you have root i.e. Did you run root.bat or use some other tool to root after flashing stock?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
When boot into recovery says in red text "dm-verity verification failed" and when selecting reboot nothing extra appears

---------- Post added at 10:19 PM ---------- Previous post was at 10:16 PM ----------

no i didnt do root.bat (yet) even tho i know it works
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Well there's that idea, DM-Verity seems to be enabled. By the way, you don't seem to have any unauthorised firmware running at this moment so why did the DM-Verity fail?

Also, even if we cannot use the engKernel we could still try the modified boot.img, the only problem is that it is only available there for the S7 and S7E devices.

Side Note: You mentioned that you could run adb as root with kernel, if we could this without violating Knox, then we could try to make a root that runs on every boot. (this does not seem to be patched in the engkernel) (i.e. something like using the dirtycow vulnerability).

Extra Side Note: Is there any way we could check if DM-Verity is enabled in the modified boot file, without having to actually flash it.

Extra Extra Side Note: Why is there a cert file anyway then, if we cannot confirm or deny that it will trip Knox or not with it?

By the way, You are able to exit recovery right?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
actually if i try to exit the recovery it reboots and goes straight back in after maybe 5 attempts it goes back into the system and when it doesnt i flash the kernel again. Also in status in settings it shows custom instead of official but i think that appeard in qcom s7's too
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Yawn.... Signing Off for now, it is very late where I live.

Sorry I cant help right now.:(
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Hi [MENTION=6185853]Rainbow_Dash[/MENTION],

Any updates on your phone?

By the way, I opened the default.prop of the modified boot.img.

Here is copy-paste of it.

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
telephony.lteOnCdmaDevice=0
rild.libpath=/system/lib64/libsec-ril.so
rild.libpath2=/system/lib64/libsec-ril-dsds.so
persist.security.ams.enforcing=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.zygote=zygote64_32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
ro.dalvik.vm.native.bridge=0
debug.atrace.tags.enableflags=0
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Fri Feb 5 03:06:57 KST 2016
ro.bootimage.build.date.utc=1454609217
ro.bootimage.build.fingerprint=samsung/hero2ltexx/hero2lte:6.0.1/MMB29K/G935FXXE1APB5:eng/test-keys

As you will notice ro.secure is equal to 0, if I am right this means that DM is disaled in this modified boot.img.

By the way, here is the default.prop of the original engkernel.

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
telephony.lteOnCdmaDevice=0
rild.libpath=/system/lib64/libsec-ril.so
rild.libpath2=/system/lib64/libsec-ril-dsds.so
persist.security.ams.enforcing=1
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.zygote=zygote64_32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
ro.dalvik.vm.native.bridge=0
debug.atrace.tags.enableflags=0
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Tue Sep 27 15:33:53 KST 2016
ro.bootimage.build.date.utc=1474958033
ro.bootimage.build.fingerprint=samsung/hero2ltexx/hero2lte:6.0.1/MMB29K/FA60_G935FXXU1API2:user/test-keys

Here the ro.secure=1, which seems to indicate DM is enabled, as seen by [MENTION=6185853]Rainbow_Dash[/MENTION] on his device when he flashed it.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Ivan_Meler:
DM-Verity expects system image that it was shipped with thats why it fails and that also causes it to loop back to recovery on boot

Also if we do modify boot.img it would trip knox since image wouyldnt be signed anymore
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Thanks [MENTION=4610599]Ivan_Meler[/MENTION] for clearing up why DM-Verity failed!

The modified boot.img seems to be just an normal engkernel with DM verity disabled, mock locations on etc., it may be possible that it is signed with a valid signature, although I do admit that it is unlikely.:( Otherwise, if this does not work we may try to make a run-as root file with something like the dirtycow vulnerability as it may not be patched up (purposefully) in the engkernel by the Samsung devs. :fingers-crossed:

By the way, How did the Snapdragon people make their No Knox method, if not by using an engbootloader and kernel?

Also, we still have no news about the engbootloader here, we are now waiting for any person willing to risk their phone by trying the sboot to report back here. (which is unlikely to ever happen as I heard the wrong/bad bootloader may hard-brick their device)

By the way, can anybody explain why can't we just flash a newer bootloader if using the engbootloader causes some errors or bricks your phone. I think that Samsung bootloader downgrade protection would not apply here. :confused:

Edit: If anyone wants to test the modded kernel, they can, it won't hard-brick your device, however, the same thing cannot be said for KNOX, it may or may not be tripped.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] :
This exploit does not work on the S7 with Exynos, even with older versions of the monthly security patch.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Well, then! We just have the option of checking out the modded boot.img now.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Ok since obviously no one will flash the engroot kernel i will. Anything in particular i should look for assuming it boots?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] js45721:
Results?

Gesendet von meinem SM-G935F mit Tapatalk
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Well... You should really only flash the boot.img if it is for your device (S6E+). Otherwise, I am pretty sure that it won't boot. :( So the only option we have is to find the eng_root image for your device and considering there is only the "G928T_UVE3DPG1_ENGROOT.7z" available other than the g930 and g935 on the source website, if you have the 928T then we are in luck and can go ahead with the testing, if not then flashing it probably won't boot up.

By the way, to answer your question, assuming the phone boots , you should of course check if DM is disabled ( through recovery), since we cannot check if Knox was re-tripped (can we?) , the only other thing left would be to check if the devices says that it has the engineering firmware running, (i.e. if the device says test_keys) which it should.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Well i dont have a g928t (tmo) i have the g928f variant but so was the other engboot and it did boot anyways.Also i doubt i need to find that firmware as the other engboot was compiled in february and i had the december update.None of those firmwares seem to exist on sammobile anyhow

Atm in doing a twrp backup (takes long to do a 45gb backup) and will flash and see how it goes
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
flashed the engroot kernel booted fine in recovery "dm-verity check failed" -eng in kernel version.Nothing much seems changed
[Samsung Galaxy S7 Edge Guides, News, & Discussion] nitrous²:
Doesn't that mean that DM-Verity is disabled?

Nvm. Just re read the last page.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Thats exactly what happned with the last engboot kernel. Nothing seems changed with this rooteng kernel
[Samsung Galaxy S7 Edge Guides, News, & Discussion] js45721:
So we have nothing?

Gesendet von meinem SM-G935F mit Tapatalk
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
[MENTION=6185853]Rainbow_Dash[/MENTION]

So, I flashed the ENG_ROOT file for the 935F.

I unticked Auto Reboot in Odin. The file flashed successfully, and I turned the phone off. Booted into recovery, wiped cache, then hit 'Reboot System now', it took a few seconds on 'Verifying DMVerity hash tree', then it said 'Successfully verified DMVerity Hash tree', but one thing I noticed was in recovery there was another line of text (error message) in red font, didn't read it since the phone rebooted very quickly. Anyway, I left it for over 5 minutes on the S7 Edge logo, hoping to see a blue LED, but it still didn't boot.

Good news, it too did NOT void KNOX, so I'm still safe.

Lastly, the first two eng kernels were approx 26-27 MB each, this ENGROOT one is 38 MB, and the stock boot.img from the ROM I'm already on, is also around the same size.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] CuBz90:
I'm about to root so if anyone needs any testing doing before I root, let me know and I'll be willing to try. Be quick tho, I can't hold back much longer lol
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
If you still haven't rooted, please try the eng root file and check adb logcat it as that will help everybody know what problem we have!
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
This is maybe because of the wrong model kernel being used?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] CuBz90:
Unfortunately as I had no response I went ahead and rooted.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Ah well thats OK!
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Hi Everybody,

So, here is an update of what we have found so far!

1. The Eng kernels / root are signed by Samsung and do not seem to trip KNOX. :good:

2. The Eng_Root files are signed files that allow you at least ADB root shell access? (correct me if I am wrong!) :victory:

3. The Eng_boot files are bootloaders but we can't confirm nor deny if they are signed by Samsung or if they are actually Eng files. :(

So, that's a brief summation of everything so far! I think it is possible to use the root file for doing this!

P.S. What about doing cosmetic changes to your phone's KNOX and System Status, I mean, if you could just change your system to display that KNOX is not tripped always and that your System Status is Official!

The obvious downside is that Knox will show as tripped if you flash another ROM or use something that can directly check KNOX's status, however, the obvious answer to that is to re-patch your system (maybe automatically by the ROM) and not allow Samsung Care to unlock your phone (if your problem is an hardware issue like a broken screen).
[Samsung Galaxy S7 Edge Guides, News, & Discussion] CuBz90:
This is possible with Venus342's KNOX Reset Pro. Many people have claimed it has worked (according to the developer). The app has recently been removed from the app store.

This method simply shows 0x0. Knox will work but Samsung Pay will not.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Yep! I know about that application by Venus342, have you tried that out?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] CuBz90:
No. Don't fancy paying £22 for something I don't really need. If I ever need it I might try it.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Schrotty35:
Its working with s7 edge real?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] EasyGoingXD:
[MENTION=7345227]venus342a[/MENTION] Maybe the dev can help us with this question :)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] venus342a:
Hello,

Greetings. KNOX Reset Premium is compatible with S7 Edge. Tested by me, beta testers and app users (90% users use S7 Edge). Although incase of any issues, we'll provide you 100% refund. I'm extremely sorry for the high costs, but see everything requires money. We hired 4 developers from XDA to help me. They are still there, and we pay them $100 each month. Additionally there are many other costs so real sorry! :(

We'll launch demo version soon.

It wasn't removed from Google Play Store by Google.

We stopped production for January due to high amount of requests. We'll publish it again on play store on 3rd February.

Enjoy!
[Samsung Galaxy S7 Edge Guides, News, & Discussion] nitrous²:
So it's just a cosmetic change then?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Has_anDroid:
Oh my god knox
[Samsung Galaxy S7 Edge Guides, News, & Discussion] nitrous²:
Could this be of any help for a new approach? https://googleprojectzero.blogspot.de/2017/02/lifting-hyper-visor-bypassing-samsungs.html

I mean, he leveraged all of KNOX security mechanisms on the Kernel level according to the article I read about this.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
No, It says explicitly that KNOX which Samsung tells us is an hardware component works again after using it, but the website says that you need to have stock for it to work, so I think that it may be useful for getting your warranty back if you can still access your device. You could just flash stock, root, install the App, and then voila! Warranty back. This is all assuming that it actually works and is not a scam. :)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
[MENTION=6185853]Rainbow_Dash[/MENTION],

You said specific exploits were left open previously, what exploits did you mean?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
[MENTION=5063250]murtaza02[/MENTION],

Maybe it is because you didn't have the sboot file flashed? By the way, did you try to use ADB logcat using your laptop? I attached it here if you may want to flash it again! :)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
Not sure if flashing it now will work since I'm on stock Nougat...

Sent from my SM-G935F
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Eh.. It doesn't matter.

Powered by Android N on my Samsung Galaxy S7E!

:D
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
Give me till later today to try it out.

Sent from my SM-G935F
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Eh.. It doesn't matter, maybe somebody else would like to try! :)

Powered by Android N on my Samsung Galaxy S7E!

:D
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
[MENTION=5063250]murtaza02[/MENTION],

Any updates? :)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
Aha yes, forgot to post here even though I went ahead with everything.

Flashing the sboot file, failed. I thought it was because I used Odin 3.12.3, so I used the other modified Princecosmy Odin instead. Same thing, sboot didn't flash. I eventually got bored of it, so I went ahead and voided KNOX anyway, running Resurrection Remix on my phone now, and I couldn't be happier.

Seems these files were fishy after all, since none of them seem to work.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
How about the Eng_Root file? And the sboot file probably could not be flashed because you were on the Nougat Update, so Samsung Bootloader Downgrade Protection applied, when I said it wouldn't matter, it was for the boot.img, not the sboot.bin one, SBDP does not usually apply in in-between OS updates but it certainly does when upgrading to Nougat. :)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
I had flashed the Engroot file earlier, back when I was still on MM, and that had the same result as the ordinary eng kernel files. Flashed successfully, didn't void KNOX but didn't boot. Didn't even trigger dm-verity in stock recovery.

Sent from my SM-G935F
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Err... Sorry for the miscommunication there, my bad :( , I was actually asking if you could just do an adb logcat on the phone when it didn't boot, or if the phone booted enough for adb to recognize it.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
Are logcats even possible on the S7 edge boot screen?

It didn't boot at all, so there was no way for the PC to recognize it in that state.

Sent from my SM-G935F
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Aaarggh... Just checked, it seems it was possible in the S6E but not in the S7 :( .
[Samsung Galaxy S7 Edge Guides, News, & Discussion] TRoN_1:
I wonder if chainfire has commented on this Knox reset app. I searched everywhere and can't find ANYONE that successfully got an S7 edge to change from

Warranty Void: 1 (0x0100) or (0x030c) to

Warranty Void: 0 (0x0000)

when in Download mode. And I think that is where it really counts for Samsung warranty. They check there first.

No youtube, no forums, nothing confirming that it works. I did read a few new xda so called "members" with 1 or 2 posts confirming it WORKS! and how AMAZED they are :) :)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
[MAYBE] Solution to Eng-Root not working.

Hi all,

I had been puzzling over why the Eng-Root file flashed w/o tripping knox but didn't make the phone boot up.

I thought that maybe it is because we were downgrading from a newer bootloader to this Eng_Root file so I decided to try to flash Stock firmware that was built before the 5th of Feb. When I checked with Updato, I noticed a strange thing, there is NO firmware which is older than March, therefore,

I went and tried to find the original source of the Eng_root file because it was bound to have something an test file, I spent my whole day. (most of it was spent on getting to know what I had to find!)

And found a bootloader which had a build date of the 4 Feb 2016 with the original source of the file which it turns out was from the Z3X Samsung Box.

So, now that the explanation is over, here are the links to the file!

Note: I have unpacked all the boot.img files and attached them so anybody who wants can see what's inside the boot.img for themselves. With it, I have also put the orig. sboot.bin file if anybody wants to check that too. :)

P.S. I also found a .tar.md5 version of the ENG_Root file, I have included both versions. (.tar and .tar.md5)

Edit: I just realized you can select which files to download from Google Drive. :facepalm:

Link to Unpacked boot.img files and Original files: Google Drive Link

Link to only Unpacked boot.img + sboot.bin: Google Drive Link

Link to Original Files: Google Drive Link

Edit: Great, I bricked my phone. :(

Update: No worries, flashing stock made it work. :)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
Will see if I can try it out, though it probably wouldn't work because I'm on Nougat, but I'll see.

Best part is, I traded in my 0x1 Black S7 edge, for an almost new Silver Titanium one with 0x0 KNOX so I should be able to experiment.

Sent from my ONEPLUS A3003
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Sorry... The orig_boot file has an invalid MD5 hash, Odin says binary is invalid.

Also, trying to flash the .tar.md5 version of the root file gave me a bootloop on Nougat.

P.S. After flashing the root file on my device, it kept automatically re-booting even after a simulated battery disconnect :( , the trick was to quickly switch into Download Mode before it re-booted, I guess my fault for turning on Auto-Reboot. If you're going to try, it is best to first downgrade to MM and then try. :)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] archit12:
Any updates on this?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Matt_85:
anyone is willing to try ?

i think the best thing is to downgrade to a full original firmware with a build date before the 5th of Feb,

then try to flash sboot and eng kernel right?

since [MENTION=7554803]Random04[/MENTION] recovered his from the brick , i think it should be almost risk free

anyone got that particular stock firmware?

the only thing i'm wondering about if it is possible to downgrade BL to MM version when flashing full stock MM rom through odin

any news, anyone tested this procedure ? i think we may be close :fingers-crossed: , it would be a shame to surreder now

edit:

i found these:

https://samsung-firmware.org/model/SM-G935F/region/BTU/ (29.01.2016)

https://samsung-firmware.org/model/SM-G935F/region/ZTO/ (04.02.2016)

https://samsung-firmware.org/model/SM-G935F/region/WIN/ (04.02.2016) Italy branded (Wind)

edit #2 :

i managed to flash G935FXXU1APB4 stock fw which is before 5 feb 2016, now i have the bootloader

BL_G935FXXU1APB4_CL7162483_QB8489947_REV00_user_low_ship.tar.md5,

in your opinion which files should i flash and where do i have to put them in odin?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] thrutheeyes:
how to install / use this? Got DRK ENG binary problem on my G930f
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Frug01:
What are these files for?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] kt.thegioiso:
I think it used to enable "USB Debungging" or enable ADB
[Samsung Galaxy S7 Edge Guides, News, & Discussion] tahsinahmed:
Please help me. i flashed the file G930F_XXE1APBG_ENGROOT.tar on my Galaxy S7( SM-G930F), but then my phone can't boot anymore.

My phone only boots again after i flashed the original fireware to my phone.

But without engroot i have no root access
[Samsung Galaxy S7 Edge Guides, News, & Discussion] asadnow2k:
will this work on andriod 7.0 or 7.1 ?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] steevelehoux:
g935w8 flash my bootloader lack of battery, no power no sound no bootloader no recovery and is not detected by windows, i search solution for sdcard bootable.

Ideas? sdcard not working ap bl cp csc +pit
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Trimixer:
Just dealt with this, in my case it had something to do either with the charging port, moisture, I think, or letting ithe battery get that low while flashing? Idk, it just turned off, and zip, dead. No responses to plugging in to anything including chargers. stuck it on a wireless charging pad, the lightning bolt came on in about 5 minutes, let it go overnight, good to go. Hope this helps, that's a really crappy feeling. I wonder how many warranty returns are because of this, I thought I was concrete bricked
[Samsung Galaxy S7 Edge Guides, News, & Discussion] psyalemao:
Hi everyone, have a G930F. It appears that G930F_XXE1APBG_ENGROOT is for MM 6.0.1 only. I read that we need to toogle on developer options, usb debugging and OEM unlocking first. I found this link

https://mega.nz/#!rsZi0L4R!B_U6iXaOd-tX9aJRIrCZsrcocC9QeCp4hDIrRWF_OT0

its G930FXXE1BPG3 full firmware with eng boot appears to be a little newer than APBG and found this site too

eng-root.firmware.ir/sm-g930ffd

it has eng boot for another phones like G935F. The site says is for nougat 7.0 G930F would like to know if anyone have tried it yet or if it is real?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] xmanz:
Any info please.. If I've got it correct your locked s7 edge qualcomm got the fm unlocked by carrier? I and quite a few have unlocked qualcomm g9350 but the fm that is in the chip is not activated. Can anyone shed. Light on a possible solution eg something from your rom to flash. Thank you hope ? to hear some opinions…
[Samsung Galaxy S7 Edge Guides, News, & Discussion] RazzaMataz:
When i got my samsung repaired under warranty they replaced the motherboard,

Samsungs rep asked me if id rooted it, i asked why he said they woukd charge £30 extra if rooted.

How comes people belive rooting voids warranty?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] ayamgoreng:
depend on what country.

on some country they can voids your warranty if your knox=0x1
[Samsung Galaxy S7 Edge Guides, News, & Discussion] McRuli:
Hi, I burn this ENG_BOOT_G935A__PJ2.tar

Result > SoftBrick.