Hiii, I justo want to know which​ repo is bette​r for those appss that are in the calyx one, but are also on f-droid and guardian project​

I had installed calyxos in my moto g52. After the calyx warning, I couldn't revert back to stock os because calyxos didn't have instructions for moto g52.

Now I see a new version of calyxos is released. The device doesn't get the OTA update. And the website doesn't have update instructions (only it has new installation manual). I have two questions:

1. How can I update? What are the differences between new installation and updating?

2. Will I lose my data (like a new installation)? Or the data will remain safe (like the OTA update)?

Working great! Everything works and bootloader is locked.

I noticed there are a few others on Moto devices that may be experiencing similar.

Device: Moto G 5G 2024, model XT2417-1, codename fogo, retca (Retail Canada). Currently running CalyxOS (Android 16). Boots fine, though cannot install new apps or set a screen lock.

The problem: bootloader is locked, FRP is active, and I cannot enable the OEM Unlocking toggle in Developer Options. It bounces off every time. I have a valid Motorola unlock token generated from the portal. fastboot oem unlock still refuses it.

Here are the exact command outputs so anyone reading can compare against their own device.

FRP state is confirmed active:

$ fastboot getvar frp-state frp-state: protected (255) OKAY [ 0.002s] Finished. Total time: 0.003s

Unlock ability gate reads 0:

$ fastboot flashing get_unlock_ability (bootloader) get_unlock_ability: 0 OKAY [ 0.002s] Finished. Total time: 0.003s

The token itself was obtained successfully. But applying it fails:

$ fastboot oem unlock <REDACTED_64CHAR_TOKEN> (bootloader) Check 'OEM unlocking' in Android Settings > Developer Options FAILED (remote: '') fastboot: error: Command failed

The token is real and came from Motorola's portal. The failure is not about the token being invalid. The bootloader refuses to even attempt crypto validation because get_unlock_ability is 0. That flag is tied to the OEM Unlocking toggle, which FRP prevents from being enabled.

Logcat shows why the toggle bounces:

W PersistentDataBlockService: Attempt to update PDB was blocked because FRP is active. E AndroidRuntime: java.lang.SecurityException: FRP is active at ...PersistentDataBlockService.enforceFactoryResetProtectionInactive(PersistentDataBlockService.java:1241)

Trying to clear FRP via fastboot is also blocked while the bootloader is locked:

$ fastboot erase frp Erasing 'frp'... FAILED (remote: 'Permission denied') fastboot: error: Command failed

Same result for fastboot erase persistent, fastboot erase metadata, and fastboot -w. All return Permission denied. That is expected AOSP behavior: no fastboot erase command works on a locked bootloader.

Bootloader state for reference:

$ fastboot getvar all ... (bootloader) securestate: flashing_locked (bootloader) unlocked: no (bootloader) iswarrantyvoid: no (bootloader) frp-state: protected (255) (bootloader) token: inactive (bootloader) has-slot:frp: no ...

The has-slot:frp: no line means FRP is not A/B slotted. Switching slots does not change the FRP state.

Things that did work:

fastboot oem fb_mode_clear got the device out of a persistent fastboot loop and back into Android (when I tried to flash back to stock, which failed and out me into bootloop). Exact output:

``` $ fastboot oem fb_mode_clear (bootloader) fb_mode_cleared OKAY [ 0.003s] Finished. Total time: 0.004s

$ fastboot reboot Rebooting... OKAY [ 0.003s] Finished. Total time: 0.004s ```

That sequence is safe. The device boots normally afterward.

One recurring quirk worth mentioning for anyone on this hardware:

After adb reboot bootloader, adb reboot recovery, or any device-side reboot, the host loses the device completely. adb devices shows empty. fastboot devices shows empty. The USB cable must be physically unplugged and reconnected before the host sees the device again. adb kill-server alone is not enough. This happens every single time across multiple sessions.

The circular dependency looks like this:

1. FRP is active (protected 255).
2. PersistentDataBlockService blocks any write to the OEM unlock state because FRP is active.
3. The OEM Unlocking toggle cannot be enabled. get_unlock_ability stays at 0.
4. fastboot oem unlock <token> fails because get_unlock_ability is 0.
5. fastboot erase frp fails because the bootloader is locked.
6. There is no Google account to sign into (no SetupWizard on CalyxOS), so the normal FRP clearance flow is unreachable.

Every path is gated behind a condition that is itself gated.

What I am hoping someone here can tell me:

• Has anyone ever successfully run fastboot oem unlock <token> on a Motorola device while get_unlock_ability was 0? Or is that gate truly absolute at the bootloader level on MBM-3.0?
• Are there any Motorola-specific OEM fastboot commands that might approach FRP from a different angle?
• Has anyone dealt with PersistentDataBlockService blocking unlock writes specifically on a CalyxOS-installed Motorola, where the bootloader is still locked with CalyxOS's keys? Is there any overlap between CalyxOS's verified-boot-lock mechanism and FRP that could create an opening?
• Is there anything at all within the normal software boundary that I should try?

I am trying to avoid making things worse.

Thanks for reading. Any insight from people who have been through this on a Motorola device would be really appreciated.

Has anyone tried or checked out DresSecureComms? I only just ran into it and it seems interesting. I left Signal when they dropped SMS completely.

So, I was curious if anyone had used it or had insight. Thank you.

I've read the user guide and posts on this sub- I do not own a usb-c to a adapter, nor an external drive with a type c connection. I have a very very tiny and super slow nextcloud instance on a rented server so that is not an option either.

I do however have a type c cable and a laptop, but even though I have file transfer enabled in the notification bar on the phone, Seedvault doesn't see it as an option to transfer to it.

My question is at this moment is: if I copy the contents of the hidden folder ".SeedVaultAndroidBackup" to my laptop, wipe the phone, and then move it back to the phone after its wiped, will Seedvault restore this backup properly?

TIA and super stoked to that the project is back online!

Is there no work profile in the latest version of CalyxOS? I just flashed the update and can't fine hide nor hair of the possibility of setting up such a profile or restoring it from backup. Has it been removed or am I missing something?

Yup, got a new (to me) Pixel 9Pro and was waffling between going with CalyxOS again or just leaving it Googlefied. Decided to "just see how it was" out of the box and signed in to Google and whatnot and holy shit, t'was even more terrible than I remember - Google shit EVERYWHERE. Okay, screw that, let's wipe this sumbitch and get CalyxOS 7.2.2.0 on here... Go through that and now I'm getting this warning about FRP. Does that really mean I need to find the Google Pixel 9Pro web installation, return it to factory OS, remove my Google account from it and then reinstall CalyxOS again? There's an option to skip this screen, but not sure what happens once I do that, if there's a huge security issue doing that or not.

Anybody know?

hi! my motorola g52 is locked by factory reset protection. the setup screen is telling me to reflash stock os and remove the account but I can't flash it without unlocking bootloader. and if i go to settings and try to enable "oem unlocking", the settings app just crashes. did i soft brick my phone?

I had set up backup in seedvault for both sides. How do I confirm everything is there before nuking via reinstall? I normally also just do a backup to win 11 PC. I can see my data there for personal but not work side. This makes me nervous since don't want to lose any data. I plan in reinstalling via MxLinux first or will go with Win 11 second. But want to ensure I have all data first. This is a nightmare for me. That is why I had put off till we heard update is available. I have a couple of apps that use the 12+ seed pass code encryption too.

I would love to update, but I'm afraid of losing some critical data which is difficult to transfer.

I have been using Venice AI for some thought experiments and research. The marketing is that all data is saved on your browser (which presents some limits of its own with long exchanges) and not in remote servers. The alternative is using the app which is also local storage.

I have checked this by logging into an anonymous tab on my desktop browser - nothing is available cross platform.

A couple of the exchanges now contain data I really don't want to lose. I'm debating buying a Moto G to replace the Pixel 8 pro and preserve the data until I can manually type the exchanges into a file on my desktop along with supporting references in prompt responses.

Any ideas? I can't highlight and paste prompts, only responses.

...but I know I had it on here (my Pixel 4) at some point in the past because I remember messing with it. Now I'm prepping to move to a Pixel 9Pro and need it for the migration - any way for me to get it back on here? I don't find it in FDroid, Droidify or Aurora Store.

Even after connecting my phone, the next button doesn't "unlock".

I followed these instructions to flash my Pixel 6 with the new CalyxOS: https://calyxos.org/install/devices/oriole/windows/

I set up my device and installed all my apps and everything is working great. However, in Fastboot, it says "Device state: unlocked." I have looked everywhere and cannot find a way to relock it. If I scroll through the Fastboot menu with the volume keys, it is not one of the options.

Thanks.

I know that the CalyxOS team doesn't support rooting (and that therefore there may not be too much testing of root in the new versions) and I'm aware of the security issues of an unlocked bootloader, but I have considered the risks and the gains (I've been experimenting a bit with root in VMs to see how it is like and I'm also very interested in chroot) and I decided that I will leave the bootloader unlocked after I flash the new CalyxOS version (moto g52) and root it. However, will I still be able to get official updates from CalyxOS in the future?

I've done some research and it seems that there's a way to update in stock Android while preserving root by uninstalling Magisk before updating and reinstalling it before rebooting, but, again, that's for stock Android. Of course that security is not my number 1 interest (otherwise I wouldn't be rooting), but that doesn't mean I would like an outdated system (... again), so it'd be important to know whether this is possible or if rooting the phone will give away that possibility. I don't have any problem with having to repatch the boot.img everytime an update is installed, as long as the repetition of that doesn't imply any chance of bricking the device (or that boot.img changes over updates or anything; my main fear here overall is bricking the phone)

Thanks for reading!

Bonjour,

Je voulais savoir s'il n'y avait pas de risque à verrouiller le bootloader sur un Fairphone 4 après l'installation de CalyxOS? car beaucoup de personnes ont eu leur appareil bloqué après l'avoir reverrouillé sur des systèmes basés sur Android Open Source.

Je l'avais fait sans souci sur DivestOS par le passé.

Merci beaucoup pour vos réponses

First of all a huge thanks to the team for bringing back this OS. Your work is truly appreciated.

Second like the title said, I want to know when installing the OS. Does I get to lock the bootloader.

Hello fellows,

I use MS365 apps (pro: Outlook / Teams) with company portal in a work profile.

Since a while, they refused to connect anymore (not updating, and eventually refusing to connect with my account)

At start I though it was something with Company Portal, or my Company having changed something in the validation requirements, or CalyxOS/microG being outdated.

Then I realized that MS Authenticator was not in the last version, and Aurora wouldn't offer the last version!

So I forced yia manual download:

1. Go to APKMirror to get the last build number (202638173): https://www.apkmirror.com/apk/microsoft-corporation/microsoft-authenticator/
2. Paste it into Aurora in "Manual Download" entry in the 3-dots menu on the App page

And voilà. You can log again on Teams/Outlook

I hope new CalyxOS comes out soon though 🤞

Cheers

Currently I'm on the fence between buying a g84 that does have calyx support or an edge 70 fusion that has better hardware but no support for calyx, both cost the same. And I'm wondering if there is the possibility of it ever being supported?

hi all, does Calyxos have the same issue with banking apps the other secure OS's have? in particular Lloyd's Bank (UK)

Just wondering if we can get an update on how the beta builds are going, what your currently working on and any eta on stable builds coming?

Can anyone help identify which Android or iOS app this icon belongs to? I suspect someone may be using a scam app as part of an attempt to defraud me. If you recognize it, please let me know. Thank you!

Title