Actually to start my phone I have to connect it to the usb cable and after is stuck on the TWRP logo (v3.4.0-0).
The history :
Three days ago i saw many updates of /e/ (since 2021) notifications in a same time. I install the last one but the install fail and I can’t connect my phone with my PC (not a driver issue in the PC I Try with an another phone and that’s ok).
TWRP give the information of rypted issue. I saw this issue could be resolve by formatting the phone. But after that I only have the TWRP logo. If I press vol+, vol- and start button I can see Galaxy 7 logo and after the TWRP logo.
As far as i remember TWRP 3.4 was alway buggy, better is to use 3.3 or 3.5 or 3.6 or 3.7
For an upgrade from Q to R (without dataloss) you had to install first e-1.19.1-q, and then e-1.20-r.
But as you now have already formated /data partition, the way to recover your phone working should be flashing latest TWRP (or recovery-e) and then directly install e-1.20-r
Ok to flash the latest TWRP but I can’t connect my phone and my PC.
It’s not a PC driver issue, a cable issue because I can do that with an other samsung phone (S5 mini).
Is there any way with the sd card ?
IF TWRP is ok, there is another way to apply the upgrade. Check the ability of TWRP > INSTALL to navigate say to the root of SD card. You can download the /e/OS ROM to root of SD card (SD card in a reader attached to PC) and then install from there.
TWRP is not ok. It’s stuck to the logo.
When my phone is not connected (power or PC) = black screen
When my phone is connected, first the logo of Galaxy S7, after black screen and after TWRP logo.
If then I press vol+, vol- and start I have the logo of Galaxy S7, black screen and TWRP logo.
Sorry I could have not understand very well your proposal but like It’s not possible to have connection between PC and Phone how Odin can make connection to the phone. Does it have its own drivers ?
Odin is recognised to be a “leaked” Samsung tool, perhaps rather at Engineer level rather than User level.
As I understand it Odin does a more fundamental contact with the phone than Android Debug Bridge. Hence it is the tool used to revert a Samsung to Stock ROM.
Of course I may still be misinterpreting “broken USB connection”. This maybe a pure hardware issue and require a replacement USB module, quite inexpensive, but of course requires some disassembly. What was the last thing that happened before you observed broken USB?
I don’t know the actual mode of the phone.
The only thing I can do is connect/disconnect usb cable and press buttons vol+, vol- and start to restart the phone (logo Galaxy S7 and logo TWRP after).
I can have the Download mode.
I start Odin in admin and have connection (COM4) when I press vol+ on phone.
(Odin has its own driver ! your wright that’s worth testing)
In Odin Options I have only F. Reset Time
I press Start and have “PASS!” result after few seconds.
I have to manually reboot the device by pressing the main button, the power button and the volume down button. As soon as the screen turns off, I move my finger from the volume down button to the volume up button (while continuing to press on the other buttons) in order to enter into TWRP.
I can now see the TWRP logo with the new version (3.7.0_9-1) but always unknown device for PC and stuck on the splash screen (no welcome screen)
Just for clarity, how do you get “unknown device”?
Probably worth one more try with TWRP twrp-3.6.1_9-0
@Ghisbar, am I assuming that you were on a stable build? Be aware to either stay on stable, or change to dev, but e-recovery should probably match your ROM.
Samsung release different variant of their OS for each client branch, they sell their product to many carriers in many countries, and to many independants recellers in many countries.
So the release is fractionned in 4 parts
BL : bootloader relative partitions
AP : system relative partitions (mostly android and generic apps)
CP : radio-modem relative partitions
CSC : country/carrier relative partitions (country and carriers specific apps + APN)
Open CSC: This is the standard code used on most international versions of Samsung devices. It includes all firmware and carrier-specific features regardless of region.
Carrier CSC: This code is specific to a particular carrier or network operator. It includes carrier-specific features such as branding, apps, and networks.
Country CSC: This code is specific to a particular country or region. It includes country-specific features such as language support and regional settings.
OEM CSC: This code is specific to a particular manufacturer or distributor. It includes OEM-specific features such as boot animations and wallpapers.
