Related
Hi all,
for now I'm still on a GS2, but I am considering buying a GNote your rom and I like a lot. So I plan to install it on my S2 to go to.
A question: I am in CM9 for now, with your rom (which is based on CM9) can I do the update with the available Nightly of CM9 ?
Or maybe I did not understand (which should not wonder ) and it can not work like that?
Thank you in advance for the answer.
If you are on PARANOIDANDROID v1.0 and update to a nightly from CM9. You will then be on CM9 not PARANOIDANDROID.
Even tho it is based on CM9 it is two different things.
Updates that get put in to CM9 nightlys will be put in to PARANOIDANDROID when they want and their rom will be updated, so will there thread and the OTA updater.
To sum up, if you flash a CM9 Nightly then you will lose your PARANOIDANDROID rom.
Also make sure you use the extended steps to install a new rom.
The steps on the OP are very clear but apparently some users miss some things or can't get a properly installation so, here are the extended steps (personally i'm always use this method):
1.Reboot into recovery
2.Wipe Data / Factory Reset
3.Wipe Cache Partition
4.Install the Main ROM
5.In recovery go to Advanced
6.Wipe Dalvik Cache
7.Fix Permissions
8.Wipe Cache Partition
9.Reboot
10.If at the first boot you can't do the configuration of the google account, skip this step and continue
11.When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot
12.When you boot again into the system the data will be enable and you can do the configuration of Google Account (if you don't do this before)
13.This is the moment for install all the extras like themes, fix's, kernels, etc.
14.Enjoy!!!
Thank's all.
Still Confused....
dwightvanbentem said:
Also make sure you use the extended steps to install a new rom.
The steps on the OP are very clear but apparently some users miss some things or can't get a properly installation so, here are the extended steps (personally i'm always use this method):
1.Reboot into recovery
2.Wipe Data / Factory Reset
3.Wipe Cache Partition
4.Install the Main ROM
5.In recovery go to Advanced
6.Wipe Dalvik Cache
7.Fix Permissions
8.Wipe Cache Partition
9.Reboot
10.If at the first boot you can't do the configuration of the google account, skip this step and continue
11.When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot
12.When you boot again into the system the data will be enable and you can do the configuration of Google Account (if you don't do this before)
13.This is the moment for install all the extras like themes, fix's, kernels, etc.
14.Enjoy!!!
Click to expand...
Click to collapse
I have rooted my GT N7000 with Stock ICS ROM from SAMSUNG [India]
BaseBand Version : N7000DDLP4
Kernel : 3.0.15-N7000DDLP8
How do I go about?
Do I need to first downgrade it to GB Stock India
N7000DDLC1---------2.3.6---------2012 March---------N7000ODDLC1-----------India--------------------------------------
OR
Do I downgrade it to SGN_XX_OXA_KJ1_FACTORYFS ???
please guide what to do...
Issue installing
http://forum.xda-developers.com/showthread.php?t=1729331&fb_source=message
Can someone help me. Tried to post a question in that post itself but need to have 10 comments or something.
Anyways, followed the following instruction which said to (i think)
boot into cwm
wipe data/factory reset
wipe cache partition
wipe dalvik cache
then i tried to install the file that i get from mediafire using install zip from sdcard
Find the file (in the download folder is where i saved it) but as soon as it starts to install it, stops ..calling out to an error (something 7)
Could someone see if i did it correctly or there is some other issue?
Currently running broodrom rc5
I am noob in s2 kitchen, I want install this rom..
I'm on Androidhouse 2.3.6, and kernel: [email protected] #101, baseband I9100XXKP1, ROM version: TurkbeyRom v30
Tutorial or help me pleasse
here are the steps for the instalation mate..you find them in the faq on the resurrection remix thread with all the files you need..hope this is enough
The steps on the OP are very clear but apparently some users miss some things or can't get a properly installation so, here are the extended steps (personally i'm always use this method):
Reboot into recovery
Wipe Data / Factory Reset
Wipe Cache Partition
Install the Main ROM
In recovery go to Advanced
Wipe Dalvik Cache
Fix Permissions
Wipe Cache Partition
Reboot
If at the first boot you can't do the configuration of the google account, skip this step and continue
When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot
When you boot again into the system the data will be enable and you can do the configuration of Google Account (if you don't do this before)
This is the moment for install all the extras like themes, fix's, kernels, etc.
Enjoy!!!
ionutz1708 said:
here are the steps for the instalation mate..you find them in the faq on the resurrection remix thread with all the files you need..hope this is enough
The steps on the OP are very clear but apparently some users miss some things or can't get a properly installation so, here are the extended steps (personally i'm always use this method):
Reboot into recovery
Wipe Data / Factory Reset
Wipe Cache Partition
Install the Main ROM
In recovery go to Advanced
Wipe Dalvik Cache
Fix Permissions
Wipe Cache Partition
Reboot
If at the first boot you can't do the configuration of the google account, skip this step and continue
When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot
When you boot again into the system the data will be enable and you can do the configuration of Google Account (if you don't do this before)
This is the moment for install all the extras like themes, fix's, kernels, etc.
Enjoy!!!
Click to expand...
Click to collapse
Thanks, but I am on 2.3.6, how install recovery? only flash android 4 zip? and what kernel?
i think you need to read this to know exactly what you have to do http://forum.xda-developers.com/showthread.php?t=1075278 ..if you have any question i'll be glad to try to help you
Here are best videos you will ever see for galaxy s2 rooting, CWM installation, and ICS installation:
--rooting your galaxy S2 the easiest and safest way: (If not already rooted)
http://galaxys2root.com/galaxy-s2-root/how-to-root-galaxy-s2/
-- Install CWM
http://galaxys2root.com/galaxy-s2-r...ckworkmod-recovery-on-rooted-galaxy-s2-i9100/
--Install ICS Resurrection:
http://galaxys2root.com/galaxy-s2-hacks/how-to-install-rom-on-galaxy-s2/
You will notice that all files needed are listed below video except the last one which you can download from here:
http://forum.xda-developers.com/showthread.php?t=1436854
Remember always to take a backup before flashing any rom.
Good Luck.
First of all, this is my first post on this forum, so I'd like to say hello to everybody.
I made a bit of a mess with my father's phone (it was mine before he had it, so it was already modded), and the explanation will be somewhat long because I tried everything before coming here for help.
This phone had Android 5.1.1 Lollipop, installed through the official Cyanogenmod 12.1 Nightlies. It was working perfectly, but I wanted to install more Gapps on the /system partition and switch some of the original Cyanogenmod apps with the corresponding Google apps. I used Deltadroid's modular Gapps (Thread here: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368) to install everything I needed on the /system partition, but I only did a factory reset+cache wipe instead of wiping the /system partition too and starting from scratch, because I couldn't find the option to wipe the /system partition in the "stock" Cyanogen Recovery. Now the phone will boot, enter recovery mode and even get to the setup screen, but as soon as the Google Play Services are needed, they crash and the setup won't go on. I tried installing the CWM but the signature check fails every time, I tried using ADB but I'm no expert and I don't know how to make it work, I tried reinstalling the ROM and wiping /data and /cache once again to no avail, I tried basically everything but it seems the only thing that can be done is wiping the /system partition and reinstalling both the ROM, the Gapps and the add-ons.
The problem is, I have no idea how to wipe the /system partition, so I was wondering if anyone here could help.
Thanks in advance.
Hi @Valtekken
You just need to have a "signed" .zip to flash through that recovery. Try the philz 6.48.4 attached here. I have heard of a few people not being able to flash this one, if it doesn't install, use the other one first, reboot to recovery, and then flash 6.48.4. So -
1. Flash the philz recovery
2. Reboot to recovery, not system
2a. (Flash the other one, reboot to recovery [if you used XWMS3 first])
3. Do your wipes(you should only need to wipe /system if you want to keep your data, but I always recommend a clean install if possible - /data, /cache, and dalvik/art cache as well)
4. Install the new CM12.1 and gapps
BTW the gapps you can flash will depend on whether or not you have repartitioned. If you have stock /system partition just install a pico or minimal gapps
noppy22 said:
Hi @Valtekken
You just need to have a "signed" .zip to flash through that recovery. Try the philz 6.48.4 attached here. I have heard of a few people not being able to flash this one, if it doesn't install, use the other one first, reboot to recovery, and then flash 6.48.4. So -
1. Flash the philz recovery
2. Reboot to recovery, not system
2a. (Flash the other one, reboot to recovery [if you used XWMS3 first])
3. Do your wipes(you should only need to wipe /system if you want to keep your data, but I always recommend a clean install if possible - /data, /cache, and dalvik/art cache as well)
4. Install the new CM12.1 and gapps
BTW the gapps you can flash will depend on whether or not you have repartitioned. If you have stock /system partition just install a pico or minimal gapps
Click to expand...
Click to collapse
First of all, thank you for answering!
I tried many "-signed" .zips, but none of them worked, so I'll assume I used non-compatible ones. There was space for the Gapps on the /system partition, mainly because I made sure of getting only the Gapps and the few addons I needed, so the MB count was very low.
I'll try your recovery right now and let you know in a moment, hopefully this solves the problem and I can have the phone working again.
Managed to install the recovery, format the /system, /data and /cache partitions, install the rom, the Gapps and the add-ons. It worked, but the phone still gives me an "Unfortunately, Google Play Services has stopped". How can I get the apps to work? What could the problem be?
I solved the problem, finally...I changed the Gapps package (I used TK's Gapps) and managed to install it and make everything work.
Thanks for all your help! I think the thread can be closed now.
Hey people,
this shall mainly be a fast way to navigate users to necessary steps for diverse situations.
Instead of repeating the procedures over and over in each thread, this can be cited.
I will suggest you what I always do, and what I find safe and what I have good experiences with.
Still, you do everything at your own risk! So don’t complain to me if you mess something up by following my steps.
This well known phrase also counts here: “YOU are choosing to make these modifications”.
*********************
Preparations
Recovery
Make sure you are on the latest TWRP version.
Currently this is 3.2.3-0.
Backups
Before any of these procedures you should make a backup of every partition and save it at an external place – an usb stick, your PC, but not on your phone! Also copy the content of your entire internal storage at such an external place.
This will not always be needed and I will add more details of what you will surely lose when applying each method, but sometimes things just go wrong and suddenly your whole storage may be lost out of nowhere (happened to me more than once already).
A nice app that helps you restoring your apps and app data in a very quick way is Titanium Backup (get it from the Play Store). If you use the Pro version, you can restore everything basically with one click, so think about this way of backing up things as well (external copies are also advised here for obvious reasons).
Firmware
Make sure you are on adequate firmware for your ROM. Which firmware that is, must be taken from the respective ROM thread.
Adequate firmware needs to be present at any time before the actual ROM installation,
otherwise installation will fail, as the ROM expects a certain minimum to be present.
You will not need to always flash firmware again, when installing other ROMs or ROM versions.
The one you flashed last time sticks until you flash another.
A nice alternative to always flashing whole MIUI Developer versions are the zips offered by the firmware updater tool (just search through the xda topics).
*********************
So here we go with methods you should know:
***************
* Dirty Flash *
***************
Note that:
This is not recommended if the ROM maintainer or developer suggested a clean flash
If you wanna solve weird issues, you may try this first, but a Clean Flash or a Complete Formatting will probably help better
Use-cases:
You wanna install an update for a ROM you are momentarily on
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik and Cache
Flash ROM zip right on top of existing installation
(Optionally) Re-/flash root (re-flashing is not necessary for Magisk most of the time if you installed it before)
****************
* Clean Flash *
****************
Note that:
You will lose Gapps, settings, apps and app-data
Also recommended from time to time, even when a dirty flash would be sufficient
Some developers always prefer this method over a dirty flash
Use-cases:
You wanna flash a ROM from the same Android generation (e.g. both ROMs are from generation Nougat 7.1.2) you are currently on
You are experiencing issues after dirty flashing a ROM
Benefits:
Clean way of installation
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik, Cache, System, Data, (momentairly I also advise) Vendor
Flash ROM zip
(Optionally) Flash custom kernel
(Optionally) Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Flash root
***************************
* Complete Formatting *
***************************
Note that:
You will lose Gapps, settings, apps, app-data and the content on your internal storage – basically everything on your phone!
Use-cases:
You wanna flash a ROM of a different Android generation (e.g. switch from Nougat to Oreo)
You are experiencing weird issues, even a clean flash doesn’t solve
Benefits:
Clean way of installation
Good problem solver
Procedure:
Wipe Dalvik, Cache, System, Data, (momentairly I also advise) Vendor
Format data (the one where you need to type “yes”)
Reboot to recovery to access the Data partition correctly again
Flash ROM zip
(Optionally) Flash custom kernel
(Optionally) Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Flash root
****************************************
* Solve unable to mount Data error *
****************************************
Note that:
You will lose Gapps, settings, apps, app-data and the content on your internal storage – basically everything on your phone!
Use-cases:
TWRP suddenly shows the above error and even a Complete Formatting doesn’t help (or work)
Procedure:
Re-flash latest TWRP via fastboot (not from within TWRP)
Perform a Complete Formatting
********************
* Gapps Re-flash *
********************
Use-cases:
You want to change your current Gapps setup, but keep your current ROM installation
Benefits:
Only takes a few minutes
You will not lose settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Wipe Dalvik, Cache and System
Flash ROM zip
Flash Gapps package for Arm64*
(Optionally) Flash Gapps additions*
(Optionally) Re-/flash root
********************
* Kernel Change *
********************
Note that:
This works for almost every kernel, but if the developer suggests another method, follow his
Use-cases:
You want to change the kernel, but keep your current ROM installation
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Extract the boot.img of your current ROM
Flash the boot.img by selecting “flash image” in TWRP
Reboot to System and let everything cool down for a minute or two
Reboot to TWRP
Flash new kernel
(Optionally) Re-/flash root
Wipe Dalvik and Cache
*******************************
* Stock Kernel Restoration *
*******************************
Use-cases:
You're on a custom kernel and want to switch back to stock one
Benefits:
Only takes a few minutes
You will not lose Gapps, settings, apps and app-data
Content on your internal storage will (/should) stay untouched
Procedure:
Extract the boot.img of your current ROM
Flash the boot.img by selecting “flash image” in TWRP
(Optionally) Re-/flash root
Wipe Dalvik and Cache
********************************
* Splash Screen Restoration *
********************************
Note that:
A clean flash will not solve this
Use-cases:
Some kernel's or ROM's splash screen sticks and you wanna get rid of it.
Benefits:
Only takes a minute
You will not lose anything on your phone (except the splash screen ; ) )
Procedure:
Just re-flash your current firmware
*I usually go for Pico Gapps from opengapps.org, as they don't include anything I don't need or like, and add a couple of things from deltadroid by flashing them right after the Pico Gapps package. Some stock apps can be overwritten this way, so you don't have two for the same purpose (e.g. stock calendar and google calendar) and it results in a nice minimal Gapps configuration.
I’m open for corrections, questions or doubts! Please leave a comment in these cases!
last updated: 2018-08-20
Nice little guide!
Small note: rooting on f2fs with Magisk has been fixed recently if you didnt know yet.
HelpMeruth said:
Nice little guide!
Small note: rooting on f2fs with Magisk has been fixed recently if you didnt know yet.
Click to expand...
Click to collapse
Thanks!
And thanks for the info. So were these issues Magisk related only?
Phil_Smith said:
Thanks!
And thanks for the info. So were these issues Magisk related only?
Click to expand...
Click to collapse
iirc yes(there were SQL issues on the Magisk app), but I don't really follow superSU anymore since its been sold to some random company.
This is a very good guide.. Thanks mate
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:
Get CalyxOS for Poco F1
Kernel Source:
Kernel source
If you like my work, please consider buying me a coffee.
Telegram support
Screenshots.
Reserved 2
haserex said:
Thank u for this is this no longer maintained?
Click to expand...
Click to collapse
It is, but I am facing some issues when trying to compile. Might take a while to fix.
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
Twrp recovery latest. Flashed latest calyx. Stuck at bootloop.
Please help. Stuck at bootloop with v2.7.0. Is anybody else facing this issue?
Atwood001 said:
Please help. Stuck at bootloop with v2.7.0. Is anybody else facing this issue?
Click to expand...
Click to collapse
Did you do a clean flash?
Dev_Mashru said:
Did you do a clean flash?
Click to expand...
Click to collapse
(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.
Atwood001 said:
(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.
Click to expand...
Click to collapse
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?
Dev_Mashru said:
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?
Click to expand...
Click to collapse
twrp-3.5.2_10-0-beryllium.img. Should I try with other recovery?
Atwood001 said:
twrp-3.5.2_10-0-beryllium.img. Should I try with other recovery?
Click to expand...
Click to collapse
That seems possible a vendor/firmware problem, try to flash stock miui first to recover all partitions data correctly, then flash calyxos...
Step 1. Twrp > wipe > format data> Advanced wipe > select dalvik, cache, data, internal storage > wipe
Step 2. Flash calyxos.zip
if bootloop just format data again...
Hope it helps...
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!
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.
Zatsando said:
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!
Click to expand...
Click to collapse
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!
Ajudia said:
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!
Click to expand...
Click to collapse
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!
Zatsando said:
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!
Click to expand...
Click to collapse
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.
What's the difference between this rom and lineage with microg?
True question
TioCareca said:
What's the difference between this rom and lineage with microg?
True question
Click to expand...
Click to collapse
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.
Retrial said:
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.
Click to expand...
Click to collapse
I was thinking the same, that's why the question, the firewall and vpn was my selling point, but i think it can be done in all roms too...
Anyway thanks for the dev to give us another choice