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

Search This thread

Homeboy76

Senior Member
  • Aug 24, 2012
    2,574
    1,248
    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
    there is a space between -- and slot
    fastboot unknown option -- slot
    should be :
    fastboot flash boot --slot all magisk_patched.img

    This command is just wrong: when i type
    fastboot flash boot--all
    with the boot.img file location...

    It might help if you open a Command prompt (#1) in the Platform-tools folder (#4).
     
    Last edited:
    • Like
    Reactions: Badger50

    mattwheat

    Senior Member
    Oct 25, 2012
    1,144
    581
    BIRMINGHAM
    I didn't try it like that. I was merely following exactly what the O. P. played out as the method to do so. Then when that didn't work I tried all different way of entering the command. I did not try it with the file path before the partition to be flashed to. That's generally not the order fastboot commands are entered.

    Is that what worked for you?

    ---------- Post added at 11:03 AM ---------- Previous post was at 10:58 AM ----------

    there is a space between -- and slot
    fastboot unknown option -- slot
    should be :
    fastboot flash boot --slot all magisk_patched.img

    This command is just wrong: when i type
    fastboot flash boot--all
    with the boot.img file location...

    It might help if you open a Command prompt (#1) in the Platform-tools folder (#4).


    I've tried it with powershell from the platform tools folder I've also got fastboot and adb setup system wide to be able to just type cmd in windows task tray search bar or by using the keyboard shortcut to open cmd promtp and initially I copied and pasted the O.P. 's command that he lays out. Figured he was driving this bus so I would just follow the drivers instructions. But it didn't work. That's why I went to trying every variation i could think of.
    And I know that fastboot recognizes my device due to the fastboot devices cmd returning the id. So with that said it shouldn't matter where I run cmd prompt from due to it being system wide and verified by fastboot returning the id. It never has been an issue before. As long as you're telling fastboot the file address to pull from.


    What I was merely trying to explain is no matter what spaces I insert or don't insert, whether it's typed 100% correct or not it returns the same error. Regardless.
    From both powershell opened in the platform tools folder or not. And with cmd prompt opened from the tools folder or not. With adb and fastboot setup system wide on my windows 10 PC.
     
    Last edited:

    Homeboy76

    Senior Member
  • Aug 24, 2012
    2,574
    1,248
    ...That's generally not the order fastboot commands are entered.

    Is that what worked for you?

    ---------- Post added at 11:03 AM ---------- Previous post was at 10:58 AM ----------

    ...What I was merely trying to explain is no matter what spaces I insert or don't insert, whether it's typed 100% correct or not it returns the same error. Regardless.
    From both powershell opened in the platform tools folder or not. And with cmd prompt opened from the tools folder or not. With adb and fastboot setup system wide on my windows 10 PC.
    fastboot flash boot --slot all magisk_patched.img
    Yes.

    I understand you are trying to explain what is not working. Here is the problem I'm having with your explanation of the problem:
    a. several people have used this guide succesfully to root their phone following the OP.
    b. You didn't try the Moderators suggestion.

    So, that makes me wonder what is different about your phone or PC that is causing you problems.

    This error is the key to the problem:
    FAILED (remote: Not allowed to flash (boot ?)
    Hmmm, is # 3. A. applicable?

    So, if your phone is still not rooted:
    - calm down
    - stop blaming everything but you as the reason you cannot root your phone. Blame will not root your phone.
    - reread the instructions from start to the Index, then read #1 and the other numbers that are applicable to what you are trying to do. Don't forget to read all the notes associated with each number (set of instructions).
    - Try again.
     
    Last edited:
    • Like
    Reactions: Badger50

    mattwheat

    Senior Member
    Oct 25, 2012
    1,144
    581
    BIRMINGHAM
    I haven't tried it with the "=" in the command line. I'll try that ....

    ---------- Post added at 07:21 AM ---------- Previous post was at 07:14 AM ----------

    fastboot flash boot --slot all magisk_patched.img
    Yes.

    I understand you are trying to explain what is not working. Here is the problem I'm having with your explanation of the problem:
    a. several people have used this guide succesfully to root their phone following the OP.
    b. You didn't try the Moderators suggestion.

    So, that makes me wonder what is different about your phone or PC that is causing you problems.

    This error is the key to the problem:
    FAILED (remote: Not allowed to flash (boot ?)
    Hmmm, is # 3. A. applicable?

    So, if your phone is still not rooted:
    - calm down
    - stop blaming everything but you as the reason you cannot root your phone. Blame will not root your phone.
    - reread the instructions from start to the Index, then read #1 and the other numbers that are applicable to what you are trying to do. Don't forget to read all the notes associated with each number (set of instructions).
    - Try again.

    Trust me I'm calm. And I'm not necessarily blaming everything but me. As youll see from some of me questions to you guys I've asked "what am I doing wrong". "what am I missing". That's all. And I'll be sure to go back through it very thoroughly. Trust me I'm not wanting to have these issues. I would love nothing more than to never had missed whatever it is I'm missing so I could already have root and have my phone mirrored to my GMC head unit in my truck. Not a big fan of Android autos style. The UI has gotten better. But thanks ill look over the stuff and try again. I do appreciate everyone's help.
    And by the way who is the moderator?
     
    • Like
    Reactions: Homeboy76

    Homeboy76

    Senior Member
  • Aug 24, 2012
    2,574
    1,248
    I haven't tried it with the "=" in the command line. I'll try that ....

    ---------- Post added at 07:21 AM ---------- Previous post was at 07:14 AM ----------



    Trust me I'm calm. And I'm not necessarily blaming everything but me. As youll see from some of me questions to you guys I've asked "what am I doing wrong". "what am I missing". That's all. And I'll be sure to go back through it very thoroughly. Trust me I'm not wanting to have these issues. I would love nothing more than to never had missed whatever it is I'm missing so I could already have root and have my phone mirrored to my GMC head unit in my truck. Not a big fan of Android autos style. The UI has gotten better. But thanks ill look over the stuff and try again. I do appreciate everyone's help.
    And by the way who is the moderator?
    Great! :)
    Is your SDK platform-tools r29.0.6?
    The Forum Moderater is Badger50. The suggestion to use the '=' in the command line was his suggestion.
     
    Last edited:

    mattwheat

    Senior Member
    Oct 25, 2012
    1,144
    581
    BIRMINGHAM
    heres everything i just tried
     

    Attachments

    • Capture5.PNG
      Capture5.PNG
      49 KB · Views: 84

    mattwheat

    Senior Member
    Oct 25, 2012
    1,144
    581
    BIRMINGHAM
    ok i downloaded platform tools r29.0.6 and tried again still the same thing

    theres something very weird going on with this bootloader is unlocked i set all the seting in magisk per the OP instructions followed everything to a "T"
     

    Attachments

    • Capture6.PNG
      Capture6.PNG
      10.7 KB · Views: 71
    Last edited:

    mattwheat

    Senior Member
    Oct 25, 2012
    1,144
    581
    BIRMINGHAM
    notice how when powershell returns the error it always puts a space between the "--" and "slot" notice how i type it without the space
     

    Attachments

    • Capture7.PNG
      Capture7.PNG
      16.9 KB · Views: 77

    mattwheat

    Senior Member
    Oct 25, 2012
    1,144
    581
    BIRMINGHAM
    If by #2 you're referring to the fastboot devices command? Check the screen shot. I did that. Like I've said before I've don't all these steps from the cmd prompt and from powershell. I'm aware of how to open cmd prompt and change the directory by using "cd" and like I've said before I set up adb and fastboot system wide so I can fastboot from any folder. Been setting it up for years like that as well as I did it the way the instructions say to do it by dropping the patches boot img into the platform tools folder and open powershell or cmd from inside that folder with the fastboot.exe in it. I'm willing to try anything y'all can think up to throw at it. But I'm not real optimistic at this point. I've tried different USB cables. I tried watching CNN while doing it instead of FOX. Hell I tried holding my mouth a different way. But nothing. I can see any time now I'm gonna get one of those artistic images in the cmd window that's made up of strategically placed letters, numbers, and symbols that create a design and it's gonna be a big middle finger pointing right at me with an 80's style computer digitized voice laughing like Vincent price. Lmfao
     

    Badger50

    Forum Moderator
    Staff member
    Feb 27, 2011
    12,091
    12,746
    61
    Kansas City
    If by #2 you're referring to the fastboot devices command? Check the screen shot. I did that. Like I've said before I've don't all these steps from the cmd prompt and from powershell.

    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! ?
     
    • Like
    Reactions: mattwheat

    mattwheat

    Senior Member
    Oct 25, 2012
    1,144
    581
    BIRMINGHAM
    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! ?
    No need to apologize I was just merely explaining I'm not a noob at this. But hey I mess up and miss stuff just like any body can. That's why I've been reaching out to yall. Trusting that I'm pretty sure yall are a little more seasoned than I. I did a lot back with the nexus 7 2013 and razor hd and hd Maxx. And some galaxies around the s3 thru s5 days. And nexus 6 and 6p. Then had a family and didn't do anything more really than just root for viper and LMT launcher. But now LMT launcher works without root. But Android 10 basically has it built in with the gestures so kinda been out of the loop. But ive noticed the way the system and boot partitions are designed now is vastly different than the old days of odexed and deodexed Roms. And CyanogenMod. It's now gone a little above my pay grade if you will. But I think that's a good idea to try flashing the stock boot.img and start over. But for what it's worth do you think the stock boot will flash of cmd is returning the errors as unknown command errors and not something describing wrong partition size or invalid signature or anything really that would relay that it has the right paths just wrong format or size or something? Seems like the errors are really more like user errors. Meaning I'm typing it wrong it would seem but clearly, or from what I can see, I'm typing it correct. Hell I even copied and pasted the commands from y'all's advice y'all left in the replies I got.
     

    mattwheat

    Senior Member
    Oct 25, 2012
    1,144
    581
    BIRMINGHAM
    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!

    done!!!!!!!!!!!! thank god thank you sir thank you very much that worked
     

    Attachments

    • Capture8.PNG
      Capture8.PNG
      14.6 KB · Views: 152

    Homeboy76

    Senior Member
  • Aug 24, 2012
    2,574
    1,248
    done!!!!!!!!!!!! thank god thank you sir thank you very much that worked
    @mattwheat
    Woke up and saw what I had missed. lol
    Glad you got it rooted:)

    I was wondering why all your images were blue and not black like the Command Window.

    Curious:
    What worked for you, so other XDA members can benefit from it:
    - Opening a Command prompt?
    - Switching slots?
    - What, exactly, did you do to resolve the problem?
     
    Last edited:

    Homeboy76

    Senior Member
  • Aug 24, 2012
    2,574
    1,248
    Last edited:
    • Like
    Reactions: Badger50

    Badger50

    Forum Moderator
    Staff member
    Feb 27, 2011
    12,091
    12,746
    61
    Kansas City
    You snooze you lose, I was inspecting the inside of my eyelids lol. Woke up and saw what I had missed.
    Ok, another way of doing #1. A. Option 2, Note: 1 :)

    Nothing wrong with a little eyelid inspection from time to time my friend?? if you think it's useful, add it to your excellent guide for more options.
    Under option 2
    Subset 2...code 1, 1A....and how the heck did I get here!?
     
    • Like
    Reactions: Homeboy76

    Homeboy76

    Senior Member
  • Aug 24, 2012
    2,574
    1,248
    Nothing wrong with a little eyelid inspection from time to time my friend?? if you think it's useful, add it to your excellent guide for more options.
    Under option 2
    Subset 2...code 1, 1A....and how the heck did I get here!?
    Don't know how you got there ROFLMAO.
    Thanks but no thanks #1. A. Option 2, Note: 1. is all that's needed.
     
    • Like
    Reactions: Badger50

    Top Liked Posts

    • There are no posts matching your filters.
    • 22
      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
      2
      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!

      done!!!!!!!!!!!! thank god thank you sir thank you very much that worked
      1
      Great write up...as always. Is there an way to update security patches and keep root?
      1
      Great write up...as always. Is there an way to update security patches and keep root?

      Not really if you use factory images.

      https://forum.xda-developers.com/pixel-4-xl/how-to/november-factory-images-t3997383/post80784067
      1
      Hi, is everyone still passing safetynet?
      No! :(
      I've just rooted my new Pixel4XL, the process went smoothly, but not passing Safety-net (i.e. ctsProfile is false)
      You're not alone!. :(
      Seems Google has reapplied their attestation shenanigans again. Likely a harbinger of things yet to come! ??
      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
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone