[10] [GSI] MSM-Xtended [ARM64-A/AB] [Experimental] - Treble-Enabled Device Development A/AB ROMS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Disclaimer:
We're not responsible for bricked devices, dead SD cards, thermonuclear war,
or you get fired because the alarm app failed. Please do some research
if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you blame me in any way for what happens to your device, I will laugh at you.
BOOM! goes the dynamite
Oh… Really I need to introduce them! .
Team "MSM Xtended" is here with new era of Android.
They have tried their best to blend it with all available options, features and stability of different ROMs in to one for better user experience.
Here
MSM Team
If you like their work you can buy them a cup of coffee:
SuperDroidBond
MSM-Xtended Website
MSM-Xtended Blog
ROM Download
Gapps Download
Magisk Download
For better user experience, it's recommended to flash Nano Gapps only.
Clean Flash
The basic steps for flashing a GSI are:
1. Download the GSI file and uncompress the .7z archive
2. Uninstall Magisk if it was previously installed, by using its uninstaller and reboot the phone
3. Wipe Data, Dalvik, and Cache partitions
4. Flash the GSI to system partition, GApps, and maybe specific files for your phone (see post 2)
5. Boot and perform a minimal setup (enabling USB Debugging as a suggestion)
6. Reboot into recovery and flash Magisk
7. Reboot to system and #GetXtended.
There is more detailed information on GSI and how to flash it on phhusson’s wiki and in his thread here on xda. Also vince31fr brings useful info and workarounds.
Dirty Flash
1. Download the GSI file and uncompress the .7z archive to get the .img file
2. (Optional) Uninstall Magisk if it was previously installed, by using its uninstaller and reboot the phone
3. Wipe Dalvik and Cache partitions
4. Flash the GSI (.img file) to system partition, GApps, and maybe specific files for your phone (see post 2)
5. Boot and perform a minimal setup (enabling USB Debugging as a suggestion)
6. If you uninstall Magisk (step 2), reboot into recovery and flash Magisk
7. Reboot to system and #GetXtended.
If you fail to follow these instructions, please don't bother reporting any bugs
If you use Xposed, please don't bother reporting any bugs
MSM-Xtended Sources
We would like to give thanks to everyone in the Android community, big or small.
That said, we would like to thank all These Teams for their contribution to the Open Source Community.
LineageOS/Cyanogenmod
GZOSP
ColtOS Team & Specially @Rakesh.Batra
OmniROM
Nitrogen OS
AICP
crDroid
DirtyUnicorns
Screwd AOSP
CypherOS
Liquid Remix
Benzo ROM
BootLeggers ROM
AOSP Extended ROM
Syberia-Project
PixelDust Project
Pixel Experience
Contributors: Technical
ROM OS Version: Android 10
Created: 2020-06-21
​

Issues and workarounds:
1. Check your phone compatibility with Treble before following these instructions.
2. Generally, smart charging feature (Settings > Battery > Smart Charging) does not work on Treble. You can have the same functionality using Battery Charge Limit app.
3. Can't flash Gapps due to error 70 (insufficient storage space available in System partition)? In TWRP, just go to Wipe menu > Advanced Wipe > check System partition > Partition options > Resize FS. Then flash Gapps again. In other recoveries, the steps are similar.
4. To get Viper4Android working on GSI ROMs, please, thank here or the Magisk modules.
5. For RAW support on cameras: Settings > Phh Treble Settings > Misc features > and select Expose Aux cameras (Qualcomm) if possible.
6. You may need to flash the vbmeta.img file specific for your device (firmware) before you first boot the GSI. Discover your actual slot: check in TWRP reboot options or in fastboot mode: fastboot getvar current-slot. Then run in the same slot you're flashing the GSI image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
7. If you lose Wi-Fi and/or Bluetooth, you should flash the dtbo.img file specific for your device (firmware). Discover your actual slot: check in TWRP reboot options or in fastboot mode: fastboot getvar current-slot. Then run in the same slot you're flashing the GSI image:
For A/B devices, run:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
For A-only devices, run:
fastboot flash dtbo dtbo.img
8. Additional files as Permissiver v5 and DM-verity, forced encryption, and disc quota disabler must be needed to boot.

Thanks

Gheartxz2017 said:
Thanks
Click to expand...
Click to collapse
If it works, please, give me feedback

Hi, is based in phh v220?

Os_Herdz said:
Hi, is based in phh v220?
Click to expand...
Click to collapse
It has all the latest phh patches that I manage to apply without breaking the gsi. Shortly, yes.

Technical said:
If it works, please, give me feedback
Click to expand...
Click to collapse
Only stay in bootanimation I flash permissiver but doesn't work

Not boot[emoji24]
Gửi từ SM-G610F của tôi bằng cách sử dụng Tapatalk

Thanks for the feedback. I'll need to figure out what happened. It will take a while

No build with gapps installed?

Technical said:
It has all the latest phh patches that I manage to apply without breaking the gsi. Shortly, yes.
Click to expand...
Click to collapse
Bootloop in bootanimation, tried enforce, tried permissive and with magisk but no booted. The bootanimation is really good.

Stucks at bootanimation ! Waiting a boot fix ! I love Xtended ROM.

muhamet said:
No build with gapps installed?
Click to expand...
Click to collapse
Probably not, it takes a lot of space and time to build (compared to vanilla versions). I have limited resources and it's being very challenging even to boot Gapps are not the focus right now.

Technical said:
Probably not, it takes a lot of space and time to build (compared to vanilla versions). I have limited resources and it's being very challenging even to boot Gapps are not the focus right now.
Click to expand...
Click to collapse
Do you find a solution to boot please ?

Dan225 said:
Do you find a solution to boot please ?
Click to expand...
Click to collapse
Not yet. Trying not to give up

Technical said:
Not yet. Trying not to give up
Click to expand...
Click to collapse
No solutions?

Technical said:
Not yet. Trying not to give up
Click to expand...
Click to collapse
Hi got my device back from the dead after a long time (nubia z17 8gb128gb )but now the world got android 10 even my device (lineage os 17.1 offical) for me:good:
But i dont have even manage to get a gsi to boot (except android 11 R aosp) can you give me a tip?

Guys, I'm trying to bring back camera to work in crDroid and EvolutionX. Both are booting ok.
MSM-Xtended revelead a much more difficult ROM to build. If I find the way to bring back a working camera there, probably it'll be easier to move there. There is no features on MSM that are missing on EvolutionX, for instance.
And I won't have time and resources (disk space) for a 3rd GSI.

On latest Phh build?

Technical said:
MSM-Xtended revelead a much more difficult ROM to build. If I find the way to bring back a working camera there, probably it'll be easier to move there.
Click to expand...
Click to collapse
May be it will help - https://4pda.ru/forum/index.php?showtopic=892755&view=findpost&p=94999066
Quote from next message on 4pda:
Igor~s said:
ROM is built with the settings to increase the system speed and system services optimization.
Click to expand...
Click to collapse

Related

[ROM][9.0][angler] Pixel Experience [AOSP][2019/12/13]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Nexus 6P [angler]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 9.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Facelock
Known issues
Nothing
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 9.0.0_r46
Security patch level: December 2019
Build author/Device Maintainer: PixelBoot
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
​
XDA:DevDB Information
PixelExperience Pie, ROM for the Huawei Nexus 6P
Contributors
PixelBoot
Source Code: https://github.com/PixelExperience
ROM OS Version: 9.x Pie
ROM Firmware Required: TWRP, Unlocked bootloader
Based On: AOSP
Version Information
Status: Stable
Created 2018-11-22
Last Updated 2019-12-14
Installation Instructions:
Grab our recovery from the peripherals section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.
A few notes before you proceed:
Before going straight to the download section there’s something we would like to tell you. We have changed the default encryption method for the phone, migrating to File-Based Encryption (you can get more information from the official Google documentation page). In order to get this encryption mode working, you will need to use our custom recovery (compiled from the latest source) which is compatible with this encryption and, just for the first time, you will have to wipe your internal data, so backup your data before proceeding.
Peripherals:
FBE Recovery: TWRP
Nexus 6P PixelExperience Telegram Group: Join
Thread reopened and cleaned since builds are now stable!
Big thanks to StatiXOS team for the sources.
Check them out here: https://github.com/StatiXOS
Can we use stock TWRP instead of FBE version and skip encryption?
wizardwiz said:
Can we use stock TWRP instead of FBE version and skip encryption?
Click to expand...
Click to collapse
Regular TWRP will not work, and will result in bootloops, or infinite boot cycle.
Kindly take your time and flash the FBE version of TWRP.
In the long run, they're basically the same thing, so I don't see why not. ^^
PixelBoot said:
Regular TWRP will not work, and will result in bootloops, or infite boot cycle.
Kindly take your time and flash the FBE version of TWRP.
In the long run, they're basically the same thing, so I don't see why not. ^^
Click to expand...
Click to collapse
OK, thanks for the reply.
Is there an option to keep the file system un-encrypted or is it a must?
wizardwiz said:
OK, thanks for the reply.
Is there an option to keep the file system un-encrypted or is it a must?
Click to expand...
Click to collapse
I believe it's a must.
I know it sounds annoying in real-time but it is really handy in reality.
So far working well. Thanks
Someone who shows screenshots ..?
Hi, so I just installed the ROM and my phone has powered up now. The only issue that I'm facing is that I keep on getting an error saying "Bluetooth Keeps Stopping", what could be the issue? :/
Whats the default password for TWRP?
PixelBoot said:
Installation Instructions:
Note: If your phone only has 4 cores, download the BLOD patch (you can find it in the download section), flash our recovery.img from your working TWRP and then install the BLOD patch.
Grab our recovery from the peripherals section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.
Click to expand...
Click to collapse
Nice to see you back again. I thought you forgot about us after the thread being closed. Thanks Dev
Gearswar said:
Nice to see you back again. I thought you forgot about us after the thread being closed. Thanks Dev
Click to expand...
Click to collapse
I cleaned it to get a fresh start!
Official Support is now out for Angler!
Get your hands on it now!
Google Nexus 6P (angler)
PixelBoot said:
I cleaned it to get a fresh start!
Click to expand...
Click to collapse
Thanks Dev @PixelBoot for your time and effort.
Will start happy flashing today
Thanks
@PixelBoot im getting Android setup keeps stopping error, any solution?
thanks
Cannot boot into rom, always reboots to recovery.

[OFFICIAL][9.0]ProjectTitanium Beta ARM64 A-A/B[GSI][Update 02/07/2019]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is ProjectTitanium?​"ProjectTitanium is an GZOSP-Based-Custom Aftermarket Firmware Distribution for Android Devices. Our Goal is to Deliver Performance with many Features, Security, Cleanliness, and good Battery Life, Trying to make Something Unique than any other Android ROM. We Hope That you'll Love our Work, and help us in Making it even Better in the Future.
Features:​Work In Progress
Featured Stuffs:
- TiPapers
- About ProjectTitanium
-WIP
And many more being added regulary! *soon
Installation:​Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest ProjectTitanium ROM & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ProjectTitanium ROM
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
Downloads:​A/B: PTi-Beta-0.5-GSI-ARM64-AB-OFFICIAL(update 02/07/2019)
Only A: PTi-Beta-0.5-GSI-ARM64-A-OFFICIAL (update 02/07/2019)
GApps
Source Code:​ProjectTitanium
Credits:​
-@XTutorials(Founder/Lead Developer)
-@DarkJoker360(Co-Founder/Lead Developer)
-@Thespartann(Senior Developer)
-@K3RN3L_P4N1C(Web Developer)
- Phhusson for Treble trees
- LineageOS
- GZOSP
REPORTING BUGS/PROBLEMS!
As soon as the problem occurs, feel free to tell me or, if possible, send me a logcat and I'll see what I can do!​
Have a feature request? Don't spam here. Visit our Telegram group!
ProjectTitanium Official Website:
ProjectTitanium
ProjectTitanium Official Telegram group:
Telegram
Support us!
Hello, Gracious human! if you like our work, you may support us by donating:
PayPal
Note
This ROM is in Beta state for now, I uploaded it here mainly for testing purposes(not that it can't be used as a daily ROM, it can actually, it just doesn't have all the things the final 1.0 will have.
​
A/B one does not boot on Xiaomi Mi 9 (Vendor used: Xiaomi.eu 9.5.30)
all other GSIs do boot with exact same procedure.
Mohammed779 said:
A/B one does not boot on Xiaomi Mi 9 (Vendor used: Xiaomi.eu 9.5.30)
all other GSIs do boot with exact same procedure.
Click to expand...
Click to collapse
Ah, damn. Let me see what I can do. Thanks for the report.
Could you give me any log?
Mohammed779 said:
A/B one does not boot on Xiaomi Mi 9 (Vendor used: Xiaomi.eu 9.5.30)
all other GSIs do boot with exact same procedure.
Click to expand...
Click to collapse
Same issue for same device.....
I will test it on s9+ and let u know if it boots or no
Update coming this night fixing hopefully all boot issues, even though on some devices it boots...
Regards,
ARM 64 A Only build boots fine on ZTE Axon 7. I had a quick browse through Settings, seems very barebones. I don't blame ya, you said yourself it's in beta. I'll keep an eye out for when you've had a chance to update it
Booted on s9+ but the rom is like stock aosp no features or anything, maybe because it is still on beta
Update 02/07/2019!
Good Evening! I'm back as I said, and here is the update for this ROM.
Changelog:
-Boot issues fixed!
-Vendor fixed!
-New stock wallpaper
-Fixed build number bug
-Other miscellaneous fixes
Download:​Only A:
PTi-Beta-0.5-GSI-ARM64-A-OFFICIAL
A/B:
PTi-Beta-0.5-GSI-ARM64-AB-OFFICIAL
Best Regards!​
A/B Build added to the update reply, now since the builds should work our team is going to start working on actually bringing features to this.
Hopefully sooner than you think.
Regards,
Akhayev said:
Booted on s9+ but the rom is like stock aosp no features or anything, maybe because it is still on beta
Click to expand...
Click to collapse
Would you please tell the Firmware and Vendor you are on . Thank you !
fares70 said:
Would you please tell the Firmware and Vendor you are on . Thank you !
Click to expand...
Click to collapse
Brk3 vendor , and firmware use the one u already using ,
XTutorials said:
A/B Build added to the update reply, now since the builds should work our team is going to start working on actually bringing features to this.
Hopefully sooner than you think.
Regards,
Click to expand...
Click to collapse
Do you mean this ROM is intended to be feature-rich like Havoc, Liquid, PixelDust...?
Boots on Blu Vivo XI.
Hello Goodnight.
I previously installed GSI roms.
but now I try to install with the usual procedure
for my G9600 S9
but I can not get into the system
it always stays in the logo and never passes from there.
I already wait more than 25 minutes and nothing.
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
Unpack it if it wasn't in .IMG format
Wipe DATA, and reboot in TWRP
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Install the kernel for GSI GSI Kernels
In TWRP mount System, then go to ADVANDED, File Manager, and delete this file: system/bin/rw_system.sh
Reboot system
What is wrong?
Technical said:
Do you mean this ROM is intended to be feature-rich like Havoc, Liquid, PixelDust...?
Click to expand...
Click to collapse
Well, we want to make something different from any other ROM, but yes, it will also have plenty of features enough to satisfy everyone, hopefully also reaching my intentions. We intent of bringing 1.0 this fall.
Regards,
hi Guys
I can not install a gapps twrp error 70 otherwise rome runs well and as always with my asus zenfone 5 ze620kl automatic brightness does not work ..
can you please build a rome with gapps.
Thank you
XTutorials said:
Well, we want to make something different from any other ROM
Click to expand...
Click to collapse
What do you mean?
Until May I was able to compile Bootleggers, Havoc and Liquid. Since then, sepolicy and other specific issues are blocking building or booting later. I like featured rich ROMs and I could help to compile Titanium, although my knowledge is not enough to help you, devs.
---------- Post added at 08:19 ---------- Previous post was at 08:14 ----------
barbaross said:
hi Guys
I can not install a gapps twrp error 70
Click to expand...
Click to collapse
In TWRP, just go to Wipe menu > Advanced Wipe > check System partition > Partition options > Resize FS. Then flash Gapps again.
Technical said:
What do you mean?
Until May I was able to compile Bootleggers, Havoc and Liquid. Since then, sepolicy and other specific issues are blocking building or booting later. I like featured rich ROMs and I could help to compile Titanium, although my knowledge is not enough to help you, devs.
Click to expand...
Click to collapse
Well, this ROM can be build as any other ROM, so anyone with some Linux knowledge should be able to build this, as any other ROM.
And soon accepting official maintenance!
mezacorleehone said:
Hello Goodnight.
I previously installed GSI roms.
but now I try to install with the usual procedure
for my G9600 S9
but I can not get into the system
it always stays in the logo and never passes from there.
I already wait more than 25 minutes and nothing.
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
Unpack it if it wasn't in .IMG format
Wipe DATA, and reboot in TWRP
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Install the kernel for GSI GSI Kernels
In TWRP mount System, then go to ADVANDED, File Manager, and delete this file: system/bin/rw_system.sh
Reboot system
What is wrong?
Click to expand...
Click to collapse
First you need BRK3 vendor , and flash aosp kernel not gsi , the best kernel is Endurance-Kernel-AOSP-1.2.30.zip
First, wipe system data cache and then flash vendor then flash the rom then flash kernel the magisk then reboot ot will work fine , no need to delete rw_system or anything

[ROM][PIE-9.0][UNOFFICIAL] Cosmic-OS v4.0 - Corona (FBE) [2019/09/03]

[ROM][PIE-9.0][UNOFFICIAL] Cosmic-OS v4.0 - CORONA [Angler][2019/09/03]
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Cosmic-OS is a Custom ROM based on Android Open Source Project (AOSP) with additional features, performance and battery life improvements.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions for flashing:
Download ROM and GApps.
Copy ROM and GApps to internal storage.
Wipe /data, /system and /cache.
Flash ROM and GApps
Enjoy
Note: First boot and boots after every update can take some time. They may even loop a few times. We do not support custom kernels or mods like MultiROM. If you have an issue, make sure your edits aren't interfering with the issue you're reporting.
ROM
GAPPS
For GAPPS visit the site, select ARM64 in the Platform section, 9.0 in the Android section & in the Variant section choose the type of package you want to install.
Credits
- @sagarshah1729 (Founder/Lead Developer)
- @Sid_Sun (Contributor)
- @Agent_fabulous (Contributor)
- Nitrogen Project
- LineageOS
- AOSCP
- OmniROM
- ABC ROM
- Dirty Unicorns
- Kabou Zeid for Phonograph
Have a feature request? Don't spam here. Visit our Google Plus community or Telegram group
Cosmic-OS Official Website:
Cosmic-OS
Cosmic-OS Google Plus community:
G+
Cosmic-OS Official Telegram group:
Telegram
Support Us
Hello, Gracious human! if you like our work, you may support us by donating:
Paypal
PayTM​XDA: DevDB Information
CosmicOS Pie, ROM for the Huawei Nexus 6P
ROM OS Version: 9.x Pie
ROM Firmware Required: TWRP, Unlocked bootloader
Based On: AOSP
Version Information
Status: Stable
Build Date:2019/09/03
Contributors
@PixelBoot (helping me out) @beingmishra (source and server) @amallxw
Rom Source: https://github.com/Cosmic-OS/
A few notes before you proceed:
Before going straight to the downloading, there’s something we would like to tell you. We have changed the default encryption method for the phone, migrating to File-Based Encryption (you can get more information from the official Google documentation page). In order to get this encryption mode working, you will need to use our custom recovery (compiled from the latest source) which is compatible with this encryption and, just for the first time, you will have to wipe your internal data, so backup your data before proceeding.
Installation Instructions:
Grab our recovery and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.
Is this system-as-root? I'm BLOD and patch won't work if it is!
Sent from my Nexus 6P using XDA-Developers Legacy app
bigcelo75 said:
Is this system-as-root? I'm BLOD and patch won't work if it is!
Click to expand...
Click to collapse
This is system-as-root
we made a build for 4core devices with the patch but there few features which don't work.
I'll be building EvolutionX in few days.
I'll try not to make it SAR so that you can flash the blod patch
amallxw said:
This is system-as-root
we made a build for 4core devices with the patch but there few features which don't work.
I'll be building EvolutionX in few days.
I'll try not to make it SAR so that you can flash the blod patch
Click to expand...
Click to collapse
I appreciate that my friend. Looking forward to it![emoji6]
Sent from my Nexus 6P using XDA-Developers Legacy app
Installed it with no issues and so far so good. It's a complete rom, has everything i need even gray scale reading mode. Didn't notice any battery drain for now, but still i always enable agrressive sleep and standby. Will give any further thoughts after i used it for a while. The onyl thing is that the simple gapps do not work on this rom, had to use open gapps.
sage of six paths said:
Installed it with no issues and so far so good. It's a complete rom, has everything i need even gray scale reading mode. Didn't notice any battery drain for now, but still i always enable agrressive sleep and standby. Will give any further thoughts after i used it for a while. The onyl thing is that the simple gapps do not work on this rom, had to use open gapps.
Click to expand...
Click to collapse
aight
?
Oke so my review in short. The rom is as most roms just fine. For my usage i have no bugs to report. The only slight potential donwside might be that the battery life was not as good as on pixy or superior os, but its not far behind. However this might be due to, I've used a lot more lte with this rom than on those since I'm back to work form vacation, and second that my battery might be giving me slight signs it'll need a replacement soon. So take the battery thing with a grain of salt, try it your self first and compare.
Is there a feature list for this rom?
MaddScientist said:
Is there a feature list for this rom?
Click to expand...
Click to collapse
check website?
Hi, thanks for the ROM, runs great from the short time I had on it (forgot to get gapps package) when I got opengapps 9.0 stock it said that the ROM needed opengapps for 8.1, same with Pico, pretty confusing. Any help would be great
Gapps issue
I even tried Simple Gapps, thinking maybe they would work. Will try 8.1, but it definitely won't use 9.0 gapps. BTW, I downloaded the nano gapps. Other than that, this rom is absolutely beautiful. It is fast, and it is just a very good-looking rom. So, I hope you keep working on this. I can't say enough about how quick it is. So, thanks, and I hope the gapp thing can be worked out. Okay, what ended up working was ARM 8.1 gapps. NOT arm 64. Not sure why or how. Just FYI. Thanks.
I shall be trying this ROM out soon. I have to flash gapps 9.0 arm 64?
sufy1000 said:
I shall be trying this ROM out soon. I have to flash gapps 9.0 arm 64?
Click to expand...
Click to collapse
Yes,,,flashed it today ,, Currently using it
abdullahk6809 said:
Yes,,,flashed it today ,, Currently using it
Click to expand...
Click to collapse
I just tried to flash 9.0 pico package. It said it was the wrong version, and I needed 8.1 gapps. What package did you use?
9.0 Gapps not working
kenetix said:
I just tried to flash 9.0 pico package. It said it was the wrong version, and I needed 8.1 gapps. What package did you use?
Click to expand...
Click to collapse
UPDATE. I did find a way that worked for me. https://forum.xda-developers.com/nexus-6p/development/rom-dot-os-3-0-t3898420/page25
All credit goes to that guy for figuring this out.
Can anyone help me here
I tried fashing the FBE recovery via fastboot and the cmd shows that it's finished flashing but I am not able to boot into recovery instead I stuck in GOOGLE logo
Skull2candy said:
Can anyone help me here
I tried fashing the FBE recovery via fastboot and the cmd shows that it's finished flashing but I am not able to boot into recovery instead I stuck in GOOGLE logo
Click to expand...
Click to collapse
You are on custom rom(fde) before flashing it?It would be better if you explain your problem in detail.
abdullahk6809 said:
You are on custom rom(fde) before flashing it?It would be better if you explain your problem in detail.
Click to expand...
Click to collapse
I don't have any rom installed and my phone is 4core

Development [ROM][12][OOS CAM] CherishOS 3.4.5 for OnePlus 9R [OFFICIAL][2022-02-21]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH(for first install) :​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Format Data & Reboot to System
2nd Method(Using Sideload):
Note: You can't sideload with any recoveries, only some recoveries support sideloading this rom. I have provided one below
1. Download ROM zip from sourceforge and put it in adb folder
2. Download recovery.img from here
2. Put it in the folder where you have your adb files, and then open a terminal and execute the command
Code:
fastboot flash recovery recovery.img
3. Reboot to recovery
4. Choose "Apply update"
5.
Code:
adb sideload rom.zip
6. Reboot to recovery
7. Factory reset / Wipe all data
8. Reboot system
Dirty Flash(to update):​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Reboot to System
2nd Method(Using Sideload):
1. Download ROM zip from sourceforge and put it in adb folder
2. Reboot to recovery
3. Choose "Apply update"
4.
Code:
adb sideload rom.zip
5. Reboot to recovery
6. Reboot system
Download ROM(Gapps)
-Lineage OS
-AOSP
-Pixel Experience
-DotOS
- @1249131356
- @chandu dyavanapelli
- Others who I forgot to mention
Based on Android 12.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
You tell me? (none)
Cherish-OS Source
Kernel Source
Telegram Group
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
​CherishOS for OnePlus 9R
Device: lemonades
Maintainer: @Amsal1
Build Type: Official
ROM Kernel: Linux 4.19.225
Based On: AOSP
Android OS version: 12
Security patch level: January 2022
Version Information:
Status: Stable
Current Stable Version: 3.3.5
SELinux Status: Enforcing
Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Its a unified build of kebab and lemonades which is using kebab as codename in the rom
Reserved
Hi. Just wanted to flash this rom but unable to find the payload.bin file after extraction.
Please help. Thanks in advance
HULK2275 said:
Hi. Just wanted to flash this rom but unable to find the payload.bin file after extraction.
Please help. Thanks in advance
Click to expand...
Click to collapse
Its inside the ROM zip which is of about 1.91GB size
Amsal1 said:
Its inside the ROM zip which is of about 1.91GB size
Click to expand...
Click to collapse
Thanks. Will dirty flash work on this rom?
can you help me to flash this rom on my OP 9R ??
fakesoul1234 said:
can you help me to flash this rom on my OP 9R ??
Click to expand...
Click to collapse
Follow OP instructions.
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download and extract the ROM zip & find the payload.bin file.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Format Data & Reboot to System!
HULK2275 said:
Thanks. Will dirty flash work on this rom?
Click to expand...
Click to collapse
Yes, you can dirty flash further new releases of this rom.
Want to try this ROM, but do the banking and payment apps work and also does it show certified in playstore ?
ASTR05 said:
Want to try this ROM, but do the banking and payment apps work and also does it show certified in playstore ?
Click to expand...
Click to collapse
Yes, safetynet pass by default and device is certified. Follow the OP instructions for flashing the rom.
Hi All,
Just wanted to know when using this Rom on One Plus 9R, the charging speed varies between 2297mA or 9W approx and doesn't charge in higher speed i believe so i think its not as fast as OnePlus OOS. Any suggestions to fix it boys?
can cn version LE2100 flash this rom?
jojowithecho said:
can cn version LE2100 flash this rom?
Click to expand...
Click to collapse
Yes.
Update - 3.4
Device Changelogs:
- Enabled QuickTap
- Switched to IllusionX kernel
- Updated WFD Stack from lemonadep
- Added min/max refresh rate settings
- Improve rounded corners
- Added themed icons for oneplus camera & gallery
- some more improvements and fixes
Quick question, do we need to first unlock bootloader before flashing this rom in OP9R?
Got bootloop after rebooting to recovery after flashing the rom (the 5th step of the 1st method).
upd: unbricked and tried another time, it's ok.
upd2: nice rom, works pretty good, thanks a lot!
nitishkadwal01 said:
Quick question, do we need to first unlock bootloader before flashing this rom in OP9R?
Click to expand...
Click to collapse
yes
Hi Cherishos Developer, I'm Using latest version rom on my oneplus 9R, Very Stable with More customization. But I'm facing one Big issues with the Fingerprint Scanner, It works fine in Lockscreen unlocking but, while using fingerprint unlock for app lock the entire display was flashing while touch a screen not only in (FP Area). While using in dark place in low brightness It was a uncomfortable to use. Otherwise this rom is very stable to use as daily driver.
Overall My Suggestion:
* Need to Re-Calibrate Fingerprint Scanner and Some Bugs
And, I Appreciate the Developer Efforts for Build this Awesome Rom For Oneplus 9R
Thank you Dev
kiruba Developer said:
Hi Cherishos Developer, I'm Using latest version rom on my oneplus 9R, Very Stable with More customization. But I'm facing one Big issues with the Fingerprint Scanner, It works fine in Lockscreen unlocking but, while using fingerprint unlock for app lock the entire display was flashing while touch a screen not only in (FP Area). While using in dark place in low brightness It was a uncomfortable to use. Otherwise this rom is very stable to use as daily driver.
Overall My Suggestion:
* Need to Re-Calibrate Fingerprint Scanner and Some Bugs
And, I Appreciate the Developer Efforts for Build this Awesome Rom For Oneplus 9R
Thank you Dev
Click to expand...
Click to collapse
Already fixed in upcoming build ))
One more bug: reset battery stats feature doesn't work.

[ROM][12.1][UNOFFICIAL] PixysOS [PL2]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Pixys is a butter smooth Android aftermarket firmware. We handpicked the best features around and are adding our own juice into it.
Get ready to taste the unique features it brings with itself.
We aim to deliver an experience with original ideas and features along with the useful things the community is accustomed to.
@Subinsmani
@rahul9999
@@ki
@Shreejoy Dash
@kvijaya
@AxelBlaz3
@Psycho-Mods
@aswin_a_s
@Gero
@melvingarcia
Support Us if you like our work
Got an issue or suggestion? Reach us at
Telegram: https://telegram.me/pixysos_chat
Phone calls & messaging
Wi-Fi & Mobile data
VoLTE (but no icon in statusbar)
Fast charging
Dark theme, night mode
Fingerprint sensor
Face unlock
NFC
FM Radio
Wireless Bluetooth audio with AptX codec
and much more...
Less customizations but more stability...
Pixys: PixysOS
Pixys Device Sources: PixysOSDevices
NOTE: It is recommended to update your stock ROM to Android 10 before flashing this custom ROM.​
IMPORTANT: If you want to use GAPPS build, it is necessary to resize system and vendor partition on your phone before flashing rom! This step will perform format of system and vendor partition and even userdata partition so make a backup if you don't want to lose your data!
If you downloaded VANILLA build, you can skip this step and if you want then you can flash gapps of your choice.
Please download this nice and user friendly Nokia Repartition Tool brought to you by Raghu Varma and look at this instructional video:
Just use the first option "3.5G S - 1G V" - it is enough for this rom.
NOTE: After resize your phone will be automatically booted to TWRP, but because this tool is intended for Nokia 6.1 Plus, this TWRP will refuse to flash ROM zip on 6.1. In this case just reboot to bootloader and download this TWRP for our Nokia 6.1, boot it and everything will be fine. Now you can begin flashing.
After booting to TWRP:
1) If you just resized your system and vendor partitions using Nokia Repartition Tool then you have already formatted userdata so you can skip this step, otherwise if you want to do a clean flash then please Format Data by typing yes, then go to the Bootloader and reboot TWRP. (For dirty flash use adb sideload method because TWRP can not decrypt Android 12 userdata partition.)
2) Flash latest ROM zip via TWRP
3) Switch to alternative slot (if you are on slot a switch to b if you are on b switch to a)
4) Reboot system
Now you are done!
SafetyNet on latest PixysOS builds passes out of the box, so you won't need root/Magisk anymore. Flash Magisk only in case that you really need to root your device.
ROM: Sourceforge download link​At the download page, you can choose GAPPS build (with Google play store and other apps included) or VANILLA build, which contains only basic apps without Google play store (in this case you can flash gapps of your choice).
Wi-Fi Hotspot works only without password. FIXED
Custom statusbar icon pack is reverted back to default after device reboot.
Credits:
- Google for AOSP
- Dirty Unicorns
- Pixel experience
- AOSP extended
- LineageOS
- Superior OS
- Statix OS
- YAAP
- Krypton AOSP
- Project-Kaleidoscope
- AICP & POSP Team for thread template idea
- Also many pro developers who all help us to bring this rom to you...
- Please let us know if we forgot to mention your name in credits...​
Contributors:
Big thanks to LineageOS developers and maintainers for Nokia 6.1 device and vendor tree on which this build is based!
Since PixysOS v5.1.5 thanks to Raghu Varma Android developer for new Nokia 6.1 device tree + vendor and kernel sources!
Kernel source:
https://github.com/LineageOS/android_kernel_nokia_sdm660
Kernel source since PixysOS v5.1.5:
https://github.com/RaghuVarma331/android_kernel_nokia_sdm660/tree/android-12.0-gcc
ROM OS Version: 12.1
ROM Kernel: 4.4.x
Based On: AOSP
Version Information
Status: Stable
Current Version: v5.1.5
Hey, really appreciate your work!) Specific bug for your rom is inability to setup magisk, because stock rom recovery "Failed to clear BCB message" error, adb sideload method doesn't works in it too. If i flash boot TWRP, then I can't boot rom, it stucks on boot logo. General bugs for all roms, such as hanging vibration (12.1 bug), gcam, that after some time of use can't take photos are here. Again. thanks for your work!!
Hi, thanks for your reply! Magisk works on this ROM, I just tested the version 24.3.
You need to boot into TWRP (twrp-3.4.0-0-PL2_sprout-11.0-20200909.img), select adb sideload option and flash latest Magisk zip. Then reboot and check the magisk app. Now you are successfully rooted. ;-)
Note: If you are installing Magisk right after flashing rom, don't forget to switch slot first!
I tried to install magisk right after I installed rom. For example now I am on a slot B, rom is installed on slot A. Magisk would setup on current slot, not as rom, that would setup on inactive slot -> I need go to the A slot to setup magisk. If I try to do that through stock rom recovery on slot A, I get error, because ADB sideload isn't working. If I try to "fastboot flash "twrp"" on slot A, then I can install magisk, but I am stuck on the rom boot logo. If I try to use twrp install.zip file from TWRP on slot B, then I get would the same problem (boot logo) on slot A. ADB sideload is installing magisk in current slot, that's why I can't do it from slot B to setup magisk on slot A. It's a bit sadly. And the second question to you, why our community vendor has general GCam problem, that is on all roms? Maybe you can contact to developers of it to fix that problem? Because it's really shame bug)
Just tell me about the experience you had with the Rom. is it smooth or not
Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.
Gcam not working fix it
Machi007 said:
Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.
Click to expand...
Click to collapse
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)
Rbargujar said:
Gcam not working fix it
Click to expand...
Click to collapse
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
FarLine99 said:
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)
Click to expand...
Click to collapse
I don't understand why to use stock recovery when we have TWRP.
Machi007 said:
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
I don't understand why to use stock recovery when we have TWRP.
Click to expand...
Click to collapse
Because if we try to use flash boot twrp on rom slot, then rom can't boot, it stuck on boot logo)
OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.
Machi007 said:
OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.
Click to expand...
Click to collapse
Maybe) In my experience, if I flash TWRP after flashing rom the rom doesn't boot, at all. Maybe I have done something wrong, but any way, if you will fix the stock recovery, it would be better!)
I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.
Machi007 said:
I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.
Click to expand...
Click to collapse
I tried to use twrp installer first, it did not worked for me, then I tried to use fastboot flash boot method, that is recommended for this TWRP. Using both flash recovery and boot method is new for me, so maybe it will be ok. But flash boot method doesn't work. And yeah, I used recommended from you Raghu's TWRP.
New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!
Machi007 said:
New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!
Click to expand...
Click to collapse
Maybe would try later, thanks for your work!)
Is anyone able to check if Duo Mobile 2fa is working?
I did all the steps, installed the rom, It siad "Fhasing A/B Zip to ianctive slot: B" after I try to change the slot and reboot, it says no OS installed... Is anyone else having this issue?
I did the Nokia Partition Tool, rebooted to bootloader, booted into the 3.4 TWRP it suggested and did the steps, It still said the error and rebooted back into TWRP*
EDIT: I was redoing it for the 3rd time as I typed this message and it magically worked.
Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too? Perhaps then the installation would fit on the device without repartitioning -- I have made a couple of observations that have made me arrive at this conclusion:
My experience with LineageOS 19 is that the build + MindTheGApps package fits on the stock system partition without the need for repartitioning.
On the official PixysOS downloads page, I see that the size difference between Android 12 vanilla and GApps builds for one of the devices is something like 600 MB.
I am downloading the build at this instant, and I'm going to try fiddling around with the system image to make it fit on my PL2 before resorting to repartitioning (because we all know how much of a pain that can be ). I intend to install it later in the day, so I don't yet have feedback on the build itself.
Cheers! And thanks for your effort and time!
EDIT: I must also add that for a) people who prefer to use only core Google apps like GMS and Play Store (e.g. myself), and b) people who do not want to use even core Google services, a vanilla build would be ideal.
Vedanth Padmaraman said:
Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too?
Click to expand...
Click to collapse
I'll consider it, maybe from the next build I'll provide both versions.

Categories

Resources