yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] billa:
ADB should only be stopped (2-3 times back to back) at the beginning of running the Root.bat, no need to stop it during the process.

The idea here is to start with a clean machine with no adb deamon running at all.

As far as the script, nobody had to modify it, it works just fine as is.

I can only suggest to reflash it again with stock UES4BRA1, do a full factory reset from the recovery menu then proceed to step 2.

Not judging your abilities, but it seems that some small detail is somehow being missed during the steps.

Pay close attention to where it says enable adb/oem etc, it's very important to do it multiple times EXACTLY as instructed.

Try again, because nobody else had this issues, so the question is more like "Don't understand, what am I missing here?" ;)

Looking at your log...

Installing Root

adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Read-only file system

adb: error: failed to copy 'supersu/init.sec.boot.sh' to '/etc/init.sec.boot.sh': couldn't create file: Read-only file system

adb: error: failed to copy 'supersu/launch_daemonsu.sh' to '/etc/launch_daemonsu.sh': couldn't create file: Read-only file system

It clearly shows that your system is "Read-only file system" which could indicate that the eng-boot didn't flash properly.

Again, my only suggestion is go back to step 1 and follow through 5, but don't do any workarounds, do it exactly as written to a "T".
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
the adb offline problem (although there are several google hits on the problem) turned out to be nothing more than making sure the S7 screen was unlocked (not enough to just be booted to "Swipe screen to unlock" - gotta do the swipe and PIN). That goes into the bit bucket.

Something odd happens when I flash XAA-G930UUEU4BQD2-20170428165520.zip. The boot splash screen still has the padlock icon. When flashing back to stock (step 2.), I use CSC_OYM_G930UOYM4BQD2_CL10860000_QB13198947_REV02_user_low_ship_MULTI_CERT.tar.md5 not HOME_CSC_yada yada Also, if there's a PIT file around (see step 2. in the how-to), I don't see it. It's not in the .zip - just the bl, ap, cp, and two csc files.

Step 3. the "block out boot loops" step, runs with the expected mix of success and fails. A puzzle shows up here. After step 2., there's the padlock in the boot splash. After step 3., it's gone. Why is that? Do I care?

Step 4., the ENG flash. I'm using the patched odin, which hasn't shown any problems. I'm guessing that Samsung_G930_QC_Eng_Boot_Root_v2017-03-01.TAR goes into odin's AP spot. Unlike step 2., where odin does an md5 checksum check for bl, ap, cp, csc, it doesn't do anything with the ENG tar. Just for curiousity's sake, I tried putting it in BL. Clicking BL showed me the same file. (I did

not

hit start) Questions: does Samsung_G930_QC_Eng_Boot_Root_v2017-03-01.TAR go to the AP slot? Should odin do any checking on this file? If the "read-only" error points to the ENG file not being properly flashed, what did I not do, or do incorrectly?
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
I deleted the work space (folders and files) I was using, made sure I had current files, replaced the old workspace with folders Step2, Step3, Step4, Step5. The zip(s) appropriate to the step go in the folder. I Tweaked Root.BAT to start with adb kill-server to avoid problems with a running adb daemon, and to save the time needed to open a command window and type cd /d... and adb... Yes, there is a running adb server when Root.BAT starts running.

This is the ENG file name: Samsung_G930_QC_Eng_Boot_Root_v2017-03-01.TAR - where does it belong in odin (BL, AP, CP, or CSC)?

I stepped through the folders and still get "read-only" at the end of step 5. Remember I was able to root this phone earlier but had to re-do it after adding the SIM.

I'm out of ideas.
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
I tried 2-5 again this morning (might as well do it when I'm awake and not doing an all-nighter). I was obsessive about letting the kernel settle (over 45 min. wait). All files came from the links in the how-to. I put each step's files in their own folders. Each folder got an unzipped patched odin and adb. I did an adb kill-server before each batch file ran. I verified the developer USB settings were right. I verified that the RSA stuff for the PC was set to "always allow" - ditto for MTP. I used a different USB port and a different USB cable.

Aside from step 5, the bat file step outputs look OK. The two uses of odin produce PASS.

Fail. "Read-only file system".

In step 4, where should the ENG file be opened in odin? Is there an .md5 version to get a checksum test?
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] freeop:
Place the ENG file in the AP section of Odin.
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] billa:
No idea what's going wrong with your process, nobody else has reported any issues... what I did notice is that you're not using the BRA1 firmware as in the instructions, not sure if that has anything to with it. Try again with the BRA1 firmware and see what happens. The eng-boot had to be in the AP tab, and there are no md5 checksums in any of the files.
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] reasonz20:
How do I navigate to supersu file using cmd because I have no idea how use it?
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
Gotit - that's what I thought. TNX

---------- Post added at 07:58 PM ---------- Previous post was at 07:27 PM ----------

I'm confused - isn't step 2 where a stock UES4BRA1 is flashed? I haven't done an FDR from recovery. I'll do it with this iteration of trying to root.

You're talking about the settings in Developer options, right? I check them before every time I use a .bat file. In any case, I'll recheck during this iteration.

Trust me, "Don't understand, what am I missing here?" is running around and around in my head, and has gone around often enough to leave groove there. LOL

Step 2 - I'm using ...\Foo (instead of ...\Step2) only to be 100% sure I'm using BRA1:

Step 3:

Step 4:

Step 5:
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
Step 2 - flashing from the files shown earlier and doing an FDR didn't change anything. Step 3 looked reasonable - a lot of lines get "not installed", a few get success. Step 4, using ENG from AP passed. Once again, step 5 failed.

Waiting for the phone to be connected ...

adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
Device connected ...

Removing FlashFire ...

Removing SuperSU ...

Removing Fingerprints ...

Resetting Lockscreen Security ...

rm: /system/priv-app/Chameleon2: No such file or directory

Removing Any SuperSu Images ...

Removing Knox Stuff...

Preparing For Root ...

Phone will reboot and continue do not unplug...

Waiting for the phone to reconnect ...

After device is reconnected and recognized by the computer
Press any key to continue . . .

Device reconnect ...

-------------------------------------
- 1 Install FingerPrint Fix -
- 2 Do Not Install FingerPrint Fix -
-------------------------------------
Please make your decision: 2

--------------------------------------------------
- 1 Install Root No Tweaks -
- 2 Install Root With CPU Governor Conservative -
- 3 Install Root With CPU Governor Ondemand -
- 4 Install Root With CPU Governor Interactive -
- 5 Exit -
--------------------------------------------------
Please make your decision: 1

-------------------------------------
- 1 Install SuperSU Root -
- 2 Install Magisk Root -
- 3 Install Systemless Root -
-------------------------------------
Please make your decision: 1
Installing Root
adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Read-only file system
adb: error: failed to copy 'supersu/init.sec.boot.sh' to '/etc/init.sec.boot.sh': couldn't create file: Read-only file system
adb: error: failed to copy 'supersu/launch_daemonsu.sh' to '/etc/launch_daemonsu.sh': couldn't create file: Read-only file system
Success
Success
chmod: /system/xbin/su: No such file or directory
chcon: /system/xbin/su: No such file or directory
chmod: /system/etc/launch_daemonsu.sh: No such file or directory
chcon: /system/etc/launch_daemonsu.sh: No such file or directory
If you get this error in above script
adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Text file busy
during install please reboot and try again
Press any key to continue . . .

After flashing the stock system, there's a brief blue screen with a spinning arrow in the middle of the Andy figure (no more 3D Andy - bummer) and something about a system update. I've seen this before (with 3D Andy and a blue ball spinning away), while flashing other phones. Is this update event a problem? Since I'm using the stock BRA1 files, I assume this event is normal. Or is it?
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
Decided to bring my S7 back to stock. I flashed BRA1 (step 2 files) and then opened up recovery. At the bottom of the screen, I found this...

No Support SINGLE-SKU
Supported API: 3

# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC

What is VZW doing here??? The phone is unbranded and unlocked. Is this mess being caused by the VZW SIM???

(BTW the screen really does show "Appling", not "Applying")
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] billa:
It's normal to see the carrier's name of last sim card your have or had inserted, which brings up another suggestion, do not insert a sim during the flashing and rooting process to avoid any interference (not a critical issue but do it anyway). You can insert it after it's all done and verified, at which point it's normal for the "unbranded" firmware to boot into a blue screen for auto-configuration.

Look, this is my last message about your issue, all I can suggest is to ALWAYS start the rooting process with a clean stock flash, AND a full factory reset form recovery, then proceed to the rest of the steps. Keep trying, and you will succeed ;)

Last, but not least even though you see xbin read-only error, yet your phone is rooted, well then just leave it at that I guess.

Not sure what you're trying to do by navigating to the supersu file, can you describe your aim please?
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
For this iteration, I downloaded everything all over - except BRA1. Updato has me throttled back to about a day to d/l. The version I used is 1 day old and came from updato.

I pulled the SIM/SD carrier altogether - nothing in the phone. BRA1 flashed as usual. I did an FDR. I let the full setup process run to the end. In Developer I enabled OEM, USB, and cleared the RSA keys.

I used File Explorer to browse Phone to be sure MTP was working. I ran the fresh security+OTA script. It failed because this was the point where "allow this computer access this device" finally showed up. After the script end, I approved the request and checked the "no need to ask again" box. I ran the script a second time and it ran as usual: lots of files not found, a few found.

I flashed Samsung_G930_QC_Eng_Boot_Root_v2017-03-01. odin reported PASS. After rebooting, I left phone alone for 45 minutes.

I verified the OEM and USB options in Developer and ran Root.BAT from Samsung_G93x_QC_CF-SU_v2.82_2018-02-01_SSU+MGK. I chose no fingerprint fix, root w/ no tweaks, and SuperSu Root. The same read-only messages came back.

I checked OEM and USB options in Developer and ran Root.BAT from Samsung_G93x_QC_CF-SU_v2.82_2018-02-01_SSU+MGK. I chose no fingerprint fix, root w/ no tweaks, and SuperSu Root. The same read-only messages came back.

SuperSu 2.82-SR5 Root S7 was installed. It reports permission denied to access /sbin/su. FlashFire is present but, of course, reports it can't run - not rooted.

I used a terminal to look around, in some of the directories involved. There is not hint of what should be there, installed by the step 5 script.

All of the above brings me to thinking ENG didn't flash as it should. Even though odin says it did (PASS). Something's gone wrong here but I don't know what.

RootChecker says the phone's not rooted and it lists all the possible directories where SuperSu should be. SuperSu isn't in any of them. supersu/init.sec.boot.sh and supersu/launch_daemonsu.sh aren't in /etc/. There is no supersu in /etc. Trying to use SuperSu doesn't work. FlashFire doesn't work (no SuperSu to grant permission). I can't invoke su from Material Terminal (no SuperSu to grant permission). If the phone's rooted, nothing I've tried confirms it.

I'm not a total idiot about phones and Linux. I've been using Linux, one way or another, from prior to the 1.0 kernel, when Linus was very hands on. What I don't have is understanding the hacks, tweaks, and general magic to get around roadblocks in Android.
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] kimber45:
Just looking back through your posts(in case i decide to re-root and have issues) and noticed you said you used odin to flash the eng kernel, but did you use the prince comesy(sp) version? Just a thought I had, maybe a dumb one.
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] Craz Basics:
Yes! You have to use prince comsy for eng
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
I think I've finally found out why the ENG flash doesn't grant root. This is no longer an unbranded phone!

On the box the model number is SMG930UZKAX. That's echoed by the sticker on the back of the case. The box says unbranded. But... Phone INFO *Samsung* says the phone's Product Code is now SM-G930

ZKAVZW

- note the missing U

I could well be wrong about this, but it seems that VZW has hijacked my phone. Very early in this process I tried rooting and IIRC actually got there. The SIM wasn't in the phone. When I put it in, the phone wouldn't do anything except show a window from VZW about using the SIM (I wish I'd written down the message). My guess is that somehow, adding the SIM (from VZW) ultimately branded the phone.

In an effort to at least change the CSC, I flashed BRA1 with CSC code TMK (USA/no carrier). The VZW SIM was not in the phone. I did an FDR from Recovery. Phone INFO shows no sign of TMK. VZW remains in the product code and firmware CSC code. Is this phone now a VZW branded phone? Can it be unbranded?

Input?
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] Craz Basics:
Why is everyone having trouble now? What security patch are you all on? Works fine with January patch
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
That's my other contender for why things stopped working. According to About Phone, my phone's security patch level is dated Jan. 1, 2018.
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] reasonz20:
Not sure what you're trying to do by navigating to the supersu file, can you describe your aim please?[/QUOTE]

Thanks for the reply, I found what I was looking for.
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
It depends on which OP you read here. The posts right at the top of this thread like PrinceComsy, but the BillA OP (two OP's from two OP's in one thread? Too weird)... the BillA how-to specifically calls out odin3.12.3_patched - which is not the PrinceComsy odin. The PrinceComsy version has "PrinceComsy" added to the banner at the top of the odin window. The patched version doesn't. BillA includes the unpatched odin3.12.7 in his OP.

I tried odin 3.13, too. It showed a bunch of warnings in Korean and English, and didn't fix the problem with ENG not rooting my S7. Otherwise, I didn't see any results differences between the other odin versions. I'm sure there are some meaningful differences in them, but none of them changed the ENG problem.
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] solomon702:
Hey fellas is anyone else having problems downloading the file G935UUES4BRA1_7.0.zip or Samsung_G935U_UES4BQL1_v7.0.0.ZIP

Both somehow miraculously end up stopping at 88% downloaded....tried like 4 times each...anyone else having this issue???
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] reasonz20:
What is the order to flash back the AT&T S7 EDGE to stock? I mean BL, AP and so on?
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
Whoa - looooong quote - better to cut&paste what matters. I'm just sayin'...

If your question amounts to "I'm going to use odin to flash something. In what order do I fill in BL, AP, CP, CSC?", the answer is "it doesn't matter". I usually load them in in order, BL first, then AP... That's just me. Plug your phone in, and don't mess with it once odin repearts the port the phone it tied to.

Odin does a checksum test on each file. AP, because of its size, takes longer than, for example, BL. There is no MD5 checksum for the ENG file; odin will not check that file.

At the end of the run, let odin sit for a couple minutes after the last step, to be sure it's finished or the phone is rebooting. If the phone is rebooting, wait until that's done, and wait some more. Odin may have more work to do. Interrupting a flash is a very, very, very bad idea.

---------- Post added at 10:05 AM ---------- Previous post was at 10:00 AM ----------

Short answer: nope.

Who are you downloading from - what site?
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] Craz Basics:
Eng will not root lol; Eng just allows you to run a adb daemon as root so you can push files via adb to root your phone. Look for the root.bat
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
OK, odin w/ patch flashes/loads Samsung_G930_QC_Eng_Boot_Root_v2017-03-01 and odin says "PASS" at the end. Presumably the flash really worked.

Let's guess the rooting comes apart during Root.BAT in Samsung_G93x_QC_CF-SU_v2.82_2018-02-01_SSU+MGK

@echo off
echo Waiting for the phone to be connected ...
echo.
adb wait-for-device
echo Device connected ...
echo.
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount rootfs /
adb shell mount -o rw,remount /data
echo Removing FlashFire ...
echo.
adb uninstall eu.chainfire.flash >NUL 2>&1
echo Removing SuperSU ...
echo.
adb uninstall eu.chainfire.supersu >NUL 2>&1
adb uninstall com.topjohnwu.magisk >NUL 2>&1
adb shell rm -r /data/s7startup >NUL 2>&1
echo.
echo Removing Fingerprints ...
echo.
echo Resetting Lockscreen Security ...
echo.
adb shell rm -r /system/priv-app/Chameleon
adb shell rm -r /system/priv-app/Chameleon2
adb shell rm -r /data/biometrics >NUL 2>&1
[/ SNIP out lots of rm's ]
adb shell rm -r /data/data/eu.chainfire.flash >NUL 2>&1
echo.
echo Removing Any SuperSu Images ...
echo.
adb shell rm /data/su.img >NUL 2>&1
adb shell mv /data/su.img /data/su_old.img >NUL 2>&1
adb shell rm /data/su_old.img >NUL 2>&1
adb shell mount -o rw,remount /data
adb shell rm /system/xbin/su >NUL 2>&1
[/ SNIP out lots of rm's ]
adb shell rm /system/etc/install-recovery.sh >NUL 2>&1
echo.
echo Removing Knox Stuff...
echo.
adb shell rm -r /system/priv-app/Chameleon >NUL 2>&1
[/ SNIP out lots of rm's ]
adb shell rm -r /system/app/UniversalMDMClient >NUL 2>&1
echo.
echo Preparing For Root ...

All of this seems to work. All of the mount -rw's work. The only error is removing Chameleon2 - I hope that's OK. Everything seems to run as it should.

[/ WHACK off choices leading to this code - no fingerprint patch, no governor tweaks, SuperSu, not Magisk or systemless]
:SYSTEM
echo Installing Root
adb uninstall com.topjohnwu.magisk >NUL 2>&1
adb uninstall eu.chainfire.supersu >NUL 2>&1
adb shell rm /data/su.img >NUL 2>&1
adb shell rm -r /system/etc/launch_daemonsu.sh >NUL 2>&1
adb shell rm -r /system/xbin/su >NUL 2>&1
adb shell rm -r /system/bin/su >NUL 2>&1
adb push supersu/xbin /system/
adb push supersu/init.sec.boot.sh /etc/
adb push supersu/launch_daemonsu.sh /etc/
adb install -r SuperSU.apk
adb install -r flashfire.apk
adb shell chmod 0755 /system/xbin/su
adb shell chcon u:object_r:system_file:s0 /system/xbin/su
adb shell chmod 0700 /system/etc/launch_daemonsu.sh
adb shell chcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh
echo If you get this error in above script
echo adb: error: failed to copy 'supersu/xbin\su' to '/system/xbin/su': couldn't create file: Text file busy
echo during install please reboot and try again
pause
@echo off
goto END
[/WHACK off huge chunks of irrelevant script]
:END
echo Rebooting
adb shell reboot
exit

(see the full Root.BAT for the missing code)

The push's fail. The installs say Success. The chmod's and chcon's fail.

If the script can't push in supersu, then rooting won't or hasn't happened. Is what was flashed in the ENG broken? Is something else broken?
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] Craz Basics:
Eng shouldn't be broken lol... They this root.bat: https://drive.google.com/file/d/0Bygh6W_e2Fo5M185ZENkSUl3Zmc/view
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
A case of virtual beer to ya! I'm rooted!

What does this script do that the other missed?

Sooner or later SuperSu will want to update binaries. If I do it, do I break things (I've seen that in another phone I rooted) or doesn't it matter? For some reason, FlashFire app doesn't want to run to completion. It detects an OTA (it should) and then... nada. It just goes away. Finally, is there a way to make that OTA go away? Obviously I won't be using it.
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] Craz Basics:
Yes, updating binaries breaks it... As for flashfire, just update it. And for the ota, does wiping cache work? You can disable/uninstall software update packages (there's two)
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
OK, I'll stay away from messing with SuperSu. I think I saw some way to suppress the "need to be updated" - got any ideas about that?

Gotit about FlashFire.

I'll try wiping the cache - how much trouble could that get me into? ;) I'll cruise around with Ti to stop the updating. BTW, does using Samsung_Security+OTA_Disabler_(BillA_v2018-01-01) have any value here?

Good on ya for saving my sanity. ;D
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] Craz Basics:
No ideas on the need to be updated, but the file by billa; Not sure if that will, I've never used it. If it deletes the software update apps then it should. And no problem mate... Kevp75 got me saying mate alot?
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] RBEmerson:
The OTA hovering around in the phone bothers me more than avoiding SU updates. I have some control over the updates but OTA... not as much.

"Mate - the word that won't go away". I have a friend, from near Stuttgart Germany, who moved to Sydney. Even he can't get rid of "mate". LOL
[T-Mobile Samsung Galaxy S7 Edge Guides, News, & Di] Craz Basics:
It's a pretty dope word. And clearing cache doesn't remove the ota? I thought it did.