S20+ SM-G985F/DS y2s - stuck at odin4 vbmeta.tar

I cannot tell you what to do … only point you to things you may need to learn about (more) … but “renaning”, I think, does not do the fundamental change required.

2 Likes

rename is misunderstanding…
here are 4 options to create a recovery.tar
.

using the linux GUI :

use the right clic and choose compress it
then select the .tar format

or

as advised in /e/ documentation, using the terminal

tar --format=ustar -cvf recovery.tar recovery.img

.

.

you could also create a magic combined .TAR !

using the linux GUI :

by drag and drop the vbmeta.img into the openned recovery.tar
or
select the two files before using the right clic and compress them both into an unique .TAR that can be flashed in AP slot using Odin

using the terminal :

tar --format=ustar -cvf recovery.tar recovery.img vbmeta.img
2 Likes

You re right @piero and @aibd . I am sorry for this error.

Just want to add that the simple ./odin4 --reboot is also timed-out, whereas it does work on the S6lite and also on my “american” uncompatible S20+ (I have just tried).

Maybe not a problem of file formats?

recovery flashed with windows odin 3.1.14 : surprisingly this time for me, it worked at first try! :smiling_face_with_sunglasses:

So the problem was the odin4 on linux
Here some prinscreens:

And happy to see /e/OS logo at startup

Now go for some testing.
Thanks @piero, @aibd and @ronnz98

3 Likes