[Android Q&A, Help & Troubleshooting] smarroquin:
Hello xda-developers world! I've been an avid reader of this forum for several years now, for this website is my old faithful when ever I have time to play. ;) Any ways, I've been working on this Samsung Galaxy S7 (SM-G930A) 32GB which, after all my attempts is currently on Bootloader V.9 unfortunately, for quite some time. Well, long enough for me to finally want to make my first thread on here. This device was given to me by a friend who thought I'd be able to fix it. I ended up keeping it due to the project taking several months (on and off due to the day job). He had this phone rooted using the Engineer's Boot method and decided he wanted a fresh start. I believe he proceeded to factory reset via stock recovery, which immediately threw him for a boot loop.

Symptoms:

Boots to the, "Recovery booting..." screen, transitions to the, "Installing System Update," follows up with the, "Erasing," animation, pauses on the, "No Command," screen, and finally reboots in to the same sequence until the battery is depleted. I am not able to access the recovery menu, so I am also not able to utilize ads commands. Download mode is still accessible, and I am able to flash stock firmwares to my heart's content. These attempts have also included extracting the PIT mapping from the CSC binary and checking the, "Re-Partition," box. I've used every version of Odin (v3.10.7 and up), including the various editions (Official, 3B_PatcheD, PrinceComsy, and Modded Raymond). Heimdall's releases on Linux, Mac OS X, and Windows XP, Vista, 7, 8, 10 were also utilised. When accessing the logs (via Power + Volume Up) at the, "No Command," screen, the following is displayed:

E:[libfs_mgr]Blob verification failed :255

E:Failed setting up dirty target

failed to mount '/system'(Bad file descriptor)

E:[libfs_mgr]Error creating device mapping: Device or resource busy

E:[libfs_mgr]Couldn't create verity device!

E:Failed setting up dirty target

[omc-app-link] fail to mount /system as rw

...and continues on with the same failure to mount /system for the various permission requests (omc-permission, omc-sysconfig-permission, omc-permissions-permission, omc-res-permission, hwr_symlink)

First of all, thank you for your time and bravery to make it this far down my post! I hope I've explained all the information that I have currently, as accurately as possible. I know it is quite an essay, but I wanted to avoid the twenty questions game that happens so frequently on here, due to questions without context. Now, my questions are...

Is there a known method of deleting all of the partitions on an Android device and reformatting the storage drive?

Do I have the classic case of a /dev/null being overwritten and is it correctable on this device? (I know on Linux it usually is via terminal by replacing the inode...)

I am open to any suggestions concerning the PIT file I have attached, which I was able to pull using Heimdall.

drive.google.com/file/d/1uS2BKzKxDMRjHkCfFt_kGoHrRJyqjlQQ/view?usp=sharing

(It has been translated to a .txt file, so feel free to take a look.)

It is really frustrating being able to see the issue, having countless tools at my disposal, yet feeling so powerless to correct it. Which leads me to my final question: Why haven't I thrown this phone out the window of my Maybach doing 280mph and given my life 100+ hours back? :D