[Verizon Samsung Galaxy S7 Edge ROMs, Kernels, Reco] Delgoth:
[MENTION=1949695]jrkruse[/MENTION]

I'm sorry if you've already answered this question in this or one of your other modified roms.

Please direct me to it if so. But how exactly is the firmware modified? Is it because you use the U Firm's Bootloader & Modem with the Verizon AP & CSC? Or did you make other modifications under the hood that the signature verifications still agree with?

I'm asking because I'm trying to wrap my head around everything that can actually still be done to our device besides a custom Recovery. I have so many theories. I know that sounds crazy but I literally have about 30 pages (single spaced in MS Word) of stuff written about the internals of the v3 and v4 BL Software Revisions that I haven't posted in my threads.

I know a S*** Ton about all kinds of different topics of the newer Android Firmwares. But I'm not an expert on any one field. And I've never made up an entire ROM before. I would say I'm quite the budding developer. I have all (most) of the knowledge needed to do all kinds of things, but I've yet to actually DO them.

I know it's a lot to ask how do I take the stock ROM and turn it into a copy of your Hybrid ROM. But really, what did you do to make this?

If you're up for a decent read, I can post or PM to you, all the R&D/Conversations I've had that led to all the development we did on the Exynos7420 board. When I tested our Root Console on an unrooted S7 Edge, it worked as well since both the Exynos & Snapdragon CPU's use the Arm64-v8 Arch. Currently the G935's U Firmware can be downgraded back to the Revision 4 'PI3' from september in order to take advantage of the Greyhat Root Console.

The research I did for my Original Greyhat Root thread for the G925V applied fully to everything DirtyCow. Half of that thread I deleted yes, But the initial post is still intact. A lot of what I posted had implications into too many exploits and at the time before Christmas last year we saw Hundreds of Exploits patched. Too many of my posts in my initial thread put exploitable code into too many hands to use in the wrong way. And I had found myself a target of someone online. I've made a bunch of posts over the last 8 months in regards to my observations about DM-Verity and Combination Firmwares. It was all applicable, but too many people are too quick to dismiss what I was saying and did not actually investigate. 2016 Saw More Security Exploits Patched than ANY Year to date. And a large majority of those exploits were exploited on the Galaxy S6 Line of Products, the Exynos7420 Mainboard. Which is why the International S7 Lineup on the Exynos Arch is easily developed for. Most of the same problems persist. The U.S. S7's use the Snapdragon Processor for just that reason. But even using different hardware, the same software problems persist.

You were even able to Root CID 15 Galaxy S5's using Combination Firmware Files. (Thanks btw I knew it was possible but didn't know to dive deeper into the rabbit hole). I basically said that back in October of 2016, Combination Firmwares disable Verity along with its problems even without an ENG Kernel. But not many people know of or about the capabilities of the Factory Binary. And I didn't know which step to take after that. Even you probably know more than I on that subject, given what you've done with the S5. I'm still just a jack of all trades. I have more of a width, than a breadth, of knowledge. And I can't find the guides I need. But I know you know the details I need to know. Because your work proves it.