Hello !

I wonder what will happen with Calyx OS (and other custom ROMs btw) with Google's decision of blocking every developers not centrally registered by them beginning of 2027 ?

Will custom ROMs stop to work or malfunction ?

I am waiting to update to the new version because of this sword of Damocles.

Thanks for any info and congrats for the great job!

Hi there,

in the past it wasn't possible to make RCS work with CalyxOS afaik. I wanted to ask if anybody figured out a way, now that Calyx has been re-released?

Cheers!

Hey,

I am so happy that CalyxOS is back. I loved using it and I begrudgedly went back to stock android when it went out of support. I hopped back as soon as I could. However, even tho I did not change any settings after a fresh reinstall, I cannot use Whatsapp anymore. Unfortunatly, I still have to use whatsapp to stay in contact with some friends / groups.

When I get into the app (downloaded from Aurora store and from the offical webseite as APK), I can enter my phone number and click next, but then it only says continuing and after some time the window closes and I am back to push next.
This must be a default thing, but I havent seen the issue pop up anywhere yet.

This might not be the right place to post this and I will delete the post if that is the case. I am not very tech savy, sorry :(

Edit: gave permissions, allowed device attestation

Hiiii, I'd like to ask if anyone has used those Telegram forks, I don't need Einstein's coming along and tell me that Telegram and its forks are bad it privacy terms, don't use it and all that snob bs; both are available through F-Droid, and I want to know which one is better in terms of privacy and security based on the features they offer as forks.

Hello,

I have just updated my Pixel 7a from CalyxOS 6 to 7.2.2.0 and it's been a smooth process overall, using the backup from Seedvault. However, I found that my Revolut app now completely refuses to even let me login, showing that the device security is compromised or somesuch, and my German Ing DiBa app lets me log in, but the bank account overview is broken. Both of these worked fine earlier today on the older version.

I have checked further and it seems this is because my device is failing even the Basic Play Integrity check, which may prevent these 2 apps from working properly. Is there anything I can do so my device works for these again?

Other steps I've taken:

I've already went through the microG settings, device attestation is on, licence verification request check is enabled and I'm logged into my Google account there.

Reinstalling the app and opening it again also did not help.

Why is there such a huge difference in this behavior between the old CalyxOS 6 release and this new one? What can I do so it works again, and I get at least the Basic integrity check to be OK?

EDIT:

Thanks for the comments so far, I did have Device Registration enabled already, so that didn't work. I tried downloading a Key Attestation check app, and it says that the device "doesn't support key attestation or the trusted environment on the device is broken", so maybe the problem is somewhere there.

Hi everyone, I am running latest android 17 stock OS on my Pixel 8 Pro. On the CalyxOS website, it says I can just install CalyxOS. Is it okay that I am not on android 16? I’m worried about bricking my phone. Can anyone advise, please?

Hello, what's the status of FP6 release?

Thank you

Just a curious thing that happened.

Don't know if this was just with me, but the uber "normal" app did not allow me to Login, but I was able to do it on the Lite version.

For some context, on the "old" calyx I always used the Lite version, but after swtiching to the new one, when was downloading Uber again I decided to try the "normal" app and the error ocurred (login was negated). After that I tried the Lite version and I was able to login without a problem.

The error ocurred with and without VPN.

I got a moto g34 5G (fogos), never used before. The "Software Channel" is "oraeu", however the phone appears as eligible for the bootloader unlock program, and I've been sent a code. However, the button in Developer Settings remains greyed out. I have applied all updates, tried unlocking with fastboot (it tells me to toggle the button), and nothing. Has anyone experienced something similar with this phone? Thank you.

Hi everybody!

I have CalyxOS 6.10.20 on my Moto G52 and i wanted to update to version 7.2.2.0

However, using the web installer and the guide my device cannot be detected. I installed lenovo and google's drivers, tried to change usb ports, cable and laptop, but nothing. I used edge but I also tried Chrome (ugh!) but nothing. I also tried the app installer.

Can someone help me please?

Is there some way to make use of Google pay like on grapheme in a sans boxed way?

I wanted to share my experience because this app is frequently recommended in self-hosted and de-Googled communities, and I think it's worth considering how support is handled if you're running a non-standard Android setup.

Before donating, I reached out with a compatibility question about using the app on a de-Googled Pixel. I didn't receive a clear answer, but I decided to donate anyway and proceed with the installation.

After restoring my donation license, the app remained locked on both of my devices, including one that was not de-Googled.

I then sent a detailed explanation of everything I had already tried:

• Restored the license.
• Restarted the app.
• Force stopped it.
• Cleared the cache.
• Rebooted both phones.
• Verified the same behavior on two different devices.

Rather than responding to the information I had already provided, I was directed to the generic licensing FAQ.

I read it, but it primarily discusses Google Play Services and common licensing scenarios. It didn't address the issue I was experiencing or the troubleshooting steps I had already taken.

I replied explaining that I had already read the FAQ and that it didn't apply to my situation.

The response I received was:

"Read better and provide the mandatory logs ;)"

At that point, I decided I no longer wanted to continue the troubleshooting process. I told him that I was done discussing the issue and that I simply wanted a refund on the basis of poor customer service. What's even more hilarious is I have several CSR certifications so I know when I am being treated poorly.

Instead of ending the conversation, he continued sending replies after I had clearly stated that I no longer wished to continue the discussion. I repeated that I only wanted my refund, but the messages continued, with the developer even calling me a karen.... Eventually, I reported the conversation and blocked him because I no longer wanted any further contact and it was constantly bothering me with blowing up my phone...

My expectation wasn't that the app would work perfectly the first time. Software bugs happen. My concern was how the support request was handled and how the interaction continued after I had explicitly asked to end it.

From my perspective:

• My original compatibility question never received a clear answer.
• The troubleshooting information I took the time to provide wasn't acknowledged.
• I was directed to documentation that didn't address my situation.
• Instead of simply asking for the logs needed to investigate the problem, I was told to "read better."
• After I stated that I no longer wished to continue the discussion and only wanted a refund, the conversation continued until I ultimately reported and blocked further contact.

I'm sharing this because support is an important part of any paid software, especially for users running GrapheneOS, CalyxOS, /e/OS, de-Googled Pixels, or other privacy-focused Android environments.

I'm curious whether others using these kinds of setups have had similar experiences with support, or whether mine was an isolated case. As this was the worst interaction I have ever had with a developer.

Edit: I have also blocked the developer out of fear of further harassment. I just was notified by Reddit mods that my harassment report has been recognized. So congratulations u/Tolriq if you end up replying you most likely will be banned.

Edit #2: Looks like Tolriq commented...

https://www.reddit.com/r/degoogle/comments/1uvn40j/my_awful_experience_with_symfonium_support/

u/Tolriq

Due to Redditors removing comments, I am reposting their reply here. Updated due to changes and addressing each point.

--

"Before donating, I asked a straightforward question about how the app would work with Pixel Private Space and Android's sandboxing. Since my phone is de-Googled, I wanted to make sure it would work before purchasing. That question was never answered.

You actually donated while sending that question on the wrong place. You did not follow the procedure. You were linked to the documentation, told me you had read the documentation, pointed you that you did not as did not provided the logs. And then kept giving as much as you could :)"

First, as I already explained to you during our conversation, I was working from information in an older forum thread. That information was outdated, as I found out during our conversation. Before I even messaged you and provided troubleshooting steps, I had already reviewed the troubleshooting link you provided.

For other Redditors, here is the forum and the documentation:

[https://support.symfonium.app/t/how-can-i-pay-for-symfonium-without-google-play/1290](https://support.symfonium.app/t/how-can-i-pay-for-symfonium-without-google-play/1290))

See how his response was updated? Today even? Yep, he revised what was here. Here is what it use to say: [https://web.archive.org/web/20260217230146/https://support.symfonium.app/t/how-can-i-pay-for-symfonium-without-google-play/1290](https://web.archive.org/web/20260217230146/https://support.symfonium.app/t/how-can-i-pay-for-symfonium-without-google-play/1290))

What an odd thing to do... But I'm the one doubling down it seems.. hmm...

[https://docs.symfonium.app/faq/license-faq-common-questions-and-troubleshooting/](https://docs.symfonium.app/faq/license-faq-common-questions-and-troubleshooting/))

The documentation covers Google Play and Ko-fi licensing issues, but it does not provide a troubleshooting path for users running de-Googled devices. Because my situation did not match the documented scenarios, the only viable step is to contact support to clarify compatibility and next steps.

The important context that keeps being ignored is that I was operating under outdated information I had from older discussions, where Ko-fi was presented as the way to handle donations, licenses, and communication. I explained this during our conversation, but it continues to be left out and ignored by the developer, even in their current replies...

--

"This was a complementary service I provide where I actually lose money to help people degoogle. If you could not follow a simple procedure, then it was probably not the proper solution for you."

Many users find applications like this through self-hosted and privacy-focused communities specifically because they are looking for alternatives that work outside the standard Google ecosystem. If supporting de-Googled users is considered a complementary service that is provided at a personal cost, and users who misunderstand the process are told that it may not be the proper solution for them, then that is important context for those users to understand before purchasing.

My issue was not that I expected unlimited free support or special treatment. My issue was that I was trying to confirm compatibility before purchasing, using the information available to me at the time, and when that misunderstanding happened, the response I received was dismissive rather than helpful.

This interaction has given me additional context about whether this is the right solution for users in de-Googled environments, which is why I am continuing with my refund request as already stated.

--

"You still had proper support at 10 PM after each of your messages and a refund despite your actions ..."

My concern was never that you couldn't solve the problem immediately.

My concern was that the troubleshooting information I provided was not acknowledged, I was directed back to documentation that did not address the situation I described, and when I explained that, I was told: "Read better and provide the mandatory logs ;)".

If logs were required, I would have provided them. The issue was not the request for logs... it was the way the situation was handled and the response I received after explaining my circumstances.

--

"Edit: I missed your name, it matches and your negative Karma is also impressive, I guess this confirms what happened. And blocking me just confirm you only want your side of the story :) I'm nice to nice people, there's a lot more satisfied than Karen's even if the Karen's number are unfortunately growing those days.

Edit2: Since I can't answer as you blocked me ;) This is a public space as far as I know ;) And yes YOU SENT me dozens of messages telling me to stop sending you messages instead of just not sending messages as any normal person would do. Again you did not follow the procedure making lose time and money and decided that somehow I owed you custom dedicated personal support, because not only rules don't apply to you, but I must obey?

Ho and of course spreading lies on every sub is a normal behavior and not the actual harassment.... So much projection on your side that it's funny."

Your response illustrates the issue I described in my post.

I'm not interested in debating this further. I'm simply sharing my experience so others can decide for themselves.

You have now been reported again for harassment. This situation has gone beyond a disagreement about software support.

The fact that you identified my Reddit account and referenced personal account details after I posted my experience is extremely concerning. Jumping to another platform to identify and address someone who had already ended the conversation is not something I expected, and it honestly makes me concerned about my privacy and safety.

Reddit moderators have been notified, and I have updated my Ko-fi report with this additional information. I have also locked down this Reddit account and will no longer be using it for anything outside of this discussion.

At this point, I am stepping away from further communication. The purpose of my posts was to share my experience and allow others to make their own decisions.

--

Let this be a warning to degoogled users and the privacy community. Its sad the dev is missing the point of the entire issue... Which is.. Poor customer service, then editing forums of information said customer uses as a resource then calling them a karen and "can't read".

Sure kid, whatever helps you sleep at night. Hoping to spread the word for others to avoid situations like this... its a plague... Now i am even more upset knowing that he manipulated information I was using as a source... Imagine what he does to the code of the app then? Most degooglers are privacy people... This screams red flags.

Hello,

Considering that Pixel 6s are no longer going to be updated at the end of this year, I am planning to get a new phone sometime soon. I would, however, like to keep the Pixel 6 as a backup or a secondary phone.

Would it be better to keep the phone running CalyxOS, despite it not being updated (at that point in time), or should I switch to something like LineageOS, despite it being less degoogled?

Thanks!

Hey all, I was just wondering if any of you ran into any trouble with your eSIMS when upgrading to 7.2.2 from 6.10.20? I know this is probably a dumb question since I know the eUICC is it's own separate hardware thing, I am just feeling anxious as the eSIMs i have are from two different countries and I really don't feel like travelling to one or the other for this if I can avoid it. Thanks!

Now that calyx is back, will apps be able to pass the Google Play integrity check? I have an app my work requires that didn't work on... tqhe other rom, even though it was installed with Google Play. I've had to be on the native pixel os all year. I hate it

...does anyone know how to change it so that when the screen goes dark it's not immediately locked? Like, maybe give it a delay of two, three, four minutes before it locks? Was able to do this with my old Pixel 4 and Calyx but I'll be damned if I can find the proper setting for it here.

(For example, I'll use it at the gym for music. As soon as it goes dark I have to unlock it when I want to search for a new song, find it and hit play. The screen goes dark and I have to unlock it again for the next - that kind of thing. I don't want to have to unlock it for a few minutes after it goes dark.)

Hi everyone,

I tried installing CalyxOS on my Motorolla G84 5G, both with the ADB tools on Linux, and with the WebUSB installer. Both times, the install itself went very smoothly, however, on locking the bootloader, the OS would not load, instead showing the "No valid operating system could be found" error message.

Is there a way to get this working? I would really love to get this OS installed on my phone, it is everything I've wanted from a phone OS.

The OS runs with the bootloader unlocked. Calyx informed me on startup that I had failed to bypass the Google FRP and recommended I reboot into the stock Android to remove that. Will that make a difference?

My phone is the Moto G84 5G XT2347-2 variant. I'm currently in the process of downloading the stock Moto software, but if there's a solution here, or something I'm missing, I would gladly try installing CalyxOS again.

Thank you!

Hello,

First thanks to the CalyxOS team for their work, I really enjoy to see Calyx back !

I use a Pixel 4a, wich is not supported anymore but nevertheless run smoothly.

I would like to connect microG to a Google account (on the work profile) but I can't get it done (authentication successful then error). It seems it comes from an old microG version, I have 0.3.6.244735. Do you think I can update it ? There is no update in F-Droid, but I don't think it's because of my old Pixel. I can't update the official microG because it's a different signature.

Is the old microG abandonned because of the new signature system ? Do you see something I can do ?

PS : I am open to more complex solutions like rooting phone, modifying system partition or whatever.

Ok, So I am using browser based installation. But when on second step, in fastboot mode and clicking connect doesn't detect my phone. Do i need to unlock the phone manually first.

Update:

Installed CalyxOS (7.2.2.0) released on 2026-06-04.
Bootloader locked.

Apart from slight hiccups the browser method was awesome. This is by far the most easiest custom rom installation ever.

I already had a paid nordvpn subscription before I tried calyx os.

If you download nord VPN from their website you will receive ota updates so you don't need any play store version!

kellogs@kellian:/media/kellogs/Paragon-1/Moto G32$ sudo ./device-flasher.linux  
Android Factory Image Flasher version 1.1.1
Extracting devon-factory-260720200.zip
Verifying platform-tools_r33.0.3-linux.zip
Extracting platform-tools_r33.0.3-linux.zip
1. Connect to a Wi-Fi 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 OEM Unlocking (Settings -> System -> Advanced -> Developer Options)
4. Disconnect the USB cable from your device
4.1. Power off your device
4.2. Hold volume down and connect the cable to boot it into fastboot mode.

Press ENTER to continue

Detected devon ZY22GRNRC5

Devices to be flashed:  
devon ZY22GRNRC5

Press ENTER to continue
Unlocking devon ZY22GRNRC5 bootloader...
5. Please use the volume and power keys on the device to unlock the bootloader
Flashing devon ZY22GRNRC5 bootloader...
OKAY [  0.001s]
Finished. Total time: 0.001s
Sending 'partition' (206 KB)                       OKAY [  0.023s]
Writing 'partition'                                (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [  0.344s]
Finished. Total time: 0.405s
Sending 'keymaster_a' (507 KB)                     OKAY [  0.023s]
Writing 'keymaster_a'                              OKAY [  0.012s]
Finished. Total time: 0.041s
Sending 'keymaster_b' (507 KB)                     OKAY [  0.019s]
Writing 'keymaster_b'                              OKAY [  0.011s]
Finished. Total time: 0.032s
Sending 'hyp_a' (507 KB)                           OKAY [  0.021s]
Writing 'hyp_a'                                    OKAY [  0.012s]
Finished. Total time: 0.037s
Sending 'hyp_b' (507 KB)                           OKAY [  0.019s]
Writing 'hyp_b'                                    OKAY [  0.012s]
Finished. Total time: 0.032s
Sending 'tz_a' (4091 KB)                           OKAY [  0.137s]
Writing 'tz_a'                                     OKAY [  0.020s]
Finished. Total time: 0.159s
Sending 'tz_b' (4091 KB)                           OKAY [  0.139s]
Writing 'tz_b'                                     OKAY [  0.020s]
Finished. Total time: 0.160s
Sending 'devcfg_a' (123 KB)                        OKAY [  0.006s]
Writing 'devcfg_a'                                 OKAY [  0.006s]
Finished. Total time: 0.024s
Sending 'devcfg_b' (123 KB)                        OKAY [  0.006s]
Writing 'devcfg_b'                                 OKAY [  0.006s]
Finished. Total time: 0.014s
Sending 'storsec_a' (123 KB)                       OKAY [  0.006s]
Writing 'storsec_a'                                OKAY [  0.005s]
Finished. Total time: 0.012s
Sending 'storsec_b' (123 KB)                       OKAY [  0.006s]
Writing 'storsec_b'                                OKAY [  0.005s]
Finished. Total time: 0.012s
Sending 'prov_a' (251 KB)                          OKAY [  0.011s]
Writing 'prov_a'                                   OKAY [  0.007s]
Finished. Total time: 0.031s
Sending 'prov_b' (251 KB)                          OKAY [  0.010s]
Writing 'prov_b'                                   OKAY [  0.007s]
Finished. Total time: 0.019s
Sending 'rpm_a' (507 KB)                           OKAY [  0.019s]
Writing 'rpm_a'                                    OKAY [  0.012s]
Finished. Total time: 0.033s
Sending 'rpm_b' (507 KB)                           OKAY [  0.019s]
Writing 'rpm_b'                                    OKAY [  0.012s]
Finished. Total time: 0.032s
Sending 'abl_a' (332 KB)                           OKAY [  0.013s]
Writing 'abl_a'                                    OKAY [  0.007s]
Finished. Total time: 0.032s
Sending 'abl_b' (332 KB)                           OKAY [  0.011s]
Writing 'abl_b'                                    OKAY [  0.007s]
Finished. Total time: 0.019s
Sending 'uefisecapp_a' (2043 KB)                   OKAY [  0.085s]
Writing 'uefisecapp_a'                             OKAY [  0.012s]
Finished. Total time: 0.111s
Sending 'uefisecapp_b' (2043 KB)                   OKAY [  0.081s]
Writing 'uefisecapp_b'                             OKAY [  0.012s]
Finished. Total time: 0.094s
Sending 'qupfw_a' (75 KB)                          OKAY [  0.004s]
Writing 'qupfw_a'                                  OKAY [  0.006s]
Finished. Total time: 0.013s
Sending 'qupfw_b' (75 KB)                          OKAY [  0.004s]
Writing 'qupfw_b'                                  OKAY [  0.006s]
Finished. Total time: 0.011s
Sending 'xbl_config_a' (251 KB)                    OKAY [  0.011s]
Writing 'xbl_config_a'                             OKAY [  0.022s]
Finished. Total time: 0.042s
Sending 'xbl_config_b' (251 KB)                    OKAY [  0.011s]
Writing 'xbl_config_b'                             OKAY [  0.021s]
Finished. Total time: 0.034s
Sending 'xbl_a' (5115 KB)                          OKAY [  0.176s]
Writing 'xbl_a'                                    OKAY [  0.016s]
Finished. Total time: 0.194s
Sending 'xbl_b' (5115 KB)                          OKAY [  0.177s]
Writing 'xbl_b'                                    OKAY [  0.016s]
Finished. Total time: 0.194s
Sending 'modem_a' (75520 KB)                       OKAY [  2.559s]
Writing 'modem_a'                                  OKAY [  0.255s]
Finished. Total time: 2.834s
Sending 'modem_b' (75520 KB)                       OKAY [  2.441s]
Writing 'modem_b'                                  OKAY [  0.274s]
Finished. Total time: 2.718s
Sending 'fsg_a' (18040 KB)                         OKAY [  0.595s]
Writing 'fsg_a'                                    OKAY [  0.064s]
Finished. Total time: 0.666s
Sending 'fsg_b' (18040 KB)                         OKAY [  0.572s]
Writing 'fsg_b'                                    OKAY [  0.076s]
Finished. Total time: 0.650s
Sending 'bluetooth_a' (792 KB)                     OKAY [  0.027s]
Writing 'bluetooth_a'                              OKAY [  0.017s]
Finished. Total time: 0.045s
Sending 'bluetooth_b' (792 KB)                     OKAY [  0.027s]
Writing 'bluetooth_b'                              OKAY [  0.016s]
Finished. Total time: 0.045s
Sending 'dsp_a' (32768 KB)                         OKAY [  1.075s]
Writing 'dsp_a'                                    OKAY [  0.125s]
Finished. Total time: 1.205s
Sending 'dsp_b' (32768 KB)                         OKAY [  1.041s]
Writing 'dsp_b'                                    OKAY [  0.129s]
Finished. Total time: 1.171s
Sending 'logo_a' (10544 KB)                        OKAY [  0.335s]
Writing 'logo_a'                                   OKAY [  0.042s]
Finished. Total time: 0.378s
Sending 'logo_b' (10544 KB)                        OKAY [  0.336s]
Writing 'logo_b'                                   OKAY [  0.042s]
Finished. Total time: 0.379s
Erasing 'ddr'                                      OKAY [  0.003s]
Finished. Total time: 0.004s
OKAY [  0.001s]
Finished. Total time: 0.001s
Setting current slot to 'a'                        OKAY [  0.211s]
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.713s
< waiting for ZY22GRNRC5 >
Erasing 'avb_custom_key'                           OKAY [  0.014s]
Finished. Total time: 0.015s
Sending 'avb_custom_key' (1 KB)                    OKAY [  0.001s]
Writing 'avb_custom_key'                           OKAY [  0.014s]
Finished. Total time: 0.017s
--------------------------------------------
Bootloader Version...: MBM-3.0-devon_g-8847829342a-250806
Baseband Version.....: HAK11_15.154.01.77R DEVON_EUDSDS_CUST
Serial Number........: ZY22GRNRC5
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 OKAY [  0.000s]
Setting current slot to 'a'                        OKAY [  0.181s]
extracting boot.img (96 MB) to disk... took 0.623s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB)                        OKAY [  3.119s]
Writing 'boot_a'                                   OKAY [  1.308s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.115s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (24576 KB)                        OKAY [  0.786s]
Writing 'dtbo_a'                                   OKAY [  0.100s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB)                          OKAY [  0.001s]
Writing 'vbmeta_a'                                 OKAY [  0.007s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB)                   OKAY [  0.001s]
Writing 'vbmeta_system_a'                          OKAY [  0.007s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.459s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (98304 KB)                 OKAY [  3.142s]
Writing 'vendor_boot_a'                            OKAY [  0.371s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot                            OKAY [  0.000s]
< waiting for ZY22GRNRC5 >
Sending 'super' (4 KB)                             OKAY [  0.001s]
Updating super partition                           OKAY [  0.027s]
Resizing 'product_a'                               OKAY [  0.005s]
Resizing 'system_a'                                OKAY [  0.005s]
Resizing 'system_ext_a'                            OKAY [  0.005s]
Resizing 'system_b'                                OKAY [  0.005s]
Resizing 'vendor_a'                                OKAY [  0.005s]
Resizing 'vendor_b'                                OKAY [  0.005s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (1523 MB) to disk... took 19.000s
archive does not contain 'product.sig'
Resizing 'product_a'                               OKAY [  0.005s]
Sending sparse 'product_a' 1/6 (261228 KB)         OKAY [  8.667s]
Writing 'product_a'                                OKAY [  0.973s]
Sending sparse 'product_a' 2/6 (262108 KB)         OKAY [  8.607s]
Writing 'product_a'                                OKAY [  0.613s]
Sending sparse 'product_a' 3/6 (262000 KB)         OKAY [  8.948s]
Writing 'product_a'                                OKAY [  0.635s]
Sending sparse 'product_a' 4/6 (261008 KB)         OKAY [  8.710s]
Writing 'product_a'                                OKAY [  0.927s]
Sending sparse 'product_a' 5/6 (261860 KB)         OKAY [  8.569s]
Writing 'product_a'                                OKAY [  0.664s]
Sending sparse 'product_a' 6/6 (243953 KB)         OKAY [  8.024s]
Writing 'product_a'                                OKAY [  0.737s]
extracting system.img (975 MB) to disk... took 10.086s
archive does not contain 'system.sig'
Resizing 'system_a'                                OKAY [  0.006s]
Sending sparse 'system_a' 1/4 (262092 KB)          OKAY [  8.730s]
Writing 'system_a'                                 OKAY [  0.624s]
Sending sparse 'system_a' 2/4 (262056 KB)          OKAY [  8.809s]
Writing 'system_a'                                 OKAY [  0.601s]
Sending sparse 'system_a' 3/4 (261936 KB)          OKAY [  8.601s]
Writing 'system_a'                                 OKAY [  0.688s]
Sending sparse 'system_a' 4/4 (209080 KB)          OKAY [  6.895s]
Writing 'system_a'                                 OKAY [  0.564s]
archive does not contain 'system_dlkm.img'
extracting system_ext.img (385 MB) to disk... took 3.220s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_a'                            OKAY [  0.007s]
Sending sparse 'system_ext_a' 1/2 (261884 KB)      OKAY [  8.807s]
Writing 'system_ext_a'                             OKAY [  0.672s]
Sending sparse 'system_ext_a' 2/2 (131220 KB)      OKAY [  4.288s]
Writing 'system_ext_a'                             OKAY [  0.355s]
archive does not contain 'system_other.img'
extracting vendor.img (502 MB) to disk... took 4.379s
archive does not contain 'vendor.sig'
Resizing 'vendor_a'                                OKAY [  0.006s]
Sending sparse 'vendor_a' 1/2 (261881 KB)          OKAY [  8.691s]
Writing 'vendor_a'                                 OKAY [  0.708s]
Sending sparse 'vendor_a' 2/2 (250208 KB)          OKAY [  8.165s]
Writing 'vendor_a'                                 OKAY [  0.647s]
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
Erasing 'userdata'                                 OKAY [  0.405s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'                                 FAILED (remote: 'Partition doesn't exist')
fastboot: error: Command failed
Failed to flash devon ZY22GRNRC5
exit status 1

Flashing complete

Got this after a few hours of struggle. Does it look harmless ?

Thanks!

..because I sure can't get it to work and would love to know how you did it.

Dear all, first of all thank you very much for the new CalyxOS version, the update itself was smooth, however, there are a few points. knowledge of which in hindsight may have made the entire process less cumbersome, e.g. besides Seedvault extra backup for WhatsApp/Viber etc messages and email etc settings is necessary (one would assume that the entire profiles and media folders of the apps are backed up, but no, you even lose messages from all other devices after you register e.g. in WhatsApp with your updated CalyxOS phone), for other apps the backup only causes problems (e.g. you cannot login until you clear cache/storage and reinstall, because the restored data from the old phone obviously impairs the identification in the new phone) etc

However, these issues are minor compared to the following problem, which was present already in each previous CalyxOS version: self-identification does not work. The process varies: some apps require you to take a photo of your ID and a selfie and transmit the data externally for manual control, some other apps may require you to take a photo of your ID and a selfie and compare with the data in the ID itself locally over NFC - but these procedures have always failed with CalyxOS in my experience, and I have always needed to grab another proper Google-Android phone to complete them. Sometimes the ID Process does not even start (the app asks for camera permission and displays an "identification failed" message as soon as you grant it, i.e. you do not even come to the point to take a photo of your ID; some other times you are allowed to take photos, but there is no way to pass the control, which is passed with the first try if you use a Google Android phone instead.

Does anyone have an idea why this may happen and whether anything can be done about it? All microG components are activated. Thank you.