• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][ANDROID 11][UNOFFICIAL] CalyxOS [beryllium]

Search This thread

Dev_Mashru

Senior Member
Jan 26, 2016
578
657
CalyxOS is an Android mobile operating system that puts privacy and security into the hands of everyday users. Plus, proactive security recommendations and automatic updates take the guesswork out of keeping your personal data personal.

Learn more out CalyxOS.

Working:
  • Telephony (Calls and Data)
  • IMS (RCS, VoLTE and WiFi Calling)
  • WiFi
  • Bluetooth
  • Camera (and flashlight)
  • Audio (Record and Playback)
  • Video Playback
  • Sensors
  • GPS
  • Encryption (FBE)
  • DM-Verity Enabled
Bugs:
  • You tell me

Installation:
  • Wipe /system, /vendor, /cache
  • Format data
  • Flash calyxos zip

Notes:
  • Do NOT flash gapps
  • I do not work for or under the calyx institute
  • Poco F1 does not maintain the android security model as much as the officially supported devices. It does not have complete android verified boot, but dm-verity is enabled

Download:

Kernel Source:

If you like my work, please consider buying me a coffee.

Telegram support
 
Last edited:

Dev_Mashru

Senior Member
Jan 26, 2016
578
657
Screenshots.
 

Attachments

  • photo_2021-05-13_19-44-12.jpg
    photo_2021-05-13_19-44-12.jpg
    44.5 KB · Views: 689
  • photo_2021-05-13_19-44-00.jpg
    photo_2021-05-13_19-44-00.jpg
    46.8 KB · Views: 668
  • photo_2021-05-13_19-44-08.jpg
    photo_2021-05-13_19-44-08.jpg
    45.6 KB · Views: 690
  • photo_2021-05-13_19-44-04.jpg
    photo_2021-05-13_19-44-04.jpg
    62.1 KB · Views: 684
  • photo_2021-05-13_19-43-52.jpg
    photo_2021-05-13_19-43-52.jpg
    45.5 KB · Views: 706
Last edited:

Atwood001

Member
Jan 11, 2014
19
5
Did you do a clean flash?
(I was on lineageos before)

Flash process 1-
Step 1. Twrp > Advanced wipe > select dalvik, cache, system, data, vendor > wipe
(Did not wipe internal storage)

Step 2. Flash calyxos.zip from internal storage.

Result- Stuck at bootloop for 5 min.

(Had to reboot to recovery again manually.)

Flash process 2 -
Step 1.
Step 1. Twrp > Advanced wipe > select dalvik, cache, system, data, vendor, internal storage > wipe

Step 2. Moved calyxos file from pendrive to internal storage. Had to mount usb-otg.

Step 3. Wiped dalvik, cache, system, data, vendor again just in case.

Step 4. Flash calyxos.zip from internal storage.

Result- Stuck at bootloop for 5 min.

Flash process 3 -
Step 1. Twrp > wipe > format data

Step 2. Twrp > Advanced wipe > select dalvik, cache, system, data, vendor > wipe

Step 3. Moved calyxos file from pendrive to internal storage. Had to mount usb-otg.

Step 4. Wiped dalvik, cache, system, data, vendor again.

Step 4. Flash calyxos.zip from internal storage.

Result- Stuck at bootloop for 5 min.
 
  • Like
Reactions: duttyend and Ajudia

Dev_Mashru

Senior Member
Jan 26, 2016
578
657
(I was on lineageos before)

Flash process 1-
Step 1. Twrp > Advanced wipe > select dalvik, cache, system, data, vendor > wipe
(Did not wipe internal storage)

Step 2. Flash calyxos.zip from internal storage.

Result- Stuck at bootloop for 5 min.

(Had to reboot to recovery again manually.)

Flash process 2 -
Step 1.
Step 1. Twrp > Advanced wipe > select dalvik, cache, system, data, vendor, internal storage > wipe

Step 2. Moved calyxos file from pendrive to internal storage. Had to mount usb-otg.

Step 3. Wiped dalvik, cache, system, data, vendor again just in case.

Step 4. Flash calyxos.zip from internal storage.

Result- Stuck at bootloop for 5 min.

Flash process 3 -
Step 1. Twrp > wipe > format data

Step 2. Twrp > Advanced wipe > select dalvik, cache, system, data, vendor > wipe

Step 3. Moved calyxos file from pendrive to internal storage. Had to mount usb-otg.

Step 4. Wiped dalvik, cache, system, data, vendor again.

Step 4. Flash calyxos.zip from internal storage.

Result- Stuck at bootloop for 5 min.

You seem to be flashing fine. Not sure why you are getting stuck in a bootloop. Only people who flashed DFE were facing this issue, but since you arent flashing that either, I'm not really sure. Which twrp are you using?
 

TioCareca

Senior Member

Zatsando

Member
Oct 16, 2017
15
8
This is exciting stuff, being able to port this Rom into Poco F1 is huge! However I 'm sceptical of using an unofficial rom for my main smartphone. No offence for the developer, though, I hope the Calyx OS team find his project and properly port it for poco f1 as an official one!
 
  • Like
Reactions: Ajudia

nolam10

New member
Jul 20, 2018
4
1
When i flash a rom i never wipe vendor.And now you should update the vendor lo the latest one before you flash again. never wipe vendor if you know its the latest.Afher installing the latest vender format data and reboot back into recovery and wipe dalvik cache system internal storage and data and flash from sd card or external storage .Another way is to restore the phone to latest manufacturer rom and the reinstall twrp and 100%clean wipe but don't wipe vendor.
 
Last edited:

Ajudia

Senior Member
Oct 13, 2017
154
28
This is exciting stuff, being able to port this Rom into Poco F1 is huge! However I 'm sceptical of using an unofficial rom for my main smartphone. No offence for the developer, though, I hope the Calyx OS team find his project and properly port it for poco f1 as an official one!
Calyx OS official only possible with device having secured boot means relocking bootloader after flashing Rom, which most device lacks except pixel phones and mi A1,
this rom rocks on F1 enjoy!
 
  • Like
Reactions: duttyend

Zatsando

Member
Oct 16, 2017
15
8
Calyx OS official only possible with device having secured boot means relocking bootloader after flashing Rom, which most device lacks except pixel phones and mi A1,
this rom rocks on F1 enjoy!
yeah I know that, but using and unofficial rom and most important of all, without making the code public is not safe for anyone. not to hate on the developer (I am a developer myself) but I try to use stuff that they are open source, especially when it comes to OS's. I really hope the dev releases the code so the poco f1 community (who I m sure it embrace this rom) can audit it and give their approval!
 
  • Like
Reactions: duttyend and Ajudia

Dev_Mashru

Senior Member
Jan 26, 2016
578
657
yeah I know that, but using and unofficial rom and most important of all, without making the code public is not safe for anyone. not to hate on the developer (I am a developer myself) but I try to use stuff that they are open source, especially when it comes to OS's. I really hope the dev releases the code so the poco f1 community (who I m sure it embrace this rom) can audit it and give their approval!

First off, I dont see why using an unofficial build is an issue, its not that if it was official you'd suddenly know me to verify anything. That being said, as @Ajudia said, official isnt possible because F1's bootloader cant be locked after flashing a custom ROM. When it comes to open sourcing the code, I havent deviated much from the calyx source. In fact I have turned down multiple requests to add live display, as it would deviate more from the original source. That said, the only changes that were done were CAF additions to get it to boot and get everything working. The only major deviation is addition of QTI BT to the original source. All those were picked from LOS. Also the kernel is already open source. You are welcome to audit it and report back if you find anything. That said, I did plan to push the few repos where the code was changed, but didnt find enough time to push. If I find time in the future, ill push them. Also for all the ROMs out there whose code is open and have official support, there is no way for you to verify that the developer is actually using what he is showing. At the end of the day you have to trust the developer that he is indeed using what is shown to the world or compile the ROM yourself.
 

Retrial

Recognized Contributor
Jun 10, 2015
1,296
2,177
Athens
Samsung Galaxy S4
Xiaomi Poco F1
What's the difference between this rom and lineage with microg?
True question 😉
With respect to the dev, tbh CalyxOS wihout the ability to relock the bootloader is pretty much useless for the nature of this ROM. (Bootloader can be locked only in Pixels and Xiaomi A2 devices)
I guess the build in Firewall and App Lock it's something make it stands out, otherwise it's like a pure AOSP ROM with microG.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    so when i flash this rom. wont lock my bootloader??
    No, if you lock your bootloader with a custom rom, you won't be able to boot.

    if you asking if the rom lock your bootloader, no, it won't.
    👍
  • 12
    CalyxOS is an Android mobile operating system that puts privacy and security into the hands of everyday users. Plus, proactive security recommendations and automatic updates take the guesswork out of keeping your personal data personal.

    Learn more out CalyxOS.

    Working:
    • Telephony (Calls and Data)
    • IMS (RCS, VoLTE and WiFi Calling)
    • WiFi
    • Bluetooth
    • Camera (and flashlight)
    • Audio (Record and Playback)
    • Video Playback
    • Sensors
    • GPS
    • Encryption (FBE)
    • DM-Verity Enabled
    Bugs:
    • You tell me

    Installation:
    • Wipe /system, /vendor, /cache
    • Format data
    • Flash calyxos zip

    Notes:
    • Do NOT flash gapps
    • I do not work for or under the calyx institute
    • Poco F1 does not maintain the android security model as much as the officially supported devices. It does not have complete android verified boot, but dm-verity is enabled

    Download:

    Kernel Source:

    If you like my work, please consider buying me a coffee.

    Telegram support
    8
    What's the difference between this rom and lineage with microg?
    True question 😉

    With respect to the dev, tbh CalyxOS wihout the ability to relock the bootloader is pretty much useless for the nature of this ROM. (Bootloader can be locked only in Pixels and Xiaomi A2 devices)
    I guess the build in Firewall and App Lock it's something make it stands out, otherwise it's like a pure AOSP ROM with microG.

    I am sorry, but I beg to differ. While i agree that being able to lock the bootloader would make it much more secure, i still think calyxos is more secure because of the following reasons:
    1. I have enabled DM-Verity which means that everything in the boot process is verified once the kernel is loaded, but if something before the kernel is loaded, it will probably be able to maintain that access. That said, it is definitely more difficult to get infected with something sophisticated that starts itself before the kernel than other more common attacks out that start after the kernel is loaded, which DM-Verity should prevent from happening.
    2. Microg for LOS enables signature spoofing for all system apps (according to the FAQ on their website), which means a malware that manages to get system privileges could potentially be able to misuse the permissions. On the other hand, calyxos sandboxes signature spoofing to only the microg apps with explicit whitelist, which makes much more difficult to be exploited.
    3. Lineageos builds are userdebug, while my builds are user builds. Userdebug builds have many debugging capabilities that "normally violate the android security model" (quoted from AOSP). Those debugging capabilities could also potentially add more attack surfaces making it less secure.

    Some might even find the other features like restricting unknown USB, making a signal/ WhatsApp call directly from the dialer and other such calyx features useful.

    Like I said in the beginning of this post, it is definitely not as secure as a device with a locked bootloader would be, but I have tried my best to make it as secure as possible.
    5
    CalyxOS v2.7.0 is out. Get it here.

    Changelog:
    • Added APNs
    • Updated kernel to Ingenium v2.5
    • Source upstream (Updated to July patch)
    • More things I forgot
    4
    I am sorry, but I beg to differ. While i agree that being able to lock the bootloader would make it much more secure, i still think calyxos is more secure because of the following reasons:
    1. I have enabled DM-Verity which means that everything in the boot process is verified once the kernel is loaded, but if something before the kernel is loaded, it will probably be able to maintain that access. That said, it is definitely more difficult to get infected with something sophisticated that starts itself before the kernel than other more common attacks out that start after the kernel is loaded, which DM-Verity should prevent from happening.
    2. Microg for LOS enables signature spoofing for all system apps (according to the FAQ on their website), which means a malware that manages to get system privileges could potentially be able to misuse the permissions. On the other hand, calyxos sandboxes signature spoofing to only the microg apps with explicit whitelist, which makes much more difficult to be exploited.
    3. Lineageos builds are userdebug, while my builds are user builds. Userdebug builds have many debugging capabilities that "normally violate the android security model" (quoted from AOSP). Those debugging capabilities could also potentially add more attack surfaces making it less secure.

    Some might even find the other features like restricting unknown USB, making a signal/ WhatsApp call directly from the dialer and other such calyx features useful.

    Like I said in the beginning of this post, it is definitely not as secure as a device with a locked bootloader would be, but I have tried my best to make it as secure as possible.
    Don't get me wrong. I like that POCO F1 has this ROM even unofficial. However all these features more or less can be achieved in other ROMs too. Having them ready out of the box is useful tho.

    What I am trying to say is, all the hype about CalyxOS and GrapheneOS that makes them stands out is the locked bootloader which make them more secure. That's ofc unavailable for our device and I know you've tried to get it as close as you can.

    With all that said, I would like to see this ROM staying alive for POCO F1 and to keep it up. Giving users more choices for ROMs is nice and I like to see people start thinking about privacy and security more.✌️