FORUMS
Remove All Ads from XDA

* * * Pixel 2 XL Update To Latest 9x Factory Image & Upgrade From 8x To 9x * * *

6,434 posts
Thanks Meter: 12,925
 
By Az Biker, Forum Moderator on 7th August 2018, 03:01 PM
Post Reply Email Thread
Many users are updating from 9x to the latest factory image, and some are still upgrading from Oreo to Pie, and there are several instructional posts for both located in many different threads.

I figured I'd centralize the instructions in a Quick Reference thread, that includes all needed file links, and an easy to follow step by step.


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



UPDATE FROM 9x TO LATEST 9x FACTORY IMAGE:

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

Removal of magisk modules not necessary, (they are in full operation after I flashed the zip in twrp).

TWRP 3.2.3-1 is decrypting just fine with fingerprint + pin!


Updating to the latest security patch via fastboot is pretty much back to the easy ol' days like it was on 8.1. Badger50's method is as follows.

Download and extract the latest Taimen factory image (place in Platform Tools folder)

Fastboot the latest factory image with the -w removed (in the flash-all.bat file) to both slots, and let it boot up each time. Or use the Dueces script if you prefer. (I let the factory image choose which slot to install to, I have never, one time, manually selected either slot, and it hasn't bitten me yet )

Fastboot into twrp 3.2.3-1.IMG
Flash the twrp installer 3.2.3-1.ZIP,
Flash Cust Kernel (I use Flash -not supported after 3.19 Nov 2018 or Sultan Kernel or Elemental X (EX) kernel)
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit



UPGRADE FROM 8x to 9x:

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

These files on your sdcard:
* Latest TWRP.ZIP
* Latest Flash kernel
* Magisk uninstaller 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 9x factory image
* Latest TWRP.IMG


1. Make backup, move 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 see your device's serial number)
5. Fastboot 9.0 factory image (To KEEP internal storage intact, edit and remove -w in "flash-all.bat" file and SAVE, to wipe entire device, leave flash-all unedited)
6. Type: fastboot boot <twrpxxx.img name> to boot into Latest TWRP.IMG
7. Once in TWRP, install Latest TWRP.ZIP from sdcard
8. Reboot back into Recovery, and install the magisk uninstaller in twrp, (if you get stuck at the G screen, retry running the unitstaller in TWRP a few times in a row, this HAS worked for several users)
9. Reboot back into Recovery and install Flash kernel (latest-not supported after 3.19) or SULTANXDA kernel
10. Reboot back into Recovery
11. Reboot into System, allow OS to settle for a few minutes
12. Install Latest Magisk Manager APK (install the apk like any other app, NOT from within the Magisk Manager app)
13. Reboot into Recovery
14. Install Latest Magisk.zip [If latest Magisk does NOT work try using the 1674 version],
15. Reboot back into Recovery
16. Reboot into System
17. Profit


Troubleshooting Tips

If you get stuck at the G screen, or bootloop into TWRP, try these steps:

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

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

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

- Safety Net message in Magisk "The Response Is Invalid" is a known issue[/URL] ... Be patient
Click image for larger version

Name:	topjohnwu safety net.png
Views:	1482
Size:	85.2 KB
ID:	4572738


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


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, but it works


Again, HUGE thanks to @Badger50 for reporting BOTH of these working processes!
The Following 50 Users Say Thank You to Az Biker For This Useful Post: [ View ] Gift Az Biker Ad-Free
 
 
7th August 2018, 03:04 PM |#2  
Badger50's Avatar
Recognized Contributor
Flag Kansas City
Thanks Meter: 6,149
 
More
Quote:
Originally Posted by Az Biker

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

Please feel 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 2.0 & 3.0 cables available (trust me)

These files on your sdcard:
* TWRP 3.2.2-0.ZIP
*Flash kernel 3.0
* magisk uninstaller
*magisk zip 1674
* MM 5.8.3 APK

These files in your Platform Tools Folder:
* 9.0 factory image
*TWRP 3.2.2-0.IMG


1. Make backup, move to PC (because you never know)
2. Disable all security; patterns, pins, etc.
3. In Developer Options, make sure USB DEBUGGING is on
4. Verify fastboot is working type; fastboot devices (should see your device's serial number)
5. Fastboot 9.0 factory image(To KEEP internal storage intact, remove -w in "flash-all.bat" file and SAVE, to wipe entire device, leave flash-all unedited)
6. Type: fastboot boot <twrpxxx.img name> to boot into TWRP 3.2.2-0.IMG
7. Once in TWRP, install TWRP.ZIP on sdcard
8. Reboot back into Recovery, and install the magisk uninstaller in twrp,
9. Reboot back into Recovery and install Flash kernel 3.0
10. Reboot back into Recovery
11. Reboot into System, allow OS to settle for a few minutes
12. Install MM 5.8.3 APK
13. Reboot into Recovery
14. Install magisk zip 1674,
15. Reboot back into Recovery
16. Reboot into System
17. 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, but it works

Thanks to @Badger50 for figuring out the right steps in this process!

Well done my brother!!
The Following 7 Users Say Thank You to Badger50 For This Useful Post: [ View ] Gift Badger50 Ad-Free
7th August 2018, 04:40 PM |#3  
Senior Member
Flag Bangkok
Thanks Meter: 224
 
Donate to Me
More
Quote:
Originally Posted by Badger50

Well done my brother!!

I use unlock bootloader normal.
I was done follow your step but it's boot stuck google logo after flash magisk(16.74).
7th August 2018, 04:48 PM |#4  
Badger50's Avatar
Recognized Contributor
Flag Kansas City
Thanks Meter: 6,149
 
More
Quote:
Originally Posted by newyesor

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

Sometimes it takes 5 minutes or so on first boot. If it doesn't work, do a hard restart a few times. If that doesn't work, flash magisk again in twrp.

You use unlock bootloader normal??
7th August 2018, 04:52 PM |#5  
Senior Member
Flag Bangkok
Thanks Meter: 224
 
Donate to Me
More
Quote:
Originally Posted by Badger50

Sometimes it takes 5 minutes or so on first boot. If it doesn't work, do a hard restart a few times. If that doesn't work, flash magisk again in twrp.

You use unlock bootloader normal??

I use normal unlock bootloader.
I wait devices boot around 5 minutes and it 's reboot in to twrp recovery.
7th August 2018, 04:57 PM |#6  
Badger50's Avatar
Recognized Contributor
Flag Kansas City
Thanks Meter: 6,149
 
More
Quote:
Originally Posted by newyesor

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

So your bootloader _critical partition isn't unlocked?? Which can't be right either since you've been able to boot fastboot the update to P. Guess I just don't know what your trying to say.
7th August 2018, 05:02 PM |#7  
Senior Member
Flag Bangkok
Thanks Meter: 224
 
Donate to Me
More
Quote:
Originally Posted by Badger50

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

I use this command for flash unlock bootloader.
fastboot flashing unlock
7th August 2018, 05:15 PM |#8  
Badger50's Avatar
Recognized Contributor
Flag Kansas City
Thanks Meter: 6,149
 
More
Quote:
Originally Posted by newyesor

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

Have you ever ran fastboot flashing unlock_critical..?

Have you actually booted into the 9.0.OS yet?
7th August 2018, 05:19 PM |#9  
Senior Member
Flag Bangkok
Thanks Meter: 224
 
Donate to Me
More
Quote:
Originally Posted by Badger50

Have you ever ran fastboot flashing unlock_critical..?

Have you actually booted into the 9.0.OS yet?

I have never ran fastboot flashing unlock_critical.
Yes,My devices is base on android P and I was booted into the 9.0.OS.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_20180807-232133.png
Views:	736
Size:	136.7 KB
ID:	4566727  
7th August 2018, 05:22 PM |#10  
Az Biker's Avatar
OP Forum Moderator
Flag Sunshine and Endless Rides. USMC on my arm, .45 my hip
Thanks Meter: 12,925
 
More
Quote:
Originally Posted by newyesor

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

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

I'd start from scratch again, and make sure you follow the process exactly. Many users have used this with no issue, so maybe you missed something? The first time I flashed the factory image to my 6P (my backup) I totally skipped flashing the boot.img, and wondered why it wouldn't boot
7th August 2018, 05:30 PM |#11  
galaxys's Avatar
Senior Member
Flag Cosmos
Thanks Meter: 2,011
 
More
Kudos, just what I needed to update!
The Following User Says Thank You to galaxys For This Useful Post: [ View ] Gift galaxys Ad-Free
Post Reply Subscribe to Thread

Tags
android 9, android 9 pie, pixel 2xl pie, upgrade pixel 2 xl

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes