Great you got it working again
I wouldn’t worry to much about the unbootable slot, it will be reflashed with the next system update anyway. But if it bothers you, you could always extract your working slot and flash it onto the other one. I wouldn’t but you could
Backup a copy of your working slot though, just in case.
Aha sounds interesting, but for my understanding the slot don’t contain the whole rom? I am on A94 boot is your earlier root guide still working? I really want to try it but i don’t want to damage my mobile. I always root all my mobile phones.
Yes, those A / B slots only contain the boot partition. When performing a system upgrade the new boot.img (so your kernel and related stuff) get written to the unused slot and at reboot your system changes to that slot. Other A / B slots (like modem, recovery…) might be updated as well, depending on the update.
I don’t know of a method to completely dump your whole system at the moment, certainly not into a reflashable custom rom kind of image. Maybe it’s possible with TWRP, haven’t looked into it. The only available TWRP for the FP4 doesn’t have access to encrypted /data anyway, so no reason to try
I can’t tell you if root still works on A94, my provider apparently doesn’t want me to update just yet. But I see no reason why it wouldn’t and early reports seem to indicate it does.
If you aren’t comfortable on the command line and with some hands on troubleshooting I wouldn’t suggest rooting at the moment, since there are still no easily flashable rom images available to recover from some worst case scenarios.
I am familiar with Linux and commandlines input but not an expert in it. I guess I wait some more. It should be possible soon to reflash everything when things go wrong. Many thanks for the information and giving root as an option.
I can confirm root works with A94.
As for the update not showing up you might have the same issue I had, rooting and messing with gapps basically seemed to prevent the update to show up.
I wiped my phone (after breaking too many things by trying to get Google maps to work with microG) and the second my freshly wiped device grabbed an internet connection, the update showed up…
thank you very much!
however unfortunately it didn´t work out for me.
previously on FP4:
I was rootet on magisk for 2 weeks with A.067 image and everything was nice with lawnchair etc.
I used Titanium Backup and it looked like it worked. Except MiXplorer - search didnt work
Deactivated majority of google apps - no MicroG
for the update:
first: I tried factory reset only. Update failed.
second: I returned to stock boot.img (my build no. is quite strange: A.081) according to your prescription. no wifi, no sound any more.
first notice after reboot always: UI crashed (but it works fortunately)
third:
I tried to switch to slot b
after reboot its again in slot a
Thanks, Hirnsushi!
I just did again a factory reset.
Still no wifi, no sound, no phonecalls…
Yes, according to rar0 instructions I flashed the image. After I renamed it to A.081…
I remember your root post of warning not to flash, but I thought, rar0‘s image was different and ok to flash.
I think I flashed all three images from FP homepage:(
Have you tried flashing one of the images I uploaded?
Those are the boot_a and boot_b my device shipped with and at least one of them is a build between A.067 and A.091, so may well be your A.081.
Or you can tell me the security patch level of your A.081 build (Settings->About phone->Android version->Android security update) and I can tell you which one it should be.
Please try boot_a from my upload, that’s patch level September.
A.067 shouldn’t be used for anything apart from temporarily booting and using that to install Magisk. That build is ancient, patch level July, I’m pretty sure no device shipped with that.
When I wrote my initial instructions, that was the only image Fairphone had made available.
That should match the boot_a I uploaded. What happens if you flash that?
If it doesn’t work, make sure it actually gets flashed to the right slot (the slot might be chosen based on suffix ) either rename it to your current slot or in fastboot do: