Samsung - Galaxy S7 - herolte - Documentation Suggestions

eOSWiki Documentation Suggestions
21

Thanks @piero.
I know this dialog, but I was in the recovery, that does not display it, as far as I know.
I had swiped the data, cache and system (following the documentation).
adb devices was displaying “unauthorized”.

22

Have you enabled sideloading in the recovery ? If you’re using /e/ recovery, you should see some command lines at the bottom left corner. Look for some info there when you start sideloading.

23

Yes, I had chosen “adb sideload” (or similar label) in /e/ recovery, and saw the console lines in the bottom left. I don’t remember any error message there.
I can’t swear because I don’t have the device in hands any more, and used the SD-card workaround.

24

So did the workaround work?

25

Yes, flashing from the SD-card worked for me. It allowed me to workaround the issue, and install /e/OS 2.9 on the device

1 Like
27

Hello here,
Does someone knows why there is no e/OS version for herolte device greater than based on android 12 ?
I am thinking about building one myself to enable android auto on the device. but I don’t want to spend time if there is already a good reason for not having an official one.

28

hello @sylvain.pare, Welcome to the /e/ forum.

there are :

a-13 based
[UNOFFICIAL BUILD] Samsung Galaxy S7 / S7 Edge / Note 7 for /e/OS-T - #7 by ronnz98
a-14 based
[UNOFFICIAL BUILD] Testing! Samsung Galaxy S7 / S7 Edge / Note 7 for /e/OS-U - #13 by ronnz98

29

Thank you! Even if this doesn’t answer to my question:)

30

Then please rephrase your question.
How are available A13+A14 unofficial not

?

31

because there is no unpaid /e/ volonteer to be official maintainer
and
because paid Murena developpers are assigned to others task

1 Like
32

Thanks. ok so technically no show stopper.

33

only device, kernel, vendor must comes from Unofficial repo
because the device is not officially supported by LineageOS anymore,
and e.foundation cannot currently take the time to analyse the code modifications on the device side, and apply them into their sources.

1 Like
34

This week-end, I had to flash again a Samsung S7 at a flash-party.

When flashing from e-recovery, I had the following error message:

$ adb sideload e-3.7.1-s-20260416608787-official-herolte.zip
adb: sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

As in 2025, my workaround has been to apply the /e/OS zip file from a SD-card instead of through adb.

However, I’ve seen afterwards that the recovery link of the doc points to TWRP. Maybe it would have worked through adb with TWRP? But, in this case, the recovery should not be listed in /e/OS official herolte download . Because it’s very confusing

1 Like
36

Thanks @piero but I know this popup, and no such confirmation was asked on the device.

Plus this problem occurred when trying to sideload the /e/OS zip file, from the recovery.

adb was not served by Android itself (which can display the popup you mention), but by the recovery (that does not, as far as I know)

NB: I have a “déjà vu” effect: we already had the almost exact same discussion last year :wink: : Samsung - Galaxy S7 - herolte - Documentation Suggestions - #20 by piero

1 Like