[Solved] Galaxy S8 does not reboot into e Recovery screen

Community Easy Installer
,
21

I last successfully installed the e-2.2-t-20240723-UNOFFICIAL-dreamlte:

Now I tried to install e-2.2-r-20240719418592-dev-dreamlte in the classic way - in vain, because more or less the above mentioned failures occurred. I’ll keep it short:

  1. installation of recovery-e-1.19.1-r-20240110372392-dev-dreamlte.img
  2. installation of those vendors
  3. installation of e-2.2-r-20240719418592-dev-dreamlte.zip

Not only the /e/ ROM e-2-2-r was installed correctly, but also /e/ Recovery V2.2.

By the way:
I’ve encountered faulty /e/ recoveries more frequently since releases V2.x, not only with Samsung Galaxy devices, but - also with other CustomROM distributions that are based on the source code of LineageOS 20.0 and 21.0. If there is an bug in the LOS code, this has far-reaching negative consequences.

2 Likes
22

Wouha ! an Android 8.1 based firmware part…
still needed…today !
Bravo.

23

The idea does not come from me, but is part of the /e/ documentation

  1. Manually reboot into recovery:
  • With the device powered off, hold Volume Up + Bixby + Power. When the blue text appears, release the buttons.

On some devices, installation can fail if vendors are not up-to-date. In this case, please:

  • Download those vendors
  • Install them
    • On the device, go into Advanced > ADB Sideload, then swipe to begin sideload
    • From the computer, please run adb sideload <vendors file>
24

I’m facing the same issue with my Samsung S8 and do not have Windows.

I do not see the ADB sideload option in the Samsung menu. Should I start the phone in the recovery mode from where there’s a ADB sideload menu option and push the file with adb?

26

Hi @marcaurele welcome to the /e/ forum. I do not mean to be giving you a hard time in your first post, but I always think “same issue … which issue”, there were a lot here :slight_smile:

What same issue? Failure of Easy Installer?

Why do you mention Windows? Do you say this because of

That link is labelled a Windows method but … are you able to follow along in Linux till the point where you have TWRP … if that is what is needed? The reason for this way forward was that the e-Recovery seemed to be non-functional.

It is not there.

Well, yes … if you have a working Recovery, but the issue seems to have been to have been a non-working recovery. A Working e-Recovery would look and behave like this [HOWTO] use e-Recovery to wipe & format data before sideloading/install eOS.

27

Thanks @aibd , I wil be clearer.

My problem is to get the phone to get into the e-recovery mode / screen, on a Samsung S8. I tried with the easy-installer, but when it’s time to do the 3 buttons press from Vol Down + Bixy + power to turn off / cancel the download mode, and switch to the recovery mode with volume up + bixy + power, it does never work. I tried many times. I looked at the video where the guy simply move the finger on the volume button. Nothing could work.

Then I moved to the manual installation mode, tired to repeat the easy installer process. I built Heimdall on my linux laptop without the UI, and I validated adb could correctly see the phone with the adb devices. I validated heimdall with heimdall print-pit which rebooted the phone as described.

Now I pushing the recovery image (for which I checked the sha256 sum) with heimdall. It shows a successful upload onto the phone:

./heimdall flash --RECOVERY recovery-e-2.2-r-20240715417776-stable-dreamlte.img --no-reboot
Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading RECOVERY
100%
RECOVERY upload successful

Ending session...
Releasing device interface...

but I’m still unable to move to the recovery screen with the button dance. It keeps showing the download screen.

I thought I could use adb reboot recovery but that does not work when the phone is in download mode.

So I’m trying to understand now this Vendor thing, but do not understand how I should load it onto the phone.

Why do you mention Windows? Do you say this because of

At this point I switched to this guide but I just kept using Heimdall because I was already familiar with it. And I was able to successfully flash TWRP and boot into it!

Yes, it’s about this message. I looked at Odin and it’s all windows stuff.

My understanding is that the recovery image could be buggy and cannot let the phone boot in recovery mode, so I should find another way to get into that mode, with another image. Is the TWRP image the alternative to get eOS on a phone with the link from @krokodilregister ?

1 Like
28

I managed to get the TWRP initial image on the phone, and did the data reset as explained on the other page. I used the ADB menu entry to sideload the eOS image onto the phone and it got installed, tada! It’s on, it worked!

2 Likes
29

Thanks.
e/os recovery does not work!!! I installed twrp ( Download twrp-3.7.0_9-0-dreamlte.img )as you said and it worked immediately. Then adb sideload e-os.zip
Perfect.