I’m on a Nothing Phone (1) Spacewar, with the latest 3.2 community software. Once I updated via wifi I thought I could lock my phone as well. I performed the update as below. This went well up till step 2. after performing step 3 I’n now in a loop where I can only get into the bootloader, I cannot even go to recovery mode.I do get a good response from fastboot devices with adb. When performing ‘fastboot reboot recovery’ the device is rebooting in the bootloader. Any ideas how to get out of this loop?
Reboot your device into bootloader, via a key combination:
With the device powered off
hold Volume Down + Power
In the command prompt, lock critical partition with the following command
fastboot flashing lock_critical
Approve with Volume + then power
In the command prompt lock the device with the following command
Hi @Manoj. You added my question to a new subcategory. But CMF Phone 1 is a different phone than the one I have. My type has become ‘official’ e/os a few months ago. Maybe you could add a new subcategory: Nothing Phone (1). Thanks for the work you put in.
There is no step for locking in the installation guide…
Your device is supported by /e/OS, it doesn’t have official build with which generally locking bootloader is possible.
If you revert locking the bootloader, it should boot again.
Thank you @mihi for your reply and help. You’re right, it was better to not try locking it, but I did. In the mean time I did unlock the device again and reinstalled e/os 3.2-A15.