Are you saying I should kill the adb daemon before starting a root attempt, or are you recommending restarting during the pause after the first reboot? If so, I'm not sure how I can break through the running script to kill the daemon. If I can get that far, of course I can restart it, too.
My guess is you're saying that I should kill the adb daemon before trying to root (step 5).
In any case, I'll do a fresh stock flash and start over.
---------- Post added at 09:58 PM ---------- Previous post was at 09:46 PM ----------
WTF!!! SuperSU is present and Joey Krim says I'm rooted. I have utterly no idea why this worked despite the error message which, I assumed, said I didn't reach being rooted. Very, very strange... NTL I got where I'm wanted to go, even if I haven't a clue as to why I'm there.
Yes, it's better to start running the script with no adb deamon running, since the script will invoke it on its own.
On top of Task Manager > Processes make sure there are no running ADB.EXE
If there are, right click on it and kill it.
Just follow this, don't skip anything, follow it step by step, trust me it works!
p.s. The only thing I can think of about your weird issue, is that you may have more then one phone plugged in to the same pc, and while the script ran fine on the S7, the other one could have thrown those strange errors. Anyway, next time make sure there's only ONE phone is plugged in, all adb's stopped, and follow the step by step instructions. A similar situation has occurred to me in the past, and it was really frustrating trying to figure out the root cause. Now, this may or may not be in your case, nonetheless it's worth taking a look at.