Since you tried to reflash to stock you probably don’t need a A.0128 vbmeta.img anymore, right?!
What errors did you get when running the flash_fp4_factory.command script?
If you didn’t get any have you tried changing the slot fastboot --set-active=a? That part of the script is still broken and won’t execute if you don’t have fastboot in your $PATH (if you are on Linux, no idea how that works on Windows )…
I am also having this problem.
I would like to install Magisk 25.2 on my FP4. Since the version newer than A142 for FP4 no longer provide boot.img on kernel source website, I patiently waited for A170 factory image appear on the offline download page.
So I downloaded the zip but flashed stock A142 boot.img back before letting the phone update itself to A170. Then I extracted the boot.img from FP4-FP4D-factory.zip/images to let Magisk patch it. The patched boot does not work. The system UI crashes constantly. I tried again confirming I’m not using the old boot.img. Same thing.
So I looked at the install guide on Magisk github. It suggests in addition to flashing patched boot.img, vbmeta needs to be flashed too with this prompt. So I extracted vbmeta from factory.zip. Now I’m having bootloop suggesting factory reset.
I tried flashing unpatched boot and vbmeta. Does not work. What could I do to save it?
So am I understanding you correctly, that you were running Magisk already? If that’s the case, why didn’t you update using the Magisk app?
Why did you flash the A.142boot.img? Were you on that version before you updated?
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
Entirely optional and you absolutely don’t need to use that for the FP4.
Before we try to get this fixed, could you reboot into recovery and check the third line from the top for the version in your current slot (the last four characters are enough) and the output of …
Because I installed Magisk by patching the boot.img, and the system updater would not let me update with that. Some integrity verification I guess?
The Magisk did not receive update, so no need to update it. The only way to install available in the app is patching boot.img.
The output is:
Finished. Total time: 0.008s
I tried twice flashing A.170 boot & vbmeta before reboot. Still the same prompt.
I guess the auto update worked because I remember the phone loaded and I checked the system information in settings. However the system UI would crash once before loading probably because I’m applying A.163 boot on a A.170 system…?
If that’s the case the act of flashing A.163 vbmeta on A.170 probably the step that broke it…?