Database Users

[GUIDE] Pixel XL Android 8(OREO) Unlock/Install Stock Images + Kernels/Recovery +

[Guide] Pixel XL Android 8.0.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + November Security Patch
Other Pixel XL Guides:
Android 9.0.0 (Pie), Android 8.1.0 (Oreo), Android 7.1.2 (Nougat)​
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'.
This Guide also works for the Pixel: If, you download the correct files for the Pixel.
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
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 Android8/Oreo Factory Image
Pixel XL (Fi/Canada) - marlin-opr1.170623.032-factory-990d8d51.zip
Pixel XL (other carriers) - marlin-opr3.170623.013-factory-af0b6564.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 Android SDK or Platform tools installed.
Important: Update Android SDK or Platform Tools, regularly, for optimal performance.
Need help installing Android SDK or using SDK Platform tools:
How to Install ADB & Fastboot on Mac, Linux & Windows-(Method 1)
Using the SDK Platform-Tools
Credits/Thanks/Recognitions
TWRP
TEAM TWRP - TWRP 3.2.0-0 for Google Pixel XL
Special thanks to @gubacsek - for [MOD][RECOVERY] Working TWRP recovery for Pixel/Pixel XL on Android O
SuperSU/suhide/Flashfire
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
[Android 4.2+][ROOT][2017.09.21] FlashFire v0.73 by Chainfire
FlashFire Documentation
Magisk/MagiskManager
[BETA][2017.11.24] Magisk v14.5 (1456) by*topjohnwu
[DEV] [Magisk] Official Pixel (XL) Support is Here! by topjohnwu
Magisk Manager Releases topjohnwu
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
Special thanks to @goodwin_c - for [Unofficial] Google Pixel family support
Custom Kernels
[KERNEL] [November 16] ElementalX 2.03 (Oreo) by flar2
[KERNEL][28.11.2017] Kirisakura-Harmony-O 2.12 [3.18.84][ANDROID OREO][SCHEDUTIL] by Freak07
[KERNEL/ROM]Sharkey Kernel and Uberstock for Pixel/Pixel XL by DespairFactor
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
Custom ROMs
[ROM][Pixel-XL][8.0.0_r17] Pixel Dust OREO for marlin [ALPHA] by spezi77
Other
spaceman860 - TWRP 3.1.1-1 Backup
Special Thanks to LeMoise - for the Root with Magisk remain Stock - Pass SafetyNet and Receive OTA Updates. It was nice while it lasted. Sorry, it stopped working with the November Security Patch.
Those I may have, inadvertently, forgotten.
Index
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 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.
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 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 USB cable.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock 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:
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 reads 'Your device software can't be checked for corruption. Please lock the bootloader' You will receive this warning until, you relock the bootloader.
Important: do not repeat do not relock your bootloader unless your phone is fully stock. You must flash the factory image 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 #13 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 appropriate Factory/System 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-aaa9.999999.999.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following and press enter.
Code:
flash-all
Install Factory Image and keep data
Important: If upgrading to Android8/Oreo from Android7/Nougat 7.x.x. Do #4 - Install Factory Image and wipe data
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
Edit flash-all.bat: remove -w
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa9.999999.999.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following and press enter.
Code:
flash-all
Install Custom Kernel
Flash with TWRP
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Backup your data and Internal storage
Download files:
Factory Image for Nexus/Pixel Devices to your Computer
TWRP 3.2.0-0 for Google Pixel XL
Custom Kernel - to your Phone
[KERNEL] [November 16] ElementalX 2.03 (Oreo) by flar2
[KERNEL][28.11.2017] Kirisakura-Harmony-O 2.12 [3.18.84][ANDROID OREO][SCHEDUTIL] by Freak07
[KERNEL/ROM]Sharkey Kernel and Uberstock for Pixel/Pixel XL by DespairFactor
SuperSU - to your Phone
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
Fastboot the boot.img.
Use a File Explorer to extract the contents of your factory image.Open the folder it creates and, extract the second archive (image-marlin-aaa9.999999.999.zip)
Then open the folder it creates and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the device/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, and leave your phone in bootloader mode, and connected to your Computer.
Install TWRP
Place twrp-3.2.0-0-marlin.img in your platform-tools folder and Rename it twrp.img
Type the following command at the prompt:
Code:
fastboot boot twrp.img
Flash Zips.
When TWRP boots on your phone, Tap the Install button, and select twrp-pixel-installer-marlin-3.2.0-0.zip
Reboot Recovery
Tap the Install button, and select a Custom Kernel
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Swipe the slider to install.
Reboot System
Boot Recovery
Tap the Install button, and select SR5-SuperSU-v2.82-SR5-20171001224502.zip
Swipe the slider to install.
Note: The sequence of flashing the zips is important
Reboot System
Install BusyBox to/sbin/supersu/xbin.
Flash with Flashfire
Warning: "FlashFire is an extremely powerful application, it should be used with caution. Data loss, soft-bricks, and even hard-bricks are possible if used incorrectly. Unless you are an expert user, consult FlashFire's website and this thread before doing anything potentially destructive."
Backup your data and Internal storage
Install Application:
Install Flashfire Application from Google's Play Store
Open Flashfire Grant Root
Tap Plus Sign (+)
Tap Flash ZIP or OTA
Locate/Navigate to ZIP File location
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Tap file
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Check the Restore boot and recovery images box
Tap Checkmark (Top right corner)
Verify before you Flash
Flash ZIP or OTA - Has the file you want to flash and ✓ Restore boot and recovery images is present.
If not repeat 2. Flash with Flashfire d through h above.
EverRoot - ✓ Inject SuperSU is present.
If not, Tap EverRoot Select Inject SuperSU
Reboot should default to ✓ Normal.
Tap Flashfire symbol to Flash file
Root with SuperSU
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Backup your data and Internal storage
Download files:
TWRP 3.2.0-0 for Google Pixel XL
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire to your Phone
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Boot Bootloader
Connect device/phone to Computer
Open a Command Prompt on your computer.
Type the following command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, and select
twrp-pixel-installer-marlin-3.2.0-0.zip
Reboot Recovery
Tap the Install button, and select
SR5-SuperSU-v2.82-SR5-20171001224502.zip
Swipe the slider to install.
Reboot System.
Note: Install BusyBox to/sbin/supersu/xbin.
Root with SuperSU - Pass Safetynet
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Note: If you did #6 - Install Custom Kernel or #7 - Root with SuperSU, above you already have root. Start at m..
Backup your data and Internal storage
Download files:
TWRP 3.2.0-0 for Google Pixel XL
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
SR5-SuperSU-v2.82-SR5-20171001224502.zip to your Phone
UPDATE-suhide-v1.09-20171001222116.zip to your Phone
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
Busybox
There are several different versions (Free and Pro, see Credits/Thanks/Recognitions above) find one that works for you.
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Boot Bootloader
Connect device/phone to Computer
Open a Command Prompt on your computer.
Type the following Command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select twrp-pixel-installer-marlin-3.2.0-0.zip
Reboot Recovery
Tap the Install button, select SR5-SuperSU-v2.82-SR5-20171001224502.zip
Swipe the slider to install.
Reboot System.
Boot Recovery
When TWRP boots on your phone, tap the Install button, Select
UPDATE-suhide-v1.09-20171001222116.zip
Swipe the slider to install.
Reboot System
Note: Install BusyBox to /sbin/supersu/xbin.
Root with Magisk - Pass SafetyNet
Important: I haven't tested Magisk 14.5 or Magisk Manager 5.4.3. If you have problems redo #9 substitute Magisk 14.3 for Magisk 14.5 and Magisk Manager 5.4.0 for Magisk Manager 5.4.3.
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Install TWRP, Custom Kernel, Magisk, and Busybox.
Backup your data and Internal storage
Download files:
TWRP 3.2.0-0 for Google Pixel XL
twrp-3.2.0-0-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.2.0-0.zip to your Phone.
Custom Kernel (Optional) - to your Phone
[KERNEL] [November 16] ElementalX 2.03 (Oreo) by flar2
[KERNEL][28.11.2017] Kirisakura-Harmony-O 2.12 [3.18.84][ANDROID OREO][SCHEDUTIL] by Freak07
[KERNEL/ROM]Sharkey Kernel and Uberstock for Pixel/Pixel XL by DespairFactor
Magisk
[BETA][2017.11.24] Magisk v14.5 (1456) by*topjohnwu
Magisk-v14.5 (1456).zip to your Phone.
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
Magisk-uninstaller-20170928.zip to your Phone
Flash boot.img.
Use a File Explorer to extract the contents of your factory image. Open the folder it creates and, extract the second archive (image-marlin-aaa9.999999.999.zip)
Then open the folder it creates and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the device/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, leave your phone in bootloader mode and connected to the Computer.
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Type the following Command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select
twrp-pixel-installer-marlin-3.2.0-0.zip
Swipe the slider to install
Reboot Recovery
Tap Install, select Custom kernel (Optional)
Note: If you do not want to install a Custom Kernel go to n below.
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Swipe slider to install
Reboot System
Boot Recovery
Tap Install, select Magisk-v14.5 (1456).zip
Swipe slider to install.
Reboot System
Install BusyBox (Optional)
Open Magisk Manager, tap Menu, tap Modules, verify Busybox for Android NDK is checked.
Root with Magisk - Pass SafetyNet without installing TWRP
thanks stryker09
Important: Set Pin before using TWRP: Setting > Security > Pin.
Backup your data and Internal storage
Read/Do (as applicable) #1 - Command Prompt/Boot Bootloader/Boot Recovery; #2 - Testing ADB (Android Debug Bridge)/fastboot; #3 - Unlock Bootloader; #5 - Install Factory Image and keep data; and Tips and Tricks -OTA Installation Tips
Download files:
TWRP 3.2.0-0 for Google Pixel XL to your Computer.
[BETA] Magisk v14.5 (1456) by topjohnwu
Magisk-v14.5 (1456).zip to your Phone.
Flash boot.img.
Use a File Explorer to extract the contents of your factory image. Open the folder it creates and, extract the second archive (image-marlin-aaa9.999999.999.zip)
Then open the folder it creates and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the phone to your Computer via USB cable.
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, leave your phone in bootloader mode and connected to the Computer.
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Type the following Command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots up, tap Install, select Magisk-v14.5 (1456).zip
Swipe Slider to Install
Reboot System
Install BusyBox (Optional)
Open Magisk Manager, tap Menu, tap Modules, verify Busybox for Android NDK is checked.
Custom ROMs for Pixel XL
[ROM][Pixel-XL][8.0.0_r17] Pixel Dust OREO for marlin [ALPHA] by spezi77
Other - TWRP Backup
Boot Recovery.
Tap Backup and select Partitions to backup
Boot
System Image
Vendor Image
Data (Optional)
Swipe Slider to backup
Reboot System
Your backup will be stored in /Storage/Emulated/0/TWRP/...
Return to Stock and Lock Bootloader
Return to Stock
Backup 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-aaa9.999999.999.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.:
Type the following command at the prompt, and press enter.
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 command 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
Audio Mod
[GUIDE] How to install ARISE sound on 8.0 Magisk by kingbri
[GUIDE] ARISE magnum OPUS on magisk android 8.0 by kingbri

getting viper4android to work would be great.
busybox refused to install

TheUndertaker21 said:
getting viper4android to work would be great.
busybox refused to install
Click to expand...
Click to collapse
Arise works perfectly.

jaxenroth said:
Arise works perfectly.
Click to expand...
Click to collapse
which one did you flash ?

jaxenroth said:
Arise works perfectly.
Click to expand...
Click to collapse
Please more info about version and install settings!
I am trying at the moment v4a get to work with bootable twrp..... Would appreciate further info a lot.

Hi, step 3, first code should be fastboot flash bootloader bootloader.img and not fastboot flashbootloader bootloader.img
(i.e there is a gap between flash and bootloader)

To root mine all I did was chainfires boot-to-root. Then you can install and substratum theme with O support. I'm using the Swift black theme. You have to install only 5 at a time or it won't work. It says in the description for the app. My Android O is blacked out now and I'm happy.

Why is it claiming it must be a Google purchased phone? Many Verizon users have an unlocked bootloader.

TheUndertaker21 said:
which one did you flash ?
Click to expand...
Click to collapse
ARISE+Deuteronomy+2.94+Modular Aroma Installer

jaxenroth said:
ARISE+Deuteronomy+2.94+Modular Aroma Installer
Click to expand...
Click to collapse
getting abnormal when i flashed that
it worked when i use supersuconfig in permissive mode but i lost root when i do
do you still have root ? and how did you manage to get it

{
"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"
}
I flashed SU from TWRP, booted into system, from there adb'd back to BL and booted TWRP again and flashed aroma installer.

Is the aroma installer necessary for just being stock rooted with adaway? Or would I just fastboot boot twrp then flash latest SuperSU and reboot?
Sent from my Nexus 6P using Tapatalk

waiting for nexus 6p

TheUndertaker21 said:
getting viper4android to work would be great.
busybox refused to install
Click to expand...
Click to collapse
Updated OP with BusyBox path information.

grifforama said:
Hi, step 3, first code should be fastboot flash bootloader bootloader.img and not fastboot flashbootloader bootloader.img
(i.e there is a gap between flash and bootloader)
Click to expand...
Click to collapse
Thanks for the 'editing' help.

encephalon9986 said:
To root mine all I did was chainfires boot-to-root. Then you can install and substratum theme with O support. I'm using the Swift black theme. You have to install only 5 at a time or it won't work. It says in the description for the app. My Android O is blacked out now and I'm happy.
Click to expand...
Click to collapse
Yeah, there's more than one way to root, I prefer Chainfire's SuperSU. Thanks for the Substratum information.
Which Substratum theme engine and version did you use?

Mike02z said:
Why is it claiming it must be a Google purchased phone? Many Verizon users have an unlocked bootloader.
Click to expand...
Click to collapse
A case of CRS (can't remember s#*t) Lol. I just forgot to change it. Thanks for the reminder.

jaxenroth said:
View attachment 4249400 I flashed SU from TWRP, booted into system, from there adb'd back to BL and booted TWRP again and flashed aroma installer.
Click to expand...
Click to collapse
Great!

Neverendingxsin said:
Is the aroma installer necessary for just being stock rooted with adaway? Or would I just fastboot boot twrp then flash latest SuperSU and reboot?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, "just fastboot boot twrp then flash latest SuperSU and reboot"
This is a Pixel XL thread.

Chouiyekh said:
waiting for nexus 6p
Click to expand...
Click to collapse
This is a Pixel XP thread.

[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.

[AIO GUIDE] Install Magisk with OTA +Make your own patched_boot...

Hey ! Today i will give you all the different ways/steps for root your Mi A2 easily.
+ How to manually create patched_boot.img for your version (beta...) without extrernal help.​
Code:
Your warranty is now void.
We are not responsible for bricked devices, dead
SD cards... Please do some
research if you have any concerns about features
included in this GUIDE before using it! YOU are
choosing to make these modifications.
Summary
- Part 1 : Install drivers and unlock bootloader. Credit to @balazs312
- Part 2 : Root with 2 ways
- Bonus : Backup boot.img and make patched_boot.img
- Part 3 : OTA
Part 1 :
So, First you need to install drivers and unlock your phone bootloader. Skip to part 2 if already done.
1. Installing drivers & Preparing PC
- Download this and extract it
- Open and install "adb-setup-1.4.3.exe"
- When it is done, go to "Drivers" folder and start "miflash_unlock.exe"
- Click on the gear icon top right corner and click on "Check" next to "Click the button to install the drive"
- Do as the installer says
- Hopefully the drivers has been installed so we're done with it, let's head on the next step.
2. Preparing phone for unlocking
- On your phone navigate to Settings->System->About phone and tap the build number until you see "You are developer"
- Go back once and you'll see a new menu called "Developer options"
- Tap on it and search an option called "OEM Unlocking", enable it
- We're done here. Let's keep going
3. Entering fastboot and unlocking bootloader (MAKE A BACKUP of your data!)
- Hold your power button down, tap on restart and hold your volume DOWN button while it resets until you see the Mi bunny doing its thing
- Now we're in Fastboot mode, hooray
- Download this zip and extract it on your PC
- Open it and type "cmd" (without the quotations) in the file manager header where you see (This computer>somethingsomething>Mi A2 fastboot), don't be afraid just type it in, and hit enter and you'll enter into command prompt
- Now we are ready for action
- Type these commands one by one:
fastboot flashing unlock
fastboot flashing unlock_critical
After this, you will see a warning message that your bootloader is unlocked and your data is not safe, blah blah... Just ignore it everytime you power on your phone.
Part 2 :
So there are currently two ways to root his phone. Let's start with the first.
Methode 1 : We will use the new temp twrp. Method by me.
1. Download files...
- Download this TWRP.
- Place it in your adb folder.
- Download Magisk-v17.2_a and Magisk-v17.2_b.
- Copy these 2 zips in your phone internal storage.
2. Check current-slot...
- Plugin your phone to you pc
- Navigate to your settigs on your phone.
- Open Developer settings
- Enable Usb Debugging
- A pop up should appear on your phone scren, hit and box and autorize the pc.
- on your pc, open fastboot command prompt, and type "adb reboot bootloader" , your device should reboot to fastboot
- type "fastboot getvar current-slot". Remember if the result is a or b.
3. Root using temporally twrp
- Reboot your phone in fastboot.
- On your pc, open fastboot command prompt, and type "fastboot boot twrp-3.2.3-jasmine-20181020.img"
- Your phone now reboot into twrp, it down't flash it, so after a reboot twrp will be gone.
- If twrp ask a password for decrypt data put your phone PIN and validate.
- Click on install and select Magisk-v17.2_a if the result in Step 2. is A, and Magisk-v17.2_b if result is B and swipe to install.
- Then select Reboot.
Now you have Magisk 17.2 installed on your phone, and twrp is gone after reboot. You can select beta in Magisk settings and update to 17.3 if you want.
Methode 2 : We will use patched_boot.img.
1. Where to find patched_boot.img ?
- Go here and check if there is your build version. If yes dowload the patched_boot.img file ( need to be on pc ) and skip to step 2. If not continue.
- If you can't find your correct build patched_boot.img (Because you are on the beta, and nobody share the file or something like that....) you can easily make your own using temp twrp. Go to Bonus part, make your patched_boot.img and continue.
2. Pepare files.
- Copy the patched_boot.img in your adb folder
- Be sure to rename it to "patched_boot.img"
- Download latest Magisk Manager apk here (currently v6.0.1)
- Copy the apk on your phone storage.
3. Install Magisk
- Reboot your phone in fastboot.
- Open a fastboot command prompt on your pc.
- Type "fastboot boot patched_boot.img"
- Your phone will reboot, put your pin....
- Go in your prefer file explorer and Install the magisk apk.
- Now open Magisk Manager app
- Click Install, direct install. Wait for the process
- And click reboot.
Now you have Magisk 17.2 installed on your phone. You can select beta in Magisk settings and update to 17.3 if you want.
Bonus
So, i will show you how to backup your current bot img. And how to make your own patched_boot.img, so people who are on Beta OTA can root there phone without any external help...
1. Backup the boot.img
- Download this TWRP.
- Place it in your adb folder.
- Reboot your phone in fastboot.
- On your pc, open fastboot command prompt, and type "fastboot boot twrp-3.2.3-jasmine-20181020.img"
- Your phone now reboot into twrp, it down't flash it, so after a reboot twrp will be gone.
- If twrp ask a password for decrypt data put your phone PIN and validate.
- In TWRP, click on "Advanced"
- Click "File Manager"
- Navigate to /dev/block/platform/soc/c0c4000.sdhci/by-name
- You will se a lot of files, and if you look you will see 3 important files, boot, boot_a and boot_b.
- Click on the "boot" file
- Click "Copy File"
- Navigate to /sdcard
- Click the blue arrow and swipe to confirm
- Click reboot
- Copy the file on your pc, and rename it to "boot.img" instead of "boot".
Now you have backup your stok boot.img you can use it for stock or whatever you want....
2. Create the patched_boot.img file
- Download latest Magisk Manager apk here (currently v6.0.1)
- Install the apk on your phone
- Open Magisk Manager
- Go to settings , click Update Channel and select Beta
- Return to home of Magisk Manager
- Click Install, then Boot image file patch ( don't know the correct typo because for me the app is in french, champion du monde !! xD ) and wait for the end of the process.
Done you now create your own patched_boot.img ! Enjoy !!
Part 3 :
So, now i will explain you how to install OTA when you have magisk.
- First, disable Automatic system updates in developer options, so it won't install OTAs without your acknowledgement.
- Open Magisk Manager, click Uninstall, then Restore Images. Don't reboot !
- Now Search for update and wait for the process. BUT do not press the "Restart now" or "Reboot" button !
- Open Magisk Manager, hit Install, then Install to inactive slot.
- Reboot when it's done.
If it don't work (strange) and ota failed, you can find your stock boot.img for your build version here, or backup your boot.img using the[ B]1.[/B] of the Bonus part and flash it using the command "fastboot flash boot_( your current slot) boot.img" (you can check your current slot with command "fastboot getvar current-slot).
If you have issues or something like that, here are some telegram group :
MiA2dev
MiA2OffTopic
HexKernel

Work perfect with october update
Thanks 4 your great work

nnexuss said:
Work perfect with october update
Thanks 4 your great work
Click to expand...
Click to collapse
Your wellcome, enjoy

Thx for your very, very good work. No Problems at all with October update. :good:
mahalo

yorkberliner said:
Thx for your very, very good work. No Problems at all with October update. :good:
mahalo
Click to expand...
Click to collapse
nice, enjoy

What to do when Magisk prompts that "Stock Image does not exist"?
Couldn't find a folder to put stock image.

0firuz said:
What to do when Magisk prompts that "Stock Image does not exist"?
Couldn't find a folder to put stock image.
Click to expand...
Click to collapse
can you explain which part you try to do, and on which steps you got this error? for more support you can join telegram groups from the bottom of the guide.
*edit* you can flash stock boot.img for future OTA. check the Part 3 : OTA

Hi
Right now im on OPM1.171019.011.V9.6.13.0ODIMIFE (5 sept 2018) rooted with magisk
I just want to update and re-root, the painless style. I dont want to flash a ****load of stuff to have a functionning phone.
Can anyone confirm that step 3 is ok? Thats the same method than for MI A1, and it was only half functionnal, i dont want to play with fire.
After having killed the IMEI numbers and the persist partition of the A1, it took me 2 weeks to repair, I dont want to **** up this one too. Hell no.

kaott said:
Hi
Right now im on OPM1.171019.011.V9.6.13.0ODIMIFE (5 sept 2018) rooted with magisk
I just want to update and re-root, the painless style. I dont want to flash a ****load of stuff to have a functionning phone.
Can anyone confirm that step 3 is ok? Thats the same method than for MI A1, and it was only half functionnal, i dont want to play with fire.
After having killed the IMEI numbers and the persist partition of the A1, it took me 2 weeks to repair, I dont want to **** up this one too. Hell no.
Click to expand...
Click to collapse
this is safe. but if you want to can just use patched boot method.

I used the method described in Step 3 to install the September OTA (V9.6.13.0) and re-install Magisk. It worked like a charm, but I am trying to repeat the method to install the October update without success. The OTA updater downloads the update, and starts installing it, but it fails miserably every time.
I have even completely uninstalled Magisk and flashed the img from here: https://sourceforge.net/projects/others/files/MiA2/
But It does not work, the OTA installer always fails.
I'm clueless, what can I do?

doragasu said:
I used the method described in Step 3 to install the September OTA (V9.6.13.0) and re-install Magisk. It worked like a charm, but I am trying to repeat the method to install the October update without success. The OTA updater downloads the update, and starts installing it, but it fails miserably every time.
I have even completely uninstalled Magisk and flashed the img from here: https://sourceforge.net/projects/others/files/MiA2/
But It does not work, the OTA installer always fails.
I'm clueless, what can I do?
Click to expand...
Click to collapse
it's because during the ota process, the current slot change. but you can back to stock September ROM, then update. and after that root using my second post https://forum.xda-developers.com/mi-a2/how-to/guide-2-minutes-magisk-installation-t3856980/amp/

Thread closed at OP request

Tutorial to Flash Lineage on Oneplus8t with magisk. Works with devices with originally locked bootloader (tmobile locked models)

READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.
Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down) Recommended to use Command Prompt commands instead of powershell (type cmd in platform-tools directory) https://developer.android.com/studio/releases/platform-tools
Unlock oem bootloader
Enable developer options (click build number several times)(make sure you’re connected to internet)
Enable oem unlocking, advanced reboot, usb debugging
Reboot to bootloader/fastboot
fastboot oem unlock
Unlock bootloader
Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding volume down while
booting)
Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)
fastboot flash boot (path to boot.img)
fastboot flash dtbo (path to dtbo.img)
fastboot flash recovery (path to recovery.img)
Download firmware (https://kremowka.xyz/files/8fw/)
Enter recovery mode, enter fastbootd
Advanced > enter fastboot
Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload
LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in
there somewhere
Open notepad, copy commands from lineage, save as (file name).bat, drag into powershell from file explorer
(flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”
Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.
Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)
adb devices (to confirm phone is connected properly and device drivers are configured properly)
adb sideload (path to lineage 19.1 .zip)
Sideload will likely get stuck at 47%. This is normal. Just wait.
Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)
adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are
too large. Just download them all from google play store once booted.
Signature verification failed will pop up, just confirm “yes”
Reboot recovery?
adb sideload (path to copy partitions .zip)
Back > Reboot system now
It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have
data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done
that before this step (do it in fastboot, search up adb shell pull)
If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something
happened.
OPTIONAL (if you want magisk/root)
Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on
Search in settings for “advanced”, click “advanced restart” and enable
Hold power button, restart, recovery
Apply update > apply from adb
adb devices
adb sideload (path to magisk .apk)
Signature verification failed, install anyway
Volume up to go to back arrow, reboot system now
Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts
Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file
transfer is on
DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
What I use: Safetynet universal fix and raven.A12L (spoofs as pixel 6 pro to let safetynet work)
Install from storage
Order I did it in was safetynet then raven, rebooting between each one but I'm not sure if it matters
Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click
google play services, google play store, and carrier services (the square check box next to the name, make sure
every check below when you open it as a dropdown menu is checked
Reboot phone
Now you can download whatever you want
If you install twrp, make sure you are using android 12 version and not android 11, android 11 twrp will destroy
your recovery if you try to use it on android 12.
Add on: If your phone is not detected by your pc, or is detected as “MTP” with an exclamation mark, you do not
have the right drivers. There are plenty of resources online to fix this, but one that I had trouble with was that I
was on windows 10 N instead of whatever the other version is, which doesn’t come with “mediafeaturepack.”
You need to install that on your own from https://www.microsoft.com/en-us/software
download/mediafeaturepack, or, if your device isn’t listed, go to windows application “optional features” and
add it from there.
If your computer won’t download qdloader 9008 qualcomm drivers through device manager, there are a few
things i’ve tried to fix it. Make sure you have correct drivers
from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
“The system cannot find the file specified”
Open command prompt as administrator
Type DISM /Online /Add-Package /PackagePath:"Full path of .cab file"
I put mine in C: drive folder but I'm not sure it matters
Also I'm not sure which one of the three I downloaded from the website. Did not cause any issue downloading
and trying to install all three, let me know if you figure out which one works. Maybe you need all three, I don’t
know.
If that doesn’t work, do sfc /scannow
Open windows update, make sure all updates are applied and restart windows (make sure you go to optional
updates and select qualcomm drivers)
Fastboot won’t connect
Make sure you’re using a usb 2.0 port instead of a usb 3.0 port, and make sure your usb cable is a data cable.
Google the difference if you don’t know what it is. Download usb drivers
from https://developer.android.com/studio/run/win-usb, open device manager, see if anything is there, if it
shows something in “other devices” click on it, click update drivers, browse my computer, let me pick, have disk,
and then browse to android_winusb.inf and click update, click bootloader interface. If you get “error 10 device
won’t start” when installing bootloader interface, one possible solution is to disable driver signing.
Open command prompt as an administrator (doesn’t have to be in platform tools directory)
bcedit /set testsigning on
Reboot, try to install driver again.
If your device is bootlooping, and you enter fastboot after updating to a12 firmware AND you have magisk\
modules downloaded AND you have twrp installed, do not press the up volume button, only cycle through
options with volume down, because it may enter an option cycle and you won’t be able to do anything unless
you fastboot flash boot twrp.img.
It’s recommended that as soon as you root, you backup persist.img, which contains imei info (you don’t want
that to get destroyed) I am unsure if there’s anything else device specific you need to backup, I've heard
vendor_image may be but it’d not as important as persist.
To backup persist.img, put phone in recovery, type in command prompt or powershell
adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
adb pull /tmp/persist.img persist.img
This should save persist.img to your computer. Back it up somewhere you keep important things. Also don’t
give it out at random as it contains your imei number, not sure what the consequences of that could be but
nothing good is likely to come of it.
Important shortcuts:
Power + vol up – boot into system
Power + vol down – boot into fastboot
Power + vol up + vol down – boot into edl
IF DEVICE IS BOOTLOOPING AND YOU CAN’T ENTER ANY DIFFERENT MODES, CONTINUE HOLDING POWER +
VOL DOWN IN RANDOM PATTERNS. IT HAS TAKEN ME 20 MINUTES OF RANDOM BUTTON COMBINATIONS TO
GET INTO FASTBOOT FROM A BOOTLOOP. YOU WILL ALWAYS BE ABLE TO EXIT A BOOTLOOP IF YOUR PHONE
IS PHYSICALLY UNDAMAGED.
If VoWifi doesn’t work, pixelify dialer can get it working. Probably also just any custom dialer, but I like Google
dialer. Wait for the interface to change slightly, don’t clear data until you’ve waited at least a minute or two and
closed and reopened it a few times, but if it doesn’t change after installing pixelify then force close, clear data,
and wait a minute or two, reopen, and then wait. If it continuously doesn’t change you can reflash pixelify.
Note – If using pixelify module, disable auto update for android system intelligence, it will break gboard
translate and possibly slow down device.
You can also use magisk module “mindetach” to detach com.google.android.as from play store, which will fix
any auto update bugs. Credit to vewu for showing me that
https://github.com/j-hc/mindetach-magisk
https://github.com/Pixel-Props/raven/releases
https://github.com/kdrag0n/safetynet-fix
Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community.
Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.
Apologies for formatting, this is copied from a word doc. Please feel free to indent and number list yourself and
send me a better version

Does the third option work?

INTseed said:
Does the third option work?
Click to expand...
Click to collapse
did you configure the denylist? try clearing cache and data for google play services, google play store, and carrier services and rebooting

Mrmcfeffers said:
READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.
Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down)
a. Unlock oem bootloader
i. Enable developer options (click build number several times)(make sure you’re connected to internet)
ii. Enable oem unlocking, advanced reboot, usb debugging
iii. Reboot to bootloader/fastboot
iv. .\fastboot oem unlock
v. Unlock bootloader
b. Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding
volume down while booting)
2. Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)
a. .\fastboot flash boot (path to boot.img)
b. .\fastboot flash dtbo (path to dtbo.img)
c. .\fastboot flash recovery (path to recovery.img)
3. Download firmware (https://kremowka.xyz/files/8fw/)
4. Enter recovery mode, enter fastbootd
a. Advanced > enter fastboot
5. Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in there somewhere
a. Open notepad, copy commands from lineage, add .\ before each line, save as (file name).bat, drag into powershell from file explorer (flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”
b. Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.
c. Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)
i. .\adb devices (to confirm phone is connected properly and device drivers are configured properly)
ii. .\adb sideload (path to lineage 19.1 .zip)
Sideload will likely get stuck at 47%. This is normal. Just wait.
d. Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)
i. .\adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are too large. Just download them all from google play store once booted.
Signature verification failed will pop up, just confirm “yes”
e. Reboot recovery?
i. .\adb sideload (path to copy partitions .zip)
6. Back > Reboot system now
a. It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done that before this step (do it in fastboot, search up adb shell pull)
7. If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something happened.
8. OPTIONAL (if you want magisk/root)
9. Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on
a. Search in settings for “advanced”, click “advanced restart” and enable
b. Hold power button, restart, recovery
10. Apply update > apply from adb
a. .\adb devices
b. .\adb sideload (path to magisk .apk)
i. Signature verification failed, install anyway
ii. Volume up to go to back arrow, reboot system now
11. Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts
a. Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file transfer is on
12. DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
a. What I use: Safetynet universal fix, disableflagsecure (lets you screenshot netflix lol), and raven.A12L (spoofs as pixel 6 pro to let safetynet work)
i. Install from storage
ii. Order I did it in was safetynet, then raven, then flag secure rebooting between each one but I'm not sure if it matters
b. Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click google play services, google play store, and carrier services (the square check box next to the name, make sure every check below when you open it as a dropdown menu is checked
c. Reboot phone
13. Now you can download whatever you want
https://github.com/Pixel-Props/raven/releases
https://github.com/kdrag0n/safetynet-fix
https://forum.xda-developers.com/t/disable-flag-secure-magisk-module-v3-0-by-mehedi-hjoy.4490475/
Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community. Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.
Apologies for the ****ty formatting, i copied this from a word document. I don't know how to paste the indents.
Click to expand...
Click to collapse
How can you claim this 'works on locked bootloader', when right at your ( 2) you say 'unlock bootloader'. And if your instructions require unlocked bootloader (which they surely do), then they are useless, because once your bootloader is unlocked, you can simply flash Magisk with recovery.

optimumpro said:
How can you claim this 'works on locked bootloader', when right at your ( 2) you say 'unlock bootloader'. And if your instructions require unlocked bootloader (which they surely do), then they are useless, because once your bootloader is unlocked, you can simply flash Magisk with recovery.
Click to expand...
Click to collapse
modded msm tool allows bootloader unlocking

Mrmcfeffers said:
modded msm tool allows bootloader unlocking
Click to expand...
Click to collapse
What does this have to do with your 'working on locked bootloader'? That statement is false. You can't flash anything on locked bootloader, and if you unlock bootloader, then you can simply flash Magisk via recovery without the need for your 'method'.

optimumpro said:
What does this have to do with your 'working on locked bootloader'? That statement is false. You can't flash anything on locked bootloader, and if you unlock bootloader, then you can simply flash Magisk via recovery without the need for your 'method'.
Click to expand...
Click to collapse
seems to have worked for me. i meant "working on locked bootloader" as in it include steps to unlock. it's also a guide to installing lineage, not just magisk. i'm not sure what issue you have here, it's a specific tutorial for a specific problem.

Mrmcfeffers said:
seems to have worked for me. i meant "working on locked bootloader" as in it include steps to unlock. it's also a guide to installing lineage, not just magisk. i'm not sure what issue you have here, it's a specific tutorial for a specific problem.
Click to expand...
Click to collapse
It's just a decription in thread name that is a bit misleading.
At first it appears like it can be done on locked bootloader.
And it's obviously not, as stated in your instruction point #2.
Otherwise, nice tutorial.

Mrmcfeffers said:
DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
Click to expand...
Click to collapse
So is acc incompatible with this device? Or is this a warning only at that step in the tutorial?

jinncarry said:
So is acc incompatible with this device? Or is this a warning only at that step in the tutorial?
Click to expand...
Click to collapse
Don't use acca from f-droid. Acc from the official GitHub (https://github.com/VR-25/acc) is fine and works perfectly