• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Guide] How to root the Pixel 3a with or without twrp & take OTA updates once rooted

Search This thread

joedp2

Member
Oct 17, 2014
26
3
I am trying to do the latest update.

I downloaded the file, patched the boot.img file through magisk, and replaced the original with the renamed patched file.

I removed the -w from the flash-all.bat file.

But I cannot get it to run.

I have tried running the .bat file directly. I have tried dragging it into a cmd folder. I have tried it with the phone turned on. I have tried it in bootloader mode. I have tried it in fastboot mode.

Every time, I get a message that it is waiting for a device. I have the adb files in the same folder with the update files and adb commands work, so I know the phone is connected and recognized.

What am I doing wrong?
Update:

I installed new windows android drivers, which allowed helped, but I am now getting this message when I try the reflash:

"C:\Users\joedp\Documents\Phone stuff\Pixel root\Android 11\sargo-rq3a.210905.001-factory-2dd7b68f\sargo-rq3a.210905.001\flash-all.bat"
Sending 'bootloader' (8373 KB) OKAY [ 0.228s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.001s
< waiting for any device >
Sending 'radio_a' (73372 KB) OKAY [ 2.069s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g670-00116-210406-B-7261833
(bootloader) Flashing partition modem_a
OKAY [ 0.562s]
Finished. Total time: 3.101s
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: b4s4-0.3-6863017
Baseband Version.....: g670-00116-210406-B-7261833
Serial Number........: 943AY0JE2C
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' FAILED

Device version-bootloader is 'b4s4-0.3-6863017'.
Update requires 'b4s4-0.3-7357923'.

fastboot: error: requirements not met!
Press any key to exit...

Now what?
 

mulperi

Senior Member
Apr 25, 2010
145
34
Update:

I installed new windows android drivers, which allowed helped, but I am now getting this message when I try the reflash:

"C:\Users\joedp\Documents\Phone stuff\Pixel root\Android 11\sargo-rq3a.210905.001-factory-2dd7b68f\sargo-rq3a.210905.001\flash-all.bat"
Sending 'bootloader' (8373 KB) OKAY [ 0.228s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.001s
< waiting for any device >
Sending 'radio_a' (73372 KB) OKAY [ 2.069s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g670-00116-210406-B-7261833
(bootloader) Flashing partition modem_a
OKAY [ 0.562s]
Finished. Total time: 3.101s
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: b4s4-0.3-6863017
Baseband Version.....: g670-00116-210406-B-7261833
Serial Number........: 943AY0JE2C
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' FAILED

Device version-bootloader is 'b4s4-0.3-6863017'.
Update requires 'b4s4-0.3-7357923'.

fastboot: error: requirements not met!
Press any key to exit...

Now what?
Copy all the files from the zip archive to the directory that contains adb.exe and try again:
  1. flash-all.bat
  2. bootloader-sargo-b4s4-0.3-7357923.img
  3. radio-sargo-g670-00116-210406-b-7261833.img
  4. image-sargo-rq3a.210905.001.zip
 

dcarvil

Senior Member
Apr 20, 2016
485
259
I am trying to do the latest update.

I downloaded the file, patched the boot.img file through magisk, and replaced the original with the renamed patched file.

I removed the -w from the flash-all.bat file.

But I cannot get it to run.

I have tried running the .bat file directly. I have tried dragging it into a cmd folder. I have tried it with the phone turned on. I have tried it in bootloader mode. I have tried it in fastboot mode.

Every time, I get a message that it is waiting for a device. I have the adb files in the same folder with the update files and adb commands work, so I know the phone is connected and recognized.

What am I doing wrong?
I think you need to run flash-all.bat with the original, unpatched boot image file, not the patched version. After the update is completely installed (which requires booting into Android with the unpatched boot image), do:

adb reboot bootloader
fastboot flash boot magisk_patched.img
 
Last edited:

joedp2

Member
Oct 17, 2014
26
3
I think you need to run flash-all.bat with the original, unpatched boot image file, not the patched version. After the update is completely installed (which requires booting into Android with the unpatched boot image), do:

adb reboot bootloader
fastboot flash boot magisk_patched.img
I just tried flashing with the unpatched image file, but I got the same error message.
 

joedp2

Member
Oct 17, 2014
26
3
New update:

I looked at the updates list and realized that there are new ones every month, but the last time I had updated was January. So I flashed the February update, which seemed to work, but then soft-bricked the phone in a bootloader loop.

I then flashed the April update, which I had not had a chance to patch, and was successful. I left the phone unrooted overnight and patched and flashed the May update this morning.

My first attempt to flash the June update did not work, but I didn't have time to try again, so I will see if I can patch and flash the rest of the updates after work tonight.

I appreciate all the help. we'll see if I need any more help after I try to do more of the sequential updates tonight or tomorrow.
 

joedp2

Member
Oct 17, 2014
26
3
Do you still get "Writing 'bootloader' FAILED (remote: 'No such file or directory')"?

If so, what is the output of the following commands?

type flash-all.bat
dir
Yes. I am still getting an error when it tries to flash the new bootloader. I get the same error with the June, July, August, and September updates. I had no trouble with the March, April, or May updates.



type flash-all.bat
@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-sargo-b4s4-0.3-7357923.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-sargo-g670-00116-210406-b-7261833.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-sargo-rq3a.210905.001.zip

echo Press any key to exit...
pause >nul
exit


dir
Volume in drive C has no label.
Volume Serial Number is D827-5684

Directory of C:\Users\joedp\Documents\Phone stuff\Pixel root\Android 11\Update sept 2021\sargo-rq3a.210905.001-factory-2dd7b68f\sargo-rq3a.210905.001

09/24/2021 06:24 AM <DIR> .
09/24/2021 06:24 AM <DIR> ..
09/19/2021 04:30 PM 5,941,760 adb.exe
09/19/2021 04:30 PM 97,792 AdbWinApi.dll
09/19/2021 04:30 PM 62,976 AdbWinUsbApi.dll
09/23/2021 10:03 PM 8,574,632 bootloader-sargo-b4s4-0.3-7357923.img
09/19/2021 04:30 PM 243,200 dmtracedump.exe
09/19/2021 04:30 PM 440,320 etc1tool.exe
09/19/2021 04:30 PM 1,632,768 fastboot.exe
09/23/2021 10:04 PM 984 flash-all.bat
09/23/2021 10:03 PM 1,104 flash-all.sh
09/23/2021 10:03 PM 1,053 flash-base.sh
09/19/2021 04:30 PM 43,520 hprof-conv.exe
09/24/2021 06:26 AM <DIR> image-sargo-rq3a.210905.001
09/23/2021 10:03 PM 1,673,259,778 image-sargo-rq3a.210905.001.zip
09/19/2021 04:30 PM 231,594 libwinpthread-1.dll
09/19/2021 04:30 PM 501,248 make_f2fs.exe
09/19/2021 04:30 PM 501,248 make_f2fs_casefold.exe
09/19/2021 04:30 PM 1,157 mke2fs.conf
09/19/2021 04:30 PM 770,560 mke2fs.exe
09/19/2021 04:30 PM 761,396 NOTICE.txt
09/23/2021 10:03 PM 75,133,068 radio-sargo-g670-00116-210406-b-7261833.img
09/19/2021 04:30 PM 38 source.properties
09/19/2021 04:30 PM 1,217,536 sqlite3.exe
21 File(s) 1,769,417,732 bytes
3 Dir(s) 885,705,371,648 bytes free
 
Last edited:

dcarvil

Senior Member
Apr 20, 2016
485
259
Yes. I am still getting an error when it tries to flash the new bootloader. I get the same error with the June, July, August, and September updates. I had no trouble with the March, April, or May updates.



type flash-all.bat
@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-sargo-b4s4-0.3-7357923.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-sargo-g670-00116-210406-b-7261833.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-sargo-rq3a.210905.001.zip

echo Press any key to exit...
pause >nul
exit


dir
Volume in drive C has no label.
Volume Serial Number is D827-5684

Directory of C:\Users\joedp\Documents\Phone stuff\Pixel root\Android 11\Update sept 2021\sargo-rq3a.210905.001-factory-2dd7b68f\sargo-rq3a.210905.001

09/24/2021 06:24 AM <DIR> .
09/24/2021 06:24 AM <DIR> ..
09/19/2021 04:30 PM 5,941,760 adb.exe
09/19/2021 04:30 PM 97,792 AdbWinApi.dll
09/19/2021 04:30 PM 62,976 AdbWinUsbApi.dll
09/23/2021 10:03 PM 8,574,632 bootloader-sargo-b4s4-0.3-7357923.img
09/19/2021 04:30 PM 243,200 dmtracedump.exe
09/19/2021 04:30 PM 440,320 etc1tool.exe
09/19/2021 04:30 PM 1,632,768 fastboot.exe
09/23/2021 10:04 PM 984 flash-all.bat
09/23/2021 10:03 PM 1,104 flash-all.sh
09/23/2021 10:03 PM 1,053 flash-base.sh
09/19/2021 04:30 PM 43,520 hprof-conv.exe
09/24/2021 06:26 AM <DIR> image-sargo-rq3a.210905.001
09/23/2021 10:03 PM 1,673,259,778 image-sargo-rq3a.210905.001.zip
09/19/2021 04:30 PM 231,594 libwinpthread-1.dll
09/19/2021 04:30 PM 501,248 make_f2fs.exe
09/19/2021 04:30 PM 501,248 make_f2fs_casefold.exe
09/19/2021 04:30 PM 1,157 mke2fs.conf
09/19/2021 04:30 PM 770,560 mke2fs.exe
09/19/2021 04:30 PM 761,396 NOTICE.txt
09/23/2021 10:03 PM 75,133,068 radio-sargo-g670-00116-210406-b-7261833.img
09/19/2021 04:30 PM 38 source.properties
09/19/2021 04:30 PM 1,217,536 sqlite3.exe
21 File(s) 1,769,417,732 bytes
3 Dir(s) 885,705,371,648 bytes free
I don't see anything obviously wrong, but since it stopped working with the June update my guess would be you are using an old version of fastboot. What is the output of "fastboot --version"? It should be 31.0.3.

From your directory structure, it appears you have multiple instances of fastboot on your pc. That can lead to problems if they are not all the same version.

I'm not sure why you are trying to flash the monthly updates sequentially, unless it is for troubleshooting purposes. They are full images, so all you need is the latest update.
 
  • Like
Reactions: joedp2

joedp2

Member
Oct 17, 2014
26
3
I don't see anything obviously wrong, but since it stopped working with the June update my guess would be you are using an old version of fastboot. What is the output of "fastboot --version"? It should be 31.0.3.

From your directory structure, it appears you have multiple instances of fastboot on your pc. That can lead to problems if they are not all the same version.

I'm not sure why you are trying to flash the monthly updates sequentially, unless it is for troubleshooting purposes. They are full images, so all you need is the latest update.
I could explain the flawed thinking that led me to try the sequential updates, but I think I'll seem less foolish if we leave it at "troubleshooting purposes".

I'm getting an error when I try "fastboot--version" also. It says it is not a valid command.

As far as the multiple instances/versions, I downloaded it new when I started trying to update last week. I have not gone through all the other folders to get rid of older downloads. Is that something I should do?


Update: I checked the source.properties file and it says the version is 31.0.3.
 

joedp2

Member
Oct 17, 2014
26
3
I went back and deleted multiple copies of older versions of the adb tools. Then I deleted the September update download and redownloaded it. I tried again and got the same error.
 

dcarvil

Senior Member
Apr 20, 2016
485
259
I went back and deleted multiple copies of older versions of the adb tools. Then I deleted the September update download and redownloaded it. I tried again and got the same error.
So you are now on fastboot version 31.0.3?

Your original post said "I have tried it in bootloader mode. I have tried it in fastboot mode.". Bootloader mode is fastboot mode. What command are you executing prior to flash-all.bat to put the phone in fastboot mode. Are you sure you are not in fastbootd mode instead of fastboot mode when you execute flash-all.bat?

Before you execute flash-all.bat, execute "fastboot devices". What is the output?

BTW, if you don't click reply to my message, I do not get notified you have replied.
 

dcarvil

Senior Member
Apr 20, 2016
485
259
I could explain the flawed thinking that led me to try the sequential updates, but I think I'll seem less foolish if we leave it at "troubleshooting purposes".

I'm getting an error when I try "fastboot--version" also. It says it is not a valid command.

As far as the multiple instances/versions, I downloaded it new when I started trying to update last week. I have not gone through all the other folders to get rid of older downloads. Is that something I should do?


Update: I checked the source.properties file and it says the version is 31.0.3.
You get the "not a valid command" error because you left out the space between fastboot and --version.
 

joedp2

Member
Oct 17, 2014
26
3
So you are now on fastboot version 31.0.3?

Your original post said "I have tried it in bootloader mode. I have tried it in fastboot mode.". Bootloader mode is fastboot mode. What command are you executing prior to flash-all.bat to put the phone in fastboot mode. Are you sure you are not in fastbootd mode instead of fastboot mode when you execute flash-all.bat?

Before you execute flash-all.bat, execute "fastboot devices". What is the output?

BTW, if you don't click reply to my message, I do not get notified you have replied.
I really appreciate all your help.

When I first tried, I had tried executing the flash-all.bat file after adb reboot fastboot and adb reboot bootloader. When I figured out that earlier updates would work, it was when I used adb reboot fastboot., so that was what I kept using

After I enter adb reboot fastboot, the screen says fastbootd.

fastboot devices yields:

943AYOJE2C fastboot
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Yes. I am still getting an error when it tries to flash the new bootloader. I get the same error with the June, July, August, and September updates. I had no trouble with the March, April, or May updates.



    type flash-all.bat
    @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-sargo-b4s4-0.3-7357923.img
    fastboot reboot-bootloader
    ping -n 5 127.0.0.1 >nul
    fastboot flash radio radio-sargo-g670-00116-210406-b-7261833.img
    fastboot reboot-bootloader
    ping -n 5 127.0.0.1 >nul
    fastboot update image-sargo-rq3a.210905.001.zip

    echo Press any key to exit...
    pause >nul
    exit


    dir
    Volume in drive C has no label.
    Volume Serial Number is D827-5684

    Directory of C:\Users\joedp\Documents\Phone stuff\Pixel root\Android 11\Update sept 2021\sargo-rq3a.210905.001-factory-2dd7b68f\sargo-rq3a.210905.001

    09/24/2021 06:24 AM <DIR> .
    09/24/2021 06:24 AM <DIR> ..
    09/19/2021 04:30 PM 5,941,760 adb.exe
    09/19/2021 04:30 PM 97,792 AdbWinApi.dll
    09/19/2021 04:30 PM 62,976 AdbWinUsbApi.dll
    09/23/2021 10:03 PM 8,574,632 bootloader-sargo-b4s4-0.3-7357923.img
    09/19/2021 04:30 PM 243,200 dmtracedump.exe
    09/19/2021 04:30 PM 440,320 etc1tool.exe
    09/19/2021 04:30 PM 1,632,768 fastboot.exe
    09/23/2021 10:04 PM 984 flash-all.bat
    09/23/2021 10:03 PM 1,104 flash-all.sh
    09/23/2021 10:03 PM 1,053 flash-base.sh
    09/19/2021 04:30 PM 43,520 hprof-conv.exe
    09/24/2021 06:26 AM <DIR> image-sargo-rq3a.210905.001
    09/23/2021 10:03 PM 1,673,259,778 image-sargo-rq3a.210905.001.zip
    09/19/2021 04:30 PM 231,594 libwinpthread-1.dll
    09/19/2021 04:30 PM 501,248 make_f2fs.exe
    09/19/2021 04:30 PM 501,248 make_f2fs_casefold.exe
    09/19/2021 04:30 PM 1,157 mke2fs.conf
    09/19/2021 04:30 PM 770,560 mke2fs.exe
    09/19/2021 04:30 PM 761,396 NOTICE.txt
    09/23/2021 10:03 PM 75,133,068 radio-sargo-g670-00116-210406-b-7261833.img
    09/19/2021 04:30 PM 38 source.properties
    09/19/2021 04:30 PM 1,217,536 sqlite3.exe
    21 File(s) 1,769,417,732 bytes
    3 Dir(s) 885,705,371,648 bytes free
    I don't see anything obviously wrong, but since it stopped working with the June update my guess would be you are using an old version of fastboot. What is the output of "fastboot --version"? It should be 31.0.3.

    From your directory structure, it appears you have multiple instances of fastboot on your pc. That can lead to problems if they are not all the same version.

    I'm not sure why you are trying to flash the monthly updates sequentially, unless it is for troubleshooting purposes. They are full images, so all you need is the latest update.
    1
    I just retried flashing after adb reboot bootloader. Looks like it worked.

    Thank you again for all your help!
    Yes, the "adb reboot fastboot" was the problem. That puts the phone in fastbootd mode instead of fastboot mode. I have no idea why the earlier updates worked in fastbootd mode.

    Glad I could help.
  • 41
    [Guide] How to root the Pixel 3a with or without twrp & take OTA updates once rooted

    THIS IS A DRAMA FREE THREAD, I'M NOT GOING TO BASH OTHERS THREADS, NOR AM I GOING TO GO AROUND TO THOSE THREADS AND BASH THEM IN IT BECAUSE I SOMEHOW FEEL SUPERIOR TO THEM.

    Standard you do this at your own risk and I'm not responsible for anything warning.


    There are a few ways you can go about rooting. You can either use twrp, manually patch the stock boot image and flash it, or just flash a pre-patched boot image. I'll be going over all three, but keep in mind i have depreciated the pre-patched method now that we have twrp. twrp is dead on 10

    Do these first if you haven't already:

    Update your fastboot and adb
    I just toss these 4 highlighted files into the windows folder, but you may have a different set up(I put them in the windows folder so I don't have to add them to PATH.)
    https%3A%2F%2Fcdn.discordapp.com%2Fattachments%2F399670410565910529%2F578336582684246027%2Funknown.png


    Googles USB driver if you need it
    right click the start menu icon, click device manager, then locate your phone(should have a yellow symbol on it, right click it, then click update driver, then click browse my computer, click the browse button and then navigate to where you extracted the drivers, click the main folder(usb_driver) and then click ok, then click next and ok through any prompts.


    CMD = Command Prompt

    Unlocking your bootloader:
    This wipes your phone
    1. Run through the initial setup if you haven't already, if you haven't don't bother logging into your google account.
    2. Enable dev options(settings>about phone>build number>tap it 7 times).
    3. Go into settings>system>advanced>dev options>oem unlocking, click the toggle.
    4. While still in dev options scroll down a little and enable usb debugging.
    5. Plug your phone into your pc.
      if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
    6. Open up command prompt(powershell works to but i always use command prompt) type into the cmd window
    7. Code:
      adb reboot bootloader
      The phone will reboot into fastboot mode.
    8. Now type into the cmd window
      Code:
      fastboot devices
      See if it lists a device, if not you need to install the drivers I linked to. If you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.
    9. type in
      Code:
      fastboot flashing unlock
      You will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm.

      Your bootloader is now unlocked and you follow one of the below root methods.

    Onto the root methods:
    these are for stock phones, not ones using a custom kernel

    IF ON Q YOU MUST USE MAGISK 19.4+

    Grab your boot.img from here
    it's inside the zip that is inside the folder in the main zip you download

    patching and flashing the stock boot.img:
    This is the only way to root on android 10+ as twrp doesnt work

    1. Reboot your phone.
    2. Run through the initial setup again, this time you can log into your google account and set the phone up how you want. Re-enable dev options, enable adb, and turn off auto updates.
    3. Grab the stock boot.img for your matching build(from the link above).
    4. Put the boot.img on your phone, location doesn't really matter, as long as you know where you put it.
    5. Download and install Magisk Manager.
    6. Open up magisk manager and click install, then select the "Select and Patch a File" option, let it do its thing.
    7. Move the patched image from your phone to your pc(magisk stores the patched image in your downloads folder).
    8. Open up a cmd window and type in
      Code:
      adb reboot bootloader
      if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
    9. Once you are in the bootloader(fastboot) type in
      Code:
      fastboot getvar current-slot
      This will tell you the currently active slot of your phone, remember it.
    10. Now to flash your patched boot.img.

      - If the cmd window location does not match the location of the boot.img you will have to enter that too.
      - If you're on windows 10(this only works on English as far as i know) you can use my Tools Menu it will give you some handy options in your right click context menu. It makes things a lot easier as you can just right click in the location of the boot.img and open a cmd window there.

      - If your cmd window is opened in the same location as the boot image you can just do(don't include the ")
      Code:
      fastboot flash boot_"slot "whatever the boot.img is named"

      - If your cmd window was not opened in the same location as the boot image you will need to do one of these.
      Code:
      cd C:\Users\pbanj\Desktop\android
      the cd command changes the current directory to where you tell it. then you can just do
      Code:
      fastboot flash boot_"slot" "whatever the boot.img is named"

      - Or you can type out the location to the boot.img or just drag the boot.img file onto the cmd window. example:
      Code:
      fastboot flash boot_"slot" C:\Users\pbanj\Desktop\boot.img
    11. Once that's done flashing just type in
      Code:
      fastboot reboot
      MAKE SURE YOU GO INTO DEV OPTIONS AND TURN OFF AUTO UPDATES.

    You should use the twrp method over this next one. I'll no longer be adding updated pre-patched boot images as they're completely pointless now that we have twrp.

    Do NOT use this method, it's here just for history sake
    Method 3 booting a prepatched boot.img and direct installing Magisk:
    This gets you rooted a bit faster. thanks to @Uzephi for reminding me about this.
    1. Grab the boot.img that matches your build number in about phone. These were made using the newest canary build of magisk at the time of adding them to the post. If I update them I'll mark them as updated. I used the canary builds for these as it's what I personally use
      - PD2A.190115.029
      - PD2A.190115.032 Updated to newest canary build as of May-28-2019
      - PQ3B.190605.006 This is the June update Updated to the 19.4-c1602d25(19301) canary build
      - PQ3B.190705.003 this is the July update

      Save it somewhere and rename it if you want.
    2. If not already in fastboot mode open up a command prompt window and type in
      Code:
      adb reboot bootloader
      if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
    3. Once you are in the bootloader(fastboot) type in
      Code:
      fastboot boot "whatever the boot.img is named".img
      - If the cmd window location does not match the location of the boot.img you will have to enter that too.
      - If you're on windows 10(this only works on English as far as i know) you can use my Tools Menu it will give you some handy options in your right click context menu. It makes things a lot easier as you can just right click in the location of the boot.img and open a cmd window there.

      - If your cmd window is opened in the same location as the boot img you can just do(don't include the ")
      Code:
      fastboot boot "whatever the boot.img is named".img

      - If your cmd window was not opened in the same location as the boot image you will need to do one of these.
      Code:
      cd C:\Users\pbanj\Desktop\android
      the cd command changes the current directory to where you tell it. then you can just do
      Code:
      fastboot boot "whatever the boot.img is named".img

      - Or you can type out the location to the boot.img or just drag the boot.img file onto the cmd window. example:
      Code:
      fastboot boot C:\Users\pbanj\Desktop\android\boot.img
    4. Once booted run through the initial setup again(if you haven't already after unlocking the bootloader), this time you can log into your google account and set the phone up how you want.
      MAKE SURE YOU GO INTO DEV OPTIONS AND TURN OFF AUTO UPDATES.
    5. After you've run through the initial setup(if you had to) open up Magisk Manager(it will most likely say the manager needs to be installed as it is currently only a stub) and then click on the top install option, then click install in the popup that comes up, then click the direct install option.
      unknown.png

      unknown.png

      unknown.png

    6. After it finishes click reboot and you're good to go


    UPDATING
    There are a couple methods of updating.

    Uninstall the edge sense plus mod before you update or you won't be able to root again/you'll end up in a bootloop and will have to enter safemode to disable it.

    WHEN UPDATING TO ANDROID 11 DISABLE ALL MAGISK MODS AND REBOOT ONCE BEFORE UPDATING.

    If you're using any custom kernel you'll have to flash the stock boot.img first before updating for the sideload method. The magisk method it might not matter but I'm not 100% sure on that. I'd think it'd be fine if you had magisk backup the stock image before you flashed the custom kernel, I don't use one so I cant be 100% sure though.

    magisk has removed the ota method for pixel devices so these are the ways to update now.

    My personal favorite way to update is to use the full system image as it's fastest. Disable any custom themes or modules that are known to cause bootloops when updating. Then:
    1. grab the system image from here, unzip the folder and inside of it you will find another zip. open that up and pull the boot.img out.
    2. Use magisk manager on your phone to patch that and then take the patched image and rename it to boot.img and put it back in the zip you pulled the stock one from.
    3. Open the "flash-all.bat or .sh if on linux" and remove the -w from the end(this is important as it stops your device from being wiped) save the bat file.
    4. put your phone into fastboot mode and run the flash-all script. should take about 5 min and then your phone will reboot and you are good to go.

    I made a telegram group where I'll be posting the system images ready to flash. I typically make them within a few days of the update coming out. https://t.me/joinchat/EC3ivRhc2-t4y1J4REtuqg


    Alternative Update method

    1. Grab the OTA update from here.
    2. Reboot the phone into recovery, you can just use
      Code:
      adb reboot recovery
    3. Once in recovery press power and up and you should see the options.
    4. Go down to apply update from adb(use the volume keys to change options and the power button to select).
    5. Open a cmd window if you haven't already and type in
      Code:
      adb sideload "ota update file"
      Location matters just like it did during the initial flashing, if you didn't open the cmd window in the same location as the update file andyou don't remember what to do, just take a look at one of the root methods as they tell you how to go about fixing that. Or just type in "adb sideload" and then drag the update file onto the cmd window.
    6. After the ota is done select the "reboot to bootloader option".
    7. Once in the bootloader(fastboot) just flash the pre-patched boot.img like you did before. remember the slot changes with each update so make sure you get the current slot, or if you remember what slot it was using before the update just switch input the other one. so if it was on slot a you would flash the patched image to b and vise versa.



    BOOT IMAGES:
    This is a google drive folder, it will have both stock and patched images. I also provide the newest Magisk manager These are zip files, you must unzip them to use them.
    - https://drive.google.com/drive/folders/1wH7pvsHYznbDJ_vTsb_dWBNJBDcx2wHx?usp=sharing

    Ways to get pay to work
    Completely automated way:
    • Install this Magisk mod, it can also be found in the Magisk Manager by searching "sql" it is named "SQLite for ARM aarch64 devices"
    • Reboot. This step might not be needed, but it's how I did it when figuring everything out.
    • Grab this file
    • Use your favorite root explorer and place it in /data/adb/service.d/
    • Set the perms for the gpay file to rwxr-xr-x(755) owner and group should be "root" if they're not already.
    • Reboot
    That's it, you never have to worry about it again. service.d is where Magisk loads scripts from, so magisk will handle everything for you. Thanks to the people who helped me figure the script out, I forgot their names.

    - SEMI-AUTO/AUTO METHOD
    - MANUAL METHOD.

    How to use Netflix
    1. Grab the newest apk from here.
    2. Install the apk.
    3. Add the apk to your Magisk Hide list.

    if you need help you can ask here in the thread or in the Telegram group
    13
    Hello,
    I will receive my pixel 3a tonight and I want to root it since the beginning to have more possibilities with it.
    But I'm not an expert to root Pixel phone.
    I have a OnePlus 6T who was easy to root.

    Can anyone create a little tuto or guide to root the pixel 3a with magisk ?

    Thanks for your help

    super simple. I'll assume you use windows
    should be noted that unlocking it wipes the phone.
    standard you do at your own risk warning applies

    update your adb and fastboot I just toss these 4 highlighted files into the windows folder, but you may have a different set up(I put them in the windows folder so I don't have to add them to PATH.
    unknown.png
    you may also need the usb drivers

    - run through the initial setup(don't bother logging into your google account).

    - enable dev options(settings>about phone>build number>tap it 7 times)

    - go into settings>system>advanced>dev options>oem unlocking, click the toggle

    - while still in dev options scroll down a little and enable usb debugging

    - plug your phone into your pc
    if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box
    - open up command prompt(powershell works to but i always use command prompt) type into the command prompt
    Code:
    adb reboot bootloader
    the phone will reboot into fastboot mode.

    - now type into the cmd window
    Code:
    fastboot devices
    and see if it lists a device, if not you need to install the drivers i linked to
    right click the start menu icon, click device manager, then locate your phone(should have a yellow symbol on it, right click it, then click update driver, then click browse my computer, click the browse button and then navigate to where you extracted the drivers, click the main folder(usb_driver) and then click ok, then click next and ok through any prompts


    - if you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.

    - now type in
    Code:
    fastboot flashing unlock
    you will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm

    - now you can flash the boot.img I provided that matches your build number using
    Code:
    fastboot flash boot "whatever the boot.img is named"
    if the cmd window location does not match the location of the boot.img you will have to enter that too examples
    Code:
    fastboot flash boot C:\Users\pbanj\Desktop\boot.img
    or you can do
    Code:
    cd C:\Users\pbanj\Desktop
    and then just do the normal fastboot flash boot whatever the boot.img is named.

    if flashing fails use the command
    Code:
    fastboot getvar current-slot
    it will tell you the currently active slot, either A or B. run the flashing command again but this time instead of boot do boot_"slot letter" example
    Code:
    fastboot flash boot_a boot.img


    - after that finishes flashing you can reboot the phone by typing in
    Code:
    fastboot reboot

    - now go through the setup and actually set your device up.

    - after it is set up open up the magisk manager and it will tell you it needs to install the real manager, select ok

    - now open the real magisk manager and it will prompt that it needs to install so extra stuff, select ok, and then reboot when it asks you to.

    - you're now rooted, add what you want to magisk hide, and install the magisk mods you want, although i wouldn't go too crazy until we have twrp. if pay doesn't work follow the steps i gave in the main post.

    - to update magisk just select the direct install method.

    MAKE SURE YOU GO INTO DEV OPTIONS AND TURN OFF AUTO UPDATES.

    - follow this to do an ota update

    also a shameless plug. if you want to make opening command prompt or powershell in your current folder a bit easier you can use My tools menu but iirc it only works on English windows 10.
    7
    I'll be updating the thread with boot images until we get twrp
    7
    Here is a fix for those who updated with edge sense plus installed. https://cdn.discordapp.com/attachme.../589904771545300992/boot-magisk-core-only.img

    Use "fastboot boot" instead of "fastboot flash". After that boots open up Magisk manager and remove the edge sense plus mod. You can then root properly.

    The file is based on the June update and was made by @ApeironTsuka so everyone should thank them.

    Once I get home I'll add this to the main post, but I wanted to share this asap.
    6
    Looks like it's still a little rough, I'll wait for him to get things sorted out a better. Thanks for the heads up.

    Everything working 100% now. The 3A XL is my new daily driver.