Was this the screen you were getting:
https://source.android.com/docs/security/features/verifiedboot/boot-flow#locked-devices-with-custom-root-of-trust
If so, that’s completely normal.
Have you tried unplugging the phone and holding either Vol. Up / Vol. Down while plugging it back in?
Yes, I got inside bootloader and recovery. Sorry I was panicing a bit. So nothing bricked indeed.
I still get unlock_ability 1 on bootloader. The problem it’s jsut that Calyx Os doesnt boot. I’ve tried factory reset too but it loops on bootling fairphone screen. Why is it?
I should be 100% able to unlock it again, but I want to understand what is happening.
I got LOCKED devices with custom root fo trust
Thank god 
You just booted from the Magisk boot.img, right?
I would unlock it, install Calyx again and repeat the process.
That’s what you want 
AAHHH okay that makes sense!! When i should uninstall magisk then? Because one thing is sure, I have to use magisk to set unlock_ability = 1.
Or maybe can’t be locked?
Just follow the tutorial I linked to before and use the newest Magisk and this patched boot.img:
If you flash the image instead of just booting it, you modify the boot partition, changing it’s hash and breaking Android Verified Boot in the process. In that state you indeed can’t lock your system, as is to be expected.
I am not very lucky… I tried beta version without success. Now I just used this new method device-flasher.linux from Install on Fairphone 4
When I run it (with OEM unlocked and USB-debug) I get:
Android Factory Image Flasher version 1.0.6
Extracting FP4-factory-22402070.zip
Verifying platform-tools_r33.0.3-linux.zip
Extracting platform-tools_r33.0.3-linux.zip
1. Connect to a wifi network and ensure that no SIM cards are installed
2. Enable Developer Options on device (Settings -> About Phone -> tap "Build number" 7 times)
3. Enable USB debugging on device (Settings -> System -> Advanced -> Developer Options) and allow the computer to debug (hit "OK" on the popup when USB is connected)
4. Enable OEM Unlocking (in the same Developer Options menu)
Press ENTER to continue
Detected **my-S/N**. No matching factory image found
No devices to be flashed. Exiting...
Press enter to exit.
Looks like a fastboot issue to me, do you get anything for fastboot devices (after adb reboot bootloader)?
If you don’t, try different USB-cables / -ports, fastboot can be a bit picky sometimes.
Running the flasher as root might also help, if you don’t have the right permissions set up.
For some reason I just tried again and it went to unlock the bootloader. Now I got stuck in the next step bootloader (critical) - this is new to me.
Unlocking FP4 6551379f bootloader...
5. Please use the volume and power keys on the device to unlock the bootloader
Unlocking (critical) FP4 6551379f bootloader...
5.1. Please use the volume and power keys on the device to unlock the bootloader (critical)
My phone just restarted in factory reset after bootloader was unlocked. No Calyx, the installer shows no error or progress.
That’s a known issue, the FP4 doesn’t reboot into fastboot after unlocking the bootloader / critical partitions. The devs are looking into it.
If your phone booted to userland (normal Android), keep the device-flasher running and reboot it to fastboot by holding Power+Vol. Down, let go of Power as soon as the screen turns black.
If you have stopped the device-flasher, or you have further issues, just run it again.
I tried to follow the advice when i ran ./flash_all.sh the laptop stopped recognizing the phone and i can no longer get the laptop to ask the phone to go to fastboot, what do i do? I would seriously appreciate any help
Welcome to the community 
In what state is your phone right now? 
Don’t follow the steps above, that’s the old way, the FP4 is now supported by the (much safer) device-flasher, have a look at the official instructions.
When i originally tried to follow the original instructions i after running device-flasher i just got Android back as a factory reset like when i first bought it.
So i tried to do something else and found this article. Thank you for the response i really hope for some guidance on how to solve the specific problem im facing right now. It used to be able to go to fastboot menu but my computer doesnt even recognize the device anymore after running the command /flash_all.sh. on step 8. it only lasts turned on for a few seconds (im attaching a picture from using a friends phone) but then restarts over and over again. I dont know what to do. Living in the American continent getting this phone was not easy. id appreciate help i cant find anyone around that has experience with this.
i can only add one picture at a time so ill try to reply twice
Unplug the USB cable, turn the phone off, hold Vol. Down while plugging it back in. That should get you into fastboot.
Check if your laptop can see it with fastboot devices, if it doesn’t, try different USB-cables / -ports until it shows up.
Next step, stop using flash_all.sh, use 
Make sure there are no spaces in the path you’re running the device-flasher from, it doesn’t like that 
Its beautiful! It works! Thank you 
I installed Calyx OS on the FP4 back when this guide was still the way to go and you couldn’t lock the bootloader. Two questions:
Welcome to the community
Thank you very much for the help! I’ll try it out as soon as I have backed up my data.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.
