yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yeah I can see it now too, it's failing on my 4XL running AOSiP but I'm sure it's just a minor hiccup for now. I have the Netflix and Disney+ latest apks saved from TiB I can share if anyone needs them in the meantime. I don't really care about safetynet except for those two apps so I can wait it out. It's funny, when I made the recommendation, it worked, now this morning it doesn't. It changes quickly
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Not yet, I've tried all the 4 and 5 fingerprints with and without basic, no change. That being said, the DUO mobile app security checks out OK though and says it passes safetynet when magisk say it fails so I'm wondering what's really going on now. DUO also checks for root and with magisk hide, it's not detected so this is definitely interesting (unless DUO doesn't really check safetynet but that wouldn't make sense since it's a security framework app).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
kdrag0n figured out what they did... https://github.com/ProtonAOSP/andro...mmit/15633a3d29bf727b83083f2c49d906c16527d389

You can find the Magisk Mod that fixes it over in the Magisk thread. There is one for Android 11 and one floating around that works on both Android 10 & 11, I believe. You shouldn't have to use MHPC after flashing it. Just make sure Magisk Hide is still enabled.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Spunkybob:
Yep, I'm passing safety net and the missing apps are now able to be installed.

When I try to add a card to gpay it says the below.

gpay is hidden from root.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
You may need the Gpay mod.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yup already resolved, thanks for the heads up though. First thing I did was backup my SD (just in case), then I FULLY removed magisk (uninstalled), rebooted, installed the latest magisk app, redid my boot.img and enabled root. Rebooted then enabled magisk hide, and installed "safetynet-fix-v1.1.0.zip" along with props (only the two modules in my second pic).

I used the new safetynet fix with magiskhide and props config (using pixel 4XL with 11 fingerprint) with basic forced on my 10 ROM and it's back to normal. Screenshot shows the date and time (right now) with safetynet passed in the background.

You may not need to FULLY remove magisk but I did so because I was testing many modules so I didn't want to confuse things or worse, use a module that wasn't needed and isn't confirmed safe (I tried a lot at first and all found on random internet searches) so I felt it safest to wipe magisk data, delete all downloaded modules, remove magisk FULLY and start over safe and freshly.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
Glad you got it resolved (y) . Yeah, you can just flash the module without having to do all that other stuff. Shouldn't even need to use props config unless you got other modules, etc. that make it necessary.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I had to use props, CTS failed until I did. I first started with just the new safetynet-fix, reboot, nope, enabled props, then set to basic using pixel 4 XL fingerprints for 11 (I'm on this ROM so 10 OS), then rebooted and it passes but not until props was enabled and configured. Other than a custom ROM and magisk, I have nothing else installed (no exposed, no custom kernel, nada) nor any other modules except those 2 (props and safetynet-fix) for modules, nothing else, and just root and magisk are installed, but nothing else.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
Ah, so it's the rom that's causing you to use props. Anyway, my main point was about the other stuff, i.e. uninstalling Magisk, etc.. You can just flash the mod without doing all of that.

EDIT: I see someone else already pointed that out in another thread.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
No I know, that was more for my sanity/security and noted it probably wasn't needed (full removal of magisk). I did a lot of testing, code revisions, and modules installed so I wanted to get back to basics so I could help others. Before I could do that, I had to first remove everything so it was fresh, but without anything 3rd party, then I started off with 1 change at a time until it worked so I could give the last amount of changes to XDA'ers as possible so it was as easy as can be.

I probably should remove that note because you're not the only one mentioning it (other forums), but the point I was making (which was probably lost because I gave to much info) was to show only what's needed (magisk hide, props, and safetynet-fix). This was needed for my setup because I'm using a custom ROM but others have reported only needing safetynet-fix with magisk hide enabled. I also required props, but not everyone will.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
New build is up: https://www.androidfilehost.com/?w=files&flid=318615

Please test and report back. Latest stock image (Jan) is required.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Who-Lep:
New build flashed successfully and no FC alerts.

Thanks!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ayed78:
phone detect as pixel 5 ?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
Yes, to pass safetynet.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
IDK about anyone else, but I'm loving this ROM (but the 10 version). It has just the right amount of extra goodies that I need in a ROM, plus the stability I need, along with the performance and balanced battery life! This ROM is amazing and I've tested all 10 and the few 11 versions available for the 4XL (plus stock+rooted 10 and 11). PD just seems to just work but without any hiccups I've found in over a week of using solely as my DD! I for one and sticking with the 10 as long as possible. Mainly because of the stability and battery life along with TWRP fully working with 10. I'll jump to 11 when TWRP works for 11 and 11 ROMs are more mature. I've tried the 11 version but I'll wait a bit before moving over.

PD is as stable as stock, as stable as DU and all other 10 ROMs. I'm glad I tried PD as I almost didn't. I didn't like the PD version for my 2XL so I figured the 4XL may be the same, but I couldn't have been more wrong! This ROM is excellent!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mingaldrichgan:
FWIW, the 1/22 build of PD 11 has been rock-solid for me! (Granted, I've only been running it for a day and a half, but still...)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Oh cool, thanks for the feedback, I'm planning to try it soon. I made a nandroid of my running 10 yesterday in prep for the test. I love this pixidust 10 ROM, so I'm not in a rush. It runs really really good.

It's amazing how well the same os can run on a pixel 4 XL but didn't run as great on my 2 XL. I almost missed PD because of it and older attempts to use it on my 2xl not going so great but I'm glad I did try it. It's been my DD for some time now and I love it!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Good call, I am trying 11 version (latest PD) now, and so far, wow, rock solid! If it all works out, I will stick with 11 PD!

Ha! I love safetynet passes out of the box, I may change the fingerprint back to 4XL, but I might leave it. Running great so far but I will reply when its all setup and running (in case I encounter any issues) but so far, so good!

-EDIT, after a day/night of 11, I rolled back to 10. Not for ROM related reasons, but because of overnight battery consumption and warm device with nothing running. This isn't a ROM issue, I know this because I fully tested it BEFORE going to bed (but ALSO BEFORE installing and configuring everything, including kernel testing), so it was cold to the touch as well as normal battery usage. Later after configuring everything, and testing a kernel, overnight I was streaming Disney+ and it started to warm up, skip ahead a few hours and it was hot so I shut down streaming and rebooted but didn't start anything. It didn't cool down and the battery continued to drop with nothing running. This means I did something in my testing after it was smoothly running so until I sort out what I did that caused this issue (my own fault, again, NOT ROM related), I will remain on the 10 PD.

My best guess is an older app that I always use in my setup that isn't compatible with 11 and caused it wakelock. I will sort it out and get to the bottom of it. AGAIN, NOT A ROM (11) issue but my own doing so don't misread this as a bug in 11, its not.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
On the 1/22 build, I'm not sure if rcs is just being weird with sticking on verifying number, or of it's just broken on PD, I'll try and get a log tomorrow, fKm, haven't had a chance today to do so.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
What is rcs?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Google "Rich Communication Services" which is the live messaging (like an apple user texting another apple user), it simply shows live typing and stuff like that (but a lot more, this is one of the features). It works for me on 11 (this ROM) using Google Messages so I suspect Google had a hiccup (which happens all the time when I am setting up RCS), but wasn't a ROM issue. I know this works BECAUSE I used 10 and 11 of PD WITH RCS working and verifying on both devices. This is a Google issue most likely and will sort itself out in time, but NOT a ROM issue! I have this RCS verification hiccup happen every few attempts on multiple ROMs including stock 10 and 11.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
Good to know it's likely just rcs weirdness
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
No worries, I always have issues with RCS. When it fails to activate, I give up and wait a few hours. It usually does it itself in the background, or I need to reactivate it then it works. Is definitely not a ROM issue though, I tested both 10 and 11 of PD and both work. RCS is active on my 10 PD right now from this mornings rebuild.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] jubeilecu:
Build installed and running OK.

Not big bugs by the moment, very smooth, nice battery life, Safety pass OK.

All working perfectly, Android Auto, Hotspot, Bluetooth, LTE, etc...

Also works three fingers gesture screenshot, dt2w, dt2s.

Some minors bugs:

Living universe wallpaper forces close if you chooses directly. You can set up anyway through Style & Wallpapers.

Other little bug, or maybe isn't, appears when you press power button and it shows the Google Home Control Devices. This screen should be opacity, but it's translucent.

Miss some features:

Always on display. I can't disable or at least i can't see the option to turning off.

Refresh Screen Rate: Same trouble. I can't see the option to force it to 90hz, even developers options.

I did clean install.

100% recommended.

Great work!!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] jubeilecu:
By the way, Rooted and magisk 100% funcional
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] heocon77:
I cant find mosion sense in rom ?, hic
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] heocon77:
and i can modify name to Pixel 4xl ?, thanks
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
It is not supported in A11 yet.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
That is possible in settings.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ryaniskira:
Can you share your Magisk patched boot image please? I tried patching the boot image on the latest Canary but it's not booting for me.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] shiftr182:
You dont need canary anymore. Use stable.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] jubeilecu:
I'm not use canary really. Stable Version works perfectly at all.

Could you try by this?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
as others said, use stable, no more canary needed and you shouldnt reuse someone else's boot.img, patch your own, otherwise you may loop. I use this ROM (10) with stable MAGISK and its rock solid.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] appro77:
Deleted.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] appro77:
I've installed the latest version of 11 and tried patching the boot image and flashing it several times using Magisk 21.4 but when it boots it gets to the lock screen and is unresponsive. I've tried both the Stable and Beta channels of Magisk.

My only option then is to go back to Fastboot and flash the original boot.img.

Any ideas?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Are you sure you are not patching the wrong boot.img, OR reusing any older one, OR someone else's? I only ask because this is the ONLY ROM I use (PD 10) as my DD (I test all ROMs but PD 10 is my go-to daily driver) as its solid! PD 10 is rock solid stable with ROOT and MAGISK working without any loops so its my go-to for stability and performance! I also want to point out, you are posting about 11 issues in the PD 10 forum, so I am not sure if you are somehow using the wrong boot.img (possibly from an 11 ROM) and trying it on the wrong OS-level (10 vs 11) or if its just the process used.

The latest MAGISK (stable) works without an issue so its either the wrong boot.img used, OR the process along the way got messed up. If you use the last 10 PD ROM, with the boot.img pulled from the 10 ROM, then freshly setup 10 Android OS (or 11 if using 11), then patch the boot.img from the SAME OS and boot.img pulled from the zip used to install the ROM with the same MAGISK installed into that ROM, then ADB and boot from the newly patches boot.img, it will work. This I promise you, but dont use anyone else's boot.img, or any other boot.img EXCEPT the one for the same ROM made by the SAME MAGISK installed under the running Android OS.

It WILL loop if you use someone else's, OR the wrong boot.img, OR you do not use the same boot.img made from the same running OS you just installed. What I mean by this is simple, EVERY TIME you rebuild the OS, make a new boot.img (from the ROM install zip) and patch that .img to the SAME OS you used to make it with (meaning dont reuse an older one or one made from the SAME OS but at an earlier time). ONLY make it with the SAME OS you plan to use it on, otherwise I have also had loop issues, it wasnt until I figured out that MAGISK needs the same boot.img it patched from the SAME running OS and not an older one, or someone else's. Basically what I am saying is do not take shortcuts, make a new boot.img and patch it on the same running OS as you plan to be ROOT'd and running with. Make sure to go through the setup first (Android), then install MAGISK, then patch a fresh boot.img, then ADB it and boot, and it will work, but only if you do it right without any shortcuts.

If all else fails, explain your install process of the ROM, then GAPPs (if using GAPP-free), then explain the MAGISK and ADB process so we can sort it out, but if you do what I laid out, it will work.

--EDIT, one other thought that popped in while reviewing your post notes, is KERNEL. Are you using 3rd party kernel? If so, try it without the kernel and use the stock built-in kernel to see if you can rule that out.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] appro77:
Thanks for the detailed reply. I ended up giving up on 11 because I found bugs like the dialer not hanging up a call. That was enough for me to get rid of it as unreliable. I then tried to install 10 again by first flashing the Aug 20 stock firmware and then installed PD10 using the links at the start of this thread.

I had exactly the same issue as the first time I tried to install. The install got halfway through and then gave an error. I can't remember the exact error that was shown in the command window. I should have written it down. The phone definitely wouldn't boot. At that point I gave up for now and flashed stock and rooted it with Magisk no problem.

I'd like to give PD 10 another try because I really like the look of what I saw when I had PD 11 running. Unless I've done something wrong when installing 10 I'm not sure how to get it installed, given that my previous 2 attempts failed in exactly the same way.

Should I be flashing the Aug 2020 stock image and then using the links to the rom zip and boot image at the start of the thread as I have done on my previous 2 attempts?

Edit: It wasn't a slot problem because.....

fastboot --set-active=a or fastboot --set-active=b didn't help it to boot.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
The easiest way to know what firmware to use (assuming its not in the OP), is to open the ROM zip, go to META-INF\com\android and read this line"

post-build=google/coral/coral:10/

QQ3A.200805.001

/6578210:user/release-keys

I highlighted the important lines, then go to the official Google firmware page for the device, and find the matching firmware. This corelates to:

10.0.0 (QQ3A.200805.001, Aug 2020)

I dont think thats your issue though, I think its either kernel related, or you are not patching the boot.img from the same OS you are using, with the same MAGISK installed in the OS. That's the only time I get bootloops, when I do not make a new and fresh patched img . FROM the same installed OS running the MAGISK installed FROM that same OS you plan to ROOT (meaning do not use anything other than the boot.img made from the SAME OS you installed, using the right boot.img from the zip).

You also didnt really answer my questions about install steps and processes used, so I am best guessing based on what you did reply with. If you follow the OP steps to a T, it wont fail, so I am confused what failed, where (halfway through), is that MAGISK, the OS ROM, ETC?

Do this, extract the payload.bin from the PD 10 ROM zip, then use python to extract the boot.img from the SAME PD ROM zip used to install the OS, thats what you patch in MAGISK. THEN take that NEW boot.img (from the original payload) install within MAGISK, select patch, select the boot.img you just extracted using python (payload dumper), then ADB that to the boot. Thats the right process and anything else isnt stable.

This isnt a slot issue so I wouldnt expect that to solve anything. I suspect you arent using python to extract boot.img using the payload dumper scripts (since you didnt note that anywhere but its CRITICAL), then using that dumped boot.img (from payload script) and using the installed PD 10 ROM, install MAGISK and patch that and ONLY that boot.img within MAGISK (once its installed and running in the OS). Its kind of critical you know what you're doing, reach out if you need exact steps and more help.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] appro77:
Thanks for your detailed reply. The issue that I was having with PD10 was getting it installed. I wasn't trying to root it with Magisk because I couldn't install the rom, let alone try to root it.

I followed the procedure at the start of the thread to install the rom i.e. Installed the Aug 20 factory image, flashed the downloaded boot image from the link at the start of the thread, fastboot erase data, then sideloaded the rom linked at the start of the thread. The sideload failed at 47% with an error.

I let it sit for a while because I think I read somewhere that the 47% thing can be a bug. It wouldn't proceed any further though and PD wouldn't boot.

I tried the whole procedure above a second time, starting with flashing the Aug 20 stock image, but I ended up with exactly the same result.

As I mentioned earlier when I did all of the above with PD11 it installed fine with no issues. It was only when I tried to root PD11 with Magisk that I had problems. I then found that the dialer seemed to be buggy so I have now flashed back to stock and rooted that so I can use Skyvalex.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] appro77:
Thanks for this info. Battery life looks incredible. So after installing stock Android 10 I need to install a kernel before installing TWRP? Can you elaborate on which kernel to use and how to install it? I've used ElementalX before and just installed it with the ElementalX Manager.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yes the battery life is amazing, that's one of the main reasons I'm on PD 10, but know, I use the native, built-in kernel that comes with PD and I disable all apps that autostart but are not needed (like games). This keeps the background free of running rogue apps stealing precious battery life. 4.14.191-unicornblood-pixel4-q is the kernel that's installed by default.

EX used to be my only go to kernel, but with PD 10, I had weird issues using EX originally and I haven't been back to EX. If you use EX under PD 10, I cant comment if it works or not so user beware. Kirisakura DOES work for 10 but don't go higher than 5.2.6 (last 10 kernel release before rebasing to 11). I left the default PD 10 kernel in my daily driver though and its awesome.

For stock 10 to use TWRP, EX kernel worked though (so once you revert to stock 10 firmware, ROOT IT, install EX kernel or Kirisakura), boot TWRP, factory reset, then install PD 10 with GAPPs and boom, you are done.

---NOTE if you have issues with TWRP going black, or rebooting to BL, boot stock firmware again, download the Kirisakura kernel 2.5.6, open EX app again, go to tools, then flasher, and install Kirisakura 2.5.6 kernel, this will remove EX kernel and replace with Kirisakura kernel, then reboot to TWRP again (ADB TWRP.img). This should work, I was able to get TWRP running with EX kernel a few times, but I found Kirisakura was far more stable. EX went black when booting TWRP a few times whereas Kirisakura seemed to always work, so its up to you, but either way ROOT and EX app will be the easiest way to get the stock firmware prepped, sure its more work, but its the best, sure-fire method I found (and I tested all sorts of scenarios).

This is the exact process I used to install PD 10 weeks ago and its STILL rock solid! The only time I move from PD 10 is to test other ROMs for users, but this is my go to ROM.

NOTE you do not have to ROOT the stock firmware, but it makes it much easier to install EX kernel from the app so its up to you but its not a requirement (if you can get the kernel installed without ROOT or TWRP).

This is how I did it:

-Revert to 10 firmware with -w (after backing up everything)

-Run through stock firmware setup, skip most things (I only setup G account for store)

-Install EX app from store (or from another location)

-Install MAGISK app

-Root (using the STOCK firmware boot.img), patch in MAGISK, boot patched .img

-EX App kernel --> install kernel (leverages ROOT to install EX kernel)

-Boot TWRP

-Factory reset

-Install PD 10

My device says it averages over 1 day but really I get 2 to 3 especially when I'm not doing anything but phone, text, or email. Even when I'm playing games, it still lasts pretty decent, yes it sucks battery life if I'm playing resource intensive games, but otherwise, it idles forever. This wasn't out of the box though, remember what I said about rogue apps running on their own in the background, those have to be controlled to get the best battery life, same as wakelocks so get a decent app manager to handle them:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] appro77:
Thanks for the instructions. Much appreciated! I won't be able to get to it for a few days, but when I can make the time I'll give it a go and report back.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
My pleasure! Let me know when you're rocking PD 10! I bet you love it so much, that you remain on it for the foreseeable future!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Delete, sorry, wrong forum