[CLOSED][Guide] Root Pixel 4 XL Android 10 (Q)

Status
Not open for further replies.
Search This thread
By:
Advanced…
Z

Zander_Sig

Senior Member
Apr 19, 2012
128
6
OMG! I must be stupid!!! I am trying to flash the factory image.... I am opening a command terminal in my platform-tools folder which is on my desktop (I have put the factory image folder in the platform-tools folder (unzipped)) but when I do the flash-all script I am getting this error..

"C:\Users\Alex_WIN7_PRO\Desktop\platform-tools>flash-all
'flash-all' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Alex_WIN7_PRO\Desktop\platform-tools>"

What am I missing? It restarts the bootloader when I do this command "adb reboot bootloader"
 
Badger50

Badger50

Senior Moderator / Moderator Committee
Staff member
Feb 27, 2011
18,099
7
35,494
64
"Always on the Hunt"
Samsung Galaxy Note 10.1
Samsung Galaxy A10
Zander_Sig said:
OMG! I must be stupid!!! I am trying to flash the factory image.... I am opening a command terminal in my platform-tools folder which is on my desktop (I have put the factory image folder in the platform-tools folder (unzipped)) but when I do the flash-all script I am getting this error..

"C:\Users\Alex_WIN7_PRO\Desktop\platform-tools>flash-all
'flash-all' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Alex_WIN7_PRO\Desktop\platform-tools>"

What am I missing? It restarts the bootloader when I do this command "adb reboot bootloader"
Click to expand...
Click to collapse

Read this and you'll know what your missing :cool:

https://xdaforums.com/pixel-4-xl/how-to/january-images-t4030919/post81409523
 
  • Like
Reactions: Zander_Sig
Z

Zander_Sig

Senior Member
Apr 19, 2012
128
6
OK I was dragging the whole folder into my platform-tools folder. Duh!!! Stupid me!

I copied these files into my platform-tools folder...

bootloader-coral-c2f2-0.2-5940465.img
flash-all.bat
image-coral-qq1b.200105.004.zip
radio-coral-g8150-00041-191016-b-5945070.img
flash-base.sh
flash-all.sh

I then type "flash-all" in the command prompt.

and I then get this...

"C:\Users\Alex\Desktop\platform-tools>flash-all
Sending 'bootloader_a' (8761 KB) OKAY [ 0.546s]
Writing 'bootloader_a' (bootloader) Flashing Pack ve
rsion c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition logfs
OKAY [ 0.343s]
Finished. Total time: 1.170s
Rebooting into bootloader OKAY [ 0.031s]
Finished. Total time: 0.062s
Sending 'radio_a' (82676 KB) OKAY [ 4.368s]
Writing 'radio_a' (bootloader) Flashing Pack ve
rsion SSD:g8150-00041-191016-B-5945070
(bootloader) Flashing partition modem_a
OKAY [ 0.640s]
Finished. Total time: 5.288s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: g8150-00041-191016-B-5945070
Serial Number........: 9A221FFBA002TA
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Checking 'version-bootloader' OKAY [ 0.062s]
Checking 'version-baseband' OKAY [ 0.047s]
Setting current slot to 'a' OKAY [ 0.078s]
extracting boot.img (64 MB) to disk... took 1.031s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.857s]
Writing 'boot_a' OKAY [ 0.452s]
extracting dtbo.img (8 MB) to disk... took 0.296s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.343s]
Writing 'dtbo_a' OKAY [ 0.125s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.140s]
Writing 'vbmeta_a' OKAY [ 0.062s]
extracting vbmeta_system.img (0 MB) to disk... took 0.016s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.140s]
Writing 'vbmeta_system_a' OKAY [ 0.062s]
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.062s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.016s]
Updating super partition OKAY [ 0.016s]
Resizing 'product_a' OKAY [ 0.016s]
Resizing 'system_a' OKAY [ 0.016s]
Resizing 'system_b' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.000s]
Resizing 'vendor_b' OKAY [ 0.005s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (2126 MB) to disk... took 432.704s
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.016s]
Sending sparse 'product_a' 1/5 (524284 KB) OKAY [ 28.311s]
Writing 'product_a' OKAY [ 3.479s]
Sending sparse 'product_a' 2/5 (524284 KB) OKAY [ 24.977s]
Writing 'product_a' OKAY [ 3.650s]
Sending sparse 'product_a' 3/5 (524284 KB) OKAY [ 25.756s]
Writing 'product_a' OKAY [ 3.635s]
Sending sparse 'product_a' 4/5 (521664 KB) OKAY [ 21.980s]
Writing 'product_a' OKAY [ 3.635s]
Sending sparse 'product_a' 5/5 (83500 KB) OKAY [ 2.543s]
Writing 'product_a' OKAY [ 0.811s]
extracting system.img (762 MB) to disk... took 117.691s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.016s]
Sending sparse 'system_a' 1/2 (524284 KB) OKAY [ 15.522s]
Writing 'system_a' OKAY [ 3.572s]
Sending sparse 'system_a' 2/2 (256960 KB) OKAY [ 7.644s]
Writing 'system_a' OKAY [ 1.966s]
archive does not contain 'system_ext.img'
extracting system_other.img (67 MB) to disk... took 13.775s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.047s]
Sending 'system_b' (69276 KB) OKAY [ 1.934s]
Writing 'system_b' OKAY [ 0.733s]
extracting vendor.img (660 MB) to disk... took 387.496s
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.000s]
Sending sparse 'vendor_a' 1/2 (524284 KB) OKAY [ 15.413s]
Writing 'vendor_a' OKAY [ 3.370s]
Sending sparse 'vendor_a' 2/2 (152544 KB) OKAY [ 4.571s]
Writing 'vendor_a' OKAY [ 1.279s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.357s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.078s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting OKAY [ 0.000s]
Finished. Total time: 1331.959s
Press any key to exit..."

My phone is now displaying "fastbootd" at the top and giving me these options...

Reboot system now
Enter recovery
Reboot to bootloader
Power off....

I waited about 30 minutes or so and now my phone is back on wanting me to set it up from scratch! YEAH!


Looks like I got it... now I just need to ROOT it.


Question: Should all those errors be in the command prompt screen text?
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,728
Google Pixel 8 Pro
Zander_Sig said:
OMG! I must be stupid!!! I am trying to flash the factory image.... I am opening a command terminal in my platform-tools folder which is on my desktop (I have put the factory image folder in the platform-tools folder (unzipped)) but when I do the flash-all script I am getting this error..

"C:\Users\Alex_WIN7_PRO\Desktop\platform-tools>flash-all
'flash-all' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Alex_WIN7_PRO\Desktop\platform-tools>"

What am I missing? It restarts the bootloader when I do this command "adb reboot bootloader"
Click to expand...
Click to collapse
Read #2, then Redo #4 'wipe data' you skipped something.
 
Last edited:
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,728
Google Pixel 8 Pro
Zander_Sig said:
OK I was dragging the whole folder into my platform-tools folder. Duh!!! Stupid me!

I copied these files into my platform-tools folder...

bootloader-coral-c2f2-0.2-5940465.img
flash-all.bat
image-coral-qq1b.200105.004.zip
radio-coral-g8150-00041-191016-b-5945070.img
flash-base.sh
flash-all.sh

I then type "flash-all" in the command prompt.

and I then get this...

"C:\Users\Alex\Desktop\platform-tools>flash-all
Sending 'bootloader_a' (8761 KB) OKAY [ 0.546s]
Writing 'bootloader_a' (bootloader) Flashing Pack ve
rsion c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition logfs
OKAY [ 0.343s]
Finished. Total time: 1.170s
Rebooting into bootloader OKAY [ 0.031s]
Finished. Total time: 0.062s
Sending 'radio_a' (82676 KB) OKAY [ 4.368s]
Writing 'radio_a' (bootloader) Flashing Pack ve
rsion SSD:g8150-00041-191016-B-5945070
(bootloader) Flashing partition modem_a
OKAY [ 0.640s]
Finished. Total time: 5.288s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: g8150-00041-191016-B-5945070
Serial Number........: 9A221FFBA002TA
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Checking 'version-bootloader' OKAY [ 0.062s]
Checking 'version-baseband' OKAY [ 0.047s]
Setting current slot to 'a' OKAY [ 0.078s]
extracting boot.img (64 MB) to disk... took 1.031s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.857s]
Writing 'boot_a' OKAY [ 0.452s]
extracting dtbo.img (8 MB) to disk... took 0.296s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.343s]
Writing 'dtbo_a' OKAY [ 0.125s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.140s]
Writing 'vbmeta_a' OKAY [ 0.062s]
extracting vbmeta_system.img (0 MB) to disk... took 0.016s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.140s]
Writing 'vbmeta_system_a' OKAY [ 0.062s]
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.062s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.016s]
Updating super partition OKAY [ 0.016s]
Resizing 'product_a' OKAY [ 0.016s]
Resizing 'system_a' OKAY [ 0.016s]
Resizing 'system_b' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.000s]
Resizing 'vendor_b' OKAY [ 0.005s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (2126 MB) to disk... took 432.704s
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.016s]
Sending sparse 'product_a' 1/5 (524284 KB) OKAY [ 28.311s]
Writing 'product_a' OKAY [ 3.479s]
Sending sparse 'product_a' 2/5 (524284 KB) OKAY [ 24.977s]
Writing 'product_a' OKAY [ 3.650s]
Sending sparse 'product_a' 3/5 (524284 KB) OKAY [ 25.756s]
Writing 'product_a' OKAY [ 3.635s]
Sending sparse 'product_a' 4/5 (521664 KB) OKAY [ 21.980s]
Writing 'product_a' OKAY [ 3.635s]
Sending sparse 'product_a' 5/5 (83500 KB) OKAY [ 2.543s]
Writing 'product_a' OKAY [ 0.811s]
extracting system.img (762 MB) to disk... took 117.691s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.016s]
Sending sparse 'system_a' 1/2 (524284 KB) OKAY [ 15.522s]
Writing 'system_a' OKAY [ 3.572s]
Sending sparse 'system_a' 2/2 (256960 KB) OKAY [ 7.644s]
Writing 'system_a' OKAY [ 1.966s]
archive does not contain 'system_ext.img'
extracting system_other.img (67 MB) to disk... took 13.775s
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.047s]
Sending 'system_b' (69276 KB) OKAY [ 1.934s]
Writing 'system_b' OKAY [ 0.733s]
extracting vendor.img (660 MB) to disk... took 387.496s
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.000s]
Sending sparse 'vendor_a' 1/2 (524284 KB) OKAY [ 15.413s]
Writing 'vendor_a' OKAY [ 3.370s]
Sending sparse 'vendor_a' 2/2 (152544 KB) OKAY [ 4.571s]
Writing 'vendor_a' OKAY [ 1.279s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.357s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.078s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting OKAY [ 0.000s]
Finished. Total time: 1331.959s
Press any key to exit..."

My phone is now displaying "fastbootd" at the top and giving me these options...

Reboot system now
Enter recovery
Reboot to bootloader
Power off....

I waited about 30 minutes or so and now my phone is back on wanting me to set it up from scratch! YEAH!


Looks like I got it... now I just need to ROOT it.


Question: Should all those errors be in the command prompt screen text?
Click to expand...
Click to collapse
Yes, you skipped something: #4 2 b
If you are referring to the 'does not contain' as errors, yes. Do #6 then do #9 to root.
 
Last edited:
  • Like
Reactions: Zander_Sig
Z

Zander_Sig

Senior Member
Apr 19, 2012
128
6
Hummm?

Homeboy76 said:
Yes, you skipped something: #4 2 b
If you are referring to the 'does not contain' as errors, yes. Do #6 then do #9 to root.
Click to expand...
Click to collapse

No I did not edit the script. I checked it and made sure it had the -w in it.

It did erase everything on my phone. I was just concerned about the errors that showed up when I was flashing the stock android system "coral-qq1b.200105.004"

Should I go back and do it again?

I have my phone back up and running. Am I just need to patch the boot file and gain root.
 
H

Homeboy76

Recognized Contributor
Aug 24, 2012
4,200
2,728
Google Pixel 8 Pro
Zander_Sig said:
No I did not edit the script. I checked it and made sure it had the -w in it.

It did erase everything on my phone. I was just concerned about the errors that showed up when I was flashing the stock android system "coral-qq1b.200105.004"

Should I go back and do it again?

I have my phone back up and running. Am I just need to patch the boot file and gain root.
Click to expand...
Click to collapse
No. Just do #6, then #9 to root.
 
Z

Zander_Sig

Senior Member
Apr 19, 2012
128
6
Awesome!

Homeboy76 said:
No. Just do #6, then #9 to root.
Click to expand...
Click to collapse

Cool man! Thank You! And thanks to everyone else!

I am almost there! ;)

---------- Post added at 09:54 PM ---------- Previous post was at 09:18 PM ----------

Got it! I am now "Rooted" and a "Superuser"! Finally!!

Thanks again guys!!!!

5 Stars for everyone who worked on this and who helped me out!
 
Last edited:
Z

Zander_Sig

Senior Member
Apr 19, 2012
128
6
Off topic... I know this is off topic but I am having serious issues with my tap vibration and the tap sounds. They just quit working.... Not sure what to do. Sometimes my keyboard will vibrate on taps and sometimes it won't. I hope this is not a hardware problem. I just bought this Pixel 4 XL a little over a month ago!

I wonder if I should wipe my phone and start fresh to see if it is a hardware problem. Has anyone else having issues with the tap vibrations and sounds?
 
S

State.of.mind

Senior Member
Sep 2, 2011
468
86
Google Pixel 7 Pro
Can the moderator make this sticky

---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
Zander_Sig said:
Off topic... I know this is off topic but I am having serious issues with my tap vibration and the tap sounds. They just quit working.... Not sure what to do. Sometimes my keyboard will vibrate on taps and sometimes it won't. I hope this is not a hardware problem. I just bought this Pixel 4 XL a little over a month ago!

I wonder if I should wipe my phone and start fresh to see if it is a hardware problem. Has anyone else having issues with the tap vibrations and sounds?
Click to expand...
Click to collapse
No but I bet it's your screen protector.

---------- Post added at 07:17 PM ---------- Previous post was at 07:01 PM ----------

Anyone having issues with the March update and face unlock?
 
D

drup88

Senior Member
Jun 21, 2013
267
31
Melbourne
Samsung Galaxy A Series 2017 A3, A5, A7
Google Pixel 4 XL
The guide to me personally is not clear enough when it comes to OTA updates. Can someone help clarify?

If im on Feb and March update has just come out. It would be much easier to just flash OTA update then reflashing a whole new full image right? (unless you want a clean install or other specific reason and dont care about wiping data).

So i just followed the instructions here using adb commands.
https://developers.google.com/android/ota

However i've lost root now and im reading that i have to reflash the boot.img (which is not in the OTA.zip downloads and only the full image downloads) So have i come full circle to the realisation that i have to download the full image regardless?
 
Last edited:
p70shooter

p70shooter

Senior Member
Jan 9, 2013
2,720
1,848
drup88 said:
The guide to me personally is not clear enough when it comes to OTA updates. Can someone help clarify?

If im on Feb and March update has just come out. It would be much easier to just flash OTA update then reflashing a whole new full image right? (unless you want a clean install or other specific reason and dont care about wiping data).

So i just followed the instructions here using adb commands.
https://developers.google.com/android/ota

However i've lost root now and im reading that i have to reflash the boot.img (which is not in the OTA.zip downloads and only the full image downloads) So have i come full circle to the realisation that i have to download the full image regardless?
Click to expand...
Click to collapse
Or go to the guide section and someone has uploaded the boot.img and the patched boot.img
 
mattwheat

mattwheat

Senior Member
Oct 25, 2012
1,193
594
BIRMINGHAM
i tried to flash the patched boot.img and i get back

fastboot unknown option -- slot

i literally copied and pasted your cmd prompt command from the original post what am i doing wrong

when i type fastboot flash boot--all with the boot.img file location i get this

target reported max download size of 268435456 bytes
sending 'boot--all' (32144 KB)...
OKAY [ 0.198s]
writing 'boot--all'...
FAILED (remote: Not allowed to flash (boot--all))
finished. total time: 0.352s

no matter how i type the command i get the same thing
FAILED (remote: Not allowed to flash (boot ?)
? ---- meaning what ever way i type it
 
Last edited:
Badger50

Badger50

Senior Moderator / Moderator Committee
Staff member
Feb 27, 2011
18,099
7
35,494
64
"Always on the Hunt"
Samsung Galaxy Note 10.1
Samsung Galaxy A10
mattwheat said:
i tried to flash the patched boot.img and i get back

fastboot unknown option -- slot

i literally copied and pasted your cmd prompt command from the original post what am i doing wrong

when i type fastboot flash boot--all with the boot.img file location i get this

target reported max download size of 268435456 bytes
sending 'boot--all' (32144 KB)...
OKAY [ 0.198s]
writing 'boot--all'...
FAILED (remote: Not allowed to flash (boot--all))
finished. total time: 0.352s

no matter how i type the command i get the same thing
FAILED (remote: Not allowed to flash (boot ?)
? ---- meaning what ever way i type it
Click to expand...
Click to collapse

Not trying step on the OP's guide since it is an excellent one for sure. Does the command...
fastboot flash boot magisk_patched.img --slot=all
work for you at all??
 
  • Like
Reactions: Homeboy76
Status
Not open for further replies.

Similar threads

P
  • Sticky
[Guide] Pixel 4 XL (Unlocked from Google Store) - Root and Bootloader Unlocking
Replies
621
Views
89K
H
Homeboy76
H
[Guide] Root Pixel 4 XL with Magisk Android 13
Replies
420
Views
79K
H
Homeboy76
madscribblerz
Working root instructions for Verizon Pixel 4 XL
Replies
83
Views
36K
Mr Hassan
Mr Hassan
wrongway213
[GUIDE] Google Pay working SIMPLY with unlock/root on Pixel 4/XL [GUIDE]
Replies
40
Views
21K
D
denzel09
KillerBytes
AT&T Pixel 4 XL Has a Locked Bootloader
Replies
94
Views
20K
kashif91
kashif91

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 22
    H
    Homeboy76
    Mod edit: Thread closed on request of OP! Oswald Boelcke, Senior Moderator

    11 Root Pixel 4 XL Android 10 (Q) Unlock/Lock Bootloader + Systemless ROOT
    Android Security Buletin-August 2020
    Pixel Update Bulletin—August 2020    ​

    Introduction
    1. This Guide is for Pixel 4 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 4 XL'.
    2. This Guide also works for Pixel 4 owners: If, they download the Pixel 4 files.

    NEW
    1. Gpay not working? Try this.
    2. Tulsadiver's ADB Magisk Module Mod Installer has a LINUX instaler.
    3. The best instuctions on how to Pass SafetyNet, i've ever read.

    Update(s)
    1. Factory/OTA Images - 08/05
    2. Magisk Stable - Magisk-22.0 02/23
    3. Magisk Beta - Magisk-22.0 02/23
    4. Magisk Canary - Magisk-22001
    5. TWRP - twrp-3.5.0_10-1-coral.img/zip 01/02
    6. SafetyNet - SafetyNetFix v1.1.1 01/16
    7. SDK Platform-tools - r31.0.0 03/01
    8. Custom Kernels
      • No Updated Kernels
    9. Custom ROMs
      • Waiting

    Disclaimers
    1. I assume no responsibility for the malfunctioning/bricking of your phone.
    2. 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
    1. A Pixel 4 XL phone with an unlocked bootloader.
    2. The latest Android 10 (Q) Factory or OTA Image: "coral" for Pixel 4 XL
      1. Factory Image
      2. OTA Image
    3. Computer - With the latest SDK Platform-Tools: r31.0.0 installed.
      • Important: Update Platform Tools, regularly, for optimal performance.

    Other Guides

    Credits/Thanks/Recognitions
    1. @topjohnwu - Magisk Canary
    2. Those I may have, inadvertently, forgotten.

    Index
    (NOTE: Numbers 1-13 are not steps, they are individual sets of instructions).
    1. Open a Command Prompt/Boot Fastboot Mode/Boot Recovery

      • Open Command Prompt on Computer
        1. Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
        2. 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.
        3. Notes:
      • Boot fastboot mode:
        • 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.
    2. Test fastboot

      • Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
      • Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
        Enable USB Debugging.
      • Open a Command Prompt on your computer in the Platform-tools folder.
      • Boot fastboot mode on your phone (#1)
      • Connect the phone to the Computer.
      • At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
    3. Unlock Bootloader/Return Phone to Stock/Lock Bootloader

      • Unlock Bootloader

        1. This will erase all user data from the device!
        2. Backup your data
        3. Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
        4. Boot fastboot mode
        5. Connect the phone to the Computer with USB cord.
        6. Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
        7. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        8. Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
        9. When your phone reboots disconnect your usb cable.
        10. Note: After unlocking your bootloader, you'll see a warning: You will see this warning until, you relock the bootloader.
      • Return Phone to Stock

        1. Important: Do not relock your bootloader until you have returned the device to Stock..
        2. Backup your data/Internal storage
        3. Settings > System > Advanced > Reset Options > Erase all data (factory reset)
        4. Log in
        5. Set up phone
      • Lock Bootloader (Google Pixel 4 XL)

        1. Return the phone to Stock before Locking the bootloader!
        2. This will erase all user data from the device!
        3. Boot fastboot mode
        4. Open a Command Prompt and type this at the Prompt: fastboot flashing lock
        5. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        6. Allow the process to complete, then type this at the Command Prompt: fastboot reboot
        7. Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
        8. Tap Back > Developer options and toggle OEM Unlock off.


    4. Install/Update Factory Image keep or wipe data

      • Important Note(s):
        1. When doing a major upgrade i.e., Android 10 (Q) to Android 11 (R): I recommend doing a clean install. What is a clean install?:
          • Doing a Factory reset prior to installing, major, update.
          • Using flash-all.bat file without removing the -w.
        2. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 4 XL - coral.
        3. If your phone is rooted and you have Modules installed and you want to 'Keep Data', remove them before you install the Factory Image:
          Why? Some Modules need to be updated before use with a new Factory/OTA image because (sometime) Google makes changes to Factory/OTA images that break the Modules          .
        4. How to remove Magisk: Open Magisk App ==> Tap Uninstall == Tap Restore Images.
        5. If you get an error:when flashing the Factory image, try one of these options:
          • Change the USB port to a non charging USB port.
          • Change the USB cord to one that doesn't have the blue color head or use a USB C to C cable.
          • Change Computers.
      • Backup your data
      • Download the latest Factory Image: Pixel 4 XL - coral to your Computer.
      • Extract the factory Image to a folder.
      • Keep Data

        1. Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e. Notepad. Remove -w from this command: fastboot -w update image-coral-aa9a.999999.999.zip
          Note: If you do not remove the -w your data and internal storage will be wiped.
        2. After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
          • bootloader-coral-....img
          • flash-all.bat
          • image-coral-....zip
          • radio-coral-....img
        3. Open a Command Prompt on your computer in the Platform-tools folder ==> Boot fastboot mode on your phone ==> Connect the phone to the Computer.==> At the prompt type: flash-all and press enter.
        4. Note: During the flashing you may notice the phone is in fastbootd mode that is a normal for Android 10 (Q).
        5. System will reboot when flashing is complete.
        6. Do #7 or #8 to root/reroot.
      • Wipe Data

        1. Open the folder you extracted the Factory Image to and View the flash-all.bat file with a file editor i.e. Notepad. Verify the file has the -w in this command: fastboot -w update image-crosshatch-aa9a.999999.999.zip
          Note: This will wipe your data and internal storage.
        2. Copy/Move these files to the Platform-tools folder:
          • bootloader-coral-....img
          • flash-all.bat
          • image-coral-....zip
          • radio-coral-....img
        3. Open a Command Prompt on your computer in the Platform-tools folder ==> Boot fastboot mode on your phone ==> Connect the phone to the Computer.==> At the prompt type: flash-all and press enter.
        4. Note: During the flashing you may notice the phone is in fastbootd mode that is a normal for Android 10 (Q).
        5. System will reboot when flashing is complete.
        6. Do #7 or #8 to root/reroot.
    5. ADB Sideload

      • Stock Recovery
      • Custom Recovery - TWRP

        • Important notes:
          1. Charge your device.
          2. Enable USB Debugging on your phone.
          3. Install the latest version of SDK Platform-tools on your computer.
        • Open a command prompt in the computer's ADB folder: the folder with ADB.exe in it.
        • Put the (flashable zip) file you want to sideload in the computer's ADB folder.Copy the Zip file you want to install on your device to the ADB folder.
        • Connect your device to your computer using a USB cable.
        • Boot T.W.R.P.
          1. T.W.R.P installed: Boot fastboot mode ==> use volume buttons up/down until you see Recovery mode ==> press power botton.
          2. T.W.R.P. not installed: Boot T.W.R.P: Put twrp.img file in the computer's ADB folder ==> open a command prompt in ADB folder ==> at the prompt type fastboot flash boot "Name of twrp file.img" without the quotation marks.
        • When T.W.R.P boots tap Advanced ==> ADB Sideload.
        • ✓ the wipe Dalvik cache box
        • Swipe to start
        • On your Computer: Enter the following command at the command prompt. adb sideload <filename.Zip> i.e., adb sideload myfile.zip
        • You will see the progress of the sideloaded file.
        • When the file finishes sidloading, reboot your device.
        • Done!
    6. Extract/Flash boot.img

      • Extract boot.img

        1. Download the latest Factory image to your phone.
        2. Use a File Explorer to extract the boot.img from the Factory Image.
        3. Extract the Factory Image file (coral-pda1a.999999.999-factory-99a9a99a.zip) to a folder.
        4. Open the folder and, extract the Image file (image-crosshatch-aa9a.999999.999.zip).
      • Flash boot.img

        1. Note: Flashing this file removes root.
        2. Open the folder you extracted the 'image file' to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
        3. Boot fastboot mode
        4. Connect the phone to the Computer
        5. Open a Command Prompt and type the following command at the prompt:
          Code: 
          fastboot flash boot --slot all boot.img
        6. Reboot
    7. Install T.W.R.P./Root/Reroot with Magisk and Pass SafetyNet.

      • Important Note(s):
        1. Set Pin before installing TWRP: Settings > Security & location >Screen lock > Pin
        2. Backup your data
      • Download files - The listed files are used with #7, and #8.
        1. T.W.R.P
        2. Magisk- Download to your phone
        3. Custom Kernels - Download to your phone
          • No Updated Custom Kernels
        4. Kernel Manager - Download to your phone
      • Boot fastboot mode
      • Connect the phone to the Computer with USB cord.
      • Copy twrp-3.5.0_10-1-coral.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: fastboot boot twrp.img and press enter.
      • When TWRP boots, disconnect the phone from computer.
      • If requested, swipe to allow modifications.
      • Tap Install select twrp-installer-3.5.0_10-1-coral.zip, Swipe Slider to install
      • Reboot Recovery
      • Root/Reroot

        1. Note(s):
          • If you are rerooting, tap Install, select Magisk's uninstaller.zip, Swipe the slider to install.
          • Some Custom Kernels can be updated by flashing via Kernel Manager without losing root. Check the Custom Kernel thread (OP - Installation/Instructions) to find out which Custom Kernels.
        2. With Custom Kernel (Optional)
          • No Updated Custom Kernels
        3. Without Custom Kernel
          • Tap Install, select Magisk-Beta/Canary/Stable zip.
          • Swipe Slider to Install
          • Reboot System
          • Install Modules (Optional)
    8. Boot T.W.R.P./Root/Reroot with Magisk and Pass SafetyNet.

      • Backup your data
      • Download files - See #7 - Skip the twrp-installer
      • Boot fastboot mode
      • Connect the phone to the Computer with USB cord.
      • Copy twrp-3.5.0_10-1-coral.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: fastboot boot twrp.img and press enter.
      • When TWRP boots, disconnect the phone from computer.
      • If requested, swipe to allow modifications.
      • Root/Reroot

        • Note: If you are rerooting, tap Install, select the latest Magisk's uninstaller.zip, Swipe the slider to install.
        • With Custom Kernel (Optional)
          • No Updated Kernels
        • Without Custom Kernel
          • Tap Install, select Magisk-Beta/Canary/Stable zip.
          • Swipe Slider to Install
          • Reboot System
          • Install Modules (Optional)
    9. Root/Reroot with Magisk and Pass SafetyNet.

      • Important Note(s):
        1. When doing a major upgrade i.e., Android 10 (Q) to Android 11 (R): I recommend doing a clean install. What is a clean install?:
          • Doing a Factory reset prior to installing, major, update.
          • Using flash-all.bat file without removing the -w.
        2. To root use Magisk App Beta, Canary or Stable App to patch the Stock boot.img.
      • Download files:
        1. Magisk App - Download to your phone
        2. Custom kernels - Download to your phone - install with Kernel Manager
          • No updated Kernels
        3. Kernel Manager - Download to your phone
      • Patching the boot.img

        1. Do #6 - Extract boot.img
        2. Install Magisk (Beta or Canary) App
        3. Open Magisk App
        4. Depending on the version of Magisk App installed: Set the Update Channel to Beta, Canary or Stable.
        5. Tap Install (next to Magisk)
        6. Tap, Select and Patch a File
        7. Select the boot.img file you extracted from the latest factory image.
        8. Tap the ✓ (Check Mark)
        9. Tap Let's Go
        10. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img) and stored in the download folder.
        11. The phone will reboot.
        12. Copy the magisk_patched.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
        13. Boot fastboot mode (See #1B)
        14. Connect the phone to the Computer with USB cord.
        15. Open a Command Prompt (See #1A) in the folder you copied the magisk_patched.img to.
        16. Type fastboot flash boot magisk_patched.img at the Prompt and press enter.
        17. Type fastboot reboot at the Prompt and press enter.
        18. Important Notes:If your phone boot loops try one of the following options:
          • Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
          • Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
        19. Pass SafetyNet: #12 Apps/Mods/Scripts/Tethering/Themes
      • OTA Installation - Keep Root -- No Computer Needed
    10. Set Magisk App Update Chanel/Update Magisk

      • Set Magisk App Update Chanel

        • Open Magisk App > Tap menu icon > Settings > Update Channel > Select Stable, Beta, Canary or Custom.
      • Update Magisk

        1. When Magisk App notifies you of an update:
        2. Tap install.
        3. Select, Direct Install (Recommended)
        4. When it finishes installing
        5. Tap, Save Log
        6. Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
        7. Tap, Reboot
        8. Done!
    11. Custom ROMs for Pixel 4 XL

      • Need help with a Custom ROM?
        1. Follow the Installation Instructions of the Developer of the Custom ROM you are trying to install.
        2. If you have a problem Installing the ROM, Search the thread of the Custom ROM you want to install for solutions to problem before posting a request for help on their thread.
      • Custom ROMS
        1. Alpha/Beta

          • Waiting...
        2. Official

          • Waiting...
        3. Unofficial

          • Waiting...
    12. Apps/Mods/Scripts/Tethering/Themes
    13. T.W.R.P. 3.5.0_10-1 Backup/Restore
    View
    2
    mattwheat
    mattwheat
    Badger50 said:
    My apologies. I certainly was not trying to impugn your knowledge base or technique. I simply missed the SS for the CMD is all. I really don't know what the problem could be since both of the commands that have been discussed, work for myself and others. I suppose the work around would be to fastboot the boot.img, switch slots, then fastboot it again. However, I'm sure that won't mitigate your frustration as to why it doesn't work. I do like the "Vincent Price" retaliation technique though!
    Click to expand...
    Click to collapse

    done!!!!!!!!!!!! thank god thank you sir thank you very much that worked
    View
    1
    S
    State.of.mind
    Great write up...as always. Is there an way to update security patches and keep root?
    View
    1
    Badger50
    Badger50
    State.of.mind said:
    Great write up...as always. Is there an way to update security patches and keep root?
    Click to expand...
    Click to collapse

    Not really if you use factory images.

    https://xdaforums.com/pixel-4-xl/how-to/november-factory-images-t3997383/post80784067
    View
    1
    H
    Homeboy76
    jefrymm said:
    Hi, is everyone still passing safetynet?
    Click to expand...
    Click to collapse
    No! :(
    KACE321 said:
    I've just rooted my new Pixel4XL, the process went smoothly, but not passing Safety-net (i.e. ctsProfile is false)
    Click to expand...
    Click to collapse
    You're not alone!. :(
    Badger50 said:
    Seems Google has reapplied their attestation shenanigans again. Likely a harbinger of things yet to come! ??
    Click to expand...
    Click to collapse
    Yup!. :eek:

    A temporary fix for passing safetynet is this Magisk module. I use the module's name as the link name for the post: hardwareoff_1.1.zip
    View

New posts