Cannot load Android System. Your data may be corrupt.

groupby64

Last week I entered my unlock password in the morning and the phone immediately reset. Before getting to the screen lock the phone goes to GrapheneOS recovery and has the error message

"Cannot load Android System. Your data may be corrupt. "

My options are 'Try again' and Factory data reset'.

I have tried to sideload. I had to wait until the recent update because it said that the version on my phone had a more recent timestamp than the one available on the releases page.

I have tried the sideload again with the most recent update. This completed but unfortunately I get the same message.

Anything I can do? I would like to recover my data if possible.

nandohyphen1

groupby64 "Cannot load Android System. Your data may be corrupt. "

My options are 'Try again' and Factory data reset'.

To me that sounds like the options you get if you enter the duress PIN. I can't confirm though, since I've never wiped my phone before with the duress PIN, only saw a video a long time ago of it, and I believe those were the options. Did you have a duress PIN set? Did you accidentally wipe it? Like I said, don't know if this is the cause, maybe others can verify. :)

nandohyphen1

groupby64 Last week I entered my unlock password in the morning and the phone immediately reset.

That also sounds like duress PIN behaviour

de0u

groupby64 Last week I entered my unlock password in the morning and the phone immediately reset. Before getting to the screen lock the phone goes to GrapheneOS recovery and has the error message

"Cannot load Android System. Your data may be corrupt. "

This behavior suggests that the flash storage holding the active system image has failed.

groupby64 I have tried to sideload. I had to wait until the recent update because it said that the version on my phone had a more recent timestamp than the one available on the releases page.

I have tried the sideload again with the most recent update. This completed but unfortunately I get the same message.

You could try sideloading that image twice.

de0u

groupby64 I would like to recover my data if possible.

You could try a forensic data recovery company.

ejns

nandohyphen1 That's not quite right. I just wanted to point this out in case anyone decides to test it. No confirmation is given if you enter the Duress PIN - it just freezes briefly, then goes black. That's it.

It's been a while since I've done it so maybe they've changed something, but I doubt it - a confirmation dialog kind of defeats the purpose.

groupby64

I did have a duress pin set. However, there is no way I would have accidentally used it since it was entirely numeric and my normal pin was all letters.

The day before this happened I removed the fingerprint scan and screen lock pin because I needed to get into my phone quickly thought the day.

When I set it back up in the evening the screen unlock was not behaving normally. I Cannot recall exactly what the behaviour was.

Overnight would have been the first time it went to first unlock mode.

groupby64

de0u
Do you mean repeat the sideload procedure again?

de0u

groupby64 Do you mean repeat the sideload procedure again?

Indeed.

Did the first one complete without an error?

groupby64

de0u

It did and so did the second.

groupby64

I get this when I run

'.\fastboot.exe getvar all'

in powershell

current-slot:a
slot-successful:a:no
slot-successful:b:yes
snapshot-update-status:snapshotted

Does this mean my phone is trying to load into A but is not working? B is working?

Can I force load B? or update A?

Did the phone fail during an update?

de0u

groupby64 snapshot-update-status:snapshotted

I don't know what "snapshotted" means.

groupby64
current-slot:a
slot-successful:a:no
slot-successful:b:yes

I believe this means that the bootloader believes that an update is in progress, from B to A, but believes that A has not successfully booted.

I think that in theory after some number of attempts to boot A without success the bootloader is expected to switch back to B. But I don't know how many that is, nor do I know whether "snapshotted" might be a problem.

You might try letting it bootloop for a while (maybe 30 times?) to see if it does switch back to B. And maybe a developer will comment.

groupby64

de0u Hi. I tried that but it did not do anything. I have also tried a more recent OTA update. Very frustrating. Anything else I can try to get my data?