yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jiexi:
Just bought a new pixel xl, and I can't for the live of me figure out how to get this **** working. I always seem to get stuck in a bootloop..

1) Flash may factory image

2) boot into bootloader

3) fastboot boot twrp 3.0.2

4) install twrp RC1

5) install supersu sr3

6) install boot signer zip

7) reboot into recovery

8) factory wipe

9) install pure nexus 7.1.2_r8

10) install twrp RC1

11) install supersu SR3 2.79

12) install elemental

13) install boot signer zip (force resigned since it seemed to be signed already after elemental was installed)

14) boot system

The phone boot loops a few times, then gets to the bouncing balls loading screen and seems to be stuck here forever...

What am I doing wrong?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Oh you guys and these crazy steps.

Sometimes you have to ask yourself why when you flash something. Like why flash su twice?

So one huge thing to remember is that there are two slots for system.

When you flash a rom it loads up like an OTA. It flashes to the inactive slot so if you were using your device the OTA would flash to the inactive slot so that in your next boot it would essentially swap slots to he most updated.

So when you flash the rom it goes to the inactive slot. At that point you should only follow up with TWRP and the bootsigner. Reboot to recovery (now the slot with the rom is active), then and only then do you go back and flash Su, twrp, then the boot signer.

Also the last two things you flash should always be TWRP and bootsigner if you flash anything that modifies the boot.img.. for instance SU. That's part of the reason why you keep bootlooping..

I'd try the process without SU to see if you can even boot.

Then try it with su but without the kernel.

Then boot back into recovery and flash the kernel.

Flashing a ton of things the first go around only makes it harder to figure out where you are going wrong.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jammol:
I'm having a weird issue with mine since going to Preview 2 of O. I can't use TWRP(any version). Device boot loops. I'm stuck stock! :(

PM me.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TheBobMiller:
[MENTION=4395895]BeansTown106[/MENTION] Any chance on bringing back the force expanded notifications option? I miss it from earlier builds!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dmb219:
When I decided to backtrack from the O preview I flashed the April factory image, then took the ota to the May update. That gets O off of both slots. I flashed the April bootloader on the May update to avoid the signing business. There might be an easier or quicker way to fix it but this works.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stuntnmore:
im on the latest may update, made sure all substratum overlays were off, dirty flashed but i still keep getting a system ui error everytime i bootup.

---------- Post added at 01:42 PM ---------- Previous post was at 01:23 PM ----------

Where is the bootsigner zip?

i cant find any links for it
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stuntnmore:
Ended up having to format didn't even need the boot verification,
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
Only need the boot zip after flashing TWRP, Kernels and Supersu/Magisk
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
If you needed the boot signer you would know because you would need to be on the may bootloader and you wouldn't even boot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] stuntnmore:
That's the thing it wasn't before , at some point i made a mistake in the process of it all. At least my phone is working now. I appreciate your help though
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Glad you figured it out.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jammol:
Hmm, I'm going to try that then. I've flashed the April and May factory with both slots and it's boots just fine, but once I flash TWRP and reboot it just loops at the Press pause screen.

Edit: Question for you guys, in the bootloader, what does your Secure Boot say next to it?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Production
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jammol:
Oh okay. Yeah that's what mine says. I never really looked at it before and though, that's odd.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jiexi:
I can't figure this out. This isn't my first android phone, and definitely not my first time flashing roms. A little disappointed that a phone being sold by Google to replace the nexus line is so unstraight forward to flash. I'll pay someone $10 to hold my hand and get this rom, supersu, and EX working on my phone on with latest May update. Seriously, tired of fiddling with this.

EDIT: Nevermind... figured it out. For anyone else confused af. Don't even bother with the may bootloader + verified boot signer combo.

Flash-all May to slot A

Switch to slot B

Flash-all May to slot B

Switch to slot A

Flash April bootloader to slot A

Switch to slot B

Flash April bootloader to slot B

Switch to slot A

Fastboot boot TWRP RC1

Wipe Factory Reset

Flash ROM

Flash TWRP RC1

Reboot System, Let it get to the setup screen

Restart to Recovery

Flash SuperSu v2.82

Reboot System, Let it get to the setup screen

Flash EX

Reboot System, Let it get to the setup screen

Set your **** up
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikefnz:
Your dedication is admirable. I don't have that sort of time anymore so I will just have to stay with O until I have a spare couple of hours!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] MeetFace:
Are people flashing SuperSU 2.79 SR3 after the update fiasco, or is it preferable to update to 2.82? If the latter, which zip you using?

---------- Post added at 06:22 AM ---------- Previous post was at 05:58 AM ----------

For anyone else looking, I flashed the 2.82 zip in recovery, simply updating the APK didn't work for me.

---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------

https://xdaforums.com/showpost.php?p=72429329&postcount=9810
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jammol:
Finally got this thing working!!!

Had to go to L image to get it to boot. Can't run PureNexus for whatever reason. Only thing I can run is LOS unrooted and no TWRP allowed. Called Project Fi, got a new XL coming. ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jiexi:
I'm running UPDATE-SuperSU-v2.82-20170526223454.zip

Test-1 is the most recent one though. SuperSu should alert you to a new version when this fiasco is over and he releases a new stable version. Current version in playstore is 2.81 (this is the broken one). I assume he'll just jump to 2.83 once it's ready.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
That's super weird. Hopefully that isn't a foreshadow of things to come with O
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rickysidhu_:
Somewhat off-topic, but I'm wondering if anyone has some information on that RamDump issue? I posted in this thread as well:

https://xdaforums.com/pixel-xl/help/ramdump-t3582446

But I thought I'd ask here, just in case someone has some more detailed info. The RamDump happened to me for the first time this morning - I had powered off my device, and when I turned it back on, there was a long vibration followed by the RamDump message.

I'm not too worried just yet, since it's the first time it's happened, but I thought I'd ask if anyone is able to shed some more light on this!

Thanks in advance
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] nadiros:
I'd like to know as well. Has happened to me several times with latest Pure Nexus and April Bootloader
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 93fuelslut:
Subscribed
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aaronpw0621:
It has happened to me too. And now I can't get twrp, SuperSU, or a custom ROM to flash. Just bootloops at black warning screen. Then sometimes the ramdump screen appears. I have been forced to stock unrooted because of this. We really need a thread that explains in detail how to flash stock image to both slots if that's the actual issue. But one day I flashed a custom ROM just like always on this device. The next day nothing but issues.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] EstiR86:
Has anyone been receiving an error when trying to call someone? I can seem to call anyone but when i go to setting and under cellular networks and turn off Advanced

Calling i seem to be able to call and receive calls. Does anyone know why this is?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I'll say my ramdump doesn't come with any outstanding issues. I usually only see it when I hold down the button combination to shut down and reboot into the bootloader.

I see the ramdump and continue holding the combination until I end up in the bootloader.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ModWilliam:
Is there a way to enable one handed mode without the navbar? (I disabled the navbar)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Almaretto:
I followed instruction in post #4 with some modifications:

make sure you are on the latest bootloader, radio, vendor image

install twrp via the instructions in twrp forum

wipe data factory reset

flash rom.

flash twrp zip again as the rom overwrites twrp (stupid pixel lol)

It just kept rebooting into TWRP. I re-did steps 3-4 > rebooted > step 5

if you desire boot into the os, then reboot into recovery and flash supersu

Phone booted up great. But, then went to reboot to flash SuperSu. Now, it is cycling between "Your device software can't be checked for corruption. Please lock the bootloader." Quick flash of white screen with google,

and ramp dump screen

If I do nothing, it keeps cycling. I can either press power to pause at "lock the bootloader" screen or hold down up+down and screen goes black. I cannot seem to get back to bootloader.

EDIT1: Used bootloader sequence (pwr + PD) to start process over at step 3 and was able to complete process.

EDIT2: For Wifi Calling, I noticed under main "Wireless & networks" section, Wi-Fi calling always says "Cellular preferred;" even if roaming preference is set to "Wi-Fi."
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JAYNO20:
I'd love to hear a fix for this, but I am pretty sure it doesn't actually switch. Even on a stock rom I couldn't get it to show Wifi preferred.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Is this specific to verizon?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JAYNO20:
I think so.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Almaretto:
When I was stock, mine switched.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JAYNO20:
Verizon?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Almaretto:
VZW and non-VZW. I first order Big red and then quickly returned to order Google.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JAYNO20:
I have 3 Pixels around me at all times. All VZW and NONE of them have allowed that switch whether stock or rooted and rom'd. If yours did it would be the first I've ever seen.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Almaretto:
I had VZW on 7.1.1 and 7.1.2 (unrooted). Now I have Google, first on 7.1, then 7.1.1, and now 7.1.2. I have not tested NONE long enough to notice whether preference makes a difference in call quality.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JAYNO20:
Right, but that's not the question here. I have no clue if it actually makes a difference or not. Just noting that even after switched the settings still shows Cellular preferred.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Almaretto:
I just received a couple calls and each time it said wi-fi calling. But, it dropped one of them. I did not have that issue on the VZW version. My priority would be if it makes a difference.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scottay5150:
Good morning, I am taking a cross country trek from Denver to Big Sur. Along the way having difficulty connecting to free WiFi along the way.

It seems that Denver is a xFinity town and beyond is not? I don't know what the difference is or if there is a fix.

Any ideas?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Jammol:
Not sure what exactly you're asking, but open Xfinity wifi isn't available everywhere Xfinity exists as yet unfortunately. Now if you switch states, I've had to sign in again on the Xfinity open wifi spot that I found until I got to another state. Not sure if that's supposed to be that way, but that's how it happened to me from Colorado, Nebraska and Kansas.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scottay5150:
I'm not having issues with xFinity. Connecting with McDonald's, Wendy's WiFi all no connection.

Around my house it's not an issue. Is there an app that can help with WiFi connectivity?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jlee08517:
A little off topic. I thought most of big sur was closed due to road closures from rain?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scottay5150:
Yup it is, except for one way in..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scottay5150:
This is what I am seeing in King City CA and elsewhere.. View attachment 4166499
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikefnz:
Flashing from 7.1.1

Had my Pixel XL for just over a week now & I've finally managed to root it and get TWRP installed using Skipsoft.

Now I'm on 7.1.1 with build NOF27B.

I have skimmed various comments here and elsewhere and am wary about the next steps to successfully install Pure Nexus.

Does anyone have the time and confidence to outline the steps from here to guarantee a successful installation of Pure Nexus?

I've flashed a few phones in my time but this one appears to involve some serious zig zags....

Guidance would be much appreciated!

Cheers
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] fairyshacker:
Just got my pixel xl a few hours ago, haven't booted up yet. Awaiting for new installation instruction. :D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] EstiR86:
Read the second post
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Have you searched the forum? Some one asks for steps every 3 days or so. They've been posted quite a few times. You could probably search for the word steps and find a ton of support.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikefnz:
Thanks. The simple approach worked. Followed original instructions with my 7.1.1 version. Everything is running sweetly. All the war stories must relate to those starting from 7.1.2.

Just a note to others then. If you are having problems try using Skipsoft to clean everything and load up a stock 7.1.1 version, get TWRP flashed, and get root. Then it seems relatively straightforward to flash the ROM.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] EstiR86:
Skipsoft? I'm not familiar with the software.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mikefnz:
https://xdaforums.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I haven't used a toolkit but if it's just using simple fastboot and adb commands there should be no issues.

Also most of those horror stories are going to be from the May builds on. The may bootloader requires users to use the verified boot signer and I have seen a number of steps from different users to work for some and don't work for others.

If you decide to flash to the may build or even the June build of stock firmware I would fastboot flash the April bootloader to avoid all the verified boot signer stuff.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Both slots aren't by design meant to be bootable. They get the bare minimum to be useful when its time accept an OTA.

That why if you just switch slots to see what the otherside is like you may screw up /data/ and need a clean install..

With you never just flashing the rom twice, your other slot had place holders. When you flashed PN it flashed to that inactive slot.. So the previously active slot has the stock system image, the one you switched to.

I've never bother to try and have two fully functioning slots so I can't answer that question. I do know the one time I had a rom on both slots and just tried to swap all it did was give me FCs on programs and I ended up wiping data..
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rickysidhu_:
Ahhh, that actually makes a lot of sense! Thanks for your reply.

As for me using the flash-all twice, do you think that's overkill? My guess is that it might be, unless I'm planning on relocking the bootloader, in which case I'm assuming it is a good idea to get factory images on both slots.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I personally don't do it but there are pros and cons depending on how you look at it.

When you flash the flash all zip Im pretty sure the inactive slot gets a place holder system img.

So when you flash both slots the inactive at the time you flash will not get a full system image UNLESS you modify the flash all batch file to do so.

The plus side is things like bootloader and vendor get mirrored to each slot so if you flashed a rom to inactive slot it replaces the placeholder system img and everything else should be good (modem, radio, bootloader, vendor)

You could also just manually fastboot flash the system image to the inactive slot once your flash all finishes but I don't know if that toolkit supports that.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rickysidhu_:
Thanks again for all the info, it's much appreciated kind sir.

Now that the flash-all method works again for me, I'm probably going to refrain from using the toolkit - it's probably better to go the flash-all way in case deeper troubleshooting is required in the future, or if the toolkit stops being supported.

I'll also stick to using flash-all just once if I ever want to clean flash before flashing a new version of PN, but will do it twice if I ever want/need to relock my bootloader, just for good measure. Thanks again for all your input! :highfive:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] spotmark:
Not to stray, but I tried flashing two different ROMS to each slot, and it was not fun. :silly:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jayf99:
Probably more an issue with the WiFi network than your phone.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bagofraisins:
Holy **** man thank you. I was on an older build of PN when I heard the news about Paranoid Android. I flashed it and didn't like it, so I wanted to instead update my PN. No matter what I tried, I could not get it to boot after many hours. I was finally able to get it all working with your instructions. Why is the Pixel so difficult to work with...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sefirosu0522:
Following [MENTION=4622637]jiexi[/MENTION]'s post, I came up with this to help myself. See attached. The only thing I'm not seeing in the instructions is mention of the vendor image. Is it not needed? I'd like to point out that I added a step to make sure I start in slot A since my phone always defaults to slot B. Should I not do this?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
The devices shouldn't be defaulting to a particular port. It may seem that way but I doubt that is what is happening.

If you flashed a factory image that is of the same build this rom is based off of then you don't need to flash the vendor. If you flashed a different build you have to flash the vendor any time after the first boot/reboot after flashing the rom
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sefirosu0522:
Thank you. All I know is that every time I boot into the bootloader, it says it's on slot B.

Right now, I'm running the stock May image. Build N2G470. I'm just rooted and have TWRP installed. Am I good to follow the guide I created for myself?

I can't thank you enough for your input.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Those steps should work so long as you aren't on the may bootloader. You also don't have to boot into system. You can just reboot recovery Everytime it mentions rebooting.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sefirosu0522:
Thank you. I might hold off for now then. I am on the May bootloader.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Your steps though call out flashing the April boot loader. If you did that then you should be fine.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sefirosu0522:
Those are the steps I want to take. I was on the current PN but then root updated and broke stuff so I did a flash all on the May image. That's where I'm at today. Just stock May image, rooted and TWRP. I'm assuming the May image would have the May bootloader if you do a flash all?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Look at your steps. Step seven has you flashing the April bootloader.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sefirosu0522:
Okay I'll give it a whirl tomorrow and see what happens. I haven't actually taken these steps yet. I just wrote them down and wanted to make sure the process would help my situation. Wish me luck!

Thanks again!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jiexi:
You won't need the vendor image for the latest Pure Nexus if you're already on may images (because that vendor image is the the one from may)

I assume you know how to run the flash all for may(and that you can remove the -w option inside the flash-all.bat, or .sh or whatever version of the script you plan on running).

Good luck!

EDIT: Also make sure your set-active commands are correct. pretty sure it's _a and _b
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Being on a May build alone doesn't mean they don't have to flash a vendor image. They need to flash the vendor for the May build the rom is based on..

So either flash all the variant the rom is based on and not have to flash the vendor or flash all any other variant and just flash the correct vendor in twrp.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] b4u2:
My phone keeps trying to boot to slot B when everything is set up on slot A. When I reboot the phone it goes to TWRP instead of just rebooting. It took many attempts and forcing slot A but it finally rebooted. No idea why it's doing this. Sometimes rooting and custom is PIA

This all started because apps start crashing and closing. That's when I discovered it was somehow on slot B
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sefirosu0522:
I'll double check the slot commands. I know how to run the flash all for May. I don't know what removing -w does. I did see it in the batch file.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Its so it doesnt wipe the sdcard partition or data
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sefirosu0522:
Got it. Thank you. Okay so last thing, at what point do I need to flash the vendor image given the attached steps? And if I'm going to flash the April bootloader, do I still need the verified boot signer? The latest I have is v7.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
You don't need the vbs for any bootloader from april or earlier.

Flash the vendor the same time as su.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sefirosu0522:
Will do. Thanks for all the help!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sefirosu0522:
Guys having an issue following those steps I listed earlier. I can't flash the April bootloader. I've replaced it multiple times. Here's the error I get. Any thoughts?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bdr9:
It looks like you are missing the file extension. Try adding .img to the end of the command.