Samsung S7 bricked ? stuck on TWRP logo

[Ghisbar]

It is when I swipe to begin sideload than the phone is disconnecting. At the end of the Sideload it reconnects. When I swipe to reboot it disconnect. Some seconds later the PC find a new Usb device unknown.

[aibd]

@Ghisbar

The tutorial show a picture where format uses mke2fs. On my phone it is using make_extf4fs.
Is it Ok?

I am not sure where you are seeing this. Maybe this helps ?

@Anonyme

Validate by dragging the “Swipe to Wipe” arrow from left to right.

If red error messages show up, your phone is probably encypted but TWRP can’t decrypt the /data partition (it’s a common issue on Samsung phones).

To solve that problem, go to Wipe > Advanced wipe, select “data”, click on “Repair or Change File System”, then on “Change filesystem”. Select exFAT (or another one if it doesn’t work, it doesn’t matter), then swipe from the left to the right. Redo the manipulation but this time select ext4 (which is the original file system) then slide from the left to the right.

[Ghisbar]

@aibd

I am not sure where you are seeing this. Maybe this helps ?

Validate by dragging the “Swipe to Wipe” arrow from left to right.

If red error messages show up, your phone is probably encypted but TWRP can’t decrypt the /data partition (it’s a common issue on Samsung phones).

To solve that problem, go to Wipe > Advanced wipe, select “data”, click on “Repair or Change File System”, then on “Change filesystem”. Select exFAT (or another one if it doesn’t work, it doesn’t matter), then swipe from the left to the right. Redo the manipulation but this time select ext4 (which is the original file system) then slide from the left to the right.

I follow all the steps of this Howto and also see at the end of the process the e and its boucing ball during 30mn and the restart with TWRP…

I use for my S7 :

• ODIN Odin3-v3.13.3
• TWRP 3.6.9_9-0
• e-1.20-r-20240221382013-stable-herolte.zip

Is there any problem with one ?

[piero]

in case you encountred problems using TWRP, the recovery-e can be recommanded…

[Ghisbar]

Ok I try also recover-e without succes.
I try to to reinstall stock SamsungOS without success (sbin issue)

I think it’s a hardware issue.
I stop to try and buy a S7 edge.

Thanks to you and aidb to try to help me.

[piero]

The s7edge often fall on the floor because it swipe easily from hands

[piero]

Insist to reinstall Stock SamsungOS is a good option…

[Ghisbar]

@piero

The s7edge often fall on the floor because it swipe easily from hands

I’m looking for a small, waterproof smartphone with good battery life.
The S7 edge seems not too bad to meets these requirements.
If you have any other ideas, I’d love to hear from you.

[Ghisbar]

@piero

Insist to reinstall Stock SamsungOS is a good option…

I’ve tried a dozen times, changing the cable and the USB port on the PC without success.

[piero]

I was thinking about options in Odin such as erase first or something like that…

Or trying a combination firmware then a normal…

Or using Samsung Kies instead of Odin…

As @aibd said, it is very rare to brick a Samsung…

[aibd]

@Ghisbar

I think it’s a hardware issue.

Perhaps a repair shop could give an opinion on it being USB module fault.

Are there any clues appearing on the Download mode screen?

[Ghisbar]

@aibd

Are there any clues appearing on the Download mode screen?

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

[aibd]

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.

[Ghisbar]

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.

[make-nz]

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.

Samsung Galaxy Tab A7 10.4 2020 (Wi-Fi) flashing help needed

If you decide to use Odin, just a few things to watch out for: Stop Odin from AutoReboot You can do that every time you start Odin, in the Option tab(next to the Log tab) or open the Odin3.ini and change it there for good: [APOption] RePartition=0 AutoReboot=0 FResetTime=1 FlashLock=0 TFlash=0 NandErase=0 Keep an eye on the Log, as connection issues show up there, which are often missed [ODIN-Stock-flash_S7_badUSB] If you ever have to install a Stock ROM, there are single-part and 3/4/5-par…

[aibd]

@Ghisbar

I try to to reinstall stock SamsungOS without success (sbin issue)

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.

[Ghisbar]

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)

[Ghisbar]

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 !

[Xxpsilon]

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

[Ghisbar]

@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.