[XDA Assist] Gelmage:
I've been trying for more than 2 weeks now to get my phone back to working condition, I finally decided to just register and ask, maybe I'll get lucky right?...

So, I've been using all kinds of threads found mainly on this site thus far. A few from other sites but mainly here, it seems like the trusted place online for this kind of stuff. I had rooted my phone without much knowledge prior to doing so, and was very careful with it after root. Then one dark day... I was uninstalling something and hit cancel. From there, my troubles began. Soft bricked, freezes at logo.

https://xdaforums.com/grand-prime/development/files-sm-s920l-straight-talk-verizon-t3411688

This thread here is the last place I was looking to fix my phone, but just couldn't get it to work. Finally got my phone to at least show up in odin, I'm pretty sure that's only because I fired up a virtual PC which installed win. 7 drivers (The OS I wanted to emulate so I could see my phone again). I didn't have to actually install the OS on my virtual PC, the simple installation of the program and the win7 setup (I'm pretty sure at least) made my phone recognizable by odin. Here are the details:

On Downloading Screen -

Odin Mode

Product Name: SM-S920L

Current Binary: Samsung Official

System Status: Custom

Reactivation Lock(kk): On

Qualcomm Secureboot: Enable (CSB)

RP SWREV: S1, T1, H1, R1, A1, P1

Secure Download: Enabled

Secure Check Fail: Boot (Has changed many times, I've seen system, recovery, and boot so far. I usually don't pay attention though, so possibly more)

With Odin using files from the above thread and other threads, the furthest I have gotten was with a combination of files in the above thread. It actually started writting, but then failed. Generally doesn't get that far.

Here are several attempts I've made in the last half hour

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> boot.tar.md5 is valid.

<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> system.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

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

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

<ID:0/003> Removed!!

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> recovery.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Removed!!

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

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

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

<ID:0/003> boot.img

<ID:0/003> NAND Write Start!!

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

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

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

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

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

<ID:0/003> Removed!!

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

<ID:0/004> Added!!

<ID:0/004> Removed!!

<ID:0/004> Added!!

<ID:0/004> Removed!!

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

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

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

<ID:0/003> boot.img

<ID:0/003> NAND Write Start!!

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

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

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> system.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

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

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

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> MD5 hash value is invalid

<OSM> stock.sm-s920l.recovery.tar.md5 is invalid.

<OSM> End...

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

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

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

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> recovery.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

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

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

I have the ability to start the phone with options to use system recovery, clear cach, etc. Actually, it's probably smarter to just restart my phone and list my options so you know exactly what is showing.. Before I do, I sometimes leave the SIM card in, sometimes have it out. Doesn't seem to make a difference.

Reboot System Now

Apply Update from ADB

Apply update from external storage

Apply update from Cache

wipe data/factory reset

wipe cache partition

reboot to bootloader

power down

view recovery logs

I've tried nearly every combination of things I could think of, and it remains the same. I've read several threads saying my problem is the reactivation lock, yet most of those threads had someone saying they fixed theirs in some unique way. If anyone at all knows step by step what I need to do, please please let me know. I'm running a windows 8.1 (Recently upgraded from win. 8 with several notable problems (missing system files/drivers))

Thank you in advance! If any extra info is needed, please let me know. Please keep in mind that until I soft bricked my phone, the most I knew about phones beyond your typical user was that rooting existed, and the stuff you could use/do after rooting was awesome, until I accidentally hit cancel.

(Almost forgot to mention, my wife has exact same phone/model as I do. Can something be done knowing that? I just, can't do anything that would risk her phone's operating condition)