Related
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.
So i installed TWRP, SUPER SU, custom ROM (linageOs), now i need GApps but here i have a problem. I placed a zip folder that i need to install while android was turned ON, i went to TWRP and i can`t find this zip file.
I don`t have access to files while in TWRP recovery (pc says that device stopped working or has been plugged out).
TWRP says that internal storage is 0MB, but there are folders like acct, boot, cache etc...
payer0 said:
So i installed TWRP, SUPER SU, custom ROM (linageOs), now i need GApps but here i have a problem. I placed a zip folder that i need to install while android was turned ON, i went to TWRP and i can`t find this zip file.
I don`t have access to files while in TWRP recovery (pc says that device stopped working or has been plugged out).
TWRP says that internal storage is 0MB, but there are folders like acct, boot, cache etc...
Click to expand...
Click to collapse
Update your recovery. You are using an old version of TWRP. Use the one in the opening post of LineageOS thread or latest OrangeFox and you will be able to see your internal storage.
SuperSU is also outdated. Use Magisk instead (latest official version should be 17.1).
Flash ROM, flash GApps, flash Magisk and reboot your phone
Noter2017 said:
Update your recovery. You are using an old version of TWRP. Use the one in the opening post of LineageOS thread or latest OrangeFox and you will be able to see your internal storage.
SuperSU is also outdated. Use Magisk instead (latest official version should be 17.1).
Flash ROM, flash GApps, flash Magisk and reboot your phone
Click to expand...
Click to collapse
Worked, thanks
Thanks man you saved time and energy
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Important Info
DON'T USE TWRP 3.0.2-0 OR OLDER WITH LINEAGEOS. IT DOES NOT WORK CORRECTLY. USE VERSION 3.2.1.0 HERE
Current lineage 16.0 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
If you already have those you don't need to flash them again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS OFFICIAL: https://download.lineageos.org/shamu
Latest build dates back to april 1st 2020 and there will be no new OFFICIAL builds as shamu has been promoted to LineageOS 17.1.
LineageOS UNOFFICIAL: lineage-16.0-20201107-UNOFFICIAL-shamu.zip
Includes November 2020 Android Security Bulletins.
Here is its md5sum.
Google apps: MindTheGapps or OpenGAPPS <= nano
HEADS UP:
When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
If you are migrating from an OFFICIAL build to the UNOFFICIAL build you have 2 options:
Wipe data and do a clean install of UNOFFICIAL build
Dirty flash thanks to an intermediate MIGRATION build
First flash the MIGRATION build (lineage-16.0-20200430-MIGRATION-shamu.zip md5sum), boot to it and then flash the UNOFFICIAL build and boot to it.
SU addon zip: Addon Install zip / Addon Removal zip
NOTE: LineageOS does not come with root, so this is now provided for those that want it.
The install zip is a one time flash, like gapps.
Meaning, it persists when updating to a new LineageOS nightly.
Changelog
Builddate: 2019.03.01
Changes:
[new] Initial LineageOS 16.0 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
You're also welcome to use npjohnson's personal builds, but these are experimental, and likely to destroy your data. These builds include GApps, and Pixel-Goodies, among other things -- you'll find no support for these, so please don't discuss these here.
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, Elektroschmock, dwardo
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2019-03-01
Last Updated 2020-11-07
Reserved
Please read how to
- Properly report a bug: https://wiki.lineageos.org/bugreport-howto.html
- Capture a log https://wiki.lineageos.org/logcat.html
Clean flashed Lineage 16.0, Gapps 9.0 Mini, Magisk 18.0. I was not encrypted on LOS 15.1
Edit: Had a hiccup on the setup screen (phone froze). Restarted and all good.
Edit: Pixel Launcher doesn't seem work for me. Crashes every time going to home screen. Had to go to APKMIRROR and download latest version. Was working for 5 minutes or so, but now crashes again. Still messing with it.
Edit: Clean flashed a second time with 16, Gapps 9.0 FULL, and Magisk 18.0. Setup screen froze again. I'm gonna restore my 15.1 backup as I've run out of time to mess around.
FYI - I'm not looking for help.. just posting my experience.
Confirming everything is good here with 16.0.
I basically followed the steps on the LOS wiki (upgrading from 15.1, unencrypted, no wiping-data):
1. Format /system partition in TWRP
2. Sideload 16.0 ROM
3. Sideload Opengapps 9.0
4. Sideload Magisk
5. Reboot
Everything working.
Only thing I noticed (which may be just how Lineage OS is designed) was my homescreen setup was overwritten by the Lineage OS defaults so I had to set up widgets again.
Great work bro as always @Electroshmock :good:
Just a small reminder, if a user is going to post about issues with the ROM, please attach logs for the OP to help look into the issue.
Hi, I lost the /data partition (error: Failed to mount '/data' (Device or resource busy)), how to get it back?
Initially I had the latest 15.1, and did all instructions to my best understanding. All went well, but when I was ready to finally reboot, TWRP 3.2.1.0 said I have no OS installed. Then I formatted data, and the problems started.
EDIT: /data became OK after I rebooted to recovery. Now I installed again the same way, before final reboot TWRP said I have no OS installed. But I ignored that and rebooted. Now the system seems to work, at least I'm currently settings up the phone again.
But the question is: why does TWRP inform that I have no OS installed?? Any ideas?
wrsg said:
Confirming everything is good here with 16.0.
I basically followed the steps on the LOS wiki (upgrading from 15.1, no wiping-data):
1. Format /system partition in TWRP
2. Sideload 16.0 ROM
3. Sideload Opengapps 9.0
4. Sideload Magisk
5. Reboot
Everything working.
Only thing I noticed (which may be just how Lineage OS is designed) was my homescreen setup was overwritten by the Lineage OS defaults so I had to set up widgets again.
Click to expand...
Click to collapse
This method worked for me as well. :good:
amroj said:
Hi, I lost the /data partition (error: Failed to mount '/data' (Device or resource busy)), how to get it back?
Initially I had the latest 15.1, and did all instructions to my best understanding. All went well, but when I was ready to finally reboot, TWRP 3.2.1.0 said I have no OS installed. Then I formatted data, and the problems started.
Click to expand...
Click to collapse
Probably need to add that to OP. You cannot be encrypted. Need to format (not wipe) user data partition in TWRP. You will lose everything there, so backup to PC or usb flash drive.
TWRP 3.2.1-0
data was formatted and encrypted with Lineage 14, upgraded to 15 and now 16.
Flashed LineageOS 16.0 + MindTheGapps + Magisk 18.1
After reboot: message from OS: your password is correct but the data is corrupted, factory reset is needed
Tried to reboot to TWRP: password not correct
Rebooted to OS and did factory reset: same message (password correct but data corrupted).
I have an offline backup on a PC with LineageOS 15 + data.
Wiping data does not help (same problem after reboot), I guess I have to format it.
Ideas ?
everdium said:
TWRP 3.2.1-0
data was formatted and encrypted with Lineage 14, upgraded to 15 and now 16.
Flashed LineageOS 16.0 + MindTheGapps + Magisk 18.1
After reboot: message from OS: your password is correct but the data is corrupted, factory reset is needed
Tried to reboot to TWRP: password not correct
Rebooted to OS and did factory reset: same message (password correct but data corrupted).
I have an offline backup on a PC with LineageOS 15 + data.
Wiping data does not help (same problem after reboot), I guess I have to format it.
Ideas ?
Click to expand...
Click to collapse
sideload
wrsg said:
sideload
Click to expand...
Click to collapse
So format data and then sideload LineageOS 15 or 16 ?
OP says that data can not be decrypted by TWRP if encrypted by LOS 16.
everdium said:
TWRP 3.2.1-0
data was formatted and encrypted with Lineage 14, upgraded to 15 and now 16.
Flashed LineageOS 16.0 + MindTheGapps + Magisk 18.1
After reboot: message from OS: your password is correct but the data is corrupted, factory reset is needed
Tried to reboot to TWRP: password not correct
Rebooted to OS and did factory reset: same message (password correct but data corrupted).
I have an offline backup on a PC with LineageOS 15 + data.
Wiping data does not help (same problem after reboot), I guess I have to format it.
Ideas ?
Click to expand...
Click to collapse
Same here
rivernov said:
Same here
Click to expand...
Click to collapse
I formatted data, rebooted and now in the LineageOS 16 initial setup.
If that works, the only problem is how to restore the data partition from the LOS 15 backup.
Well, the good old stability and smoothness of LOS!
All pretty fine here! Franco Kernel working fine!
Please dev. Any root solution to remove brighness slider from quick settings?
everdium said:
I formatted data, rebooted and now in the LineageOS 16 initial setup.
If that works, the only problem is how to restore the data partition from the LOS 15 backup.
Click to expand...
Click to collapse
It worked. After a reboot, its now reinstalling all my apps.
There is still the matter of restoring the LOS 15 backup but I have all my data in the cloud. Maybe its better not to restore the backup and see whatever settings need to be reapplied manually.
But now my data is encrypted by LineageOS 16 and the OP says that TWRP can not decrypt it.
everdium said:
So format data and then sideload LineageOS 15 or 16 ?
OP says that data can not be decrypted by TWRP if encrypted by LOS 16.
Click to expand...
Click to collapse
Did you try doing that, in spite of TWRP not being able to decrypt it? What error did you get?
edit: I guess it's too late for you to try this, I didn't read your latest reply until after typing that.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
everdium said:
It worked. After a reboot, its now reinstalling all my apps.
There is still the matter of restoring the LOS 15 backup but I have all my data in the cloud. Maybe its better not to restore the backup and see whatever settings need to be reapplied manually.
But now my data is encrypted by LineageOS 16 and the OP says that TWRP can not decrypt it.
Click to expand...
Click to collapse
I had the same issue, I solved it by using an option from inside the Android settings, I think it was reset phone or something like that.
L.F.B. said:
Well, the good old stability and smoothness of LOS!
All pretty fine here! Franco Kernel working fine!
Please dev. Any root solution to remove brighness slider from quick settings?
Click to expand...
Click to collapse
Umm, is Franco Kernel even being updated for the Shamu anymore? It doesn't seem so, not sure why you are even flashing it. It'll be behind on performance and security updates.
wrsg said:
Did you try doing that, in spite of TWRP not being able to decrypt it? What error did you get?
edit: I guess it's too late for you to try this, I didn't read your latest reply until after typing that.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
I had the same issue, I solved it by using an option from inside the Android settings, I think it was reset phone or something like that.
Click to expand...
Click to collapse
So after the problems with mounting data, I formatted it with TWRP. Rebooted, finished the LOS 16 setup and all my apps where reinstalled.
Everything seems to work and guess what, I rebooted into TWRP and it is able to read everything on data. The strange thing is, it doesn't ask for the PIN.
Maybe its not encrypted ? I thought LineageOS 16 would encrypt it on install. How can I check ?
everdium said:
So after the problems with mounting data, I formatted it with TWRP. Rebooted, finished the LOS 16 setup and all my apps where reinstalled.
Everything seems to work and guess what, I rebooted into TWRP and it is able to read everything on data. The strange thing is, it doesn't ask for the PIN.
Maybe its not encrypted ? I thought LineageOS 16 would encrypt it on install. How can I check ?
Click to expand...
Click to collapse
LineageOS 16.0 does not force the encryption of your data. If you need a bit of security you can encrypt your data from within settings.
I wonder why some of you have problems with upgrading. I tried several combinations. Perhaps because TWRPs format is also broken and you didn't use the fastboot format command.
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
Ancient OS 6.4 ROM 26-01-2023
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
TWRP_SZANCSO.img is my work, included 4.9 kernel, included Midnight Commander (mc), fixed many factory bugs, working USB storage mode, and DT2W. Download link: ROM.
Boot into recovery
Wipe system, vendor, data, cache partitions to clean install.
(If your /data partition secured, maybe need format /data if you want to use this ROM.)
(If you are upgrading from a previous version of 6.4, you do not need to wipe the /data, but you need to wipe the Dalvik and Cache.)
Flash Rom in TWRP (sideload or copy any storage)
Flash OpenGapps (Optional) [I'm not using GAPPS, I'm not going to give you advice.] (NOT TESTED!)
Flash Magisk Root (Optional) [I'm not using Magisk, I'm not going to give you advice.] (NOT TESTED!)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to ~1-2 minutes.
Update 01-02-2023: switching to Weeabo version, fixing Bluetooth-calling issue
DOWNLOAD
Known issues: -
Not tested: VOLTE, GAPPS, Magisk
Screenshots: maybe soon...
TWRP kernel source: LINK
OS source: LINK
ROM OS Version: 12.1/L
ROM Kernel: Linux 4.9 Source
ROM info: 12L, system_root partition, Android quota removed (easier to go back to earlier 7.x-11.x ROMs), NOT encrypted.
Created: 26-01-2023 6.4 version
Last Updated: 01-02-2023 6.4 Weeabo version
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
Update 01-02-2023: switching to Weeabo version, fixing Bluetooth-calling issue