Database Info

Urgent help needed odin fail

Hi all I will keep it brief.
I have tried to flash with Odin 3.10.6, 3.10.7, 3.09, 3.10 root, twrp, stock firmware G920F but everything fails at "Nand Write Start" its driving me crazy. I've tried different versions of Odin, Twrp, and even Smart switch multiple times but nothing will write to the phone. ODIN ALWAYS FAILS AT NAND WRITE START.
My phone will only boot into download and NOTHING else not even recovery.
Any help welcome......

Try different firmware revisions. You flashing stock? What was the last fw successfully flashed?
Sent from my SM-G920F using Tapatalk

It is Stock G920F (united kingdom EE (EVR).
My problem is No matter what version of Odin or what I try to flash Odin always fails after Nand Write Start. It's not just the stock firmware, it's anything I try to flash in download mode.

Im actually in the same boat just now. ODIN wont flash the EVR Firmware (previously it did, mine fails on the cm.bin). I have tried different ODIN versions and also different laptops. Also the Smart Switch / Kies3 recovery procedure didnt work for me either. I was able to flash TWRP via down and get into recovery, but it see a lot of unable to mounts when trying to flash custom ROM and fails to do so. I think that i might have stupidly wiped via recovery something i should not have as i did noticed before all this i lost me IMEI (unknown).
I always assumed that if you can get into download you would always be ok but this is the first time for me that im having big issues.
I really hope someone can help out other wise i have a really expensive paperweight.

cooltt said:
It is Stock G920F (united kingdom EE (EVR).
My problem is No matter what version of Odin or what I try to flash Odin always fails after Nand Write Start. It's not just the stock firmware, it's anything I try to flash in download mode.
Click to expand...
Click to collapse
Reactivation lockn as seen in download mode?.
Sent from my SM-G925F
---------- Post added at 04:06 PM ---------- Previous post was at 04:04 PM ----------
johnnyblaze1977 said:
Im actually in the same boat just now. ODIN wont flash the EVR Firmware (previously it did, mine fails on the cm.bin). I have tried different ODIN versions and also different laptops. Also the Smart Switch / Kies3 recovery procedure didnt work for me either. I was able to flash TWRP via down and get into recovery, but it see a lot of unable to mounts when trying to flash custom ROM and fails to do so. I think that i might have stupidly wiped via recovery something i should not have as i did noticed before all this i lost me IMEI (unknown).
I always assumed that if you can get into download you would always be ok but this is the first time for me that im having big issues.
I really hope someone can help out other wise i have a really expensive paperweight.
Click to expand...
Click to collapse
Try to flash latest fw. Probably you've upgraded the bootloader to which cannot be downgraded.
Sent from my SM-G925F

What i've noticed with the S6 (and S7 i presume) is because you can't shut the phone down completely when your stuck on the download screen it never fully resets itself for another attempt at flashing by Odin. If your hold Power+Volume down to shut it off, the screen just goes black briefly then it comes back onto that error message about connecting it to Smart Switch for emergency recovery.
Smart Switch is a waste of time, it will download all the software for your device , say it's going to install then you get an error message telling you to use recovery code which of course it does not give you! So basically you just go round and round in circles with Odin and Smart Switch, i'm convinced it's not being able to shut the phone down completely that causing the problem of failed attempts.
Anyway something you might try that allowed me to flash G920F United Kingdom EE (EVR) PDP in the end. >>>
The phone battery eventually died, i waited for 10 minutes before charging it up to around 15% again, then i put it into Download mode, made sure my windows 10 laptop had "debugging" enabled at start up (i think this is why Nand Write Start is failing).
I loaded up ODIN 3.10.7 with "Cf auto root", connected my phone then flashed the root file straight away. It worked, so i reset Odin, put phone back in download mode and flashed EVR quickly via odin and it worked.
Over all i thin there's 2 issues here: The phone cannot be completely shut down when it will only boot to download or that smart switch recovery error and Windows 10 keeps turning off "debugging mode" which prevent Nand Write to device. I may be wrong but after hours of attempts with lots of different Odin and Firmware thats what i noticed. There has to be a way of shutting the S6 off completely .
NB: Tried latest BTU firmware, won't flash same problem "Nand Write Fail"
NB; Reactivation lock is OFF

cooltt said:
What i've noticed with the S6 (and S& i presume) is because you can't shut the phone down completely when your stuck on the download screen it never fully resets itself for another attempt at flashing by Odin. If your hold Power+Volume down to shut it off, the scree just goes black briefly then it comes back onto that error message about connecting it to Smart Switch for emergency recovery.
Smart Switch is a waste of time, it will download all the software for your device , say it's going to install then you get an error message telling you to use recovery code which of course it does not give you! So basically you just go round and round in circles with Odin and Smart Switch, i'm convinced it's not being able to shut the phone down completely that causing the problem of failed attempts.
Anyway something you might try that allowed me to flash G920F United Kingdom EE (EVR) PDP in the end. >>>
The phone battery eventually died, i waited for 10 minutes before charging it up to around 15% again, then i put it into Download mode, made sure my windows 10 laptop had "debugging" enabled at start up (i think this is why Nand Write Start is failing).
I loaded up ODIN 3.10.7 with "Cf auto root", connected my phone then flashed the root file straight away. It worked, so i reset Odin, put phone back in download mode and flashed EVR quickly via odin and it worked.
Over all i thin there's 2 issues here: The phone cannot be completely shut down when it will only boot to download or that smart switch recovery error and Windows 10 keeps turning off "debugging mode" which prevent Nand Write to device. I may be wrong but after hours of attempts with lots of different Odin and Firmware thats what i noticed. There has to be a way of shutting the S6 off completely .
Click to expand...
Click to collapse
There is no recovery code as far as I remember. As long as you have the sn that should make a go.
And there is no way to shutdown the phone completely. We can force reset but it will only shutdown whem the battery depleted.
Sent from my SM-G925F

Rosli59564 said:
There is no recovery code as far as I remember. As long as you have the sn that should make a go.
And there is no way to shutdown the phone completely. We can force reset but it will only shutdown whem the battery depleted.
Sent from my SM-G925F
Click to expand...
Click to collapse
Smart Switch is useless! I put in the model SM-G920F then the serial number and SS tells me the correct firmware is (EVR), downloads it, prepares it for installing, starts to install, gets to 1% then says "an error has occurred please use the Emergency code below to recover your phone" BUT there is no code! It says Emergency recovery code: .......nothing.
The main issue i'm experiencing is ODIN will not flash anything of any version, always fails at "Nand Write Start".
I've tried multiple versions of Odin, Stock Firmwares, TWRP, Root. Nothing will flash until the battery is dead, then when i try with a little charge for the first time Odin will usually flash the 1st file i give it (no matter what it is) then thats it, back to failing after "Nand Write Start".
Driving me crazy.

Quick update. I loaded a later FW (Still UK) and it passed in ODIN, so that was better.
But after that it booted into stock recovery, showed unable to mount efs (no sim card in). I then rebooted and its been on a blank screen ( with the blue light flashing) for the last 30mins. No real signs of life.
Cheers

johnnyblaze1977 said:
Quick update. I loaded a later FW (Still UK) and it passed in ODIN, so that was better.
But after that it booted into stock recovery, showed unable to mount efs (no sim card in). I then rebooted and its been on a blank screen ( with the blue light flashing) for the last 30mins. No real signs of life.
Cheers
Click to expand...
Click to collapse
The stock didn't flash correctly then. After you flash stock with ODIN it should reboot into recovery, should just boot into MM, and go through phone set up.
The problem with flashing different Stock firmware (even if it's same region) it can cause all sorts of issues. There's G920F BTU which is the non branded stock for Galaxy S6 G920F then there's G920F EE (EVR) G920F Vodafone (VOD) etc
You'd think the non branded BTU would be fine on any UK S6 but that's not the case unfortunately.
Use Smart Switch and go through the emergency recovery option, one you put in your model and serial number it actually tells you what stock firmware your phone was shipped with, then you find it and flash it through ODIN.

cooltt said:
The stock didn't flash correctly then. After you flash stock with ODIN it should reboot into recovery, should just boot into MM, and go through phone set up.
The problem with flashing different Stock firmware (even if it's same region) it can cause all sorts of issues. There's G920F BTU which is the non branded stock for Galaxy S6 G920F then there's G920F EE (EVR) G920F Vodafone (VOD) etc
You'd think the non branded BTU would be fine on any UK S6 but that's not the case unfortunately.
Use Smart Switch and go through the emergency recovery option, one you put in your model and serial number it actually tells you what stock firmware your phone was shipped with, then you find it and flash it through ODIN.
Click to expand...
Click to collapse
Already tried that. Flashing the EVR just doesnt work, ODIN Fails every time. Smart Switch says it should be EVR based on S/N but i just cant get it flashed.
Dont know what else to try.
Cheers

You might also try Win7 or earlier, 32-bit, if possible. There are known issues with Win8 and later.
Sent from my SM-G920F using Tapatalk

DarryDoo said:
You might also try Win7 or earlier, 32-bit, if possible. There are known issues with Win8 and later.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Its WIN7 im using on both the work and personal laptop, neither of which have had any issues in the past.
IF i flash EVR, it fails, i then flash TWRP to reboot into Recovery, but i see there alot of unable to mount / error messages, possibly the partitions are damaged? I dont know.
cheers

Potentially bricked S7 Flat? - Custom Binary Blocked by FRP Lock and Odin write fails

I bought a G930F from Amazon for use with my T-Mobile service, rooted it, and flashed a custom ROM (not sure exactly which one, but I have a folder named "CF-Auto-Root-herolte-heroltexx-smg930f") to it almost a year ago and everything was working just fine until this.
I was trying to get FRep (android macro/automation) working. It uses a setup tool on a PC that requires a connection and USB debugging enabled on the phone. When trying to run the setup I was getting errors about the socket/address already being in use so I'm not sure if it ever managed to do anything, but I saw a suggestion of rebooting my phone to fix the errors. In doing that I held down the power button, for my ROM's power options, chose reboot, went to the next reboot screen (maybe TWRP?) and chose the default reboot there.
When my phone tried to boot I got the Samsung Galaxy S7 logo with small red text of "Custom binary blocked by FRP lock". I'm still not entire sure what causes this (seems like a mismatch between having a custom ROM and some other setting). I'm wondering if the FRep setup tool somehow switched from OEM firmware protection flag. I booted into the download mode and tried to just reflash my old ROM, but even in the download mode I'm seeing "Custom binary (RECOVERY) blocked by FRP lock" with "NAND Write Start!!" then "Complete(Write) operation failed." in Odin3 logs.
I'm giving as much detail as I can because I'm not exactly sure which pieces are which. I've actually tried flashing the "CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5" and "twrp-3.0.2-2-herolte.img.tar" files in the "AP" slot in Odin3 as I don't remember which file is for what, but both give errors on writing. I'm wondering if I shouldn't do custom ROMs in the future as I don't follow the scene long enough to learn all that I should in order to not mess things up.
Any help will be appreciated!
edit: I'm downloading a stock S7 ROM from sammobile, but I don't think Odin3 will be able to flash it anyways. Is there any way to use the PIT settings or something else to change the OEM protection piece?
edit2: After downloading a stock ROM I was able to flash it all with Odin3. I think only part of it would have been necessary (maybe just needed a new bootloader, not entirely sure about AP/CP/CSC fields in Odin3.) Got the phone working again, but now I've gotta remove some popup inducing malware that I think I got when downloading a stock ROM the link in the instructions here: https://forum.xda-developers.com/galaxy-s7/help/frp-boot-fix-sm-g930f-t3350149

Anyone have AQF7 BL & CP

As the description, silly me flashed TWRP and in bootloop AQF5 for my G955F, can't enter TWRP or start normally.
Read through a few threads and tried the flash TWRP twice and instantly attempted vol up, Bixby & power button after restarting in from odin mode but it just sits in bootloop, boots into odin fine, tried so many time, with no lucks.
I have a Smartswitch backup but my phone isnt being recognised, so I try the emergency firmware route, the download & initialization gets to 83% and I get an error message, so my back up is useless until I manage to reboot or at least flash a new rom in TWRP (if I can get into it)
Just to I'm stock no root, TWRP flash knocked my Knox to 1 which i'm not bothered anyway
Been trying the past 2 days to download from samfirmware, samsung-firmware.org & updato to which my download gets to 40%, 73% and 80% before it decides to start pending then fail when I retry, been on phone to ISP and no problem on my line so I'm strumped and in need of AQF7 BL and CP please....
good thing I have an S7 as a spare

iamsloany said:
As the description, silly me flashed TWRP and in bootloop AQF5 for my G955F, can't enter TWRP or start normally.
Read through a few threads and tried the flash TWRP twice and instantly attempted vol up, Bixby & power button after restarting in from odin mode but it just sits in bootloop, boots into odin fine, tried so many time, with no lucks.
I have a Smartswitch backup but my phone isnt being recognised, so I try the emergency firmware route, the download & initialization gets to 83% and I get an error message, so my back up is useless until I manage to reboot or at least flash a new rom in TWRP (if I can get into it)
Just to I'm stock no root, TWRP flash knocked my Knox to 1 which i'm not bothered anyway
Been trying the past 2 days to download from samfirmware, samsung-firmware.org & updato to which my download gets to 40%, 73% and 80% before it decides to start pending then fail when I retry, been on phone to ISP and no problem on my line so I'm strumped and in need of AQF7 BL and CP please....
good thing I have an S7 as a spare
Click to expand...
Click to collapse
I think you only need to flash the bootloader:
https://drive.google.com/file/d/0B0pBZnf22V4qUEVsWTUwOWJwdkE/view?usp=sharing

samteeee said:
I think you only need to flash the bootloader:
https://drive.google.com/file/d/0B0pBZnf22V4qUEVsWTUwOWJwdkE/view?usp=sharing
Click to expand...
Click to collapse
Thanks pal, I ended up downloading AFQ7 after my ISP called me to say they have identified and fixed a fault on my line, my S8+ is back to normal and I've refused to install to AFQ5 update haha think I'll root it tomorrow seeing as I have a way of bringing myself back to stock now
Much appreciated

Can admin close the thread please, problem solved

S7 G930T stuck in bootloop to recovery

So I have an S7 that had the stock tmobile rom and it just crashed out of the blue and started looping. I have tried to access the recovery menu ,but it just says recovery booting in blue text at the top of the screen and then goes to a screen that says installing system update which promptly fails and I get a screen of an android and an exclamation mark above it. This is the result after my attempts to flash the stock image with odin. I am able to get to download mode, but that is about it. I am trying to get at least the stock rom working, but I've had no luck so far. Any and all help would be appreciated
Model: S7 G930T

Sanguino said:
So I have an S7 that had the stock tmobile rom and it just crashed out of the blue and started looping. I have tried to access the recovery menu ,but it just says recovery booting in blue text at the top of the screen and then goes to a screen that says installing system update which promptly fails and I get a screen of an android and an exclamation mark above it. This is the result after my attempts to flash the stock image with odin. I am able to get to download mode, but that is about it. I am trying to get at least the stock rom working, but I've had no luck so far. Any and all help would be appreciated
Model: S7 G930T
Click to expand...
Click to collapse
Hello, same as me, i got stock in the loop recovery mode, but in diferrent way, i try to tell help, or maybe someone help us both hahaha, the thing is the you need to know the "pda" of the phone in order to download the correct firmware, you need "odin 3.12", an the firmwares are in updato.com/, but, i think that you can download fw, descompress and use in odin only the "ap" and "home_csc" file, this will only update the o.s. and the home_csc will not mess with the partition, hope this coult help you, because, if you mess the partitions, and you dont know the pda of the phone, you will be like me, downloading all the fw, an trying with one by one. There something about "debbugin" and "oem" setting from deloper mode, i don't know if there will cause you trouble with the update.
Hope help you, if i'm wrong plz help us.

Stock-S7 freezes on startup after Oreo-update (full wipe, different stock ROMs)

Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp

philipp-h said:
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
Click to expand...
Click to collapse
Philip, it helps if you let us know what country your in.
Anyway the solution to your problem is pretty straight forward, you just need to flash the latest firmware for your region with Odin. No need to mess about with TWRP at this point.
Official firmware will contain a copy of the stock kernal which will also be installed when you flash with Odin 99% of the time. If for some reason the kernal is not flashed (it happens) and you continue to get the reboot issue then you will need to flash the kernal seperately first with Odin then the firmware afterwards.
The issue with the FRP lock will remain after this but should allow you to unlock with google email and password.
So we're talking, downlaod mode, flash official fimrware and go from there.

Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...

philipp-h said:
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
Click to expand...
Click to collapse
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.

cooltt said:
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
Click to expand...
Click to collapse
Hi cooltt and thanks for your help!
Unfortunately the BTU-ROM did not solve the freeze-reboot-problem but led to another: After flashing the phone gets stuck with a blue screen "Erasing". After several hours I force rebooted and now it is showing a similar screen with "Error!" and a percentage which is increasing to a random number from 0% to 12% on each boot. On first boot it shows the boot screen ("Galaxy S7"), then "Installing system update" shortly and then "Erasing". After force-reboot it shows boot screen, "Erasing" then "Installing system update", both for a very short time (sometimes misses "Installing...")
As suggested I used SamFirm to download the newest BTU-ROM (SM-G930F_1_20191218140415_dgobhw6g3v_fac; G930FXXS7ESL5/G930FOXA7ESL5/G930FXXS7ESL5/G930FXXS7ESL5). I just ticked F. Reset Time and Reboot. Re-Partitioning did not change anything. Using Odin v3.13.1 does not make a difference. The other ROMs, like SM-G930F_1_20191226131628_8ds2p6kf0v (G930FXXS7ESL9/G930FDBT7ESL9/G930FXXS7ESLA/G930FXXS7ESL9) which I downloaded with Frija (should do the same: download enc4-files from Samsung and decrypt) make the phone going to the initial setup fine, but with the reboot-problem. Tried also with Odin 3B patched.
At this point I was going to write, that I could not access the recovery mode with the BTU-ROM but just now I started it unintentionally when looking for the sequence of screens showed on boot. So I used my chance, made a full wipe and screenshot. After this the phone booted until the glowing "Samsung"-logo appeared. Then rebooted and went to initial setup (after "Androi"Installing applications") in German. The freeze-reboot-issue appears as with all the other ROMs.
The phone is certainly an original SM-930F as it was bought directly from a big, trustworthy dealer and then just used by my aunt. The only one touching it when problems appeared was me. There is SM-G930F printed on the backside and showed in download mode.
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089

philipp-h said:
Hi cooltt and thanks for your help!
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
Click to expand...
Click to collapse
Hi Phill
The only options checked in Odin should be F-Reset and Auto reboot. Don't check any others.
The blue screen erasing and updating is normal after a flash with Odin, the phone will restart a couple of times, just leave it do it's thing for a bout 10 minutes or so. If it's any longer than that as you have mentioned then it's stuck as you've said.
So we're going to start from the begining again but do something slightly different.
1. Place the phone into download mode
2. Run Odin but uncheck "Auto Reboot" so the only option checked is F-Reset Time.
3. Use whatever firmware you want, BTU or DBT the latest version. Make sure files are in the correct boxes.
4. Connect phone and flash with Odin, wait until Odin says "succeed 1" and "dissconnected" . It may even say "pass" in green, not important but "succeed 1" is important.
5. Your phone will show the bar and do not disconnect. So....disconnect from laptop / PC. The screen should remain "do not disconnect".
6. Hold volume down+home+power (in that sequence).
7. As soon as the screen goes black move your finger to volume up, while still holding down home + power. You are trying to get the phone into Recovery mode as you said earlier.
8. The option to choose in the recovery menu is "wipe cache partition" NOT "wipe/factory reset". I can see from your pictures that this option has failed because the FRP lock is still on!!
9. When you've chosen "wipe cache partition" then choose "reboot system now"
The phone should go through it's normal set up routine, erasing, update, installing apps etc, just leave it do this and hopefully the phone will boot then ask for the Google email and password which was used on the phone.
There are very few reasons for the phone to get stuck on boot....
1. Incorrect firmware,
2. Water damage
3. The phone has been Rooted with FRP lock on. It is very rare to be a hardware issue.
You should always turn FRP lock off and enable OEM unlock in settings before flashing to a phone. I know it's a little late for that but something to remember.
To check for water damage.
1. Remove SIM card and holder
2. Shine a light in the hole, you will see a WHITE sticker which turns PINK if water has ever got inside the phone.

Thanks a lot again for your great efforts!
I tried as you wrote but did not manage to start recovery immediately after flashing (tried >10 times). But after some while the BTU-ROM started and now keeps doing so even after new flash without wiping cache afterwards. Wiping data worked for me in past when I sometimes had enough time to enter Wi-Fi-password. It was saved even after reboot and away when I did data wipe in recovery. With the newest ROMs I never got beyond typing Wi-Fi credentials.
I cannot see a water damage. A root was never tried before (and OEM-lock and FRP were always on because stock, which is very bad now ). Would be absolutely no problem if this !#@*#% stock ROMs would work... TWRP installation was directly blocked when I tried my luck as last resort. I did not try other images.
Thanks nevertheless for your time and patience!