I need the e/OS build as .tar or .md5 file to load it with Samsung ODIN

[tom6]

hi guys

i get the error “An error has occured while updating the deivce software“. now i only get a connection to the phone with samsung odin and usb. but with samsung odin i only can load tar or md5 files. no zip files.

with has used linux to unpack the zip file. after that i has created an tar file. if i want to upload this file i get:

ID:0/003 Added!!
ID:0/003 Removed!!
ID:0/003 Added!!
ID:0/003 Odin engine v(ID:3.1401)..
ID:0/003 File analysis..
ID:0/003 Total Binary size: 1128 M
ID:0/003 SetupConnection..
ID:0/003 Initialzation..
ID:0/003 Get PIT for mapping..
ID:0/003 Firmware update start..
ID:0/003 NAND Write Start!!
ID:0/003 SingleDownload.
ID:0/003 boot.img
ID:0/003 install/
ID:0/003 Unassigned file
ID:0/003 Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)

so the problem is “Unassigned file“. it looks that unpack + pack dont works. or what did I do wrong?

where i could get working images?
for galaxy s8, s10, s20 and s23. for the s23 i dont has found an image for e/OS. but maybe the community could help.

[piero]

Hello @tom6, Welcome to the /e/ users forum.

.

using Odin, you will only flash custom recovery manager, not the entire custom android OS.

it is using the custom recovery that you will be able to install the system .

[HOWTO] an Unified Install Guide Project for /e/

posts are editable as a Wiki. Here is the summary : (1) install the appropriate Flashing Tools (2) allow “Non Vendor OS” to be installed on the device (3) Check the communication between the PC and your smartphone (4) Download a custom recovery manager (5) Download an /e/OS build (6) Unlock the Bootloader (7) Flash a custom recovery manager on your device (8) install /e/ from your computer, using the “adb sideload” method or (9) Install /e/ without computer using the “Device-Storage…

[tom6]

thank you piero,

for some time, I was able to bring a samsung S8 to e/OS using odin. It may be that it was also the recovery image at the time.

but the recovery-e-3.2-s-20251022539006-official-dreamlte.img i dont get as tar or md5 file too. only as img.

if i want to open it with 7-zip or mount as image i get the error that the file is damaged.

i has tested heimdall frontend. at the register utilities in the field outout i get “device detected“. but as package i need a tar.gz file. i has tested the self-created tar file. after decompressing i get: heimdall packages shouldn’t contain links or directories.

with adb i dont can work. it dont find any device.

*grrr*

[piero]

take the recovery-e-xxxxxxxxxx.img file, and simply use the right clic of the mouse, navigate in the contextual menu to create a recovery-e.tar using 7zip :