Google Pixel 2 Xl Factory Image

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or apply an alternative browser.

Az Biker

Sr. Mod / Mod & RC-RT Committees / Shred'r of MTBs

• #1

WHO IS THIS GUIDE FOR:
Anyone updating mill images inside the same Os version (ten to 10)
Anyone upgrading from one OS to another (9x to Android 10)

Below is a QUICK REFERENCE guide for those who take done this before, and a DETAILED Footstep By Step guide for the first or 2nd timer who needs each and every step outlined. Links to all required files are too provided (make sure you are selecting the latest version)

UPDATE TO THE LATEST Manufacturing plant Prototype . . . UPGRADE TO THE NEXT OS. . .

PREP Work:
* Unlocked bootloader. (*performing critical_unlock only required with bootloader versions PRIOR to TMZ20a) read it here.
* Latest SDK Platform Tools found here.
* USB 2.0 & 3.0 cables available (trust me)
* Remove screen lock security before starting
* Remove all substratum overlays
*Download and extract the latest Taimen factory image (place the second extracted folder in Platform Tools binder)

CLEAN Wink (wipe everything) or DIRTY Flash (keep data)
Decide now whether you want a fresh Os that volition restore your device to factory setup OR if you lot want to flash the latest factory image but keep your data.
For a clean flash: exit the Flash-ALL file intact, change nothing.
To retain your information: EDIT the Flash-ALL file and REMOVE the -west virtually the stop of the script. Relieve the file and reopen it to ensure the -due west has been removed,

When UPGRADING from one OS to another I reco a Make clean FLASH (go out the -w intact)

Identify these files on your sdcard (either before dirty flash or from PC later make clean install):
* Latest TWRP.Nix
* Your preferred customer kernel zip, I employ ElementalX kernel
* Magisk uninstall instructions In the event you lot need to manually uninstall and reinstall MM
* Latest Magisk.zip
* Latest Magisk Manager APK

Notation: On Android x, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the alarm "FAILED TO Mountain '/system' (invalid argument) this is a known consequence with TWRP + 10 but affects nothing :good:

QUICK REFERENCE GUIDE for updating/upgrading Pixel 2 XL:

One time you verify 'fastboot devices' on command prompt
Type wink-all to install mill epitome (allow it to install, and kicking into arrangement)
Hold vol down and ability button to boot into bootloader
Fastboot into twrp 3.three.0-0.IMG
Wink the twrp installer 3.3.0-0.Cypher,
Wink custom kernel, I use flar2's ElementalX Kernel. SELECT THE Correct 9X OR ANDROID 10 KERNEL
Let the system boot upwardly to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit

DETAILED Pace BY STEP GUIDE for updating monthly manufacturing plant images, or upgrading to the next Os (ie: 9x to 10x)
I reco a CLEAN FLASH (leave the -west intact) when jumping from one Os to a new i (not necessary when doing monthly manufacturing plant updates inside the same Os version)

Requirements:
*Unlocked bootloader and Critical_unlock* completed. (*critical_unlock required with bootloader versions PRIOR to TMZ20a) read it here.
*Latest SDK PlatformTools constitute here
*USB 2.0 & iii.0 cables bachelor (trust me)

These files on your sdcard:
* Latest TWRP.ZIP
* Your preferred Custom Kernel, I use Elemental X Kernel
* Magisk uninstall instructions In the event you need to manually uninstall and reinstall MM
* Latest Magisk.zip
* Latest Magisk Manager APK

These files in your Platform Tools Folder:
* Latest factory image (Make Sure YOU DL THE Right DEVICE IMAGE :adept: )
* Latest TWRP.IMG

1. Make backup, movement to PC (because you never know)
2. Disable all security; patterns, pins, etc.
3. In Developer Options, make sure USB DEBUGGING is on
4. Connect device to PC, verify fastboot is working type; fastboot devices (should encounter your device'south serial number)
v. Fastboot latest manufacturing plant image (To Go along internal storage intact, edit and remove -w in "wink-all.bat" file and SAVE, to wipe entire device, leave wink-all unedited)
Type: Flash-ALL (hit enter) Allow the OS to reboot and settle for a minute *REMEMBER LEAVING THE -Due west INTACT WILL WIPE YOUR DEVICE*
vi. Reboot into BOOTLOADER, in CMD screen Type: fastboot kick <twrpxxx.img proper noun> to boot into Latest TWRP.IMG
7. Once in TWRP, install Latest TWRP.ZIP from sdcard
eight. Reboot back into Recovery
nine. Install compatible custom kernel, I use flar2's ElementalX Kernel.
x. Reboot back into Recovery
xi. Reboot into Organisation, let Bone to settle for a few minutes
12. Boot into Recovery
thirteen. Install Latest Magisk.zip
14. Reboot into System
15. Profit

Troubleshooting Tips & Other Information

Click hither for * * * BASIC FASTBOOT/ADB TROUBLE SHOOTING FOR THE 2XL * * *

If y'all get stuck at the M screen, or bootloop into TWRP, try these steps:

-Perform a hard reboot (long press the power push) or

-Get back to TWRP (whether by booting into it from fastboot, or rebooting into bootloader -long press ability & vol down- then boot into recovery) and reinstall the Magisk Uninstaller in TWRP a few times.

- If you lot are bootlooping into TWRP with Magisk installed, READ THIS!

- Condom Net message in Magisk "The Response Is Invalid" is a known issue[/URL] ... Be patient

Make sure you have all the correct and/or latest versions of SDK Tools, mill image, TWRP.img and TWRP.zippo, and Magisk

Note: every bit a matter of superstition, I reboot back into recovery each fourth dimension afterward installing TWRP, cust kernel, and magisk, prior to booting into organization. It is Not required, merely it works

Again, HUGE thank you to @Badger50 for his invaluable input

Concluding edited: Aug fourteen, 2020

• #two

A lot of users take had success upgrading from Oreo to Pie and there are several tutorial / guide posts located in different threads, and then I figured I'd centralize instructions in a Quick Reference Thread, that includes all needed file links and an easy to follow stride by step.

Please experience free to make any suggestions to simplify or make this more accurate.

Requirements:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB two.0 & three.0 cables available (trust me)

These files on your sdcard:
* TWRP iii.2.two-0.ZIP
*Flash kernel iii.0
* magisk uninstaller
*magisk cipher 1674
* MM 5.8.three APK

These files in your Platform Tools Folder:
* nine.0 factory epitome
*TWRP 3.2.two-0.IMG

1. Make backup, move to PC (because you never know)
two. Disable all security; patterns, pins, etc.
3. In Developer Options, brand certain USB DEBUGGING is on
4. Verify fastboot is working blazon; fastboot devices (should run into your device'due south serial number)
5. Fastboot ix.0 manufactory image(To Go along internal storage intact, remove -west in "flash-all.bat" file and Relieve, to wipe entire device, leave flash-all unedited)
six. Type: fastboot boot <twrpxxx.img name> to boot into TWRP iii.2.2-0.IMG
vii. In one case in TWRP, install TWRP.Goose egg on sdcard
8. Reboot back into Recovery, and install the magisk uninstaller in twrp,
nine. Reboot back into Recovery and install Flash kernel 3.0
ten. Reboot back into Recovery
eleven. Reboot into System, allow Os to settle for a few minutes
12. Install MM 5.8.iii APK
13. Reboot into Recovery
fourteen. Install magisk zip 1674,
fifteen. Reboot dorsum into Recovery
sixteen. Reboot into System
17. Turn a profit

Note: as a matter of superstition, I reboot back into recovery each time after installing TWRP, cust kernel, and magisk, prior to booting into system. It is NOT required, just it works

Cheers to @Badger50 for figuring out the correct steps in this process!

Well done my brother!! :good::good:

• #three

Well done my blood brother!! :good::good:

I use unlock bootloader normal.
I was done follow your step but it'due south kicking stuck google logo afterwards wink magisk(sixteen.74).

• #4

I use unlock bootloader normal.
I was done follow your step just it's boot stuck google logo after flash magisk(16.74).

Sometimes it takes 5 minutes or so on outset boot. If information technology doesn't work, do a difficult restart a few times. If that doesn't piece of work, flash magisk again in twrp.

You use unlock bootloader normal??

• #five

Sometimes information technology takes 5 minutes or so on first kicking. If it doesn't piece of work, exercise a hard restart a few times. If that doesn't work, flash magisk once more in twrp.

Yous employ unlock bootloader normal??

I use normal unlock bootloader.
I wait devices boot around v minutes and it 'south reboot in to twrp recovery.

• #half dozen

I employ normal unlock bootloader.
I expect devices kick around 5 minutes and information technology 's reboot in to twrp recovery.

And so your bootloader _critical partition isn't unlocked?? Which tin't be right either since you've been able to kicking fastboot the update to P. Judge I just don't know what your trying to say.

• #vii

So your bootloader _critical partition isn't unlocked?? Which can't exist right either since you've been able to boot fastboot the update to P. Estimate I just don't know what your trying to say.

I utilise this command for flash unlock bootloader.
fastboot flashing unlock

• #8

I utilise this command for flash unlock bootloader.
fastboot flashing unlock

Have you lot e'er ran fastboot flashing unlock_critical..?

Accept yous actually booted into the ix.0.Bone yet?

• #nine

Have you always ran fastboot flashing unlock_critical..?

Have you actually booted into the 9.0.OS notwithstanding?

I have never ran fastboot flashing unlock_critical.
Yes,My devices is base of operations on android P and I was booted into the 9.0.OS.

Attachments

• 
  Screenshot_20180807-232133.png

Az Biker

Sr. Mod / Mod & RC-RT Committees / Shred'r of MTBs

• #10

I employ this command for wink unlock bootloader.
fastboot flashing unlock

If you flashed the mill image with no issues, then yous must have completed critical_unlock every bit well, otherwise the new bootloader shouldn't have taken (every bit far as I sympathize).

I'd starting time from scratch once more, and brand sure you follow the procedure exactly. Many users have used this with no consequence, so mayhap yous missed something? The first time I flashed the mill prototype to my 6P (my fill-in) I totally skipped flashing the boot.img, and wondered why it wouldn't boot

• #11

Kudos, just what I needed to update!

• #12

I have never ran fastboot flashing unlock_critical.
Yes,My devices is base of operations on android P and I was booted into the 9.0.OS.

Have you lot flashed the magisk uninstaller every bit well? Why are you showing magisk 16.0?

• #13

Take you flashed the magisk uninstaller as well? Why are you showing magisk 16.0?

Yes,i was flashed the magisk uninstaller also.
I effort to root with magisk on my devices.
I try to flash patch kicking for root without twrp but it'southward not work.
I endeavour to wink magisk follow you but information technology'south not piece of work.

• #14

Is flashing the kernel mandatory?

• #fifteen

Aye,i was flashed the magisk uninstaller as well.
I try to root with magisk on my devices.
I endeavour to flash patch boot for root without twrp but information technology'south not work.
I try to flash magisk follow you but it's non work.

Something just seems fishy to me. I've never heard of anyone not unlocking _critical, and being able to fastboot the manufacturing plant epitome. However, information technology seems that you lot accept somehow. All I can advise is to fastboot the 9.0 again to both slots, and allow it kicking upwardly each time.

And then fastboot into twrp, flash the installer zip, and allow it kick up. Then become dorsum to twrp, flash magisk uninstaller naught, then wink custom kernel, and let it kick upwardly. Then go back to twrp, and flash magisk 1674 again.

If none of that works, I'd unlock _critical, which volition wipe your phone, so start over.

• #sixteen

Is flashing the kernel mandatory?

Not mandatory, just it keeps TWRP touch screen working among other things...

• #17

Just wanted to say thanks for this!

I didn't have fourth dimension to update from DP5 yesterday, but I gauge that was a good affair because at present there's this guide, and it worked perfectly. Upgraded from DP5/flash 2.44 and who knows what Magisk version to all the latest and greatest in no time at all.

Thanks!

• #18

Something just seems fishy to me. I've never heard of anyone not unlocking _critical, and being able to fastboot the factory prototype. Nevertheless, it seems that yous take somehow. All I tin can suggest is to fastboot the 9.0 again to both slots, and permit it kicking up each time.

Then fastboot into twrp, flash the installer zip, and let it kicking up. Then go back to twrp, flash magisk uninstaller cipher, so flash custom kernel, and permit information technology boot up. Then get dorsum to twrp, and flash magisk 1674 again.

If none of that works, I'd unlock _critical, which will wipe your telephone, then get-go over.

im having an outcome, i followed all instructions and got booted up an everything only when i flash twrp img it stays stuck on the twrp logo, flashed the one mentioned in o.p and the newest as well to remove any doubts, just no go. Any suggestions?

• #19

im having an issue, i followed all instructions and got booted up an everything but when i wink twrp img it stays stuck on the twrp logo, flashed the one mentioned in o.p and the newest as well to remove any doubts, but no get. Any suggestions?

Do you take screen lock disabled?

• #20

Do you have screen lock disabled?

Yeah sir

Similar threads

Google Pixel 2 Xl Factory Image,

Source: https://forum.xda-developers.com/t/pixel-2-xl-update-monthly-factory-image-upgrade-to-new-os.3826330/

Posted by: badgleydrebeguing.blogspot.com

Share this post