[X]Assistant

[clever_man]

Google Pixel 2 XL - Official firmware
Pixel 2 XL, Taimen
Description | Discussion пїЅ | Purchase пїЅ | Accessories пїЅ | Pixel Google Owners Club пїЅ | Camera talk пїЅ | Unofficial firmware пїЅ | Official firmware пїЅ

Drivers and Utilities

TOOL ALL IN ONE
Necessary software for firmware -Windows
Necessary software for firmware -Linux
Necessary software for firmware -Macosx
Platform tools - rev. 28.0.1 | USB Drivers - rev. eleven

Official firmware

Official firmware (full images)
OTA updates

Instructions

Mini-FAQ(in the process of filling) -read first! Messages whose answers are in the FAQ are deleted without warning!
Factory Unlock slider is unavailable
Getting root rightsusing Magisk 14.5+
Instructions for firmware via ADB sideload

Custom kernels and recovery

Recovery:

• Download the latest version:Download TWRP
  
• Discussion on XDA:TWRP for Pixel 2 XL

Kernels:

• Stock Pixel 2 XL Kernel + SafetyNet Patch
  
• Flash kernel
  
• Kiriskura-Aurora Kernel
  
• Pixel 2 XL ElementalX

miscellanea

Verify that the device has a binding to Verizon
Google Pixel 2 and Pixel 2 XL will appeal to lovers of custom firmware

Cap updates

22/05/2018

• Deletion of irrelevant instructions
  
• Add links to TWRP
  
• Add custom firmware
  
• Update link to direct topic on Magisk

19/12/2017

• Clarification on obtaining root-rights through Magisk 14.5

20/11/2017

• TWRP update
  
• Update Mini-FAQ - installation of custom recovery.
  
• Removing a link to irrelevant instructions for obtaining root rights

07/11/2017

• Added TWRP
  
• Added instructions for obtaining root-rights
  
• Android 8.1 DP Link

Post has been editeddestroyer71 - 13.03.19, 17:26

Reason for editing: Checking whether the device is bound to Verizon

[Kisakuku]

Official September images for firmware

• Official

  пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅ download

  
  
• OfficialOTA full images
  • AssemblyOPD1.170816.010- non-operator
    
  • AssemblyOPD1.170816.011- Telstra operator
    
  • AssemblyOPD1.170816.012- operators Rogers, Fido
    
  • AssemblyOPD3.170816.012- operator Verizon

Post has been editedKisakuku - 01.11.17, 13:57

[clever_man]

Initial work with adb

• Turn on "Developer Settings" (seven times tap on the "Build Number" in the "System ->About the device ").
  
• In the "Developer Settings" turn on "USB Debugging".
  
• Connect your device to PC.
  
• Open a command prompt and type:
  
  adb devices
  
  
• When you first connect (or if you previously allowed only the current session), the PC will request access (a message on the smartphone screen) ->Allow
  
• The command line should produce a similar response:
  
  List of devices attached
  XXXXXXXXXXXXXXXXX device
  
  
• If necessary, install the necessary drivers.

Download to bootloader mode

1. The first way (via adb):
   Connect the device to the PC and type in the command line:
   
   adb reboot bootloader
   
   
2. The second method (using hardware keys):
   On the phone off, press the "Volume Down" button and, without releasing, hold down the "Power" button.
   
   To check the operation (correct installation of drivers) in bootloader mode, run the following command:
   
   fastboot reboot bootloader
   
   There should be a similar answer:
   
   XXXXXXXXXXXXXXXXX fastboot
   
   Otherwise, check that the drivers are installed correctly.

Unlocking \ locking the bootloader

ATTENTION: When unlocking / locking the bootloader, the phone returns to the factory state (REMOVES ALL WITH THE DEVICE MEMORY)! Do not forget to backup all data !!!

Pixel 2 XL has a slightly different unlock system, to completely unlock the phone in bootloader mode and type the following commands:

fastboot flashing unlock
fastboot flashing unlock_critical


To lock the bootloader, execute the following commands (in turn) in bootloader mode:

fastboot flashing lock
fastboot flashing lock_critical

Installing custom recovery

If you have already installed custom recovery, then just download the latest version of the zip-archive and update it via the "Install" item

If the recovery has not yet been installed, follow the instructions below:

1. download both img and zip files;
   
2. copy zip to device memory;
   
3. reboot the device into the bootloader and connect to the PC (drivers must be installed and fastboot configured);
   
4. in the command line type the command:
   
   fastboot boot<img_file_name>
   
   Where<img_file_name>- the full name of the downloaded image of recovery in img (including the path to the file);
   
5. a temporary recovery image will be loaded on the device;
   
6. if a password \ pin is used at boot time and gives an incorrect result when dialing, reboot into the bootloader and repeat the procedure again;
   
7. select "Install" and install the downloaded zip;
   
8. if you had a root, you need to install the stock kernel before installing TWRP, then install TWRP and then get root-rights.

Post has been editedclever_man - 23.11.17, 10:33

[Vlad J.S.]

M

We move to subsection Google .

[Kisakuku]

TWRP 3.1.1 Alpha1
Custom recovery, official alpha version withvery limited functionality

• Download image to download via fastboot from the official site
  
• Note :
  
  • Decryption of the / data partition, backup and recovery, etc. do not work.
    
  • MTP does not work
    
  • No archive for firmware recovery
• Description on the official site
  
• Discussion on XDA

[Kisakuku]

Magisk v14.4 (1444)
Official beta version for Pixel 2 XL devices

• Magisk v14.4 Magisk-v14.4 (1444) .zip(5.97 MB)
  
  
• Magisk Manager v5.4.1 MagiskManager-v5.4.1.apk(2.24 MB)
  
  
• Magisk Uninstaller Magisk-uninstaller-20170928.zip(2.77 MB)
  
  
• Gives root access toAndroid 8.0 and Android 8.1 DP1
  
• Installation Instructions
  
  1. Unzip the stock boot partition from the factory image
     
  2. In Magisk Manager, select Install / Install / Patch Boot Image File / stock boot partition
     
  3. The patched boot partition will be saved to Internal Storage / MagiskManager / patched_boot.img
     
  4. Flash the patched boot partition
     fastboot flash boot patched_boot.img
• Note : You can not use the patched boot partition from another device. The second step of the instruction must be performed on the device being flashed.

Post has been editedKisakuku - 07.11.17, 11:02

[drug1111]

Has any of the members of the forum made a root according to the method indicated above?

[Kisakuku]

November update - Android 8.0

• Officialfactory images
  
• OfficialOTA full images
  • AssemblyOPD1.170816.025- non-operator
    
  • AssemblyOPD3.170816.023- operator Verizon
• Note: November update does not include fixes for WPA2 vulnerabilitiesKRACK
  

[drug1111]

I got lost ... How do I know if the bootloader is unlocked or not?

[Displax]

drug1111,
Go to bootloader mode, it will be written there.
The string is "DEVICE STATE", "locked" or "unlocked", respectively.
Well, in the case of an unlocked bootloader, a corresponding warning will be displayed at each boot.

[Kisakuku]

TWRP 3.1.1 Beta2
Custom recovery, official beta version

• Download Fastboot boot image: twrp-3.1.1-beta2-taimen.img (40 MB)
  (MD5: 14ffb3f3727ea80a68a6c57572084fc5)
  
• Download archive for firmware in TWRP: twrp-pixel2-installer-taimen-3.1.1-beta2.zip (10.38 MB)
  (MD5: ea56212a7447e897e7bbb0d07460a52b)
  
• Download from the official site
  
• Developer Comments :
  
  • There is a decryption of the / data section for September and November assemblies
    
  • Chances are high that the decryption of the / data partition will be broken by future system updates due to a blocking installation / boot partition by Google with versions lower than the system version.
• Description on the official site
  
• Discussion on XDA

[Fduch1984]

Friends, I rutted through Magisk, after opening the bootloader. OTA updates will be gone now? And will I be able to roll updates without data loss, or will this magical opportunity also disappear?

Thank.

[NedoshXD]

KisakukuI would like to add about the installation.

The image must be installed from the PC via the console (for Win10, it is better to use cmd because it does not find fault with commands, unlike powershell, where the command should be written in the form ". \"

zip-archive must be flashed from the temporary recovery, which is placed through the console. Only then put the Magisk. temporary recovery is placed in the boot section. It is best to prepare a patched boot in advance.

I think many will help because I thought for an hour and a half ...

Add to the cap.

[clever_man]

I removed the cap, if there is something to add - write in a personal.

[NedoshXD]

Magisk is now officially on our little animal!MagiskManager-v5.4.2.apk(2.28 MB)
Magisk-v14.5.zip(5.7 MB)

[Fduch1984]

NedoshXD,
And before it was, unofficially? Still worked like.

[Kisakuku]

Fduch1984beta 14.4 was only for second Pixels. Beta 14.5 is universal and includes support for second Pixels.

[Kisakuku]

clever_man @ 10.24.17, 01:51

for complete unlocking

By itself, fastboot flashing unlock_critical does not unlock the bootloader. You must first do fastboot flashing unlock.

[clever_man]

Kisakuku @ 11/23/17 09:45

By itself, fastboot flashing unlock_critical does not unlock the bootloader

Consulted specifically before writing withDisplax, he told me that this command is enough to completely unlock. You do not confirm?

Post has been editedclever_man - 23.11.17, 10:09

[Displax]

clever_man,
That's right, first flashing unlock and then, if you need to flash the bootloader, flashing unlock_critical.
Maybe it was assumed that unlock_critical can be done immediately, but it does not work like that.

Post has been editedDisplax - 23.11.17, 10:31

[clever_man]

Displax,I will correct.