yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] badabing2003:
Thanks [MENTION=4810220]Homeboy76[/MENTION] and sorry for not being too clear.

What I meant was, Step #4 already asked for uninstall, so by step 7 Magisk is already uninstalled.

Why would I need to uninstall it again?

I suppose you tried to make each step independent of previous steps.

Thanks

BB
[Google Pixel XL Guides, News, & Discussion] Supaiku:
Does it work with the latest marlin-pq2a.190205.003-factory-8a9a1ff8 ? when I install Marlin with or without the latest flash kernel it just bootloops.

Any ideas/insights?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Yes, it works with the February 2019 Factory Image.

Do #4 'keep data' then do #8 to root with kernel.

Flash kernel hasn't been updated for the February Factory Image. You may want to try one of the kernels updated kernels (See Updates).
[Google Pixel XL Guides, News, & Discussion] Supaiku:
I guess now I realized there's a seperate thread for marlin - so... makes sense it wasn't working. However, that root method didn't quite work either. Sometimes things don't work the first time though - I'll try some more things.

I guess double checking what the kernel is built for would be an obvious one too :P Thanks Homeboy :)
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
No apology needed, you are correct #4 did have information about using Magisk's Uninstaller.zip. I have corrected that error.

Thank you for bringing it to my attention.
[Google Pixel XL Guides, News, & Discussion] Freak07:
[MENTION=4810220]Homeboy76[/MENTION] I updated my kernel again :)

You might want to adjust your thread in case you haven’t already :) it can be flashed via exkm and fkm as well as twrp.

It detects custom roms and keeps magisk root preserved :svetius:

If you have already it’s also fine! Just wanted to give you a heads up! Thanks for maintaining this guide thread!
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
You're welcome, Done!:)
[Google Pixel XL Guides, News, & Discussion] ChevyNexus:
OK fixed the update issue, just redid my platform tools.

New issue is that Magisk installer Zip is causing my phone to Bootloop back to TWRP. I have to flash Magisk Uninstaller and then the phone will boot normally.
[Google Pixel XL Guides, News, & Discussion] Frankelvis97:
What is Android PIE?

Is this version is now available in the public?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Is what the version now available in the public?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Did you get Magisk to install without boot looping?
[Google Pixel XL Guides, News, & Discussion] ChevyNexus:
I have not. I got it to be usable without root and had to stop tinkering for the day. May try later and see what I can do but I can't think of much else I could try besides reflashing the whole update again.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Do #4 'keep data' in the guide, then Do #8 to root

Note: When you do #8 , when twrp-3.2.3-1 boots select the Magisk uninstaller.zip for Magisk-18.1.zip, then select Add more zips and select Magisk-18.1.zip, then swipe the slider to install, then reboot.
[Google Pixel XL Guides, News, & Discussion] YogaSlackers:
Will this work with a Pixel? After a few hours of googleing and searching this forum I am still unsure where to ask this question. I have an unlocked bootloader on a Google version pixel 9.0. I need to be able to activate the hotspot feature that is blocked by verizon because I have unlimited data. What is the simplest process?

This is my second pixel. My last one ran the hotspot fine with just an unlocked bootloader and vs 8.X.

thanks for any links. Sorry to ask what seems like a simple question.

Sam
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=5371219]YogaSlackers[/MENTION]

Edit: What [MENTION=247249]crackerjack[/MENTION] said :)
[Google Pixel XL Guides, News, & Discussion] crackerjack1957:
Follow Homeboy's thread here for root with Magisk if you already haven't then go here.

https://xdaforums.com/showpost.php?p=76132374&postcount=76

https://xdaforums.com/showpost.php?p=77476133&postcount=8
[Google Pixel XL Guides, News, & Discussion] Xihexa.io:
Does anybody know how to FRP unlock this phone? I just got gifted one, but my cousin doesn't remember his pattern or login
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
FRP (Factory Reset Protection)

Have your 'cousin' call Google Support.
[Google Pixel XL Guides, News, & Discussion] camjac251:
I can't seem to get my phone to root with this method. I'm trying ElementalX-P-4.12 with Magisk-v18.1 on a Pixel XL 128GB Verizon (unlocked bootloader). TWRP boots just fine and my passcode works with it saying that the data was unencrypted. I select the twrp installer and reboot to recovery, choose elementalx first then magisk and install and reboot. But the phone seems to get stuck on the startup screen with the google logo and loading bar below it for a minute before rebooting to recovery on its own. This happened with an existing install of the January image and a clean wiped install of March with no Google Account added or wifi added, only a passcode with no fingerprint. Could it be hardware related?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
huh, no Google account. Ok. Try this:

- make sure SDK Platform-tools is updated to r28.0.2 on your computer

- flash the boot.img to both slots #6 in the guide

- do #7 after installing twrp.zip, reboot recovery

- tap install select Magisk's uninstaller.zip

- tap add more zips select the kernel

- tap add more zips select Magisk-18.1.zip.

- swipe the slider to install

- when install completes reboot system.
[Google Pixel XL Guides, News, & Discussion] camjac251:
Thank you for the fast reply. SDK Platform-tools should be latest, I double checked it with a fresh download. Although I do not have any ADB drivers. the platformtools should have its own drivers that it loads right? I messed up the first time doing it by only running the magisk uninstaller instead of adding all zips before installing, but essentially ran the uninstaller twice. I flashed the boot.img (there is also an aboot.img but didn't use that) using the command in the post. I then installed twrp.img and the zip, rebooted directly into recovery. Second time, I ran all of the Zips correctly at the same time in the order of uninstaller > kernel > magisk and did the log option on elementalx the second time. But after rebooting on both times, I get the same hanging loading screen.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Ok, try this:

- flash the boot.img to both slots #6 in the guide

Note: this time you are not installing twrp.

- fastboot boot twrp-3.2.3-1.img

- When twrp boots

- tap install select Magisk's uninstaller.zip

- tap add more zips select the kernel

- tap add more zips select Magisk-18.1.zip.

- swipe the slider to install

- when install completes reboot system.

If that doesn't work you probably need to start fresh: Do #4 'wipe data'. It is like a factory reset. Once it is done, login to Google and setup your phone. The only downside is you loose all your data and files (pics, etc.) that are not backed up on your computer.
[Google Pixel XL Guides, News, & Discussion] camjac251:
Just to confirm, this should work on the March Pixel XL (marlin-pq2a.190305.002-factory-adea2e11) image right? I had originally tried it back in January with my Google account added to the phone but read something somewhere saying that before resetting you should remove the Google account. So for this time, I had flashed the phone but kept data and removed the Google account and tried to run through the steps without any luck. I ended up clean wiping the phone last night after it didn't work with the clean install -w option. I get the same error if I don't run the TWRP installer and just run the magisk uninstaller, kernel, and magisk.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=9673473]camjac251[/MENTION]

Yes.

You're using twrp-3.2.3-1-marlin.img right?

I'm out of ideas, maybe someone else can offer suggestions.
[Google Pixel XL Guides, News, & Discussion] camjac251:
Thank you for trying at least. I might have a broken phone it seems if it can't be rooted. I tried the steps above but sadly got the same result.

This is a Verizon Google Pixel XL 128GB Very Silver running on an AT&T sim. It came with Oreo installed that I unlocked it with.

Here is what my bootloader info shows

Product/Variant: marlin-US-PVT
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Samsung
DRAM: 4096GB Hynix LPDDR4
Boot-slot: a
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED

I'm wondering if maybe it could've been when I was unlocking the phone that I messed something up.

I believe I ran

fastboot oem unlock

instead of

fastboot flashing unlock

which is used for older phones, not sure if oem redirects to flashing or not, hope so since I would have to relock to try the other.

https://source.android.com/setup/build/running#unlocking-the-bootloader
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Your fastboot mode is missing information (bootloader and baseband) see attached image.

Before you do anything else, please answer these questions:

a. Are you updated to the latest Android pie factory image (March 2019)?

b. Did you use this guide ( [How-to] Unlock bootloader on Verizon Pixel/XL by burduli) to unlock it?

c. Did you try rooting without the kernel?
[Google Pixel XL Guides, News, & Discussion] camjac251:
Yup, running the latest March 2019 Pie image, marlin-pq2a.190305.002-factory-adea2e11.

I omitted the other info in the bootloader since it might be sensitive. I see the same info though as the image you linked. That guide was what I followed to unlock the phone.

I get the same result if I try rooting with the ElementalX kernel or without, even after a complete clean reflash.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=9673473]camjac251[/MENTION]

Read the following, very carefully, do not do it without considering the risk: You could 'brick' your phone.

Additionally, if you do decide to do it pay close attention to all the Instructions: A missed step could 'brick' your phone. Further, if you do it you and only you are responsible for the good or bad results.

- - - This might work: - - -

- Factory reset your phone to ensure you are 100 percent stock.

- login to google setup your phone and reboot.

- follow #3 in this guide to lock the bootloader

- check bootloader mode to ensure the bootloader is locked.

- Use the unlock Verizon's Pixel XL thread to unlock the bootloader:

.

- check bootloader mode to ensure the bootloader is unlocked.

- root
[Google Pixel XL Guides, News, & Discussion] Xihexa.io:
I would, provided we were on good terms. Those quotation marks kinda tick me off though. What are you trying to imply? Lmao

Nah I'll figure it out though, or contact support myself.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
:eek::good::)
[Google Pixel XL Guides, News, & Discussion] camjac251:
It didn't work sadly. I had to modify the directions a bit because the oem unlock option in the developer settings was greyed out after locking the bootloader but it appeared to be enabled, not disabled. So I relocked the bootloader with my Google account added, took out my sim, and factory reset, no google account/no wifi, deleted phone app, reboot, wifi, chrome, google.com, and in dev options I was able to turn off oem unlock, then I turned it back on and rebooted to recovery to unlock again using flashing instead of oem this time. The bootloader shows that the device is unlocked (was locked before) so I kept my sim card out and setup my phone with wifi and my account. Then in the chrome app, downloaded fresh copies of twrp installer, elementalx, magisk uninstaller (didnt use it tho), and magisk 18.1 from the github. Went to bootloader, booted fresh twrp.img, installed twrp, rebooted into recovery, selected elementalx and then magisk and installed with save logs. But the same error happens. It'll load the pixel intro and the loading bar like how it is when you first setup a phone, but then it stays on that screen until it reboots into twrp. I took my IMEI and it looks like my phone was manufactured in April 2017 so maybe it might be defective if I can't root it. This was purchased back in Jan from Amazon's Certified Refurbished program through a third party seller. I checked the imei and SN and it seems to be genuine. Are there Pixel's that just won't root?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=9673473]camjac251[/MENTION]

Sorry, you weren't able to root. If there are Pixel XL that are unrootable I haven't heard about them. You have a Pixel XL right?

One last shot, try rooting with Magisk (Canary).

Go here: topjohnwu / magisk_files

Download these files:

- canary_builds/app-release.apk

- canary_builds/magisk-release.zip

- canary_builds/magisk-uninstaller.zip
[Google Pixel XL Guides, News, & Discussion] camjac251:
That didn't work either. I've started to experiment to see if custom ROMs would even work. Benzo Rom didn't work at first with installing it using my A slot in twrp. I then came across https://xdaforums.com/showpost.php?p=74974403&postcount=25 which ended up working but was installed on the B slot instead. I tried to install magisk over that B slot image but it didn't work and ended looping. Does magisk need to be flashed on both slots or just the active one? I'm confused on how the slots work and if I may have corrupted anything by overriding B if it was used for Google's update system. I've done the clean wipe to both slots to prevent any bricking.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
So, you followed the instructions to install Benzo ROM and you couldn't install it on slot a. Did you get an error or something? I'm no expert but, It seem to me that there is something wrong with your slot a. When you installed the factory image did you see any files being installed on slot a?

Also, I think you should post the quote above starting at the Benzo Rom didn't work... on the Benzo thread. They may have a solution to your problem.
[Google Pixel XL Guides, News, & Discussion] yusuo:
I have the exact same issue, my phone had a locked bootloader on EE, tried all the steps mentioned so far, other than trying the beta but just get a bootloop, everytime.

Uninstalling magisk fixes the bootloop
[Google Pixel XL Guides, News, & Discussion] fexaw:
Same issue.

Had rooted Pixel XL with Feb security updates, rooted with Magisk, but I wanted a fresh install, so for March I

followed Step #4, wipe data.

Started phone back up, logged in and set phone up.

Let play store update stock apps.

Did step #6, rebooted back to phone

Did step #7, no custom kernel - boots back to TWRP

Tried again, boots back to TWRP

Ran Magisk Uninstall - boots to phone

Tried Step #6 again, booted to phone

Did Step #8, boot to TWRP, no custom kernel, Install Magisk Uninstall, added 18.1 Magisk, rebooted, and it booted back to TWRP

It seems I am unable to root phone. Uninstalling Magisk gets me into my phone.

Platform Tools Pkg.Revision=28.0.2
[Google Pixel XL Guides, News, & Discussion] fexaw:
I was able to go back to Feb Security Release, with Platform Tools Pkg.Revision=28.0.1, doing step #4 wiping data, then Step #8 to get Magisk installed. Once I get the phone back up the way I like I may try to update to March security.

P.S. [MENTION=4810220]Homeboy76[/MENTION] you rock, I've been quietly following this post for 2 years and it's always worked.
[Google Pixel XL Guides, News, & Discussion] mushi_ami:
unable to flash

got this error while flashing the latest firmware in my pixel xl (verizon). what should i do ? what did i do wrong ? help me out !

extracting system.img (1953 MB) to disk...W/ziparchive( 8609): Zip: unable to allocate 2048663784 bytes at offset 0: No space left on device

error:

failed to extract 'system.img': I/O error
[Google Pixel XL Guides, News, & Discussion] fexaw:
Today I updated to March Security Release, with Platform Tools Pkg.Revision=28.0.2, doing step #4 keeping data, then Step #8 to get Magisk installed.

I guess there is something in stock March update that does not gel with Magisk.
[Google Pixel XL Guides, News, & Discussion] unhappybirthday:
You need to free up a couple gigabytes on your computer's hard drive.
[Google Pixel XL Guides, News, & Discussion] taadow1030:
Hello all. I've read and asked, but I'm still a bit confused. Currently, I'm on stock Pie with Magisk and Franco kernel and the latest TWRP. Can I create a backup and flash an 8.1 ROM?
[Google Pixel XL Guides, News, & Discussion] mozhno:
I have stock Pixel XL ON Pie with March update and installed Magisk 18.1, working fine.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
April 2019 dropped today.
[Google Pixel XL Guides, News, & Discussion] woody1:
Has anybody installed the April 2019 update yet? Does it require Magisk 19? Any problems with rooting after the update?
[Google Pixel XL Guides, News, & Discussion] hfmls:
Hi, how to root android Q?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Root Android Q on Google Pixel 2, Google Pixel
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Yes, after you flash the 8.1 stock factory image required by the 8.1 custom rom you want to flash.
[Google Pixel XL Guides, News, & Discussion] taadow1030:
Thanks for responding. I flashed the 8.1 stock image and tried a few ROMs. My favorite has been my current... LineageOS with Greenify. Yesterday, based on my usage pattern, I hit 6 hours screen on time. 8.1 is much faster my phone than 9.0. My normal SOT on Pie and Franco kernel is 5.
[Google Pixel XL Guides, News, & Discussion] ShadowVlican:
amazingly detailed guide! thanks a bunch

i was able to root my completely stock pixel xl (april 2019) with magisk
[Google Pixel XL Guides, News, & Discussion] ksharks:
Hello,

I wanted to give the author and posters in this thread a big thank you as your instructions are well laid out and quite clear!

I did see the boot loop issues when trying to root in Magisk that people were reporting on pages 44 & 45. This is how I got it to work hopefully it will help someone else:

(Please Note: I am not responsible if the following these instructions bricks your device, this is just what worked for me.)

I noticed when the boot loop occurred was after I had installed TWRP as my bootloader (Step 7 in the guide.) when I then flashed Magisk this resulted in the boot loop issue. I decided after restoring the device to try doing it following Step 8 instead of 7 leaving the original boot loader intact. This worked and I was able to get root without the boot loop issue. I still, however, wanted TWRP as my boot loader so I went back then followed Step 8 instructions flashing TWRP over the original bootloader "without uninstalling" Magisk. This then resulted in a boot loop, I then installed Magisk from TWRP and this solved the boot loop and the device is now working great.

-ksharks
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
:good:

Thank you! One small correction TWRP is a Custom Recovery. If you do #7 TWRP replaces the Stock Recovery. If you do #8 TWRP does not replace the Stock Recovery. :)
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
:good: Thank you! :)
[Google Pixel XL Guides, News, & Discussion] DerangedLoofah:
I saw that TWRP 3.3.0 was released. Is it safe to flash at this point?
[Google Pixel XL Guides, News, & Discussion] unknown1205:
if the phone is boot looping and i can't get into the OS to enable OEM unlocking and USB debugging, is there anything I can do?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
When asking for help, it is always a good idea to start by explaining what the problem is and what you think caused the problem. Example: I did this and the phone (Pixel XL) is boot looping.
[Google Pixel XL Guides, News, & Discussion] unknown1205:
its my gf's pixel that i gave to her. she said it just started boot looping one day.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Can you get to fastboot mode?

Try this:

- Turn the phone off and put it on the charger until it is fully charged.

- Press the Power and Volume Down buttons until you see Start

- Then do #4 'keep data' in the Pixel XL guide.

Note: Download files fo the Pixel
[Google Pixel XL Guides, News, & Discussion] MichPRich:
Are you able to access the bootloader?

If yes, then yes

If no, then no.

Hold (Power+Vol.Down) until phone boots.

This should begin the standard boot w splash, but bypass/stop short of the OS and from there you would determine how to unbrick. But if [no bootloader] then [/brick] and [/fubard].
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Did you try my suggestion or [MENTION=5183327]MichPRich[/MENTION] suggestion?
[Google Pixel XL Guides, News, & Discussion] unknown1205:
when i initially posted the issue, the phone was not in my hands, i just wanted to get some info for when i do get the phone from my gf.

now that i got it, i was able to fiddle around with it by going into fastboot and stock recovery, then the phone finally booted into the OS. i was able to enable OEM unlocking through the OS and then do a clean wipe on her phone and also install TWRP incase she has issues in the future. thanks everyone.
[Google Pixel XL Guides, News, & Discussion] JU57US:
Anyone else having a problem with booting TWRP 3.3.0? I've tried 3 times rebooting now and each time I can't get past the password. I tried a PIN twice, per the norm, and a password the last time (after booting to system and changing it). It just says that the password is not recognized.

Just tried using TWRP 3.2.3.1 and get the same problem. Password unrecognized no matter what.
[Google Pixel XL Guides, News, & Discussion] taadow1030:
Have you tried removing your pin/ password prior to booting into TWRP? I've read where some people had to do that before TWRP allowed them access. I'm not sure of what version of TWRP they were using though.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
twrp-3.3.0-0

- fastboot boot twrp.img (twrp is the full name of the twrp file).

- "I tried tried PIN twice... The same pin you use to unlock your phone?

- What version of Android are you using?
[Google Pixel XL Guides, News, & Discussion] JU57US:
Yes, the PIN that locks my phone. Using the May 19 factory image, just flashed right before starting the re-root process.

Edit: If I remove my PIN completely, TWRP boots and doesn't ask for my PIN/Password at all. Thus, I can't see that anything is decrypted, or needed to be decrypted. In doing that case, can I install Magisk at that point? Or do I absolutely need to set a PIN/Password before booting TWRP?