Cannot install e/os on Galaxy S9

Dear all,

I am having problems installing e/os on a Samsung Galaxy S9 . I am doing the starlte command-line install described here (Install /e/OS on a Samsung Galaxy S9 - “starlte”). Some details:

  • SM-G960F
  • Android 10
  • From a Debian pc.
    Everything seems to work until I push the zip to the telephone, then I get the message: “E: failed to verify whole-file signature”.

A summary of my steps:

Requirements

  • Ensure your phone is charged more than 50% - OK
  • Check that adb is enabled on your PC. - OK
  • Download all the files and images mentioned in the download section below before starting the installation - OK

(I downloaded the Android 12 community starlte files version 2.7, which is a bit weird, since the S9 never got past Android 10, and the installation guide itself requires Android 10. But the download page only gives you the choice of Android 12???

These two files:

  • e-2.7-t-20250113460981-community-starlte.zip
  • recovery-e-2.7-t-20250113460981-community-starlte.img).
  • Make sure you have a working data cable to connect your device to the PC. - OK
  • Enable USB debugging on your device. - OK
  • Make sure that your model is listed in the [Smartphone Selector] - OK
  • Boot your device with the stock OS at least once and check every functionality. - OK
  1. Enable OEM unlock in the Developer options under device Settings - OK
  2. [Install Heimdall] - OK (built from source)
  3. Power off the device and connect the USB adapter to the computer - OK
  4. Boot into download mode - OK
  5. On the computer, open a terminal window, and type:
 heimdall print-pit
  1. If the device reboots, Heimdall is installed and working properly. - OK

Installing the /e/OS Recovery on your starlte

  1. Download the /e/OS recovery (linked in the Download section above) - OK
  2. Power off the device and connect the USB adapter to the computer - OK
  3. Boot into download mode: - OK
  4. On the computer, open a terminal window in the directory the recovery image is located, and type:
heimdall flash --RECOVERY recoveryfilename.img --no-reboot
  1. A blue transfer bar will appear on the device showing the recovery being transferred.

No blue transfer bar appears, but when I restart, I do get the recovery menu.

  1. Manually reboot into recovery - OK

Format the device

On /e/OS Recovery main screen:

  1. Select Factory reset - OK
  2. Select Format data / Factory reset option - OK
  3. Next screen will display a warning that this action cannot be undone - OK
  4. Select Format data to proceed or Cancel if you want to go back - OK
  5. If you selected Format data, the format process will complete - OK

Install /e/OS

In /e/OS recovery main screen:

  1. Select Apply Update and in next screen Apply update from adb - OK
  2. In the next screen, the device is now in sideload mode - OK
  3. On your PC type begin adb sideload. Type the below command in a consoleadb sideload downloaded_file_name.zip - OK
  4. Press enter key on the keyboard to start the sideloading - OK
  5. The PC console will now display Total xfer: 1.00x - OK
  6. The phone screen will now display some text with a message similar to

Script succeeded result was [1.000000]

Actually, no. It says:

E: failed to verify whole-file signature
Update package verification took 116.1 s (result 1).
E: Signature verification failed.
E: error: 21

Install from ADB completed with status 2.
Installation aborted. #1

And yes, if I reboot, I get Android again.

Any idea of what I am doing wrong?

Please can you confirm that this is the colourful e-Recovery, and not the “small text” based Android recovery?

Indeed, you are right. I end up in the stock os recovery, not the e-Recovery.
Any idea why this happens?

This is taken from the above link.

The references to TWRP and Team Win are to a previous generation of Custom recovery.

Hi,

First of all, if you’re using a Debian-based PC, go to this page: Install /e/OS Installer on Debian using the Snap Store | Snapcraft
to install the easy-installer on your PC.
Once the easy-installer is installed, connect your Galaxy S9 to your PC with a USB cable.
Then open the easy-installer and let us guide you through the process of installing /e/ os on your Galaxy s9.

Hi,
right, I will try that.
I om on some kind of derivative of Debian and could not find an installation candidate for Snap, so I disregarded the whole idea. I use apt, never heard of Snap before.
I will comment back tonight after I have tried the easy installer.

As you are capable of the command line install @CaptainMacWhirr there is little merit in using the buggy Easy Installer which is in the process of being retired. The business of the “First boot into Custom recovery” is a tripping point for very many Samsung users, and actually even more so for easy-installer users as you may read by following recent hashtags.

Hi

I hope that you are aware that there is no VoLTE available if you put a custom ROM like /e/ on the phone.
In many countries this is a major problem as many networks have dropped 2G or 3 G support completely so for these cases you cannot use it as a phone.
My provider has changed the 3G to 2G so if I use mobile data the phone needs to switch between 4G mode to 2G mode when dialing or accepting calls; this is a bit annoying as data transmission is stopped when in a phone conversation.
If you need/like /e/ I would suggest finding another phone. I had a lot of Samsung S phones (S9 included) and they are great but they are quite crippled nowadays as phones under custom ROMs.
Good luck!

@Cooler,
no, I was not aware. This sucks.
Here in the Netherlands 2G should stay available until the end of 2027 though, so I guess I can live with it for now. In 2 and a half years, the S9 will be quite old anyway.

@aibd,
Thank you. I will try again the instructions from the link tonight and report back here.

Hello all,
I was able to install /e/ yesterday evening on my S9. The button combination to restart the phone did the trick; I entered recovery and it was all plain sailing from there.

Thank you all for the support and links.

1 Like

This topic was automatically closed after 30 days. New replies are no longer allowed.