yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I was able to get it to work by making sure I waited the 20 seconds each time, (if it failed). When I didn't wait or do the captcha correctly, is when it failed (EVERY TIME). When I first tried, it error'd same as you report, but if I refresh the download page, then wait the 20 seconds, then do the captcha, click the pics, then OK, then the DL link worked but that captcha hiccup is KEY to success.

I just did a fresh test, waiting 20 seconds, then confirm captcha, and both ROM/BOOT DL (here is a pic and date showing right now). The CAPTCHA IS CRUCIAL and the KEY issue:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Adding on to the download thing...

The speeds aren't the best, but I'd recommend downloading the boot IMG first maybe since it's a smaller file, then download the rom.

Through my experience, I've noticed that the boot.img never downloads if the rom is being downloaded simultaneously. One has to be downloaded fully before downloading the other to avoid errors.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Xdevillived666:
My damned phone just updated itself to a12 stock ?! Anybody else have this happen?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
HUH, how would that be possible without allowing an OTA to official firmware but no, didn't happen here. I'd wait a few and see if anyone else reports anything but that should not happen. I didn't dev this ROM so I can't comment on the update source, but I'd be shocked if that caused it. More likely an issue somewhere in your device, and possibly wasn't cleaned properly so the secondary slot took over.

Fastboot and change the slot to opposite of what's set now, then reboot and test/confirm. You might have just switched update slots (which is how Google intended updates). They apply to the secondary slot, then on boot, applies the update and runs from that slot. I'd definitely check if you switched slots but your original descendant ROM is still there, working, but lying in wait thinking the other slot is primary.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Xdevillived666:
Think I found the culprit. Sev settings, allow automatic OTA /install on restart . Fml
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Dev options always have that by default, BUT you can't get an update without seeing it in the background (before you reboot). So I'm not convinced yet that's what happened.

Have you rebooted to BL, switched to the other slot and reboot? Chances are that's your only issue and assuming you didn't touch /data, means it would return back to normal. I truly suspect you're only running the STOCK firmware on the opposite slot, but you can manually change back to the other slot. You should REALLY REALLY REALLY check and test that NOW before you lose anything.

Plus, if that's NOT the cause, reboot to BL, swap slots back, and undone. You're risking your data and OS if you continue down the path you're on but not checking the simple slot boot order. What you say happened REALLY sounds like nothing more than an update swapping slots but stock is on the other slot so you're booting that stock slot.

If you need help, IE code/syntax, let me know and I'll walk you through it but it's as easy as can be and won't take more than a minute to do, test, and undo if needed.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Xdevillived666:
I don't have a PC by me atm. Will have to change active partition once I'm home
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
cool, I would almost bet my Harley on it that's the cause (UNLESS UNLESS UNLESS) you SAW the updater in the background working, and didn't note it. I doubt it, because you'd notice it. That being said, a slot swap happens time to time, and resembles what you noted (stock OS from an upgrade coming from 3rd party custom ROM). That's technically not possible unless the dev coded the Google OTA service (which again, I don't think is possible), bit it might be possible (IDK, never tried it, no need), BUT swapping SLOTs, most definitely is possible. I have had it happen years ago, and at first, I was shaking my head (Pixel 2 XL) and was like, WHAT THE HECK IS GOING ON?! It wasn't until I figured out they went to SLOT A/B for seamless updates (example, OS runs from SLOT A, updates to SLOT B in the background, then reboot activates SLOT B --> normally the SAME but updated OS), not stock.

When I prep/clean a device, I format userdata + system on BOTH slots (fastboot), then do the official Google firmware to BOTH slots (I interrupt the reboot at the end of the firmware flash) and reboot to BL, then do the factory firmware on the other slot. This not only cleans sys/data, but ALSO forces down the firmware to BOTH partitions (SLOT A/B) so its always cleaned and ship shop shape!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Xdevillived666:
slot swap didnt help. it has indeed been updated
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Then you def would've/should've seen it, IDK but that's not usual, normal, or anything I have ever seen before (a true move to an official firmware from 3rd party ROM) and not have data colliosion issues everywhere (FC apps, missing data, data corruption, ETC). Are you dead sure you changed the slot from A to B, or B to A? Regardless I would test BOTH slots again, set slot A as primary, boot, if still stock, reboot to BL, set B then boot, if its still set, IDK what ya did, this never happened to me from descendant (but I dont EVER take an OTA), I do them ALL manually and flash the ROM, but not OTA update so who knows, maybe I am dead wrong and there was missed OTA setting in the code the dev missed.

I wont speak for him, but I cant help if you are now on stock. If its truly stock, rollback, wipe, flash ROM and start over and don't use OTAs anymore. Personally I would backup EVERYTHING NOW before you lose it and I'll defer to the dev on that possiblity (descendant to STOCK from OTA), but I'd backup TXT / MMS / PICs / SDCard ASAP!!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I am back on descendant for a bit to help others (test a few things I was asked about privately), but I just noticed there is a June update (but it still shows MAy in OP) so you might not know. My ojnly point is if you didnt update (or see it), theres a 6/10 update (Descendant_coral-12.1-20220610) available. I am about to test this new ROM update (in depth), but so far, I kinda like this ROM a lot! My only other DD is LOS, but I kinda like these features so I might remain for a while.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Same her. I keep finding myself coming back. I've been able to use other mods to get just about as many features as crDroid, but up to where I want it. Everything also just works within Descendant with Balls being preinstalled(live translate, all the Google dialer features, etc).

One feature I really like is the double tap your phone gesture, and apart from that. Really makes me miss my Pixel 2 XL swipe down on the FP for notifications.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yeah I like it too but I'm back on LOS already, there were annoyance that couldn't be overcome with the current ROM so I'm back on LOS. I'll keep testing the ROM as it matures but for now, I'm back on LOS because of stability and performance.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] 93fuelslut:
What's soli
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
From Google:

Google's Soli is a purpose-built chip to track your motion on a microscopic scale. It uses miniature radar for real-time motion tracking of the human hand; it's able to track sub-millimeter motion at high speeds with great accuracy.

Short version is hardware that helps with tracking movement verses the older method of using software-based tracking.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Graciiaa:
Great resource here. Pretty much useful.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] 93fuelslut:
So it's like a fitness tracker?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] 93fuelslut:
Does Google call screener work?

What is the dnd button?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] 93fuelslut:
Shouldn't 2nd step be "fastboot erase userdata"?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
well so much more than that, its used for many things
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I always do + erase system when switching ROMs but the factory format (reset) in recovery does the same thing and most LOS steps say that instead.

DND is Do NOT Disturb
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] 93fuelslut:
Ok cool. I can live with that
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I was hoping to see the 1/4 mile drag in your sig but you dont show it?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] 93fuelslut:
Ran 156 in the 1/4. Got into boats now . 1970 twin turbo on ethanol
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
nice! I am more of a classic car / Harley Davidson guy (I built 12 over the years, first one still in HS at age 14)! No joke, I have physical pictures of them builds (even at 14), but this predates cell phones and camera (late 80s), first build was a 78 shovel, but I have had just about every model HD makes or made. On the classic car front, I am not where I would like to be, meaning, I dont have a classic car anymore, my last one was an old caddy (the ones like Elvis had), but my DREAM car, is a 69 SS Chevelle! At some point before I die, I will either buy my SS, or a helicopter (real heli), I am a pilot in training on the side (but still have MANY MANY MANY hours to go before I can fly on my own).

There's just not enough time in the day to do it all so I help with Android enthusiasts to help with my car withdrawals!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
My phone just did the same thing. Annoying
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Xdevillived666:
I had to reinstall the ROM . Did it again but didn't restart so still have the ROM,lol
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
Did you ever try to switch active slots and see if that fixed it?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Xdevillived666:
I did and it didn't work
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
That's so odd...

Mind if I ask about your install process as well as the notification you got when it did the update? Correct me if I'm wrong, but Descendant doesn't have the update thing in the settings and not sure about a built-in updater, but I know you can check for updates through it's "What's New" app.

Everything works through my testing without a problem.

The DND button they're talking about appear when you increase your DPI. If you go into your developer options and set your own DPI, it first pops up around 450-455 if I remember right. It'll be a little moon icon above your volume slider.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
I just got home and tried swapping to other slot and phone didn't boot. I had to swap back to the slot that updated over Descendant ROM. This is really strange. I didn't lose any data or phone configuration when the official update installed over the ROM. I find it really weird that it took an update and overwrote the custom ROM and phone works with no issues. As far as what I saw happen.....I got a notification for a system update for both the custom ROM and for official update, I took/installed neither, then this morning the phone had a notification to restart to complete update.....now I'm on official latest build and security from Google and not Descendant. Hopefully OP has a suggestion or fix. would hate for this to happen again.

I will be reinstalling the ROM again as I like it very much.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
you are doing something wrong, lay out your steps... many of us have updated no problem, I myself use ADB most of the time, but for ROMs like LOS, I will use OTA. Flash it through ADB just dont wipe data and you will work fine. There is a misstep in your process, you shouldnt be reinstalling every time you try to update, thats not normal.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
Update, I ended up installing Descendant ROM to both slots that way it doesn't update to official ROM again in the future. My steps were as follows, reboot to bootloader, flash boot then flash ROM through adb update. Next reboot to bootloader, swap active slots and flash boot then flash ROM through adb update. Afterwards both slots have the exact same ROM in my understanding. Is that a good approach or no?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Xdevillived666:
I think you misread what I put buddy. My phone auto updated to stock by itself. Was a long while ago. Since then I get update notific as rions for stock on this ROM but so far haven't had the issues again:+)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
nope buddy, I didnt misread, something is being done incorrectly with the updates. Use ADB and sideload them in the future, but I never had this problem EVER so IDK whats going on, but the update OTA manifest is not stock, so IDK how you could possibly be reverting to stock unless its not being cleaned properly (I.E. the inactive slot is STILL stock, thus STILL valid). I have urged from day 1 to all users to clean BOTH slots, and REMOVE anything STOCK, but I am always told its to much work, or its not worth it, but I do it, and guess what, never once have I EVER EVER EVER reverted to stock on ANY ROM, including this one, with TWO updates done already and not a single issue.

It comes down to either following whats recommended and not doing it your own ways, or living with the results... I am not trying to come off as a jerk, but there are ways to do things correctly, and workarounds.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
I had the exact same thing happen to me and I always reset to factory and wipe internal
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I know, and I am telling you guys, YOU ARE NOT CLEANING THE DEVICES right, you are taking shortcuts, and dont take OTA updates, ONLY sideload them, I have warned and warned of this many times.

Listen, dont listen, IDC, but guess what, my device is running descendant, and guess what, NEVER reverted to stock, through multiple updates (ADB) so DONT TAKE OTA if you are not cleaning the devices.

I will add this, if I ever get it to happen (but I wont) however, if I do, I will report and apologize but its not possible if this is setup correctly. Also I would recommend to fastboot flash --slot all boot /path/to/recovery.img MAGISK, so it trips both slots.

The source code is freely available, review it, and you will understand what I am trying to say:

GitHub - Descendant-Devices/device_google_coral: Dependency of Google Pixel 4 (flame), Google Pixel 4 XL (coral)

Dependency of Google Pixel 4 (flame), Google Pixel 4 XL (coral) - Descendant-Devices/device_google_coral

github.com
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
I didn't take OTA, it downloaded it by itself and installed on reboot. You seem upset. This forum is to help each other troubleshoot. We are simply sharing what happened to us. I understand it hasn't happened to you and that's great.

Personally I've never had a custom ROM even allow Google ota notifications to display. This ROM did and now I'm taking steps to make sure it doesn't happen again.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Sorry NOT upset, I hate messaging because I always sound like a jerk. I'm frustrated because I have explained it and explained it, if you follow the steps I laid, you'll never have an issue.

I'm right now pulling the manifest code to show you guys.

Can you do me a favor and explain that comment about downloading/installing and your entire overall step by step to install this ROM. Every step. And yes, I'm here to help but I can ONLY lead you to water, but not make you drink and you still haven't given me what I need to show you where it's breaking.

The fact that two users of hundreds have an issue, but I don't and many others don't leads me to one point. Most likely there wasn't a full clean and steps were skipped.

I need to know what exactly happened that led you to the stock firmware.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
No worries. I hate messaging as well. Tone never comes across properly .

My install steps are as follows.

Adb reboot to bootloader, fastboot flash boot, reboot to recovery, reset to factory and wipe, then adb side load ROM. Typically I only do this to whatever slot is active at the moment but because of what happened, I did the same exact steps to both slots. I'm thinking somehow ROM.updated and after reboot the device switched slots and broke the descendant ROM on its slot. With ROM being installed on both slots, this should not happen again.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
one key difference, I ALWAYS ALWAYS ALWAYS wipe system in fastbootD (A/B), wipe userdata, but only AFTER I factory flash the matching firmware to the ROM (metadata). I do the factory on BOTH slots and interrupt the reboot on slot A (right after it wipes user data) (factory firmware batch), I grab and hold vol down, power then reboot to BL, do the factory firmware again.

This way the system was now, not only wiped, but I wiped both slots (system + userdata), and then restored BOTH slots with the latest Google Factory Firmware. Then I go through a quick setup (skip everything), reboot to BL, wipe /system / data, boot to recovery, wipe again there, then sideload. No factory or stock left over WHATSOEVER but all of my partitions and volumes are cleanly prepared for the 3rd party ROM.

I have done it this way since day 1 of SLOT A/B, and I am always told its overkill, yet, I never have a single bug, hiccup, or unknown result so it works for me, and I do it every time I switch a ROM. Sure its a bit of work, but I rely on my droid for my kids, my career, and my family, so I cant risk not having a decent working android and I can test everything for all users, without worrying I am not clean.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
Yes, I read your setup process a few posts back where you detailed it also. I just have never done it that way and was never an issue before. It seems overkill but effective for you. If it happens for me again, I will follow your steps and go from there. Thanks
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
def let me know, and at the same time, I am making sure I am not lying by pulling the code but I have never this issue and I know two have so there's a commonality I would like to figure out so we can avoid it by telling new users what to do / not do. I pull OTA through wireshark and such, by sniffing my network originally then I tied that to the original issue so give me some time and I will report back the details.

If you have it happen again, TRY (please try) to remember exactly what you were doing, or popped up, or have installed, ETC., theres something you two are doing that the rest of us are not, thats where we need to focus.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
What I am wondering is this, did both of you ever try/use the beta, possibly beta 12/13?

/data/data/com.google.android.gms/shared_prefs/com.google.android.gms.update.storage.xml
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
For sure. What I remember is getting the notif for descendant update and also the notif from Google of an update. I took/installed neither, not through adb or ota. I know better than to take an update from Google while on a custom ROM..nonetheless, it installed itself in the background and next thing I knew I had the restart to complete update notif and phone was back to stock after that.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
that aint right at all, something is definitely misbehaving for you two, but IDK what yet.

I see in the code for betas, but I havent found anything that would point me to what you two are facing. I would also HIGHLY HIGHLY suggest, disabling auto updates on reboot in dev options, I ALWAYS have this off, so maybe thats the key (but it still doesnt/wouldnt explain the weirdness you two have with a Google firmware)..
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
well, I still cant provie/disprove with code yet, I didnt get a lot of time to dig back in today with work, and I cant find my wireshark, so I was either 420 when I did it, or I was tired and didnt save, I dont remember. I am probably going to redo the capture in time (if I dont figure it out by then), but I had hoped to prove what I said right or wrong, one way or the other (I am OK with being wrong when it helps others). Until I can prove/dirpove, I have no merrit other than my own updates experience without issue, and plus it never happned me, EVER. I was on it for 2 months one cliptesting during an update cycle (ADB), and currently now back on it, betwen releases, so I would have had the same issues if I also suffered from it. I cant prove one way or the other though definitively yet so if anyone sees or knows (or has had this happen), chime in please, lets figure this out. I still stand by my gut response, but without a way to prove through code or wireshark, its just my expierience as my facts so I would love to hear others who havent had this issue (and upgrade/work fine), OR if anyone else (other than the known two) had it happen..?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
Cool, no biggie. For me it's not about being right or wrong, just throwing into the chat what I've experienced. I didn't have it happen on first release, it happened while I was on the release before this last one if that helps. I will turn off update on reboot through dev options though. I really like this ROM the most out of all the ones out there so I'm cool with hiccups here and there. It has just the right amount of features and cool factor but not overwhelmed with gimmicky software. Kudos to the developer and to you for helping with troubleshooting on what otherwise seems to be a dying forum.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Nah it's all good, I just don't like to give information without facts and I usually have them handy, this one's throwing me but I'll get it in time. Yeah pixel 4 forums are slower, I think people upgrade/move on but I'm keeping mine until it dies or doesn't do something I need it to do. I love my pixel 4xl, I had em all so far and I buy them from Google so they're always unlocked and this one's the best of em all so far
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] QbanXpress:
I love the classics as well....seems we all have similar tastes

Im the same way but now I buy all my phones through Amazon refurb and they come.brand new and unlocked as well for a fraction of the cost. It does mean I'm always a year or two behind releases but I can live with that cause all my money goes to my car and fam 😂
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] 93fuelslut:
What's the flashing instructions? I just got my 4xl and haven't flashed a rom since a10
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Flash boot.img, boot to recovery, factory reset, then still in recovery, sideload, then push it from PC. Use the LOS instructions up to GAPPs, don't flash GAPPs, they're included. Once sideload is done, reboot to OS and setup.

I like to always flash the matching firmware and format userdata+system beforehand but it's not necessary. I wrote about it this forum or one of them with steps to clean and install so if you need more help, it's in the forums.