Samsung S7 bricked ? stuck on TWRP logo

[Ghisbar]

Hello,

I do many tests.
Actually I have TWRP 3.6.1_9-0 on my phone but I can also flash TWRP 3.6.1_9-1. My phone is connected to my PC as “omni_herolte”.
I try install the image of /e/OS (e-1.20-r-20240221382013-stable-herolte.zip) using the ADB sideload method.
It’s ok until “ADB sideload complete successfull”.
After, when I tap “Reboot system” there’s a message in TWRP “No OS is installed. Are you sure to wish to reboot ?”
Have I to reboot ?

[aibd]

Yes, “No OS installed” is often seen!

[Ghisbar]

Ok, I have reboot but I have the /e/ logo withh the little ball bouncing during 25 minutes and nothing else happen…
After more minutes, I can see TWRP “Unmodified system Partition”

[aibd]

OK – just suppose in some case the current Bliss version is “too hard to load” at first install.

Try a much smaller launcher, for instance, KISS https://f-droid.org/packages/fr.neamar.kiss/, downloads at 1 MB, and can be downloaded to PC from that link

With e bouncing … especially when you have experience that it lasts a long time …

adb install fr.neamar.kiss_208.apk

… or adjust for path and name of your “smaller launcher”.

@Ghisbar

After more minutes, I can see TWRP

So it gives up in the end … but it is trying for a good long time.

On other thing … maybe if you have an SD card installed in the phone it will be a good idea to take it out (in case this also helps “reduce the load at First boot”).

[Ghisbar]

I download KISS and try to install it during e bouncing but fall :

adb install fr.neamar.kiss_208.apk
adb.exe: no devices/emulators found

What about " or adjust for path and name of your “smaller launcher”" ?
Also the SD card is not in the phone.

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