Error while trying to flash recovery image 2.8 to samsung galaxy s8 dreamlte

/e/OS Devices Samsung
,
1

Hello,
I am trying to install e/os on my old samsung galaxy s8 and have come into some weird error while trying to do so.

I have been following this install guide and got to flashing the recovery img to my phone. However, whenever I try to flash the image with heimdall, I get the following error:

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%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!

Ending session...
Releasing device interface...

In addition, I see on the phone, in red text: SECURE CHECK FAILED: recovery

I have tried to go on with the next step, just in case the flash still worked, but every time I have tried to boot into the e/os recovery, I just end up in the standard Android recovery mode.

How do I fix this problem?

2

Did you remove all accounts from the phone first, especially any Samsung or Google account must be removed. An extra precaution is to Factory reset.

Did you verify the download with the checksum.

You must use a good quality data cable and preferably a USB port soldered to the motherboard of the PC.

Are there any clues by looking at the Download mode screen of any lock applied.

3

  1. Yes I have. I didn’t at first, but I thought that might be an issue and factory reset the phone. It did not change anything.

  2. Yes, all is good.

  3. My usb cable is plugged directly in the back I/O of the motherboard, and is rated for file transfer. I have also used it multiple times successfully to transfer files.

  4. Here’s all the information text that is present, from top to bottom:

In purple:
   RPMB fuse blown
   RPMB PROVISIONED
In white:
   CURRENT BINARY: Samsung Official
   FRP LOCK: OFF
   KG STATUS: Prenormal
   WARRANTY VOID: 0x0
In Yellow:
   QUALCOMM SECUREBOOT: ENABLE
In white:
   RP SWREV: B8(2,1,1,1,1) K7 S8
In blue:
   SECURE DOWNLOAD: ENABLE
In white:
   DID: *device id string*

And finally, the red SECURE CHECK FAILED: recovery only appears after I try to flash the recovery image

4

Is a problem.

I have written as much as I know on the subject over here Know your hardware - Samsung # KG or RMM State Prenormal. Is there any thing unusual about the history of the phone that might be the cause of this?

If it was a phone which had just been professionally refurbished the advice would be to have the phone online by Wi-Fi and SIM card.

Connecting to remote servers to check for software update may also remove the prenormal condition.

5

I have connected the phone with wifi and an activated SIM card, prompted the phone to look for updates, and waited a few minutes to make sure the phone has the time to connect to a remote server and now the KG status has changed to checking.

Unfortunately, the error still persists.

1 Like
6

That is a useful change. As far as I understand checking is the result when Prenormal is actually freed but “Checking” is shown when no Google account exists on the phone.

I think I would restart both the phone and the PC then check your Heimdall install by:

Boot into download mode … run

 heimdall print-pit

If the device reboots, Heimdall is installed and working properly.

Then carry on to

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

If it still fails please show the new error … and / or you might try TWRP as an alternative recovery, Download TWRP for dreamlte.

7

Alright, so print-pit indeed rebooted the device, however I got an error at the end of the print

~ heimdall print-pit
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.

Entry Count: 59
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 14649
Unknown 6: 56
Unknown 7: 4
Unknown 8: 0

-- All the entries are listed here without a problem...

Ending session...
Rebooting device...
ERROR: Failed to receive reboot confirmation!
Releasing device interface...

Since this did not cause trouble for rebooting the device I went ahead and ran the heimdall flash:

~ heimdall flash --RECOVERY recovery-e-2.8-s-20250220470167-official-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%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!

Ending session...
Releasing device interface...

The SECURE CHECK FAIL: recovery also appeared on the phone.

I still tried to boot into recovery right after, but alas, the Android recovery booted, with no sign of the e/os recovery.

As for flashing TWRP, I get the exact same error from heimdall and on the phone

~ heimdall flash --RECOVERY Downloads/twrp.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%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!

Ending session...
Releasing device interface...

I tried flashing TWRP with heimdall because, as I understood, the s8 does not have fastboot, and therefore a flash cannot be done via fastboot. If I did something wrong please tell me.

8

Are you aware of the difficulty of the First boot into recovery ? … but you are still getting a “failed upload” message.

9

If the device reboots “FROM ITSELF”, Heimdall is installed and working properly.

this is a problem…

1 Like
10

Yes I am aware that booting from the download mode directly to recovery can be quite hard. I have however tried multiple times, all giving me the Android recovery instead of the e/os one.
Most attemps have booted directly into recovery, so I was sure that it was not because the phone wiped the flashed recovery that it happened.

11

I guess it is still some problem between Heimdall and the phone. As pointed out by @piero you seem not to get the automatic reboot. (As well as still getting a “failed upload” message.)