June security update is out for Pixel 3a

[oscar1823]

What are trying to do with the previously mentioned modified image?

Oh I'm just trying to update to latest june patch.

 

[12paq]

Oh I'm just trying to update to latest june patch.

If you are rooted, use Magisk to partially uninstall root, then flash the OTA. Then reroot with Magisk.
In the "how to root" thead for this device that you mentioned, there are intructions and links to walk you through all of it.

 

[sic0048]

The "issue" is the fact that users have supplied these "modified boot.img" files and others are using them to install Magisk in an unconventional way. I realize they are doing it in an attempt to be helpful and speed up the root process and it does make it easier for the initial installation. But using these files is actually making it harder to take an "OTA Update". This is because by flashing the modified boot.img file directly, there is not a stock boot.img backup that Magisk needs to partially uninstall itself which is step 1 when taking a OTA update. Therefore people are going to be forced to either reflash the stock boot.img and then go through the normal Magisk installation process (which will create a stock boot.img file for future use) and then follow the normal OTA update process (https://topjohnwu.github.io/Magisk/tutorials.html), or they will have to flash the stock boot.img file manually when they want to take their first OTA update and then flash the modified boot.img file again after the OTA is installed in order to gain root again. Personally I think it is just easier to go through the normal Magisk installation - which I highly recommend so you don't have this issue the next OTA update.

Either way, by using these modified boot.img files, users are going to find the OTA update process harder than necessary and none of the "normal" Magisk OTA update procedures are going to work.

 

[12paq]

@sic0048
Good points.
However, none of this is really hard. It's all just fun. Especially experimenting with different ways to do things and figuring out how to get it done in a way that's best for each us at the moment. ???

 

[sic0048]

@sic0048
Good points.
However, none of this is really hard. It's all just fun. Especially experimenting with different ways to do things and figuring out how to get it done in a way that's best for each us at the moment. ?

Agreed - and I'm not trying to call anyone out for providing or using the modified boot.img files. Heck, I used them initially myself. But I do want people to understand why the OTA update process is going to be different if they use the modified files.

 

[sd_N]

Did you try to fastboot pie factory images? That should get you back to pie, kinda weird if not.

Yes, I tried...never worked. But today I got the Q Beta 4 update with June patch and it OTA'd just fine. The Google rep said it would and she also said I can now opt out of Q Beta and should get back to Pie that way. I haven't done it yet, cause this Q Beta 4 has been fast and sweet so far.

 

[pbanj]

Agreed - and I'm not trying to call anyone out for providing or using the modified boot.img files. Heck, I used them initially myself. But I do want people to understand why the OTA update process is going to be different if they use the modified files.

thats why i made a little guide for updating and added it to my post. just sideload the ota with adb, use the reboot into bootloader option then flash the new boot image to the new active slot

 

[alliance1975]

The "issue" is the fact that users have supplied these "modified boot.img" files and others are using them to install Magisk in an unconventional way. I realize they are doing it in an attempt to be helpful and speed up the root process and it does make it easier for the initial installation. But using these files is actually making it harder to take an "OTA Update". This is because by flashing the modified boot.img file directly, there is not a stock boot.img backup that Magisk needs to partially uninstall itself which is step 1 when taking a OTA update. Therefore people are going to be forced to either reflash the stock boot.img and then go through the normal Magisk installation process (which will create a stock boot.img file for future use) and then follow the normal OTA update process (https://topjohnwu.github.io/Magisk/tutorials.html), or they will have to flash the stock boot.img file manually when they want to take their first OTA update and then flash the modified boot.img file again after the OTA is installed in order to gain root again. Personally I think it is just easier to go through the normal Magisk installation - which I highly recommend so you don't have this issue the next OTA update.

Either way, by using these modified boot.img files, users are going to find the OTA update process harder than necessary and none of the "normal" Magisk OTA update procedures are going to work.

@sic0048
I have a 3a phone. It has been unlocked and was rooted via pbanj's how to root procedure. So the patched boot image has been installed to slot a.
I would like to use the normal Magisk installation you described above for subsequent OTA updates. I downloaded the stock March boot image and the June OTA. Can you please provide a procedure for getting to the normal Magisk install?

 

[sic0048]

@sic0048
I have a 3a phone. It has been unlocked and was rooted via pbanj's how to root procedure. So the patched boot image has been installed to slot a.
I would like to use the normal Magisk installation you described above for subsequent OTA updates. I downloaded the stock March boot image and the June OTA. Can you please provide a procedure for getting to the normal Magisk install?

Yes, you can just follow the normal Magisk installation steps. They have always worked with the 3a/3a XL models.

That is you allow Magisk to modify the stock boot image and then manually flash that modified boot image. But going through that extra step of having Magisk modify the stock image allows Magisk to be aware of the stock boot image location and therefore you can follow the normal Magisk "OTA update" procedures. Those update procedures will fail if you simply flashed the modified image.

 

[Rudi154]

[deleted]