Database Users

[GUIDE] Unlock/Root/Flash for Nexus 5X

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
[SIZE=+2]Nexus 5X[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Nexus 5X. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
If you're unsure about something please read the FAQ section in post #2 before creating a post to ask a question.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Below are two options for install.
Please do not install adb/fastboot via any means other than the Android SDK, using other tools (like Minimal adb & fastboot) can lead to an outdated setup and various problems with flashing. You've been warned, other tools will not be supported in this thread.
Option A
Google hosts ADB/Fastboot (platform-tools) for Windows, OSX, and Linux. This is a minimal download, in contrast to Option 2. These links and file sizes may be updated periodically by Google. If using Windows, download the Google USB Driver and follow the driver install instructions. Once you have downloaded the platform-tools zip, extract the file then transfer the platform-tools folder to your desktop. The platform-tools folder contains adb, fastboot, and several other files. Note that clicking any link for platform-tools will immediately start a download.
*Windows: platform-tools. Google USB Driver install.
*OSX: platform-tools. For additional details on how to use OSX and adb/fastboot commands, see post #3.
*Linux: platform-tools.
See Option B below for old method to install adb/fastboot:
Option B
Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Repository, Google USB Driver
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide.
For Option A and B, make sure adb is correctly installed. Open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Quick Tips[/SIZE]
How to boot into the bootloader:
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
How to boot into recovery:
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Decrypt Your Data Partition
How To Make A Nandroid Backup With TWRP Recovery
How To Make An EFS Backup With TWRP Recovery
How To Root
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Update To A New Build Of The Stock ROM
How To Flash The Factory Images (Return To Stock)
How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
FAQ can be found in post #2!
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into Settings/About Phone, scroll down and click on ?build number? continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the ?Enable OEM Unlock? checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Power off your phone then boot into the bootloader (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.​
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem unlock
This will erase all user data from the device!
You should now see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to confirm if you're sure you want to go ahead.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
Allow everything to go ahead and once finished you can disconnect your usb cable.
Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock.
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader (section 1). Please read FAQ #7 if using TWRP 3.0.2-1 or 3.0.2-2.
Download TWRP Recovery onto your PC.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Power off your phone then boot into the bootloader (power + volume down).
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot flash recovery filename.img
(The recovery filename in the command will change depending on which recovery you're flashing)
Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader, use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable. If using Nougat 7.0 or newer, you must now boot directly into TWRP and flash SuperSU (or your preferred root alternative) so that TWRP will persist between reboots.
When TWRP boots up you'll be asked whether you want to allow system modifications or to keep it read-only, choose to allow system modifications, there's no benefit to keeping it read-only.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.
Some users need a custom recovery for a temporary period, so they live boot the recovery. In this scenario, the custom recovery replaces the stock recovery until a reboot is performed. Place the file in your fastboot folder then enter this command:
Code:
fastboot boot filename.img
(The recovery filename in the command will change depending on which recovery you're flashing)
[SIZE=+1]3. How To Decrypt Your Data Partition[/SIZE]
This is no longer necessary as long as you use TWRP 2.8.7.1 or newer
Prerequisites: unlocked bootloader (section 1).
TWRP recovery cannot decrypt your data partition at this stage. In order for TWRP to be able to read/write on your data partition (to root or create a nandroid backup) you will need to format it, a format will remove encryption.
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot format userdata
Please note: this will erase all user data from the device!
Once the process has completed you can either reboot normally:
Code:
fastboot reboot
Or you can reboot back to the bootloader in order to undertake another task:
Code:
fastboot reboot-bootloader
[SIZE=+1]4. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]5. How To Make An EFS Backup With TWRP Recovery[/SIZE]
An EFS backup is very important to have, if your EFS partition becomes corrupt you will have no IMEI, and therefore will not be able to use the phone as a phone. Making an EFS backup is insurance against this catastrophic event. Without a backup, restoring your EFS can be extremely difficult or impossible. The backup you create can be easily restored using the restore tool in TWRP recovery.
Please read FAQ #7 if using TWRP 3.0.2-1 or 3.0.2-2. Boot into TWRP and select the backup option from the TWRP home screen, make sure only the EFS box is selected, and swipe to backup. The process will take a few seconds. Keep a copy of the backup on your phone and also keep another copy somewhere safe.
[SIZE=+1]6. How To Root[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest root method of your choosing to your phone:
Magisk
SuperSU Stable
SuperSU Service Release (SuperSU beta channel)
Or to root Android Nougat 7.0 visit this thread: Use SuperSU 2.78 or newer.
[WIP] Android N Preview
Boot into TWRP recovery and enter the install menu.
Navigate to where you have SuperSU stored on your internal storage and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this. You do have root, ignore this every time it comes up.
[SIZE=+1]7. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2), vendor.img (section 9).
Installing a ROM is a straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above). Next, install the vendor.img that matches the Google security OTA that the ROM you want to install is based on. Find the vendor.img inside the factory images provided by Google then flash this file with fastboot (section 9).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Select the wipe option from the TWRP home screen.
Perform a Factory Reset.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]8. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, EX Kernel Manager, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]9. How To Update To A New Build Of The Stock ROM[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This method does not wipe your data, so you will keep your apps and settings. You should have no problems, however, if you experience problems you may need to perform a factory reset and flash again. Make a backup first and transfer it to your PC.
Download the latest build via the appropriate factory images for your model (Nexus 5X/Bullhead) here.
Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
You can skip flashing the recovery if you wish, but even if you do the stock recovery may be patched on the first boot anyway. So you'll need to flash TWRP and SuperSU again if you need/want those, as well as any other system modifications you may have had.
You'll have to flash SuperSU again now, plus add any mods that you previously had.
[SIZE=+1]10. How To Flash The Factory Images (And Return To Stock)[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
Go to Settings/Backup & Reset and perform a factory data reset. This will remove all of your user data from the device (apps, settings, photos, music, etc).
Download the appropriate factory images for your model here.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
If you wish to you can also relock the bootloader with this command:
Code:
fastboot oem lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all data on an encrypted device.
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
[SIZE=+1]11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2). Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
This section will explain how to return the phone to be like it was when it came out of the box, except it will not wipe any of your personal data (photos, music, etc) from the internal storage.
Download the appropriate factory images for your model here.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into TWRP recovery and enter the wipe menu, select advanced wipe, check only the data box and swipe to wipe.
Go to the TWRP main menu and enter the reboot menu, select bootloader. The phone will now boot into the bootloader, once it has you can connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
FAQ can be found in post #2!
Donate To Me

[size=+1]Frequently Asked Questions[/size]
1. How do I boot into the bootloader?
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
2. How do I boot into recovery?
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
3. When issuing the fastboot flashing unlock command it doesn't work, I only get a list of possible commands. What's going on?
This is usually due to having an outdated adb/fastboot setup. If you installed adb/fastboot by any means other than via the Android SDK this is probably the cause. Visit the prerequisites section in the beginning of this guide to properly install adb/fastboot and ensure that it's up to date.
4. How do I take an OTA or update if I have root or other system modifications on the stock ROM?
You can't take an OTA update while you have root or any system modifications. You'd need to use fastboot to flash the system, boot, and recovery images. It's much easier to just flash the newer build with fastboot, see section 9 of this guide for full instructions.
5. Does taking an OTA update wipe my user data?
No, it doesn't.
6. Do I need to make an EFS backup?
Absolutely yes. An EFS backup is extremely important. If your EFS partition becomes corrupt, your IMEI will disappear and you will not be able to use the phone as a phone. Without a backup it can be extremely difficult (or impossible) to restore your EFS. See the next question for an EFS backup related issue and solution.
7. I have a bootloop after restoring my EFS backup in TWRP 3.0.2-1. What can I do?
TWRP 3.0.2-1 and 3.0.2-2 are the first official TWRP releases with Nougat 7.0 or newer compatibility. Unfortunately, there are separate bugs affecting TWRP 3.0.2-1 and 3.0.2-2. A member of the TWRP development team details these issues right here. This link redirects to a thread in the Nexus 6P forums but also applies to the Nexus 5X. Read the original post of that same thread to learn how to resolve this EFS restore bootloop. You must use ADB and the phone must be booted in TWRP to resolve this issue. These ADB commands work on the Nexus 5X and 6P.
8. Can I flash just the xxxxxx.img from the factory image without losing my data?
Flashing userdata.img will format your entire phone (personal data including SMS/MMS, pictures, downloaded files, etc). You can flash any combination of these partitions (boot, system, vendor, radio, or bootloader) and this will leave your personal data intact. However, any mods that you have installed into system, vendor, or boot will be overwritten and returned to the default factory image setup when you flash these partitions. Flashing recovery.img or a newer version of your custom recovery will replace your existing recovery.
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning indicates a mismatched vendor and system partition. The vendor partition was formerly integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS build and monthly security update. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line. These will always match up with the factory image of the same Android build (six digit alphanumeric name) for this device.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone that regularly receive updates to resolve security risks. If you are a custom rom user, make sure that you flash the vendor.img for the Google monthly security update that you are moving to. Be aware that sometimes AOSP roms utilize the AOSP master branch which has a newer Android build than the monthly security update for this device. You will still need to install that month's vendor.img.
The phone will fail to boot if you mismatch the vendor.img with a different Android version. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat. The vendor.img is typically not included in the custom rom zip but is often available as a separate download in the custom rom thread's first post.

Reserved #2

Reserved #3

OSX, ADB and Fastboot commands!
So you use OSX and would like to use ADB/fastboot, unlock, root, or simply have a working knowledge of your phone. Welcome! Most of the information in the guide above applies to OSX, however there are a few key changes.
Google hosts ADB/Fastboot (platform-tools) for Windows, OSX, and Linux. This is a minimal download, however these links and file sizes may be updated periodically by Google. Download the OSX platform-tools. Note that clicking the link for platform-tools will immediately start a download.
*OSX: platform-tools.
Once you have downloaded the platform-tools zip, extract the file then transfer the platform-tools folder to your desktop. The platform-tools folder contains adb, fastboot, and several other files.
To make sure your ADB is installed correctly, open a terminal command prompt and issue this cd command (change directory) to the platform-tools folder:
Code:
cd /users/username/desktop/platform-tools
then issue this command to check your adb version:
Code:
./adb version
If it returns a version number for Android Debug Bridge then you're good to go.
Using ADB/Fastboot commands
OSX natively requires "./" to prefix any ADB or Fastboot commands. If following the guide in post #1, commands issued in OSX must be written as follows ./adb [command] or ./fastboot [command]. Below are example scenarios.
To check if your device sees ADB, enable USB Debugging from within Android in Settings/Developer options. Go into Settings/About Phone, scroll down and click on build number continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and enable USB Debugging.
Code:
./adb devices
It should return your device serial number, if so, adb is working.
Reboot into the bootloader:
Code:
./adb reboot bootloader
Reboot into the recovery:
Code:
./adb reboot recovery
Fastboot commands must be performed while in the bootloader. Power off your phone then boot into the bootloader (power + volume down). Below are some example OSX fastboot commands that can be used throughout the guide:
Check if your device sees fastboot:
Code:
./fastboot devices
Install a factory image:
cd into the platform-tools folder with the following command:
Code:
cd /users/username/desktop/platform-tools
Now enter commands to flash a factory image:
Code:
./fastboot flash bootloader /users/username/desktop/bullhead/images/bootloader-bullhead-bullhead-xx.xx.img
./fastboot reboot-bootloader
./fastboot flash radio /users/username/desktop/bullhead/images/radio-bullhead-bullhead-xx.xx.img
./fastboot reboot-bootloader
./fastboot flash boot /users/username/desktop/bullhead/images/boot.img
./fastboot erase cache
./fastboot flash cache /users/username/desktop/bullhead/images/cache.img
./fastboot flash recovery /users/username/desktop/bullhead/images/recovery.img
./fastboot flash system /users/username/desktop/bullhead/images/system.img
./fastboot flash vendor /users/username/desktop/bullhead/images/vendor.img

@Heisenberg you mind if i create an index thread?

reyscott1968 said:
@Heisenberg you mind if i create an index thread?
Click to expand...
Click to collapse
Go right ahead, first in best dressed as far as I'm concerned. It is a fair bit of work to keep an index maintained though, as long as you're aware. There's a new template for indexes too, using your Google goggles you should be able to track it down pretty easily.

Heisenberg said:
Go right ahead, first in best dressed as far as I'm concerned. It is a fair bit of work to keep an index maintained though, as long as you're aware. There's a new template for indexes too, using your Google goggles you should be able to track it down pretty easily.
Click to expand...
Click to collapse
il take note.. il update the thread once im back on my pc.. now still at work ...

Deleted...
Should have read the first lines in the OP

Cant wait, should have mine around october 30th.

Might want to point out the cable /adapter required to connect to pc. (I just saw that it's not included with the phone.)

AquilaDroid said:
Might want to point out the cable /adapter required to connect to pc. (I just saw that it's not included with the phone.)
Click to expand...
Click to collapse
I picked up a few of these to get me by for now until the price of Type-C goes down a bit http://www.ebay.com/itm/381344035966

I ordered one along with my phone, will be helpful for flashing.

Thanks, a friend of mine pre order this phone, I'll follow these steps

Thanks for starting this, these were some of the most helpful threads in the N5 forum.
For Mac users who have upgraded to El Capitan, the adb/fastboot installation doesn't necessarily work perfectly right now. I'm sure the Android SDK package will update for this, but in the mean time:
Install adb/fastboot as usual similar to this thread, or for specifics:
http://forum.xda-developers.com/showthread.php?t=1917237
but, once you test this with [adb devices] or [fastboot devices] you'll most likely get a command not found error.
You'll need to add a line to your ~/.bash_profile, per this reddit thread
add the following line to your ~/.bash_profile, changing username to your mac username
Code:
export PATH="/usr/local/lib/node_modules:/usr/local/apache-maven-3.0.3/bin:/Users/[B]username[/B]/.composer/vendor/bin:/Users/[B]username[/B]/Library/Android/sdk/platform-tools:$PATH"
exit, save, then run
Code:
source ~/.bash_profile
then adb/fastboot should be good to go like before!

OP has best username ever
Sent from my Nexus 5 using Tapatalk

Doesn't work!
Code:
C:\Users\Kevin\Downloads\Nexus 5x>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.017s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.014s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.020s]
finished. total time: 0.022s

The-Kevster said:
Doesn't work!
Click to expand...
Click to collapse
Did you allow OEM Unlock in developer options?
Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Click to expand...
Click to collapse

Does the 5X have the hardware QFuse that that pops when you unlock the bootloader like the 6P?

KidWave said:
Does the 5X have the hardware QFuse that that pops when you unlock the bootloader like the 6P?
Click to expand...
Click to collapse
They both use Qualcomm based chips so yes the same thing would happen on the 5X.

[Guide] Pixel XL Android 7(Nougat) Unlock/Install Stock Images + Kernels/Recovery +

[Guide] Pixel XL Android 7.1.2 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2017 Security Patch​
Intro
This thread is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel/Pixel XL'.
It also works for Pixel owners: If, they download the correct files for their Pixel.
This Guide is not for use with the Second Generation Pixel 2 or Pixel 2 XL devices.
Update(s):
Other - Added 'Other' after 'Prerequisites'
Disclaimers:
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Google Pixel XL or Verizon Pixel XL phone with an unlockable Bootloader, ([How-to] Unlock bootloader on Verizon Pixel/XL by burduli) - The unlock method was discovered by: Qu3ntin0), and the latest 7.1.2 August 2017, Factory Image (NHG47Q - Verizon; NKG47S - T-Mobile, Fi carriers, and Rogers; NZH54D - Deutsche Telekom; NJH47F - all other carriers).
Note: If you want the latest OTA or Binaries. Tap the Menu icon (upper left corner) then tap Full OTA Images or Driver Binaries
PC - With the latest Android SDK or SDK Platform tools installed.
Important: Update Android SDK or Platform Tools, regularly, for optimal performance.
Need help installing Android SDK or SDK Platform Tools
How to Install ADB & Fastboot on Mac, Linux & Windows-(Method 1)
Easiest-way-to-install-androids-adb-and-fastboot
Other
Pixel XL Guides: Android 9.0.0 (Pie)Android 8.1.0 (Oreo), Android 8.0.0 (Oreo)
Pixel 3 XL Guide: Android 9.0.0 (Pie)
Credit/Thanks/Recognitions
TWRP
TWRP for Google Pixel XL
twrp-3.0.2-0-RC1-fastboot-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.1.0-0RC1.zip to your phone.
twrp-pixel-installer-marlin-3.1.0-0RC2.zip to your phone
SuperSU
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
Magisk/MagiskManager
[Unofficial] Google Pixel family support by goodwin_c
Custom Kernels
ElementalX kernel
Franco's Kernel
Busybox/Busybox Checker
[MODS] Android Oreo Aroma installer misc. Mods by Tulsadiver
UPDATE-Busybox.Installer.v1.26.2-ALL-signed.zip
meekfik, download from PlayStore
Busybox Free (Stericson), download from PlayStore
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] by osm0sis
UPDATE-Busybox.Installer.v1.27.2-ALL-signed.zip
Busybox Checker, download from PlayStore
Other
pcriz -Fastboot Slot Commands, Custom ROM installion help, Magisk help, and help on many many other subjects.
Those I may have inadvertently forgotten.
Index
Open Command Prompt/ Boot Bootloader/Boot Recovery
Open Command Prompt on Computer
Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
Option 2 - Open File Explorer, click platform-tools folder, highlight the directory information in the address bar or click the folder (left side of address bar) to highlight it type 'cmd' and press enter.
Note: If your computer only has 'open powershell here' in the context menu and you do not want to change it or add open 'command prompt here' use use option 2.
Boot Bootloader:
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Press volume Up/Down button until you see Recovery Mode > Press Power button.
Testing ADB (Android Debug Bridge)/fastboot
ADB
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Type this at the prompt and press enter to test ADB.
Code:
adb version
It should return a version number for ADB.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot bootloader.
Connect your phone to your computer with a USB cable.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock Your Bootloader
Backup your data and Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Build Number. Tap Build Number until you see you're a Developer. Tap back > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot Bootloader
Connect your phone to your computer via USB cable.
Open a Command Prompt on your computer.
Type the following at the prompt and press enter:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to make your selection.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll be greeted with a warning that says Your device software can't be checked for corruption. Please lock the bootloader everytime you reboot. It's ok, as long as your bootloader is unlocked it will stay there.
Important: do not repeat do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see 9 of this guide for instructions on how to return to stock and lock the boot loader.
Install Factory Image and wipe data
Backup your data and Internal storage
Download the factory image for your phone and carrier.
Unzip factory Image
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following at the prompt and press enter.
Code:
flash-all
Install Factory Image and keep data
Backup your data and Internal storage
Download the factory image for your phone and carrier.
Unzip factory Image
Edit flash-all.bat: Remove -w
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following at the prompt and press enter.
Code:
flash-all
Install A Custom Recovery and Root with SuperSU
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Important: Make and restore nandroid backups with TRWP RC1 zip. Some, users have reported problems creating/restoring nandroid backups with TWRP RC2 zip.
Backup your data and Internal storage
Download files:
twrp-3.0.2-0-RC1-fastboot-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.1.0-0RC1.zip to your phone.
twrp-pixel-installer-marlin-3.1.0-0RC2.zip to your phone.
[STABLE][2017.05.27] SuperSU v2.82 by SuperSU Release to your phone.
Copy the following file to the platform-tools folder: twrp-3.0.2-0-RC1-fastboot-marlin.img rename it twrp.img
Boot Bootloader
Connect device/phone to computer
Open a Command Prompt on your computer.
Type the following at the Prompt.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
Tap Add more ZIPs button, select SuperSU-v2.82-201705271822.zip
Swipe the slider to install.
Reboot system
Install A Custom Recovery and Root with Magisk (Clean Install)
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Important: Make and restore nandroid backups with TRWP RC1 zip. Some, users have reported problems creating/restoring nandroid backups with TWRP RC2 zip.
Note:[Substratum] theme Spectrum does not work with Magisk root.
Backup your data and Internal storage
Download the following files:
ElementalX-P-1.14.zip for Pixel XL
twrp-3.0.2-0-RC1-fastboot-marlin.img
twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Magisk-v13.3-Pixel-b4.zip
MagiskManager-5_1_1.apk
Magisk-uninstaller-20170720.zip
Flash Boot.img - If you have TWRP, SuperSU, or a custom kernel installed.
Extract the contents of your factory image and open the folder it creates. From there, extract the second archive (image-marlin-aaa99a.zip)
Then open that folder and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the phone to your computer
Open a Command Prompt on your computer.
Type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
When it finishes, leave the command prompt window open, your phone in bootloader mode and connected to your computer.
Install TWRP
Place twrp-3.0.2-0-RC1-fastboot-marlin.img in your platform-tools folder and Rename it twrp.img
Type the following command at the prompt:
Code:
fastboot boot twrp.img
When TWRP boots, tap the Install button and select twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Swipe the slider to install
Press the back button until you are on TWRP's main menu select Reboot > Recovery.
Flash the ZIPs
Disconnect your phone from your Computer.
Tap the Install button, then navigate to the files you downloaded.
Select the Magisk Uninstaller.zip, tap the Add more ZIPs button.
Select the twrp-pixel-installer-marlin-3.0.2-0-RC2.zip.
Swipe to install
Reboot Recovery
Tap the Install button select a Custom Kernel: ElementalX-P-1.1x.zip or Franco's Kernel-r1x.zip.
Tap Add more ZIPs button select Magisk-v13.3-Pixel-b4.zip, tap the Add more ZIPs button and select: twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Swipe to install
Note: During the Installation of ElementalX, ElementalX's AROMA installer interface, will require your input: So, tick I agree, then tap Next a few times and press Install ElementalX when prompted.
When ElementalX AROMA installer finishes, tap Next, and Finish. After, the other ZIPs are installed.
Reboot System
Note: If you're prompted to install the TWRP app at this point, remove check marks from two check boxes and select Do Not Install.
Install MagiskManager
Install Magisk Manager (5.1.1.apk)
Wipe data on Magisk Manager
Enable Magisk Hide
Enable Core Only Mode
Toggle on and off systemless hosts
Reboot system
Check for Latest Version, Root, and Saftey Net.
Update Magisk Dirty Flash
Download file:
Magisk-v13.3-Pixel-b4.zip or Magisk-v13.4-Pixel-beta2-build1.zip
Flash the ZIPs
Magisk-v13.3-Pixel-b4.zip or Magisk-v13.4-Pixel-beta2-build1.zip, tap the Add more ZIPs button.
Select twrp-pixel-installer-marlin-3.0.2-0-RC2.zip.
Swipe to install.
Reboot system
Check for Latest Version, Root, and Saftey Net.
Custom ROMs for Pixel/Pixel XL
[ROM][Pixel-XL][7.1.2_r24]★ Pure Nexus ★ Substratum | Fi | WiFi Calling ★[07/25/17] by BeansTown106
[ROM][Pixel-XL][7.1.2_r33][OMS] Pixel Dust for marlin [FINAL][2017/08/22] by spezi77
[ROM][Resurrection Remix v5.8.3][Android Nougat 7.1.2][OMS][07/24/17] by BDogg718
[ROM][UNOFFICIAL] LineageOS 14.1 Nightlies for the Google Pixel (marlin/sailfish) by invisiblek
Paranoid Android 7.2.1 - AOSPA - Pixel XL by freak_97
ROM][7/21/17][Marlin][7.1.2][WEEKLY]Team OctOs Oct-N by cjkacz
SCREW'D ROM
Install Custom Kernel
Franco's Kernel - SuperSu
Download file:
The latest Franco's kernel for Pixel/Pixel XL
Boot into TWRP
Press Install button select the file you downloaded
Swipe slider to install
Reboot System
ElementalX-PXL-1.xx by flar2 Kernel - SuperSU
Download files:
ElementalX kernel
[STABLE][2017.05.27] SuperSU v2.82 by SuperSU Release
Flash ElementalX zip in TWRP recovery (do not flash SuperSU-v2.82-201705271822.zip again if you're already rooted).
During the Installation, ElementalX's AROMA installer interface, will require your input: So, tick I agree, then tap Next a few times and tap Install ElementalX when prompted.
When ElementalX AROMA installer finishes, tap Next, and then Finish.
Note: If you're prompted to install the TWRP app at this point, remove check marks from two check boxes and select Do Not Install.
Franco's Kernel or ElementalX-PXL-1.xx by flar2 Kernel - Magisk
See [Unofficial] Google Pixel family support by goodwin_c for Installation Instructions.
Install Substratum Theme
SuperSU Root
Install Substratum Theme Engine from the play store.
Install [Substratum] Spectrum theme from the play store. Note: I used Substratum theme Spectrum to test the installation of Substratum with SuperSU root..
Magisk Root
Researching Information
Return to Stock and Lock Bootloader
Return to Stock
Backup your data and Internal storage
Download the appropriate factory image for your phone and carrier.
Unzip factory Image
Copy the following files to the platform-tools folder on your Computer
flash-all.bat
Verify -w is present in flash-all.bat. Example: fastboot -w update image-marlin-aaa9.999999.999.zip
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following command at the prompt.
Code:
flash-all
Lock Bootloader
Phone
Boot Bootloader
Connect your phone to your Computer with USB cable.
Computer
Open a Command Prompt on your computer.
Type the following at the prompt:
Code:
fastboot flashing lock
When it finishes the bootloader is locked.
The next step won't be needed if your Pixel XL reboots into system after bootloader relock.
You need to boot into system now, either press Power button to reboot OR issue the following command:
Code:
fastboot reboot
When your phone reboots disconnect your usb cable.
Audio Mod
Weta Audio Mod

we already have guides though

flex360 said:
we already have guides though
Click to expand...
Click to collapse
can't hurt to have an updated guide for those too lazy to read.. so many posts about "this guide is out of date" or "i dont have time to read 6 pages about other people's experiences"

Thanks for this updated guide, this was helpful. Although, in step 4 it looks like you forgot to mention flashing SuperSu.

jrhatfield said:
Thanks for this updated guide, this was helpful. Although, in step 4 it looks like you forgot to mention flashing SuperSu.
Click to expand...
Click to collapse

It has been posted several times that the June security update doesn't need the verified boot signer. Only the May update needed it.

JimSmith94 said:
It has been posted several times that the June security update doesn't need the verified boot signer. Only the May update needed it.
Click to expand...
Click to collapse
I'll research it and make changes if needed.

Great Job compiling all the information in one place. Appreciate your hard work. This should be helpful to many.
You could even update this to include flashing of Custom ROMs. And a little bit about the slot change etc. That way the guide would almost be complete.

iamjimmy said:
Great Job compiling all the information in one place. Appreciate your hard work. This should be helpful to many.
You could even update this to include flashing of Custom ROMs. And a little bit about the slot change etc. That way the guide would almost be complete.
Click to expand...
Click to collapse
Intro
The purpose of this thread is twofold:
First, it is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM...
¯\_(ツ)_/¯

About to try this with the -w flag. Is there a reason to not use a -w if I intend on rooting njh47b on a google store pixel xl?

Avasta said:
About to try this with the -w flag. Is there a reason to not use a -w if I intend on rooting njh47b on a google store pixel xl?
Click to expand...
Click to collapse
2. Install Factory Image and wipe Data
Code:
fastboot -w update image-marlin-aaa99a.zip
3. Install Factory Image and keep Data
Code:
fastboot update image-marlin-aaa99a.zip

Homeboy76 said:
2. Install Factory Image and wipe Data
Code:
update -w image-marlin-aaa99a.zip
3. Install Factory Image and keep Data
Code:
update image-marlin-aaa99a.zip
Click to expand...
Click to collapse
I was asking if there was any affect to the rooting ability of the device if you did vs didn't use the -w command. I completed my update of my phone. I never like a dirty update since it only causes problem later on. I tested it without the -w switch and everything worked (kept my data, but as mentioned dirty flashes = no good), so I went back and repeated the steps with the -w switch. Everything works like a charm. Only issue I have noticed is that Netflix is no longer compatible with my device?!? Like not really sure why, but cant install it from the play store. Will contact Netflix about this later today.

Avasta said:
I was asking if there was any affect to the rooting ability of the device if you did vs didn't use the -w command. I completed my update of my phone. I never like a dirty update since it only causes problem later on. I tested it without the -w switch and everything worked (kept my data, but as mentioned dirty flashes = no good), so I went back and repeated the steps with the -w switch. Everything works like a charm. Only issue I have noticed is that Netflix is no longer compatible with my device?!? Like not really sure why, but cant install it from the play store. Will contact Netflix about this later today.
Click to expand...
Click to collapse
Gotcha, there are no 'effects to the rooting ability of the device'.
However, some apps will not work unless you 'hide Root' with Magisk i.e. Android Pay, Netflix's, etc.
Did you root with Magisk?

Homeboy76 said:
Gotcha, there are no 'effects to the rooting ability of the device'.
However, some apps will not work unless you 'hide Root' with Magisk i.e. Android Pay, Netflix's, etc.
Did you root with Magisk?
Click to expand...
Click to collapse
I dunno about you but I have magisk hide on and hid the playstore and a few other processes but if its checking your phone at a point before you can enable magisk hide and storing the results wouldn't it not make much difference? I ask this because magisk hide or not, netflix doesnt show up. Even on a clean boot its not listed as an app I can restore. The simple fix for me is to restore a back up or simply download from apk mirror.

I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!

parano666 said:
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
Click to expand...
Click to collapse
When you flash a factory image, flash it in both slots.
Flash all once
Boot into the bootloader again
Swap slots in bootloader
Flash all again

(tks!)
(update: needed twrp-pixel-installer-marlin-3.1.0-0RC2 installed and booted to install magisk v12 pixel (was getting error 1 with twrp-pixel-installer-marlin-3.0.2-0-RC1.zip))
(update2: safety net passed!)

pcriz said:
I dunno about you but I have magisk hide on and hid the playstore and a few other processes but if its checking your phone at a point before you can enable magisk hide and storing the results wouldn't it not make much difference? I ask this because magisk hide or not, netflix doesnt show up. Even on a clean boot its not listed as an app I can restore. The simple fix for me is to restore a back up or simply download from apk mirror.
Click to expand...
Click to collapse
Ok.

parano666 said:
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
Click to expand...
Click to collapse
Intro
The purpose of this thread is twofold:
First, it is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM...
If you follow the instructions above you should not have to worry about slot a/b. The firmware will put it in the correct slot.
If you are installing Custom ROM this thread is not for you. You, should follow the installation instructions of the Custom ROM you want to install.

parano666 said:
(tks!)
(update: needed twrp-pixel-installer-marlin-3.1.0-0RC2 installed and booted to install magisk v12 pixel (was getting error 1 with twrp-pixel-installer-marlin-3.0.2-0-RC1.zip))
(update2: safety net passed!)
Click to expand...
Click to collapse
You're welcome!

[Guide] Pixel XL Android 8.1 (OREO) Unlock/Root/Install Images/Kernels/Recovery +

[Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + July 2018 Security Patch​
Intro
This Guide is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel XL'.
This Guide also works for the Pixel owners: If, they download the correct files for their phone.
This Guide is not for use with the Second Generation Pixel 2 or Pixel 2 XL devices.
Update(s):
Custom ROM - crDroid v4.7
Note: Some Custom ROM's have the latest Security Patch.
Install Custom Kernel: - See #7, or #8
Disclaimers:
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Google Pixel XL or Verizon Pixel XL phone with an unlocked bootloader. ([How-to] Unlock bootloader on Verizon Pixel/XL by burduli - The unlock method was discovered by: Qu3ntin0) , and the latest Android 8.1.0 (Oreo) Factory Image: "marlin" for Pixel XL
marlin-opm4.171019.021.p1-factory-d5fc023e.zip
marlin-ota-opm4.171019.021.p1-f0709550.zip
Note: If you want the latest OTA or Binaries. Tap the Menu icon (upper left corner) then tap Full OTA Images or Driver Binaries
Computer - With the latest SDK Platform-Tools installed.
Important: Update Platform Tools, regularly, for optimal performance.
Need help installing or using SDK Platform tools: Easiest-way-to-install-androids-adb-and-fastboot
Other
Pixel XL Guides: Android 9.0.0 (Pie), Android 8.0.0 (Oreo), Android 7.1.2 (Nougat)
Pixel 3 XL Guide: Android 9.0.0 (Pie)
Credits/Thanks/Recognitions
Heisenberg RETIRED FORUM MODERATOR - He set the standard for creating, detailed, Guides.
Those I may have, inadvertently, forgotten.
Index
Open a Command Prompt/Boot Bootloader/Boot Recovery
Open Command Prompt on Computer
Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
Option 2 - Open File Explorer, click the platform-tools folder, highlight the directory information in the address bar or click the folder (left side of address bar) to highlight it type cmd and press enter.
Note: If your computer only has 'open powershell here' in the context menu. Use option 2.
Boot Bootloader:
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test ADB (Android Debug Bridge)/fastboot
ADB
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Type this at the prompt to test ADB.
Code:
adb version
It should return a version number for ADB.
Note: If it does not return a version number type
Code:
adb reboot bootloader
and try
Code:
adb devices
again.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Note: If it does not return a version number type
Code:
adb reboot bootloader
and try
Code:
fastboot devices
again.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
Backup your data and Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Tap Build Number until you see you're a Developer. Tap back > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type
Code:
fastboot flashing unlock
and press enter.
This will erase all user data from the device!
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type
Code:
fastboot reboot
at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll see a warning: Your device software can't be checked for corruption. Please lock the bootloader. You will see this warning until, you relock the bootloader.
Important: Do not relock your bootloader until you have returned the device to Stock..
Return Phone to Stock
Backup your data and Internal storage
Download the latest Factory Image
Extract factory Image to the platform-tools folder, or the folder that has fastboot in it.
Verify -w is present in flash-all.bat. Example: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: This will erase all your Data and Internal Storage
Boot bootloader
Connect your phone to your Computer with a USB cable.
Open a Command Prompt:
Flash the Stock Factory Image on Both Slots
Type this at the Command Prompt:
Code:
flash-all
Let the phone boot.
Boot bootloader
Open Command Prompt:
Switch to the other slot.
Type this at the Command Prompt:
Code:
fastboot --set-active=other
Then type this at the Command Prompt:
Code:
flash-all
Let the phone boot.
Lock Bootloader
'B' must be completed before performing this step!
Boot bootloader
Open a Command Prompt and type this at the Prompt:
Code:
fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt:
Code:
fastboot reboot
Set up your phone.
Enable Developer Options: Settings > System > About phone > Tap Build number 7 times.
Tap Back > Developer options and toggle OEM unlocking to off.
Install Factory Image keep or wipe data
Important: When doing a major upgrade i.e., Android 7.x.x to Android 8.0.0/Android 8.1.0. I recommend wiping data.
Backup your data and Internal storage
Download the appropriate Factory Image: "marlin" for Pixel XL to your Computer.
Extract the factory Image to the platform-tools folder or the folder that has fastboot in it.
Keep Data
Open the folder you extracted the Factory Image to and Edit the flash-all.bat file to remove -w from this command: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: If you do not remove the -w not only will your data be erased but also your internal storage will be erased.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.:
Type
Code:
flash-all
at the Command Prompt and press enter.
Do #7 or #8 to root/reroot
Wipe Data
Open the folder you extracted the Factory Image to and Verify the flash-all.bat file has the -w in this command: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: This will erase your data and internal storage.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.:
Type
Code:
flash-all
at the Command Prompt and press enter.
Do #7 or #8 to root/reroot
ADB Sideload
Boot Recovery
-- On the Computer
Connect the phone to the Computer.
Open a Command Prompt.
-- On the Phone
Boot recovery
Tap Advanced > ADB Sideload.
Swipe the slider to start the ADB connection.
-- Sideload the ZIP
Copy and paste the Zip file you want sideload to the Platform-tools folder or the folder that 'adb.exe' is in.
At the Command Prompt type:
Code:
adb sideload <space> <file name>
Example: adb sideload example.zip
Press enter to begin the sideloading process.
When, you see a Reboot System button, tap it.
Extract/Flash boot.img
Extract boot.img
Use a File Explorer to extract the boot.img from the Factory Image.
Extract the Factory Image file (marlin-opm-9.999999.999-99a-factory-a9a9999.zip) to a folder.
Open the folder and, extract the Image file (image-marlin-aaa9.999999.999.99a.zip).
Flash boot.img
Note: Flashing this file removes root.
Open the folder you extracted the 'image file' to and copy the boot.img file to the platform-tools or to the folder that has fastboot in it.
Boot Bootloader
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
Reboot
Root/Reroot with Magisk - Pass SafetyNet
Important: Set Pin before installing TWRP:
Settings > Security & location >Screen lock > Pin
Backup your data and Internal storage
Download files:
The files listed below are used with 7 and 8.
TWRP
TWRP 3.2.2-0 for Google Pixel XL
twrp-3.2.3-1-marlin.img - Download to your computer
twrp-pixel-installer-marlin-3.2.3-1.zip - Download to your phone
Magisk - Download to your phone
[2018.9.1] Magisk v17.1 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
Magisk-uninstaller-20180901.zip - Post 1, Downloads
topjohnwu / Magisk
Custom kernels - Download to your phone
[KERNEL] [29 July] Pixel XL ElementalX 3.09 (8.1.0) 4.06 (P) by flar2
exNoShadez:. nine7nine/Apps
[*][MARLIN/SAILFISH] [8.1.0/9.0.0] [3.18.117] [CLANG 7.0] Flash Kernel 1.19 by nathanchance
[*][KERNEL][8.1.0][3.18.115] PureZ-Kernel-1.9 for Google Pixel XL [17/07/2018] by ZawZaw
[*]Boot Bootloader
[*]Connect the phone to the Computer with USB cord.
[*]Copy twrp-3.2.3-2-marlin.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.
[*]Open a Command Prompt on your computer.
[*]At the Command Prompt type:
Code:
fastboot boot twrp.img
and press enter.
[*]When TWRP boots, disconnect the phone from the computer.
[*]Tap Install select
twrp-pixel-installer-marlin-3.2.3-1.zip
[*]Swipe the slider to install
[*]After TWRP is installed
[*]Reboot Recovery (Tap the back button, Tap reboot, Tap recovery.)
[*]Install Custom Kernel and Root/Reroot (Optional)
Tap Install, select Custom Kernel:
ElementalX
ElementalX-P-3.09.zip
EX Kernel Manager by flar2
flashkernel-marlin-v1.19.zip
PureZ-Kernel-marlin-1.9.zip
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
[*]Root/Reroot with Magisk
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
[*]Install Modules - BusyBox, etc. (Optional)
Open Magisk Manager, tap Menu, tap downloads.
[*]Root/Reroot with Magisk - Pass SafetyNet without installing TWRP
Important: Set Pin before booting TWRP:
Settings > Security & location >Screen lock > Pin
Note: You might have noticed in the 'Install Custom kernel' section that some Custom kernels are installed before Magisk while others are installed after Magisk. The best answer I could find for when to flash a Custom Kernel when using Magisk for root is, if the Custom Kernel modifies/patches the boot image you install Magisk then the Custom Kernel otherwise you install the Custom Kernel then Magisk.
Backup your data and Internal storage
Download files:
See 'Download files' in #7 above - Do not download TWRP zip file.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.
Copy twrp-3.2.3-1-marlin.img to the platform-tools folder or the folder that fastboot is in and rename it twrp.img
Type
Code:
fastboot boot twrp.img
at the Command Prompt and press enter.
When TWRP boots, disconnect the phone from the computer.
Install Custom Kernel (Optional)
Yes
exNoShadez:. nine7nine/Apps
Tap Install, select Magisk-v17.1.zip - (Official)
Tap Add more Zips, select:
exns_eas_v3.8.1p_bca050b.zip
Or
(Stable) exNoShadez_eas_v2.8.2_f94351f.zip
Swipe Slider to Install
Save Log
Reboot System
ElementalX / Flash /PureZ
Tap Install, select Custom Kernel:
ElementalX-P-3.09.zip
EX Kernel Manager by flar2
flashkernel-marlin-v1.19.zip
PureZ-Kernel-marlin-1.9.zip
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
No
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
Install Modules - BusyBox, etc. (Optional)
Open Magisk Manager, tap Menu, tap downloads.
[*]Update Magisk
Important: "If you had the stable version or the official beta installed, you must first un-install the Magisk Manager, only, before you can install the unofficial version, because they are signed with different keys".
"The same holds true if, for example, you have @kantjer 's build installed and want to try @ianmacd 's builds". See kantjer and martyfender post: [UNOFFICIAL] next version Magisk and MagiskManager snapshots by stangri
Magisk Notification is on.
Turn on Magisk Manager update notification: Open MagiskManager > Tap menu icon > Settings > Update Channel > Select: Stable, Beta or Custom
Custom is used to get updates for Unofficial Magisk Builds.
When Magisk Manager notifies you of update availibility.
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Tap, Reboot
Done!
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Magisk Notification is off.
Open Magisk Manager
When asked 'Do you want to install Magisk-vxx.x.zip now?
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Tap, Reboot
Done!
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Unofficial Magisk Links and Channels
To set the Magisk Notification Update Channel for Unofficial Magisk Builds: Open MagiskManager > Tap menu icon > Settings > Update Channel > Select: Custom > Copy the link address below and paste it on the line:
ianmacd
Code:
https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json
kantjer
Code:
https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json
topjohnwu has a new channel:
[DEV] Magisk Canary Channel - Bleeding Edge Builds by topjohnwu Please, read the OP for the URL.
When Magisk Manager notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Tap, Reboot
Done!
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
[*][Magisk] Systemless Xposed v89.3/v90.1-beta3 (SDK 21-27)
Information only, see thread for instruction/use.
[2018.5.6][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27) by*topjohnwu
[*]Custom ROMs for Pixel XL
Need help with a Custom ROM?
First, follow the Installation Instructions in the OP (Post 1) of the Custom ROM you want to install.
Second, if you have a problem Installing it, Search the thread of the Custom ROM you want to install for solutions to problem before posting a request for help on their thread.
Official
[ROM][Pixel-XL][8.1.0_r43] [OMS] Pixel Dust OREO for marlin [R8] by spezi77
pixeldust_marlin-oreo-release-eight-20180810.zip
[ROM][OPM4.171019.021.P1][07/21] Benzo Rom 8.1.0 OMS by xanaxdroid
benzorom-8.1.0-20180721-2013-marlin.zip
[ROM] [marlin] [8.1] [LOS-based] **crDroid**OMS**v4.7 (10/12/18) by hokiealumnus
crDroidAndroid-8.1-20181012-marlin-v4.7.zip
[ROM][OFFICIAL][8.1.0]FireHound-v4.8.1 For Google Pixel XL [Marlin] by NepoRood
FireHound-4.8.1-OFFICIAL-20180907-marlin.zip
[ROM][OFFICIAL]Resurrection Remix v6.0 [Android 8.1][05/20/18] by BDogg718
RR-O-v6.0.0-20180520-marlin-Official.zip
[8.1.x][OFFICIAL][WEEKLIES] CarbonROM | cr-6.1 [marlin] by shagbag913
CARBON-CR-6.1-NOCT-WEEKLY-marlin-20180529-1130.zip
[ROM]-[Official]-[10.07.18]-Havoc-OS-[8.1.0] by SKULSHADY
Havoc-OS-20180710-marlin-Official.zip
[ROM][OFFICIAL] lineage-15.1 for Pixels (sailfish/marlin) by razorloves.)
lineage-15.1-20180731-nightly-marlin-signed.zip
Unofficial
[ROM][UNOFFICIAL][7/29/18] AICP 13.1 by stebomurkn420
aicp_marlin_o-13.1-UNOFFICIAL-20180729.zip
[ROM] [8.1.0] BootleggersROM 2.3-STABLE [Unshishufied] by stebomurkn420
BootleggersROM-Oreo4marlin.2.3-Stable-Unshishufied-20180710.zip
AOSiP 8.1 *Flash Kernel* (Unofficial) by stebomurkn420
AOSiP-8.1-Derp-marlin-20180722.zip
[ROM][Unofficial][8.1.0] Resurrection Remix 6.1.0 by dylanneve1
RR-O-v6.1.0-20180818-marlin-Unofficial.zip
Android Devs
[*]Audio Mod
ViPER4Android, [MOD]Audio Modification Library , and Audio Compatibility Patch.
Note: Some, of there can be installed via 'Magisk Downloads'.
[*]Other: TWRP Backup/TWRP Update
TWRP Backup
Boot Recovery.
Tap Backup and select Partitions to backup
Boot
System Image
Vendor Image
Data (Optional)
EFS (Once per major upgrade)
Swipe Slider to backup
Your backup will be stored in /Storage/Emulated/0/TWRP/...
Note: If you are unable to make a backup to internal storage with trwp 3.2.2-0 try backing up to USB-OTG
Update TWRP
TWRP Installation Instructions:
"If you already have TWRP installed: Download the latest zip and install the zip using TWRP".

at #5 why do I need to wipe data if coming from 8.0.0? or is it just a precaution?

Papote3 said:
at #5 why do I need to wipe data if coming from 8.0.0? or is it just a precaution?
Click to expand...
Click to collapse
FWIW, I am on 8.1 from 8.0 Nov patch and did not factory reset, just flash-all with -w removed (actually I run each command in that file myself). Everything works fine and no data/app loss...

jk8260 said:
FWIW, I am on 8.1 from 8.0 Nov patch and did not factory reset, just flash-all with -w removed (actually I run each command in that file myself). Everything works fine and no data/app loss...
Click to expand...
Click to collapse
Yeah that's what I thought. I think he just writes it just as a precaution, in case anything goes wrong on 8.1, first factory reset and then write the problem if it still persist

Supersu or Magisk
Which rooting method is best for the Pixel XL. Supersu or Magisk

Update worked like a charm on my standard Pixel.
But somehow TWRP will not decrypt, keep asking for password even though I always had a pattern which worked flawlessly in TWRP. Any suggestions so I can get rooted again?
EDIT: After a few password attempts, removing the password altogether worked. When installing TWRP.zip the command window says E:This TWRP does not have synthetic password decrypt support, that must be why I had problems.
EDIT2: SuperSU does not seem to work

Juhler said:
Update worked like a charm on my standard Pixel.
But somehow TWRP will not decrypt, keep asking for password even though I always had a pattern which worked flawlessly in TWRP. Any suggestions so I can get rooted again?
EDIT: After a few password attempts, removing the password altogether worked. When installing TWRP.zip the command window says E:This TWRP does not have synthetic password decrypt support, that must be why I had problems.
EDIT2: SuperSU does not seem to work
Click to expand...
Click to collapse
Password Encryption isnt working on the new TWRP3.2.0 gotta wait for an update or remove passwords all together...

Juhler said:
Update worked like a charm on my standard Pixel.
But somehow TWRP will not decrypt, keep asking for password even though I always had a pattern which worked flawlessly in TWRP. Any suggestions so I can get rooted again?
EDIT: After a few password attempts, removing the password altogether worked. When installing TWRP.zip the command window says E:This TWRP does not have synthetic password decrypt support, that must be why I had problems.
EDIT2: SuperSU does not seem to work
Click to expand...
Click to collapse
Supersu wasn't even in my app drawer after flashing the zip so after rebooting I just went into the zip and installed the apk manually

Thank you for this thread....it worked. I did #9

Can confirm #10 works like a charm. Thanks for the separate thread. Both your guide threads should be stickies.

Just use adb sideload...
If you want to keep all your data, just sideload the OTA via adb, instead of flashing the full factory image...
My Steps:
1) Flash stock boot.img (November for me, I used TWRP)
2) Reboot recovery
3) Choose: Apply Update from ADB
4) adb sideload marlin-ota-opm1.171019.011-9e7f2bb8.zip
5) reboot system
6) set screen lock to "none"
7) copy twrp-pixel-installer-marlin-3.2.0-0.zip to your internal storage
8) reboot bootloader
9) fastboot twrp.img
10) Install: twrp-pixel-installer-marlin-3.2.0-0.zip
11) reboot recovery
12) Install: SR5-SuperSU-v2.82-SR5-20171001224502.zip
13) reboot system
14) profit!
If you knew this, great, if you didn't, you do now :good:
Regards,
Nepo

ekowwillis said:
Which rooting method is best for the Pixel XL. Supersu or Magisk
Click to expand...
Click to collapse
In my opinion Magisk.

NepoRood said:
If you want to keep all your data, just sideload the OTA via adb, instead of flashing the full factory image...
My Steps:
1) Flash stock boot.img (November for me, I used TWRP)
2) Reboot recovery
3) Choose: Apply Update from ADB
4) adb sideload marlin-ota-opm1.171019.011-9e7f2bb8.zip
5) reboot system
6) set screen lock to "none"
7) copy twrp-pixel-installer-marlin-3.2.0-0.zip to your internal storage
8) reboot bootloader
9) fastboot twrp.img
10) Install: twrp-pixel-installer-marlin-3.2.0-0.zip
11) reboot recovery
12) Install: SR5-SuperSU-v2.82-SR5-20171001224502.zip
13) reboot system
14) profit!
If you knew this, great, if you didn't, you do now :good:
Regards,
Nepo
Click to expand...
Click to collapse
Good Information!
Did you flash a Custom Kernel (ElementalX-P-3.00.zip) or UPDATE-suhide-v1.09-20171001222116.zip to pass SafetyNet?

Papote3 said:
Yeah that's what I thought. I think he just writes it just as a precaution, in case anything goes wrong on 8.1, first factory reset and then write the problem if it still persist
Click to expand...
Click to collapse
There are three reasons I recommend #4 - 'Wipe Data' prior to rooting:
a. I write all my guides with step by step instructions for noobs.
b. Some have reported data corruption when not doing #4 - 'Wipe Data'.
c. When upgrading the OS, I always start with a clean install.
If you want to upgrade without a clean installation that's ok too, but it is much easier to trouble shoot problems if you start with a clean installation.

Homeboy76 said:
Good Information!
Did you flash a Custom Kernel (ElementalX-P-3.00.zip) or UPDATE-suhide-v1.09-20171001222116.zip to pass SafetyNet?
Click to expand...
Click to collapse
I did not flash those, I have no real need for either...
Sent from my Pixel XL using XDA Labs

Everything went well up to "erasing userdata"..... its been stuck there for 5 min... any advice?
Cancel that....Just finished...

NepoRood said:
If you want to keep all your data, just sideload the OTA via adb, instead of flashing the full factory image...
My Steps:
1) Flash stock boot.img (November for me, I used TWRP)
2) Reboot recovery
3) Choose: Apply Update from ADB
4) adb sideload marlin-ota-opm1.171019.011-9e7f2bb8.zip
5) reboot system
6) set screen lock to "none"
7) copy twrp-pixel-installer-marlin-3.2.0-0.zip to your internal storage
8) reboot bootloader
9) fastboot twrp.img
10) Install: twrp-pixel-installer-marlin-3.2.0-0.zip
11) reboot recovery
12) Install: SR5-SuperSU-v2.82-SR5-20171001224502.zip
13) reboot system
14) profit!
If you knew this, great, if you didn't, you do now :good:
Regards,
Nepo
Click to expand...
Click to collapse
Thanks
Don't you need stock recovery to be able to apply OTA?
I don't see a step doing that, and I suppose you're on TWRP, or were you already on stock recovery?
If so, then better make that a clear step.

badabing2003 said:
Thanks
Don't you need stock recovery to be able to apply OTA?
I don't see a step doing that, and I suppose you're on TWRP, or were you already on stock recovery?
If so, then better make that a clear step.
Click to expand...
Click to collapse
That's covered with Step #1, friend
NepoRood said:
1) Flash stock boot.img (November for me, I used TWRP)
Click to expand...
Click to collapse
Since boot and recovery are on the same partition, flashing stock boot will give you stock recovery. I flashed my stock boot using TWRP, however, it can be flashed via fastboot as well.
AFAIK, this can be done for all updates (I've used this method since Oreo came out), it's just like taking the OTA from Gooble, you just download it yourself :good:
Regards,
Nepo
PS, I did flash full factory image when upgrading from Nougat to Oreo, just FYI

NepoRood said:
That's covered with Step #1, friend
Since boot and recovery are on the same partition, flashing stock boot will give you stock recovery. I flashed my stock boot using TWRP, however, it can be flashed via fastboot as well.
AFAIK, this can be done for all updates (I've used this method since Oreo came out), it's just like taking the OTA from Gooble, you just download it yourself :good:
Regards,
Nepo
PS, I did flash full factory image when upgrading from Nougat to Oreo, just FYI
Click to expand...
Click to collapse
Thanks for the clarification, didn't know that was the case.
I never flashed boot using twrp, would it do it for all slots, I guess it would.
Sent from my Pixel XL using Tapatalk

Is anyone getting this error?
Code:
wiping userdata...
/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
I'm using the wipe option, but haven't ran into this one before.

[Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery +

[Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT
Security Patch - December 2019​
Introduction
This Guide is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel XL'.
This Guide also works for the Pixel owners: If, they download the correct files for their phone.
This Guide is not for use with the Pixel, Pixel 2, Pixel 2 XL, Pixel 3a, or Pixel 3a XL phones.
NEW
Android 11 (R) ROM
Update(s)
Factory/OTA Images - 12/02
Magisk Stable - Magisk-25.2
Magisk Beta - Magisk-25.3
Magisk Canary - Magisk-25205
T.W.R.P - twrp-3.4.0-0-marlin.img/zip[/URL]
SDK Platform-tools - r33.0.3
Custom Kernels
No Updated Custom Kernels
Custom ROMs Android 10 (Q)
Pixel Experience 10/25
Custom ROMs Android 11 (R)
[UNOFFICIAL][ROM][11][Marlin/Sailfish] LineageOS 18.0 [06/10/2020] by*Lunarixus
Disclaimers
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Google Pixel XL or Verizon Pixel XL phone with an unlockable bootloader.
The latest Android 9.0.0 (Pie) Factory or OTA Image: "marlin" for Pixel XL
Factory Image
10.0.0 (QP1A.191005.007.A3, Dec 2019)
OTA Image
10.0.0 (QP1A.191005.007.A3, Dec 2019)
Computer - With the latest SDK Platform-Tools: r30.0.5 installed.
Important: Update Platform Tools, regularly, for optimal performance.
Need help installing or using SDK Platform tools: Easiest-way-to-install-androids-adb-and-fastboot
Other Pixel XL Guides
Pixel XL Android 10 (Q)
Credits/Thanks/Recognitions
Heisenberg RETIRED FORUM MODERATOR - He set the standard for creating, detailed, Guides.
Those I may have, inadvertently, forgotten.
Index
(NOTE: These are not steps 1-13, they are individual sets of information/instructions).
Open a Command Prompt/Boot Bootloader/Boot Recovery
Open Command Prompt on Computer
Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
Option 2 - Open File Explorer, click the platform-tools folder, highlight the directory information in the address bar or click the folder (left side of address bar) to highlight it type cmd and press enter.
Notes:
If your computer only has 'open powershell here' in the context menu. Use option 2.
If you do not want to open a Command Prompt every time you want to use fastboot, add the path to the Platform-tools folder to Windows environment variables.
Boot Bootloader:
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test ADB (Android Debug Bridge)/fastboot
ADB
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Type this at the prompt to test ADB.
adb version
It should return a version number for ADB.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Type this at the prompt and press enter to test fastboot.
fastboot devices
It should return your device serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader (Google Pixel XL)
Backup your data/Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Tap Build Number until you see you're a Developer. Tap back > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
This will erase all user data from the device!
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll see a warning: Your device software can't be checked for corruption. Please lock the bootloader. You will see this warning until, you relock the bootloader.
Important: Do not relock your bootloader until you have returned the device to Stock..
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader (Google Pixel XL)
'B' must be completed before performing this step!
Boot bootloader
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Set up your phone.
Enable Developer Options: Settings > System > About phone > Tap Build number 7 times.
Tap Back > Developer options and toggle OEM Unlock off.
Install Factory Image keep or wipe data
When doing a major upgrade, Android 8.1.0 (Oreo) to Android 9.0.0 (Pie). I suggest wiping data/Clean Install.
Backup your data and Internal storage
Download the appropriate Factory Image: "marlin" for Pixel XL to your Computer.
Extract the factory Image to the platform-tools folder or the folder that has fastboot in it.
Keep Data
Open the folder you extracted the Factory Image to and Edit the flash-all.bat file to remove -w from this command: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: If you do not remove the -w not only will your data be erased but also your internal storage will be erased.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.:
Type flash-all at the Command Prompt and press enter.
Reboot
Do #7 or #8 to root/reroot
Wipe Data
Open the folder you extracted the Factory Image to and Verify the flash-all.bat file has the -w in this command: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: This will erase your data and internal storage.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.:
Type flash-all at the Command Prompt and press enter.
Reboot
Do #7 or #8 to root/reroot
ADB Sideload
Boot Recovery
-- On the Computer
Connect the phone to the Computer.
Open a Command Prompt.
-- On the Phone
Boot recovery
Tap Advanced > ADB Sideload.
Swipe the slider to start the ADB connection.
-- Sideload the ZIP
Copy and paste the Zip file you want sideload to the Platform-tools folder or the folder that 'adb.exe' is in.
At the Command Prompt type: adb sideload <space> <file name>
Example: adb sideload example.zip
Press enter to begin the sideloading process.
When, you see a Reboot System button, tap it.
Extract/Flash boot.img
Extract boot.img
Use a File Explorer to extract the boot.img from the Factory Image.
Extract the Factory Image file (marlin-opm-9.999999.999-99a-factory-a9a9999.zip) to a folder.
Open the folder and, extract the Image file (image-marlin-aaa9.999999.999.99a.zip).
Flash boot.img
Note: Flashing this file removes root.
Open the folder you extracted the 'image file' to and copy the boot.img file to the platform-tools or to the folder that has fastboot in it.
Boot Bootloader
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot boot.img --slot all
Reboot
Install T.W.R.P./Root/Reroot with Magisk and Pass SafetyNet.
Important:
Set Pin before installing TWRP:
Settings > Security & location >Screen lock > Pin
Backup your data and Internal storage
Download files:
The files listed below are used with 7 and 8.
TWRP
TWRP 3.3.1-3 for Google Pixel XL
twrp-3.4.0-0-marlin.img - Download to your computer
twrp-pixel-installer-marlin-3.4.0-0.zip - Download to your phone
Magisk - Download to your phone
The latest Stable/Beta Magisk Manager from Magisk by topjohnwu
[DEV] Magisk Canary Channel - Bleeding Edge Builds by topjohnwu
Custom kernels - Download to your phone
No Updated Custom Kernels
Kernel Managers - Download to your phone
EX Kernel Manager
FK Kernel Manager
Boot Bootloader
Connect the phone to the Computer with USB cord.
Copy twrp-3.5.0-0-marlin.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.
Open a Command Prompt on your computer.
At the Command Prompt type: fastboot boot twrp.img and press enter.
When TWRP boots, disconnect phone from computer.
Swipe to allow modifications.
Tap Install select
twrp-pixel-installer-marlin-3.4.0-0.zip
Swipe the slider to install
Reboot Recovery
If you are rerooting, tap Install, select the latest Magisk's uninstaller.zip, and Swipe the Slider to Install.
Note: If you have Modules installed, please read these posts by @jcmm11 'RC' before flashing/installing Magisk's Uninstaller.zip: Post 329 and Post 333
Install Custom Kernel and Root/Reroot (Optional)
Note(s):
Some Custom Kernels can be updated by flashing via twrp or Kernel Manager without losing root. Check the Custom Kernel thread (OP - Installation/Instructions) to find out which Custom Kernels.
Some Custom Kernels can also be Flashed with a Kernel Manager.
If you want to flash the kernel via the Kernel Manager instead of twrp skip #7 L1 do #7 L2 then install kernel via Kernel Manager.
Yes
No Updated Custom Kernels
No
Tap Install, select Magisk-20.4.zip - Stable/Beta
Swipe Slider to Install
Save Log
Reboot System
Boot T.W.R.P./Root/Reroot with Magisk and Pass SafetyNet.
Important: Remove Pin before booting TWRP:
Settings > Security & location >Screen lock > None
Backup your data and Internal storage
Download files:
See #7 - Skip the twrp-pixel-installer-marlin-3.4.0-0.zip
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.
Copy twrp-3.4.0-0-marlin.img to the platform-tools folder or the folder that fastboot is in and rename it twrp.img
Type fastboot boot twrp.img at the Command Prompt and press enter.
When TWRP boots, disconnect phone from computer.
If requested Swipe to allow modifications.
If you are rerooting, tap Install, select the latest Magisk's uninstaller.zip, and Swipe the Slider to Install.
Note: If you have Modules installed, please read these posts by @jcmm11 'RC' before flashing/installing Magisk's Uninstaller.zip: Post 329 and Post 333
Install Custom Kernel and Root/Reroot (Optional)
Note(s):
Some Custom Kernels can be updated by flashing via twrp or Kernel Manager without losing root. Check the Custom Kernel thread (OP - Installation/Instructions) to find out which Custom Kernels.
Some Custom Kernels can also be Flashed with a Kernel Manager.
If you want to flash the kernel via the Kernel Manager instead of twrp skip #8 I1 do #8 I2 then install kernel via Kernel Manager.
Yes
No Updated Custom Kernels
No
Tap Install, select Magisk-20.4.zip - Stable/Beta
Swipe Slider to Install
Save Log
Reboot System
Set Magisk Manager's Update Chanel/Update Magisk
Set Magisk Manager's Update Channel - Stable/Beta/Custom
Open Magisk Manager > Tap menu icon > Settings > Update Channel > Select Stable, Beta or Custom.
Custom is used to switch to Canary. Paste the URL below in the Custom Channel: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json
Update Magisk
When Magisk Manager notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Tap, Reboot
Done!
Custom ROMs for Pixel XL
Need help with a Custom ROM?
First, follow the Installation Instructions in the OP of the Custom ROM you are trying to install.
Second, if you have a problem Installing it, Search the thread of the Custom ROM you want to install for solutions to problem before posting a request for help on their thread.
Alpha/Beta
None
Official
None
Unofficial
[ROM][10.0][marlin] Pixel Experience [AOSP][2020/10/25] by*PixelBoot
Audio Mod
ViPER4Android FX/XHiFI, [MOD]Audio Modification Library , and Audio Compatibility Patch.
Note: These Mods can be installed via Magisk Manager: Tap Magisk Manager > Tap Menu > Tap Downloads > Select Mod > Tap Install.
Other: TWRP Backup/TWRP Update
TWRP Backup
To Internal Storage
Boot bootloader
fastboot boot twrp-3.4.0-0.img
[*]When twrp-3.4.0-0 boots, tap Backup and select Partitions to backup
[LIST="(1)"]
[*]Boot
[*]System Image
[*]Data
[/LIST]
[*]Tap Select Storage ==> internal storage
[*]Tap ok
[*]Swipe Slider to backup
[*][B]Your backup will be stored in /Storage/TWRP/...[/B]
[/LIST]
[/HIDE]
[*]To OTG-USB Storage
[HIDE]
[LIST="a"]
[*]Boot fastboot mode (#1B)
[*][ICODE]fastboot boot twrp-3.4.0-0.img
[*]When twrp-3.3.1-3 boots, tap Backup and select Partitions to backup
[LIST="(1)"]
[*]Boot
[*]System Image
[*]Data
[/LIST]
[*]Insert USB-OTG
[*]Tap Select Storage ==> OTG-USB
[*]Tap ok
[*]Swipe Slider to backup
[*][B]Your backup will be stored in /Storage/TWRP/...[/B]
[/LIST]
[/HIDE]
[/LIST]
[/HIDE]
[*][B]Update[URL="https://twrp.me/google/googlepixelxl.html"]TWRP[/URL][/B]
[/LIST]
[/HIDE]
[/LIST]

Reserved

Reserved

Once again, fantastic guide Big thanks :highfive:

Way to be on top of things @Homeboy76, Job Well Done, once again :good:

Do OG Pixels need magisk 1671 or 1674?
Pixel 2 and 2 xl have some troubles, so there is a specific magisk version for them in the flash kernel thread, before flash I just wanna make sure 1671 won't cause issues, thank you.

Hi.
Can anyone tell me?
I want to flash Android Pie.
Now I'm on official Lineage OS 15.1 + twrp 3.2.2 + Magisk
I need to do step 3 (and flash all to both slots)?
Return Phone to Stock
Or I need to do step 4 (and flash all only once)?
Install Factory Image
Thanks in advance.

Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?

djl236 said:
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
Click to expand...
Click to collapse
I did, but I was running FireHound v4.7 (July Security), so I got a lot of different FCs, lol (Hey, I had to try). If you're on stock, you'll probably be fine.
I just installed TWRP 3.2.3, did a factory reset and setup fresh. No issues after that.
I had to use Magisk beta 16.7 to root. I did a restore with TiBu and all my previous apps are working fine.

Hi, i followed this (already 9 with OTA) :
Boot Bootloader
Connect the phone to the Computer with USB cord.
Copy twrp-3.2.2-0-marlin.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.
Open a Command Prompt on your computer.
At the Command Prompt type:
Code:
fastboot boot twrp.img
and press enter.
When TWRP boots
Disconnect phone from computer.
Swipe to allow modifications.
Tap Install select
twrp-pixel-installer-marlin-3.2.2-0.zip
Swipe the slider to install
After TWRP is installed
Reboot Recovery (Tap the back button, Tap reboot, Tap recovery.)
then
flash Magisk-v16.7(1671).zip - (BETA)
Swipe Slider to Install
Save Log
Reboot System
did not install custom recovery tho
it stuck at google logo. do i need to flash custom kernel?

I have this same problem, using 3.2.3. Not installing TWRP, I installed Elemental X alone and it works fine. It's when I try to install Magisk 16.7 that it bootloops on the Google Logo
lesp4ul said:
Hi, i followed this (already 9 with OTA) :
Boot Bootloader
Connect the phone to the Computer with USB cord.
Copy twrp-3.2.2-0-marlin.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.
Open a Command Prompt on your computer.
At the Command Prompt type:
Code:
fastboot boot twrp.img
and press enter.
When TWRP boots
Disconnect phone from computer.
Swipe to allow modifications.
Tap Install select
twrp-pixel-installer-marlin-3.2.2-0.zip
Swipe the slider to install
After TWRP is installed
Reboot Recovery (Tap the back button, Tap reboot, Tap recovery.)
then
flash Magisk-v16.7(1671).zip - (BETA)
Swipe Slider to Install
Save Log
Reboot System
did not install custom recovery tho
it stuck at google logo. do i need to flash custom kernel?
Click to expand...
Click to collapse

jeremyafrank said:
I have this same problem, using 3.2.3. I installed Elemental X alone and it works fine. It's when I try to install Magisk 16.7 that is bootloops on the Google Logo
Click to expand...
Click to collapse
found this , magisk 16.7 1674
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view
didn't work either lol

I'm going to have to go back to 8.1 (had done a dirty flash, but I'm only running stock) until this is sorted. Some nice things I'd like to play with in Pie, but not at the expense of root.
lesp4ul said:
found this , magisk 16.7 1674
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view
didn't work either lol
Click to expand...
Click to collapse

TENN3R said:
Do OG Pixels need magisk 1671 or 1674?
Pixel 2 and 2 xl have some troubles, so there is a specific magisk version for them in the flash kernel thread, before flash I just wanna make sure 1671 won't cause issues, thank you.
Click to expand...
Click to collapse
1674 is for Pixel2/Pixel2XL
[TAIMEN/WALLEYE] [9.0.0] [4.4.146] [CLANG 7.… - Pg. 284 | Google Pixel 2 XL

Where is my mistake?
I flashed Pie image marlin-ppr1.180610.009-factory-90a4fa8b
(flash all.bat)
And had a lot of errors (Screenshot attached).
After reboot to system I have Lineage OS 15.1 that I had before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance.

djl236 said:
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
Click to expand...
Click to collapse
Yes, this is how I updated.
- I was on stable Magisk 16.0 so I flashed the most recent Magisk uninstall ZIP in TWRP to be safe, since 9.0 requires the Magisk 16.7 beta
- boot to bootloader
- flash-all.bat removing -w
- fully boot to system
- turn off, boot to bootloader
- fastboot boot new TWRP 3.2.3-0
- install TWRP 3.2.3-0 ZIP
- install Magisk 16.7 ZIP
- boot to system
- I had to reauthorize root access for all root apps and enable systemless hosts in Magisk
Device passes SafetyNet and is certified in Play Store.

jeremyafrank said:
I'm going to have to go back to 8.1 (had done a dirty flash, but I'm only running stock) until this is sorted. Some nice things I'd like to play with in Pie, but not at the expense of root.
Click to expand...
Click to collapse
1674 is for Pixel2/Pixel2XL: [TAIMEN/WALLEYE] [9.0.0] [4.4.146] [CLANG 7.… - Pg. 284 | Google Pixel 2 XL

Anyone try going from 8.0.0 directly to 9? I haven't done updates in forever. Don't want to just try and end up messing things up for myself.

djl236 said:
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
Click to expand...
Click to collapse
I did with no problem.

I did a dirty install from Stock 8.1 with only Magisk.
Installed TWRP, Elemental and Magisk in that order rebooting to system in-between each one. It seems as soon as Magisk 16.7 is installed, many apps fail to launch or break, i.e. the Google Play Store can no longer open without force closing, Titanium Backup errors because it can't read the TB Pro key, going into settings and trying to change some things causes the UI to freeze up. But some apps like Twitch does work. Though Magisk is broken as well, i.e. Magisk Hide doesn't work but root access is detected. Safety, however, fails both on the inbuilt test in Magisk Manager and the SafetyNet app.
If I open Magisk Manager and install 16.0 apps goe back to working fine, but Magisk is still broken in the same way and SafetyNet still won't pass.
Reading back through the thread, I see that some get boot loops due to Magisk, but for others, it works fine and SafetyNet passes which I find odd... Either way, I guess we'll all have to wait for the next Magisk update!
EDIT:
Turns out, running the Magisk Uninstaller zip, then flashing the Magisk 16.7 zip seems to solve the issue!
Can confirm Magisk Hide now works and SafetyNet passes. Seems like running the uninstaller is a good step to add into this guide if the user was previously running Magisk.

Root Stock/Custom ROMs using Magisk

Hey Guys, I have created a Guide on How to Root Mi A2 on Stock ROM or Custom ROM, Just click on
PHP:
Your warranty is now void.
I am not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
Install Magisk on Stock Roms Oreo & Pie
Needs:
- Unlocked Bootloader
Procedure:
- Download the Respective patched_boot_buildno.img file for your Build Number.
- Rename the patched_boot_buildno.img file to "patched_boot.img" and past it to your adb folder.
- Download and move Magisk Manager apk file to Internal Storage
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
- Now open command window in your adb folder and use the following command
PHP:
fastboot boot patched_boot.img
Your phone shoulds boot
- Install Magisk Manager apk
- Open Magisk Manager
- Click Install then choose Direct install. Reboot.
Done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using following commands
PHP:
fasboot flash boot_a boot.img
fasboot flash boot_b boot.img
Install Magisk on Custom Roms
Needs:
- Be on a Custom Rom
- Latest Magisk Beta zip check Dowloads Section
- Latest TWRP.img check Dowloads Section
Procedure:
- Download the latest Magisk Beta or Stable zip from Downloads Section
- Download the latest TWRP Recovery image file from Downloads Section
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
PHP:
fastboot boot twrpfilename.img
- Phone will boot TWRP Recovery.
- Navigate to Advanced > Adb Sideload
- Swipe to allow
- Open command prompt in ADB Folder on your PC
Code:
PHP:
adb sideload magisk_version.zip
Reboot and done, you have Magisk on your device.
To Uninstall it, Download Magisk uninstalled zip and flash it via twrp or do the same process with
PHP:
adb sideload magisk_uninstaller.zip
Downloads Section:
Boot / Patched Boot images
Magisk Thread for Beta zip / Apk file
Twrp images & zip

:/ okay