I’m on the sidelines and still believe things being up to either userland util (busybox mount), but much more likely kernel file system support (for custom mount options too) being responsible. Sure I can be wrong, I never debugged this on an affected device to see where this goes.
It’s interesting that you say the starlte behaved differently after the reset and it must be up to “state” (filesystem, version?) if it’s mountable. I can’t contribute to this more without taking the time to go debugging.
“Is the devices USERDATA partition mountable in a recovery? (in case of FBE - filebased-encryption - it’s not required for this table if it’s decrypted and filenames are shown)”
I have the same problem and read the whole thread, but the problem is not solved:
Fairphone FP3+, Signal messenger backup and incoming WhatsApp videos clogged memory to 100% - now, upon phone start, MicroG and system services immediately crash, shutting down the phone.
The device is encrypted, and locked for TWRP. In Recovery mode, system files are not visible or empty (e.g. /sdcard shows up as an empty foler). I also tried twrp decrypt, which doesn’t work.
@rabon - deleting just any system files won’t help, has to be from userdata. The method in the threads (really strewn around, but basically 2 commands) works 100% on the FP3 models. If you’re still stranded let me know
@jan545651 good feedback for others, reviewing your replies imo your starlte then didn’t have an encrypted userdata and /e/recovery expected an encrypted userdata. Thus it worked after reset. Is that an explanation? as this megathread is used for the general no-space issue but runs under the headline “how to mount encrypted …” it could set a wrong framing for new thread entries over time.