{
"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"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices,
* 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's working :
Everything that worked in last OFFICIAL build.
There are NO MODIFICATIONS at all. If something didn't work in the last official LineageOS release, it wont work in this build.
Instructions :
Download build and copy it to Internal Memory
Reboot to TWRP recovery
Create TWRP Backup (Recommended)
Flash the latest build (Clean Flash if coming from any other build)
Flash Magisk/LineageSU zip (Optional)
Flash GApps/MicroG (Optional)
Reboot
Downloads :
deb
Build: lineage-14.1-20230514-UNOFFICIAL-deb.zip
MD5: 534dff964ca9c44a8ab00e6a6d3883f9
flo
Build: lineage-14.1-20230514-UNOFFICIAL-flo.zip
MD5: 66a094b14a1f1531af1d195bf787a03b
TWRP
deb: twrp-3.4.0-0-deb.img
flo: twrp-3.4.0-0-flo.img
followmsi builds: TWRP-followmsi
Root Method:
Magisk: here
LineageOS su: here
Addon (GApps/MicroG):
GApps: BiTGApps (arm 7.1.2)
MicroG (Built via FriendlyNeighborhoodShane repo): MinMicroG.zip
Source Code: https://github.com/LineageOS
Proprietary Files: TheMuppets
Kernel Source: Here
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4.0
Security Patch: May 2023
Created 2021-01-12
Last Updated 2023-05-14
Older Builds
Downloads:
AFH Google Nexus 7 (2013) Root Folder (Builds older than July 2022)
SourceForge - deb
SourceForge - flo
Thank you.
Hi,
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Any idea what it could be?
Thank you,
aurocha said:
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Click to expand...
Click to collapse
I am not sure what you mean. This ROM runs on reparttioned device only. Boot into recovery, select wipe, select system partition and tap on 'resize or repair' button (you don't need to repair or resize, it's just to check partition size). There will be a report on partition size. This size should be above 1.1 Gb or the ROM won't boot. Exit this page without doing any modifications. If the partition size is 800 Mb or so you have to repartition the device.
aurocha said:
Hi,
Somehow I'm not being to properly install and boot this build.
I repartitioned, then restored the stock partitions via the same script; installed the above TWRP.
I can only see the LOS logo for a very long time.
Any idea what it could be?
Thank you,
Click to expand...
Click to collapse
You do not need to repartition. It works correctly on stock partition scheme (system with 832M size). Also, make sure that in TWRP, all your partitions are in ext4 format.
Try doing this:
- Goto Wipe -> Advanced wipe -> select all partitions and then swipe. Once done go back to main menu
- Goto Wipe -> Format Data -> type "yes" and then press enter. Once done go back to main menu
- Goto Reboot and then select Recovery
- After reboot, tick the "allow system modification" and then swipe to enter TWRP.
- Connect to Laptop/PC and copy lineageos.zip
- Flash only lineageos.zip (for testing)
- Reboot
If you get the welcome screen, then there should be an issue with any other zips that you are flashing along with the ROM.
Os_A said:
I am not sure what you mean. This ROM runs on reparttioned device only. Boot into recovery, select wipe, select system partition and tap on 'resize or repair' button (you don't need to repair or resize, it's just to check partition size). There will be a report on partition size. This size should be above 1.1 Gb or the ROM won't boot. Exit this page without doing any modifications. If the partition size is 800 Mb or so you have to repartition the device.
Click to expand...
Click to collapse
cm-14.1 works with stock partition scheme. You need repartition only for Android 9 ROMs and above (If I am not wrong as I don't know about oreo)
I have successfully installed on my Nexus 7 (2013) LTE (deb) with stock partition scheme.
M4Master96 said:
You do not need to repartition. It works correctly on stock partition scheme (system with 832M size). Also, make sure that in TWRP, all your partitions are in ext4 format.
Try doing this:
- Goto Wipe -> Advanced wipe -> select all partitions and then swipe. Once done go back to main menu
- Goto Wipe -> Format Data -> type "yes" and then press enter. Once done go back to main menu
- Goto Reboot and then select Recovery
- After reboot, tick the "allow system modification" and then swipe to enter TWRP.
- Connect to Laptop/PC and copy lineageos.zip
- Flash only lineageos.zip (for testing)
- Reboot
If you get the welcome screen, then there should be an issue with any other zips that you are flashing along with the ROM.
cm-14.1 works with stock partition scheme. You need repartition only for Android 9 ROMs and above (If I am not wrong as I don't know about oreo)
I have successfully installed on my Nexus 7 (2013) LTE (deb) with stock partition scheme.
Click to expand...
Click to collapse
Hi,
Just wanted to report that, after restoring my tablet with official image from Google and wiping it and flashing lineageos-14.1, it all went ok.
I then proceeded to flash BitGapps core and Magisk and it's running like a charm.
I don't know why it wasn't running, but I decided to revert back to the original partition scheme, restore stock images, and start all over again.
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Thank you for keeping our device alive!
Regards,
aurocha said:
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Click to expand...
Click to collapse
I felt the same which is why I went back to Nougat.
I use microg as only use it for watching movies/tv shows and for reading. AuroraOSS works like a charm for installing apps.
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
M4Master96 said:
I felt the same which is why I went back to Nougat.
I use microg as only use it for watching movies/tv shows and for reading. AuroraOSS works like a charm for installing apps.
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
Click to expand...
Click to collapse
Yep, that's the kernel I'm running. Mainly because of DT2W. Loads of options when flashing because of the Aroma installer and easily manageable with exkm, which I bought some years ago.
M4Master96 said:
By the way, If you want things like DT2W (double tap to wake), overclocking CPU/GPU, etc... you can also flash ElementalX-N7-6.17 kernel
Click to expand...
Click to collapse
When you flash this kernel, is there a way to re-apply/restore existing settings? I have had to go through the Aroma installer and manually enter the same settings after every update, but I can see an elementalxbackup file in my Internal Storage, which would be much easier to use if possible!
plusminus_ said:
When you flash this kernel, is there a way to re-apply/restore existing settings? I have had to go through the Aroma installer and manually enter the same settings after every update, but I can see an elementalxbackup file in my Internal Storage, which would be much easier to use if possible!
Click to expand...
Click to collapse
I think you need to use EX Kernel Manager app from Play Store which is basically app developed by the same person who built ElementalX kernel for managing the kernel. But you will need to Root your device for the app to work (if I am not wrong)
this looks great - thank you - does it work with any of the Custom Kernels?
February 2021 Security Patches
deb
Build: lineage-14.1-20210208-UNOFFICIAL-deb.zip
MD5: 7ed9473d325d20b863d1516d902602d7
flo
Build: lineage-14.1-20210208-UNOFFICIAL-flo.zip
MD5: 9a6617aa7111b4c91daf310e7bf09183
Added links in first post
M4Master96 said:
I think you need to use EX Kernel Manager app from Play Store which is basically app developed by the same person who built ElementalX kernel for managing the kernel. But you will need to Root your device for the app to work (if I am not wrong)
Click to expand...
Click to collapse
Ah I suspected this, hmm
thanks
Thanks all you guys, was looking for a decent rom for this tablet, can't live without doubletap2wake and newer roms are just too heavy for this gadget, was looking for a decent rom for it, and I have finally find it
March 2021 Security Patches
deb
Build: lineage-14.1-20210309-UNOFFICIAL-deb.zip
MD5: 6d23b5115b073a6d9a85981cb6abac11
flo
Build: lineage-14.1-20210309-UNOFFICIAL-flo.zip
MD5: 39f1a8945af9870369ffdd1deefb5e4c
Updated links in first post
First also a big THX from me for supporting our good old nexus7. You mentioned in #8 that you use microg only. How can i achive that? Is there a ready made microg.zip i can just flash with twrp after rom?
sundog1 said:
First also a big THX from me for supporting our good old nexus7. You mentioned in #8 that you use microg only. How can i achive that? Is there a ready made microg.zip i can just flash with twrp after rom?
Click to expand...
Click to collapse
I create flashable microg zip via https://github.com/WeAreFairphone/flashable-zip_microG and then flash it along with ROM, magisk and kernel. Afterwards, I use SmaliPatcher Module to patch and enable SignatureSpoofing so that MicroG works.
I had also raised Merge Request in lineageos4microg so that We can build ROM with microg without syncing repository but my MR is still open and so, Not able to build that.
April 2021 Security Patches
deb
Build: lineage-14.1-20210409-UNOFFICIAL-deb.zip
MD5: 627ce7454888bc71aec2fea10e6023ce
flo
Build: lineage-14.1-20210409-UNOFFICIAL-flo.zip
MD5: 54ac5466ae8df749a6650ee1c7b28e82
Updated links in first post
aurocha said:
Hi,
Just wanted to report that, after restoring my tablet with official image from Google and wiping it and flashing lineageos-14.1, it all went ok.
I then proceeded to flash BitGapps core and Magisk and it's running like a charm.
I don't know why it wasn't running, but I decided to revert back to the original partition scheme, restore stock images, and start all over again.
This version is stable, fluid and fast, and probably it's the best version for our device, since Android Q seems to be a bit more heavy on resources (tried the official flox build).
Thank you for keeping our device alive!
Regards,
Click to expand...
Click to collapse
Hi,
May i know which 'official image' you restored and which version of twrp was used?
I flashed LOS 18.1 before and it work but seems lag. Then I tried to flash this ROM but faced the same problem, endless looping is the screen of upwards arc w/ circle (LOS logo?) running from right to left again and again.
Thank you!
Update: Well, i just follow the link provided by @JT1510365 in https://forum.xda-developers.com/t/...oted-unmodified-6-0-mra58v-flashable.3694735/ and download the stock rom, restore to 6.0, it boot normal. Then flash twrp & this rom and it work now.
Thank you for your share of the reinstallation of 'official image'.
Related
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.
{
"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 ASB for Galaxy S2 [i9100]
What is this?
Pixel Experience ASB is an AOSP ROM based on the original project, 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 features for the proper functioning of the device and latest ASB patches for Android Oreo
Based on Android 8.1
NOTE:
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.
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Lights
Sound / vibration
Known issues
VSync
DON'T FLASH GAPPS, ALREADY INCLUDED
Download:
AFH: New builds
Old builds without emulated storage
Android OS version: 8.1.0_r65
Security patch level: July 2019 (Lineage ASB)
Build author: linusdan
Source code: https://github.com/PixelExperience
Kernel of device: https://gitlab.com/linusdan/kernel_samsung_smdk4412/tree/oreo
ROM Developer: linusdan
Credits - @rINanDO
Before installing ROM, you need to:
- 1.5 GB of system partition
- Emulated storage (from the April build).
Not sure how? See in this post
If you like my work, do not forget to click the button thanks. It's free!!!
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.0.x
Based On: AOSP
TWRP Required: TWRP 3.3.1-1 EMU
Version Information
Status: Stable. No longer maintained
Created 2018-09-21
Last Updated 2019-07-15
Reserved
NO ETA REQUESTS!
DOWNLOAD LINKS IN OP
Frequent questions
I do not use GAPPS! How can I remove?
R: Unfortunately not. Sorry.
What are the bugs?
R: See Known issues in OP.
How do I get root?
R: Download SuperSU Flashable and install via TWRP. After this, update the application by the Google Play
I found a bug!
Make a logcat and put it in pastebin/hastebin. I'll look when I can
You will need a computer, adb installed, usb debugging enabled on the smartphone and a usb cable.
Here's how to do it here.
1. Open Command Prompt (Windows) or Terminal (Linux/macOS).
2. Type:
Code:
adb logcat -d > logcat-dd-mm-yyyy.txt
This will save the log to logcat-dd-mm-yyyy.txt.
No nonsense questions, please!
Avoid meaningless discussions and help you and the user have useful information on the thread :good:
Dan, when I connect the phone to the PC, I can not access the files because there is no information to authorize the procedure in the notification! Please take a look when you can.
Calm down, Padawan! This is not a bug but google stuff. They have placed the authorization option on development tools. Everyone is trying to understand why this
Do this when you want to have access to them:
Go to System -> developer option -> USB and activate MTP manually.
What will be the frequency of compilations?
Monthly or every two months . I plan to spend $12 per month for the projects.
Praying for the low dollar quote on the Google Cloud Engine :laugh::fingers-crossed::good:
Upgrade from Samsung stock ROM to latest build using ODIN 3.13.1
Also recommended for devices with Android 4.4 - 5+
Back up your files and make a full wipe before the procedure.
Files Required:
Stock ROM
Pit file by-the.gangster
Samsung USB Driver
Odin 3.13.1
Latest Pixel Experience
Pit file with Emulated Storage by rINanDO
TWRP Emulated Storage 3.3.1-1 by rINanDO
0) Install Stock ROM
0.1 After downloading the tools, install the Samsung USB Driver and unzip the file of the rom.
The original rom file is tar.md5
0.2a Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
0.2b Start Odin 3.13.1 in your PC.
0.2c Connect your phone via USB to your PC.
0.2d Press volume up on your phone, Odin should detect your phone.
0.3 In the pit tab on the left side, select the file "i9100_1.5gb-system_6gb-data_512mb-preload_by-the.gangster.pit"
0.4 In AP button, select the tar.md5 file. The Odin app will frozen for a few minutes but do not worry.
After this, select start button. Wait terminate, do not pull the cable
0.5 The device will restart. A message will appear stating that it is encrypted. Turn off your device and enter recovery mode (Volume up + Power/Standby + Home and hold for 10 seconds). Clear Cache and Dalvik / Cache. Restart.
0.6 A warning will appear in the status bar saying that the partition is corrupted. Format the partition. Verify that the partition succeeded in the device settings.
0.7 Charge the phone and follow the next instructions.
1) Prepare your phone
1.1 Copy the ROM to the Micro-SDCard before flashing.
1.2 Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
1.3 Start Odin 3.13.1 in your PC.
1.4 Connect your phone via USB to your PC.
1.5 Press volume up on your phone, Odin should detect your phone.
2) Odin
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
AP : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
Press Start.
3) After successful flash
Reboot phone into Recovery
Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1. Swipe to allow modifications.
4) TWRP
In TWRP 3.3.1-1 you need to format partitions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
Dalvik / ART Cache
Cache
System
Non-emulated Storage
-> Swipe to Wipe
5) Install Pixel Experience and boot system.
P.S: To prevent "Uncryption unsuccessful" error of GAPPS at first start:
- Reboot to recovery and Wipe -> Format Data -> Type [yes] again
Changelog
15072019 [EOL] - FINAL BUILD
* Android 8.1.0_r65
* Fix audio stereo recording
* GApps updated to the latest
* Add dummy keydisabler to allow navbar disabling
* Chromium webview: Updated to 75.0.3770.101 via LOS;
* Added Bluetooth SIM Access Profile support (not tested)
* Using the preload partition for compatibility with the new version of TWRP Emulated Storage by rINanDO
* Applied security updates from LineageOS (July 2019) because Google has not released a new tag for the Oreo
Important:
Update the TWRP before installation!
Files Required:
TWRP EMU 3.3.1-1 by rINanDO
1) Flash TWRP EMU 3.3.1-1 by rINanDO and reboot recovery.
2) Install the new update with dirty flash.
Changelog
04062019 [EOL]
* Android 8.1.0_r65
* GApps updated to the latest
* Fix ADB connection via FunctionFS
* Chromium webview: Updated to 72.0.3626.121 via LOS;
09042019 [EOL]
First PixelExperience ASB build
* Android 8.1.0_r63
* Increased heapsize to 360mb
* Support to multi user added
* GApps updated to the latest
* Performance enhancements
* Emulated storage implemented
* Ported FunctionFS to our kernel (credits goes to @rINanDO)
24112018
* Updated sources;
* GApps updated to the latest
* Fix brightness button;
* Various bug fixes.
07112018
* Updated sources;
* GApps updated to the latest
13102018
* Enabled wifi powersave mode (credits goes to @rINanDO)
* Chromium webview: Updated to 69.0.3497.109 through the lineageos repository;
* GApps updated to the latest
04102018
* Performance optimizations;
* Implementation of auto sleep through (battery drain has improved a lot!);
* GApps updated to the latest
ohh!! i was waiting for this!!
thanks
i'll try and report
thanks alot for share :good:
but if this is a beta, i think it's better add BETA in title
linusdan said:
PixelExperience for Samsung Galaxy SII International (GT-I9100)
DON'T FLASH GAPPS, ALREADY INCLUDED
Download:
GDrive - AFH
Last Updated 2018-09-21
Click to expand...
Click to collapse
Thanks for the ROM. But I don't need and like g-apps. How to uninstall them?
I'm getting error 7 while patching system partition. I have 1GB system partition. how big does it need?
fixed it, system partition had gone dirty, fixe it, could able to flash
guest4711 said:
Thanks for the ROM. But I don't need and like g-apps. How to uninstall them?
Click to expand...
Click to collapse
chhapil said:
I'm getting error 7 while patching system partition. I have 1GB system partition. how big does it need?
fixed it, system partition had gone dirty, fixe it, could able to flash
Click to expand...
Click to collapse
I put this information in the second and third posts. I was going to add before, but I was very sleepy. Take a look, please
linusdan said:
I put this information in the second and third posts. I was going to add before, but I was very sleepy. Take a look, please
Click to expand...
Click to collapse
Sure will help as normally pixel ROMs come with gapps pre packaged it needs bigger system partition.
Also i have seen from Moto G forum, folks have seen better results with Android Go config.
Worth a try for our old device
linusdan said:
INSTRUCTIONS FOR RESIZING THE PARTITION
2) Open the odin. In the pit tab on the left side, select the file "I9100_1.5GB-System_6GB-Data_512MB-Preload_by-
Click to expand...
Click to collapse
Do you recommend that pit files for all yours ROMs? For Nougat too?
Gastozz said:
Do you recommend that pit files for all yours ROMs? For Nougat too?
Click to expand...
Click to collapse
And why not?
Thanks, Feedback as soon as possible
New build is up with Android Go configurations.
Download in OP.
-So far for me:
-Install from jb 4.2.1 after repit get find.
- Phone not recognized by connecting PC câble to windows 7
- Cannot open files from ES explorer apps. Message "SD card formated as internal memory, reboot your phone"
- My files apps works to go to external SD but until now internal SD no chance, maybe a repit problem, going to repit and reinstall to see.
- Camera works great but sending photos by bluetoth or gmail didn't work.
- Don't know anything about call transmition, cose' still have issue regarding, after reboot, ask me for network unlock.
Since i bought it 7 years ago, free from any mobiile operator, i never had this problem before and until now it got thousands "ROM flash".
Maybe because i changed the sim card or imei issue? so long guys
islander999 said:
-So far for me:
-Install from jb 4.2.1 after repit get find.
- Phone not recognized by connecting PC câble to windows 7
- Cannot open files from ES explorer apps. Message "SD card formated as internal memory, reboot your phone"
- My files apps works to go to external SD but until now internal SD no chance, maybe a repit problem, going to repit and reinstall to see.
- Camera works great but sending photos by bluetoth or gmail didn't work.
- Don't know anything about call transmition, cose' still have issue regarding, after reboot, ask me for network unlock.
Since i bought it 7 years ago, free from any mobiile operator, i never had this problem before and until now it got thousands "ROM flash".
Maybe because i changed the sim card or imei issue? so long guys
Click to expand...
Click to collapse
I am using ROM for 8 days and have not seen any related issues. I'll consider some things.
Thanks for the feedback!
linusdan said:
I am using ROM for 8 days and have not seen any related issues. I'll consider some things.
Thanks for the feedback!
Click to expand...
Click to collapse
Regarding the unlock network code message, it happens since i tried to install lineage-15.1-20180731-UNOFFICIAL-i9100 i guess, not from your ROM.
But for other bugs i still have issue, even after new reinstall, from repit. Maybe i miss something after the repit process.
I don't remember, should we reconfigure the format of cache, system, etc ?
islander999 said:
Regarding the unlock network code message, it happens since i tried to install lineage-15.1-20180731-UNOFFICIAL-i9100 i guess, not from your ROM.
But for other bugs i still have issue, even after new reinstall, from repit. Maybe i miss something after the repit process.
I don't remember, should we reconfigure the format of cache, system, etc ?
Click to expand...
Click to collapse
Yes! A thorough cleaning is always recommended.
linusdan said:
Yes! A thorough cleaning is always recommended.
Click to expand...
Click to collapse
Thanks for your answer but i did all the wipe.
I was meaning before, do i have to change file system from EXT4 to F2FS for example
islander999 said:
Thanks for your answer but i did all the wipe.
I was meaning before, do i have to change file system from EXT4 to F2FS for example
Click to expand...
Click to collapse
If you wish.
https://forum.xda-developers.com/showthread.php?t=3752664 go apps it works on dotos v2.5 oreo
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
*****Disclaimer*****
Important note before proceeding!!!
The copy A/B partions zip is crucial in order to prevent bricks. It only needs to be done if your coming from the stock ROM or you recently restored stock firmware manually. Other wise without it you can brick due to Motorola's A/B partition scheme.
Preparation for A/B Roms:
01. Download TWRP.
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip + TWRP_installer
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. Boot into recovery
03. Install ROM.zip + TWRP_installer
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must "format data" in recovery before using ROMS
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
LIST-KNOWN-ISSUES-ON-YOUR-DEVICE-HERE
None
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 )
Device tree: https://github.com/Rondeau79/android...motorola_ocean
Vendor tree: https://github.com/Rondeau79/proprie...g/lineage-16.0
Download Link: https://androidfilehost.com/?w=files&flid=302315
AB copy partitions Download Link: https://androidfilehost.com/?fid=4349826312261636295
XDA:DevDB Information
CrDroid Pie, ROM for the Moto G7 Power
Contributors
Rondeau79
Source Code: https://github.com/crdroidandroid/android/tree/9.0
Kernel tree:https://github.com/Rondeau79/android_kernel_motorola_sdm632/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest bootloader and TWRP recovery
Based On: Lineage OS
Version Information
Status: Stable
Current Stable Version: 5.11
Stable Release Date: 2019-11-25
Created 2019-11-27
Last Updated 2019-12-23
Reserved
Thank you Rom is really stable and beautiful plenty of customization baked in. Been running it for 4 days no problems at all OTA is also working great two updates already love it
Thanks! I run it as my daily driver. My first official ROM! I have built plenty in the past, but decided to make the jump. As soon as a few bugs get straighten out I will be moving it to Android 10!
Just installed the rom a couple of hours ago, and damn it's good! Only a small problem though, when you make a screenshot the little menu that appears where you can edit and take extended screenshots closes after a few seconds on its own. Is this intended or a bug? If so I hope you can fix it in the next update. Thanks a lot for the rom!
badapple420 said:
Thank you Rom is really stable and beautiful plenty of customization baked in. Been running it for 4 days no problems at all OTA is also working great two updates already love it
Click to expand...
Click to collapse
Gabe29 said:
Just installed the rom a couple of hours ago, and damn it's good! Only a small problem though, when you make a screenshot the little menu that appears where you can edit and take extended screenshots closes after a few seconds on its own. Is this intended or a bug? If so I hope you can fix it in the next update. Thanks a lot for the rom!
Click to expand...
Click to collapse
You can change the animation speeds in developer options to slow down that screenshot options. That will allow that edit page to stay on your screen longer.
Rondeau79 said:
You can change the animation speeds in developer options to slow down that screenshot options. That will allow that edit page to stay on your screen longer.
Click to expand...
Click to collapse
I see, I set the duration scale to 0.5x so no wonder it closed so fast. Anyways is there a way to make opengl skia the default gpu renderer? Because it switches back to default after a reboot.
Gabe29 said:
I see, I set the duration scale to 0.5x so no wonder it closed so fast. Anyways is there a way to make opengl skia the default gpu renderer? Because it switches back to default after a reboot.
Click to expand...
Click to collapse
Flash the attached zip in recovery. It will take care of that.
Rondeau79 said:
Flash the attached zip in recovery. It will take care of that.
Click to expand...
Click to collapse
Thank you, it worked.
As it is getting regular updates I though I would give this ROM a try on my new G7 Power. To be honest it works much better than I expected, not seeing any stability problems and it has some nice features. Still testing, but will probably start using this ROM + phone as my daily.
I did however have a heck of a time installing and getting both the ROM and TWRP to boot on the phone. That mostly had nothing to do with this ROM and more to do with the A/B partitions thingy Google has done on recent phones (which I have grown to hate). Also the ROM's install instructions are a bit vague in parts, so there was a bit of a learning curve (for me at least).
One the upside everything I have tested so far works. Storage encryption is enabled by default and working, wifi works (even with hidden SSIDs), dual SIMS works, camera app works, fingerprint works , call quality seems good. SELinux is disabled, which is not good but I can live with.
A big thanks for the all the done work on this!!
joefidler said:
As it is getting regular updates I though I would give this ROM a try on my new G7 Power. To be honest it works much better than I expected, not seeing any stability problems and it has some nice features. Still testing, but will probably start using this ROM + phone as my daily.
I did however have a heck of a time installing and getting both the ROM and TWRP to boot on the phone. That mostly had nothing to do with this ROM and more to do with the A/B partitions thingy Google has done on recent phones (which I have grown to hate). Also the ROM's install instructions are a bit vague in parts, so there was a bit of a learning curve (for me at least).
One the upside everything I have tested so far works. Storage encryption is enabled by default and working, wifi works (even with hidden SSIDs), dual SIMS works, camera app works, fingerprint works , call quality seems good. SELinux is disabled, which is not good but I can live with.
A big thanks for the all the done work on this!!
Click to expand...
Click to collapse
Download terminal emulator
Su
setenforce 1
SeLinux will be enforcing
Hey @Rondeau79, thank you for the rom, this was actually the only one I was able to flash. (But I think the problem is on my side of the table
Is there any way to get rid of the google-parts of the rom (searchbar etc.)? Thx in advance!
[email protected] said:
Hey @Rondeau79, thank you for the rom, this was actually the only one I was able to flash. (But I think the problem is on my side of the table
Is there any way to get rid of the google-parts of the rom (searchbar etc.)? Thx in advance!
Click to expand...
Click to collapse
The search bar is apart of the launcher, it is based off the Lawn chair launcher. You could always not flash Gapps and use Aptoide as store for apps..
Any suggestions on the best way to use MicroG with this ROM? It's listed here https://forum.xda-developers.com/showpost.php?p=71042083 as having signature spoofing but I could not find it. cheers.
joefidler said:
Any suggestions on the best way to use MicroG with this ROM? It's listed here https://forum.xda-developers.com/showpost.php?p=71042083 as having signature spoofing but I could not find it. cheers.
Click to expand...
Click to collapse
Some ROMs have an option button built in. Others the option is just baked in, it will work.
joefidler said:
Any suggestions on the best way to use MicroG with this ROM? It's listed here https://forum.xda-developers.com/showpost.php?p=71042083 as having signature spoofing but I could not find it. cheers.
Click to expand...
Click to collapse
Go with the Xposed method. As of late CrDroid Pie dose not support it. That would have to be a custom build.
Thanks @Rondeau79 will try Xposed. MicroG's spoofing check does not detect signature spoofing.
---------- Post added at 02:56 PM ---------- Previous post was at 02:56 PM ----------
Thanks @Rondeau79 will try Xposed. MicroG's spoofing check does not detect signature spoofing.
This will be the first ROM I flash to my phone. Can wait to get it set up!
joefidler said:
Any suggestions on the best way to use MicroG with this ROM? It's listed here https://forum.xda-developers.com/showpost.php?p=71042083 as having signature spoofing but I could not find it. cheers.
Click to expand...
Click to collapse
WoofahRayet said:
This will be the first ROM I flash to my phone. Can wait to get it set up!
Click to expand...
Click to collapse
Any questions feel free to pm me!
Thanks again for this port o.p
Ive tried all roms accept omni and this rom by far exceeds expectations. The Best Gaming Rom ive used.
I dont know what changes were made from the kernel between the 11/19 build and the 11/28 build. But I got better performance with the 11/19 kernel so i lm using the 11/19 build boot.img on the 11/28 rom update.
Battery drain is less noticeable on the latest build as the 11/19 build was draining very fast.
Once one roots this rom with a few tweaks, one will see a huge boost in performance.
Resurrection Remix was my daily driver prior because of the Led Notification light in which i love on this phone.
@Rondeau79 can the notification light get added to CRDroid like on RR and Aospex...?cOther than that no bugs to report.
You rock o.p..!!!
{
"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"
}
This is Cypher. An extension to pure Android. Cypher tries maintain the purity of Android while offering useful features for users. The goal is to give the highest level of performance whilst achieving Simplicity.
Code:
/*
* 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.
*/
Get your builds and changelog from our website
get.cypheros.co
Note: Builds are updated as soon as possible. There is no build cycle. Information pertaining to your device is displayed Accordingly. The current build is the latest for your device. If your device is scheduled to release on a certain day, but the new build isn't displaying, contact your device maintainer for more information but wait at least 72 h. Please know builds are updated by 12am EST.
Special Thanks to matteo0026, who is maintaining the device sources and TWRP.
Become apart of our G+ community - JOIN
REMINDER
If you're having issues and want to submit a report (Logcat) please make sure you are reporting from the stock kernel, not a modified kernel. Modified kernels can break or fix, even improve things. It depends. I can't get a full clue of the issue when you're not running the original kernel.
Click to expand...
Click to collapse
Features:
- Status bar Customization
- Changeable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
- Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- System
- Screenshot partial and full
- Scrolling cache customization
- Power menu customization
- One-handed mode
Credits
LineageOS
AICP
PureNexus
AOKP
Dirty Unicorns
Paranoid Android
and more..
Installation instructions :
Be sure to have installed the latest TWRP recovery (you can find it in downloads)
Download the latest build and GApps (ARM, 9.0, I advice pico package) and copy it to your external SD-Card
Make a full Backup of your Data and copy it to your external SD-Card or USB-OTG
Boot to recovery mode
Wipe > Advanced wipe > Select system, data, cache and dalvik/art cache (and, if you want to clean more, select even internal storage, which deletes all the content in /sdcard) and do swipe to wipe. Format /data. When it's finished go to home page
Install > select ROM zip file > swipe to flash and when it's finished go to home page
Do the same thing to flash GApps and Root (if needed)
Reboot > System
Update instructions :
Be sure to have installed latest TWRP build
Download the latest build
Boot to recovery mode
Install > select ROM zip file > swipe to flash and, when it's finished go to home page
Reboot > System
Known issues
Mirror Screen maybe broken
Uplink to Chromecast maybe broken
Downloads (ROM)
matisse (10.1) devices: Androidfilehost, Mega
millet (8.0) devices: Androidfilehost, Mega
Matisse and Millet via Github
Other Stuff
TWRP Recovery Matisse and Millet: XDA, Mega, Matisse, Millet
GApps: https://opengapps.org/ (ARM, 11, Best to use is Nano or Pico) or
GApps: MindTheGapps
Magisk: https://github.com/topjohnwu/Magisk
Contributors:
crazydrive22, matteo0026 and all the S3NEO devs that provided the base for developing Pie on Tab 4
Source Code:
https://github.com/lineageos for samsung msm8226 common device and kernel source, with some patches coming from Gerrit for device source
https://github.com/s3neo for matisse and millet and specific variants device and vendor source
Thread started at 2021-09-24
Thread updated at 2022-01-20
New Updates for CypherOS are online.
Changelog
-Security Patch October '21
-Synced with LOS-Source
-A lot of work under the Hood from @matteo0026
Wonderful rom sir. My first issue is that Im not able to sign into playstore when or get past "Getting tablet ready" it always says "Couldnt connect" Not sure if its the rom or the gapps but im using opengapps. Anyway, thank you so much for the hard work that you have done with this rom. Extremely impressed. Thank you so much and looking forward to see more of your work.
Dvalin21 said:
Wonderful rom sir. My first issue is that Im not able to sign into playstore when or get past "Getting tablet ready" it always says "Couldnt connect" Not sure if its the rom or the gapps but im using opengapps. Anyway, thank you so much for the hard work that you have done with this rom. Extremely impressed. Thank you so much and looking forward to see more of your work.
Click to expand...
Click to collapse
Are you sure Wifi is connected?
If yes, try a different package of Gapps or try to restore a older backup (/data only) from a different ROM, if you have. Also be aware, that our tablets cannot connect to Routers with WPA3.
This will be fixed in one of the next builds.
crazydrive22 said:
Are you sure Wifi is connected?
If yes, try a different package of Gapps or try to restore a older backup (/data only) from a different ROM, if you have. Also be aware, that our tablets cannot connect to Routers with WPA3.
This will be fixed in one of the next builds.
Click to expand...
Click to collapse
I tested mindthegapps from this link https://www.cyanogenmods.org/downloads/mindthegapps-11-0-download/ its letting me setup, so it just opengapps that is the issue. Will share more later
Dvalin21 said:
I tested mindthegapps from this link https://www.cyanogenmods.org/downloads/mindthegapps-11-0-download/ its letting me setup, so it just opengapps that is the issue. Will share more later
Click to expand...
Click to collapse
Aye. Sometimes the Setup Wizard is causing troubles.
logcat and kernel logs. Also, the button for the camera is so low on the screen its cut off. I tried to make a phone call earlier, but it would just end the call immediately. Im able to get on the internet with 4G though
Dvalin21 said:
logcat and kernel logs. Also, the button for the camera is so low on the screen its cut off. I tried to make a phone call earlier, but it would just end the call immediately. Im able to get on the internet with 4G though
Click to expand...
Click to collapse
Hi. I´ve tested the Issues you mentioned.
The Camera App seems to be broken or has a wrong resolution. That´s nothing i can fix but i´ll report it to the devs. As a workaround install Open Camera. This App is working normal.
I tested phonecalls (in and out) with 4G and Edge. Both are working for me.
Maybe there´s an issue with your local provider. If the problem persists, i would suggest to dl ROM and Gapps again (maybe a file is corrupted), delete your ROM in TWRP + format /data and do a clean install of both, ROM and Gapps. Often this will fix those errors.
Your logcat is looking not too bad except a crash of firebase, what definetly could cause the trouble. But we´ll see it, if you´ve done a clean and fresh installation.
Hi, I got the SM-T531 tablet and I'm going to download this ROM and see how it behaves I will do all the possible tests I can do, to contribute. There's no way the 3g works right, just connections right?
Utherbone said:
Hi, I got the SM-T531 tablet and I'm going to download this ROM and see how it behaves I will do all the possible tests I can do, to contribute. There's no way the 3g works right, just connections right?
Click to expand...
Click to collapse
Yes, unfortunately 3g isn't working at any ROM from 9 to 11.
Matteo is working on it but with no success so far.
New Files are up!
-synced with LOS-Source
-Security Patch November 2021
-all Devices are now able to use WPA3
Hi @crazydrive22 . I'll take the opportunity and ask you a question of mine. I'm having trouble flashing any SM-T531 compatible roms. I will list the steps I followed.
1 - Flasing twrp with heimdall. At first I tried here: https://twrp.me/samsung/samsunggalaxytab4101.html but ta off the link there.
I downloaded it here on the XDA forum: https://forum.xda-developers.com/t/recovery-3-5-2_9-unified-matisse-millet-twrp-recovery.4019831/ ;
2 - full wipe and format;
3 - Flashing this rom (with or without gapps) Resulting: Loop in Samsung logo or should I wait too long?
Thanks for working.
Utherbone said:
Hi @crazydrive22 . I'll take the opportunity and ask you a question of mine. I'm having trouble flashing any SM-T531 compatible roms. I will list the steps I followed.
1 - Flasing twrp with heimdall. At first I tried here: https://twrp.me/samsung/samsunggalaxytab4101.html but ta off the link there.
I downloaded it here on the XDA forum: https://forum.xda-developers.com/t/recovery-3-5-2_9-unified-matisse-millet-twrp-recovery.4019831/ ;
2 - full wipe and format;
3 - Flashing this rom (with or without gapps) Resulting: Loop in Samsung logo or should I wait too long?
Thanks for working.
Click to expand...
Click to collapse
Hi.
First boot can take a lot of time. If it's not booting i would suggest to flash Stock 5.0.2 and start again from scratch. It's nescessary to had 5.0.2 installed once to make sure, that the Bootloader is updated. The Bootloader from KitKat (4.x) is not working with LineageOS 9 or newer and it's forks like crDroid or Cypher. The TWRP from Matteo is good, it's the lastest one and working well. But i can't tell you anything about Heimdall. I'm using Odin only to flash Stock or TWRP.
crazydrive22 said:
Hi.
First boot can take a lot of time. If it's not booting i would suggest to flash Stock 5.0.2 and start again from scratch. It's nescessary to had 5.0.2 installed once to make sure, that the Bootloader is updated. The Bootloader from KitKat (4.x) is not working with LineageOS 9 or newer and it's forks like crDroid or Cypher. The TWRP from Matteo is good, it's the lastest one and working well. But i can't tell you anything about Heimdall. I'm using Odin only to flash Stock or TWRP.
Click to expand...
Click to collapse
Thanks for the answer, it must be the 4.4.x bootloader, I didn't even ask if I had the 5.x.x one, I'm flashing the 5.0.2 About haimdall. It's wonderful, a point that can be negative is that the process is more manual, you must select each file for its respective partition, the good thing is that with it you can capture the pit file, it is very rare for an error to occur except if there is a problem on the PC or cable. It works on Linux and Windows and Mac OS X. I will return with news.
This is working amazing on my SM-T530NU, far better than whatever Nook bloat that was running before.
Installed and tested in matisselte, very good rom, very fluid. Everything works perfectly,
I will continue using this rom, very happy with how it works.
I hope you continue with the updates. Great job
groulo said:
Installed and tested in matisselte, very good rom, very fluid. Everything works perfectly,
I will continue using this rom, very happy with how it works.
I hope you continue with the updates.
Click to expand...
Click to collapse
THX.
Updates every Month ca. 15th, maybe earlier.
Hello again @crazydrive22. I tested this rom, conclusions, this rom in my normal use, very usable with tricks in developer options "disable animations scale and enable acceleration 2d". Overall is good.
Sorry. I stay practice English, on this time don,t use translator
New Builds are up.
Changelog
-synced with LOS-Source
-Security Patch December 2021
I need help, I have a problem, I have gone to update and I have restarted in recovery mode, but the tablet does not start, it is in a loop restarting all the time. I have disconnected the battery and the problem continues.
What I can do?
{
"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.