4.4.2 failure - what went wrong? Help needed

Hi everyone,

I just tried to apply the 4.4.2 update on my pixel 5 and I got this error that I’ve never had: I got led to a white screen saying RECOVERY
”Can’t load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Reason: init_user0_failed”

Now i am an absolute beginner, installed e/os with a friend who is not available right now. I have no idea what this means, not even what a factory data reset would imply (would that mean the phone runs on google again? really wanna avoid that)…

Does anyone have any ideas of what i should do? Tried again a few times but it always leads me back to this screen… any help appreciated!

factory reset means setting back your userdata - not back to stock rom, back to /e/OS factory state.

there was a similar report for redfin / pixel 5 - Feedback for v4.4.1 and v4.4.2 - #68 by tatrapikao and a similar thread here. None really had conclusions.

Do you have a backup?

2 Likes

thank you, i will read that other thread.
no i have no backup since pixel 5 has no sd card slot (i went for the cheapest refurbed pixel at the time without paying attention ahah) and i use a mac pc so can’t connect the two.

but yeah that’s somehow excuses, i should figure out a way to do my backups so i dont risk losing my data…

thanks for your reply!

on Backup: if you got the extra space on the phone itself, Seedvault can backup to the same storage as the device itself, where you siphon it off with something like synctrain regularly.

If your case is as in the linked thread, there aren’t many explanations online why the f2fs superblock is invalid after the update or reboot. People affected would need to record the superblock and compare what happened.

For me the “solution” was to connect my phone to a computer with the software fastboot installed. As your Phone installs the update to one of two “Slots” (A and B) chances are a working system is still intact on your phone. All you might have to do is connect to a computer with fastboot installed, and switch back to the working slot. That is to be done with the command "fastboot set_active other” from a terminal. After this you should have a working phone again without losing any data. I will wait for the next update and try again. Good luck!

2 Likes

Hi,

had the same twice (4.4.1 and 4.4.2). Seems to be a widespread if not general issue for Pixel 5 and 4a.

Everytime switiching slot worked for me. You can do it as tatrapikao decribed above - or what is easier if you are new to this, after several failed restarts the phone did change slot automatically for me and at one point in recovery it will state 4.2 again and then rebooting is successfull.

Unfortunately the update will keep popping up, so make sure to ignore it until a new version with a fix is available.

Good luck!