* * * [Pixel 2 XL] - UPDATE Monthly Factory Image / UPGRADE To New OS * * *

Beast38

Member
May 20, 2013
7
1
0
I use normal unlock bootloader.
I wait devices boot around 5 minutes and it 's reboot in to twrp recovery.
My situation is the same as newyesor.

It looks fine in most step(I even try boot into system after every step). But when I install "Magisk". No matter the version is 16.0 or 16.7. After reboot, it will takes about 3 minutes waiting, then reboot itself, then into TWRP recovery.

I didn;t remember the " fastboot flashing unlock_critical" is finish or not.(But the root is good when I using 8.1.0).

Anyway, I try to unlock and it shows as below. I'm now confuse what happened.

----------------------------------------------
C:\adb>fastboot flashing unlock
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.000s

C:\adb>fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.000s
-----------------------------------------------

The android system is 9.0.0 and works fine for now(Without root). Can't finish the Magisk root process.
 
Last edited:

almondbiscuit

New member
Jan 2, 2017
3
2
0
Koala city!
I updated okay without TWRP

Hello there, I'd like to just report here that I updated from Android 8.1 to 9 yesterday relatively trouble-free and quickly by
  • Updating Magisk Manager to 5.8.3 (still on Oreo at this point, and Magisk 16.0)
  • Flashing full image in bootloader without -w
  • Installing Magisk 1671 by using the patch boot image method (now on Pie)
and so far I think everything seems fine (including setting a PIN) after using it for one day and root is working.
However, others report that the patch boot image method didn't work for them so I'm not sure why it worked for me…
I didn't have TWRP on my phone, either before or after the update. So probably not helpful if you need TWRP!
 
Last edited:
  • Like
Reactions: hfam

vermaekansh

Senior Member
Aug 20, 2010
557
61
0
Followed each and every steps of this guide and tasting the Android P for the first time.

Thanks for providing such details, really helped a lot.

PS: Just after when I installed Magisk.uninstaller.zip when when rebooted to recovery , touch was not working, so i just rebooted to bootloader and then recovery. all went well.

I know this is not the forum to ask, If someone can give me essential magisk modules for our pixel 2 XL, that would be great help.
 
  • Like
Reactions: Az Biker

Badger50

Forum Moderator
Staff member
Feb 27, 2011
11,218
9,394
253
60
Kansas City
My situation is the same as newyesor.

It looks fine in most step(I even try boot into system after every step). But when I install "Magisk". No matter the version is 16.0 or 16.7. After reboot, it will takes about 3 minutes waiting, then reboot itself, then into TWRP recovery.

I didn;t remember the " fastboot flashing unlock_critical" is finish or not.(But the root is good when I using 8.1.0).

Anyway, I try to unlock and it shows as below. I'm now confuse what happened.

----------------------------------------------
C:\adb>fastboot flashing unlock
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.000s

C:\adb>fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.000s
-----------------------------------------------

The android system is 9.0.0 and works fine for now(Without root). Can't finish the Magisk root process.
Are you using minimal adb or the latest fastboot version 28.0? Are you using a laptop or desktop pc? Have you tried different USB A to USB C cables?

Hello there, I'd like to just report here that I updated from Android 8.1 to 9 yesterday relatively trouble-free and quickly by
Updating Magisk Manager to 5.8.3 (still on Oreo at this point, and Magisk 16.0)
Installing Magisk 1671 by using the patch boot image method (now on Pie)

and so far I think everything seems fine (including setting a PIN) after using it for one day and root is working.
However, others report that the patch boot image method didn't work for them so I'm not sure why it worked for me…
I didn't have TWRP on my phone, either before or after the update. So probably not helpful if you need TWRP!
Hahahahahaha....yeah, go figure! This device seems to be bipolar at times to say the least. Glad you got it working though :good:
 

newyesor

Senior Member
Jul 27, 2014
606
226
0
Bangkok
My situation is the same as newyesor.

It looks fine in most step(I even try boot into system after every step). But when I install "Magisk". No matter the version is 16.0 or 16.7. After reboot, it will takes about 3 minutes waiting, then reboot itself, then into TWRP recovery.

I didn;t remember the " fastboot flashing unlock_critical" is finish or not.(But the root is good when I using 8.1.0).

Anyway, I try to unlock and it shows as below. I'm now confuse what happened.

----------------------------------------------
C:\adb>fastboot flashing unlock
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.000s

C:\adb>fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.000s
-----------------------------------------------

The android system is 9.0.0 and works fine for now(Without root). Can't finish the Magisk root process.
Hi friend,I can root magisk without twrp recovery.:good:

REQUIREMENTS -

1 - PC with working ADB
2- Stock boot image (boot.img) of your device (extract file from factory image android P)
3 - Magisk Manager app (v 5.8.3)
4 - Active Internet connection
5 - Active mind and patience.
6.Devices must is unlock bl.

==================================================

Step 1: Patching the stock boot.img

- Install MagiskManager apk on your android device
- Copy the stock boot.img of your device to your phone's internal storage or SD card
- Launch Magisk Manager app
- If prompted to install Magisk, select NO THANKS
-Setting>Update Channel>Beta
- Select Install > Install > Patch Boot Image File >
Navigate to the location of the stock boot.img you copied earlier on, then Select it
-Magisk Manager should begin downloading the magisk zip file used for patching
-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
-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

-Setup adb and fastboot on your PC.
-Unlock the phone's Bootloader (if its not unlocked)
-Re-enable USB debugging on the phone
-Connect the phone to the PC via USB cord
-Boot into fastboot mode.
-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
 

Attachments

Last edited:
  • Like
Reactions: CPngN and icepixie

vwood2121

Senior Member
May 21, 2008
138
20
0
Ok I have a situation. I spent 4 hours going through this process multiple times but all is well until I install magisk.... The phone boots to the Google G with a line under it and sits there..... I'm stumped. I even let it sit 20 min in that state. If I boot back to twrp and uninstall magisk the phone boots fine. Any ideas appreciated
 

Badger50

Forum Moderator
Staff member
Feb 27, 2011
11,218
9,394
253
60
Kansas City
Ok I have a situation. I spent 4 hours going through this process multiple times but all is well until I install magisk.... The phone boots to the Google G with a line under it and sits there..... I'm stumped. I even let it sit 20 min in that state. If I boot back to twrp and uninstall magisk the phone boots fine. Any ideas appreciated
Believe me, I have felt your pain. I went through all that on Monday! I must have dirty fastbooted the factory image 5 times to both slots, did numerous hard restarts with the power button, and kept trying all the things that are listed in this guide in the OP. Then finally, it worked out of the blue. Can't give you a rhyme or reason though. I've read that some folks did a FDR and wiped their phones and got it working. So other than that, I don't know what to tell you my friend :confused:
 

bemagrp

Senior Member
Jan 30, 2014
153
42
58
As per recognized developer @flar2 instructions as follows:

- remove pin, or any security
-reboot to bootloader, remove "-w" from flash-all script and flash factory image
-let it reboot fully and finish updating
-reboot to bootloader and fastboot boot twrp
-install Magisk and reboot to system
-autoflash ElementalX from EX Kernel Manager

Did it myself, absolutely no problem, credit goes to @ flar2.
 

cjrivera04

Senior Member
Jun 18, 2010
609
197
73
Believe me, I have felt your pain. I went through all that on Monday! I must have dirty fastbooted the factory image 5 times to both slots, did numerous hard restarts with the power button, and kept trying all the things that are listed in this guide in the OP. Then finally, it worked out of the blue. Can't give you a rhyme or reason though. I've read that some folks did a FDR and wiped their phones and got it working. So other than that, I don't know what to tell you my friend :confused:
This phone just does that. I can second this. Sometimes I can go through the steps and it takes the first time, other times I have to keep at it until it takes. It's so odd. Glad to see I'm not the only one.
 

newyesor

Senior Member
Jul 27, 2014
606
226
0
Bangkok
As per recognized developer @flar2 instructions as follows:

- remove pin, or any security
-reboot to bootloader, remove "-w" from flash-all script and flash factory image
-let it reboot fully and finish updating
-reboot to bootloader and fastboot boot twrp
-install Magisk and reboot to system
-autoflash ElementalX from EX Kernel Manager

Did it myself, absolutely no problem, credit goes to @ flar2.
Hi,I have a question with you method for root magisk on android P.
reboot to bootloader and fastboot boot twrp (twrp.img)
-install twrp.zip via twrp ,go back to twrp
-install last magisk and reboot to system.
-autoflash ElementalX from EX Kernel Manager
 

bemagrp

Senior Member
Jan 30, 2014
153
42
58
Hi,I have a question with you method for root magisk on android P.
reboot to bootloader and fastboot boot twrp (twrp.img)
-install twrp.zip via twrp ,go back to twrp
-install last magisk and reboot to system.
-autoflash ElementalX from EX Kernel Manager
This is @flar2 method , and what is your question?
 

azpatterson3

Senior Member
Jun 8, 2011
534
261
93
St. Louis
I flashed pie over dp (removed -w). Flashed. uninstall Magisk. Reboot. Flashed latest twrp. Reboot. Flashed flash kernel. Reboot. Flashed Magisk. Reboot. Everything works great except twrp won't recognize my lock pattern. Can't get it to recognize no matter what combo install method I use. It's not a huge deal to disable the lock if I want to use twrp but I just am of the type who likes things working perfectly without workarounds. Am I going to have to start from a complete wipe (flash pie without removing "-w"?
 

sublimaze

Senior Member
Oct 13, 2010
2,630
984
193
For anyone having trouble getting adb/fastboot commands working, DO NOT use Minimal ADB & Fastboot. That package is outdated and doesn't play well with Android 9. Download the latest adb/fastboot package from Google, which is linked in OP
 
  • Like
Reactions: Az Biker