I have a Pixel 6A in front of me with Iode and it boots up to the Logon Screen. Stable for few seconds there and then device does restarts.
What I can see is that a message appears that the storage space is low, with the message: “Some system functions…”
Booting into safe mode is possible but hasn’t been resolved the problem.
I can switch to Fastboot Mode.
Does anyone have any ideas, can anyone help?
Is this a new install? What system was on it prior to iodé? I recommend flashing back to stock A15 and giving iodé installation another go.
No, Iode has been running for a longer time, a few months. The user now told me that yesterday briefly popped a message, something corrupted.
Currently it is the case if I shutdown the device and switch it on again and I don’t log in, then it remains stable for the time being and I can access it via ADB or Fastboot.
But I don’t know what to do there. with adb. ADB shell shows me the folders
When I try ADB shell CD /sdcard/ returns “No such file or directory”
When i try adb shell pm trims-caches 100m, then the device is restarting.
But the restarts are very quick, I don’t think it’s a real restart, the Iode logo appears and then the login screen again very quickly.
Edit:
It looks like the userdata partition is corrupt …
Yes, that is what it looks like. Not sure if the flash storage has died or what.
And there are no ways to check a partition with CheckDisk or something with adb or in bootloader mode…
If I’m fast, I can open the file explorer for a short moment and then I see the base folder.
I don’t know of any way to do that. With the partition being encrypted, it could be risky to lose data if you run disk repair utilities on it (even if you could). I think you will need to factory reset it / reformat it: not sure how much data they don’t have a backup of. The reason that adb shell isn’t giving you access to view userdata is because on firstboot it remains encrypted until the user unlocked it by logging in (consider that “security” but as we know “security and convenience are not the best friends” 
). So if they can’t login, then it remains an encrypted black box.
Hello Rik, thank you,
USB debugging is enabled and I can also display adb-shell directories. But it doesn’t help. Corrupt is corrupt. And with every access the device crashes. Unfortunately, there are simply no tools (at least not without root) via ADB to run a check disk. I see it now that only a Factory Reset can help.
Unfortunately, there is no backup yet. After setting up the new device, this was still on the to-do list. Manual backups just don’t work for the vast majority of users because they don’t. There are good solutions for automatic backups, for example with FolderSync to an SMB sharing on your own computer or in a cloud.
Life is what happens while you make other plans. 
certainly, we all are in that boat
I think the more questionable situation is if the flash storage is actually failing and that led to the corruption or what really happened? Once you have a working system again possibly there are some diagnostics that can be performed on it to read SMART data or other but I haven’t looked at it before and don’t even know if SMART data or other exists for mobile systems!?! Will need a bit of research, please let us know what you may find if anything!
Yes, I will report …
Hey Volker,
das Bessere soll nicht der Feind des Guten sein. Einmal in der Woche nen kleinen Speicherstick anhängen, woraufhin Seedvault automatisch loslegt, ist machbar. Dann hat man im blödesten Fall Daten von einer Woche verloren, aber immerhin alle anderen gerettet. Ich finde die Backup-Möglichkeit sehr bequem, viel bequemer als mein Sicherungssystem für den Rechner. Dort mach ich wirklich zu selten eine Sicherung (auf externe Festplatte).