[Samsung Galaxy Note 8 Questions and Answers] Kamikaze_Ice:
Sorry if any of this has been mentioned or answered, I'm many pages behind and still playing catch up. Wanted to post something I was working on during very small but frequent breaks at work lol.

This is something I mentioned weeks ago in one of Kalm's threads. Happens to me with official firmware and even my original backups.

That is not the only "issue" I see when I enter the stock recoveryI

I'm really OCD, so whenever I want to flash any OS/Hardware stuffs I will always do a fresh install, so I've been doing full flashes of firmware with Odin (BL/AP/CP/Full CSC/USERDATA) with the default options in addition to using "Re-Partition" and "Phone EFS Clear". I'll comment on the last option below)

believe that whatever is causing this problem is also what makes the blue update screen fail at 32% (gets here then starts "erasing").

If I boot back into the stock recovery I get the same blue update screen that will always say "no command" before actually going into the recovery.

Once in recovery I see three "issues" in the log:

Failed to map file 'CACHE:recovery/sec_omc.zip'

THIS FILE EXISTS WHY CAN'T YOU SEE IT YOU POOPY DOOKIE CHIN FRONTHEAD SUNGSAM.... sorry, I lowered myself to Samsung's level lol.

I do not know why this is not seen by the device. As long as this file exists, stock recovery will constantly try to update android and always fail at 32%. This never happens once it's deleted or cache is wiped.

The contents of the file will be different depending on whatever firmware file was last flashed. I wonder if flashing multiple firmware files at once via Odin will pack them together in this zip or if it's literally the LAST file flashed by Odin.

I know the file exists because I can flash the zip in /cache/recover/ via ADB or even with TWRP (before and/or without flashing the verity/encrypt zip as per TWRP thread).

NOTE: If you use TWRP to flash this zip, only flash this zip file. Do not mount anything, do not wipe anything and do not flash anything else or you will be stuck with a maximum 16GB total allocation for all partitions (NOT the partition table, only the reported size of internal memory---This is NOT permanent. This happened to me and I didn't notice it for days. Flashed full firmware with a full boot to fix it (default Odin options with firmware in all slots).

The full boot is important or the /data partion may become unmountable in TWRP and fail to boot. Data wipe with TWRP, ignoring errors, boot into Download and reflash full firmware. If not fixed, do a "data reset" in stock recover and reflash full firmware again.

E: ensure_path_unmounted failed to unmount /efs (Device or resource busy)

No clue. Doesn't happen with TWRP.

/efs appears to get unmounted multiple times during boot so I don't know why it throws a fit now, and after looking at "view recovery logs" I didn't see anything. I may have gone blind though, the built in log viewer is HORRIBLE (inverted scrolling even with volume buttons??? ...:eek:) I should have pulled the logs and used Notepad++, but was being lazy at that point lol.

Multi-CSC is ALWAYS changing to AT&T

This ALWAYS shows regardless of what my CSC is.

I think this is caused from left over files from using Tkkg1994's CSC with that one line added so it would work with the Note 8, since Re-Partitioning+Phone EFS Clear+full firmware flash is useless.

This appears to be nothing but a harmless visualization and this is never seen outside of stock firmware.

The last part is interesting, as those options are clearly NOT doing anything as expected with the /EFS partition.

In fact, I think the EFS Clear option is really more of a Rebuild EFS sort of how wiping dalvik/cache makes the phone rebuild the cache based on what already exists. (read: nothing erased, do not start from scratch, do not pass go and collect $200.)

I don't know what belongs in /EFS but from my experience so far it is giving off some weird vibes and might be worth farting around in since those options didn't behave as expected.

You no longer have this issue? Does the blue android update screen fail at 32% or actually finish? See above for my experience (in this post).