A52s 5G, Galaxy Tab S5e (LTE/Wi-Fi)
A somewhat more detailed documentary,
as a supplement to the install description of iode.
Here especially in Windows (My experiences):
Update the stock firmware to the latest
Unlock OEM in developer settings
activate adb and (type adb reboot bootloader)
First check if adb works:
adb --version
adb devices
adb devices -l
When not - check driver manually → Windows Devicemanager …
type adb reboot bootloader (adb reboot download)
Better:
shut down phone - and press Vol+ + Vol- while plugging to computer,
In Download Mode (DL), long press Vol+ and unlock bootloader
Device is reseted, and restart and then
enable again Developer mode and debugging …
Download the latest
iode-[…]-vbmeta.img and
iode-[…]-recovery.img
from (iodéOS for A52s 5G | iodéOS for Tab S5e (LTE) | iodéOS for Tab S5e (Wi-Fi))
and rename them as vbmeta.img and recovery.img.
Create tar files from them:
tar cvf vbmeta.tar vbmeta.img and
tar cvf recovery.tar recovery.img
Reboot to DL mode, (see above) and
flash with Odin
ODIN: In Download-Mode:
You can see that Odin has recognized your Samsung device
when a colored bar or a field appears in the Odin window
under the area of “ID: COM”, mostly yellow or blue, with a port number (e.g. COM3).
In addition, the message “added !!” In the news window below the connection,
the ODIN automatically installs the necessary drivers (if not yet available).
If not Check USB-Driver in Windows Devicemanager …
ODIN: vbmeta.tar (select it in AP) and then recovery.tar
My Question : How can you both flash at once?
After the flash of VBMeta, the device starts again with a reset,
Then again: first setup, developer mode again, debugging …
Otherwise Odin has to be started again to flash the recovery …
As soon as the flash ends,
quickly press Power + Vol+ buttons altogether
to directly reboot to recovery
Important:
Device can remain inserted, but you can press very much,
if you have to miss it, repeat again with flash recovery with Odin …
Again: Check if adb works (see above - adb –devices …)
if not manually assign the right driver …
From recovery => Factory reset => Format Data/factory reset
From recovery => Apply update => Apply from ADB =>
adb sideload <rom.zip>