Ahrrr…
F****, F****, F**** !
Help, @aibd @tcecyk did you remember a solution to something like that ?
at minus the cause ?
Any further ideas? Do i need to do a factory reset?
try again to boot… prior.
i will search for solved in archived topics
Search results for 'your data is corrupt order:latest' - /e/OS community
I tried again. It goes back to the same point. I guess i could try from power off?
do you have a SDcard setted up as to enlarge internal storage ?
could be the cause…
or full internal storage ?
I saw the posts regarding lack of space but I really don’t think this is the case here.
The device has 256GB and it was minimally used. No images/videos. Not many apps at all
So sorry I was not able to help you.
i don’t see where we fail…
thanks to your backup, i hope it can be restored…
Maybe we wait in case @aibd has any ideas?
but do you think if I do a factory reset I will eventually be able to get a working os?
yes for sure if you do a factory reset .
Only as you “called” me … I will give a quick reply without reading the full “story so far” … you have a backup so Upgrade with Format data seems the clean way to go.
One might read the Updater script with the ROM in /meta-info or such to check my memory of there being some special requirements ??
Perhaps we don’t take this entirely literally
… but the current recovery may not fit with the current sideload and updater script.
Are we jumping a13 → a15 at that time?
1 Like
In this scenario jumping from A12 to A15
Will doing factory reset work at this stage?
Factory-reset at this stage is expected to give you
an untouched clean stock e-3.2-a15-beyondx
1 Like
I do not have the answers tonight, sorry.
Only fastbootd is offered in that screenshot. Here fastboot has moved into “userspace”, so potentially that command
sudo ./fastboot flash boot recovery-e-3.2-t-20251026540684-community-beyondx.img
may have tried to do the “impossible” … did it fail benignly or may it have caused a problem which still exists ?? idk.
I checked the updater scripts for a13 and a15 and did not see the specific “special requirements” hazard I hinted to in Post #52.
Edit
Never mind all I just said, the most recent error with init user0 indicates Format data or Factory reset may be a fix.
1 Like
difference could be between a12 and a13
but a12 dev builds are not available anymore to check…
Thank you very much both. Factory reset brought it to life in Android 15. In my case the restore was easy as I had only contacts, sms and call logs to restore, which I had backed up using an app and restored them quite easily. I wonder if having had a gradual upgrade: a12→a13→ a14→a15 would have yielded better results.
I appreciate your help anyway…
1 Like
i ask myself why exactly…
what is your computer ?
could it be an old x86_32bits or a recent arm_64 ?
i built this heimdall binary on an Intel® Core™ i5- considered by linux as amd_64 so, "generic x86_64"