[Samsung Galaxy S7 Questions and Answers] mindlight:
Hi Obi Wans, you are my last hope.

Just before I went to bed last night I accidentally put my fat finger 2mm on the wrong spot and Samsung thought it was an excellent idea to start the waiting upgrade. After the first reboot the S7 just wont get past the "glowing" Samsung logo.

Situation:

Bootlooping. Black screen with glowing white Samsung logo. Led is glowing in blue in sync with the logo on the screen.

Phone does not restart / reboot. It is stuck in above mentioned situation.

Still on Nougat. Update was Nougat to Nougat. I use to be a couple of updates behind. I think last update I did was in Feb/Mar.

Hot A F. While not connected to anything but running the Samsung logo it is hot as F. Burning hot. I guess the CPU / Memory is working hard with something but I have no clue what that could be.

Can reboot and go into eiither Recovery Mode or Download Mode.

Wishlist (in priority order):

Get phone to boot up perfectly with no data loss or triggered Knox.

Get phone to boot up perfectly with no data loss but with triggered Knox.

Get access to files and / or opportunity to backup apps / settings / data in Internal memory.

I would really prefer not to trigger Knox. I'll do it if there is no other option and if it is possible to get access to the phone with unharmed configs or at least get data from the phone.

I thought I was smart when I set up ADB a couple of weeks ago. ADB access during bootup is working and the keys are in place.

Information I currently have:

Model No: SM-G930F

CPU Eyxnos

"NEE" / Nordic version.

Unlocked from day 1.

Never rooted or had any non stock roms.

Serial No: (Is there any risk related to put this on internet?)

Logcat log saved to my PC (Is there any risk related to put this on internet?)

Tools I have at my disposal:

ADB access that has been working ok during the night and morning. It is somewhat flaky because it seems like while I have access during Samsung glows the connection seems to break and I have to connect with f x adb shell again.

PC with both Ubuntu, Windows 7 and Windows 10. I could probably install XP if that would be of any help at all.

Another identical Samsung Galaxy S7. Friend gave it to me since screen was broken. Samsung fixed screen. Empty because Factory reset.

100Mbps internet connection.

What I have tried this far:

Rebooting (a thousand times)

Wipe Cache partition from Recovery Mode (vol up + home + power).

Shut down from Recovery Mode menu and then turning on with power button.

Mount /system (yeah, knew it wouldn't fix anything. Just wanted to see that /system was mountable.)

Tried flashing in "HOME_CSC_NEE_G930FNEE2DRB5_.....tar.md5" with Odin. (downloaded the exact version ADB reports when checking dmesg and / or logcat from sammobile). I read that this could help getting out of bootloop. Important was to use "HOME" and not the other CSC if you wanted to keep phone from going Factory Reset.

Anyone got ideas?

Edit 1: I have connected the phone and am running a logcat, dumpsys and a cat of all "files" under /proc to text-files on my pc.

When checking logcat it looks almost like it has tons of work to do but really never gets finished with the upgrade?