This morning I tried to update /e/OS on a FP3. On reboot I got the "Can’t load Android system… " message. Spent the last 4 hours trying to flash the /e/OS back onto the device but to no avail. Now I fear I have to reset to factory data. I fear I will lose everything I spent years collecting, contacts, notes, files all of it.
I have the adb fastboot tools installed on the same ubuntu PC I used to install /e/OS with the first time but any fastboot command I give results in . If I restart the phone in recovery, go to Apply update from ADB and do “adb devices” in terminal I do see the phone listed. Any Fastboot command still gives .
Sort of on the end of my rope here. I tried running fastboot as root this gave the same result. Am I totally screwed now or am I still missing something?
It seems I am one step further now. This whole time I started the phone in fastboot mode but then went into recovery mode and tried to flash from there>Apply update>apply from adb. It seems fastboot commands work wehn you stay in the fastboot mode menue on the phone.
Now however I see active slot is A but when I do
fastboot flash system system.img
Sending sparse ‘system’ 1/4 (522236 KB) OKAY [ 15.724s]
Writing ‘system’ FAILED (remote: ‘Partition flashing is not allowed’)
fastboot: error: Command failed
That ‘fastboot flashing unlock’ command erases your userdata! Others with this problem, try to set the other partition active first before erasing data: fastboot --set-active=b or fastboot --set-active=a
thanks, but your warning was too late. It seems I have deleted all my data. I guess I am back where I was this morning. #fubar
if unlocking erases data why is there the fastboot -w command to start with. I hope I have a copy of my contacts from a year ago somewhere otherwise I am pretty much screwed out of all my previous data now. Also I have no idea how to prevent this from happening next time I get an update notification. Having serious doubts whether /e/ is for me.
The fastboot -w command is there to wipe userdata. Not all users unlock their phone because they may already had done this. So fastboot -w is meant for first install. In this case there was an incident the OTA was corrupt, and that resulted in a non booting phone as you experienced. Now the solution for this would be to set the other partition active again (the software before the update is still there).
Please consider this as an incident, i’m sure the /e/ team is improving their workflow. I don’t work for /e/ just a volunteer, but hope you stick with /e/.
Where can I find the October 30 update? My phone is still on 0.12-202010376806 and preferences/System/Updater/reload doesn’t find any new updates (last checked: 1 November 2020 8:03). I don’t mind doing a factory reset. It is worth it for me to not have to have the new MicroG. It would be nice not to carry two phones to have the Corona Warn App along with me.