ROM thread text:
This is crDroid for 5.5" Pixel XL [marlin]
crDroid Website: https://crdroid.net/
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
Vendor image for current build - OPM4 July vendor image - DOWNLOAD VENDOR
GAPPS: For now, open gapps unofficial, also courtsey @razorloves - DOWNLOAD GAPPS
OpenGapps: Not Supported anymore, use @razorloves gapps.
First time installing crDroid to your PixelXL, or coming from another ROM:
**NOTE** As you probably know by now, marlin (and sailfish) is weird. You must be on TWRP 3.2.0.0 to install this! 3.2.1.0 does not allow ROM installation. 3.2.0.0 does not encrypt properly, so you must remove your PIN/password before booting to and / or installing it. These installation instructions will assume you already know and have done that.
**NOTE** You are also able to use 3.2.1.-2 (3.2.0.0 or 3.2.1.-2)(Nothing in between)
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip & vendor img to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
5) Flash TWRP ***If you do not do this, you will lose TWRP!***
6) Reboot back into TWRP
7) Flash vendor image
7a) Mount vendor partition, navigate to vendor/overlay and delete that folder
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk 16.2
If you like music like I do and want to make it better, see post #3 for instructions on installing ViPER4Android.
Instructional Video
I Apologize about video quality, but this will help get you an idea of the steps involved.
Steps are the same for Marlin and Sailfish. Use corresponding files for device.
https://youtu.be/mmxIrp7BiRk
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
None yet, If you find something that is consistently reproducible, do so and pull a log. Without logs, we cannot fix the bugs. Please report any that you run into, assuming you have tested on a clean install. :good:
NOTE ON SUBSTRATUM
We currently do not have substratum commits in the ROM because they have not updated their repos on git for Oreo. As such, if you want to use Substratum, you will be doing so by allowing root and using legacy mode. you -must- make sure whatever theme you try supports 8.1. Even some that say they support Oreo may only work with 8.0, not 8.1. I'd recommend the following:
Suggestion: whenever installing themes, remove your pin/password so you can get TWRP to mount data.
If you get in a FC/bootloop situation, boot to TWRP, mount data and remove the file /data/system/overlays.xml.
That should allow you to boot and uninstall the overlays without reinstalling anything.
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- @razorloves - Without his device tree and kernel bringup to work from, crDroid for marlin would not be possible at all. Apart from the ROM development itself (for which @neobuddy89 bears the largest burden, in addition to the great developers of LineageOS itself), credit for this ROM being able to even build goes to razorloves.
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
crDroid G+ community
Source Code:
Device tree: https://github.com/razorloves/android_device_google_marlin
Kernel tree: https://github.com/razorloves/android_kernel_google_marlin
Vendor tree: https://github.com/razorloves/proprietary_vendor_google
Credit for all of those trees goes to @razorloves , without whose work crDroid for marlin would be a shell of itself!
XDA:DevDB Information
[ROM] [marlin] [8.1] [LOS-based] **crDroid**v4.7, ROM for the Google Pixel XL
Contributors
hokiealumnus, neobuddy89, BHermes21, razorloves
Source Code: https://github.com/crdroidandroid
ROM OS Version: 8.x Oreo
Version Information
Status: Nightly
Current Stable Version: v4.0
Stable Release Date: 2018-03-23
Beta Release Date: 2018-01-19
Created 2018-01-09
Last Updated 2018-10-12
I already said it in my post above, but feel it needs repeating. HUGE thanks to @razorloves , without whose marlin bring-up this ROM would still not be built.
*** NOTE - We cannot actively support audio (or any other) mods. I'm posting this because it works for me and I use it personally. This is not supported by our ROM team. Only the ROM / vendor / gapps and nothing else is supported by the crDroid development team. ***
If you like music as much as I do and prefer to use Viper4Android, install it as follows:
0) This requires Magisk; install Magisk 15.2 (as of 1/9/2018)
1) Using a root explorer (I prefer FX File Explorer), navigate to /system/system/priv-app/AudioFX and rename AudioFX.apk to AudioFX.BAK. Reboot.
2) Install three Magisk modules:
a) Magisk SELinux Permissive Script (Get it here: https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549)
b) Busybox for Android NDK v1.27.2 by osm0sis (Get it from Magisk downloads in the Magisk app)
c) ViPER4Android FX v2.8 by ahrion, zackptg5 (Also from Magisk downloads)
3) Reboot.
4) Enjoy your better music!
Sweet thanks
Awesome! I know I asked this on the nougat version, does the unlimited photo storage work? I noticed on the unofficial LOS rom by @razorloves it's been enabled, but I wanted to confirm. I'm still running nougat because I've been waiting for an oreo rom that has DUI.
hokiealumnus said:
This is crDroid for 5.5" Pixel XL [marlin]
If you're looking for the 5" Pixel [sailfish], it is not built yet; sorry.
Click to expand...
Click to collapse
Yet...... Hahaha there's still hope! Thanks for your work as always man. crDroid on N was solid as it gets!
Awesome thank you. Flashing now
Akomack said:
Awesome! I know I asked this on the nougat version, does the unlimited photo storage work? I noticed on the unofficial LOS rom by @razorloves it's been enabled, but I wanted to confirm. I'm still running nougat because I've been waiting for an oreo rom that has DUI.
Click to expand...
Click to collapse
It -says- it does in Photos. However, it said it did in Nougat, but never did actually work in any LOS / LOS-based ROM. It took up storage space even though the Photos app said back up all you want with Pixel. Therefore I can't promise full functionality. The app does say it works though.
thebigdonny said:
Yet...... Hahaha there's still hope! Thanks for your work as always man. crDroid on N was solid as it gets!
Click to expand...
Click to collapse
No promises on a time frame though I'm sorry to say!
hokiealumnus said:
No promises on a time frame though I'm sorry to say!
Click to expand...
Click to collapse
Soon TM
Added instructions for using Viper4Android in the 3rd post while they're still working on a functioning ARISE.
Works very good only one force close which I just uninstalled and reinstalled anyway been running du 12.0 nice change thanks
hokiealumnus said:
If you like music as much as I do and prefer to use Viper4Android, install it as follows:
0) This requires Magisk; install Magisk 15.2 (as of 1/9/2018)
1) Using a root explorer (I prefer FX File Explorer), navigate to /system/system/priv-app/AudioFX and rename AudioFX.apk to AudioFX.BAK. Reboot.
2) Install three Magisk modules:
a) Magisk SELinux Permissive Script (Get it here: https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549)
b) Busybox for Android NDK v1.27.2 by osm0sis (Get it from Magisk downloads in the Magisk app)
c) ViPER4Android FX v2.8 by ahrion, zackptg5 (Also from Magisk downloads)
3) Reboot.
4) Enjoy your better music!
Click to expand...
Click to collapse
Bruh, gimme the credit, if u want atmos and any other mod for 8.1 here's the link https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124/page1
kingbri said:
Bruh, gimme the credit, if u want atmos and any other mod for 8.1 here's the link https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124/page1
Click to expand...
Click to collapse
Why would I give you credit? I've never even seen that post.
Are there any custom kernels that will work with this ROM right now?
Sent from my Pixel XL using Tapatalk
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
*Update*
For those of you that get stuck at this point and run into bootloops, instead of Wiping Cache, System & Data manually, just simply hit "Factory Reset" instead. and continue with OP's flashing instructions and you should be good.
Thanks so much, Hokie! Packed with features, really appreciate all of the detailed instructions! Thank you!
Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
Click to expand...
Click to collapse
Yes that is normal
Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
Click to expand...
Click to collapse
Yep normal.
Reboot recovery. Flash gapps/vendor reboot.
Giving this a whirl. Thanks OP!!!
Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
*Update*
For those of you that get stuck at this point and run into bootloops, instead of Wiping Cache, System & Data manually, just simply hit "Factory Reset" instead. and continue with OP's flashing instructions and you should be good.
Click to expand...
Click to collapse
Aye, that is normal. It just means you don't have vendor installed, which you can't do until rebooting back to TWRP (so it switches slots).
Factory reset does not wipe system partition. If you are coming from a different ROM, when you switch slots, you are leaving a different ROM on your inactive slot. Not a huge deal, but I don't recommend it.
Edit - The best way to avoid stressing about that is to allow the reboot, but interrupt boot (pwr + vol down), and go right to recovery from the bootloader.
BHermes211 said:
Are there any custom kernels that will work with this ROM right now?
Click to expand...
Click to collapse
Maybe? I haven't tried installing one yet. ElementalX has always worked well in the past, indeed I always built nougat crDroid with it. Just haven't tried it on Oreo.
If you want to try installing it, worst it will do is bootloop. Just dirty flash (wipe only cache/system, leave data, repeat normal install) back to the included kernel.
Related
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
...
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 15.0
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
(link the best one for your device, there are several variants out there right now, nano/micro GApps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behaviour on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
NOTE:
WE ARE ENCRYPTED (FILE BASED FORCED ENCRYPTION). So if you are unencrypted format data partition or use any no_verity solution you want. We don't support it.
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended). Bluspark twrp recovery recommended.
3. Wipe the System, Cache, and Data (you might need to format the data partition in some cases!).
4. Flash firmware. Actual one is 10.0.0-H1. Download.
5. Flash the ROM Zipfile.
6. Reboot to TWRP recovery.
7. Flash the GApps (optional, needed for e.g. Google Playstore to work) and Magisk (optional too if you want a root solution).
8. Reboot and set up your device.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.3 don't usually need to be flashed on every dirty flash.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/AICP/kernel_oneplus_msm8998
Device tree source:
https://github.com/AICP/device_oneplus_msm8998-common
https://github.com/AICP/device_oneplus_dumpling
Vendor source:
https://github.com/AICP/proprietary_vendor_oneplus
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
AICP Team
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
AICP 15.0, ROM for the OnePlus 5T
Contributors
GreekDragon, eyosen, csolanol, wartomato
Source Code: http://github.com/AICP
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Firmware >= 10.0.0-H1
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 15.0
Stable Release Date: 2020-04-06
Created 2018-01-19
Last Updated 2020-06-22
Reserved
Reserved
wow, Aicp is out and from @GreekDragon.. Welcome it is a long time from IceCold kernel
OMG! AICP is here! OP5T dev is starting moving for real...
Do we need to be decrypted or can we flash on encrypted? You're going to get this question a million times so I think you should mention it in the op.
Thanks!
Will give it a try - thanks.
---------- Post added at 10:40 PM ---------- Previous post was at 10:39 PM ----------
hassan_1000 said:
Do we need to be decrypted or can we flash on encrypted? You're going to get this question a million times so I think you should mention it in the op.
Thanks!
Click to expand...
Click to collapse
I think you need to be decrypted - see step 3A.
Ok, if you are from OB2 OOS , you need fully format data and all otherwise you will face bootlop ( I tried ) haha..
so fully format, clean flash rom, gapps, reboot. If u want root flash magisk.
rom is really great, so many features ..but I feel it is kinda laggy xD
P.S
after flashing ob1 , rom is smoother all good now
Yup, because we are on ob1 firmware. Ob2 is not merged and makes it laggy, gives fingerprint issues, etc...
:good: more info
WELCOME AICP!!!! One of my favorite ROMS
Will definitely give it a try. But my first concern is about the camera.. how is it performing?
I'm encrypted. How can I make myself decrypted? I'm new with this sorry. But I've been flashing roms for a while now. It's just strange that all roms I have tried requires people to be encrypted.. and this one requires decrypted. Thank you for the hard work dev and hope to hear frod you..
melmarPH said:
I'm encrypted. How can I make myself decrypted? I'm new with this sorry. But I've been flashing roms for a while now. It's just strange that all roms I have tried requires people to be encrypted.. and this one requires decrypted. Thank you for the hard work dev and hope to hear frod you..
Click to expand...
Click to collapse
To decrypt you need to format data (not wipe) in twrp.
It will wipe the whole sotrage on your phone, so take a backup first (pictures, downloads etc).
U35632317 said:
To decrypt you need to format data (not wipe) in twrp.
It will wipe the whole sotrage on your phone, so take a backup first (pictures, downloads etc).
Click to expand...
Click to collapse
I appreciate your reply mate.. if decrypting means wiping my internal storage.. that means I'm gonna delete everything right? Including the rom file in my internal storage?
melmarPH said:
I appreciate your reply mate.. if decrypting means wiping my internal storage.. that means I'm gonna delete everything right? Including the rom file in my internal storage?
Click to expand...
Click to collapse
Yes, that's right. So you need a pc or otg to take an external backup. But you need to do this only once.
U35632317 said:
Yes, that's right. So you need a pc or otg to take an external backup. But you need to do this only once.
Click to expand...
Click to collapse
Got you! Thank you so much for the information.. lastly, I am currently using a custom rom based on OnePlus 5T Oreo Beta 2. Do I need to do anything else before flashing apart from formating data for decryption?
marko94 said:
Ok, if you are from OB2 OOS , you need fully format data and all otherwise you will face bootlop ( I tried ) haha..
so fully format, clean flash rom, gapps, reboot. If u want root flash magisk.
rom is really great, so many features ..but I feel it is kinda laggy xD
P.S
after flashing ob1 , rom is smoother all good now
Click to expand...
Click to collapse
Mate, how exactly did you flash ob1 in this portion? Coz I was able to get this ROM to boot up but as what you've mention with this comment, there is a terrible lag and my settings keeps crashing when trying to add a finger print . please help me out..
Do you need no verity zip to stay decrypted?
Sent from my OnePlus5T using XDA Labs
tcat007 said:
Do you need no verity zip to stay decrypted?
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Some rom don't force encryption, but i flash no versity after flashing every rom(for safe side)
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LAOS) we are now LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.1
Download link: https://www.androidfilehost.com/?w=files&flid=274850
Official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: http://dwnld.aicp-rom.com/
Google Apps:
select ARM + Android Oreo 8.1 here: https://opengapps.org/
- SELinux is permissive
- The current builds are "incompatible" with some apps in the Play Store > You can download the last build without this issue here
You tell
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot", then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash, and then reboot.
Using the ROM:
Q. How do I enable software buttons?
A. Go to Aicp Extras/Navigation bar, and enable it.
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I keep losing root with Magisk, how do I fix it?
A. Check this out. If that doesn't work for you, ask for help in this thread, read or ask in the Magisk thread on XDA or just re-flash Magisk!
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Flash the root solution of your choice (optional).
7. Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the device, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
KERNEL:
The kernel in this ROM follows LAOS source with custom additions.
PREREQUISITE FOR OTA:
To be able to flash using the built-in OTA app, TWRP recovery is needed.
You can still use the LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. The Zipfile gets saved in the "aicp_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Sources:
Kernel source
Device tree
Vendor tree
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
@deadman96385
@Galaxy-MSM8916 team
@elginsk8r
ROM OS Version: 8.1.0 Oreo
Kernel: Linux 3.10.x
Version Information:
Status: NIGHTLY
Release Date: 25-6-2018
You want to see a "normal" night at the "DEV office", click here!!
Can it be installed on t555?
Mihai14 said:
Can it be installed on t555?
Click to expand...
Click to collapse
Since I don't own a SM-T555, I can't tell you whether it boots or not. This build is designed for the Wifi-only variant, so your tablet definitely won't support LTE/telephony. Maybe I'll publish a SM-T555 build in the future.
virsys said:
Since I don't own a SM-T555, I can't tell you whether it boots or not. This build is designed for the Wifi-only variant, so your tablet definitely won't support LTE/telephony. Maybe I'll publish a SM-T555 build in the future.
Click to expand...
Click to collapse
I don't really care about ril but it just doesn't boot. Like the other roms and i just can't find the problem. Lineage os 14.1 should boot on t555 too but without ril and it ij stuck in the boot logo refusing to boot into /system.
Mihai14 said:
it just doesn't boot.
Click to expand...
Click to collapse
Have you fully wiped the cache & data partition?
What does "it doesn't boot" mean:
Does it pass the samsung splash screen & shows a stucking boot animation?
Are there tombstones in the data/tombstones folder present?
virsys said:
Have you fully wiped the cache & data partition?
What does "it doesn't boot" mean:
Does it pass the samsung splash screen & shows a stucking boot animation?
Are there tombstones in the data/tombstones folder present?
Click to expand...
Click to collapse
Yes clean flashed the rom. No it doesn't pass the samsung logo it's not a bootloop. There is no tombstones folder in /data
Mihai14 said:
Yes clean flashed the rom. No it doesn't pass the samsung logo it's not a bootloop. There is no tombstones folder in /data
Click to expand...
Click to collapse
I guess you know what you're doing and have enabled OEM unlocking. When TWRP is able to boot, the rom is probably not compatible with the SM-T555. I can message you when I've compiled a SM-T555 testversion. Only if you would like to help me making the SM-T555 compatible.
virsys said:
I guess you know what you're doing and have enabled OEM unlocking. When TWRP is able to boot, the rom is probably not compatible with the SM-T555. I can message you when I've compiled a SM-T555 testversion. Only if you would like to help me making the SM-T555 compatible.
Click to expand...
Click to collapse
Of course i would want to help. I can PM you my telegram.
Hi all,
I tested the ROM on SM-T550 and it boots quiet well.
Initial google (nano opengapps) setup was broken for me, but the setup
via "Google app" and my phone worked.
Another thing is that when installing a browser it
crashes right after starting it.
Opera says that I have no space free
Chrome says something like an unexpected error.
Buildin browser just appears short and closes immediately.
The game little wars and Netflix app shows the same behaviour.
So right now I can't use the ROM but I am very Happy that this device is not abandoned!
Thank you for your work and if I can help testing, just drop me a line.
I have SM-T550
Its great ROM, but.. Problem, has error browser, for example: I can't open Google chrome, opera, ... Pls fix? You are the best! ??
Ok so apparently it boots but the screen is always black. I just found a screenshot i've taken accidentally after i flashed the rom and it seems to boot.
ramaxcalmax said:
Another thing is that when installing a browser it
crashes right after starting it.
Click to expand...
Click to collapse
Thanks for your report. The latest build should work.
My Model: SM-T550
I have one problem... The ROM is great working with all browser (Google Chrome, Opera, ...) Very Good.
But... Please you read.
- It's very laggy the security (for example: PIN, password and Sequence). I'm ready PIN, it's fine.
When my tablet is lock PIN (Off). I'm watching TV or other. My tablet lets off 1 hour. After, I go my tablet open "On" it's very laggy and PIN too, all..
I hope you understanding? I'm a deaf, sorry!
I'm fighting against selinux right now. I'll update the build soon, thanks for your hint.
I think I found why the screen is not working on t555: might be because of a problem in the kernel. More precise the dt. You can use the kernel from the stock firmware as base to fix this. Also for the ril take look at samsung galaxy j5 2015/2016 sources. They have the same chip as t555/t550. Especially the 2016 version as it have almost the same base firmware (7.1.1).
Mihai14 said:
You can use the kernel from the stock firmware as base to fix this.
Click to expand...
Click to collapse
Maybe you should build it on your own. The entire building process is basically very simple.
It's actually quite easy to port it from the gt510wifi device tree. The kernel sources are available and the only thing to worry about is the RIL.
virsys said:
Maybe you should build it on your own. The entire building process is basically very simple.
It's actually quite easy to port it from the gt510wifi device tree. The kernel sources are available and the only thing to worry about is the RIL.
Click to expand...
Click to collapse
I would but my laptop is quite s**t. I have tried to build roms before but ot was a fail.
Thanks for keeping this device relevant. Working great!
Could this be ported to the 8" variant SM- T350 ? We have no Oreo development
vin_001 said:
We have no Oreo development
Click to expand...
Click to collapse
That's not true.
There's oreo development.
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
DOWNLOAD GAPPS
First time installing crDroid to your Moto G5, or coming from another ROM: <--THESE MAY NEED UPDATING FOR YOUR PARTICULAR DEVICE; BE THOROUGH IN INSTRUCTIONS-->
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
You tell me
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- ENTER-SPECIFIC-THANKS-HERE-IF-YOU-HAVE-THEM
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
crDroid G+ community
Source Code: https://github.com/crdroidandroid
Device tree: https://github.com/Fedray/android_device_motorola_cedric/tree/lineage-16.0
Kernel: https://github.com/Sohamlad7/android_kernel_motorola_msm8937/tree/lineage-16.0
Vendor: https://github.com/Sohamlad7/android_vendor_motorola_cedric/tree/lineage-16.0
ROM OS Version: 9.0.0 Pie
Based On: LineageOS 16
Version Information
Status: Stable
Current Stable Version: 5.0
Stable Release Date: 2019-01-21
Last Edit Date: 2019-01-21
Changelog:
20/1/2019
-Initial build
biometric sensor working?
Screenshots?
Welcome back @Fedray ROM works flawlessly so far!
Joseph3546 said:
biometric sensor working?
Click to expand...
Click to collapse
Yes, of course, it works on every rom.
lucki1000 said:
Screenshots?
Click to expand...
Click to collapse
I will upload when I have time.
mrfrantastic said:
Welcome back @Fedray ROM works flawlessly so far!
Click to expand...
Click to collapse
Thanks Glad to hear that!
Fedray said:
Yes, of course, it works on every rom.
I will upload when I have time.
Thanks Glad to hear that!
Click to expand...
Click to collapse
Whats the chance to go offical with this ROM?
fedray back at it again with another stable rom, good to see you post something once in a while
Thanks for this ROM, I already relied on you worh on the Moto G, Fedray!
Any advice what to do if Quickstep launcher fc at startup? Wiping cache/dalvik is problematic because trwp can not decrypt the data partition. Btw: Does anybody usw a twrp version abel to decrypt it?
Did someone successfully managed to install Magisk? After I flash it, it always does not appear in Magisk Manager. Manager claims it is not installed and offer to do it, but this also does not work.
sambahb said:
Did someone successfully managed to install Magisk? After I flash it, it always does not appear in Magisk Manager. Manager claims it is not installed and offer to do it, but this also does not work.
Click to expand...
Click to collapse
Uninstall magisk install magisk start if app not in the list extract the zip and install the app manually, and if the app say additional setup needed install it again without uninstall.
lucki1000 said:
Uninstall magisk install magisk start if app not in the list extract the zip and install the app manually, and if the app say additional setup needed install it again without uninstall.
Click to expand...
Click to collapse
Is there a place, where this manually is described better? I am not sure, what you exactly mean.
sambahb said:
Is there a place, where this manually is described better? I am not sure, what you exactly mean.
Click to expand...
Click to collapse
Okay, you should uninstall magisk over TWRP then you install magisk via TWRP, then make a restart and boot into crdroid, if magisk app not avaible, then go to the magisk.zip and install manually the magisk.apk (who is in the zip) and if you get a report in the magisk app like this additional setup needed or similar you reboot into TWRP and install magisk again and reboot into crdroid that should work.
lucki1000 said:
Okay, you should uninstall magisk over TWRP then you install magisk via TWRP, then make a restart and boot into crdroid, if magisk app not avaible, then go to the magisk.zip and install manually the magisk.apk (who is in the zip) and if you get a report in the magisk app like this additional setup needed or similar you reboot into TWRP and install magisk again and reboot into crdroid that should work.
Click to expand...
Click to collapse
This is exactly what I did about 5 times. First I always had to install Magisk Manager manually because it was not available. After install Manager told me that Magisk is not installed and there is the possibility from within the app. Download worked, but installwise nothing happend. It looks like it does not event try
sambahb said:
This is exactly what I did about 5 times. First I always had to install Magisk Manager manually because it was not available. After install Manager told me that Magisk is not installed and there is the possibility from within the app. Download worked, but installwise nothing happend. It looks like it does not event try
Click to expand...
Click to collapse
You install it start system and if you get magisk is not installed then go again to TWRP and install magisk, (without uninstall or any wipe or something else only install magisk again) if this also not work ask in the magisk thread.
when I will get official built. This ROM is loving. please built official version as soon as possible. Thanks to developer.
Anyone else constantly experiencing system UI crashes?
Will there be an update to 5.1?
Thanks to the developer, great ROM!
Hi.
I have upgraded from crdroid 8 to this rom and losted biometric sensor.
It does not appear at Configurations, the Moto Actions configurations don't work for finger gestures.
It was working at previous crdroid version.
I did a clean install.
Any suggestion on how to make it work again?
Lrd-Nero said:
Anyone else constantly experiencing system UI crashes?
Will there be an update to 5.1?
Thanks to the developer, great ROM!
Click to expand...
Click to collapse
Same problem.
diogopetermann said:
Hi.
I have upgraded from crdroid 8 to this rom and losted biometric sensor.
It does not appear at Configurations, the Moto Actions configurations don't work for finger gestures.
It was working at previous crdroid version.
I did a clean install.
Any suggestion on how to make it work again?
Click to expand...
Click to collapse
Flash this using the TWRP to make your fingerprint work again: https://drive.google.com/file/d/1e_8alb2MFX7uXqjYZ7OruCCImbYIge1r/view
{
"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 Google Pixel XL [marlin]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
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 11.0
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 11.0.0_r46
Security patch level: December 2021
Build author/Device Maintainer: PixelBoot
Device Source code:
https://github.com/PixelExperience-Devices/device_google_marlin
https://github.com/PixelExperience-Devices/kernel_google_marlin
https://gitlab.pixelexperience.org/android/vendor-blobs/vendor_google_marlin
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Reserved
Niceeeeee!!! I have been waiting too long for this <3
Awesome! Thanks alot for this! Couple of questions before flashing. Does it include stock google camera? Does it retain unlimited photos storage and also is it possible to flash over stock without losing all data? I know the last isn't recommended, but would be nice.
BoboBrazil said:
Awesome! Thanks alot for this! Couple of questions before flashing. Does it include stock google camera? Does it retain unlimited photos storage and also is it possible to flash over stock without losing all data? I know the last isn't recommended, but would be nice.
Click to expand...
Click to collapse
1. The camera included is one provided by cstark. It is a modded version of Google Camera which includes features from later Pixels, but should still hold the original features.
2. Yes, you can still upload unlimited photos in original quality.
3. Unfortunately, it is not possible to directly flash PixelExperience over stock. In fact, 11 requires a full device repartition. It's easy as flashing a .zip file before the ROM to do so.
If you have any more queries, make sure to let me know!
PixelExperience - OFFICIAL | Android 11
Updated: 14/03/'21
Links:
Sailfish [1.06GB]
Marlin [1.06GB]
️Telegram Group
Disclaimer:
This build requires you to re-partition your device in order to flash.
Kindly read the Pre-install instructions before flashing.
Changelog:
Initial stable release for Google Pixel/XL
PixelExperience (Plus Edition) - OFFICIAL | Android 11
Updated: 14/03/'21
Links:
Sailfish [1.06GB]
Marlin [1.06GB]
️Telegram Group
Disclaimer:
This build requires you to re-partition your device in order to flash.
Kindly read the Pre-install instructions before flashing.
Changelog:
Initial stable release for Google Pixel/XL
Flashed and working fine. Thanks a lot for your hard work, still going through the setup but so far so good. Will report if I come across anything funny.
kartikb said:
Flashed and working fine. Thanks a lot for your hard work, still going through the setup but so far so good. Will report if I come across anything funny.
Click to expand...
Click to collapse
Hey dude! (or dudette), would you please walk me throught the installation process? I'm a noob on flashing custom roms, and i'm facing some difficulties flashing this rom. I downloaded the repartition zip form the link, and I'm flashing it throught twrp recovery and then the rom zip file but it gets stuck on a bootloop. What am I missing? (Please forgive any misspellings, I'm also a noob at english)
Flashing both the regular and plus versions doesn't seem to work for me. They both get to 35%, then I get:
28 (ErrorCode::kDownloadOperationExecutionError)
Error in /sideload/package.zip (status 1)
Great great work! Will surely be trying this at the first available free time!
kartikb said:
Flashed and working fine. Thanks a lot for your hard work, still going through the setup but so far so good. Will report if I come across anything funny.
Click to expand...
Click to collapse
Hi. Are you able to download Google Camera from playstore and does it work fine?
Is selinux enforced? Tks
Going through Pixelexperience site, came across two versions for Pixel XL- Stable android 11 and Stable Android 11 (plus edition).
What's the difference between the two? Apologies if this is common knowledge, but this is the first time for me using Pixelexperience.
pantsaregood said:
Flashing both the regular and plus versions doesn't seem to work for me. They both get to 35%, then I get:
28 (ErrorCode::kDownloadOperationExecutionError)
Error in /sideload/package.zip (status 1)
Click to expand...
Click to collapse
I'm facing with this issue too. Have done repartitioning successfully. :'(
lmvuong1997 said:
I'm facing with this issue too. Have done repartitioning successfully. :'(
Click to expand...
Click to collapse
I have solved the issue, this is what i have done:
- Boot into twrp from fastboot, using the latest twrp 3.5.0
- Advanced Wipe (system, dalvik, data), change active slot and then repeat (just to be sure)
- adb sideload the repartitioning zip
- Format data (where you type 'yes') then reboot into twrp
- (From Kartik Billimoria on Telegram)Push rom zip file to /sdcard via adb push command then flashed the rom
- Change to inactive slot (the slot you flashed the rom), reboot to fastboot to make sure the active slot has changed (for me it has not), if not change it by 'fastboot set_active a' (or b). Reboot.
josegarfer01 said:
Hey dude! (or dudette), would you please walk me throught the installation process? I'm a noob on flashing custom roms, and i'm facing some difficulties flashing this rom. I downloaded the repartition zip form the link, and I'm flashing it throught twrp recovery and then the rom zip file but it gets stuck on a bootloop. What am I missing? (Please forgive any misspellings, I'm also a noob at english)
Click to expand...
Click to collapse
It will not work via TWRP recovery.
1. Kindly go on the downloads page and install the PE recovery.
Code:
fastboot flash boot recovery.img
(It may bootloop once or twice, but then it will show up in PE recovery)
2. Go into Apply update via ADB.
Code:
adb sideload repartition-ogpixel-**gb.zip
3. Factory Reset/Wipe Data.
4. Apply update via ADB and sideload the ROM.
Code:
adb sideload PixelExperience-**.zip
5. Reboot and wait patiently.
Hope this helps.
pantsaregood said:
Flashing both the regular and plus versions doesn't seem to work for me. They both get to 35%, then I get:
28 (ErrorCode::kDownloadOperationExecutionError)
Error in /sideload/package.zip (status 1)
Click to expand...
Click to collapse
lmvuong1997 said:
I'm facing with this issue too. Have done repartitioning successfully. :'(
Click to expand...
Click to collapse
If you are still in difficulty, follow the mentioned post below:
PixelBoot said:
It will not work via TWRP recovery.
1. Kindly go on the downloads page and install the PE recovery.
Code:
fastboot flash boot recovery.img
(It may bootloop once or twice, but then it will show up in PE recovery)
2. Go into Apply update via ADB.
Code:
adb sideload repartition-ogpixel-**gb.zip
3. Factory Reset/Wipe Data.
4. Apply update via ADB and sideload the ROM.
Code:
adb sideload PixelExperience-**.zip
5. Reboot and wait patiently.
Hope this helps.
Click to expand...
Click to collapse
gverma1 said:
Going through Pixelexperience site, came across two versions for Pixel XL- Stable android 11 and Stable Android 11 (plus edition).
What's the difference between the two? Apologies if this is common knowledge, but this is the first time for me using Pixelexperience.
Click to expand...
Click to collapse
PixelExperience Plus Edition provides extra tweaks that you can apply.
One that comes to mind is further customization to the notifcation bar to include network stats.
If you're up for extra customization from ROMs like LineageOS, consider flashing Plus instead.
gverma1 said:
Hi. Are you able to download Google Camera from playstore and does it work fine?
Is selinux enforced? Tks
Click to expand...
Click to collapse
By default, the ROM includes Google Camera PX by cstark27, which is more up to date than the stock (marlin/sailfish) Google Camera app. It includes newer features such as Portrait mode and Timelapse.
However, from the Google Play Store, you are still free to install the stock one.
As for SELinux, yes. It is enforced.
For stable releases from PixelExperience, it is required that builds are on Enforcing.
lmvuong1997 said:
- Change to inactive slot (the slot you flashed the rom), reboot to fastboot to make sure the active slot has changed (for me it has not), if not change it by 'fastboot set_active a' (or b). Reboot.
Click to expand...
Click to collapse
No need for this last part. If on TWRP, after flashing the ROM, you just need to reboot back to recovery and it will automatically set to the inactive slot.
{
"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 linkAt 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.