[Guide] Root Pixel XL Android 11 (R)

Search This thread

Rootmaster906

Senior Member
Dec 2, 2020
202
11

Attachments

  • 20210213_093609.jpg
    20210213_093609.jpg
    5.7 MB · Views: 9

Lughnasadh

Senior Member
Mar 23, 2015
2,014
1,317
Google Nexus 5
Huawei Nexus 6P
I know what phone I have. I posted in here cuz I saw a post about bootloop on sailfish and it directed me here. This thread is also more active. My apologies
Well, since you never mentioned that at the beginning I had no way of knowing. Try removing the first file in your platform tools folder. You don't need it as you have already extracted all of its contents into the folder already.

Also, that downloads folder you are using seems to be missing a lot of files. Are you putting those 6 files from the factory image in the actual platform tools folder? If not, do that. See screenshot below.
 

Attachments

  • Capture.PNG
    Capture.PNG
    54 KB · Views: 7
  • Like
Reactions: Homeboy76

Rootmaster906

Senior Member
Dec 2, 2020
202
11
Well, since you never mentioned that at the beginning I had no way of knowing. Try removing the first file in your platform tools folder. You don't need it as you have already extracted all of its contents into the folder already.

Also, that downloads folder you are using seems to be missing a lot of files. Are you putting those 6 files from the factory image in the actual platform tools folder? If not, do that. See screenshot below.
can I get a download link for that platform tools folder that you are using? I cannot find it on Google anywhere. Do I need all of those files or is that just an example?
 

Lughnasadh

Senior Member
Mar 23, 2015
2,014
1,317
Google Nexus 5
Huawei Nexus 6P
can I get a download link for that platform tools folder that you are using? I cannot find it on Google anywhere. Do I need all of those files or is that just an example?

Here's a screenshot of all the files that should be in there. Of course replace Coral with Sailfish files.
 

Attachments

  • Capture.PNG
    Capture.PNG
    72.1 KB · Views: 2

Rootmaster906

Senior Member
Dec 2, 2020
202
11
I was thinking that I could just go ahead and flash the Verizon images this is a Verizon phone. What if I try and reflash the stock image and then lock my bootloader, do you think that would help? Also, if I were to flash the Verizon stock firmware will it lock my bootloader?
 

Lughnasadh

Senior Member
Mar 23, 2015
2,014
1,317
Google Nexus 5
Huawei Nexus 6P
Am I fubar? It's still in a bootloop
I was thinking that I could just go ahead and flash the Verizon images this is a Verizon phone. What if I try and reflash the stock image and then lock my bootloader, do you think that would help? Also, if I were to flash the Verizon stock firmware will it lock my bootloader?
Are you flashing the latest factory image (Dec. 2019)? Is your bootloader definitely unlocked? If it is, don't relock your bootloader. You will not be able to do anything with a locked bootloader. Do not flash anything besides the Google factory images.

Are you using windows? Are you leaving the -w intact in the flash-all.bat file? If windows, are you using command line and not Powershell?

Show a screenshot of your platform tools folder. Show what happens after you flash the factory image (like were there any errors?). I have to go out for a while but maybe @Homeboy76 can help for a bit?
 
  • Like
Reactions: Rootmaster906

Rootmaster906

Senior Member
Dec 2, 2020
202
11
Are you flashing the latest factory image (Dec. 2019)? Is your bootloader definitely unlocked? If it is, don't relock your bootloader. You will not be able to do anything with a locked bootloader. Do not flash anything besides the Google factory images.

Are you using windows? Are you leaving the -w intact in the flash-all.bat file? If windows, are you using command line and not Powershell?

Show a screenshot of your platform tools folder. Show what happens after you flash the factory image (like were there any errors?). I have to go out for a while but maybe @Homeboy76 can help for a bit?
The answer is yes to all of your questions. I've used the command line and I've also used the actual flash all bat file. I flashed the last four Android 10 factory images to my phone and it keeps going into a boot loop . Yes I am flashing factory images and I followed all of your instructions. I bought this phone on eBay so I don't know the history of the phone. I thought I would be able to fix the phone figured it was in a boot loop and that obviously the phone does work. Lol
 

Rootmaster906

Senior Member
Dec 2, 2020
202
11
The answer is yes to all of your questions. I've used the command line and I've also used the actual flash all bat file. I flashed the last four Android 10 factory images to my phone and it keeps going into a boot loop . Yes I am flashing factory images and I followed all of your instructions. I bought this phone on eBay so I don't know the history of the phone. I thought I would be able to fix the phone figured it was in a boot loop and that obviously the phone does work. Lol
No errors in flashing... Just after the flash it will go to the home screen and then do its boot loop all over again
 

Rootmaster906

Senior Member
Dec 2, 2020
202
11
here is my output. then it reboots then goes into a bootloop. could maybe the slots be corrupted?

Sending 'bootloader_a' (32384 KB) OKAY [ 1.240s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 16.512s]
Finished. Total time: 17.975s
Rebooting into bootloader OKAY [ 0.030s]
Finished. Total time: 0.097s
Sending 'radio_a' (57140 KB) OKAY [ 2.276s]
Writing 'radio_a' OKAY [ 0.851s]
Finished. Total time: 6.120s
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.010s
--------------------------------------------
Bootloader Version...: 8996-012001-1808030001
Baseband Version.....: 8996-130181-1806061856
Serial Number........: FA6C80302248
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.005s]
Checking 'version-bootloader' OKAY [ 0.038s]
Checking 'version-baseband' OKAY [ 0.036s]
Setting current slot to 'a' OKAY [ 0.408s]
extracting boot.img (29 MB) to disk... took 0.404s
archive does not contain 'boot.sig'
Sending 'boot_a' (29753 KB) OKAY [ 1.084s]
Writing 'boot_a' OKAY [ 0.593s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
archive does not contain 'product.img'
extracting system.img (1930 MB) to disk... took 47.373s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 24.789s]
Writing 'system_a' OKAY [ 4.039s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 31.294s]
Writing 'system_a' OKAY [ 3.883s]
Sending sparse 'system_a' 3/4 (524284 KB) OKAY [ 30.551s]
Writing 'system_a' OKAY [ 3.892s]
Sending sparse 'system_a' 4/4 (404408 KB) OKAY [ 29.412s]
Writing 'system_a' OKAY [ 3.145s]
archive does not contain 'system_ext.img'
extracting system_other.img (313 MB) to disk... took 12.197s
archive does not contain 'system.sig'
Sending 'system_b' (321188 KB) OKAY [ 12.464s]
Writing 'system_b' OKAY [ 2.649s]
extracting vendor.img (259 MB) to disk... took 10.135s
archive does not contain 'vendor.sig'
Sending 'vendor_a' (266068 KB) OKAY [ 10.064s]
Writing 'vendor_a' OKAY [ 2.243s]
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 26.463s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 29939712 4k blocks and 7487488 inodes
Filesystem UUID: 8eb05aea-6e1b-11eb-b1c4-c57104781f19
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (604 KB) OKAY [ 0.099s]
Writing 'userdata' OKAY [ 0.147s]
Rebooting OKAY [ 0.042s]
Finished. Total time: 264.425s
Press any key to exit...
 

Rootmaster906

Senior Member
Dec 2, 2020
202
11
the first owner said they replaced the battery....could a battery cause a bootloop? when it was running, it kept a charge and worked a few days. i had adb sideload lineage 17 and it worked fine for a couple days then the loops happened again. ugh
once the flash for stock is complete, it will boot to the google splash screen and the bar under it stops, then it loops. on each loop a diff screen pops up. one with a lock icon, then it is just plain google...what is going on?!
 

Rootmaster906

Senior Member
Dec 2, 2020
202
11
@Echo off
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-sailfish-8996-130181-1806061856.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-sailfish-ppr2.180905.006.a1.zip

echo Press any key to exit...
pause >nul
exit
here is the properties for flash-all bat

yes. the -w is there. something is jamming the bootloader
 

Top Liked Posts

  • There are no posts matching your filters.
  • 17
    [Guide] Root Pixel XL Android 11 (R) Unlock/Lock Bootloader + Install Custom ROMS + Update Magisk/Systemless Root



    Introduction
    This Guide is for Google Pixel XL owners that want to Root their phone, enjoy the benefits of rooting it and installing a Custom ROM.


    Updates
    1. Factory/OTA Images12/02/2019
    2. Magisk Stable App - Magisk-23.0 05/12
    3. Magisk Beta App - Magisk-23.0 05/12
    4. Magisk Canary App - Magisk-23001
    5. TWRP - Waiting for T.R.W.P. for Android 10 (Q)
    6. SDK Platform-tools - r31.0.2 April
    7. Custom Kernels
      • None...
    8. Custom ROM(s) - Android 11 (R)
      • PixelExperience 05/12
      • PegasusOS 05/05
      • PixePixelDust 04/20
    9. Custom ROM(s) - Android 10 (Q)
      • lineage-17.1 05/12


    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 XL phone with an unlocked bootloader.
    2. Android 11 (Q) Custom ROM (Index #6 below).
    3. Computer - With the latest SDK Platform-Tools: r31.0.2 installed.


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


    Index
    (NOTE: Numbers 1-8 are not steps, they are individual sets of instructions).

    1. Open a Command Prompt/Boot Bootloader/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 ADB (Android Debug Bridge)/fastboot

      • ADB
        1. Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
        2. Open a Command Prompt on your computer.
        3. Type this at the prompt to test ADB.
          adb version
          It should return a version number for ADB.
      • fastboot
        1. Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
        2. Open a Command Prompt on your computer.
        3. Boot Bootloader
        4. Connect the phone to the Computer with USB cord.
        5. Type this at the prompt and press enter to test fastboot.
          Code:
          fastboot devices
          It should return your device serial number.
    3. Unlock Bootloader/Return Phone to Stock/Lock Bootloader

      • Unlock Bootloader

        1. Backup your data/Internal storage
        2. Activate Developer Options: Tap Settings > System > About Phone > Tap Build Number 7 times or until you see you're a Developer.
        3. Tap back > Developer Options and toogle OEM Unlock on and, toggle USB Debugging on.
        4. Boot Bootloader
        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.
          This will erase all user data from the device!
        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.
          Note: After unlocking your bootloader, you'll see a warning: Your device software can't be checked for corruption. Please lock the bootloader. You will see this warning until, you relock the bootloader.


          Important: Do not relock your bootloader until you have returned the device to Stock.
          .
      • Return Phone to Stock

        1. Backup your data/Internal storage
        2. Settings > System > Advanced > Reset Options > Erase all data (factory reset)
        3. Log in
        4. Set up phone
      • Lock Bootloader

        1. Important: Do not relock your bootloader until you have returned the device to Stock..
        2. Boot bootloader
        3. Open a Command Prompt and type this at the Prompt: fastboot flashing lock
        4. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        5. Allow the process to complete, then type this at the Command Prompt: fastboot reboot
        6. Set up your phone.
        7. Enable Developer Options: Settings > System > About phone > Tap Build number 7 times or until you see'You are a Developer. Tap Back > Developer options and toggle OEM Unlock off.
    4. 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 (10.0.0 (QP1A.191005.007.A3, Dec 2019)) to a folder.
        4. Open the folder you extracted the Factory image to and, extract the Image file (image-marlin-aaa9.999999.999.99a.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 the platform-tools or to the folder that has fastboot in it.
        3. Boot Bootloader
        4. Connect the phone to the Computer
        5. Open a Command Prompt and type the following command at the prompt:
          fastboot flash boot boot.img --slot all
        6. Reboot
    5. Set Magisk App Update Chanel/Update Magisk

      • Set Magisk App Update Channel

        • 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!
    6. Custom ROMs for Pixel XL

    7. Mods
    8. Other: TWRP Backup

    2
    Well I'm kind of making progress. Let me tell you what I did... I flashed a factory image of the latest one Android 10...after the flash it began to bootloop once again... I button combo into fastboot and went ahead and locked the bootloader... Chose reboot and every time it boots it boots right back into stock recovery...I factory reset it 3 to 5 times, reboot and once again reboots right back to stock recovery.. I took some pictures of the recovery logs in recovery...I am really adamant about fixing this issue as I have heard that a lot of people are experiencing it.. take a look at my pictures homeboy. to my surprise I am able to go back into fastboot and lock and unlock the bootloader at will. After looking at the pictures what do you think that the issue is?
    I admire your tenacity to get your Google Pixel fixed.

    I am not a Google Pixel technician, so I cannot help you fix your Google Pixel. My guide is for a Google Pixel XL operation not maintenance.

    Maybe your best resource is Google search.
    1. Google Pixel - XDA Developers Forums
    2. Welcome to the Google Pixel Help Community
    3. Fix a Pixel phone that's restarting or crashing
    4. Google Pixel Forum

    Have a nice day! :)
    2
    hi guys I am not new to modding phones. However it has been a long time for me. I did have my 6p running on lineage for a while. But then I got the pixel xl and have had pixels ever since. I have not had a need to root or modd them. I currently have the 4xl and my wife has the 3a xl so I have this pixel xl sitting around. I want to get back into modding a little bit. I just need some guidance.
    Currently I have downloaded the latest sdk for windows I will need a little assistance with that for example how do I put adb and fastboot into the root directory so I dont have to go through typing all the file paths in. I also downloaded the latest stock .img so I have a clean install if anything goes crazy.
    Now I need to know where to start. I assume unlocking the bootloader is the same as the 6p. But after that do I install twrp then use that for magisk to get root? Once I have those questions answered I can probably take it from there. I would like to try out different roms and kernels and other mods. Sorry for the noob questions I just want to get it right. I always learn stuff on this fourm and thats why I love it.
    Start by reading the guide: Introduction, Disclaimers, Update(s), Prerequisites, and Index (Numbers 1 to 11).
    Why?
    ...how do I put adb and fastboot into the root directory so I dont have to go through typing all the file paths in.
    - There is a link in Prequisites c. (Need help installing or using SDK Platform-tools) that describes editing your Path Variable.

    "Now I need to know where to start. I assume unlocking the bootloader is the same as the 6p."
    - Assume nothing, several people have bricked their phone(s) assuming. Read #3 in the guide.

    "But after that do I install twrp then use that for magisk to get root?"
    - T.W.R.P. does not work with Android 10 to root: Read #9 to root.

    There is no need to apologize for the "noob questions". Everyone on XDA was a "noob" at some point in their life.
    2
    Hey, first off thanks for the guide. I have been experiencing the same boot issue that a few others have. I am on the latest version of everything, android sdk, latest factory image, latest magisk (tried both stable and canary). I can patch the boot.img with magisk and after i flash the magisk_patched.img, i reboot the phone and it sticks on the google "G" with the progress bar underneath it. I am on the same build number as the one I downloaded ending in 007.A1, using the same boot.img from it. When it hangs up, I can flash the same boot.img that I used magisk to patch and reboot the phone and it is back to normal and goes right to the lock screen. I could be wrong, but it appears that my issue is with the boot.img being patched with magisk somehow. Any advice or help is appreciated, thanks.

    edit: When it sticks on bootloop, i can still use a command prompt to "adb reboot fastboot" and then flash the stock boot.img and it boots normal.

    Were you rooted on the September factory image?
    Did you fastboot flash boot --slot all magisk_patched.img?
    SDK Platform-tools r29.0.5?
    Read this it might help.
    1
    Has anyone tried using the current TWRP and Magisk?

    Yes. Didn't work, just rebooted twice (I think) then booted directly into android.
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