at first I didn’t notice that, and rebooted too quickly, but then I tried flashing again and that time I waited until the command finished doing it’s stuff. I’m still stuck in a bootloop.
fastboot flashing unlock_critical is apparently one of the commands in the Calyx’ flash-all.sh script already (disregard, that’s the command I tried manually after reading your post, apparently I’m very easily confused):
also, in the output I’m seeing several commands throwing “archive does not contain X” messages, like archive does not contain 'vbmeta_vendor.img'. I’m not sure if it’s a message because of some repurposed script, or am I missing some files, despite having verified the .zip file I downloaded from CalyxOS website.
edit: okay, I had to manually factory reset the phone (I thought the installer would take care of that?!) and it booted!
If you’re still testing, could you please do a test?
Unfortunately I don’t have a test device.
Because of the unlock_ability=0 problem after a first reboot after installation.
Please test if the problem also exists if you don’t reboot via the extended boot menu, but always just run the “adb reboot” instead.
If it makes a difference, it would also be interesting to see if it is the same in iodéOS and FPOS.
That shouldn’t make a difference, I always run adb reboot / fastboot reboot instead of using the menu when flashing devices
But since I wanted to test what happens if you don’t reboot anyways, might as well test if there is different behaviour somewhere
I’ll follow this up in the other topic, since I’m only testing FPOS on the other device for now.
Edit: Just to clarify this part:
get_unlock_ability gets reset on the first regular boot, so once you reached full userspace it’s already too late. Or did you mean something else with extended boot menu?
My thoughts were as fallows:
Is there maybe a difference to reboot, after first restart, in bootloader to unlock to bootloader if you restart via extended boot menu “long press power buttton/restart/bootloader” or via “adb reboot bootloader”?
Is in both situation the unlock_ability reset to 0?
I’m still not entirely sure what you mean by extended boot menu, sorry.
If we are talking about the menu that pops up when long pressing the power in a regularly running system, you already went to far to prevent it. The same goes for adb reboot, at that point the flag has already been changed.
If you mean the bootloader menu, I have tried every possible way to reboot the phone before the first start, as documented in the other thread. As long as you don’t boot into proper Android it’ll stay on 1, as soon as you start the regular system it’ll change, haven’t found a way around it (yet)
those of your who run Calyx, have you managed to make the phone find the update? I’ve been checking for the past few days with no results. Calyx doesn’t support root and/or unlocked bootloader, so they won’t assist with that.
Nope, it works just fine unlocked
The installer only fails because it’s checking the hashes for the partitions it should be updating and since Magisk changes the boot partition it will stop and throw an error.
good to know that there’s a workaround! out of curiosity though, what images does the “restore” part refer too? is it just the stock boot.img? because it looks like I don’t have it on my device since I just flashed the one you’ve posted earlier in the thread and Magisk complains about about the lack of a stock backup. but if it’s just that, then I guess I’ll just get the one packed in the .zip from the Calyx website and follow the rest of the steps properly.
When you reinstall Magisk, I would go the fastboot boot route, makes OTA updates a lot quicker.
There’s also the option in the app to install Magisk to the other slot after an update and before rebooting, but I haven’t tried that yet. Not sure if Android Verified Boot likes a patched boot partition on the first boot after upgrading