[ROM][OREO][OFFICIAL] lineage-15.1 for Pixels (marlin/sailfish) - Google Pixel XL ROMs, Kernels, Recoveries, & Other

[ROM][OREO][OFFICIAL] lineage-15.1 for Pixels (marlin/sailfish) - Google Pixel XL ROMs, Kernels, Recoveries, & Other

Official 15.1 nightlies have been discontinued.
Go here for the official 16.0 thread.
{
"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 a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki.
Important Info
Make sure you have the vendor, radio, & bootloader img's installed, from the stock oreo 8.1 OPM4.171019.021.P1 July 2018 factory image. More info below.
Download Links
marlin rom: https://download.lineageos.org/marlin
marlin vendor, radio, & bootloader img's: https://androidfilehost.com/?w=files&flid=278595
marlin twrp: https://twrp.me/google/googlepixelxl.html
sailfish rom: https://download.lineageos.org/sailfish
sailfish vendor, radio, & bootloader img's: https://androidfilehost.com/?w=files&flid=278596
sailfish twrp: https://twrp.me/google/googlepixel.html
google apps (Optional): https://wiki.lineageos.org/gapps.html
root su addon (Optional): https://download.lineageos.org/extras Note: Use arm64 zip. After installing the su addon, you can enable root in developer options.
Instructions
Initial Install
NOTE#1: Make sure you have the correct vendor, radio, & bootloader img's installed in BOTH slots before installing lineage. They can be extracted from the oreo 8.1 OPM4.171019.021.P1 July 2018 factory image or use the ones in the download section above that I already extracted for you. You can flash them using the following commands:
fastboot flash --slot all vendor VendorFileName.img
fastboot flash --slot all radio RadioFileName.img
fastboot flash --slot all bootloader BootloaderFileName.img
NOTE#2: The official mindthegapps build that's linked in the wiki are very minimal (like opengapps pico), so i made my own mindthegapps build that is pretty much the same as opengapps nano. download link
NOTE#3: If you're a Project Fi or Sprint customer, you need some extra gapps, so use this one instead. download link
NOTE#4: If you want to update from my unofficial 15.1 build to official without wiping, you can follow the "How to dirty flash an official weekly over an unofficial build" steps here.
1. boot into twrp and wipe data and system
2. flash rom zip
3. flash twrp zip
4. in twrp main menu, select reboot then recovery (this will reboot you into the other slot)
5. flash gapps zip (optional)
6. flash su addon zip for root (optional)
Reboot & enjoy.
Updating
If you've already done the initial install, then you can use the LineageOS Updater to install new builds. It's in settings->system->about phone->lineageos updates.
It will give you a notification when a new build is available.
Weather Provider Addons (Optional)
For those that like to use the lineage cLock widget, here are some weather provider apk's you can use that i compiled.
https://www.androidfilehost.com/?w=files&flid=243785
Changelog
https://download.lineageos.org/marlin/changes/
Bug Reporting
If a bug is discovered, confirm it with other users in this thread, then report it following our wiki here: https://wiki.lineageos.org/bugreport-howto.html
LineageOS Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Source Code:
Device tree: https://github.com/LineageOS/android_device_google_marlin/tree/lineage-15.1
Kernel tree: https://github.com/LineageOS/android_kernel_google_marlin/tree/lineage-15.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-15.1
Android version: 8.1.0 Oreo
Kernel version: Linux 3.18.70

Omg LOS 15 ! Any Sailfish compatibility ?

Nice

Nice!!!!! Bugs?

Anyone Flash this yet?

Thanks very much for this. Op instructions were flawless and booted right up. Feel's good to be running los, everything I've tested/used works perfectly

billiepreks said:
Any Sailfish compatibility ?
Click to expand...
Click to collapse
nope, sorry. But it can be built and works fine. I know a person that uses it.
TotoBerto02 said:
Bugs?
Click to expand...
Click to collapse
Only a couple things come to mind that are worth mentioning...
Livedisplay has not been implemented yet. But Night Display is working fine.
And I cherry-picked the buttons settings changes into this rom, which is still a work-in-progress. So some of them don't work yet, but most do.
JS.zip said:
Op instructions were flawless...
Click to expand...
Click to collapse
Thanks to @kgjel for that :good:
He gave me a set of detailed instructions that I revised slightly and put in the first post.

JS.zip said:
Thanks very much for this. Op instructions were flawless and booted right up. Feel's good to be running los, everything I've tested/used works perfectly
Click to expand...
Click to collapse
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!

mrhds said:
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!
Click to expand...
Click to collapse
Same problem here, i get about 3-5 Boot Loops and then it finally stops at the G with the line under. I tried multiple times...

mrhds said:
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!
Click to expand...
Click to collapse
I saw that as well. I was on 8.1, I took the main op too be correct.

mrhds said:
The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013.
Click to expand...
Click to collapse
thanks. fixed.
unfortunately, flashing stuff on a marlin is a major pain in the rear. very easy to mess up.
make sure you follow the steps EXACTLY.

AndroidDevices said:
Same problem here, i get about 3-5 Boot Loops and then it finally stops at the G with the line under. I tried multiple times...
Click to expand...
Click to collapse
mrhds said:
No such luck here. The post says to be on 8.1 OPM1.171019.011, but the detailed instructions say to match what's in the lineage.mk, which is OPR3.170623.013. Which stock build were you on when installing this ROM? I either get boot loops or it ends up booting up, but it is still the stock OS. I have tried following the detailed instructions exactly, and all seems to go well, but no Lineage!
Click to expand...
Click to collapse
The lineage MK file linked in the detailed instructions shows OPM1.171019.011. Not sure which one you're looking at? The link goes here: https://github.com/razorloves/android_device_google_marlin/blob/15.1-testing/lineage.mk#L22

hokiealumnus said:
The lineage MK file linked in the detailed instructions shows OPM1.171019.011. Not sure which one you're looking at? The link goes here: https://github.com/razorloves/android_device_google_marlin/blob/15.1-testing/lineage.mk#L22
Click to expand...
Click to collapse
I read the detailed instructions, im not looking at what he's looking at...FYI

TWRP 3.2.0-0 is unable to decrypt the factory "opm1" /data store. 3.2.1-0 is able to decrypt but fails to flash LOS. Something is not quite correct here.....

carbinefreak said:
TWRP 3.2.0-0 is unable to decrypt the factory "opm1" /data store. 3.2.1-0 is able to decrypt but fails to flash LOS. Something is not quite correct here.....
Click to expand...
Click to collapse
Do you have a pin or password on your lockscreen? If so you must remove it first

so are you the new maintainer? officially?

Zehlek said:
Do you have a pin or password on your lockscreen? If so you must remove it first
Click to expand...
Click to collapse
Good catch, Removed the password and ran through the procedure just fine. Phone just finished first boot and is in the process of updating apps now......
Thanks! Super Cool!

@razorloves is this always required when flashing any rom on Maril?
f - Go to `Mount` and select to mount `Vendor`. Go back to TWRP home
g - Go to `Advanced` - > `File Manager`. Navigate to /vendor/overlay/, then click the checkmark in the bottom right. Select `Delete`.
Click to expand...
Click to collapse

Thanks to @razorloves for making me actually read directions and stop being such a noob....

jmiller3342 said:
so are you the new maintainer? officially?
Click to expand...
Click to collapse
Yes. Intervigil is a maintainer too.
Zehlek said:
@razorloves is this always required when flashing any rom on Maril?
Click to expand...
Click to collapse
not necessarily.
Google put a couple theme apk's and frameworks apk in that folder. It will override a lot of changes we make to our custom rom. So I think it's best to remove it.
You can see my comments in this change to give you an idea of one of the problems that frameworks apk can cause. https://review.lineageos.org/198569
When you flash stock rom or flash the vendor img from the stock rom, it will replace that folder that was deleted.

Related

[ROM][10][OFFICIAL] lineage-17.1 for Pixels (marlin/sailfish)

{
"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 a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki for more details.
IMPORTANT NOTES:
1. If you use twrp it will ask if you want to install the twrp app. Make sure you tap "DO NOT INSTALL".
2. If you care about your stuff, make a backup in TWRP first, just in case. Transfer it to a pc, along with all your stuff in internal storage.
3. The newest vendor, radio, & bootloader img's are included in the rom zip, so no need to worry about flashing those manually.
4. Lineage comes with adb root that you can enable in developer options, but if you want root for apps, flash magisk in recovery (after renaming magisk.apk to magisk.zip). Just don't flash it during initial lineage install, as it's known to cause bootloop if you do.
Downloads:
marlin rom: https://download.lineageos.org/marlin
sailfish rom: https://download.lineageos.org/sailfish
gapps: (gapps are optional) link WARNING: Only use nano or pico because the system partition is too small on our device.
google fi gapps addon: if your carrier is Google Fi, flash this zip right after flashing the gapps zip. https://androidfilehost.com/?fid=8889791610682871038
Instructions:
FOR INITIAL INSTALL
marlin: https://wiki.lineageos.org/devices/marlin/install
sailfish: https://wiki.lineageos.org/devices/sailfish/install
FOR UPDATING
For normal updating from official 17.1 to a newer official 17.1, follow these steps:
marlin: https://wiki.lineageos.org/devices/marlin/update
sailfish: https://wiki.lineageos.org/devices/sailfish/update
Protip: Enable "Prioritize update process" in the Updater preferences to make it go faster
NOTE: If you're updating from my unofficial build to the official nightlies, follow steps here.
Alternative manual updating instructions:
1. boot into lineage recovery.
2. install rom zip.
3. if you use gapps or magisk, select the "reboot into recovery" option, then install those zips.
FOR UPGRADING (From official 16.0 to official 17.1, for example)
marlin: https://wiki.lineageos.org/devices/marlin/upgrade
sailfish: https://wiki.lineageos.org/devices/sailfish/upgrade
Changelog
marlin
sailfish
Bug reporting
https://wiki.lineageos.org/bugreport-howto.html
Source Code:
Marlin Device tree: https://github.com/LineageOS/android_device_google_marlin/tree/lineage-17.1
Sailfish Device tree: https://github.com/LineageOS/android_device_google_sailfish/tree/lineage-17.1
Kernel tree: https://github.com/LineageOS/android_kernel_google_marlin/tree/lineage-17.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-17.1
Credits:
Many thanks to my fellow LineageOS team members and all the contributors out there in the community. :good:
Android version: 10
Kernel version: 3.18.137
Status: Nightly

That's great! Does this have Google dialer included?

Thank you for your awesome work

Intriguing ?.

<Mod edit: Quoted OP removed>
A lot of Google's apps crushing , the rest is all good . I know is a beta so no complaints

Hello!! I installed this assembly, I liked it, but later can I switch to nightly assemblies from this assembly?

alin919 said:
A lot of Google's apps crushing , the rest is all good . I know is a beta so no complaints
Click to expand...
Click to collapse
I had that but it was because I also wiped system and cache. I reflashed stock and only wiped data and now Google apps work except for Gmail

Just reporting, I am not passing safety net

alin919 said:
A lot of Google's apps crushing , the rest is all good . I know is a beta so no complaints
Click to expand...
Click to collapse
Do you have Magisk installed? I removed Magisk and now all Google apps work

Zehlek said:
Do you have Magisk installed? I removed Magisk and now all Google apps work
Click to expand...
Click to collapse
I do now , but is weird ... now drive is working and calendar and gmail not ( second time installed clean and downloads the apps from playstore before got root )

Try this, it helped me
Zehlek said:
Just reporting, I am not passing safety net
Click to expand...
Click to collapse
This video helped me pass safety-net
https://youtu.be/8ATH032lIXs

An easy fix, for anyone with the gmail issue, you just have to go to settings->apps->gmail->permissions, and allow permissions to contacts and calendar.
EDIT: I'll try to figure out the issue of why gmail is not being granting permissions automatically, like it should.
But in the meantime, i'll just include gmail in my builds. That way it has that right permissions and just works like it should. If you don't want the app, you can just go to settings and disable it.
EDIT#2: New builds are available in first post. One notable feature that was added is, network traffic monitor in statusbar. :good:
Note: I don't have a sailfish so that build is untested, but it should work fine. Please someone give it a try and let us know if it's ok. Confirmed, it's working good on sailfish too.

razorloves said:
EDIT#2: New builds are available in first post. One notable feature that was added is, network traffic monitor in statusbar.
Note: I don't have a sailfish so that build is untested, but it should work fine. Please someone give it a try and let us know if it's ok. :good:
Click to expand...
Click to collapse
Incredible thanks!! I'll test this out

Is the system mounted r/w on this rom?

razorloves said:
An easy fix, for anyone with the gmail issue, you just have to go to settings->apps->gmail->permissions, and allow permissions to contacts and calendar.
EDIT: I'll try to figure out the issue of why gmail is not being granting permissions automatically, like it should.
But in the meantime, i'll just include gmail in my builds. That way it has that right permissions and just works like it should. If you don't want the app, you can just go to settings and disable it.
EDIT#2: New builds are available in first post. One notable feature that was added is, network traffic monitor in statusbar.
Note: I don't have a sailfish so that build is untested, but it should work fine. Please someone give it a try and let us know if it's ok. :good:
Click to expand...
Click to collapse
So far so good, I saw this that root is disabled, is there anyway to enable it without using Magisk?

cyberbandit1998 said:
Is the system mounted r/w on this rom?
Click to expand...
Click to collapse
ikr, it was read only on the stock rom, immediately went back to Los16 lol

so, it seems as if there are no real game-breaking issues out of the gate?? I'm looking forward to trying this later but was holding off for some more feedback, so far it seems to be pretty positive... one (stupid) question... After flashing this can you easily just flash back to a PIE rom if need be, or once you go Android 10 you can't go back?

yes you can
johnblundon said:
so, it seems as if there are no real game-breaking issues out of the gate?? I'm looking forward to trying this later but was holding off for some more feedback, so far it seems to be pretty positive... one (stupid) question... After flashing this can you easily just flash back to a PIE rom if need be, or once you go Android 10 you can't go back?
Click to expand...
Click to collapse
I have flashed stock pie from Android 10 a couple of times

Zehlek said:
So far so good, I saw this that root is disabled, is there anyway to enable it without using Magisk?
Click to expand...
Click to collapse
not yet. have to use magisk.
johnblundon said:
After flashing this can you easily just flash back to a PIE rom if need be
Click to expand...
Click to collapse
yep, i did it the other day. went from lineage 17 to 16, with just a data wipe. no issues.

So device personalization services app kept crashing so I uninstalled it
also trying to enable black theme in settings makes settings app crash
Also had the Gmail permission bug thanks for posting the fix ?
Also why was twrp overwritten by stock Google recovery ?
I didn't see a warning about that anywhere in op
Note I did a clean install wiped all partitions but internal storage in twrp 3.3.0.0 before flashing rom and then magisk zip

[ROM] Dirty Unicorns 14.7 {Blueline} (09/13/20)

{
"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"
}
About Us:
Dirty Unicorns is an AOSP based project built to enhance the stock Android experience.
Our focus has been and is always to contribute back to the community. That is ultimately why we do what we do.
We DO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. This includes, but is not limited to; Devices, Gerrit, our websites and services, etc.. The only thing that we ask in return is that you have patience, search the thread for answers prior to posting, read diligently, and try to enjoy the process with us!
Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_google_bluecross
Flashing Instructions:
If you have a device that uses TWRP
Verify that you're using the latest version of TWRP
Perform a FULL WIPE: (A full wipe is when you wipe system/data/cache/dalvik)
Flash the latest version of this ROM
Reboot and ENJOY!
If you have a device that does not use TWRP
Download boot.img and ROM zip from DU server
Reboot into bootloader and flash the boot.img
Code:
fastboot flash --slot all boot boot.img
Reboot to recovery
Go to recovery select factory reset
Select Apply update from ADB to flash the zip
Code:
adb sideload nameofbuild.zip
Reboot and ENJOY!
If you're just updating DU on a device without TWRP
Download ROM zip from DU server
Reboot into recovery and select Apply update from ADB to flash the zip
Reboot system now and ENJOY!
**All bugs and feature requests must be reported to JIRA**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
**If you fail to follow these instructions, please don't bother reporting any bugs**
Download Links:
Build(s) - Blueline
Other Links:
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
JIRA (Bug Reporting / Feature Requests) - http://jira.dirtyunicorns.com/
Telegram - https://t.me/dirtyunicorns / https://t.me/DirtyUnicornsSupport
XDA:DevDB Information
Dirty Unicorns, ROM for the Google Pixel 3
Contributors
NYCHitman1
Source Code: https://github.com/DirtyUnicorns
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.7
Stable Release Date: 2020-09-13
Created 2020-08-08
Last Updated 2020-09-13

Been running this for a long time now. Stable and great battery life. Thank you to the DU team for your continued hard work!!

I've tried some roms and still can't find one as good as this one

why is my phone still stuck in stock rom after success sideloading on du recovery ?
D:\Download\blueline-qq3a.200805.001>adb sideload du.zip
Total xfer: 2.00x

rz9511 said:
why is my phone still stuck in stock rom after success sideloading on du recovery ?
D:\Download\blueline-qq3a.200805.001>adb sideload du.zip
Total xfer: 2.00x
Click to expand...
Click to collapse
you are messing with a/b partitions.. follow installation instructions to the letter

rz9511 said:
why is my phone still stuck in stock rom after success sideloading on du recovery ?
D:\Download\blueline-qq3a.200805.001>adb sideload du.zip
Total xfer: 2.00x
Click to expand...
Click to collapse
Because you probably never had stock on both slots. Flash stock to both slots then follow the flashing instructions from the OP.

I have the same problem as the person above.
Flashed latest factory image.
After following the instructions in "If you have a device that does not use TWRP", stock is still booting.
But the kernel shows unicorn, although the rest of the OS looks awfully alike stock, so I think it is stock.. A ROM feature list would be great..

Major Stuen said:
I have the same problem as the person above.
Flashed latest factory image.
After following the instructions in "If you have a device that does not use TWRP", stock is still booting.
But the kernel shows unicorn, although the rest of the OS looks awfully alike stock, so I think it is stock.. A ROM feature list would be great..
Click to expand...
Click to collapse
Follow the instructions of what I said above...

NYCHitman1 said:
Follow the instructions of what I said above...
Click to expand...
Click to collapse
And could you please explain how we flash it to both slots?
Edit; got it working now
- Removed the -w in flash-all (not sure if it was necesarry)
- Runned flash-all while on b
- Then fastboot --set-active a
- Runned flash-all while on a
Then followed the instructions, and it worked.

Major Stuen said:
And could you please explain how we flash it to both slots?
Edit; got it working now
- Removed the -w in flash-all (not sure if it was necesarry)
- Runned flash-all while on b
- Then fastboot --set-active a
- Runned flash-all while on a
Then followed the instructions, and it worked.
Click to expand...
Click to collapse
Boom. Good job!
Sorry for the tough love, but nobody learns anything by just being fed answers.

Is there any way install the vanilla Google sans font/any other additional font to the theme engine without rooting? Or does this need to come from you.
Thanks.

Crickets0812 said:
Is there any way install the vanilla Google sans font/any other additional font to the theme engine without rooting? Or does this need to come from you.
Thanks.
Click to expand...
Click to collapse
It's already included in DU.

There is a version of it yes, but it isn't exactly the same. It's a bit bolder than the original. As to the second part of the question, is there any way to add fonts myself?

Crickets0812 said:
There is a version of it yes, but it isn't exactly the same. It's a bit bolder than the original. As to the second part of the question, is there any way to add fonts myself?
Click to expand...
Click to collapse
Unfortunately not. You would have to download our source and compile your own builds with modifications to frameworks/base, packages/apps/DU-Themes, and vendor/themes.

Yo this rom slaps. Any plans of intergrating wireguard in the kernel?

infamous_black said:
Yo this rom slaps. Any plans of intergrating wireguard in the kernel?
Click to expand...
Click to collapse
That's a negative, bro.

Been using this rom for about two months now... I don't know a lot of roms that can top this kind of stability! I love using it as my daily driver. Thank you!!!

Tech180 said:
Been using this rom for about two months now... I don't know a lot of roms any other custom ROM that can top this kind of stability! I love using it as my daily driver. Thank you!!!
Click to expand...
Click to collapse
Fixed that for you

Hi guys, I've been trying to download this rom all morning but for some reason it keeps failing right after 1 gig. I've tried 4g, wifi and hardline but I keep getting the same result. Any ideas?

Pete02 said:
Hi guys, I've been trying to download this rom all morning but for some reason it keeps failing right after 1 gig. I've tried 4g, wifi and hardline but I keep getting the same result. Any ideas?
Click to expand...
Click to collapse
Not sure. Seems to be something related to slow internet speeds. Our webmaster is looking into it.

[ROM][11.0][marlin] PixelExperience [AOSP][OFFICIAL]

{
"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.

[OFFICIAL] LineageOS 19.1 for Moto G7 Plus

{
"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"
}
Moto G7 Plus
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Moto G7 Plus.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
lake - Official builds
lake - My unofficial with Google Apps/Pixel goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8998

Amazing!
Thanks a lot for the continuing support!

npjohnson said:
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
lake - Official builds
lake - My unofficial with Google Apps/Pixel goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Click to expand...
Click to collapse
This mean rooted device would not get support here?

when you start doing non-standard things with your phone, people aren't going to be able to help you troubleshoot problems as well. The more you deviate, the less likely people will be willing to help you. That's to be expected. It's the reason I keep things pretty vanilla (LOS + opengapps pico)...

proza said:
This mean rooted device would not get support here?
Click to expand...
Click to collapse
Correct.

NpJ, do you have recommend vendor firmware updates from official moto builds similar to this guide for OnePlus?
Update firmware on fajita | LineageOS Wiki
wiki.lineageos.org
I don't see any link to a similar sorta page from lake:
Info about lake | LineageOS Wiki
wiki.lineageos.org
Just wondering, because I haven't touched Moto ROMs since buying the phone.

retry0001-coffee said:
NpJ, do you have recommend vendor firmware updates from official moto builds similar to this guide for OnePlus?
Update firmware on fajita | LineageOS Wiki
wiki.lineageos.org
I don't see any link to a similar sorta page from lake:
Info about lake | LineageOS Wiki
wiki.lineageos.org
Just wondering, because I haven't touched Moto ROMs since buying the phone.
Click to expand...
Click to collapse
Nope, newest for your device. That's about it.

OK but should we grab the latest MOTO stock ROM, and copy the same partitions over as outlined in the 6T guide? If we do not do that, will it make latest LOS 19 buggy? Out of curiosity, what does *your* vendor patch level date say?

retry0001-coffee said:
OK but should we grab the latest MOTO stock ROM, and copy the same partitions over as outlined in the 6T guide? If we do not do that, will it make latest LOS 19 buggy? Out of curiosity, what does *your* vendor patch level date say?
Click to expand...
Click to collapse
nope - Just as long as you're on latest Android version - say lake, you should be on android 10, doesn't matter which sub version.
Vendor SPL is dependent on lineage, not stock - we build vendor - the 6T didn't used to - so they had to have users flash vendor themselves.

Oh interesting. Thanks for that clarification.

I looked for version 19.1 on the official website and didn't find anything to download. A few hours ago it was available. What happened?

Cool, thanks for the hard work!

fNttRX said:
I looked for version 19.1 on the official website and didn't find anything to download. A few hours ago it was available. What happened?
Click to expand...
Click to collapse
There is a new version built this night ( 20220427) now online. This worked now for me and even the first boot was really fast (~2 min). https://download.lineageos.org/lake
Had issues the whole night with the 20220426 build. I was always in a boot loop after sideloading the 26 version.
Later, I tried to go to Stock Rom first with the Lenovo Rescue and Smart Assistance (to my XT1965-3 (EU) ).
Sideloaded Recovery and Lineage 19.1 again -> bootloop.
Went to bed late, saw a new version right after getting up -> works as expected
First, Thank you @npjohnson for your work!
Do you have a personal donation link?

Version 27 hasn't bootloop
Do you have any problems installing gapps? I can't add google account after installation. i get application error. Wipe doesnt change anything
After installing 27.04 LOS, system updates info shows it is version 26. I can update to 27 but after reboot nothing happens and it still shows 26 with the option to install 27 again.

Can TWRP be used to flash this? If yes, any special version of TWRP needed?
I boot to TWRP using fastboot and not installing it on the phone.

dr.haggis said:
There is a new version built this night ( 20220427) now online. This worked now for me and even the first boot was really fast (~2 min). https://download.lineageos.org/lake
Had issues the whole night with the 20220426 build. I was always in a boot loop after sideloading the 26 version.
Later, I tried to go to Stock Rom first with the Lenovo Rescue and Smart Assistance (to my XT1965-3 (EU) ).
Sideloaded Recovery and Lineage 19.1 again -> bootloop.
Went to bed late, saw a new version right after getting up -> works as expected
First, Thank you @npjohnson for your work!
Do you have a personal donation link?
Click to expand...
Click to collapse
PayPal.me/nolenjohnson

jmozmoz said:
Can TWRP be used to flash this? If yes, any special version of TWRP needed?
I boot to TWRP using fastboot and not installing it on the phone.
Click to expand...
Click to collapse
Probably but I'd just use lineage recovery.

I installed it with the latest TWRP. It bootlooped with flamegapps but installed successfully with mindthegapps.
I install twrp on the system and it has a handy choice to reflash itself after installing the rom. You then must reboot to twrp to add the gapps zip or it will not work.
For anyone else interested I also installed magisk and it works perfectly but be aware of @npjohnson's point re loss of support.

petexd said:
I installed it with the latest TWRP. It bootlooped with flamegapps but installed successfully with mindthegapps.
I install twrp on the system and it has a handy choice to reflash itself after installing the rom. You then must reboot to twrp to add the gapps zip or it will not work.
For anyone else interested I also installed magisk and it works perfectly but be aware of @npjohnson's point re loss of support.
Click to expand...
Click to collapse
Thank you for your answer. Did you do a fresh install/wipe the data partition?
I have currently installed Lineageos 18.1 + Open Gapps for Android 11 (nano). Can I do a dirty flash/install with Lineageos 19 and MindTheGapps?
Which version of Magisk do you use? And which version of TRWP?

jmozmoz said:
Thank you for your answer. Did you do a fresh install/wipe the data partition?
I have currently installed Lineageos 18.1 + Open Gapps for Android 11 (nano). Can I do a dirty flash/install with Lineageos 19 and MindTheGapps?
Which version of Magisk do you use? And which version of TRWP?
Click to expand...
Click to collapse
I did a format data AND wipe with twrp-3.6.1. Make sure you follow the install instructions on twrp for motorola g7+. You need the img file and the zip.
I don't use open gapps- too mush bloat - but I got a bootloop with flamegapps so I followed npj's advice and used mindthegapps.
I didn't try a dirty flash so I don't know but I would go for the full wipe.
Good luck but if you do it properly you shouldn't need it.

Development [ROM] [OOS12FW] RisingOS v1.1 Android Project [dre] [UNOFFICIAL] [Updated June 16]

Can you point to the C.23 firmware that is a requirement for this ROM?
I don't see that in the list of available firmware for N200.
https://www.getdroidtips.com/oneplus-nord-n200-5g-stock-firmware/

Are you gonna make more updates to the core version or are you gonna focus on the gapps version now? And what’s the difference because I have the core version but there’s still gapps that can be turned off is it the same way with the gapps version? Also can I just upgrade to the gapps version?

can you use the same method as lineage upgrade os method to sideload this from los 19.1?

talejandroamazom said:
can you use the same method as lineage upgrade os method to sideload this from los 19.1?
Click to expand...
Click to collapse
No lineage 19.1 is based on Android 11 stock firmware. You have to upgrade your stock firmware to Android 12 before flashing this build.

Curiously said:
Are you gonna make more updates to the core version or are you gonna focus on the gapps version now? And what’s the differencek because I have the core verbutpj butpj thKeepere’s still gapps that can be turned off is it the same way with the gapps version? Also can I just upgrade to the gapps version?
Click to expand...
Click to collapse
GAPPS version is the only one I'm supporting now (it just has a few extra apps installed).
The "Core" version was using flags for minimal GAPPS functionality. Builds without GAPPS would have been labeled "Vanilla" if I would have made it. I figure there's no point in supporting GAPPS and gappsless builds when GAPPS is easily disabled within the ROM.

zm55 said:
Can you point to the C.23 firmware that is a requirement for this ROM?
I don't see that in the list of available firmware for N200.
https://www.getdroidtips.com/oneplus-nord-n200-5g-stock-firmware/
Click to expand...
Click to collapse
I'm running these builds TMO C.21 firmware. C.23 specifically is not required, though that is what the vendor blobs are based on.

Travisholt92 said:
No lineage 19.1 is based on Android 11 stock firmware. You have to upgrade your stock firmware to Android 12 before flashing this build.
Click to expand...
Click to collapse
thanks, also i flashed it and did everything right but when i boot in the touchscreen wont respond, is there something to fix this

talejandroamazom said:
thanks, also i flashed it and did everything right but when i boot in the touchscreen wont respond, is there something to fix this
Click to expand...
Click to collapse
Which stock firmware version are you running?

Travisholt92 said:
Which stock firmware version are you running?
Click to expand...
Click to collapse
c.23 de2117

talejandroamazom said:
c.23 de2117
Click to expand...
Click to collapse
Did you flash the "copy-partitions" zip in recovery to make sure the c.23 firmware is on both slots?

Travisholt92 said:
Did you flash the "copy-partitions" zip in recovery to make sure the c.23 firmware is on both slots?
Click to expand...
Click to collapse
yes i did

talejandroamazom said:
yes i did
Click to expand...
Click to collapse
Can you get a logcat and email it to me @ [email protected]
USB debugging should still work on first boot without enabling it in dev options.

talejandroamazom said:
yes i did
Click to expand...
Click to collapse
Also, could you test to see if you have the same issue with LineageOS 20 or Pixel experience? Both of those are based on the same firmware.
I occasionally encounter this issue in recovery but haven't had it happen in the ROM

Travisholt92 said:
GAPPS version is the only one I'm supporting now (it just has a few extra apps installed).
The "Core" version was using flags for minimal GAPPS functionality. Builds without GAPPS would have been labeled "Vanilla" if I would have made it. I figure there's no point in supporting GAPPS and gappsless builds when GAPPS is easily disabled within the ROM.
Click to expand...
Click to collapse
Can I convert to the gapps version from the core? Or do I have to factory reset?

Curiously said:
Can I convert to the gapps version from the core? Or do I have to factory reset?
Click to expand...
Click to collapse
You can dirty flash

Travisholt92 said:
Also, could you test to see if you have the same issue with LineageOS 20 or Pixel experience? Both of those are based on the same firmware.
I occasionally encounter this issue in recovery but haven't had it happen in the ROM
Click to expand...
Click to collapse
wait forget it it works! i forgot to sideload the zip file and i thought it did bc it said install complete

talejandroamazom said:
wait forget it it works! i forgot to sideload the zip file and i thought it did bc it said install complete
Click to expand...
Click to collapse
Glad to hear you got it working

If anyone is prepared to do the legwork I have a firmware flashable zip with instal scritps from my op 7 pro which could be modified to flash the appropriate firmware to a n200...replace all the partition images, change the device checks etc. I'm not going to straight out attach it because I don't want anyone trying to patch an op 7 pro firmware file on their n200.

famewolf said:
If anyone is prepared to do the legwork I have a firmware flashable zip with instal scritps from my op 7 pro which could be modified to flash the appropriate firmware to a n200...replace all the partition images, change the device checks etc. I'm not going to straight out attach it because I don't want anyone trying to patch an op 7 pro firmware file on their n200.
Click to expand...
Click to collapse
can i participate in this as a tester

Better Mobile App

welcome