The md5sum of the Twrp I’ve flash in october is
twrp-3.2.3-1-a5y17lte.img.md5 file content : 9a5bed8e6d5483bc1595169162c58540 twrp-3.2.3-1-a5y17lte.img
It’s downloadable with the image, you can check it with command : $md5sum -c twrp-3.2.3-1-a5y17lte.img.md5
or to calculate it : $md5sum twrp-3.2.3-1-a5y17lte.img
If different try to download it another time (download corrupt)?
Why not try with the tar file (then untar it, and flash) or try with an older version ?
Apparently @Manoj you were right. I can go further now, I can reach the recovery mode which is like the picture below. So, how to install /e/ with that (https://gitlab.e.foundation/e/wiki/en/wikis/device/a5y17lte/install → the part “Installing /e/ from custom recovery” seems to be written for the use of Official TWRP App, don’t it?)? Should I restart from the beginning or not?
Not sure as I do not have a samsung device. @rhunault any help here. @FreeSpace now seems to be in the default recovery mode and not TWRP. Can the /e/ rom be placed on the sdcard (if available) and flashed with the Apply update from SD card option.
No, I haven’t tried. But I think I have understood what’s wrong. I checked and the device is not rooted (so I cannot used TWRP) however I did the following steps before :
The enable developer mode procedure:
Go to Settings.
Scroll down to "About Phone".
Software Information.
Look for the infobox "Build number".
Tap this 7 times, after 3 times you will get a notification "you are x tabs away etc"
Head back to "Settings".
Scroll Down.
Select "Developer options".
Enable: "OEM unlock".
Enable: "USB debugging".
@rhunault If you want we can continue this conversation in pm.
I think you don’t know the defiifernt between rooting and unlocking. For TWRP and/or flashing a custom rom there is no need for rooting. But the boozloader must be unlocked. And I think your bootloader is NOT unlocked nd that’s the problem
When I tried to use the recovery mode I went to default recovery mode and I got this following message at the bottom of the screen :
#fail to open recovery_cause (No such file or directory)#
#Reboot Recovery is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
# MANUAL MODE V1.0.0#
Successfully verified dmverity hash tree
E: Failed to clear BCB message: failed to find /misc partition