Galaxy s7 unlock bootloader

/e/OS Devices Samsung
1

Hello everyone,

I can’t access to the bootloader of my samsung galaxy S7 and I can’t install /e/ os.

I activated the option OEM unblock in the development mode and but when I go after in the download mode, I have the blue/green screen but it doesn’t propose me to unblock the bootloader.
There are only 2 options (to continue or to cancel).

I tried many things (factory reset, another USB cable, change the date and the hour, replace the drivers, etc.) but it didn’t solve the issue.

When I do an adb devices, my device appears but it doesn’t with the command fasboot devices. If I try to start directly in the bootlader (from the recovery mode or with the command adb reboot bootloader), the device restart android and it doesn’t go in the bootloader.

Someone please to help me ?

2

Samsung does not use fastboot.
Know your hardware - Samsung. No fastboot command is seen on the install page.

In order to unlock bootloader you probably have to be online. In Download aka Odin mode do you see Prenormal?

4

Thanks for your help and your information about fastboot.

Ma device is online and in the odin mode, I have this screen :slight_smile:

20250908_112147
20250908_1121471816×4032 349 KB

The option to unlock the bootloader is missing.

5

I see “Volume up to Continue” … this does what?

6

I have this screen :

20250908_130114
20250908_1301141816×4032 211 KB

7

It looks like you are good to go. The bootloader appears unlocked.

It is only this screen after “Volume up to Continue” which is your Download mode aka Odin mode.

It is suggested to heimdall print-pit to test your heimdall install before

heimdall flash --RECOVERY recoveryfilename.img --no-reboot
8

OK thanks it worked very well. The custom recovery of /e/ os is now installed and I can access to it but I have another issue now with the installation of the OS.

I’m trying to send adb command but my device is unauthorized while there weren’t any trouble before that. I enabled ADB in the recovery but it doesn’t work, my device is still unauthorized.

I tried to stop and restart the adb server but it doesn’t change anything.

I thought to install twrp instead of /e/ recovery but I would like to know if there’s something to solve my issue because I don’t want to start from the beginning…

Here is the screen with my ADB commands :

20250908_165724
20250908_1657241920×865 139 KB

9

This could happen if a Factory reset happened and this turned off USB debugging, and / or when allowing adb, be sure to tick “allow from this PC always”.

e-Recovery has a switch, I think from Advanced > Enable ADB but you did that already. Might be worth to add Mount System ??

May be worth to experiment with TWRP.

I did bookmark this link a while back How to Enable USB Debugging from PC Using ADB Command? but untested by me. Ofc it is an unsubtle ad for itoolab so you would want to be confident that you understand the command line intervention before you start.

10

I tried with twrp instead of custom /e/ os and it worked., no issue with adb, my device was recognised.

I don’t know why it doesn’t work with /e/ recovery… Anyway, the OS is installed and everything is working.

Thanks for your help.

2 Likes