Samsung S7 bricked ? stuck on TWRP logo

[aibd]

I guess first try

adb devices

during bouncing e – to see if you actually have contact.

@Ghisbar

What about " or adjust for path and name

Did you download Kiss to your platform-tools folder ? That may be easiest thing no need to be concerned about path in this case.

Does it have the same name that I used ?

[Ghisbar]

Few seconds after the start of the installation of e there is a message in the PC “Unknown Device…” and “omni_herolte” is not as device in the file manager. So there 's no contact.

I download Kiss to my downloads directory but I have put adb in the path.
I use the same name, you can see it in my last message (copy of the terminal editor)

[aibd]

@Ghisbar

is not as device in the file manage

We do not expect the file manager to see the phone under these circumstances.

If the length of time of bouncing e is predictable at 20 minutes + … then the optimum time to try adb devices is at 18 minutes (this might give “First boot” some time to develop). If adb devices should ever give a response, then go for

adb install fr.neamar.kiss_208.apk

If you open a Device manager window, do you see the phone as a " Problem device" ?

[Ghisbar]

Now after long minutes it returns to TWRP. The PC can see the phone as “omni_herolte” in the file manager.
In the devices manager it is seen as “Appareils mobiles/omni_herolte”.

I try to see the phone by adb

List of devices attached
ce0616062db3960604      recovery

so it was ok, but if I try after

C:\Users\Utilisateur\Downloads>adb install fr.neamar.kiss_208.apk
Performing Streamed Install
adb: failed to install fr.neamar.kiss_208.apk: /sbin/sh: cmd: not found code here

A question, like I try a new installation. I start by Wipe and Format where we need to say yes;
The tutorial show a picture where format uses mke2fs. On my phone it is using make_extf4fs.
Is it Ok?

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