yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
I allowed SuperSU to do a binary update and lost root. I uninstalled SuperSU and went through re-rooting with Odin (same process as used originally). Root Checker says I failed (as does TI). SuperSU gives a binary occupied message and Root Checker says Root User Account Error - Error: stderr: null, stdout:null, exit_value: 0

Now what?

---------- Post added at 07:13 PM ---------- Previous post was at 06:27 PM ----------

ADDED: This is an unbranded phone. NTL, flashing a carrier's stock firmware before re-rooting is at least tolerable. Is any carrier's firmware better or less bloated than any other's?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] jruka:
When ssu updated and I lost root all I did was push root.bat thru adb and I will not update ssu
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
Push root.bat? Where would I push it to on the phone? Is it executable on the phone? FWIW, I've run it twice (on my PC), with and without SSU installed - no root.

IIRC, some versions of SSU caused problems with rooting, but I don't remember the details.

Also, would any of the SSU replacements help?

Finally, any thoughts about flashing stock firmware from some carrier (phone is unbranded) and then rooting? The question here is would that leave the phone branded?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] jruka:
So if when you reboot you get the padlock you are still on the eng kernel. If that is true uninstall ssu and then follow the same procedure to push ssu back to your phone with your pc. Open adb folder that contains root.bat file and run it. All I do is double click it from that location, I believe it's version 2.74. The latest ssu has issues. It's version 2.82 I think. But yeah all I did was uninstall, reinstall and wipe davlic partition. And then cashed partition and back to normal
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
OK, now I understand the push part. That happens in root.bat.

The bat file just doesn't get the job done, and I don't understand what causes that.

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd /d G:/Samsung/S7/Temp

G:\Samsung\S7\Temp>dir
Volume in drive G is Downloads
Volume Serial Number is 580B-B1A0

Directory of G:\Samsung\S7\Temp

05/29/2017 06:17 PM <DIR> .
05/29/2017 06:17 PM <DIR> ..
07/12/2016 11:55 AM 6,677 launch_daemonsu.sh
07/12/2016 11:24 AM 378 root.bat
04/10/2017 11:57 PM 3,304,879 SuperSU-v2.76-S7QC.zip
06/27/2016 07:51 PM 6,427,286 SuperSU-v2.76.apk
07/12/2016 11:22 AM 100,663,296 SuperSU-v2.76.img
07/03/2016 02:33 PM 396 supersu.cmds
6 File(s) 110,402,912 bytes
2 Dir(s) 374,903,934,976 bytes free

G:\Samsung\S7\Temp>root.bat

G:\Samsung\S7\Temp>adb wait-for-device

G:\Samsung\S7\Temp>adb shell mount -o rw,remount /system

G:\Samsung\S7\Temp>adb shell mount -o rw,remount rootfs /

G:\Samsung\S7\Temp>adb shell rm /data/su.img 1>NUL

G:\Samsung\S7\Temp>adb shell mv /data/su.img /data/su_old.img 1>NUL

G:\Samsung\S7\Temp>adb shell rm /data/su_old.img 1>NUL

G:\Samsung\S7\Temp>adb push SuperSU-v2.76.img /data/su.img
1537 KB/s (100663296 bytes in 63.924s)

G:\Samsung\S7\Temp>adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh
failed to copy 'launch_daemonsu.sh' to '/system/etc/launch_daemonsu.sh': Read-only file system

G:\Samsung\S7\Temp>adb install -r SuperSU-v2.76.apk
1550 KB/s (6427286 bytes in 4.047s)
pkg: /data/local/tmp/SuperSU-v2.76.apk
Success

G:\Samsung\S7\Temp>adb shell 0<supersu.cmds
touch /system/xbin/su
chmod 0755 /system/xbin/su
chcon u:object_r:system_file:s0 /system/xbin/su

chmod 0700 /system/etc/launch_daemonsu.sh
chcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh
if [ `cat /system/etc/init.sec.boot.sh | grep daemonsu >/dev/null 2>&1; echo $?` -ne 0 ]; then
echo '/system/etc/launch_daemonsu.sh' >> /system/etc/init.sec.boot.sh
fi

sync
reboot

root@heroqlteue:/ # touch /system/xbin/su
touch: '/system/xbin/su': Read-only file system
1|root@heroqlteue:/ # chmod 0755 /system/xbin/su
chmod: no such tool
255|root@heroqlteue:/ # chcon u:object_r:system_file:s0 /system/xbin/su
chcon: '/system/xbin/su' to u:object_r:system_file:s0: Read-only file system
1|root@heroqlteue:/ #
1|root@heroqlteue:/ # chmod 0700 /system/etc/launch_daemonsu.sh
chmod: no such tool
hcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh <
chcon: '/system/etc/launch_daemonsu.sh' to u:object_r:su_exec:s0: Read-only file system
ec.boot.sh | grep daemonsu >/dev/null 2>&1; echo $?` -ne 0 ]; then <
> echo '/system/etc/launch_daemonsu.sh' >> /system/etc/init.sec.boot.sh
> fi
root@heroqlteue:/ #
root@heroqlteue:/ # sync
root@heroqlteue:/ # reboot

G:\Samsung\S7\Temp>

The problem seems to be directories I need are treated as RO. That leaves me wondering about the firmware flashed by Odin. Everything looked good - got PASSED - but...???
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] jruka:
Did you ever get root back?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
No. See the log from the last attempt.

I don't know why, but the SSU part seems to not work. That is, SSU doesn't install correctly.

I cleared the cache after uninstalling SSU. It didn't make any difference.

BTW, looking at the log again, there's a line reading: "chmod: no such tool". That seems a little odd. Of course I have BusyBox installed, but without root, I assume it's not useful.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
Here use this. First unroot.bat then root.bat. This should fix the issue of breaking root after updating SU.

https://www.androidfilehost.com/?fid=745425885120736331

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
Thanks for the information!

Two questions before I pull the trigger on this:

The file is marked as being for the S7 Edge, (935), I have a non-Edge (930). Is this a problem?

Does this do an FDR or at least do a data wipe?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] freeop:
Question 1. DO NOT use the (935) version. Use the (930) one. Here's the 2 files and make sure you select the 930 tar file.

"Download engineer-rooted boot image appropriate for your model of phone:

Samsung_G930x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7) (MD5 hash 948A01ECCF280828DFD13AC366F6FE85) (credit markhaines1985)

Samsung_G935x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7 Edge) (MD5 hash F3B7C5E4E8F6B31235ED0125371EB1F6) (credit markhaines1985)"

Question 2. Yes it will completely wipe your phone just like day one and you will have to enter all the information as if you just bought the phone.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
No worries - I seriously doubted the Edge version would work, but better ask before, not after.

[/...]

Sigh... some days you're the dog, some days you're the tree. Look like this is my turn to be the tree. [/grin]
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
It will work for either the flat or edge. The unroot.bat will wipe your dalvik cache so it will take some time to boot and rebuild the dalvik for your apps, but it won't wipe any of your data.

Sent from my SM-G935V

---------- Post added at 03:22 PM ---------- Previous post was at 03:13 PM ----------

He was asking about my file I posted to fix root after breaking root by updating SU. Read a few posts back to see the conversation please... The file I posted will fix root for flat or edge, thanks.

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] freeop:
Sorry about that. That is what I get for being subscribed to these threads. Got an email with him asking about the 735 or 730 so thought he was asking about the eng.img.

Thanks for correcting my mistake.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
FYI 930 vs. 935 [/grin]

---------- Post added at 12:05 PM ---------- Previous post was at 12:02 PM ----------

Krog18 - gotit. Great thanks! [/two thumbs up]

I'll do this as soon as life stops interfering with my plans. [/<-- faint humor?]
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Qarie:
Lost root access by accidentally updating binary

I was put in a situation where i defied the holy grail of not updating the binary and doing so despite me knowing not to do it from the back of my mind.

I lost root access, and i'm trying to figure out if there's any quick fix to this silly mistake of mine, or if all i can do at this point is redo the whole root process :eek:
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] K2adir:
OP needs to update the first post.

Dear Verizon user's if you update to 7.0 after rooting using file files provided,

you need an updated Stock ROM as well.

I hope the OP will actually say that there.

this is why I somewhat hate Xda, nothing gets updated on the first post.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] jruka:
Just uninstall ssu and thru adb repush "root.bat"

---------- Post added at 07:07 AM ---------- Previous post was at 07:05 AM ----------

I did the same thing on accident. Soon as I reflashed and wiped cashed and davlic partitions I was good as new
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
Is there an unbranded stock ROM for the S7 (not Edge)? Or, where can I find one?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] gunz.jones:
The U firmware is unbranded as far as carrier stuff.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
Got that part. The question is, put another way, where do I look for the U stuff? Google?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Qarie:
A couple of issues i've ran into...

in recovery mode, when i try to click into update from adb, it says it's disabled (Which isn't the case bc i have it enabled in developer option).

I've somehow got it to work by using the root.bat while the phone is on, but now SuperSU says that the "SU Binary occupied". any suggestion?

any thank you for the guidance so far.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
Looking in the usual d/l sites, keep seeing region codes (all for the US). Most marked as belonging to a carrier. But four seem to be... I don't know what. They are LRA, XAA, TFN, and TMK. Are any of these useful for unrooting my phone before re-rooting it?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] jruka:
Trying to remember but all I did was plug phone into pc, open folder with adb, Fastboot and the root.bat .... double click root.bat , it will do its thing in a command prompt window, phone will reboot when done......
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] IcyArctix:
Help, Bootloop!

What do I do to restore my phone after it has been stuck in a bootloop? Or how do i get out and make it normal again?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] orgulloso4202:
Go to download mode and odin a stock tar file.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] loganbeck14:
Also don't quote the entire op please
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] IcyArctix:
Still Stuck in a Bootloop

My Sprint Samsung Galaxy S7 is stuck in a bootloop after running the Odin Tar file, and when I tried using the stock, it said it failed and had a failure. Can anyone help please?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
bump

Still looking for unbranded firmware to return an unbranded S7 back to stock, long enough re-root. If branded firmware is OK, then I'll install it. I want avoid backing into branding when I very much don't want it.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
Any of them should work, but the USA (XAA) version is officially the multi-carrier CSC. Hope this answers your question.

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
Great thanks - I think XAA gets it done, then.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] thrgk:
I am currently on QA4 stock, I was rooted but then returned to stock. For some reason I cannot take the latest system update even though I'm on stock, it kept failing. Is there a way I can manually update to the latest build ?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
Odin your QA4 bl then try to take the ota again.

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] thrgk:
Is there a place to download all the build ? I don't have my QA4 anymore
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
G930V

https://www.androidfilehost.com/?w=files&flid=160197

G935V

https://www.androidfilehost.com/?w=files&flid=160357

The latest is QC9 so you could odin that, just make sure you use all 4 files if you want to be able to accept future OTA's.

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] thrgk:
Ok so just flash all four files in Odin and should be all set ?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
Yup. Also FYI, if you choose home csc, it won't wipe your data, but if you use the regular csc it will.

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Spy_64:
is there a QC9 root, or do we have to stay on the older version?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] orgulloso4202:
Follow any of this to return to stock. Will help with bootloader also

https://www.androidsage.com/2016/03...galaxy-s7-and-s7-edge-full-firmware-download/

http://www.droidviews.com/android-nougat-firmware-on-sprint-galaxy-s7-s7-edge-sm-g930p-g935p/amp/
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] tmathews1988:
Tried this root method and failed. Verizon SM-G935V i probly should have researched a little more ive never had any issues with any root methods. Boot Loop i tried the restore stock i get this error on my handset.

SW REV CHECK FAIL : [about]Fused 4 > Binary 2,

Odin gave me this.

<ID:0/006> Added!!

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

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

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

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

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

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

<ID:0/006> SingleDownload.

<ID:0/006> boot.img

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

<ID:0/006>

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

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

Any ideas on how to return to stock to try root again?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] orgulloso4202:
Check my post above. One of the links is for variant
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
This method is for MM only so assuming you want to be on rooted MM, see my post about 5 posts back and download the PI3 firmware from the link for the G935V and odin that.

If you want rooted N, download QC9 firmware from the same link and odin that. Then go here to root N.

https://xdaforums.com/tmobile-s7-edge/how-to/heres-how-rooted-nougat-s7-edge-g935t-t3567502

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] tmathews1988:
935V isnt listed in that link...

---------- Post added at 11:46 AM ---------- Previous post was at 11:37 AM ----------

That may work i need to figure out now how to get back to stock... this might end up turning into a lost or stolen phone.... :/
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
The link is right there. Just use the one for the G935V. There's no reason you can't do this, it's extremely easy. Download whichever firmware version you want from that link, extract it, plug the phone into your computer, in odin add the 4 files in their respective slots, click start.

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] ecm77:
Samsung Galaxy S7 Model SM-G930U will not root

At the Odin step in this process it completes successfully but then the phone just reboots over and over. I have to flash to stock firmware to get back into the phone. Every time I try and root it this happens. I searched online for hours and cannot find any info on this. Any ideas?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
It's because this method/kernel is for Marshmallow and you're likely on Nougat. Go here

https://xdaforums.com/tmobile-s7-edge/how-to/heres-how-rooted-nougat-s7-edge-g935t-t3567502

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] ecm77:
I am on Android 6.0.1 stock and my phone is the SM-G930U version of the Galaxy S7. I cannot find any specific info online about why my phone just reboots over and over after a successful Odin root. So frustrating!!

PS: I have stock Android 6.0.1 on there now and I do not want to go to Android 7, I only want to gain root access to the device.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
Delete
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] tmathews1988:
Oops my bad i was looking at a different post... thx dude.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] ecm77:
I don't follow. In Odin I am adding the "Samsung_G930x_QC_Rooted_BOOT.TAR" to the AP section, which is what the instructions say to do. There are no other files in that zip file for the other sections in Odin. That successfully completes and then the phone just keeps rebooting. Now if I download the firrmware there are files in there for every section of Odin (BL, AP, CP, CSC) and that is how I am able to flash back to stock 6.0.1. But rooting it using just the AP section (Samsung_G930x_QC_Rooted_BOOT.TAR) gives me the boot loop.

I must be misunderstanding something.

The instructions say:

--------------------------------------------------------------------------------------------------------------------------------

Download engineer-rooted boot image appropriate for your model of phone:

Samsung_G930x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7) (MD5 hash 948A01ECCF280828DFD13AC366F6FE85) (credit markhaines1985)

Samsung_G935x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7 Edge) (MD5 hash F3B7C5E4E8F6B31235ED0125371EB1F6) (credit markhaines1985)

Note that this download is a .TAR file and while it looks like an archive, you should not extract its contents.

Power off the phone. Turn it back on while holding Home, Volume Down, and Power buttons at the same time to enter download mode. Press Volume Up to confirm that you want to flash data to the phone.

Open Odin. Click 'AP' and select the appropriate AP TAR file:

Samsung_G930x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7)

Samsung_G935x_QC_Rooted_BOOT.TAR (any Samsung Galaxy S7 Edge)

Still in Odin, click 'Start' to flash the engineer-rooted boot image and reboot the phone.

---------------------------------------------------------------------------------------------------------------------

Well that all works great, no errors, except the phone just reboots over and over at the Samsung logo and I can never move on to the rest of the procedure. So I have to re-flash back to stock and go back to square one, which leaves me unrooted still.

I appreciate the help by the way!!
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] zwroberts1:
Unroot Not Working For Me

Odin gives me a fail before it even really gets started (log below).

"<ID:0/004> 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/004> Odin engine v(ID:3.1203)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

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

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

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

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

<ID:0/004> SingleDownload.

<ID:0/004> boot.img

<ID:0/004> recovery.img

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

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

<ID:0/004>

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

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

<ID:0/004> Removed!!"

The phone itself gives a SW Rev check fail after that (in the download mode).

So I thought to myself I'd just keep it in the meantime and just restart it and use it for now, but low and behold I now can't leave download mode. If I restart regularly, I'm brought back to a software update failed screen, and if I switch to recovery mode (? vol up + home + power) I've wiped the cache partition as another forum suggested, but then going to reboot system now... That restart brings me right back into recovery. I currently have the phone off charger in hopes the battery dies and something changes then.

I'm also downloading the very very latest firmware update for the S7 Edge in hopes that maybe Odin will like it a bit better than this one (VZW_G935VVRU2APE1.zip).

Any ideas? Any solution that gets me a working phone again, I'll definitely make a donation to your PayPal! Thanks in advance for any help!
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] billdauterive23:
Dude you need the latest firmware you are trying to flash an outdated bootloader the latest is bootloader 4
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] zwroberts1:
I was trying to use the latest according to SamMobile. Wound up doing some back digging and found a post that linked this post (https://xdaforums.com/showpost.php?p=71133959&postcount=27) worked perfect! Did the Pit thing also just for safe measures too.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] revile:
Is it possible to use the return to stock method to downgrade from N to MM? I'd like to flash a MM stock firmware but the device has OTA Nougat.
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
Yeah, if you're on Verizon, just ODIN either the PI3 or PH1 firmwares and you'll be back to MM. Make sure you include the BL file as well since you're changing versions.

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
After lot of putting off until the day after what I could put off until tomorrow, I finally reverted to stock MM on my G930U. It's an FDR even but I'll accept it because the phone was clearly turning to trash (lost SD access, couldn't re-root, general aggro...). Fine, I'm waiting for the 139 apps to reload. The plan is to re-root MM and go on about life as I know it. And while I'm waiting, I get a notice that VZW is pushing a Nougat OTA. This is a U phone, but I use VZW. Anyway...

Is there a N root for the 930? I see that Edge (935) N can be rooted. Does N rooting exist for the 930, also?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] Krog18:
Yup, there's a Nougat eng kernel for the 930 and one for the 935. The link is in the OP of this thread

https://xdaforums.com/tmobile-s7-edge/how-to/heres-how-rooted-nougat-s7-edge-g935t-t3567502

The zip for the eng kernel will contain the kernels for both versions so just use the one for the flat and you'll be good.

Sent from my SM-G935V
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
Great thanks! [/two thumbs up]
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] RBEmerson:
FYI I followed the instructions accurately AFAIK and I'm currently bootlooping. I tried going back to stock MM and wound up bootlooping through recovery.

No blame attaches, just a heads up. :)

---------- Post added at 12:48 PM ---------- Previous post was at 12:02 PM ----------

[/deleted]

---------- Post added at 01:12 PM ---------- Previous post was at 12:48 PM ----------

I really shouldn't be allowed near any phone without adult supervision.

I tried flashing Nougat and wound up in a bootloop. I tried returning to MM and wound up in a bootloop. It helps to notice Odin was still fetching the Nougat tars (last folder it used). [/finger gun to head]

So I'm back to stock MM. And having to rebuild the effin' phone more time. Haters gotta hate and I'm hatin' the stoopid Nougat files.

I know this is OT but... VZW is pushing Nougat at me. I could suck it up and accept that, but I have no idea if I can root it or not. Advice?
[Verizon Samsung Galaxy S7 Guides, News, & Discussi] DynamiteRave:
The links for adb, odin, and the tar files weren't working. Does anyone have any updated links?