[OFFICIAL] LineageOS 19.1 for the Google Pixel 4 XL

Status
Not open for further replies.
Search This thread

npjohnson

Recognized Developer

lineage-os-logo.png


Google Pixel 4 XL

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 Google Pixel 4 XL.

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.
  • coral - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. 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.​
  • Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.14
 
Last edited:

Matzeus

Member
Jul 24, 2021
15
1
So I just installed LineageOS 18.1 a week ago.

Let me get this straight:
In order to upgrade to LineageOS 19 i simply install the build via adb + the gapps?
No wiping or anything required?

Or can i just install your unofficial build @npjohnson via adb and im done? Because gapps are included in your version.
 
Last edited:

npjohnson

Recognized Developer
So I just installed LineageOS 18.1 a week ago.

Let me get this straight:
In order to upgrade to LineageOS 19 i simply install the build via adb + the gapps?
No wiping or anything required?

Or can i just install your unofficial build @npjohnson via adb and im done? Because gapps are included in your version.
follow the upgrade guide on the wiki.

If you installed officials, you can't install mine without a wipe first.
 
  • Like
Reactions: Matzeus
This ROM is AWESOME! The only hiccups I hit early on was now playing was failing to start, with WiFi failures and not seeing my internet either WiFi or mobile and wouldn't start. I just clicked the WiFi button from within the now playing and joined my non 5G WiFi and it popped on and immediately started the DB download and worked! Thank you and AWESOME work! SafetyNet passes with NF working, ETC, NO issues, NO bugs I can find!!

This is the LOS version with manual MindTheGapps plus Universal SafetyNetFix plus RIRU, that's what is needed for safteynet to pass. This LOS runs fantastic!


Edit note update, I'm not sure it's working yet. I'm getting the download start over and over and it hasn't picked up anything yet, but that's not unusual when not playing music.

Screenshot_20220426-173912_Android System Intelligence.png
 
Last edited:
  • Like
Reactions: SpaceTech100

npjohnson

Recognized Developer
This ROM is AWESOME! The only hiccups I hit early on was now playing was failing to start, with WiFi failures and not seeing my internet either WiFi or mobile and wouldn't start. I just clicked the WiFi button from within the now playing and joined my non 5G WiFi and it popped on and immediately started the DB download and worked! Thank you and AWESOME work! SafetyNet passes with NF working, ETC, NO issues, NO bugs I can find!!

This is the LOS version with manual MindTheGapps plus Universal SafetyNetFix plus RIRU, that's what is needed for safteynet to pass. This LOS runs fantastic!


Edit note update, I'm not sure it's working yet. I'm getting the download start over and over and it hasn't picked up anything yet, but that's not unusual when not playing music.

View attachment 5599241
its touchy - if you used the unofficial "manual MindTheGapps plus Universal SafetyNetFix plus RIRU, that's what is needed for safteynet to pass." - none of that is used here. it's custom stuff.
 
its touchy - if you used the unofficial "manual MindTheGapps plus Universal SafetyNetFix plus RIRU, that's what is needed for safteynet to pass." - none of that is used here. it's custom stuff.
Maybe so but it's what you need to do to pass safetynet but I don't think it's a ROM issue. I think it's a gapp framework issue. And no I used the official LOS method with gapps. It failed out of the box with nothing but OS and GAPPs so it's not coming from that if that's where you were going.
 

npjohnson

Recognized Developer
Maybe so but it's what you need to do to pass safetynet but I don't think it's a ROM issue. I think it's a gapp framework issue. And no I used the official LOS method with gapps. It failed out of the box with nothing but OS and GAPPs so it's not coming from that if that's where you were going.
ah, of course on official.

unofficial one passes without anything extra.
 
ah, of course on official.

unofficial one passes without anything extra.
Understood, and you will find the majority of us will prefer LOS official, vs an aftermarket, unofficial project. I like to run LOS directly with my own choice of GAPPs so I get it from LOS website and usually opengapps. That's why I think the issue isn't with the ROM but the GAPPs, I'll dig into it.
 
Last edited:

npjohnson

Recognized Developer
Understood, I like to run LOS directly with my own choice of GAPPs so I get it from LOS website and usually opengapps. That's why I think the issue isn't with the ROM but the GAPPs, I'll dig into it.
No, the issue is that this device uses hardware, backed safety net, and without patching frameworks you can't bypass that, my ROM does so, the official one cannot and will not
 
No, the issue is that this device uses hardware, backed safety net, and without patching frameworks you can't bypass that, my ROM does so, the official one cannot and will not
That's why I run the safetynet fix with riru so I can run LOS from official LOS with my GAPPs choice (usually opengapps) but they're not 12 yet. Once I'm in a safetynet pass state, everything is certified, NF shows up and the works. This is the STOCK/LOS version (which most of us will take/use) over an unofficial/personal project:

Screenshot_20220426-192551_Google Play Store.png


Screenshot_20220426-191556_Yet Another SafetyNet Attestation Checker.png
Screenshot_20220426-191812_Settings.png
 
Last edited:

htth211101

Member
Jan 30, 2021
13
0
I like the newer version of LOS. Worked perfectly on my Pixel phone. however, my device can not pass CTS profile and Widewine is still L3 even Netflix can download normally
 
I like the newer version of LOS. Worked perfectly on my Pixel phone. however, my device can not pass CTS profile and Widewine is still L3 even Netflix can download normally
You need safetynet fix plus riru to pass SN then you'll be certified and NF will work and popup in the store. I wrote it a post above your question. NF will be SD though with L3.

Everyone here, I apologize, I was tired when I wrote this the other day but I realized that I misspelled lsposed zygisk and my custom typo dictionary filled in riru for my older comments regarding riru/zygisk. Riru is the not the right term so I'm putting the magisk module list again to visualize what I meant (hopefully I didn't confuse anyone with this wording mishap).

You only need safetynetfix and zygisk lsposed (lsposed used to be riru) so that's where the typos come into play here (self corrected from custom dictionary):

Screenshot_20220430-062713_Magisk.png
Screenshot_20220430-063247_Yet Another SafetyNet Attestation Checker.png
 
Last edited:

ZeroKool76

Senior Member
Oct 21, 2014
718
424
Coming from A13 and felt like joining the fray. Is it safe to assume that stable 12 will work just as well for a base, rather than flashing 12.1 beta?

I was on 12L for a bit and I don't recall the firmware being any different, and using a stable build to flash from seems to make more sense.

Any confirmation would be appreciated.

Thank you for the build.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 8

    lineage-os-logo.png


    Google Pixel 4 XL

    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 Google Pixel 4 XL.

    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.
    • coral - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. 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.​
    • Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
    Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.14
    5
    Hey all! The final 19.1 unofficial are rolling right now.

    From here on it will be 20 builds for these devices only when it comes to unofficials.

    The device will continue receiving official 19.1 for some time, but 20 will launch soon enough, so get ready to migrate using the upgrade guides!
    3

    @xorrgnlusrx = YES, GOAL = accessing the data partition .

    (do you want to patch stock android 12 firmware boot.img ?, i can send you a12 stock firmware patched boot.img / or los 19 stock patched boot.img if that helps.)

    & Curiousn00b suggested: "Now for accessing the data partition, maybe try flashing stock but don't wipe the device. If you're still greeted with errors, you might just end up screwed and having to fully wipe." " I normally flash stock without wiping my /data/ partition when I mess something up on a rom just to recover what I wanted, then fully wipe the device for a fresh start. If you want, you can try this as a last resort. I know sometimes you just end up in a fastboot/recovery loot about how the system is corrupted and then you're basically forced to clean flash at that point.

    I found it logical, so I tried it: Here are steps performed:​

    Was running LOS 19.1 booting to requesting password:
    1. Fastbooted files FROM A12.stock.. coral-sq3a.220705.003.a1-factory-7d161018.zip
    2. Below are steps done: taken from site: (IN YELLOW)
    POST#1 - ITEM 4===>KEEP-DATA: From BOTH sites/links
    https://forum.xda-developers.com/t/guide-root-pixel-4-xl-android-10-q.3996969/
    https://forum.xda-developers.com/t/guide-root-pixel-4-xl-with-magisk-android-13.4160441/


    3. extracted zip file
    4. Remove -w from flash-all.bat and flash-all.sh (DID NOT factory reset/wipe data)
    5. Copy/Moved these files to the Platform-tools folder:
    bootloader-coral-....img
    flash-all.bat
    image-coral-....zip
    radio-coral-....img
    6. booted to fastboot
    7. batch file did not work- bcuz it gave error stating not valid fastboot and to get lastest versio of platform tools, which is what I'm on = platform- tools_r33.0.3-linux
    8. ran
    a. fastboot flash bootloader bootloader-coral-c2f2-0.4-8351033.img
    b. fastboot reboot-bootloader

    c. fastboot flash radio radio-coral-g8150-00123-220402-b-8399852.img
    d. fastboot reboot-bootloader

    e.fastboot update image-coral-sq3a.220705.003.a1.zip


    when it finishes, google starts loading, then defaults into the boot-loader.../fastboot menu.
    DURING Step "E", I ALSO get a an option to go into a "recovery" menu and step "E" fails when entered "recovery" menu.

    ?A: is this because of the non-patched boot.img in the platform folder?
    ?B: should I attempt to fully side-load the A12 stock.zip file?

    @xorrgnlusrx = PLEASE ALSO SEND YOUR INSTRUCTIONS

    AGAIN, In advance, many THANKS for any/all assistance.
    At this stage I think you are just trolling.
    3
    Put it in the microwave on high and set settings to high for 1 Minute.
    you better stick your useless head in there
    2
    Please only discuss lineage on this thread. You've talked about so much random stuff.

    I didn't grow up in the Sixties, but reading those posts with all those different colors and font sizes gives me a small idea of what an acid trip must feel like. :ROFLMAO: