yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yeah but that depends on what version magisk used, and the one you have Is the older version (very old and can be insecure so why recommend an older version). You do need riru if you want to use the latest and stable updated version. It won't work for you because you didn't install riru with the latest version, and 1.1.1 is super old but does not require riru (but again it's super old and not supported) so you should only be recommending the latest and secure version (which does need riru):
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kushman:
ok so im now at a pc about to start the procress of restroing A11 now when i go to install LOS to clear system and stuff but how do i do this with no custom recovery
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kushman:
ok i got it installed and rooted but safetynet fails i tried as said i even updated to canory with exact steps i did on protonaosp but still fails at cts profile
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kushman:
Got it all going as it should!!!!

Although it still have a very stock feel to it😒
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Right on, good work and excellent job working through the issues (on your own) and getting it to work!!! This is EXACTLY why I help here on XDA, to help users do exactly what you just did yourself! I try to lead the users to the answers but without giving them everything along the way so they learn and do it themselves. Then in turn, they can take the lessons they learned doing it themselves, and turn around and help the next user and on and on it goes. Everyone safely and accurately helping everyone else so they're safe but without issues causing data loss!

And yes, LOS is not the most custom ROM out there by design and intention. That's pretty much the entire point, LOS is pretty much a vanilla AOSP built from source code with emphasis on stability and security but less on extras (custom features/ETC). It's more for a pure Google aosp experience but without any vendor's bloat or anything from Google added, but instead aosp that anyone can build, edit/change, ETC. All for free and built from open sourced code that's publicly available, and is stable, and safe to use (because the code is freely available) - anyone can review and see the code for security. This means there can't be any surprises or back door apps/services we wouldn't know about running or installed. Instead we can see EXACTLY what's running and installed by reviewing the source code and feel safe and secure!

That's where the beauty of Android, pure sourced Android, comes into play. Because there's no bloating or extras added, it gives you the freedom to change almost anything you want to change, or modify, ETC. For example, for the custom feel and cool extras, I use nova pro (launcher) and a few LSPosed modules (running RIRU). This allows me to tweak the OS and add just enough so that it's custom enough for me. At the same time, it's rock solid stable, yet updated every Sunday with code revisions, security / bug fixes so it's enough for me to be happy as a daily driver.

All that is what makes LOS so important to the Android world. Because of LOS existing and the sources available, it's the main platform for most aftermarket ROMs. All aftermarket ROMs are is usually LOS base with custom addons added to the base, this becomes our favorite aftermarket ROMs (any ROM that says, based on LOS) falls under this. So you can see why LOS is so popular and important (even though it's not the most customized ROM out of the box). LOS gives you the stable platform to do whatever you want to do with the ROM but knowing you have a safe base running the OS.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kushman:
Right I got u I just miss pure custom stuff lol but this been good so far
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kushman:
On question when updates happen will gapps need to be flashed every time ?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
No GAPPs are maintained so you do not need to update the GAPP package with OS updates. In fact, I really don't recommend updating or changing GAPPs after you're up and running.

To OTA, you will need to restore stock kernel (assuming you changed it at some point), and either take the OTA in system, or adb sideload the ROM update. Then you need to re-root the boot.img (because it's overwritten with the update) since boot.img would be updated with the ROM as part of the update process.

I do it like this, I adb sideload the ROM update, but from stock recovery, I don't reboot to system but instead, to the bootloader then before rebooting re-install the magisk boot.img from the original build. The only caveat here would be as long as the kernel itself wasn't updated with the ROM for any reason. If that happens then you will need to prepare the (latest updated) boot.ing from the update ROM and re-root then apply.

You do NOT need to redo any magisk add-ons, modules, props, GAPPs, nothing else. This all remains working through OTA or sideload updates.

The only thing you need to change with the update is the actual update itself (meaning the OTA update) but nothing else. It's really easy and surefire:

1) revert kernel if running custom kernel before OTA

2) reboot to bootloader then recovery

3) select “Apply Update”, then “Apply from ADB” to begin sideload

4) adb sideload filename.zip (do not factory reset or erase userdata with any update)

5) reboot to bootloader once update completes

6) reapply magisk patched boot.img

7) reboot to system and done

For my own sanity, after every update, I do always recheck SafteyNet and ensure my modules worked. They always do and SafetyNet always works so it's more to calm my OCD then anything else.

If I thought about it before originally posting yesterday, I would have advised waiting until today to build it because every Sunday there's an update. This means you'll have to update today after just building it yesterday but that's a good thing every Sunday there's a brand new updated ROM!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
This goes out to everyone here in LOS and wondering the same thing, and also to specifically answer kushman regarding the custom options with LOS.

I don't think I was clear with my full explanation of what LOS is. LOS is open sourced, this means whatever cool custom feature you like or miss, can be easily added to your own LOS build, or a change here and there adhoc. What I am saying is that the custom ROMs out there (based on LOS), are nothing more than what we have here, WITH those tweaks added to the code/ROM then built into the running ROM/apps. This means you don't need to wait for a dev to build your favorite aftermarket ROM, or add/remove X/Y/Z features, instead do it yourself. Obviously I'm giving high level examples and dumbing down the process, because there is a lot that goes into building and maintaining a custom ROM, but anyone can do it.

Keep the LOS base, but change the code (or add/remove) to reflect what you are missing, or want in the ROM. This is all a custom ROM (based on LOS) is, that code plus the extra features and tweaks. It's not difficult and anyone can do it, there are forums just for this type of thing and plenty of resources out there.

I used to write my own LOS from code, then modify what I like to change. You can do it too, it's not just developers that can do it, but anyone can. I am a senior sys architect/engineer supporting a large public cloud (I run the engineering team that built it and maintains/runs it), plus I am a developer myself so I do have an advantage over the normal user, but ANYONE can do this and build an Android ROM. I highly highly highly recommend trying it yourself, there is NOTHING better then writing/building then compiling the code into a ROM and running your very own, one of a kind ROM that ONLY YOU have (because you built it).

For me, the fun has always been to learn it and figure it out then building my own 'ClarkROM' (clark is my last name), so it's just cool in my book. Then this one of a kind ROM, is unique to just me, has just the options/features only I want added, and since I built it directly from source code, I know EXACTLY what's running and installed (plus it's my own build) so how cool is that!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kushman:
I actually want to learn to port miui roms to devices I've looks it looks confusing
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Unfortunately, I am not familiar with MIUI so I can't really comment with authority (so take this with a grain of salt because I haven't compiled an MIUI ROM ever). I also have not ever installed/MIUI as my OS mainly because it was for a Chinese phone company as far as I understood so I wasn't all that trusting when it came to ROM development but assuming the source code is open sourced and available, you should be able to do it. That's based off LOS and source code compiling, but MIUI could be a different animal all together and I'm talking out my butt.

That being said, if/when I get some free time, I'll review the MIUI project and see if it's open sourced and available. If so, I will try to compile it for you (but don't hold your breath). I won't have anything ready anytime soon, but I will try to help get you going. You can also review MIUI ROM forums to get started.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kushman:
Yes, I don't think they are open source they have a patch ROM option where you need a miui ROM from a device with similar specs then need a base for device trying port so los and or any pure aosp then from there it's mainly patching a few files now I make it sound easy if was I would have done it now I don't have anything as far as a kitchen goes but I would get I want to learn tho haha
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Then I'd definitely look into compiling LOS first, and get that working. That's your first step in the process, get up to speed with LOS and compiling it. Once you have that under your belt, then you can jump to more complex ROMs like what you're referencing with MIUI.

If you can get LOS complied and your device to boot, you're halfway there. AND if you can get service (mobile/WiFi) working, you're golden, the rest will fall into place naturally. Start here and build a LOS ROM, then branch out from there:

Build for coral | LineageOS Wiki

wiki.lineageos.org
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] insestito:
Hello, any news for LOS 19 for our Pixel 4XL?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
NO ETA questions EVER (we don't want to PI$$ off the devs)! If we lose the dev, then have no one to build for us, plus its not ready LOS side yet. You are better off reviewing the LOS website for updates.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] skothiya:
Can someone tell the flashing process

Currently i'm on A12.

And Which GApps should i flash?

Sorry but i have very less experience on flashing custom rom.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
The OP has step by step Installation instruction to install this ROM.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I agree with others, follow the OP step by step and you will be fine. I would go over the steps first and make sure you understand them all, then try it. I use OpenGapps ARM64 11 NANO (and install the rest from the Play Store). Nano build (GAPPs) will give you the needed core framework plus a little more, BUT doesn't give you everything so its up to you. I like it just the core framework, so I can add just what I want Google related installed, but not everything.

From the OP:

Download the latest supported Lineage OS build and recovery (boot) image, and ensure you are on Lineage OS 17.1 or Android 11 already.

Reboot to bootloader

Flash the provided boot.img to both slots (fastboot flash --slot all boot boot.img)

Reboot into recovery and factory reset for initial install

Sideload the latest build of Lineage OS (adb sideload lineage.zip)

(Optional) Reboot to recovery again and flash gapps

Reboot to system

(Optional) Flash custom kernel / Magisk

Wiki (LOS) install:

Install LineageOS on coral | LineageOS Wiki

wiki.lineageos.org

I will help you if/when you get stuck, but you need to follow the steps and try it yourself (so you learn the ins and outs). If you get stuck, post a detailed entry of what steps you have done, what happened with each step, and where you got stuck and what happened so we can help.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
Excellent Answer

Also, if they want root they should sideload magisk- canary_23016 after they sideload Gapps (your step 6). :)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Thanks, I try to teach my team by leading them to the answer, with giving them enough to learn to fish, rather than just feed them for the day. Its my team engineering spirit spilling over into XDA (as their leader and senior sys engineer/architect). I mentor my team, all engineers - senior and not, so it tends to be a part of me in everything I do. Often go overboard trying to help and my posts become long and detailed, but it seems to help so I continue to do it :)

Also just to note, the latest ver23 stable MAGISK worked for me every time I built out LOS 11. The latest MAGISK passed SafetyNet for me with the needed SafetyNetFix, + props (and setting the first 2 options), + RIRU. + RIRU LSPosed.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Hi, all-

My new 4XL is on the way, and I'm going with LOS. Currently running a N6 with PureNexus, BTW..

So my question is, I've been seeing the EDL bricking reports, am I correct in assuming that LOS (being a custom rom) will help prevent me from the EDL bug? I'm the kind of guy that likes to get a pure, stable, smooth ROM, then not mess with it. Just looking to find advice about avoiding EDL.. Thx!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Care to share your findings on Pixel 4 XL with EDL "bricks"? I am not disagreeing with you to argue or be a jerk, but the EDL issue(s) I know of only affects the 3. No one I know of, or here (this forum thread), or heard from (user reports), has or had and EDL issues bricking a 4XL (the ROM in this forum). I use LOS A11 (this ROM) on my PX 4XL (and ProtonAOSP for A12 when I feel like it) and never had an issue. I am constantly going back and forth between AOSP/Official/A11 and A12, with upgrading/downgrading the bootloader/firmware/radio ETC between 10/11/12 firmware with zero issues (when done right).

As far as I am aware, the EDL 3 issue was a bug in code with hardware related issues that doesn't affect our devices (but I dont know the details). I wouldn't worry about it here, with using LOS or your PX4.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
That's great news! I saw one or two Pixel 4 complaints, I thought in another thread here on XDA.. They may have been proven wrong or mistaken and I missed it. I know that the VAST majority of complaints were P3 users. I'll look around and reply the original source I saw the complaints, but glad to see your response. I can live with potential battery issues, but frankly the EDL thing had me worried, lol
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Don't lose sleep over it, I found 1 report of PX4 with EDL but thats out of millions of users with custom ROMs on the PX4. Honestly, we have no idea what the end user truly did to land in that state (EDL). Anyone can break an Android device by not doing X/Y/Z properly, so just pay attention to details and you will be fine.

As I noted, I truly do upgrade/downgrade my firmware (bootloader/radio/system) all the time. I go between A10/A11/A12 to test and help out other users (on that version) so I have to match to reproduce it. I never have an issue but I am also a dev on the side so I am careful and know exactly what to do and not to do. Just read the directions and follow them and you will be safe. I always follow the steps of the ROM OP, or dev OP.

I also always use a Google FACTORY firmware of the version I plan to use (so for LOS this ROM, I would prepare by using the matched firmware for A11 that LOS uses). This keeps my device in tip top shape (by removing the old) and prepped for the new ROM OS so it works perfect.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Thanks for the advice, that's basically my plan. Its his I did my N6, and its worked well for 6 years, hoping to get the same enjoyment from my P4 on the way.. Thx!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
you will love it, I literally just yesterday (no joke) got my friend's Pixel 4 XL (brand new in box) from Amazon and setting it up for him. He is older (so not as tech familiar), and I LOVE my pixel 4 XL so I figured save him a few bucks with the 6, and keep it to the same device I have. That way it will last him a few years and because I have the same device/ROM, I can make sure no updates damage anything and keep him running (otherwise I will be helping him every day in person).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Zenjir0:
I have successfully installed LineageOS 18.1 using TWRP 3.6.0_11-0 as the boot.img and everything boots and works fine.

My question now is how do I get OpenGApps and Magisk installed? Do I have to install them via the command on my desktop machine via a sideload command?

My Process:

From Stock (A11) I push the TWRP boot.img to both A and B Slots

Boot into TWRP as if you were going into recovery mode

Factory Wipe and Format Data on the device, I do it twice for good measure.

Push the latest LineageOS build to the /sdcard/

Install LineageOS like normal on TWRP with the added check box of reflashing TWRP (if I don't the LineageOS boot.img overrides it)

Reboot into System, Lineage Boots up and goes through the New Device Startup Process.

So LineageOS is 100% installed and working.

Here is where I get confused:

I then put Stock OpenGApps 64bit on the internal storage of the device along with Magisk 23.0 APK (and it's ZIP variant)

Boot back into Recovery and attempt to install OpenGApps

Fails with error 70 which typically means that the system partition is to small. (I've tried OpenGApps and MindtheGapps same results)

However, the system partition does not appear to be mounted and I do not see an option to format it in WIPE.

I believe this is due to the nature of the Pixel 4 XL using dynamic partitions or SUPER partitions with the A/B partitions.

I don't use this device as my daily driver yet, but would like to as I believe my carrier might make my current device (OnePlus 5T) unable to make voice calls due to something about the device only using 3G for voice but 4G LTE for data.

Also if I somehow get this working, are there any dangers to using LineageOS's built in OTA updater for weekly or monthly builds? As in, will using it overwrite the TWRP boot image or remove Magisk?

I appreciate any help or insight.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
You need to install OS, then immediately reboot recovery to switch slots, then install OpenGapps (GAPPs of choice). You are asking for GAPP framework issues if you didn't reboot recovery right after OS (follow OP steps). You need to redo it properly for GAPPs to work.

OTA updates work weekly (through LOS) but ensure you are on the stock kernel BEFORE you try the OTA through LOS (for the OTA process to succeed).

You are overthinking GAPPs, its simple, when you are ready to install LOS, copy the LOS and GAPPs zip to a folder on your PC, ADB SIDELOAD the OS (ROM) from the folder, don't do anything else after the OS installs, reboot recovery, install GAPPs (adb sideload the same way you did the OS) from the same folder on PC, but don't use TWRP, use the built-in LOS recovery per OP), then boot OS and configure OS. Then if you want ROOT and/or custom recovery, reboot to bootloader and fastboot it once patched through MAGISK or if just a kernel. If you don't do GAPPs exactly that way, after the OS, but before you boot, you wont have integrated Google App Framework integrations (tie in) so redo it with the steps laid out. Use OpenGapps Nano or Micro.

Then install MAGISK (normal not beta), patch the boot.img for LOS, fastboot the new MAGISK boot.img, enable props (first two options and set to A12signatur), then enable SafetyNetFix, install RIRU, RIRU SafetyNet Universal fix, then you will pass SafetyNet. Read my steps a few notes back. You do MAGISK and/or kernel AFTER OS and GAPPs are done, and the OS booted. Kernel and ROOT are optional but are done the last step after OS/GAPPs.

My GAPP flavor of choice for LOS A11 is ARM64 / 11 / NANO and I install anything else from the play store (GCam, Google Messages, ETC).

Don't overthink it and make it harder on yourself with commands and steps not listed in the OP step layout. You don't need to push anything, ADB sideload the OS, GAPPS, KERNEL, ROOT, ETC. This is taken literally from the OP, follow it to the T and you will be solid:

Download the latest supported Lineage OS build and recovery (boot) image, and ensure you are on Lineage OS 17.1 or Android 11 already.

Reboot to bootloader

Flash the provided boot.img to both slots (fastboot flash --slot all boot boot.img)

Reboot into recovery and factory reset for initial install

Sideload the latest build of Lineage OS (adb sideload lineage.zip)

(Optional) Reboot to recovery again and flash gapps of choice (MindTheGapps are recommended)

Reboot to system

(Optional) Flash custom kernel / Magisk

Your step by step process only works for the OS, but not GAPPS, or ROOT, or kernel, so yes LOS was installed but not the GAPP (Google APP Framework) which is critical to Google Apps. You need to reboot recovery to install GAPPs then you are safe to do ROOT/KERNEL but make sure GAPPS is done correctly right from the get-go or you will feel it later on and have to redo it again properly this time (reboot recovery for GAPPs).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
To make sure I'm good and can get it done in one shot, I should be safe using the Google factory firmware that is latest on the public page, correct? I am downloading 11.0.0 (RQ3A.211001.001, Oct 2021) right now in preparation. I didn't see a verizon-specific firmware, so going with that unless you say otherwise.. Thanks again!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Don't use a Verizon (or branded) firmware for LOS (really for any device) that doesnt matter and you dont want the bloated garbage included. LOS is universal, so there doesnt need a Verizon firmware in prep, and even if there was one, you'd be flashing a verizon bloated firmware to your pixel.

Instead, open the meta file and find this line:

.zip\META-INF\com\android\metadata

post-build=google/coral/coral:11/RQ3A.211001.001/7641976:user/release-keys

RQ3A.211001.001 --> firmware needed
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] craiger27:
Cool, I learned something new (and there is a lot to learn <g>).

Looks like I'm getting the right one, so all should be good.

Thanks!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
NP! Just make sure you install LOS then reboot recovery right after OS sideload, but before you boot the OS, and sideload GAPPs or you will have issues. Follow the OP steps and it will work perfectly!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] zhouyh:
As for the lineage os18.1, Can Google photos app back up my photos without limitation?