yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] bigsyd:
I was on Android 8.1.

Decided to download the Android 9 image and upgrade.

When I do an Install with the -w option in the flash-all.bat, I get the message seen in the attached jpg file.

If I do an install without the -w, it completes a dirty install and Android 9 is now running on my Pixel XL.

I would prefer to do a clean install. How should I deal with this error I'm receiving.?

the complete command window is shown in the attached jpg

https://www.dropbox.com/s/ku1wxhhjj3ant3z/InstallPie.jpg?dl=0
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
That's because with the -w it is like doing a factory reset. it wipes your Pixel XL's internal storage (look at the 'Note' #4 C. 2. a.). See jpg: Fourth line from the bottom:

wiping data

. Your internal storage should be empty, so it can't find the files because they are not there Go to Settings > Systems > Advance > Reset options > Erase all data (factory reset) when it finishes resetting. log into Google and update to android 9.0.0 via OTA. Then do #7 or #8 if you want to root, but before you do. Get the latest SDK Platfrom-tools r28.0.1, the link is in the OP 'Prerequisites b'.
[Google Pixel XL Guides, News, & Discussion] bigsyd:
That is correct. I was following the instructions for conducting a wipe when doing a flash-all via the image method. I want the phone to be "clean" going from 8.1 to 9.0

I was thinking the -w would wipe out everything and give me a clean install from scratch. Are you saying it can't wipe and complete the install because the internal storage is encrypted?

So, once I decrypt using your instructions, I should be able to use the -w option? Or, I'm better off doing an OTA. It has already completed an install of Android 9 maintaining all of my apps and data and settings.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Your thinking was correct, that is what should have happened.

So once... No.

If you installed the pie factory image, with the -w in the flash-all.bat file and it did not wipe your data and internal storage it was a 'nevermind'.

If pie is working and you're happy with the installation. Enjoy some pie.
[Google Pixel XL Guides, News, & Discussion] bigsyd:
Well, yes, I did get Pie to install and run by removing the -w wipe option. I'm happy it's running. Just not pleased that I don't have a clean install.

I'll keep searching to try and find a way to wipe.

Thanks for your help.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Go to Settings > Systems > Advance > Reset options > Erase all data (factory reset) when it finishes resetting. log into Google and update to android 9.0.0 via OTA. Then do #7 or #8 if you want to root, but before you do. Get the latest SDK Platfrom-tools r28.0.1, the link is in the OP 'Prerequisites b'.
[Google Pixel XL Guides, News, & Discussion] H0wdy:
Ok, I saw some possible solutions here, but they didn't work for me.

I had the reboot problem, so I did magisk 17.1 uninstall a while back. I left TWRP installed.

After what I read here, I just booted into twrp, went to settings, unchecked the two things, and installed magisk 17.1 zip.

Same bootloop problem :( Having to go ahead and uninstall magisk again.
[Google Pixel XL Guides, News, & Discussion] epazot:
Why do you have people installing the factory image TWICE? Step 3B and 4C are redundant, aren't they? That's unclear with the way this guide is written. And why flash the boot image after this in step 6?

In my opinion you'll find a much better general guide here: https://xdaforums.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
No.

These are not steps, you don't do them 1 through 13. They are individual sets of instructions . There are 13 sets of instructions. You do the set(s) that apply to your need(s).

#3B is for people who want to return there phone to stock.

#4 is for people who want to install a factory image.

Additionally, the link you posted is primarily for people who are installing Custom ROMS.

Opinions are like noses everybody has one. So, I do not need yours
[Google Pixel XL Guides, News, & Discussion] H0wdy:
Can you please tell me what to do for my situation :(
[Google Pixel XL Guides, News, & Discussion] zosX:
Hello. Using the latest stable magisk and TWRP here.

I tried this before with the beta magisk that supported 9 and I'm still having the same issue as before.

This is all on slot B btw which is what it defaults to after a factory flash it seems.

1. Full wipe/factory image flash

2. Boot TWRP img

3. Install TWRP via ADB sideload which flashes A and B

4. I did run magisk unistaller on my last attempt here to to avoid any lingering problems possibly.

5. Install Magisk 17.1.

6. Bootloop to recovery every single time

I've gone through this guide step by step twice now today and I get the same result I did when Pie first because stable.

There seems to be no way to install magisk and TWRP together. If someone has a solution.....i'll be waiting.....
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
This was not in my instructions: "Install TWRP via ADB sideload..."

Just follow the instructions.

Don't add your 'twist' to the instructions and then wonder why the instructions did not work.

a. fastboot the boot.img (from the September 2018 factory image for 'marlin') to both slots (See #6)

b. fastboot boot twrp.img

c. Install twrp.zip with twrp.

d. install magisk's uninstaller.zip with twrp.

e. install magisk-17.1.zip with twrp.

f. reboot system
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
I don't know what to tell you. :rolleyes:

a. Are using a Linux computer?

b. Which Linux and what version?

c. Is java installed?

d. Did you load the lib(s)

e. Do you have the latest Linux SDK Platform-tools (r28.0.1)?

The link is in the OP: Prerequisites b.

f. Are you adding this / in front of your commands i.e.

/fastboot boot twrp...img. I think Linux requires it.
[Google Pixel XL Guides, News, & Discussion] Phalanx7621:
So I'm not exactly sure why people suggest that you jump through hoops, but there are easier ways to achieve what you're trying to do. make sure you have the latest factory image for the pixel XL. Boot into your bootloader, and use fastboot to wipe your partitions.

> fastboot erase cache > fastboot erase system > fastboot erase userdata

Afterwards using either command line or Windows Powershell, run fastboot flash-all.bat (this is assuming that you placed the factory image that you want the flash in the same folder as ADB and fastboot are located). If you are running Windows Powershell you have to run the command like this ./ fastboot flash-all.bat (or .\ can't remember which way the slash faces) as far as I know there's no reason why it shouldn't work, but just in case you may wanna run either one as administrator although it's not and shouldn't be necessary. This is just how I would suggest doing it because even if the flash old. Back command doesn't work properly and you have to remove the -w it's okay because you just wiped previously with fastboot so it will be clean.

Edit: if you don't want to use fastboot to do this and do it all in one steps you can of course boot TWRP and then use TWRP to wipe as well, if the desire is simply wipe the phone clean before flashing.
[Google Pixel XL Guides, News, & Discussion] bigsyd:
Thank you very much for your time and effort. I will give that a shot today.
[Google Pixel XL Guides, News, & Discussion] H0wdy:
I do use Linux, Fedora 28 64bit, java, latest platform tools.

However, I'm getting the exact same results when I boot into TWRP and flash zip files.
[Google Pixel XL Guides, News, & Discussion] zosX:
I also tried it from within TWRP yesterday. It honestly should make zero difference how it is installed. The end result is the same. It bootloops to recovery.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Some Pixel XL are having the bootloop problem. I don't know why, they are having it. It doesn't seem to matter what method they use to root. The result is still the same.

Did you try Phalanx7621 method?
[Google Pixel XL Guides, News, & Discussion] zosX:
I've tried every method I could. I tried this several times now. Its not me. Before flashing Magisk WITHOUT installign TWRP worked. At least with the last beta. This doesn't seem to be the case anymore. What's really frustrating is that it is obviously working fine for some people and others it is not. There should be no reason for it not to be universal. I tried flashing a new factory image to the A slot and then I ran the latest update zip and it defaults to slot B after that. Probably when the update is run. If its booting off of slot B, then that should be where magisk should get installed, right? That's where it install by default. TWRP flashes both slots but magisk does not.

Something's wrong.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=4244154]H0wdy[/MENTION]

I asked for the Linux information so I could help you find a solution. All my searches confirmed you are doing everything right. I hope someone else has a solution that will solve the boot looping problem. :(

Edit: Try zosX steps on page 25 he is rooted.
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
tried installing one then rebooting recovery the install the next?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
You're right, something is wrong rooting Pixel XL phones should be universal. I have no clue as to what is wrong nor why rooting it is not universal for all Pixel XL.

Have you tried flashing Kantjer's Unofficial Magisk build (#9 )?
[Google Pixel XL Guides, News, & Discussion] zosX:
Yes. I typically reboot between installs. At least now I do. Before I would just load all the zips and one and let them flash over.

---------- Post added at 06:47 AM ---------- Previous post was at 06:46 AM ----------

No. I've only tried the stock magisk. I was assuming that the problem I had before would have been fixed by the time it left beta. Sadly the beta was the only one that worked for me. Maybe I'll go back and retry that sometime. I've held 3 pixel phones in the last few months and it did this one all of them.
[Google Pixel XL Guides, News, & Discussion] zosX:
I filed a bug report over at github. Hopefully that will escalate this.
[Google Pixel XL Guides, News, & Discussion] Phalanx7621:
I only ever use Magisk beta, I was assuming that was what you were using as well. If you haven't, I would download that and give it a try
[Google Pixel XL Guides, News, & Discussion] zosX:
The maintainer told me that I'm doing something wrong and closed the bug report. Claims he has a Pixel XL as a daily driver. I'll try the beta. This is kind of frustrating. I've followed the instructions in this thread step by step several times and I just end up with a bootloop.

Its not like its complicated. Boot TWRP ---> Flash Magisk right? I mean there's really no way to screw that up.
[Google Pixel XL Guides, News, & Discussion] aankkurr:
Boot TWRP > flash latest Magisk Uninstaller > flash latest Magisk
[Google Pixel XL Guides, News, & Discussion] zosX:
Yeah. I just did that. I tried both 17.1 and 17.2. No dice.
[Google Pixel XL Guides, News, & Discussion] aankkurr:
I had same problem like you, but doing this has solved this issue on 5 of my PXL. Last thing i can suggest is make sure you are on slot b
[Google Pixel XL Guides, News, & Discussion] zosX:
I flashed the boot.img back over and booted TWRP manually. Then I ran the uninstaller and then I tried 17.1, 17.2, AND 17.3 Debug. All give me a boot loop with or without TWRP installed. I also tried removing the pin and running the installer with no pin. Same deal.

---------- Post added at 11:44 AM ---------- Previous post was at 11:37 AM ----------

I'm on slot B. I flashed this six ways to Sunday and it still doesn't work. I honestly don't know what else I can try asides from re-flashing the factory image for the fourth time and starting over from scratch. I don't see why that would give me a different result after doing the same steps four times now.
[Google Pixel XL Guides, News, & Discussion] zosX:
WHOAH. I got it to work ladies and gentleman.

This one was frustrating.

I went back to the old technique of removing the pin and google user. So the steps I took were as follows:

1. Remove google user and pin

2. Install Magisk ----> Bootloop

3. Flash factory rom

4. Still bootlooping....OK...Factory Reset

5. OK it Boots.

6. Magisk Uninstaller just to clear out anything lingering

7. Boot TWRP via fastboot

8. Sideload magisk.17.1.zip

9. Reboot but DO NOT install TWRP in system when it asks

(I honestly think that was where I was going wrong here because I always swipe it out of habit when it prompts me. I've been flashing for a decade now....)

10. You should have a fresh clean factory install that is now rooted.

Try those steps!
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
:good::)

So, you didn't install twrp? You just did steps 6-9 got root?

[MENTION=3187474]zosX[/MENTION]

Edit:

Would you, please, elaborate on "9. Reboot but DO NOT install TWRP in system when it asks" for others who are having the boot looping issue?
[Google Pixel XL Guides, News, & Discussion] roman.ramirez.12:
I think what he means is when you finish flashing and you press reboot. At the last screen the last option it gives you is to install TW RP as a system app. You will see the button" do not install" and then you'll see the swipe bar on the bottom. Do not swipe. Just press the button that says do not install.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
:good::)
[Google Pixel XL Guides, News, & Discussion] Phalanx7621:
I didn't know people were doing that , that may solve a lot of people's problems. I've always said no to that because I was flashing TWRP so why would I install it again ? Just my thoughts.
[Google Pixel XL Guides, News, & Discussion] big blue:
So I flashed the October image after removing the -w flag from the script, rebooted and let it finish system update, reboot bootloader, fastboot boot twrp.img {3.2.3-1 pretty sure that's the latest) flashed magisk 17.2 (same as on September image) I prefer not to flash twrp, I just boot the image when I need recovery. Reboot system. Anyway everything is fine, I have root and everything. But when I run SafetyNet I get an api error. See screenshot. I even installed magisk again with patched boot method reboot and still same outcome. I just need SafetyNet for some banking apps is all. And I know I should probably start over adding the -w flag back into the script. But I just don't have the time for a complete wipe and restore today. Not the end of the world so I'll just hang tight read some other people's experiences here, over on the magisk thread and I'll look through the twrp threads. Thought I'd ask here though... Has anyone been able to get SafetyNet working on October image.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Turn on 'Magisk Hide' restart Magisk and check it.

Are you using Exposed?

Read this: Magisk and Magisk Hide Installation and Troubleshooting guide
[Google Pixel XL Guides, News, & Discussion] big blue:
Thanks...yes Magisk-hide was checked. No exposed modules here. I actually just clean wiped it last night. It was really starting to bog down anyway. I'd been dirty flashing since like beta 2 so it was time. Much better now. Thanks for the help :good:
[Google Pixel XL Guides, News, & Discussion] PrettyPistol555:
Where are the Driver Binaries used?

I searched through EVERY step, nothing...
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
They are not used in any of the sets of instructions.

Go to 'Prerequisite b.' tap the Factory link, tap the menu on that page, tap Driver Binaries read.
[Google Pixel XL Guides, News, & Discussion] H0wdy:
I can't remember, where does it ask if you want to install it as a system app again? I can't remember where I get that prompt.
[Google Pixel XL Guides, News, & Discussion] Phalanx7621:
Before you reboot into the system after installing TWRP for the first time
[Google Pixel XL Guides, News, & Discussion] H0wdy:
Well,

I got it rooted!

I downloaded marlin for October. I did flash-all, but I removed -w.

I then rebooted to bootloader, booted twrp. ACCIDENTALLY flashed twrp zip, but I had unchecked "reboot after" in preferences.

I then went into TWRP settings and hit restore defaults, but then removed all checkmarks afterward.

I then flashed magisk 17.1 . I did NOT wipe cache. I then hit home, and reboot system, and it worked.

Is there an easy way to hide root from bank apps now?
[Google Pixel XL Guides, News, & Discussion] defens23:
I used this thread to hide root from my banking apps. Chase Pay especially.

https://xdaforums.com/apps/magisk/magisk-banking-app-story-t3741951

---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------

I found this thread using XDA search. I want to give my Pixel XL to my son. I need to lock the bootloader, remove root, and return to stock. I am on Google Pie 9.*. I just updated to the October 2018 security update. I am also using Magisk. Will the instructions on the first page work for what I need to do?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
https://www.didgeridoohan.com/magisk/HomePage
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
#3 b and c should work
[Google Pixel XL Guides, News, & Discussion] defens23:
I looked at those. Thank you for confirming.
[Google Pixel XL Guides, News, & Discussion] HueyT:
Thank you for this guide. I'm not a newbie but new to Pixel XL (marlin). Other phones included Nexus 6, LG G2, LG G6, Moto G4, etc. This dual slot thing is driving me nuts. I was able to install custom roms and back them up fine in TWRP, but I can't seem to restore them on latest official TWRP 3.2.3.1. I backed up \boot, \system, \vendor, \data, \efs. Yet, when I clean wipe (from slot A) and then restore (still on slot A) \boot, \system\, \data, and reboot phone would hang at the white "Google" splash screen with the "unlock" icon at the bottom of screen and then eventually go back to twrp. I can mount all partitions and look at the \system section with all files inside that partition (restore was successful). I can decrypt with TWRP using my 4 digit pin just fine.

Please help as it's driving me crazy as I can't restore any of my backup. I would have to reinstall the rom from the zip and then restore backed up TWRP \data partitions and then it'll work. It should restore the whole rom from TWRP without having to redownload and reinstall the rom zip everytime I want to restore my backe dup rom.

Thanks in advance.
[Google Pixel XL Guides, News, & Discussion] tomek21:
Telus vs Regular Image

My current carrier is Koodo which is a Telus discount brand, but I got my phone used online, so it probably wasn't a Telus phone originally.

Which image should I use? I'm not sure if it's hardware dependent, or current carrier dependent.

Thanks!
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Did you back up boot, system image, vendor image, data, and EFS?

If yes, do 4 'Keep Data', fastboot twrp-3.2.3-1.img, tap backup, tap restore, select backup file, swipe to restore.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
¯\_(ツ)_/¯
[Google Pixel XL Guides, News, & Discussion] HueyT:
In other words, I must restore data using fastboot boot twrp.img from a PC and restore from that temporary twrp image instead of trying to restore from the permanent TWRP 3.2.3.1 recovery already install on my phone?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
"Telus Discount"

9.0.0 (PPR1.181005.003, Oct 2018, Telus Only)
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
No!

Boot bootloader (What slot is it on? Do not change slots.) > use up or down volume key to 'Recovery mode' > press power > when twrp opens > enter pin > tap backup > tap restore > select backup > swipe to restore.

Note: If you backed up your Pixel XL phone with twrp-3.2.3-1. You should restore it with twrp-3.2.3-1
[Google Pixel XL Guides, News, & Discussion] HueyT:
So as long as I backed up all partitions, including \boot, \system, \system image, \vendor, \vendor image, \data and restoring ALL partitions, I can restore from TWRP 3.2.3.1 already installed on my phone? SlotA means stay on slot A to restore? Correct?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
The only partitions you need to back up are:

boot, system image, vendor image, data and EFS (look at #13 A.)

If you have added the system and vendor that may be the cause of the bootloop.

You can restore in twrp-3.2.3-1 if you made the backup with twrp-3.2.3-1.
[Google Pixel XL Guides, News, & Discussion] HueyT:
Yep, this is it. Thank you. Going back to make backups correctly. Pixel XL needs only \vendor img and \system img, and won't work with just \vendor and \system (or both \vendor img and \vendor, \system img and \system). Most other phones are fine with just \system and \vendor (but marlin is not like most phones) :good:
[Google Pixel XL Guides, News, & Discussion] mrkkk:
I want to root just so that titanium backup works

What steps must I take and which ones can I avoid?
[Google Pixel XL Guides, News, & Discussion] tomek21:
I'm really curious why out of all the other carriers out there, Telus is the only one with it's own separate image.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
I do not know.
[Google Pixel XL Guides, News, & Discussion] csh8428:
What should I know coming PureNexus 7.1.2 SuperSU root to Magisk?

It's been a while since I've loaded a custom ROM. I've been on PureNexus 7.1.2 ,PureKernal 3.18.31 for several years that I rooted with SuperSU. Bootloader is unlocked.

Is there anything different/additional I would need to do given what I'm coming from and going to this ROM or can I just follow the instructions in the OP?

Thanks,

Craig
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Double post, posted on LquidRemix.
[Google Pixel XL Guides, News, & Discussion] dan133714:
Hi, I have the original pixel (not XL) so I have been following this guide with the exception of loading the correct pixel files (sailfish) instead of the pixel XL files.

I had a stock pixel with android pie and the latest oct 2018 OTA update. I've followed the guide, downloaded the latest oct 2018 patch android pie factory image, installed that (with the -w removed so as not to lose all my data). I already had a PIN set so I then fastbooted the latest twrp img, installed twrp zip, ran the magisk uninstall anyway, and rebooted into recovery again. I then installed the latest magisk (17.2).

When it reboots it gets stuck in a bootloop. If I install the uninstall magisk zip my phone boots up into the system correctly. I've tried multiple times and tried magisk 17.1 as well. I just can't seem to get magisk installed without a bootloop.

I don't want to install a custom ROM or kernel, do I have to and is that why I'm getting this bootloop?

Any ideas?

Thanks
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Read Page25 zosX post.
[Google Pixel XL Guides, News, & Discussion] 1xdroid:
I have a successfullly rooted pixel xl. I haven't done anything since august to the phone. A couple questions. I noticed there's an october update to the the Pie software. I have watched videos and read several threads on how to update the software, but i was wondering the way you guys recommend to do it. Is there anyway to update it and keep root and apps? Also the version of TWRP i had was 3.2.3-0 and when i tried to install it my phone got encrypted and it wanted a password to decrypt it so i just fastbooted twrp with no install. Was the issue resolved in the 3.2.3-1 version? Does anyone know is it safe to install now? Also what's the difference in the adnroid pie software 9.0.0 (PPR1.181005.003, Oct 2018, Telus Only) and 9.0.0 (PPR2.181005.003, Oct 2018)? Which one do i use, i don't know what telus is. Should i use full ota images or factory image when just updating software, what's the difference? Thanks.