yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] mattkilla420:
I decided to go back to the Stock firmware of PH1. Like you said I was nearly all the way there but I was stuck dead in the water last night and just decided to go back with all the buggys. I did exactly those instructions ,said the Odin process works fine. I successfully flashed supersu to the phone and then went to Play Store and downloaded flash fire. No matter what I did Flashfire would not load up and had an error message that it could not acquire root. That's when I got stuck trying to update the binaries for superSU. There has to be something in the process that I left out or skip because I have the custom padlock on the opening splash screen. But just to note even after I flash my stock firmware PH1 I still have that custom padlock opened up? I thought that was supposed to go away when you were on stock firmware it did on the S6.

Anyways I may try the process again in the future I was just a bit worried because I got my phone brand-new at 6 p.m. last night and by 8 p.m. I had already buggered it up. This is all after I some how bricked my S6 yesterday. I've tried to Odin several firmware packages to the phone but it gets stuck in the setup wizard trying to activate the phone number every time. Can anyone in here shed any light on that it is a Samsung 920v?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
You just need to reboot the phone a second time and the custom padlock will go away.

As for your g920v......as long as you can get into download mode then you're not bricked.

I'm sure you probably did factory reset and wipe cache from recovery both before and/or after odin your firmware.

There's also a Verizon software repair assistant that might help.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] wrestlsimp:
I am having trouble getting my GS7 unrooted. I rooted, installed SuperSU, and decided it is not for me. I tried to click "unroot in superSU" but that says "failed". I then used odin to flash over the stock firmware found on this forum but when I click start it shows "auth failed". I have tried a few different Odin version (I am running as administrator).

Are there specific settings I need to change my phone to?

I have OEM unlock on as well as USB debugging.

Here is error in Odin (latest version)

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> emmc_appsboot.mbn

<ID:0/003> lksecapp.mbn

<ID:0/003> xbl.elf

<ID:0/003> FAIL! (Auth)

Any input/help is greatly appreciated!
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
Unroot via supersu wont work. You need the correct firmware for odin. There's a couple places you can download, but the op is outdated and any firmware you find there won't install. The revision number needs to be same or higher. Sammobile and updato.com are good places to start but depends on phone variant.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] meh3884:
has anyone been able to figure out how to successfully update after unrooting and returning to stock? the updates still fail on t-mobile trying to update from PG1. unroot and return to stock was successful, but updates fail. tried unroot steps a second time and an extra factory reset but still no dice.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
Can you find the pia or pk1 firmware online and odin yourself? Or maybe the ota will work from pia if you can only find that firmware.....and then go to pk1 from the pia via ota. Now I'm confused. Lol
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
Lmao I'm getting confused now too. All these different firmware versions are a huge pia! Lol

---------- Post added at 01:40 AM ---------- Previous post was at 01:38 AM ----------

I have an idea, but not sure if it's the case here. Is it possible your bootloader is a different version than your firmware? Try to odin stock again, but this time include the bl if you didn't and then attempt another ota. Maybe the different versions are blocking the ota.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] meh3884:
So finally got it to work. I tried one more time to do the return to stock steps, except this time I selected the HOME_CSC file for CSC instead of the regular CSC. I'll be honest I don't know what that file was for or if it's even for sure what worked, but now I'm happily updated to PK1 over OTA. My next try was going to be flashing PIA and seeing if that worked.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
I was thinking the same thing with the BL file too, but didn't mention it because I thought he was already on/coming from the same version he was trying to odin. Plus, I don't think the Home_CSC was the solution to OTA's but I've been wrong before.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] SantinoInc:
What do you guys think about root on this phone? Is it totally worth it? Is it not worth it because it's draining battery and making the phone too hot? Is it not worth it because you can't take the newest OTAs?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
I need to have root because of my ocd.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] SantinoInc:
Thanks for the reply. Are you happy with the performance of your rooted phone as compared to it when it was stock
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
Never really used it before rooting......originally bought an s7 active but once got it home realized the polycarbonate screen scratched easily and was design flaw....even though it makes screen break proof it increases scratch ability, and I don't use screen protectors, my ocd.

Anyway, that's another story, and so after that I had read very in depth about the s7 rooting, v15 fix, etc.....the entire threads. So I took the s7 active back to at&t and exchanged for the s7 and put it in an otterbox commuter and now it's very active with a very durable screen, and I don't use screen protectors, my ocd.......and so I never used the phone before rooting. I brought the phone home and immediately rooted and fixed.

But, on the flip side, we had a two for one deal on the s7's from at&t and my kid got one too and we've been comparing each to the other for months now, and find very little difference in operation. Batteries last about the same and both will get warm at times. Kids phone is updated to pi2 I think....maybe something higher by now......mine is at ph1.....where it is likely to stay until I get a new phone. I have gone back to stock when I had put the Echoe Rom on but didn't like it enough to keep, so I rolled back to ph1 because that was the latest at the time and what I was on anyway. I may try stang5litre rom and if I get into trouble after that and have to go back to stock I may look for latest firmware at that time. For now im happy though and so far none of the apps I use are requiring updated firmware. If that starts happening then I would have to update firmware too at that time.

I'm sure this is more than you asked but I'm chillin with nothing better to do.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] SantinoInc:
Lol, I appreciate the lengthy response. I think you just inspired to take the ROOT plunge!

I just feel that my phone is infected with shiit if I leave all this garbage bloat ware on it. Even the U firmware that is supposed to be relatively bloat free has too much crap on it for my liking.

Can you tell me what carrier you're on? Also, did you debloat on your own or did you use the script in the OP?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
No debloat......v15 fix only. At&t g930a ph1 firmware. Once I freeze a few things in titanium backup and then stop all updates from playstore apps......I still get a notice, from somewhere?? Not sure where though, that an update is available for whatever app......so I can download at leisure and update what I want. So all the extra bloatware stuff doesn't bother me since I can control what runs, when it runs, etc....basically then, I have a couple of bloatware folders in the apps section that hold all the junk I rarely, if at all, use. I only keep the apps I regularly use on the main phone screen and the apps I use sometimes on the second screen.

You may want to do some research on how your phone operates with root, because from what I've read over the last several months, not all variants are equal and act the same as one another under pressure.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] alaindesjardins:
Best part about this guide is where you return to stock.

Now my phone works great again! I wish having root didn't introduce so many problems but I realize now I can live without it for the sake of performance and stability.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] dtroup64:
Nice to see a fellow Mainah in these forums...
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] alaindesjardins:
Likewise. I'm a bit salty with my root attempts lately, following everything and trying to have what I had with my note 4 but I've just had nothing but bad luck. Thinking about getting the pixel from Google seeing as how Verizon locked the bootloader on their version.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] mattkilla420:
Sad but I totally agree
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
Totally understand and agree......I would take stability and performance over root too, had I needed to make that trade.....luckily not....
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] SantinoInc:
Thanks for all the feedback. Looks like the vast majority agree that root isn't worth it on this phone. This really sucks! This is a flagship phone owned by millions of people and Samsung screwed things up for us!
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] dtroup64:
Not sure I agree that Samsung screwed things up for us. They made a terrific phone. We decided to purchase it knowing full well there would probably be no development. There were other routes to take, but we took this one. This is still the best phone I've ever owned.

Now that I see where the Pixel is headed, I'll take a long and hard look before my next upgrade, however. But chances are that with the terrific technology Samsung puts into these, I just might stay with them.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] SantinoInc:
IDK if I totally agree with you on this. Yes, it's still a top tier phone but Samsung is really losing their luster. After the Note 7 debacle they lost a lot of credibility with the masses. This whole locked bootloader thing seems to be a trend that is continuing for the Android phone manufactures. So I guess I can't blame Samsung because the other manufacturers are doing the same thing. I was looking at a LG V20 but their root process is even more ridiculous than ours. I just feel that "ROOT" is going the way of the dodo bird. They are making it more and more difficult.

Honestly all I really want is the ability to delete apps I don't want to use. Hell, even coming from iPhone they give you more flexibility on what you can delete and they have ZERO carrier bloat.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] dtroup64:
Package Disabler doesn't do the trick for you?

I only have apps that I want on my phone at present.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] SantinoInc:
You know, I was going to buy it from the Play store but it seems that all the recent reviews are saying the guy is a sellout and it doesn't really disable all that much anymore. If you're personally using one of these package disablers can you advise which one you're happy with? I don't want to waste money on something that a lot of people don't seem to be too happy with.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] nyr2k2:
Those of us that tinker with our devices are a very small portion of the market overall. I don't think many manufacturers or providers really care about helping the root community.

For your average consumer, a stock S7E, maybe with a package disabler, is the best phone money can buy. That our variant is locked down sucks for us, but in no significant way diminishes the quality or appeal of the phone.

---------- Post added at 08:11 AM ---------- Previous post was at 08:06 AM ----------

I don't see any real difference between the handful of apps out there. I did use BK Package Disabler, which was just fine for disabling everything I wanted. Once I rooted however I just went back to using good old Titanium Backup.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] SantinoInc:
So you're happy with your phones performance after root? I think I'm just going to have to jump in there myself and give it a shot.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] nyr2k2:
Yeah, overall I'm satisfied. What I've found is that if I root, run the fix package, freeze some apps with TiBu, then slap on an L-Speed profile and Greenify, I'm good to go. If I start tweaking too much beyond that I run into problems. Do the basic fixes and enjoy the phone. And hey, if you're one of the unlucky ones who has issues, it's easy to go back to stock.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
That's where I'm at too, the basic fixes after root are enough for me. I don't even go as far as you with greenify or lspeed and still have a perfectly good working phone. From what I've been able to deduce from reading is that it's very carrier dependant.....and not really sure why. But if you're on at&t, then I would have to say you're good to go with root.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] ChinDaChin:
Thanks for the excellent guide [MENTION=1599591]psouza4[/MENTION] !

Confirming I'm running AT&T Galaxy S7 PF2 engineering ROM. Phone does take much longer to boot (the whole Samsung, and AT&T logo). It also gets hot, then afterwards it cools off. I have noticed that Touchwiz and the Android system crashes upon reboot - this may be entirely my fault as I dug through some files and made some changes (manually added wifi SSIDs)

Overall experience- :good:
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] dclutter1:
I installed the Verizon Flat S7 rooted image over the Nougat beta and it bootloops.

I tried to fix it by odin-ing back to stock (BL, AP, CP, and CSC) and that fails and won't boot.

<ID:0/003> Odin engine v(ID:3.1203)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> emmc_appsboot.mbn

<ID:0/003> lksecapp.mbn

<ID:0/003> xbl.elf

<ID:0/003> FAIL! (Auth)

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Phone screen says:

SW REV CHECK FAIL: (aboot)Fused 4 > Binary 0

[1]eMMC write fail: aboot

I've tried every version of Odin I can find... Not sure what to do now :/
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] PRL77:
Yeah, man, totally rocking. All good. Well, mostly good. My only gripe is this new expanded notifications that just started after rooting. Is it possible to disable notifications from expanding by default? I can't even "collapse" them with two fingers. They start to collapse but go back to "expanded" when let go. Looking to prohibit expansion by default. Don't mind it being expandable manually but not by default without touching it.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
Which stock firmware are you trying to odin? You probably need to find the same version as you were originally on. There is also a Verizon software repair assistant that may help.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] dclutter1:
I'm using the version from the OP of this thread.

I flashed the N update zip through recovery when that came out a couple weeks ago so, not sure what version I was on.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
No going backwards once on a certain revision. Find the latest revision and odin that....at least ph1 or pia or one of those.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] dclutter1:
Thank you! That's what I needed. PH1 flashed fine and I'm back up and running.

For anyone else looking for PH1 Odin files, I found them here:
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
Nice work.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] FusionX:
I'm on the verizon variant. After the initial root process, the phone was laggy as hell (I'll admit that I didn't install any of the fixes from the OP)... But, I just flashed supersu installed flashfire and then installed a custom rom and the phone has been just as good as it was before root. I also created a backup with flashfire that I backed up with ADB to my PC. So, I can flash new firmware, re-root and restore my backup. Honestly, with flashfire it's not much different than using a custom recovery except now I haven't tripped knox. One thing to note on flashfire since I've done this on two phones now is that it takes FOREVER to request root access and then after I granted it I had to force quit the app and re-open it for it to become functional.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] surffdog:
Is there a newer updated version of Samsung_G935x_QC_Rooted_BOOT.TAR?

Hi, and thanks for all the information on rooting a Samsung Galaxy S7 Edge Snapdragon. Mine is Verizon, SM-G935V on firmware G935VVRU4API3, my question is there a newer file than the Samsung_G935x_QC_Rooted_BOOT.TAR as today, 12/7/2016?

---------- Post added at 01:02 PM ---------- Previous post was at 12:56 PM ----------

Would you be able to give instructions on how you did your flash?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Soooperstar:
I'm cool with it. I use the beta tester lspeed with govtuner embedded. I don't really have any lag.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
As far as I know there's only one engineering kernel available. The original may have been updated, but if so, it's never been leaked.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Ummmmmmm:
I tried to return to stock following this guide using Odin prince on my G935P running the latest update to return to the stock sprint s7 edge file provided and I definitely matched up the Ap, CP, and CSC files correctly. It said auth failed and did not revert to stock. Now I have a screen on my phone saying "An error occured while updating the device software. Use the emergency recovery function in the smart switch pc software".

When I load up smartswitch on my win10 pc it says my device is unsupported even though I am running the latest version, have the proper usb drivers installed, and have the windows media package installed.

Can anyone please help?

Edit: Error I get on my phone says "SW Rev Check Fail : [System]Fused 3 > Binary 1"

And in Odin it says:

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin engine v(ID:3.1203)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> boot.img

<ID:0/003> recovery.img

<ID:0/003> system.img.ext4

<ID:0/003> FAIL! (Auth)

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] ChinDaChin:
Hey [MENTION=1599591]psouza4[/MENTION], could you take a look at this thread - http://xdaforums.com/att-galaxy-s7/help/data-toggle-button-t3508836 ? Have you seen a solution for this?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] surffdog:
After rooting, strange thing at top of homescreen!

Hi, after rooting successfully my Verizon SM-G935V on firmware G935VVRU4API3, I had no issues and still don't but one really annoying one that shows something at top of my homescreen (I don't know what to call it). Also, when I scroll, it leaves a line blue/red squiggly line where ever I touch the screen.

Please see screenshot, maybe you can advise on how to get rid of it besides, re-flashing original firmware. Any help, suggestions would be great. And thanks for all the hard work.

Also, any chance of an update for Samsung_G935x_QC_Rooted_BOOT.TAR?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] JustAnotherAndroid:
Try using a regular version of Odin, I had the somewhat the same problem but mine said "module dismatch failed" and it worked, or try download the files from somewhere else, that also helped before i had the first problem
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
You got to find your current firmware to download because the pe1 firmware in the OP will no longer work because you can't go backwards from the newer updates. Look for ph1 or pia or pi3 or whatever. Also odin princecomsy is only for AT&T phones and only for engineering kernel so use Odin 3.12 or something.

---------- Post added at 01:17 PM ---------- Previous post was at 01:09 PM ----------

No update for engineering kernel. As for the blue line try cache wipe from recovery. The stuff over notification line might be something in developer options....look around at those settings. Cache wipe and reboot can fix a lot of stuff.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] nyr2k2:
Princecomsy version is definitely not only for ATT. I use it on my Verizon variant. My understanding, and what's stated in the OP, is that princecomsy is WORSE for the ATT variant.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
OP is wrong. I have AT&T and used Princecomsy's odin. If you read the Princecomsy thread that started the engineering kernel it states it's for at&t.....it's an AT&T thread.

I suppose that's good it works for verizon....I don't think it was made for verizon but so it works that's good. I guess I could have used different wording. The main thing is if going back to stock then don't use Princecomsy......it was made for the engineering kernel.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Ummmmmmm:
I found multiple firmware version here: https://samsung-firmware.org/download/Galaxy S7 edge/7l82/SPR/G935PVPS2APG1/G935PSPT2APG1/

I took 8 hours to download that one and it failed... how do I know which of the suggested similar downloads at the bottom is the version I need?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] saf4xdadev:
First off it depends on carrier. If Verizon check updato.com or sammobile.com and if other need to Google. Also check threads here on xda as there are at&t and u and others with downloads available . Then check your settings /about Phone and find your firmware ......will start with g935 or g930

.....look at the last 3 digiletters and then that's what you search for, g935xxxxxxxph1 for example. The numbers got to match or the last three need to be higher. Hope helps.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Jeremi187:
The firmware you are trying to use has the old boot loader. You need to be on g935pvps4apj2 or g935pvps4apk1.

Here is a link for each.

https://mega.nz/#!X1xUCYJQ!R3xoSZmo0vtPwUsQvtamitl1SPu5YG4aKIvHCuwuig0

http://www.sammobile.com/firmwares/download/114379/G935PVPS4APK1_G935PSPT4APK1_SPR/

I would go with the first one. Downloads much quicker. G935P is Sprint and you are looking at Verizon firmware.