yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jrock60:
I really appreciate this!

Just to be 100000% sure:

1 Fastboot - Bootloader to both slots

2 Fastboot - Radio to both slots

3 Reboot to TWRP

4 TWRP - Flash June Vendor

5 Wipe Cache

6 Flash PN

7 Flash TWRP RC2 3.1

8 Reboot TWRP

9 Flash June Vendor

10 Flash Magisk-v12.0-Pixel.zip

11 Flash TWRP

12 Reboot

I see a lot of slot switching talk all over the forum, will this not be necessary if I follow the steps above?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Depends on the theme.

---------- Post added at 12:03 PM ---------- Previous post was at 12:01 PM ----------

Your slots switch automatically at step 8, because you flashed a rom zip in step 6. Under normal circumstances you shouldnt need to swap slots manually.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jrock60:
So basically at step 9 I need to make sure it is flashing in the same slot as it was before step 6, and if not manually switch slots?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Not exactly.

If you are on A, the rom will be flashed to B. If you want to verify anything you want to check your slot prior to flashing the rom and check that it swapped after your first reboot. Thats how it should work since the rom flashes to the slot opposite the current slot.

To put it in perspective, I never check, so dont think that is a required step unless you start having issues with FCing apps and such when you boot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
Is there a reliable way of dirty flashing the ROM from a prior release that works?

I know starting with stock Google images and clean flashing would work, but it seems a bit of a overkill to lose data every month and start from scratch.

For N6 and other phones , dirty flashing was as simple as wiping cache, flashing ROM, SU, kernel and rebooting.

It seems with PIxel people always prefer to clean flash a ROM release, since dirty flash causes issues.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
You don't have to lose data if you flash-all, just remove the -w switch from the batch file.

Essentially what I am seeing as far as dirty flashing (post signed PN builds) is that its the same process as before just wipe your cache instead of a factory reset, you still have to reboot before you do su and such though.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
Thanks for the reply. For dirty flashing why should it be required to use the flash all file?

Isn't it enough just to fastboot the bootloader and radio ( if needed ) to both slots. Then just go to TWRP , wipe cache , flash ROM, flash TWRP, flash VBS. Reboot to system. Go to recovery. Flash Vendor, flash SU, flash VBS. Reboot System. Go to recovery. Flash kernel. Reboot System. Is this correct?

The flash all batch file at Google flashes the bootloader and radio. But then it also does a fastboot update of the stock ROM image. Wouldn't that be a problem if one is already on PN ROM since the custom ROM image is different from the stock ROM image etc? I guess I just don't understand the need of going to stock files again. The only thing common in the custom and stock ROM is the radio and bootloader which can be fastbooted separately. And beanstown has those files in the AFH folder from where they can be downloaded and fastbooted. . Thanks.

I guess I'm a little old school coming from N6. We used to have flashable radio and bootloader. And we had to do was to flash the ROM along with these and be done with it. The process was quick and painless. Never had to worry about stock images and the flash all bat files from Google.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] MArtyChubbs:
Thank you my friend. That worked...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
There are other partitions that get updated outside of what a ROM has. Knowing that though, there is nothing I have seen in writing that says to the left or right how important or often those updates change in a given partition.

I personally can go either way with keeping my device up to date. Sometimes I flash modem, radio, BL, and roll with it. Sometimes I grab a factory image and flash that just because I like having stock files around in case I screw up something.

Same with wiping, some people say wipe everything but SD card, some even wipe sd card but a simple factory reset works fine.

As far as dirty flashing, if I dirty flashed with the factory image, I would flash all with -w removed, immediately boot back into twrp (even though the stock rom will likely boot fine but with some FCs) and fastboot twrp, flash twrp, flash rom, wipe cach, flash twrp, reboot, flash su, etc, twrp..

Essentially the point is to keep data in tact but update everything else.

Otherwise look at your normal flashing procedures and substitute Factory Reset with Wipe Cache.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
Thanks. Makes sense. So removing the -W in the flash all bat file would keep the user data partition intact I'm guessing. Also it doesn't make sense to me to wipe internal storage. In all my previous phones I've never seen that give any benefit except to increase the time it takes to copy all files again.

Just out of curiosity what is your daily driver? Are you on stock ROM or on PN. Does the PN have better performance or battery life compared to stock ROM.

Right now I'm on stock Rooted ROM with Elemental X, but I've always used PN on my previous Nexus phones.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Wiping internal has never made sense to me but in the evolution of all things android there are some tribal practices that stand the test of time if through nothing more but word of mouth.

Things like wiping multiple times, if the command twrp sends to wipe a partition doesnt work the first time, you have more issues at hand.

But if it "doesn't not work" then hey technically it isn't wrong. Just maybe time consuming..

I'm usually on PN. Objectively speaking I get itches for more customization but always end up back here. Stability has been great and battery as well but the margin of difference is pretty small with the roms we have to choose from.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chazall1:
All good here. All functioning as expected.

Thanks for the update
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cowsquad:
Is android pay working for you guys on latest build with magiskv12. Mine is not
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] just_visiting:
Yes. Go back and read the last 10 pages or so. All the info are there.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chazall1:
I am having an issue in changing the default dialer. I set the google dialer in default settings, apps, Cog, phone app set google to default. I rebooted and the setting was set as I had set. However when I grceive a call the AOKP app starts.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Disable the aosp dialer?

---------- Post added at 12:36 AM ---------- Previous post was at 12:35 AM ----------

Go into settings and turn on magisk core only. If you don't have that option upgrade/downgrade to magisk manager 4.3.3
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cowsquad:
Thank you man. I figured out ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chazall1:
LOL Disable the aosp dialer? Thanks all good.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I don't get what's so funny about that. You have two dialers in your device and it keeps switching the default to the aosp dialer. So my Android common sense says disable the dialer you aren't using. I mean unless you have a better solution? Unless "AOKP app" isn't a typo and in that case I dont know what app that is
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chazall1:
Not meant to be dis respectful . LOL was to the the fact how easy your suggestion was. asop is what I meant. I am staying with the default asop dialer. Sometimes I may miss the basic solution that right in front of my face. Sorry
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
It's all good, I figured maybe I was screwing something up.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sassmk2:
What I did coming from May PN Build. April BL. Dirty Flashed. No Magisk.

This is what I do every time a new build comes out. Other than when Beans started signing his builds couple months back...

0. Made sure substratum theme was disabled.

1. Booted to recovery and did a Nandroid back up.

2. Wiped Cache.

3. Reboot Recovery so I was on opposite slot of May Build of PN.

4. Flashed June PureNexus.

5. Flashed TWRP RC2.

6. Reboot Recovery

7. Flashed Vendor image in TWRP.

8. Booted ROM (made sure everything was good to go)

9. Reboot to Recovery.

10. Flashed Super SU 2.79 SR3.

11. Booted ROM.

12. Reboot Recovery.

13. Flashed Elemental X v12

Everything running smoothly! Thank you Beans for the awesome work!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] elreydenj:
Now that aosp phone app has been added back as a system app, Google phone (from play store) no longer gets push notifications if aosp phone is disabled..... This seems to be a step backwards once again. I believe adding Google phone as a system app should fix this hopefully? Any one else can confirm?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I know it didnt work before for me but who knows. I will say I didn't drop it in /system/priv-app last time so maybe that will make a difference over /system/app/ when it gets installed as a system app.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Sachi315:
Yes that is all you have to do. Download the google equivalent and then either disable or fully uninstall the aosp apps if you have root and the proper app.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cowsquad:
To anyone on here using magisk. Whybi cannot install apps to system. For example. Better battery stats always fail to install to syste
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Archangel:
Make sure your mount system in something like root explorer before trying to install an app into system/app. There is a little tab in root explorer at the top that says mount ro change to mount rw
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Bogega:
Do i understand it correctly that June update doesn't require flashing the verified boot signer zip after you flash something that modifies boot.img?

Thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Golf c:
Correct, as long as you have the June bootloader installed
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ForgottenDude:
I go one step further and instead sell and buy the phone again to keep it fresh.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vega04:
So, Im getting a new Pixel-XL today. My current pixel had a dead pixel....I know right..

Anyways. I plan on Flash all with NKG47L because I am on Fi?.

-Reboot Bootloader

-Flash Temp TWRP

-Flash ROM.zip

-Flash TWRP.zip

-Flash BootSigner.zip

-Reboot system

-Setup & Boot to TWRP

-Flash SuperSU.zip

-Flash BootSigner.zip

-Reboot system

-Boot to TWRP

-Flash EX Kernel.zip

-Reboot system

My Steps right? I shouldn't have to worry about slot A/B since it will the first time its booted? I really miss how easy the nexus was.. :(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 3aucla1r3:
That first Flash TWRP.zip isn't necessary since you can flash the ROM off the temp TWRP and then the Flash TWRP.zip. You just put an extra TWRP.zip in there, probably wouldn't hurt anything, just a wasted step.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vega04:
Alright, Updated the list
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] njinstantkarma:
I haven't updated my phone since a few months back due to all the problems people have been having but I would like to get to the latest build.

I'm still on Build NOF26W with the February 5 2017 security patch. What steps should I take from here.

Is there a step by step guide or video I could follow since reading all the posts it get's very confusing this works for me then someone chimes in why did you bother doing it this way etc etc. Is there a 100% exact step by step way to get onto the current build.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] EstiR86:
Same boat here but I'm pretty sure all you need to do it flash stock download files, have twrp, factory reset then flash using instructions on second post
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JAYNO20:
I also only wear my shoes once before buying a new pair.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Rootuser3.0:
You don't have to flash the vendor? Didn't see you included that.

Anyways I successfully upgraded and I was still on 7.1.1 by flashing the google update first and then I followed those steps. When I flashed the bootsigner it failed but I was able to boot up anyway. I noticed when I flashed the google update I did to slot a and slot b so both slots had the newest bootloader and baseband.

Now I just need to root slot a and leave slot b stock
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Iceman248:
I'm having an issue with Do Not Disturb mode on 5/9 build. It was a clean flash. I've only really starting using it now. When I go to sleep, I set DND to Priority Only. I noticed on a phone call that it only vibrated. After testing, I discovered that everything else sounds off like it should, but a phone call silences the ringer, so call doesn't ring, nor does anything else after that. Even when I take it off DND, ringer is still silent. I've rebooted, played with some settings, had Phone app override DND in notifications, still does it. Any suggestions?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jlee08517:
You have to clean flash. And follow the third post that beans wrote.

If you need something more detail There has been at least 10 step by step posts past week. You should be able to find one within 5 min of searching
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vega04:
I updated my steps. because damn, I did have to flash twrp in temp twrp first. It did not install correctly.

Anyways. I plan on Flash all with NKG47L because I am on Fi?.

-Reboot Bootloader

-Flash Temp TWRP

-Flash TWRP.zip

-Reboot Recovery

-Flash ROM.zip

-Boot

-Reboot Bootloader

-Flash Vendor

-Flash Temp TWRP

-Flash TWRP.zip

-Flash BootSigner.zip

-Reboot system

-Setup & Boot to TWRP

-Flash SuperSU.zip

-Flash BootSigner.zip

-Reboot system

-Boot to TWRP

-Flash EX Kernel.zip

-Reboot system

-Power off Old Phone Insert SIM into new phone :)

the USB dongle makes this a lot quicker, installing from usb is slower btw.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] just_visiting:
Because apps like Substartum, Whatsapp, Weibo, Snapchat, etc... writes to the sd card. I'd like a fresh start everytime I flash a new rom. I want them to create new copies. I also don't backup any app data. I download all new copies of my apps from the playstore.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Hey it's your choice. I just like to let less seasoned users know this is isn't really a standard anyone needs to adhere to under normal/usual circumstances. Its a personal choice.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] just_visiting:
Oh I agree, it's my personal choice. ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 3aucla1r3:
I don't mean to be picking at you but just wanted to be sure you knew that Vendor.img can be flashed from TWRP (there's and option for image flashing in TWRP). I only say that because I notice you booted back to bootloader to do vendor and then needed Temp TWRP again. I think your way would work fine but looks like extra steps, but you do the way you feel is good. ;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] vega04:
Only reason I did it. becuase I knew after I booted PN without installing TWRP there I wouldn't have recovery. But It may work the way you said.;)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] MArtyChubbs:
Where did we get that the SD card was wiped? I always wipe data and the cash when I am doing a new ROM which I was doing in this case coming from stock I didn't have to worry about wiping the SD card since TWRP wiped it for me on expectedly so I lost all my Titanium Backups as well which is my preferred method of restoration
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 3aucla1r3:
Temp TWRP then flash ROM then TWRP.zip then Verifier/signer, reboot. Back to recovery TWRP which you have now and flash the vendor then reboot (or actually I flashed SU and Verifier/signer in that step), then add the rest like you have it. That's the way I did it and it worked.......................I'm not telling you what to do, I promise, just here's what I did in case it seems simpler.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] MArtyChubbs:
Where did you get I did wipe the SD card? I do a factory reset when I go from another ROM... It's even in the OP of every ROM.... Derp...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] spotmark:
Wasn't the verified boot signer only needed for the May bootloader?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Yes, thats correct.

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

I think you mixed up who you were responding to, the quoted text was in response to a user named just_visiting, not you.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
Finally clean flashed to the June PN release yesterday. I got bootloops while installation until I realized that the Google factory image and the PN installed on separate slots. So one of the slots was missing the bootloader. For good measure flashed radio and bootloader on both slots. Everything proceeded smoothy then.

2 questions

ROM is snappy but the battery life is less than stellar. Android OS and Android system have both BiG battery drains. Over 10 percent on both. So far the battery life is inferior to my previous stock rooted setup. Any insight as to what might be causing the heavy drain from android OS and system?

How do I know the slot that the current PN is flashed at i.e the current active slot? While dirty flashing next month, I will have to make sure that I flash PN making the other slot active. Otherwise might have 2 copies on PN in both slots or the system might not boot.

My understanding is that the ROM always flashes to the Inactive slot ( w.r.t active slot while flashing the ROM). So one has to make sure they flash from the opposite slot where the ROM is currently installed. Problem is I'm not sure whether the ROM is in slot A or slot B.

Thanks in advance.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Iceman248:
So I figured a way to resolve the ringer being silenced in Priority Only DND mode. I'll share how in case I'm not the only one with the issue. I used Tasker to put ringer back to where it was on an incoming call when in priority only mode. I could share more details if needed.

Another issue though regarding DND Total Silence mode. It silences the keypresses from vibrating. I don't prefer this. They don't really make an audible sound. Is there a way to have keypresses vibrate when it Total SIlence?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
You can see your current slot in the twrp reboot menu or on the bootloader screen.

You could flash all in both slots so that way when you flash the next update it won't matter which slot. Your device will have pn in both slots but the inactive is just that and will get overwritten in follow up flashes.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
Just to make sure I have this right. If I reboot into recovery or bootloader - will that give me the slot the ROM is installed in or will it give the other slot? I thought when you reboot the slot is changed automatically?

I had thought of doing a flash all in both slots but doing that will mean more storage space right? The bootloader and radio are small but the system and userdata partition will take a lot of space if they are duplicate across slots?

Thanks for replying.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
So if you are up and running now. Looking in twrp or the bootloader will show the current slot. Which is where the functioning rom is now.

Flashing the factory image in both slots doesn't take up more space, slot A system parition doesn't take up any of slot B's system parition so it's bacially space you won't be using anyways.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] MeetFace:
So if I flash the June factory images first, I won't need to worry about the boot signer zip? I'm on the April build right now (shouldn't matter).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] imjimmy:
Thanks. That makes sense.

I was just thinking that I can manually fastboot flash: Bootloader, Radio, Vendor, Twrp recovery on both slots. That way both are bootable. in worst case. And even if PN is flashed on the wrong slot it will work.

Last Question: I just booted into recovery and saw my current slot as slot B - which means PN is installed in slot B and will have to flashed in slot A next time.

So when I have to dirty flash next month:

Boot into TWRP.

Wipe cache.

Set Slot A to Active.

( Check active slot is slot A) - I usually do this by looking in Reboot button of TWRP.

Flash ROM

Flash TWRP

Flash VBS.

Reboot Recovery.

(Check active slot is slot B in TWRP)

Flash Vendor

Flash SuperSU

Flash VBS

Reboot Recovery

(Check active slot is slot B in TWRP)

Flash EX Kernel.

Reboot to System in TWRP and Profit.

Does this sound right, to be able to preserve data and flash an update i.e dirty flash? Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
That sounds about right. I don't think you need to flash vbs if you are on the June bootloader though.

Also you are correct you can fastboot all those files. I don't think you need to flash twrp in both slots though. Fastboot boot of twrp is basically running the twrp from memory. When you flash the zip in twrp it modifies the boot img in slot a and b to make it stick (until you do something that modifies the boot img).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] imjimmy:
Thanks. Wow, so I didn't know that Flashing the TWRP zip will make the recovery go in both the slots. That means if the radio, bootloader and vendor are manually fastbooted flashed to both slots, then it should cause less problems with bootloops. sinc e the recovery is already there and the system is flashed with the ROM.

I'm guessing the data partition will be shared across both slots. So it should be technically possible to install PN on both slots. I'm thinking of trying this, where in one slot the PN ROM is rooted and custom Kernel. The other slot the PN ROM would be without modifications (so that Android Pay, Netflix, Pokemon GO etc work).

Just wanted to make sure that I figured out the slots. Is fastboot set_active_b and fastboot set_active_a the adb commands to change slots in the bootloader?

People are reporting bricking Pixel phones when they change slot and reboot to a slot that does NOT have a bootloader installed.

What will July bring? Hopefully nothing too crazy. It's strange to me that May boot needed VBS and June does not. Thanks for your help again. Much appreciated.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Technically your device was already in the other slot before you flashed the rom so I think you are good.

Also you are correct about data being shared across slots. I know some have gone the route of running stock unrooted in another slot. Installing magisk is also an option.