yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Eudeferrer:
find it in: System, Developer Options (which must be enabled first by clicking 5 x's on the "build number"), almost towards the bottom find "Display Cutout" and click on "hide".
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Hey xda, just wanted to share that turning on the smart pixels option under the custom configurations page in settings disallows other screen overlays(draw over app) function.

If there were to be someone running into a situation like being unable to grant an an permission to draw over apps.

Check to see if the smart pixels option is ticked on:svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Samuel Holland:
CrossHatch_#1

Wow, what a nice job on this ROM. Thank you very much for supporting our device and sharing your work. It sure is really nice to have Havoc 3.0 up and running instead of just stock. This is sincerely appreciated!:)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] peconaut:
Does the hide pushes the display down like stock or just add a black cover like nacho notch
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] OrzBus:
Unfortunately it resizes the screen in a way where the top of the display is under the notch... Basically resize
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] naimi5885:
please help me,after i use this rom,i charge this phone only stop 80%,if i off the phone can full charge.How do i fix it??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Are you sure you don't have Accu​Battery running with the default limiter?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] naimi5885:
i dont use anything app,just normal use,charge stuck 79%,i off phone,charge normal up

---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------

i dont use anything app,just normal use,charge stuck 79%,i off phone,charge normal up
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Gotcha. 80% was just too similar of a number. Is this your 1st flash of Havoc? If this just started on 1st Havoc flash, I would start back over with factory install x2, etc. If this is new just to the latest build, do a dirty flash of the same build in case. Either way, I wouldn't do anything (root or kernel) until after you test after the final boot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] naimi5885:
yes 1st flash of havoc,i flash latest build 23.11.1019.do a dirty flash means boot.img again and flash zip again right?no wipe data? and can i flash this kernal "[Kernel][05.12.2019][4.9.205] Kirisakura_Q 1.3.0" is stable for havoc and root my phone?sorry for my bad english.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
=============================

Havoc-OS v3.0 Official Update

Android 10

=============================

Date: 12-06-2019

Device: Pixel 3 XL (crosshatch)

Maintainer: [MENTION=307183]stevepro[/MENTION]ski

Changelog: https://t.me/Havoc_OS/1689

Download Links:

• ROM: https://bit.ly/2qw25v0

• Boot image for flashing zip: https://bit.ly/33XjrOZ

• Merged December Security Patch

• Added Edge lighting

• Added Data Switch QS tile

• Added translations for TextClock

• Added toggle to hide arrow for back gesture

• Added more sounds from Pixel

• Updated sounds from Pixel 4 XL

• Improved Small mobile type icons

• Improved HD VoLTE icon toggle

• Improved Partial screenshot

• Improved Brightness Dialog

• Improved QS tile size and padding

• Improved Bluetooth battery level icons

• Improved Fingerprint settings for devices with FOD

• Moved Notch Cutout settings under display

• Moved Custom DP settings under display

• Fixed DnD icon margin in Volume panel

• Fixed Bluetooth battery level

• Fixed Heads Up in Gaming Mode

• Fixed NavBar layout preference
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Yes, a dirty flash in this instance is everything except wipe data. As for the kernel, this ROM already had ElementalX merged into the install. I have been using ElementalX for years, and it is perfectly stable including on this ROM of course since it is included. I've never used Kirisakura, though I am sure some folks might have a reason to choose it. Since any of the benefits of a custom kernel are already taken care of, I would stick with the included one. Rooting is the same as stock except you use the boot .img that you use during install of Havoc to patch in Magisk.

Since he just put out a new build, it might be a good time to start from scratch installing the stock December build to both slots first. Just my $0.02.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Is anyone aware if the squeeze feature will be considered for addition to this rom ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] naimi5885:
tq very much,i will try it
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Zzoro:
I flashed boot.img and now can't get into Fastboot to install this build because of "error boot prepare". Didn't have this issue with the previous builds.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
No problem. I dirty flashed a couple of hours ago, and it's running perfectly coming from the last build.

---------- Post added at 01:25 PM ---------- Previous post was at 01:22 PM ----------

I flashed a little while ago with no issues? Did the boot.img flash 'OK' in command prompt? Also, did you hash the boot.img?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Zzoro:
I updated platform tools for OS X, flashed the December factory image in both slots, then successfully flashed the boot.img from Havoc and received this error when try to boot into Fastboot (to sideload this build). Then I flashed Magisk patched boot.img and this error gone away and I could boot into the rooted system, so I thought then that the problem may be connected with the boot.img from Havoc.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
OK, I admit I am confused by this message. When you mentioned previous builds, I thought you meant you dirty flashed from the previous "weekly." You mentioned updating Platform-Tools for OS 10 which has been out for months, and even the current platform-tools has been out for over a month. So what rooted system are you in after flashing a Magisk patch, and what Magisk Patch if you couldn't sideload today's Havoc?

---------- Post added at 01:50 PM ---------- Previous post was at 01:45 PM ----------

Thanks so much, [MENTION=6864870]slothdabski[/MENTION]. Been up and rooted for a couple of hours with no issues. Huge thanks for getting the apps that just show up as app info hidden. Still gotta use a custom launcher to hide pro app add-ons that install separately of course. Was the ElementaryX base from last month (2.08)? Was that on purpose, maybe a merge? I updated to Dec 2 2.09 with EX Manager with no issues?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Zzoro:
I did the the dirty flash of december`s factory image over the Havoc-OS from 11.30. When I failed to boot into fastboot with the boot.img offered by Havoc-OS I flashed the patched boot from December release available here and now I can boot into the stock rooted system whit all the apps previously installed. I tried several times to flash boot.img offered by Havoc and boot into the fastboot to sideload the latest build but always receive the mentioned error. I mentioned Platform tools only to show that the problem can not be in the soft that I use to flash boot.img,
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
That makes more sense, but it still sounds like a corrupt havoc (crosshatch) boot.img. Did you try flashing it to both slots (you should't at that point)? Does it match the hash MD5: 666018e3aa9650b2fd93848b384f21be?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Zzoro:
Yes, the checksum is correct and I flashed it to the both slots and tried to change the actives but with the same result. So I think that the problem may be connected with the Decembers factory Image. May be I should not flash it but should sideload the latest build over the 11.30 build without updating the factory. Tried it again but get the same errors. In Bootloader: Enter reason "error boot prepare", in the same time in Fastboot "Failed to boot into userspace fastboot; one or more components might be unbootable."
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
To be sure we are saying the same thing, the initial flash of boot.img during Havoc should NOT be flashed to both slots. The device is in a hybrid state in the slots during an OTA. It is only after it completes that you can flash magisk_patched to both slots.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] twcobra:
Have you tried Android Auto. I am hoping that is working now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Zzoro:
I did some tests, so I flashed the November`s factory image then the Havoc`s boot.img after that I succeed to boot into the Fastboot for sideload the latest Havoc`s build. After that I tried the same with December`s factory image and can't boot into Fastboot. So, I think the the boot.img offered by Havoc have some issues with the December`s factory image.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
I have not. I never cared for it despite giving it a try numerous times when it was part of the stock build in the 1 and 3 series both. My vehicles have always handled things better (or at least in a way I was used to). Once it quit loading by default, that was the end of my experiments. I also remember reading that they were going to sunset the phone app of AA, and that it would only live on Android supported car nav systems. Not sure what ever happened to that.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] djcrystals:
I'm having the same issue. I've never had this issue before. I can't boot into the fastbootd mode. I've been messing with this for an hour. I've been using different boot imgs too.......it makes no sense.

It's something with the Dec Stock update....that's my guess.....but i worked all day and I'm tired and retarded, so I dunno.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] OrzBus:
I had a hard time flashing my magisk patched boot.img... so what i did since i was already on havoc, i flashed the updated boot after updating the ROM. Then i did "fastboot boot magisk_patched.img" qnd once booted into the OS i went into magisk and reflashed it since flashing the boot wouldnt stick.

In short i did...

1) adb sideload havoc.zip

2) fastboot boot magisk_patched.img

3) opened magisk app -> flash magisk

4)reboot
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
If you have a magisk patched image then just flash it directly in fastboot

fastboot flash boot magisk_patched.img

and you're set!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] naimi5885:
My phone all normal now,i want ask if i flash Kernal ElementalX 2.09 latest,with latest build now stable or not? and root.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Zzoro:
Magisk patched boot.img doesn't allow to flash unsigned rom zip so it won't help install Havoc-OS from Fastboot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
I have been running 2.09 rooted for over 24 hours without issue.

As for the folks with fastbootd issues, I simply do not know. I never was on December stock (even just to get both slots installed), so if that was the issue I wouldn't have seen it. The last full flash for me was the one right before the November image came out. Only dirty since then.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] PtN009:
im getting no simcard detected.

what should be done.

so far i have tried replacing card, card works on other phone.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] djcrystals:
After some digging I've found other people are having issues with stock Dec too, in some of the other threads. Nov worked fine.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Funny, I was never even on stock November. My last clean flash was Nov 2 I think (so used the October factory image to install the two slots). It was the last mandatory one on Havoc.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] djcrystals:
I flashed back to Nov and everything worked. I am curious what changes were made in Dec....
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Strange one for sure. I seem to remember another time recently where updating via dirty factory image (minus -w) or OTA was fine but completely fresh was not. Something that stayed in place month to month but was written fresh with a new image. I'll be damed if I can remember what it was though since it didn't impact my P3 or P 3XL
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] OrzBus:
This only works if already on Havoc... And had no issue at all flashing new havoc build directly without flashing new boot.img. i then flash the boot img second
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hawki:
Initial install

Wanting to install this for the first time. Coming from original crosshatch rom (Nov's) looking at the OP and it said install into both slot. Install what into both slots? patched boot image? original boot image? Step-by step instructions would be appreciated unles im just missing something.... TIA :confused:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
https://xdaforums.com/showthread.php?p=81014567
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] atrix2man:
I've been away from xda for a little while now and I've got some catching up to do but I have a question. I followed the instructions, flash boot.img and flashed havoc with the patched stock recovery. It was successful but I don't see havoc settings in the settings tab. Any help would be greatly appreciated.

Edit....fixed it. Great rom keep up the good work
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Sounds like you need to flash factory image to the opposite slot you had stock on. The havoc zip flashes to the slot opposite your current one, and if that slot has never had an Android 10 factory image installed to it, it'll fail to boot and switch back to the slot with stock
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] atrix2man:
Yeah I went back and redone the process and it was successful. I'm a little rusty on the pixel 3 xl. Thanks for the info ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] RegnierD:
I too experienced issues when attempting to enter fastbootd to sideload the Havoc zip. Followed same steps I always do.

1. Reboot to bootloader
2. Flash December factory image then reboot to bootloader
3. fastboot set_active other
4. fastboot reboot-bootloader
5. Flash December factory image again then reboot to bootloader
6. fastboot flash havoc_boot
6. fastboot reboot fastboot

This yields the boot error. At this point I am on slot b. Slot a is able to access fastbootd, but it's the unpatched image and doesn't allow for flashing non-Google zips.

Something is definitely different about the way the December update is applied.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
I have a test build that's uploading, can you wait and try again while still on December? I'll ping you with link when finished upping. I think it should work fine with December image
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] RegnierD:
Sure can! I stayed on the December update after this whole shebang because I had a feeling this might happen. ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
Boot:

https://drive.google.com/file/d/1BkZ59k9Mn27CW1qs13Lm6OYwEEZ5Vyyw/view?usp=drivesdk

ROM:

https://drive.google.com/file/d/1Bi42ocKagCs7oNf8KvTAcm5s5-IHn4hf/view?usp=drivesdk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] RegnierD:
Downloaded and flashing now.

---------- Post added at 07:00 PM ---------- Previous post was at 06:01 PM ----------

No go. Device just hangs at Havoc boot animation. BUT, fastbootd was accessible. I have a theory though. In the December update's flash-all information on-screen, the procedure states it is deleting/wiping whatever the opposite system is (so if A is active, B gets wiped). I'm going to try again using flash-all on A, setting active to B and then sideloading so that it'll install on top of A.

Edit: No go again. Zip aborts installation. Was trying to avoid a clean wipe, but I'm going to try the standard method and leave -w intact in the flash all batch. :|
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
ok thats a good sign and it shouldn't bootloop bc ive been running that build since yesterday which is why its dated on Dec 7th. I havent flashed December image tho. But if it lets you get into fastbootd and flash it i would expect it to boot
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
After issuing the change slot command are you rebooting back to bootloader? you need to reboot for the slot change to take effect. have you done the flash-all script on both slots? you shouldnt need to -w wipe
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] RegnierD:
Yep, I made sure to do that. I'm nearly done with the second slot's flash-all including a clean wipe. I'll report back here shortly.

---------- Post added at 07:28 PM ---------- Previous post was at 07:14 PM ----------

All is well. It just needed a wipe. Logging into my accounts and re-downloading my apps again now. If people are dirty flashing straight from the old Havoc build, things may go through without a hitch for them. If somebody boots the December image and then tries to dirty flash into the Havoc update, they will likely need to do a full wipe.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
awesome, glad its working for you. im still skeptical that a clean flash is required, Im flashing the december image and am going to try dirty flashing to see if i boot

edit: wait if you were on stock you def needed to wipe lol.

but some people were just upgrading and having issues bc they flashed december image before rom zip
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
ok dirty flashing Havoc test build worked fine after upgrading december image for me. didnt wipe data when flashing decemeber image or rom zip

Boot:

https://drive.google.com/file/d/1BkZ59k9Mn27CW1qs13Lm6OYwEEZ5Vyyw/view?usp=drivesdk

ROM:

https://drive.google.com/file/d/1Bi42ocKagCs7oNf8KvTAcm5s5-IHn4hf/view?usp=drivesdk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] twcobra:
Has the Android Auto issue been resolved.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Zzoro:
File not find. Could you upload these files again?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] slothdabski:
links fixed

boot img: https://drive.google.com/file/d/1BkZ59k9Mn27CW1qs13Lm6OYwEEZ5Vyyw/view?usp=drivesdk

ROM: https://drive.google.com/file/d/1Bi42ocKagCs7oNf8KvTAcm5s5-IHn4hf/view?usp=drivesdk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] thex2:
When I get to the sideload section, I receive the below errors. Any ideas why I'm running into this issue?"

Full list of steps taken prior to the above issue:

Started on Android 9.0.

Enabled USB Debugging and OEM Unlocking

Went into bootloader

>fastboot erase system_a

>fastboot erase system_b

>fastboot erase boot_a

>fastboot erase boot_b

>fastboot reboot-bootloader

flash-all.bat on slot a with crosshatch-qp1a.191105.003-factory-8b53e5ec (crosshatch-qp1a.191105.003-factory-8b53e5ec's md5: 182130186188a1e998fb3e50294e5f01)

the instant the OS loaded, I immediately rebooted into bootloader

>fastboot getvar current-slot

confirmed I was in slot a

>fastboot set_active b

>fastboot getvar current-slot

confirmed I was in slot b

>fastboot reboot-bootloader

>fastboot getvar current-slot

confirmed I was in slot b

flash-all.bat on slot b with crosshatch-qp1a.191105.003-factory-8b53e5ec (crosshatch-qp1a.191105.003-factory-8b53e5ec's md5: 182130186188a1e998fb3e50294e5f01)

the instant the OS loaded, I immediately rebooted into bootloader

>fastboot flash boot boot.img from OPS boot.img download (boot.img's md5: 666018e3aa9650b2fd93848b384f21be)

>fastboot erase userdata

>fastboot reboot fastboot

used volume keys and power button to select Enter Recovery

used volume keys and power button to select Apply update from ADB

>adb sideload Havoc-OS-v3.0-20191123-crosshatch-Official.zip (Havoc-OS-v3.0-20191123-crosshatch-Official.zip's md5: 5dda2fdc74a737312ab302a50f9a8de0)

dead end... please help. Any help on this is highly appreciated. Thank you.

EDIT: After realizing I was using 2019-11-23, when Ops latest post had 2019-12-07, I decided to start all over to see if I could get it to work with 2019-12-07. I followed all directions above the exact same (except updated the commands for boot_c.img and the Havoc-OS-v3.0-20191207-crosshatch-Official.zip) and received the same errors:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Zzoro:
With this boot.img I succeed to boot into fastboot on Decembers factory image.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] pangolin.rollin:
Running great on December update with the 12/07 test build. Magisk is working. Appreciate the hard work, so far no issues.

For those curious on steps..

I just clean flashed the full whole dec factory image, reboot back into bootloader, flash boot_c.img to boot with --flash=all flag, reboot to recovery and adb sideload havoc. Once booted up at least once you can flash a patch the provided boot img with latest magisk canary.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] thex2:
Are you saying that boot_c.img has to go on slots a and b? If so, can you please type the full command? I'm hoping this is my problem. Also, after you flash the factory images to both slots, do you have to go into the OS for both slots and enable USB Debugging?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] vn00914361:
Download the latest factory image and try from the beginning.

1. Boot into bootloader

2. Make sure fastboot recognizes your phone

fastboot devices

3. Use stock script to restore your phone to stock

flash-all.bat

4. Once script is done, your phone will reboot automatically. Since bootloader is unlocked, your phone at first should display a warning. Interrupt the warning by pressing Power button once. Then press and hold combination keys Volume - and Power until bootloader shows up, slowly release Power button, then Volume -

5. Switch to slot_b, then flash-all again

fastboot set_active other

flash-all.bat

6. Once done, initiate your phone. Don't bother logging into your Google account just yet.

7. Shut down your phone. Boot into bootloader

8. From bootloader, enter fastbootd

fastboot reboot fastboot

9. From fastbootd menu, enter Recovery

10. From recovery menu, choose Update via ADB

11. ADB is now enabled. Start sideloading Havoc

adb sideload "Havoc..."

12. From recovery menu, reboot to bootloader

13. Flash Havoc boot image

flashboot flash boot boot...

14. Reboot and enjoy

---------- Post added at 11:53 PM ---------- Previous post was at 11:46 PM ----------

This is the first time I'm facing this issue... I'm receiving this error msg at Recovery after it stopped sideloading Havoc at 47% :

E: failed to verify whole-file signature

E: Signature verification failed

E: error: 21

I tried on both releases 20191206 and 20191207... This is so strange... I'm going back to previous release and see how it goes...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] pangolin.rollin:
You don't have to touch anything on the stock install before installing havoc. AFAIK when you sideload it installs to the inactive, so instead of figuring out which one I was active on to install on the other I just opted to install on both.

'fastboot flash boot boot_c.img --slot=all'
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] thex2:
Did you flash boot boot_c.img? I only ask because you omitted this in your directions. Other than flashing the latest factory image, I've followed the rest of your instructions and it still doesn't work for me. I'll give the latest factory image a shot.