yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Oh yes im 100% sure it is a bootloader thats not the question if u look there you will find more funny hints to knox and stuff.

Im also 95% sure its ment for the s7 edge and it should* boot on it.

The thing i was trying to find if its really is a leaked* bootloader or some regular released one and if it is what can it help us with
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
What about changing firmwares, I believe that you can change your firmware if you can take into account the differences between them? I think this has been done before?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Hmm... Now that's the real question here then!

By the way, did you look into the mysterious ENG_Root file?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Well yes downgrading is not uncommon if you want to test the bootloader download the firmware FA60_G935FXXU1API2 from updato or sammobile extract it and replace the boot.img and aboot.bin with the "leaked" ones cross fingers and see if it boots. If it spits a red fail it either means it had detected a bootloader downgrade attempt or the bootloader signature is invalid (meaning that the aboot.bin is fake and not sammy produced)

My other theory would be if its just the released kernel and bootloader and the claim that its a leak would be a lie and if you get me the boot.img and aboot.bin from that firmware i can compare those two

---------- Post added at 10:21 PM ---------- Previous post was at 10:17 PM ----------

Its not mysterious at all actually its quite simple. Its an auto rooting kernel (which were most popular on lolipop days) it basically is the stock kernel with supersu injected inside the ramdisk so when you boot up the phone it has root acces and btw that build date is older seems it was build in february and was ment for an older build (could still work tho)

That if indeed it is legit

Those were mostly kicked out of the rooting scene bcuz they got rly unpopular and overly complicated as cf-auto-root existed
[Samsung Galaxy S7 Edge Guides, News, & Discussion] jrkruse:
I'm really not sure what your trying to accomplish here. It doesn't matter if that stuff is eng kernel or bootloader, the G935F is not the same phone as the American versions. Different processors and partition tables. It would be like trying to use s6 kernel on an s7. It isn't going to work
[Samsung Galaxy S7 Edge Guides, News, & Discussion] ProtoDeVNan0:
Don't get excited guys.

So called "engineering firmware" is only used as a test firmware to check if all sensors are working etc.

IT WON'T RESET YOUR KNOX.

It also has capabilities of fixing some parts of Your phone if You mess up flashing roms etc. But nothing else. Most devs on XDA in S7 Edge section have it, and it's useless. Angelo even posted it, debloated without engineering tools on it.

And even if You flash a full version with bootloader, modem and other files, nothing will happen. Once You change Your knox to 0x1 there's no way to change it back to 0x0.

It's kinda like test apps to check sensors + debug info about boring stuff. You can check Your sensors by using secret codes app from playstore and finding there a hardware test hidden menu. That's what the firmware has in it. Also You can read serial numbers of Your phones components. Nothing else.

So there You have it guys. Your curiosity is now gone.

If anyone wants, text me on telegram to see some screenshots of the firmware.

BUT! Since that's Samsungs private property I won't share it with anyone.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Hmm.... I thought that the Engineering firmware would allow you to root and make further system modifications without tripping Knox, I never thought that it would reset it because of the fact that Knox is regarded as an Efuse and so can not be reset as it seems to be a hardware component on the latest Samsung phones.

If I am wrong will you please tell me as I self-profess to be new to flashing and rooting on Samsung devices.

If I somehow mislead anybody then I am deeply sorry. I just thought that we can make a No Knox Root method if we had confirmed Engineering files.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
I was actually thinking about using the bootloader in conjunction with the method developed at this thread (Link: XDA link) because as far as I understand, they could not achieve permanent root because of DM-Verity and how it kicked in at every boot and reset the phone, (i.e. they needed to disable dm-verity but could not do so without violating Knox, which would defeat the purpose, a Catch-22 situation) so I thought that if we can disable DM without violating Knox via Eng bootloader we can make a No Knox method for the Exynos chipset. Once again, I self-profess to being quite new to rooting & flashing, therefore, I ask you to please tell me if I am wrong. :)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Ok first of all i did it:

We won't need the bootloader as it overly complicated stuff.Yes none of the files will reset knox but the kernel as its an engineeringkernel does leave specific exploits open (which are used for testing)

What i did was to check the validity of the source bcuz i don't have an s7 edge i downloaded the s6 edge plus eng kernel and flashed it on my own device 100% stock also i used a modded version of odin

the device surprisingly booted and when i checked it does say -eng in kernel version in status (confirming its an engineering kernel)

All i did next was use the same root.bat (with its respective files) from the qualcomm s7 root thread and yes it had root.

HOWEVER as i have my knox already tripped there is no way to check if it endeed doesnt trip knox

So as the s6 edge plus eng kernel from that website works theres no reason for me not to belive the s7 won't

EDIT: I tried flashing the bootloader (aboot.bin) but it spit an rev check fail meaning that bootloader downgrade protection has been triggered if the bootloader woudnt have been signed by samsung it wouldve spit another error
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Woohoo! Now that is great news! :good: :highfive:.

Now about the Knox, well, it seems that the Qualcomm Root does not trip Knox, so I think/hope that the Engboot would also not trip it!

Also, I assume you used the [MENTION=5028474]princecomsy[/MENTION] version of Odin?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
the qualcomm root is from the exact same place as our engboot and yes i did use princecomsy odin

Thing is if indeed it doesnt trip knox (and it doesnt for the qualcomm s7) have you seen how many devices are there?This could literally be a gold mine for rooting

Now we just need a tester for any of the devices there (exynos would be nice) to check and see if knox is being tripped.:D :highfive:

This rly got me excited
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Hmm... I really believe that we should, first of all, download all of the Engboot files from the site and then upload them to Google Drive, so we have a backup in case that site goes offline!

Wow! I am literally jumping with joy, here, we just have to see if it does or does not trip KNOX.

Edit: I may be just a tad too overexcited! :o:highfive::victory::fingers-crossed::D
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
[MENTION=7554803]Random04[/MENTION] [MENTION=6185853]Rainbow_Dash[/MENTION]

So, I tested both G935F_PH3 and G935F_PI2, neither worked. Both of them flashed successfully through Odin by princecosmy and Odin 3.12.3, but neither would boot. Phone gets stuck at the S7 edge bootup logo, and doesn't go any further.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Have you tried going into recovery and wiping cache/factory reset?

Edit: Can ADB detect your device, if so, have you tried to see the adb logcat?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
Don't want to do a reset and lose all my data since the S7E is my primary phone right now, but doing a cache wipe didn't help.

I'm back on my stock ROM, with all my data intact.

Since flashing it does NOT void KNOX (mine is still valid), someone else who's willing to do a factory reset can try it, it's not harmful and you can always just flash the Stock ROM if it doesn't boot.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
So i guess the only solution would be to downgrade to that firmware (see my older posts to see which one) and try on that.

and holy sh1t if it didnt trigger knox thats great
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Hey [MENTION=6185853]Rainbow_Dash[/MENTION],

Can you please confirm the link that I have written in the first post?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Well, It seems that we have (confirmed) officially signed Samsung files then! This is Great!
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
I thought S7E didn't allow downgrades, hence why I thought this kernel wouldn't work since the PI2 one is from the October ROM and I'm on the December ROM.

Sent from my SM-G935F
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
By the way, can you post your firmware version and AP/CSC/PDA, so we know it doesn't work on that one.

Side Note: A handy way to know your firmware and CSC/PDA etc. is by dialling *#1234# which should open up a version window which tells you that. (Just FYI) :):good:
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
I'm on official BTU 6.0.1 with the December Security patch.

Sent from my SM-G935F
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
The reason why it odin fails at downgrading is actually that the package contains an older aboot than the one currently on the phone.If you unpack the firmware delete aboot, cm and repack into a .tar it should* work

(even tho most of the times it works as is)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Well, It seems that I am in luck, as I still am on the October Security Patch!
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
Shady, very shady.

No sign of PH3 or PI2 anywhere on SamMobile or updato.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Ok then you could try it just make sure you have stock rom handy. Also make sure you have both oem unlock and usb debugging ticked. The file y need to flash is engboot not sboot. Good luck

---------- Post added at 02:20 PM ---------- Previous post was at 02:18 PM ----------

Could that mean it was supposed to be packed in a firmware that was never launched? Lemme have a look
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Wow! If that works then it would mean that we have an Official No Knox Root Method here!

By the way, the S7E firmware comes in different parts now (for some reason).

Side Note: (Noob Question) What exactly is cm?

Edit: I have also searched for the ROM you mentioned for the sboot and it also does not seem to be available on Sammobile or Updato!
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
I also checked the Eng_Root file and it seems to have an Samsung Firmware Update certificate in it, which is signed by evan.lee@samsung.com
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
1) Googling G935FXXU1APH3 brings up very shady results. There's constant mention of the word 'combination files', and a reference to the firmware mentioned above, but the file size claims to be around 600 MB only, which seems very small for a full Odin flashable ROM.

2) Call me a noob, but at the end of this text it says 'test-keys', is it not supposed to say 'release-keys' usually?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
If i remember correctly combination files are those that are supposed to be used in jtag.pffff......ur right this version was never launched.The only thing we can do now is find a firmware around the same time (usualy older) the kernel was built and pray that boots.

Funny tho how the edge plus engboot booted on the latest firmware no issues and bet thats older
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
[MENTION=7554803]Random04[/MENTION] has an October firmware, he could try the PI2 ENGBOOT since that's also an October firmware.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Raz12:
Okay ah I have a Galaxy S7 Edge Snapdragon 935U ON PI3 AT&T I hate the engboot on it because it makes the phone laggy and hot but i want root so bad. I'm willing to try or learn or flash something to take one for the team. Is there anything i can do ? .. Cause i really want a better engboot so i can have root without lag and hotness and battery drain.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
You could try flashing the latest firmware with flashfire and enabling everroot (basically flashes supersu)

That should get you rid of the ancient engboot and root the latest kernel
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Hi Raz12,

Sounds like you need to follow the fixes provided here XDA Thread.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
So just to confirm, the leaked Engineering kernel is for a firmware that isn't released to the public?

Which then means they're useless to us since nobodys phone runs that firmware.

Crap. :/

Sent from my SM-G935F
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Not rly its just more of a gamble. We need to find a older firmware that runs on those engboots.The latest firmware for the edge plus run a engboot no problem for some reason the latest one doesnt work on the s7 edge.Id say flash a firmware older than the date the kernel was compiled and see if it boots.Not much else that can be done. Meanwhile im gonna go flash stock this engboot is laggy af

Im gonna keep looking on those websites perhaps i could find a newer engboot
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Don't be disheartened, as the files are signed by Samsung, we may be able to run them by flashing an older firmware (example: PI1). And then flashing them to the device. This could work! By the way test_keys and release_keys could not mean anything as the test_keys can also indicate that it is an Engboot firmware, obviously not intentioned for public release.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
You should try the standard fixes for eng boot files, Googling something along the lines of "eng boot fixes" should help you find an How-to guide to fix mostly all issues with the Eng boot. :) :good:

(Try downloading a cpu governor modifier and try changing the mode to interactive)
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Raz12:
Wait so using flash fire and enabling ever root within flash fire will let me root my phone without using engboot ? or i would still have to use that because i can't flash without being rooted. and those fixes really fix the slowness and phone being hot. Have you tried this ? i didn't know that was the case because it seems like everyone is sorta getting the same issue.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
1. Using Flashfire and enabling everroot should trip your Knox. :(

2. The fix for the eng boot for the Snapdragon firmware was released ages ago! I can't try them as I am on a Exynos chipset and there is till now no No knox tripping method for Exynos (we are trying to make it in this thread :) ) The Snapdragon variant, on the other hand already had a No knox tripping method using the leaked Eng boot files for the Snapdragon chipset. So that file is supposed to be the fix for the Snapdragon Eng boot issues. :):good:
[Samsung Galaxy S7 Edge Guides, News, & Discussion] nitrous²:
You guys should check this thread before doing any more work http://xdaforums.com/galaxy-s7/how-to/knox-exynos-root-method-via-engkernel-t3423438/page20

It might be that what you're trying has already been done without success.

EDIT: Apparently and IINM, we're already a step further.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Well, I think there is still 1 unanswered question here. Will running the root.bat trip knox after flashing the Engboot?

I am fairly sure that it will not trip Knox as the people over at the Snapdragon thread could do this without tripping Knox. :):fingers-crossed::good:
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
I doubt that will trip knox as supersu is systemless
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
Yup, basically what Rainbow said.

I flashed both PH3 and PI2 Engboot kernels and although they didn't boot, KNOX was not tripped.

Sent from my SM-G935F
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Depends i actually booted an engboot kernel on my edge plus and ran the root.bat from the qualcomm s7 root thread and it worked. My only question now is if it trips knox.

Even if we would fail for the s7 edge at least it can be done for the s6 edge plus and other devices
[Samsung Galaxy S7 Edge Guides, News, & Discussion] MeltdownSpectre:
[MENTION=6185853]Rainbow_Dash[/MENTION]

First post of this thread:

Sent from my SM-G935F
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Raz12:
okay thanks i will try out when i get home. i didn't know they found a fix for it.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Ah, Thanks Nitrous•2 for reminding me! Yes we need to check the bootloader! If anybody would want to try the bootloader, then please do but first READ this thread completely and know that No one would be liable for any damage to your device, just to recap, the bootloader is SIGNED and seems to be an actual working bootloader for the S7 edge, but we are not able to check if it is an Eng one or not.

Also, If I remember correctly through my reading of the thread they needed an signed modified eng boot, which may very well be the Auto Rooting kernel (ENG_ROOT) that is available to us!

Notes on the EngRoot: It actually seems to have an certificate file (in the sbin) from Samsung so should NOT trip Knox.

Edit: I have added some screenshots. :) :good:
[Samsung Galaxy S7 Edge Guides, News, & Discussion] ProtoDeVNan0:
I'm starting to feel worried about this thread.

1. What happens if You flash non samsung signed thing on a engineering firmware? Well. Nothing. It simply will tell You that to avoid tripping knox it won't boot.

2. If 99% of REALLY experienced devs have it, then why didn't any of them make a non triggering root method?

3. Most people do not care about non tripping knox root method but about knox reset

And the engineering kernel that You have guys, is simply a kernel that well. Isn't a lot different than a normal kernel.

But if any of You manage to get full engineering firmware including all files. Then after flashing anything not signed by samsung it will simply show You that Your signature has been modified and Your phone won't boot to avoid triggering knox.

Real way to cheat the knox triggering mechanism?

Sign CF Auto Root with Samsungs signature, and make sure that somehow the phone won't treat those files as a knox triggering stuff.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] nitrous²:
I can't imagine devs expecting the demand of a KNOX free root method being so low that they didn't bother developing one. So a good question you have there.

That of course would be awesome. But companies are not known to share their private signing keys to the public.

EDIT: Being sarcastic. Rereading and it didn't translated well over.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Well.....How about this ENG_Root file (Link: Google Drive Link
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
erm........how do you even........

first of all lets be realistic a knox reset will never exist,and a rooting method that doesnt trip knox would be nice to have to the very few that do care about it.

also the eng kernel does have a few differences from a normal one if it wouldnt have how do you think that the qualcomm s7 got root.

We are not looking specificaly for a non knox trigger root method for the s7.For example i did get root on my s6 edge plus with an engboot kernel and the root.bat the qcm s7 guys used and that shouldnt have triggered knox.

And lol applying samsung signature to cf-auto-root?wtf it uses md5 checks and more overly complicated stuff that would never be possible not to mention no one even knows for sure how knox works
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Furthermore, even if we somehow get the private key of Samsung, they could just change it and force all users (who do not have this disabled through changing the system files) to do a compulsory/automatic update. :rolleyes: :(
[Samsung Galaxy S7 Edge Guides, News, & Discussion] nitrous²:
Very unlikely, thus, no point in discussing this and instead try to focus.

In the meantime and in case someone overlooked this:
[Samsung Galaxy S7 Edge Guides, News, & Discussion] ProtoDeVNan0:
Okay. I think our conversation is over. Not gonna waste my time lol. But still ask some devs on telegram about it. But sure. Good luck :)

---------- Post added at 05:29 PM ---------- Previous post was at 05:18 PM ----------

Uhm.. thanks for being open minded. I love that! But it was kind of a theory how we could do that. But we won't cause we obviously don't have Samsung keys :p

And yes. That's exactly what I'm trying to say. Engineering firmware contains nearly identical kernel to normal kernel. It just simply has some security checks disabled as well as it uses 1 jan 2016 security patch, and that makes the kernel easy to root. But tripping knox works still the same way as with normal kernel. If the signature will be modified knox will trip itself. Although that engineering kernel should have security and disable booting until normal signature is restored.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] VSB:
[emoji299] [emoji299]
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Hi Nitrous•2,

Thanks for pointing this out,

Umm... [MENTION=6185853]Rainbow_Dash[/MENTION] can you confirm or deny if DM-Verity is enabled or disabled?! Because if it is disabled on your phone, that would be some strong evidence suggesting it would also be disabled in the S7 kernel! And as we already know thanks to [MENTION=5063250]murtaza02[/MENTION] that the kernel does not trip KNOX!

However,

As an alternative if this doesn't work, we also seem to have a Modified Boot.img available (Eng_Root), which I have uploaded before. As I said before, it seems to be signed by Samsung!

The question here is that "Is the Samsung Cert file valid? And Is DM-Verity disabled in this file?"

Side Note: Is there a way to check if DM-Verity is enabled or disabled by looking at the filesystem?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Huh and i thought i wouldve had time to check out some note 7 ports.Gimme a few mins gotta flash stock and that kernel

Also that certificate file doesnt prove that it has been compiled by samsung the only way to check is to flash it and see who built it
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Random04:
Thanks [MENTION=6185853]Rainbow_Dash[/MENTION] for your quick reply and support!
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Ok so noob question time : How do you check if dm-verity is enabled or not?

If i shell into the phone i can navigate /system and /data with no issues from both adb and terminal.This means that its disabled right?
[Samsung Galaxy S7 Edge Guides, News, & Discussion] nitrous²:
Don't think so. Currently on stock, non-rooted KNOX 0x0 (December Security Patch PLB) build and I can navigate to /system and /data via adb and various file explorers with no issues.
[Samsung Galaxy S7 Edge Guides, News, & Discussion] Rainbow_Dash:
Running as root and being able to mount as rw and then copy move and delete files from system partition? doubt it