yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
That's the file I sideloaded. I could probably repeat the process tonight and see if that helps.

Edit: Did everything again, still getting FCs. I'd really like to avoid having to erase userdata but that's the only thing I haven't tried, and I probably won't try it. :/
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
If you didn't erase userdata then you didn't follow the steps to the T. Did you erase userdata the first time around? If it were me, I'd start over and do every step outlined (even data). If works flawless for me and others. I'd redo the March firmware with -w then start over fresh. Betcha it works and I'd definitely try it fresh and doing every step. I know it sucks wiping data but it's specifically required so I did it, and my device works fine.

You could just freeze again, true, but that's not really fixing the issue that shouldn't exist.

I know, thanks for the report, and you should be able to run it that way but something was different with the other user's setup. I was trying to figure out the difference between us to pinpoint it so I was reviewing everything possible.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
I mean to be fair, erasing user data is part of the steps specifically if you're "First time installing PixelDust ROM, or coming from another ROM", which wasn't the case here. Coming from stock I did erase it.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Right, I agree to some degree but you haven't laid out your entire setup process or what you came from prior (other than noting stock, but what firmware, what stock 10, 11 March, etc?) and how you got to a running PD from the older ROM so basically I'm guessing. If you did lay out, then I missed it but I didn't see your steps so I'm trying everything possible to find the difference. I hope you DO understand and realize that ANYTHING OTHER than coming FROM PD11 is "coming from another ROM", even stock so this IS required UNLESS dirty flashing a PD11 UPDATE (ONLY a PD11 ROM out update are suitable to dirty flash). I know you mentioned stock so I can only assumed you did everything, but I'd start over and definitely erase userdata and follow it to the letter.

That being said, the issue you face was resolved and confirmed resolved in the last update, and it was confirmed by me (twice, first initially testing the update, THEN again yesterday with a FULL wipe and rebuild from scratch) so I know 100% without a shadow of doubt, it works as it should. It was also tested by the dev, and the other user also confirmed it's resolved, only yours isn't, so there has to be something unique with your setup. That's what I'm trying to pick through and help you resolve.

Yesterday, I was done with testing scorpion, so I used the March firmware and applied manually to both slots (I interrupt the last step) which is after the erase but right before it boots into the OS (ROM). Right after it reboots (from slot A firmware finishing), I then switch to slot B and redo the firmware with -W left intact on both. That way I KNOW beyond any questions or shadow of doubt, that BOTH slots are prepared correctly, then I simply go through a quick stock OS setup and do not add an account, or security, nada, I just go through until I can shutdown. Once I'm down, I boot into bootloader, then ADB the ROM boot.img then followed the steps (with erase) to the T, then ADB sideload the ROM and setup my newly installed PD11, install my apps, and restore everything and it works flawlessly. Not a single hiccup, bug, or FC so I know the ROM itself is fine, but getting to the running OS is where we can differ so when one works (and confirmed by multiple users) but doesn't for another user (you), then we know something was done different OR installed/changed afterwards. Based on not having enough info from your setup, we are left to guess.

Again, if it were me, knowing what I know from others stating it works, I would definitely start over without a question. You can also just freeze it, but that's a bandaid solution and not really needed since it was fixed in the ROM BUT would avoid the userdata erase.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
I started with the latest February 004 factory image that I properly flashed and booted into to enable OEM unlocking. I unlocked the bootloader, and then followed the written procedure(which includes wiping data) to get to PD. I've been dirty flashing since that build with no problems until the verified FC bug showed up, then again with the latest build that I mentioned.

That is exactly why I said that this wasn't the case here and that I did erase it coming from stock in my previous post. Apologies if my wording shed doubt on when dirty flashing is "allowed". I appreciate your detail in your installation method, and the first time I flashed it I did it exactly the way you did with one difference, I did not flash both slots like you. To clarify, I'm flashing the latest boot.img provided with the rom, boot to recovery and sideload PD, then boot fully. Then reboot to flash the magisk patched boot.img. By the way, it did that thing again where it restarted mid-boot with the patched boot.img and I had to flash the patched img again to get root again. I assume something happens and makes it swap slots and boot the one I flashed before the sideload.

But in any case, I understand a data wipe is probably unavoidable, and I will do it, I just cannot in the immediate future. For now I simply reverted to the band-aid solution.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
It's weird, it sounds like you did everything right (but wipe). I'd definitely wipe data and try again, and let us know how it goes. It shouldn't be happening so I'm curious the outcome once you redo and wipe userdata. Freezing it will work as well (but we do not know what will happen with future updates and if it will work), so keep it in mind. I had it frozen originally (before fixed) and I didn't notice anything (but that doesn't mean there wasn't something under the hood). Also don't take ANYTHING I asked you as an attack or anything other than trying to understand what happened. I just wanted to make sure you understood the erase userdata comment and to help but not an attack. Over the years, XDA'ers often misunderstand my questions as attacks so I used to get into it with them but not a anymore.

I was a dev and built user ROMs a long time ago, it's in the past. I do not anymore so I try to help in other ways.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] v8088v:
Can you please helps me.

I bought an AT&T-locked device and made it free by the instruction from official AT&T website:

Unlock instructions:

1. Insert non-AT&T SIM card. The notification "SIM card isn't supported" is expected.

2. Connect device with Wi-Fi.

3. See the notification "Carrier lock removed. The device can now be used on any network."

4. Go to Settings > Network & internet > Mobile network, and confirm the non-AT&T Mobile data enabled.

Contact your manufacturer if you have additional questions.

Thanks for choosing us, AT&T

Now after factory reset I can use any sim-card and I can see that OEM-Unlock in "Developer options" is ACTIVE.

So, my question is: can install this PixelDUST ROM, root and can I flash this device by stock image for usual Pixel 4XL phone from the official google repository developers.google.com ?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
Your wording is a little obscure but from the sound of it it is possible. The process that AT&T described was to SIM unlock your device which is different from bootloader unlocking, but it's always good if you can do both. So your first step should be to unlock your bootloader. Just follow this guide to do that. Make sure your device is indeed a Pixel 4 XL(coral), and then that you are on Android 11 with the latest factory image (March 2021, RQ2A.210305.006, for coral at the time that I'm writing this), before following this rom's installation instructions.

I've never gotten into developing roms myself, but I've been in the scene for well over a decade now myself. Granted stuff has changed a lot since Eclair, some solutions like wiping data will always be a go-to xD. Of course from your viewpoint you can't know what every person knows and what they don't, and that's why I didn't take anything as an "attack", no worries.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
It should be, assuming you can unlock the bootloader and flash the firmware for coral (pixel 4XL). Assuming it's the same device, but was carrier locked but now you're unlocked (OEM enabled) then go ahead and try to unlock BL and follow the steps. Again, assuming it's truly bootloader unlocked (but not just SIM unlocked), it should work. I'd be curious to see the settings, about, and the model type returned

I cannot give 100% UNTIL I know if you're SIM unlocked, or bootloader unlocked, or both.

First step before you can even think of root or custom OS is to bootloader unlock. If that's not possible then nothing with root or ROMs will work.

SIM unlock is done by the carrier when paid off, but totally different animals so check if you can bootloader unlock.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
So I will be erasing userdata a little later tonight. I will revert to stock then reinstall from the top(and I will do both slots this time too), because this morning without me making any changes to the device a lot of my apps started crashing on launch. Apps include amazon, ebay, my bank's app, a chat app, the xda app, and others. I initially noticed it on only one app, and erasing its data or reinstalling fixed it, but after some time it started crashing again. The first time I erased amazon's data it worked for a good 5 minutes, then the second time for about 8 hours. And I just noticed now that way too many apps are affected by this.

Edit: So the FC is definitely gone, but I went through some hard times with restoring my data. Although I got my apps to install, my text messages and call logs didn't get restored, though their data is backed up on google drive. I'm trying to figure out if I can get those back.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] v8088v:
As I can see that bootloader is successfully unlocked. Now can I flash your ROM?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
Why Feb. stock image? Use latest March stock image with the latest build.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
I initially installed back in February, before the March build. I used the March image yesterday. Everything looks alright now.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Not my ROM but it looks to be unlocked, can you share a screenshot of the dev/OEM?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] v8088v:
Do you mean this OEM Unlock? It was inactive (the 2nd photo) and grey colour before unlocking the bootloader
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I cannot read the wording in the pics, but if it says, OEM unlock AND you can ENABLE it (this is super critical), can it be enabled? If so, then you are good to go and should be good to unlock BL and install PD! This setting (block) is where mobile providers prevent BL unlocks so you cannot ROOT or modify the OS. They say this is for safety but its BS (verizon sucks). Again it might be enabled but I cannot read what's there, if its enabled, then this translates to BOOTLOADER unlock and you should be good to go.

I am assuming yours says and looks like my pic, if so, go through the Google docs to unlock the BL, then follow the steps and install PD!

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Was it firmware related then? Something was different and causing the FCs, so I am trying to understand what that something was, wrong firmware would matter? Meaning, you used Feb when March was required and caused FCs but now you are not getting them when using the March firmware, or was it something else?

Just trying to understand where you are at now and if you need help still or if its good now and what the cause was (to help others who read the forums).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I only use Carbonite SMS backup (or SMS backup now I think its called). This will backup ALL texts and multimedia, to XML, and either store it in Google Drive, or locally. I then use the XML (which is the actual backup file containing all TXT/MMS and attachments), with SMS backup to restore, and never miss a beat. I have been doing this for years, through multiple revisions, multiple devices, multiple ROMs, multiple firmware, and never lose a single TXT (as far back as 2017). I own the premium license, but it works the same (or at least did, I cant confirm now because I own the license), but it works fantastic. This is what gives me the freedom (along with TiB for app-data) to test all ROMs, and never lose a message:

SMS Backup & Restore - Apps on Google Play

A simple app that backs up and restores SMS & MMS messages and call logs.

play.google.com
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
I used to do the same thing....tedious but worked. I switched to Google Hangouts for my text messaging and now I don't have to worry about all that, since it syncs to the cloud and follows me everywhere I go.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
New build was pushed. Have fun.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Awesome thanks! Dirtied the update, no problems to report at all! Running flawlessly, thank you once again!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Does it work well (hangouts) with texting (pics in particular)? I was always to nervous about text and MMS failures (which I had) in the beginning of using hangouts. Granted that was on Sprint back then (I think) AND was at least 6 years ago (whenever they released texting from hangouts). I haven't revisited hangouts since so thats good to hear. It is somewhat annoying to restore almost 10 thousand messages built-up over the years but it works really well. It just takes an hour and half sometimes (sometimes quicker but usually that long) and you can't text during that time period. You can't text because you have to set default to SMS backup so it has messaging permissions. I'd like to avoid that piece if I could so I'm interested and may try it.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
So at the very least because I was syncing messages to my PC, the Your Phone app kept them all and I found the .db file with everything on it. I may not be able to easily put them back on my phone but at least I have all the texts and images from there.

No the thing I mentioned with the February was for my initial install. I stayed with it for a month until I updated to the March build.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
I keep getting the error E:update package is older than the current build...

I have flashed the March 2021 Android 11 build to my phone

Do I need to downgrade to March 2020?

Someone please advice
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
No, March 2021 is correct. Did you already flashed a A12 developer preview before? I never had such an issue and can't reproduce it.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
Yeah, it handles MMS fine. The only issue you would have is that Hangouts NOW only works with SMS if you're using a Google Voice #. They removed the SMS support for the phone's actual # last year, which sucks. I only use my Google Voice # to make/receive calls......I don't even know my phones actual # unless I look it up LOL
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
A12 dev preview was flashed before.

But I have since downgraded to A11 March 2021 and attempted to flash this ROM. Still getting the error after the downgrade.

Boot img flashes without issue
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
We need more info, coming from 12 preview is not the issue (I was on it myself for a bit to have some fun). Can you share a screenshot, or at least tell us where you see this error (E:update package)? You DO need to go through the March firmware for Android 11 to reset and fix all partitions back to the expected PD11 ROM then go through a quick setup of the STOCK firmware (skip everything) then shutdown and boot to ADB and begin the ROM install.

Also did you try an OTA, or a FULL firmware? You can ONLY roll backwards using a full firmware, not OTA so I suspect that may be part of the issue.

Did you follow the ROM dev install steps properly, erase userdata, and so on? The only FC bug was fixed two revisions ago and is no longer an issue as long as you do it properly but I dont think that's your issue here. I have not seen an error like you are reporting so a pic would help, but if it were me, I would redo March 2021 firmware and LEAVE the -w in the script (so it wipes userdata). Where is the update package error (in ADB on the sideload), if so, are you 100% sure its using the PD BOOT.img, and not the STOCK boot.img?

Have you gone through a full firmware reset, with wiping userdata in the firmware reset, THEN again when installing PD11? You should also erase userdata per the ROM steps (as well as with the firmware update), thats just as important? If yes to all, then please explain exactly what has been done to prep (from 12) for the 11 PD install (firmware, PD, everything please). I am just giving you all the options I can think of, without having all the info so try to reset using March, then setup (skip everything), then boot the PD boot.img, nd follow the steps.

I know I am repeating myself, but its to give you multiple avenues to troubleshoot, and a lot of initial steps are identical so I tried to lay it out to help you.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Rock on, thanks for the info! I will give it a try soon and follow-up. I am on big red so I have verizon service and not GVoice. I outeright buy my pixels form Google and only use verizon for service, I cannot STAND verizon policies so I wont use their garbage locked devices (sorry ranting on big red, I hate them so I tend to blast when I can).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
- I get the error at 47% of the way through the installation before the error.

- I have only done a factory image downgrade to A11 from A12, not a full OTA image downgrade

- I have set up the stock A11 rom, ADB is enabled and working

- I performed a factory reset from fastboot after installing the boot img as indicated in the install instructions

- I am using the PD boot img

The steps I am taking are:

1. Boot to fastboot

2. Flash boot.img

3. fastboot erase data

4. boot to recovery

5. adb sideload
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I think I misread you, you did this factory image with the -w left intact, correct?

https://dl.google.com/dl/android/aosp/coral-rq2a.210305.006-factory-82bad63d.zip?hl=ru

From the install process, are you dead sure, its using the PD boot.img? It will error if using the stock boot.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
That is the reset that I did but I do not know what you mean by -w. I downgraded using the official google flash tool.

Also, 100% sure that I used the PD boot img
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Inside the batch file (flash-all), users often remove the -w to prevent user data erase, but sounds like no, you didnt:

fastboot flash bootloader bootloader-coral-c2f2-0.3-7062597.img

fastboot flash radio radio-coral-g8150-00082-210106-b-7065218.img

fastboot -w update image-coral-rq2a.210305.006.zip

Can you get a pic of the error so I can at least see it? Based on your replies so far, it sounds like you did everything so something is off but IDK what yet. If we cannot figure out whats up in the process, we need to shift to ADB , drivers, and cables, but I doubt thats the cause either.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
At 47% of the way through ADB sideload of ROM I see the following errors:

On my cpu

-adb: failed to read command: No error

On my phone:

E: update package is older than the current build, expected a build newer than timestamp 1616602095 but package has timestamp 1615673047 and downgrade not allowed.

Install from ADB completed with status 1.

Install aborted.

Only things I can try doing are

1. Try using another cpu

2. Downgrade to A10 and re-attempt

3. Flash lineage and try to flash PD next

EDIT: Redownloaded the PD ROM now getting this error:

E: failed to verify whole-file signature

Update package verification took 84.2s

E: Signature verification failed

E: Error 21
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] shiftr182:
Flash the factory A11 image twice. Flash it, let it boot, then flash it again. You need to have it on both slots. You still have 12 on the slot that you are trying to flash the rom on.

When you flash it after being in 12, it only flashes to the slot opposite of the one 12 is on (unless you flash it twice), then when you install the Rom it flashes to the slot with 12.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
Looks like a bad download.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
That's a very good point and why I always recommend to flash the factory firmware to both slots. That's probably why I can't reproduce it myself. I always reset both so it just works fine and why I didnt think of it, I assumed everyone was following the same process that works flawlessly. If you need it, its a few posts up, but simply stated:

Switch to slot A, go through the firmware reset with -W, and after slot a completes the firmware and right before it reboots (it wipes userdata) get ready to grab power+volume up and interrupt the boot to OS. Then switch to slot B, and repeat.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
That last error you got there, verification failed, could be a result of not flashing the boot.img before side loading. Happened to me since I booted the boot image accidentally instead of flashing it.

On a sidenote, any chance to fix this? In this rom, instead of showing " O' " it shows " Oh ".
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
LOL that's a funny clock bug 🙄 and I'd agree it could be the wrong boot.img but the user said it wasn't (twice) when I asked the same thing, so IDK anymore. All of my troubleshooting steps didn't seem to help so I'm hoping this user factory resets BOTH slots. Then tries again and it's successful.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
I've kept trying multiple different versions of the ROM. But still getting the error update package is older than....

Here is the screenshot of how I've flashed the March 2021 A11.

The first time I flashed, I did not click "force flash all partitions"
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] TyWillems19:
Just getting back into the root scene, and this is my first custom ROM loaded onto my phone in more than 5 years. I am very happy so far, great functionality, and I really like the customization options that are baked in. Lot's of things included that I missed from having a rooted phone.

Quick question, does this ROM have built-in incognito hotspot tethering? You know, so Verizon can't distinguish how my data is being used. Or should I download an app for tethering purposes? Any suggestions on that app if so?

Thanks in advance!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
Not upset at all, I have really appreciated your help. Since I haven't been able to downgrade successfully using the ADB method I'm just going to wait until the PD based on android 12 comes out or will continue to attempt to flash the A11 PD updates.