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

[joedp2]

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]

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]

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

 

[joedp2]

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.

 

[dcarvil]

I just tried flashing with the unpatched image file, but I got the same error message.

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

 

[joedp2]

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]

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

 

[dcarvil]

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.

 

[joedp2]

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]

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]

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]

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]

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

 

[joedp2]

I just retried flashing after adb reboot bootloader. Looks like it worked.

Thank you again for all your help!

 

[dcarvil]

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.

 

[amarmak]

Will this method work on devices with OEM Unlock greyed.

 

[pbanj]

Will this method work on devices with OEM Unlock greyed.

no if your bootloader is hard locked you are sol. youd need to wait for an exploit to be able to root it.

 

[pbanj]

updated the method to pass safetynet and fixed a broken image.

 

[Emmalfal]

I am literally on the last step of this rooting process and I'm hung up. I use fastboot flash boot_b boot.img and get a "cannot load boot.img" message. I tried just fastboot flash boot_b boot but that returned an error message,too? I feel like I'm missing just one little thing before I get to the glory of root.

 

[Emmalfal]

Just use the boot.img provided above and install magisk to use gpay with unlocked bootloader. Best to unlock when you first get the device rather than setting it up twice because unlocking wipes the device.

Sent from my Pixel 3a using Tapatalk

I doubt like hell anyone is monitoring this page. Just in case, here's the issue I'm running into. In the final step, I enter fastboot flash boot_b and then I enter the location and the file I want to flash, in this case, the Magisk patched boot.img. I get a long string of commands when I hit enter but that's all. I go back to my phone, check root and nope. Not rooted. I have no idea what I'm supposed to see when I flash the patched boot image, but so far, I'm not getting root. Any advice appreciated.