Hello, this morning I launched the update of my Samsung S5e tablet. After first reboot, no iodé logo displayed and the screen remains black 
I have no way to turn the device back on, and I can’t access recovery mode. I hope I will regain access to recovery after the battery will be empty
I managed to turn on the device with power + volume down (DL mode). The two Samsung screens are displayed, then black screen
Does anyone have an idea how I could fix the tablet ?
Other than a reinstall of 6.5 maybe and wait it out for 6.7 to come along is probably your best shot.
Thank you for your answer. Unfortunately, developper options & USB debugging were not activated before update. When I plug the tablet off on my computer, adb recognizes the device, but no action is possible (unauthorized). Is there a way to activate USB debugging through an adb command, without the device booted ?
AFAIA there isn’t, but I’m not the most android savvy person on here by a long way so don’t completely give up hope as someone who has had the experience of attempting to do it will most likely come along soon. There might be a way of doing it by rooting your device but then again, it’s beyond my level I’m afraid.
Gratitude for your clear words. I will wait a bit. As a last option I could entrust the device to a professional repairer. Enjoy “non forced labour camp” system 
In order to preseve my other devices, I have another question. It was the first update of the tablet, which I flashed last month. I can’t rembember if in updater app options, I activated or not the recovery update. Could the failure of the OS update be related to the absence of recovery update ? @iodéveloppeurs ?
I am pretty sure it is enabled by default.
So you still can’t get into recovery? (I’m not sure if you had gotten this to work after your first post). I am not certain but if you are in recovery I think you may be able to access via adb from there, then you could try to re-install the 6.6 update (using adb sideload).
But if this is beyond your comfort level, then with this being an officially supported device, can you email support [at] iode.tech?
Hello rik, thank you for being often responsive.
Unfortunately the power plus volume up key combination doesn’t work to access the recovery. And I can’t access it via adb because USB debugging is not activated. If I could access recovery it would be within my reach to sideload previous iodé version.
I’ll write to iodé support 
Best regards 
Hello, a few words to keep updated. Iodé support answered my email next day, and suggested me to reinstall iodéOS from Download Mode. I managed to access it and tried to reflash iodé recovery. Unfortunately it failed, and since that the DL mode is non longer reachable. Bricked device I’m afraid. Shit happens, I keep on giving trust to iodé. Thanks for having read.
That doesn’t seem to be a global problem. I have an S5E LTE updated to version 6.6. That wasn’t a problem and I installed a new S5e Wi-Fi from stock without any problems.
2 Likes
You’re right, I noticed no other report and it’s happy. What could happen during my update failure will remain mysterious 
To me on many aspects a privacy oriented custom ROM looks like white magic; magic is experimental
I again have no Samsung experience, what is this “Download mode”? @volker01 can you comment on that?
The Galaxy Tab S5E uses the download mode (no fastboat mode),
which is especially common for Samsung devices.
I write a HowTo Doku …
1 Like
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>
2 Likes
Good evening iodé users, a last and happy update. Today I pluged the tablet in order to load its battery. After a few minutes, the device spontaneously booted iodéOS 
Very surprising and comforting for me.
The system version is iodé 6.5. With hindsight, I tell me that during the update, the battery level was a bit to low to be successful.
Sorry for my such alarming post, concerning a basic mistake I could have avoided.
Many thanks to users who gave help
2 Likes
I’m confused about flashing VBmeta.tar and Recovery.tar
Do I flash both VBmeta.tar and Recovery.tar in the AP field? It only allows me to place one at a time, I can’t flash them together.