Related
[Guide] Pixel XL Android 7.1.2 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2017 Security Patch
Intro
This thread is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel/Pixel XL'.
It also works for Pixel owners: If, they download the correct files for their Pixel.
This Guide is not for use with the Second Generation Pixel 2 or Pixel 2 XL devices.
Update(s):
Other - Added 'Other' after 'Prerequisites'
Disclaimers:
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Google Pixel XL or Verizon Pixel XL phone with an unlockable Bootloader, ([How-to] Unlock bootloader on Verizon Pixel/XL by burduli) - The unlock method was discovered by: Qu3ntin0), and the latest 7.1.2 August 2017, Factory Image (NHG47Q - Verizon; NKG47S - T-Mobile, Fi carriers, and Rogers; NZH54D - Deutsche Telekom; NJH47F - all other carriers).
Note: If you want the latest OTA or Binaries. Tap the Menu icon (upper left corner) then tap Full OTA Images or Driver Binaries
PC - With the latest Android SDK or SDK Platform tools installed.
Important: Update Android SDK or Platform Tools, regularly, for optimal performance.
Need help installing Android SDK or SDK Platform Tools
How to Install ADB & Fastboot on Mac, Linux & Windows-(Method 1)
Easiest-way-to-install-androids-adb-and-fastboot
Other
Pixel XL Guides: Android 9.0.0 (Pie)Android 8.1.0 (Oreo), Android 8.0.0 (Oreo)
Pixel 3 XL Guide: Android 9.0.0 (Pie)
Credit/Thanks/Recognitions
TWRP
TWRP for Google Pixel XL
twrp-3.0.2-0-RC1-fastboot-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.1.0-0RC1.zip to your phone.
twrp-pixel-installer-marlin-3.1.0-0RC2.zip to your phone
SuperSU
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
Magisk/MagiskManager
[Unofficial] Google Pixel family support by goodwin_c
Custom Kernels
ElementalX kernel
Franco's Kernel
Busybox/Busybox Checker
[MODS] Android Oreo Aroma installer misc. Mods by Tulsadiver
UPDATE-Busybox.Installer.v1.26.2-ALL-signed.zip
meekfik, download from PlayStore
Busybox Free (Stericson), download from PlayStore
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] by osm0sis
UPDATE-Busybox.Installer.v1.27.2-ALL-signed.zip
Busybox Checker, download from PlayStore
Other
pcriz -Fastboot Slot Commands, Custom ROM installion help, Magisk help, and help on many many other subjects.
Those I may have inadvertently forgotten.
Index
Open Command Prompt/ Boot Bootloader/Boot Recovery
Open Command Prompt on Computer
Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
Option 2 - Open File Explorer, click platform-tools folder, highlight the directory information in the address bar or click the folder (left side of address bar) to highlight it type 'cmd' and press enter.
Note: If your computer only has 'open powershell here' in the context menu and you do not want to change it or add open 'command prompt here' use use option 2.
Boot Bootloader:
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Press volume Up/Down button until you see Recovery Mode > Press Power button.
Testing ADB (Android Debug Bridge)/fastboot
ADB
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Type this at the prompt and press enter to test ADB.
Code:
adb version
It should return a version number for ADB.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot bootloader.
Connect your phone to your computer with a USB cable.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock Your Bootloader
Backup your data and Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Build Number. Tap Build Number until you see you're a Developer. Tap back > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot Bootloader
Connect your phone to your computer via USB cable.
Open a Command Prompt on your computer.
Type the following at the prompt and press enter:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to make your selection.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll be greeted with a warning that says Your device software can't be checked for corruption. Please lock the bootloader everytime you reboot. It's ok, as long as your bootloader is unlocked it will stay there.
Important: do not repeat do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see 9 of this guide for instructions on how to return to stock and lock the boot loader.
Install Factory Image and wipe data
Backup your data and Internal storage
Download the factory image for your phone and carrier.
Unzip factory Image
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following at the prompt and press enter.
Code:
flash-all
Install Factory Image and keep data
Backup your data and Internal storage
Download the factory image for your phone and carrier.
Unzip factory Image
Edit flash-all.bat: Remove -w
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following at the prompt and press enter.
Code:
flash-all
Install A Custom Recovery and Root with SuperSU
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Important: Make and restore nandroid backups with TRWP RC1 zip. Some, users have reported problems creating/restoring nandroid backups with TWRP RC2 zip.
Backup your data and Internal storage
Download files:
twrp-3.0.2-0-RC1-fastboot-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.1.0-0RC1.zip to your phone.
twrp-pixel-installer-marlin-3.1.0-0RC2.zip to your phone.
[STABLE][2017.05.27] SuperSU v2.82 by SuperSU Release to your phone.
Copy the following file to the platform-tools folder: twrp-3.0.2-0-RC1-fastboot-marlin.img rename it twrp.img
Boot Bootloader
Connect device/phone to computer
Open a Command Prompt on your computer.
Type the following at the Prompt.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
Tap Add more ZIPs button, select SuperSU-v2.82-201705271822.zip
Swipe the slider to install.
Reboot system
Install A Custom Recovery and Root with Magisk (Clean Install)
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Important: Make and restore nandroid backups with TRWP RC1 zip. Some, users have reported problems creating/restoring nandroid backups with TWRP RC2 zip.
Note:[Substratum] theme Spectrum does not work with Magisk root.
Backup your data and Internal storage
Download the following files:
ElementalX-P-1.14.zip for Pixel XL
twrp-3.0.2-0-RC1-fastboot-marlin.img
twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Magisk-v13.3-Pixel-b4.zip
MagiskManager-5_1_1.apk
Magisk-uninstaller-20170720.zip
Flash Boot.img - If you have TWRP, SuperSU, or a custom kernel installed.
Extract the contents of your factory image and open the folder it creates. From there, extract the second archive (image-marlin-aaa99a.zip)
Then open that folder and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the phone to your computer
Open a Command Prompt on your computer.
Type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
When it finishes, leave the command prompt window open, your phone in bootloader mode and connected to your computer.
Install TWRP
Place twrp-3.0.2-0-RC1-fastboot-marlin.img in your platform-tools folder and Rename it twrp.img
Type the following command at the prompt:
Code:
fastboot boot twrp.img
When TWRP boots, tap the Install button and select twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Swipe the slider to install
Press the back button until you are on TWRP's main menu select Reboot > Recovery.
Flash the ZIPs
Disconnect your phone from your Computer.
Tap the Install button, then navigate to the files you downloaded.
Select the Magisk Uninstaller.zip, tap the Add more ZIPs button.
Select the twrp-pixel-installer-marlin-3.0.2-0-RC2.zip.
Swipe to install
Reboot Recovery
Tap the Install button select a Custom Kernel: ElementalX-P-1.1x.zip or Franco's Kernel-r1x.zip.
Tap Add more ZIPs button select Magisk-v13.3-Pixel-b4.zip, tap the Add more ZIPs button and select: twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Swipe to install
Note: During the Installation of ElementalX, ElementalX's AROMA installer interface, will require your input: So, tick I agree, then tap Next a few times and press Install ElementalX when prompted.
When ElementalX AROMA installer finishes, tap Next, and Finish. After, the other ZIPs are installed.
Reboot System
Note: If you're prompted to install the TWRP app at this point, remove check marks from two check boxes and select Do Not Install.
Install MagiskManager
Install Magisk Manager (5.1.1.apk)
Wipe data on Magisk Manager
Enable Magisk Hide
Enable Core Only Mode
Toggle on and off systemless hosts
Reboot system
Check for Latest Version, Root, and Saftey Net.
Update Magisk Dirty Flash
Download file:
Magisk-v13.3-Pixel-b4.zip or Magisk-v13.4-Pixel-beta2-build1.zip
Flash the ZIPs
Magisk-v13.3-Pixel-b4.zip or Magisk-v13.4-Pixel-beta2-build1.zip, tap the Add more ZIPs button.
Select twrp-pixel-installer-marlin-3.0.2-0-RC2.zip.
Swipe to install.
Reboot system
Check for Latest Version, Root, and Saftey Net.
Custom ROMs for Pixel/Pixel XL
[ROM][Pixel-XL][7.1.2_r24]★ Pure Nexus ★ Substratum | Fi | WiFi Calling ★[07/25/17] by BeansTown106
[ROM][Pixel-XL][7.1.2_r33][OMS] Pixel Dust for marlin [FINAL][2017/08/22] by spezi77
[ROM][Resurrection Remix v5.8.3][Android Nougat 7.1.2][OMS][07/24/17] by BDogg718
[ROM][UNOFFICIAL] LineageOS 14.1 Nightlies for the Google Pixel (marlin/sailfish) by invisiblek
Paranoid Android 7.2.1 - AOSPA - Pixel XL by freak_97
ROM][7/21/17][Marlin][7.1.2][WEEKLY]Team OctOs Oct-N by cjkacz
SCREW'D ROM
Install Custom Kernel
Franco's Kernel - SuperSu
Download file:
The latest Franco's kernel for Pixel/Pixel XL
Boot into TWRP
Press Install button select the file you downloaded
Swipe slider to install
Reboot System
ElementalX-PXL-1.xx by flar2 Kernel - SuperSU
Download files:
ElementalX kernel
[STABLE][2017.05.27] SuperSU v2.82 by SuperSU Release
Flash ElementalX zip in TWRP recovery (do not flash SuperSU-v2.82-201705271822.zip again if you're already rooted).
During the Installation, ElementalX's AROMA installer interface, will require your input: So, tick I agree, then tap Next a few times and tap Install ElementalX when prompted.
When ElementalX AROMA installer finishes, tap Next, and then Finish.
Note: If you're prompted to install the TWRP app at this point, remove check marks from two check boxes and select Do Not Install.
Franco's Kernel or ElementalX-PXL-1.xx by flar2 Kernel - Magisk
See [Unofficial] Google Pixel family support by goodwin_c for Installation Instructions.
Install Substratum Theme
SuperSU Root
Install Substratum Theme Engine from the play store.
Install [Substratum] Spectrum theme from the play store. Note: I used Substratum theme Spectrum to test the installation of Substratum with SuperSU root..
Magisk Root
Researching Information
Return to Stock and Lock Bootloader
Return to Stock
Backup your data and Internal storage
Download the appropriate factory image for your phone and carrier.
Unzip factory Image
Copy the following files to the platform-tools folder on your Computer
flash-all.bat
Verify -w is present in flash-all.bat. Example: fastboot -w update image-marlin-aaa9.999999.999.zip
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following command at the prompt.
Code:
flash-all
Lock Bootloader
Phone
Boot Bootloader
Connect your phone to your Computer with USB cable.
Computer
Open a Command Prompt on your computer.
Type the following at the prompt:
Code:
fastboot flashing lock
When it finishes the bootloader is locked.
The next step won't be needed if your Pixel XL reboots into system after bootloader relock.
You need to boot into system now, either press Power button to reboot OR issue the following command:
Code:
fastboot reboot
When your phone reboots disconnect your usb cable.
Audio Mod
Weta Audio Mod
we already have guides though
flex360 said:
we already have guides though
Click to expand...
Click to collapse
can't hurt to have an updated guide for those too lazy to read.. so many posts about "this guide is out of date" or "i dont have time to read 6 pages about other people's experiences"
Thanks for this updated guide, this was helpful. Although, in step 4 it looks like you forgot to mention flashing SuperSu.
jrhatfield said:
Thanks for this updated guide, this was helpful. Although, in step 4 it looks like you forgot to mention flashing SuperSu.
Click to expand...
Click to collapse
It has been posted several times that the June security update doesn't need the verified boot signer. Only the May update needed it.
JimSmith94 said:
It has been posted several times that the June security update doesn't need the verified boot signer. Only the May update needed it.
Click to expand...
Click to collapse
I'll research it and make changes if needed.
Great Job compiling all the information in one place. Appreciate your hard work. This should be helpful to many.
You could even update this to include flashing of Custom ROMs. And a little bit about the slot change etc. That way the guide would almost be complete.
iamjimmy said:
Great Job compiling all the information in one place. Appreciate your hard work. This should be helpful to many.
You could even update this to include flashing of Custom ROMs. And a little bit about the slot change etc. That way the guide would almost be complete.
Click to expand...
Click to collapse
Intro
The purpose of this thread is twofold:
First, it is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM...
¯\_(ツ)_/¯
About to try this with the -w flag. Is there a reason to not use a -w if I intend on rooting njh47b on a google store pixel xl?
Avasta said:
About to try this with the -w flag. Is there a reason to not use a -w if I intend on rooting njh47b on a google store pixel xl?
Click to expand...
Click to collapse
2. Install Factory Image and wipe Data
Code:
fastboot -w update image-marlin-aaa99a.zip
3. Install Factory Image and keep Data
Code:
fastboot update image-marlin-aaa99a.zip
Homeboy76 said:
2. Install Factory Image and wipe Data
Code:
update -w image-marlin-aaa99a.zip
3. Install Factory Image and keep Data
Code:
update image-marlin-aaa99a.zip
Click to expand...
Click to collapse
I was asking if there was any affect to the rooting ability of the device if you did vs didn't use the -w command. I completed my update of my phone. I never like a dirty update since it only causes problem later on. I tested it without the -w switch and everything worked (kept my data, but as mentioned dirty flashes = no good), so I went back and repeated the steps with the -w switch. Everything works like a charm. Only issue I have noticed is that Netflix is no longer compatible with my device?!? Like not really sure why, but cant install it from the play store. Will contact Netflix about this later today.
Avasta said:
I was asking if there was any affect to the rooting ability of the device if you did vs didn't use the -w command. I completed my update of my phone. I never like a dirty update since it only causes problem later on. I tested it without the -w switch and everything worked (kept my data, but as mentioned dirty flashes = no good), so I went back and repeated the steps with the -w switch. Everything works like a charm. Only issue I have noticed is that Netflix is no longer compatible with my device?!? Like not really sure why, but cant install it from the play store. Will contact Netflix about this later today.
Click to expand...
Click to collapse
Gotcha, there are no 'effects to the rooting ability of the device'.
However, some apps will not work unless you 'hide Root' with Magisk i.e. Android Pay, Netflix's, etc.
Did you root with Magisk?
Homeboy76 said:
Gotcha, there are no 'effects to the rooting ability of the device'.
However, some apps will not work unless you 'hide Root' with Magisk i.e. Android Pay, Netflix's, etc.
Did you root with Magisk?
Click to expand...
Click to collapse
I dunno about you but I have magisk hide on and hid the playstore and a few other processes but if its checking your phone at a point before you can enable magisk hide and storing the results wouldn't it not make much difference? I ask this because magisk hide or not, netflix doesnt show up. Even on a clean boot its not listed as an app I can restore. The simple fix for me is to restore a back up or simply download from apk mirror.
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
parano666 said:
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
Click to expand...
Click to collapse
When you flash a factory image, flash it in both slots.
Flash all once
Boot into the bootloader again
Swap slots in bootloader
Flash all again
(tks!)
(update: needed twrp-pixel-installer-marlin-3.1.0-0RC2 installed and booted to install magisk v12 pixel (was getting error 1 with twrp-pixel-installer-marlin-3.0.2-0-RC1.zip))
(update2: safety net passed!)
pcriz said:
I dunno about you but I have magisk hide on and hid the playstore and a few other processes but if its checking your phone at a point before you can enable magisk hide and storing the results wouldn't it not make much difference? I ask this because magisk hide or not, netflix doesnt show up. Even on a clean boot its not listed as an app I can restore. The simple fix for me is to restore a back up or simply download from apk mirror.
Click to expand...
Click to collapse
Ok.
parano666 said:
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
Click to expand...
Click to collapse
Intro
The purpose of this thread is twofold:
First, it is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM...
If you follow the instructions above you should not have to worry about slot a/b. The firmware will put it in the correct slot.
If you are installing Custom ROM this thread is not for you. You, should follow the installation instructions of the Custom ROM you want to install.
parano666 said:
(tks!)
(update: needed twrp-pixel-installer-marlin-3.1.0-0RC2 installed and booted to install magisk v12 pixel (was getting error 1 with twrp-pixel-installer-marlin-3.0.2-0-RC1.zip))
(update2: safety net passed!)
Click to expand...
Click to collapse
You're welcome!
[Guide] Pixel XL Android 8.1.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.
This guide is primarily intended for rooted users, since stock users can just take the OTA.
Key points
User data and applications are kept intact
You do not have to remove your PIN, password, or fingerprint
You do not have to remove TWRP, Magisk, your custom kernel, dtbo, or anything
This is intended for monthly security updates; developer previews and beta releases may or may not work with this method. You're welcome to try, but all may not work as expected
Installing Update:
Make sure you have the latest Google SDK Platform Tools. Extract the archive to a location of your choosing (creates platform-tools folder)
Get the latest walleye Factory Image (not OTA) from Google's Developer Page and save to a location of your choosing
Extract the archive, and open the extracted folder. You should see a list of files:
bootloader-walleye-[version string].img
flash-all.bat
flash-all.sh
flash-base.sh
image-walleye-[version string].zip
radio-walleye-[version string].img
Open the flash-all script (flash-all.bat for Windows, flash-all.sh for Linux/OSX) in your favorite text editor.
Find the line that reads "fastboot -w update image-walleye-[version].zip and remove "-w" (the wipe user data switch). Save and close the flash-all script.
Move (cut and paste, etc) all of these files to the platform-tools folder.
Enable USB Debugging from the Developer Options menu on your device (press "Build Number" 7 times if not already visible)
With your device plugged into the computer, open a command prompt in the platform-tools folder
Windows: Open the folder, hold down Shift and right click inside the folder, "Open Command window here"
Linux: If you're on Linux you already know how to do this
OSX: Open a folder in a terminal
Reboot to bootloader:
Code:
adb reboot bootloader
Execute update script in terminal:
Windows:
Code:
flash-all.bat
Linux/OSX:
Code:
./flash-all.sh
The device will reboot a few times while updating
Restoring root and/or a custom recovery
Download latest:
TWRP image
Magisk zip
TWRP zip
(Optional) Custom kernel zip
Place all files in the platform-tools folder
Reboot to bootloader
Boot TWRP image.
Code:
fastboot boot [twrp image filename].img
Push zip files to /tmp
Code:
adb push [magisk filename].zip /tmp
Optional: TWRP persistent installation + custom kernel:
Code:
adb push [twrp filename].zip /tmp
adb push [custom kernel filename].zip /tmp
Install Magisk:
Code:
adb shell twrp install /tmp/[magisk filename].zip
Optional: TWRP persistent installation + custom kernel:
Code:
adb shell twrp install /tmp/[twrp filename].zip
adb shell twrp install /tmp/[custom kernel filename].zip
adb shell twrp install /tmp/[magisk filename].zip
Reboot to system
[ Reserved ]
[ Reserved Post ]
Thanks for the guide
Sent from my Pixel 2 using Tapatalk
Thanks for that, but do not forget to mention to enable usb debugging mode, to account for people who are new to this community.
I'm having trouble Installing Magisk on Step 6. Every time I enter the code it says it can't locate the Magisk file for some reason.
Pianobeats said:
I'm having trouble Installing Magisk on Step 6. Every time I enter the code it says it can't locate the Magisk file for some reason.
Click to expand...
Click to collapse
Oops, my instructions were to push to /tmp but the flashing portion left that directory out. I updated the original post.
atifaslam7 said:
Thanks for that, but do not forget to mention to enable usb debugging mode, to account for people who are new to this community.
Click to expand...
Click to collapse
My thought was that if someone is following this guide, they're already rooted, so would already know to have USB Debugging enabled. I'll add it though for completeness sake.
ehi guys! i have one last doubt before updating to the latest factory image: i have a verizon pixel 2, bootloader unlocked, magisk installed on OPM1.171019.013, will i be able to keep my bootloader unlocked after i flash the latest factory image? i definitely don't want to lock it as i read the unlock command is not working anymore..
thanks a lot!
Thanks for the guide. Worked flawlessly!
daede86 said:
ehi guys! i have one last doubt before updating to the latest factory image: i have a verizon pixel 2, bootloader unlocked, magisk installed on OPM1.171019.013, will i be able to keep my bootloader unlocked after i flash the latest factory image? i definitely don't want to lock it as i read the unlock command is not working anymore..
thanks a lot!
Click to expand...
Click to collapse
Relocking your bootloader is not necessary to flash this. Bootloader will remain unlocked after flashing.
Telperion said:
Note: As of the February security update, TWRP 3.2.1-0 cannot decrypt the /data/ partition. When prompted for your PIN, cancel. You can keep /system/ read-only.
Click to expand...
Click to collapse
TWRP 3.2.1-1 and 3.2.1-2 are able to decrypt /data and /sdcard. MTP still doesn't work, but you can place files on the sdcard via USB in system.
socal87 said:
TWRP 3.2.1-1 and 3.2.1-2 are able to decrypt /data and /sdcard. MTP still doesn't work, but you can place files on the sdcard via USB in system.
Click to expand...
Click to collapse
This is hit and miss, for example 3.2.1-2 won't decrypt /data/ for me on P DP1. Others though have no problem decrypting data.
I kept the instructions the same, but took out the decryption note. Even if your TWRP can decrypt /data/ it's not strictly necessary for this process, so there's consistency in the guide in spite of inconsistent TWRP behavior.
Telperion said:
This is hit and miss, for example 3.2.1-2 won't decrypt /data/ for me on P DP1. Others though have no problem decrypting data.
I kept the instructions the same, but took out the decryption note. Even if your TWRP can decrypt /data/ it's not strictly necessary for this process, so there's consistency in the guide in spite of inconsistent TWRP behavior.
Click to expand...
Click to collapse
This honestly doesn't surprise me in the least; I would expect that Android P might use a different security scheme, so the decryption mechanism that works with Oreo may not be forward compatible.
For persistent twrp don’t you need to fastboot flash the recovery partition with the twrp image?
floepie said:
For persistent twrp don’t you need to fastboot flash the recovery partition with the twrp image?
Click to expand...
Click to collapse
There is no recovery partition, the recovery is now part of the boot image. You have to boot the TWRP image, then flash the TWRP zip which will patch the boot image in both slots.
Right I meant the boot partition. But this contradicts the main guide here where it indicates the necessity to flash both the twrp image to the boot partition (not just boot to the image on your PC), AND flash the twrp zip to make it persistent.
You don’t need to worry about the twrp zip at all if all you want to do is fastboot boot the twrp image.
floepie said:
Right I meant the boot partition. But this contradicts the main guide here where it indicates the necessity to flash both the twrp image to the boot partition (not just boot to the image on your PC), AND flash the twrp zip to make it persistent.
Click to expand...
Click to collapse
Not sure which guide you're referring to, but nathanchance's guide as far as I saw lined up with mine.
Sorry delete
Has there been a workaround created for those of us who can't unlock bootloader because OEM can't be unlocked? Wiping the phone and skipping wizard did not work for me. I'm just trying to root so I can delete apps I don't want.
Can someone tell me about the installing OTA.zip without unrooting or uninstalling the magisk. Is it possible to update through OTA on rooted stock ROM? Or what if we update using the OTA which comes automatically from Google?
Sent from my Pixel 2 using Tapatalk
nickporwal said:
Can someone tell me about the installing OTA.zip without unrooting or uninstalling the magisk. Is it possible to update through OTA on rooted stock ROM? Or what if we update using the OTA which comes automatically from Google?
Click to expand...
Click to collapse
That's not possible, which is why this process exists.
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode
REQUIREMENTS -
1 - Setup adb and fastboot on your PC.
2- Stock boot image (boot.img) of your device (extract file from factory image android P)
3 - Last Magisk Manager (v 5.8.3)
4 - Active Internet connection
5 - Active mind and patience.
6 - Devices must is unlock bl.
This Boot-Image is for boot android P PPR1.180610.009:
https://drive.google.com/open?id=166pE9aMk-jqns3JM74enFhsaDY6-c3yJ
Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
==================================================
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta
7- Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
CREDITS
@topjohnwu (Magisk)
Sadly goes into a bootloop for me - no idea why though
This worked for me. I had magisk installed and took the pie update. No more root. D/l the factory image and extracted the boot image to the files folder...pissmeoff they changed the name of the icon... and magisk patched the image and saved it in its folder. Found the file, moved it to the laptop then flashed it.
reawo said:
Sadly goes into a bootloop for me - no idea why though
Click to expand...
Click to collapse
I think you made a mistake.
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
reawo said:
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
Click to expand...
Click to collapse
I think you use my file(boot.img) for patch_boot.img from magisk manager.
I think you must check your build number devices.
You must use file boot.img from your factory image for root.
9.0.0 (PPR1.180610.009, Aug 2018) >This is version for my devices
9.0.0 (PPR1.180610.011, Aug 2018, Telstra) >?
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
reawo said:
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
Click to expand...
Click to collapse
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
newyesor said:
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
Click to expand...
Click to collapse
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
I receive also a bootloop and I didnt make any mistake. I also used this method pre Pie, I read that alot of users have problems with rooting Pie atm, even with TWRP
reawo said:
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
Click to expand...
Click to collapse
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
newyesor said:
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
Click to expand...
Click to collapse
I downloaded all the latest adb and fastboot. Never touched kernel or did custom recovery, always used the magisk method since i am on a pixel device. i also got the issue that my pc doesnt recognize my pixel from time to time, you think i should do a complete wipe?
I don't sure.
You are use platfrom-tool from sdk lastversion?(for flash via fastboot mode)
@reawo
I think you should flash factory image new again and factory reset your devices.
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta ,and close this app.****
7- Open app again and Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching (This process is not failed)***
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
Will work on the verizon variant (bootloader locked)?
sabi95190 said:
Will work on the verizon variant (bootloader locked)?
Click to expand...
Click to collapse
Nope. If it were that easy for bootloader locked Verizon phones, it would have been done months ago.
What happens if you lock the bootloader after all of this?
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
You'll wipe the phone, lose root, and be stock.
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
TonikJDK said:
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
Click to expand...
Click to collapse
"Borderline"???? More like certifiably insane! ?
Hi, I'm a newbie and I usually root my Pixel 4 on AT&T because I use a lot of tethering for my work which my carrier blocks.
Two weeks ago I had Android 10, unlocked and rooted. Life was good.
Phone automatically updated to Android 11 and I lost root.
Today I had some free time so I:
-Downloaded Android 11 factory img to my laptop
-Patched boot.img with Magisk 20.4 that was already installed on my phone (I think this was my first mistake)
-Flashed the new patched img to my mobile
-Restarted
-Got stuck into the G with bar at the bottom eternally
-Couldn't get into ADB devices so I restarted to fastboot
-flashed the stock boot.img by: "fastboot flash boot boot.img"
-fastboot restart
-Now stuck on Fastboot Mode loop. Device Status "unlocked", boot slot a, enter reason: "reboot bootloader"
Now I don't know exactly what to do here and I do need my mobile to work. Sorry for the newbie question but what should I do? Ideally I would like to not lose my data given bootloader is already unlocked.
P.S. I ran stock image flash-all without the -w and I'm back to square 1. How should I root then?
Thank you so much!
luisbs said:
...-Patched boot.img with Magisk 20.4 that was already installed on my phone (I think this was my first mistake)...
...How should I root then?
Thank you so much!
Click to expand...
Click to collapse
These Instructions might help:
First, you cannot root with the Stable Magisk Manager.
You can only root by using either the Beta or Canary Magisk Manager:
A. If Magisk Stable is installed:
1. Change the Update Channel to Beta or Canary
2. Install Beta or Canary Manager
3. patch the stock boot.img - tap Install next to Magisk
4. Select: Patch boot.image
5. Locate Stock boot.img you extracted from the current factory image.
6. Select it, tap the Checkmark (✓)
7. Tap Lets Go
8. Save log
9. Reboot
10. The magisk_patched.img size should be between ~64 - ~67 MB.
11. Uninstall all the modules
12. Uninstall Magisk - Restore images
13. Reboot
14. Goto D
B. If Beta or Canary Magisk Manager is installed:
1. Uninstall all modules
2 .Make sure the Update Channel is set to the version of the Manager installed.
3. patch the stock boot.img - tap Install next to Magisk
4. Select: Patch boot.image
5. Locate Stock boot.img you extracted from the current factory image.
6. Select it, tap the Checkmark (✓)
7. Tap Lets Go
8. Save log
9. Reboot
10. The magisk_patched.img size should be between ~64 - ~67 MB.
11. Goto D
C. If Magisk is not installed:
1. Download Beta or Canary Magisk Manager
2. Install Beta or Canary Magisk Manager
3. Make sure the Update Channel is set to the version of the Manager you installed.
4. patch the stock boot.img - tap Install next to Magisk
5. Select: Patch boot.image
6. Locate Stock boot.img you extracted from the current factory image.
7. Select it, tap the Checkmark (✓)
8. Tap Lets Go
9. Save log
10. Reboot
11. The magisk_patched.img size should be between 64-67 MB.
D. Flash magisk_patched.img:
1. Boot the phone into fastboot mode
(Power the phone Off ==> Press and hold the Power and Volumne down buttons until you see Start.)
2. Connect the phone to your Computer via a USB cable (A to B)
3. Open the Platform-tools folder and Right Click it.
(Make sure the magisk_patched.img is in this folder.)
Select Open Command prompt here. If you do not see Open a Command Prompt here. Click the folder icon on the left side of the address bar. The information in the address bar should be highlighted. Type cmd in the address bar and press Enter a Command Window should open. Type fastboot flash boot magisk_patched.img --slot all and press enter.
4. When it finishes, type fastboot reboot.
5. Disconnect your phone from the computer
6. Done! Your phone should be rooted
did it work on october update too?
my fastboot says: no valid slot to boot
Danieldergrosse said:
did it work on october update too?
my fastboot says: no valid slot to boot
Click to expand...
Click to collapse
Yes!
Than i am on Stock Boot lol
Danieldergrosse said:
Than i am on Stock Boot lol
Click to expand...
Click to collapse
Ok!
You dont Unserstand. My bootloader is unlocked. Why to flash the Stock boot.img Like you Said for d
Lol
Thats the Same as i Download factory extraxt and flash Boot. IMG
ITS the Same. So why you should get root with original Boot.img
Thats why i say loool
---------- Post added at 08:59 AM ---------- Previous post was at 08:57 AM ----------
Or do you rename the magisk patched in boot.img ?
I find a solution....i am Sure
Than i will Tell...
Danieldergrosse said:
You dont Unserstand...
---------- Post added at 08:59 AM ---------- Previous post was at 08:57 AM ----------
Or do you rename the magisk patched in boot.img ?...
Click to expand...
Click to collapse
Ok, I misunderstood your comments, I apologise.
No, I didn't rename the magisk_patched.img boot.img.
You dont understand what i mean....
If i flashed magisk patched it says No Slot to Boot. You Know.
Than i flash boot.img i am Back to Stock and it works....
My patched magisk doesnt Work....can you send me your patched magisk.img ?
Perhaps it works
Danieldergrosse said:
...My patched magisk doesnt Work...
Click to expand...
Click to collapse
If the edited instructions for rooting with Magisk (Posted above) didn't help. Like you said.
Danieldergrosse said:
...I find a solution....i am Sure...
Click to expand...
Click to collapse
lol
??
Homeboy76 said:
If the edited instructions for rooting with Magisk (Posted above) didn't help. Like you said.
lol
Click to expand...
Click to collapse
Don't know what's going wrong @Your side, but it works fine as ever
2WildFirE said:
Don't know what's going wrong @Your side, but it works fine as ever
Click to expand...
Click to collapse
I edited the post above to include Beta, thanks for the screenshot.
Danieldergrosse said:
??
Click to expand...
Click to collapse
Possible fix
Uploaded my patched boot.img for you: http://ul.to/utzm0kvc