Samsung S7 bricked ? stuck on TWRP logo

No red lines, no text information about something goes wrong.
Just the splash screen of e follow 30 mn after by TWRP

But I am asking about the Download mode screen – this is the green coloured screen – it is expected to be stable. Is Download mode actually unstable?

It usually tells us if there are any locks applied it can inform of other issues too.

On the download screen there are in the right up corner :

ODIN MODE     (red)
DOWNLOAD SPEED: FAST    (red)
PRODUCT NAME : S0-G930F         (white)
CURRENT BINARY: Custom         (white)
FRP LOCK: OFF         (white)
Secure Download : Enabled         (blue)
WARRANTY VOID: 1 (0x030c)         (green)
RP SWREV: B:8 K:6 S:7         (green)

And that’s all. At the end of the flash I have to reboot the phone. No more messages.

1 Like

Here I wrote something about the S7, maybe it helps.
Plus the only Samsung devices I could not flash stock or custom, had hardware failure.

1 Like

As said by @make-nz Odin to Stock ROM is a good form of test, both for the device and the PC.

Perhaps you can share any Odin error / issue.

Thank you for helping me.
I did a new flash test of the rom.
Below is the ODIN log.

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4071 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!! 
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003> 
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

And on the phone I can read

ODIN MODE     (red)
DOWNLOAD SPEED: FAST    (red)
PRODUCT NAME : S0-G930F         (white)
CURRENT BINARY: Custom         (white)
FRP LOCK: OFF         (white)
Secure Download : Enabled         (blue)
WARRANTY VOID: 1 (0x030c)         (green)
RP SWREV: B:8 K:6 S:7         (green)
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 8 BINARY: 2    (red)

I realized that my smartphone’s bootloader is in 8 and that I was trying to flash it with a ROM whose bootloader is in 2.

After loading the correct ROM, it’s ok !!!

Next step is to load e os !

1 Like

Only for information

One of my S7 (herolte) SM-G930F works perfectly with TWRP 3.7.0_9-1 + UNOFFICIAL LineageOS 20.0 for microG (A13).

The other S7 (herolte) SM-G930F works perfectly with e-rocovery (e-1.18-t-20231211, e-1.19.1-t-20240111 and e-1.20-t-20240224 + herolte.zip build by @ronnz98

1 Like

@piero , @aibd , @make-nz

Thank you very much for your help

Now I can flash my phone with the Stock ROM so I close this thread.

@Xxpsilon thank you for your information I try it.