yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a Guides, News, & Discussion] rum-z:
I'm currently rooted on Andorid 9. I used the method 1. Is it possible to follow Magisk OTA tutorial to take an OTA to the android q beta and keep root? I"m running magisk canary
[Google Pixel 3a Guides, News, & Discussion] sterrix:
Hello guys,

I'm rooted using Method 2 before TWRP was available and now I'm on the June patch. Can I ask, is it safe for me to just install TWRP and proceed to update OTA? I want to have access to TWRP on my phone.

Or do I have to unroot, install TWRP and root by flashing magisk?

Whatever steps I take, I do not have to wipe my data right?

Thanks in advance!
[Google Pixel 3a Guides, News, & Discussion] sic0048:
First, be sure you understand how TWRP works with our phones right now. Unless you run a custom kernel, you cannot install TWRP. Instead you have to boot into it using your computer anytime you want to use it. Therefore you can boot into it, flash things or make a backup, and not permanently effect the phone. Therefore it should have zero repercussions when taking an OTA because there won't be any remnants of TWRP on the phone to effect the OTA.

If you obtained root via #2, then Magisk should restore the stock kernel when you "uninstall" it as part of the OTA update process.

If you decide to run a custom kernel, then you will need to restore the stock kernel before taking an OTA. If you have TWRP permanently installed, you won't be able to boot into it while you are running to stock kernel. You should have access to the bootloader (if you run into issues and need to flash something), but not the recovery.
[Google Pixel 3a Guides, News, & Discussion] sterrix:
I'm running ElementalX right now with LZMA support. However, you're suggesting I should consider using TWRP using the fastboot method instead of permanently installing it into my phone. Mmm. TWRP not affecting the OTA does seem very convenient.

Is it possible to re-root my phone using Method 1? To do so, I have to uninstall Magisk through Magisk Manager before I can start the re-root process using stock images, am I right to say that?

Thanks for your help!
[Google Pixel 3a Guides, News, & Discussion] sic0048:
I also run ElementalX and have TWRP permanently installed. The truth is that I rarely find a need to use TWRP with a Pixel device. I don't run a custom ROM, so I don't find a lot of benefit in backing up my OS, nor do we need to use TWRP to flash updates, etc. Titanium Backup gives me backups of my apps and the OS is easily replaced/flashed should I get into trouble. If I ever run into issues and have to reflash everything, I might not actually install TWRP again and just boot into it if/when needed.

I don't think you need to worry about reinstalling Magisk. But you shouldn't need to uninstall Magisk before you flash it again in TWRP if you feel the need to do so. Of course if you run into some issues with Magisk (and sometimes it happens), then you can always flash the Magisk Unistaller zip using TWRP and then flash the Magisk Installer to regain root (ie I would uninstall it via the zip instead of using the Magisk app just to make sure everything got removed properly).
[Google Pixel 3a Guides, News, & Discussion] duh1:
Received my first OTA update request from the system this month, and was a bit surprised to have received it. I was under the impression that if you have modified the system partition in any way, that would make your phone ineligible for an OTA update. Since I did modify that early on, and did not receive OTA updates for June and July, I figured at some point I would have to sideload one.

Perhaps since this is an a/b device, Google services has been updated to ignore modified systems and now pushes OTA updates whatever the state of that partition.

With the most recent OTA update, has anyone tried to do that update with a modified system or even while still rooted and not received a tamper block verification error as mentioned in the Magisk OTA update guide? Should I reflash the boot (to unroot) and system (to unmodify) images before attempting the OTA update?

Also changed is that turning off system updates in developer options no longer prevents the OTA update from downloading and being installed to the inactive slot. All that now seems to be required is hitting that system restart to update button which will probably just sets the inactive slot to be active on reboot.

It looks like that Magisk OTA update guide is now obsolete for a/b devices, or at least Pixel devices. So how does this change the OTA procedure? Still unroot or not? Unmodified system matters or not? Should I install Magisk to the inactive slot before or after clicking the restart to update button now sitting in my settings app?

If any users have this already figured out, would appreciate the info -- thx...
[Google Pixel 3a Guides, News, & Discussion] AlPoo:
So, i'm in trouble here.

Followed OP, used method 2 to intsall magisk.

unzipped the boot image, loaded it to p3axl. had magisk patch it. then flashed it to my current boot slot.

rebooted to no command and then after a few reboots, im on a white g boot loop.

any idea how i can get out of this? stock or actually install magisk i dont mind which.

edit; was on latest beta
[Google Pixel 3a Guides, News, & Discussion] pbanj:
few issues here. one those are pie boot images, and 2 this is a thread for the 3a not the xl. you wouldnt happen to be the person from reddit would you?
[Google Pixel 3a Guides, News, & Discussion] pbanj:
i took the aug update following the magisk guide and it worked just fine. i did have to reboot and then start the guide as when i tried doing it after i noticed there was an update it wouldnt even start. but reinstalling magisk, rebooting, then restoring the stock image allowed it to update just fine. i will say though, sideloading the update is waaaaaaaaaaay faster like 3-4x faster
[Google Pixel 3a Guides, News, & Discussion] sic0048:
Are you using the latest Canary version of Magisk? You must use the Canary version if you are trying to root on any of the Android 10/Q releases. I suspect you are on the normal "stable" version and this this is why it isn't working - or you downloaded the zip for the 3a OS and not the 3a XL because the boot.img file is different between the two phones.

Normally I would say to boot into TWRP, flash the Magisk removal zip tool to remove all aspects of Magisk, and then flash the latest Canary version to get your phone working again, but TWRP doesn't work on the 10/Q releases yet either.

I think you are going to be forced to reflash the Android 10/Q beta release again and then download the Canary build using the Magisk app and changing the "Update Channel" under settings to Canary. Then follow the instructions to root the phone, but make sure you download and unzip the correct boot.img file for your phone and OS version.

But if that doesn't work for some reason, then you will have to go the full nuclear option which would be to flash your phone with a Pie release, upgrade your Magisk to the Canary releases and then reinstall the beta.
[Google Pixel 3a Guides, News, & Discussion] duh1:
A bit confused by what you say happened in your case -- you saw you had an OTA update, button said to restart to finalize installation, and you following the guide used the Manager to uninstall Magisk before rebooting and the device then wouldn't boot, or did you simply hit the OTA update restart button without uninstalling Magisk and the device wouldn't boot? Did you receive an error message at any time? Thx...
[Google Pixel 3a Guides, News, & Discussion] pbanj:
well i figured it would be like my wife's phone and if it found the update it would ask if i wanted to install. so i went to check but it was already in the middle of trying to download it or some ****. so i backed out, closed settings and went and told magisk to restore the image. then i went back into settings to see if it would work. it still just sat at the same ****. so i had magisk reinstall itself, and then rebooted. after it rebooted i immediately opened magisk manager and had it restore the image, then i went into settings and then into system update. this time it worked. but god did it take forever, like i would say it took 30+min to finish, i then had magisk install itself in the other slot and rebooted. i dont think ill ever be doing it that way again as it took way longer than sideloading the update and flashing the new boot image, that takes like maybe 10min. hopefully that cleared everything up
[Google Pixel 3a Guides, News, & Discussion] crackedvenom2:
Could at least make the images for people like me who did everything correct but the stupid phone just bootloops every time. Guess I'll go back to an old version then. Oh well.

E: Canary works. Should maybe put that in the OP so people know one might not work.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
Are you on pie? Because stable Magisk should work just fine on pie
[Google Pixel 3a Guides, News, & Discussion] duh1:
Yeah, I see what you did there -- as I mentioned in my earlier post, Google has changed their OTA update procedure, at least for the Pixels. Even if you have Auto updates turned off in Developer options, the OTA update will still download in the background and install itself to the inactive slot, it just won't restart the device without your permission. It seems like Google no longer cares about the tamper block verification on these a/b devices, so no checks are run on boot or system before the installation.

You interrupted that download and pushed it back to the beginning of that installation process. That's what probably took so long, as the download and hash check in the background is much slower than a direct download. However if you had let it finish, you would have seen the restart button under system updates which would have set the inactive slot with the newly installed system to be active.

Before you click that button, you would simply go into the Manager and install Magisk to the inactive slot, then click the restart and you should be rooted under the new update. No restoration of the boot image would need take place on your system beforehand, and in fact when the update is completed, the inactive slot contains your previous rooted system.

We are looking for further confirmation to make sure this is the case, as it would make future OTA updates much easier...
[Google Pixel 3a Guides, News, & Discussion] pbanj:
I'm pretty sure what I interrupted was the varefication step as there was no progress bar. Also the download was the fastest part, what took forever was the optimizing apps portion it was doing before it got to telling me to reboot
[Google Pixel 3a Guides, News, & Discussion] musiv2:
Does this method work on Verizon variant?
[Google Pixel 3a Guides, News, & Discussion] sic0048:
No. You cannot unlock the bootloader on the Verizon variant and therefore it cannot be rooted currently. It will take some sort of exploit to root. There may never be a root method for the Verizon model.
[Google Pixel 3a Guides, News, & Discussion] Zrbtfm:
Android Q is here... Enjoy
[Google Pixel 3a Guides, News, & Discussion] pbanj:
ok i added stock images for both of the android q updates. i also added a pre patched image for it and the magisk manager the user said to use it with. only reason i provided the patched one is because some users had issues patching their own. if you don't like it you know where to put your opinion.
[Google Pixel 3a Guides, News, & Discussion] Dixon Butz:
Good timing.

I patched my boot.img with canary build. Flashed it and it didn't root.

So I used that pre-patched img. Got root. Grassyass
[Google Pixel 3a Guides, News, & Discussion] pbanj:
np. not sure why some are having issues and some aren't.
[Google Pixel 3a Guides, News, & Discussion] Dixon Butz:
Always worked for me before. I didn't feel like trying again. I am sure I did it correctly.
[Google Pixel 3a Guides, News, & Discussion] mike9976:
Could some one tell me how to turn bubbles on thx
[Google Pixel 3a Guides, News, & Discussion] HpNoTiQ:
I've updated to Q but without uninstalling some module and now I'm in a bootloop if i flash magisk.

Would you update it to last boot image for Q (Booting with old one doesn't work and TWRP can't mount data/system on Q.)

Thanks in advance,
[Google Pixel 3a Guides, News, & Discussion] alliance1975:
Thanks [MENTION=4396787]pbanj[/MENTION]. I screwed up and couldn't install magisk onto 10. I did a factory wipe and followed your instructions from op and now have root.
[Google Pixel 3a Guides, News, & Discussion] bonfire62:
Just FYI, I had a problem with TWRP where it wouldnt see any of the files on 10(Q). I had to download the boot.img, patch it with canary magisk (19.4 i think), boot using that boot img, then install magisk directly. Have root again :)
[Google Pixel 3a Guides, News, & Discussion] sic0048:
TWRP doesn't work with Android 10 yet.
[Google Pixel 3a Guides, News, & Discussion] HpNoTiQ:
Indeed, I updated with OTA and now I can't delete magisk modules which are causing bootloop....
[Google Pixel 3a Guides, News, & Discussion] Dixon Butz:
Dev options
[Google Pixel 3a Guides, News, & Discussion] mike9976:
Thx friend i turned that on i don't think it works without adb does it
[Google Pixel 3a Guides, News, & Discussion] Dixon Butz:
I am not sure. I have not tried it yet.
[Google Pixel 3a Guides, News, & Discussion] bonfire62:
Was having huge slowdown and app crashes after installing through booted magisk install, did a wipe and clean install and it worked great
[Google Pixel 3a Guides, News, & Discussion] omiCar:
Can you elaborate? I have the same issue, I have already installed Magiskv19.3 while on Pie; updated to Andriod 10 yesterday, now I can flash the MagiskUninstaller from TWRP because it does not show any of my data/files. Do I need to revert back to Pie and then install The Canary Version of Magisk from there?
[Google Pixel 3a Guides, News, & Discussion] HpNoTiQ:
Bad idea to revert back to PIE (dirty flash). You're now stock to Q without root until someone release TWRP or magisk boot image core only with september q update.
[Google Pixel 3a Guides, News, & Discussion] reyqn:
Isn't there a way to patch a boot.img with magisk core only instead of regular magisk?
[Google Pixel 3a Guides, News, & Discussion] sic0048:
You don't want to "dirty flash" Pie, but there is zero issues with flashing the full factory Pie image that is available from Google. This will do a full wipe and factory reset the phone (erasing all files/pictures/texts stored on the phone) so be sure to backup any important data off phone prior flashing.

Of course the latest Pie version is going to be an older security update and won't be updated in the future, so the longer we are on Android 10 the less attractive going back to Pie will be. But no one is "stuck" on Android 10. If you can't live without TWRP, then by all means feel free to switch back to Pie for the time being.

If for some reason a person wants to be on Android 10, but cannot root correctly for some reason due to a previous Magisk installation causing issues, a person can simply flash the full factory Android 10 image from Google which again will factory reset the phone and will erase all remnants of an older Magisk installation. Then the person should be able to reinstall Magisk using the Canary Magisk Manager App and the modified boot image installation method. In other words, there is no reason to go back to Pie just to turn around and flash Android 10 again.

Edit - actually theoretically the Pie installation is still on a person's phone that has upgraded to Android 10. It is simply installed on the other partition. You should be able to use ADB to boot into the other partition and have your Pie installation back. I haven't personally tried this, so I cannot be 100% that it will work, but it should. This means you don't even have to flash the Pie image to go back to Pie. As noted below, this option is not available. Once you successfully boot into a partition, the rollback protection kicks in and prevents you from booting into the non-active partition.
[Google Pixel 3a Guides, News, & Discussion] HpNoTiQ:
Yes but that means backup and restore without root which is a long way.

I'll try to compile magisk at home and change the check for cache/.disable_magisk to /persist/cache/.disable_magisk (which is accessible unencrypted in TWRP https://github.com/topjohnwu/Magisk/issues/1286).

Moreover, on a/b device, you can't boot to other slot after the first successfull boot on the updated partition.
[Google Pixel 3a Guides, News, & Discussion] reyqn:
Nice thinking :D I couldn't wait anymore so I tried it out and it worked like a charm!

As said before, just create a file named .disable_magisk in /persist/cache/ and fastboot flash boot with this pre-patched img.

You should be able to boot, disable your modules and patch again the real magisk!

Apparently I can't post link to files in here so here it is

mega(dot)nz/

and the key is

#!1k0DTQYD!MguIhzP2fkNtLeGe2JolVt4dFnDQQgjtlrRdNtoOMvU

Edit: the boot.img is for qp1a.190711.020, not sure it works with qp1a.190711.019 but you could give it a go I guess.
[Google Pixel 3a Guides, News, & Discussion] PowerUser64:
I updated to android 10 (qp1a.190711.019), lost root, and now I can't boot my own Magisk Canary-patched boot.img, or any other patched boot.img files (ex: the one in the first post in the part about android q) without a boot loop. Is there any way for me to root on android q right now, or do I have to wait for an update to the magisk boot.img patcher to get root? (Or does anybody have a patched boot.img that might work for me?)
[Google Pixel 3a Guides, News, & Discussion] HpNoTiQ:
Thanks, I thought EdXposed was working on Q...

Now, I'm back!
[Google Pixel 3a Guides, News, & Discussion] spiou:
Like in August, still no luck to ota update with the Magisk procedure :

1) restore stock boot img

2) apply system ota : download, and then install but it finished with "installation problem" message

I don't understand why it failed, obviously many people succeeded

I just have Magisk installed and 2 modules (systemless hosts and YouTube Vanced), nothing more.

I tried to disable the 2 modules of Magisk before restoring boot, but still no luck.

I know how to update with sideload comand, but I really would like to update with this easy Magisk procedure.

Any idea what could be the culprit ? Is my system image tempered ? How to verify ?

Thank you for your feedback.
[Google Pixel 3a Guides, News, & Discussion] AutomaticFailure27:
Are you on the latest canary of magisk? I haven't done it yet, but I feel this could be the culprit.
[Google Pixel 3a Guides, News, & Discussion] spiou:
I am on the latest stable version. I know canary is required for Android Q : if the Q update ended successfully I planned to install the canary version to re root in the inactive slot, but it failed before. By the way for Pie, I never saw that canary was required to update the security patch.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
Awesome, I'll add it to the main post when I'm at my PC later today.
[Google Pixel 3a Guides, News, & Discussion] mdewii23:
Can't install magisk

I tried method 1 and couldn't select my storage so, I tried method 2 now I get this. No idea where I'm going wrong. Thanks for the help.
[Google Pixel 3a Guides, News, & Discussion] Tulsadiver:
Could you walk me through where and how to set this flag to always boot core-only when compiling Magisk? I have magisk.h open and I see

#define DISABLEFILE "/cache/.disable_magisk

I'm also looking in flags.h file.....

I'm wanting to be able to make boot.imgs for booting in core-only mode for bootlooping recovery reasons. I have a Pixel 3 XL.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
is your bootloader unlocked? is your fastboot up to date?
[Google Pixel 3a Guides, News, & Discussion] kodiak:
Hello.

Used this method to root my pixel (on pie) but now I want to update to android Q.

The steps are:

1 - Use the Magisk app to uninstall.

2 - Reboot

3 - Update to Q from settings

4 - Reboot

5 - Install Magisk canary

6 - Download the QP1A.190711.020 image and extract the boot.img to phone.

7 - Use magisk to prepatch the latest file and the flash this file.

Is this or am I missing something?

Will the phone be formated?

Thanks
[Google Pixel 3a Guides, News, & Discussion] HpNoTiQ:
HI,

You can do

0 change to Magisk canary build and flash it

1 uninstall magisk (restore image)

2 disable magisk module which cause bootloop in q (mainly edxposed)

3 update

4 install magisk to inactive slot

5 reboot and enjoy android q rooted
[Google Pixel 3a Guides, News, & Discussion] kodiak:
Thanks for the reply but did not quite understand the first t two steps.

Is it to install the magisk canary, reboot, use the app to uninstall (root is removed), update to q and do the other steps?

Did not quite understand the step you numbered as 1.
[Google Pixel 3a Guides, News, & Discussion] HpNoTiQ:
First, you switch magisk to canary build. (https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337).

Then you reboot after flashing.

After reboot, you disable module not yet compatible with Android Q (Edxposed will cause bootloop) and you uninstall it (https://topjohnwu.github.io/Magisk/tutorials.html).

Then, you update to OTA.

When it's finished, you don't accept reboot and go back to magisk to install to inactive partition.

When it's done you reboot and voila you are updated to Q and rooted.

---------- Post added at 10:01 AM ---------- Previous post was at 10:00 AM ----------

Canary build was updated on saturday : we won't need a modified patched image since we can disable module via adb.

https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/notes.md

Magisk (f383d11d) (19309)
Allow removing modules without root in ADB shell by magisk --remove-modules. Useful when stuck in bootloop and have access to ADB (99% of the time).
[Google Pixel 3a Guides, News, & Discussion] kodiak:
Done.

Thanks
[Google Pixel 3a Guides, News, & Discussion] pbanj:
See how that says 99%? Ya that's prob more like 75%. Don't get me wrong, it's better than nothing, but there was much better ways to help people in a bootlooped situation.
[Google Pixel 3a Guides, News, & Discussion] TheErasedChild:
Hi,

I have done something wrong and now I have several issues in my Pixel 3a. It doesn't respond to any command. Sometimes don't work vibration, sometimes don't work touchscreen, and sometimes don't work speaker (or all things in the same times). I think i have done a mistake when I have boot img. I have tried to recovery the factory img but is not a solution. The phone is totally briked.... Please, what can I do? If anyone can help me I can contribute with a snmall reward. (sorry for bad english i'm italian) Thank you at all
[Google Pixel 3a Guides, News, & Discussion] sic0048:
First off, it is highly unlikely that you have truly bricked your phone. I would suggest that you flash the full factory image directly from Google. You will find both the images and the full instructions at that link. Just make sure you flash an image for your phone (Sargo) and not another phone. You can pick a Pie or Android 10 image - whichever you want to end up with.
[Google Pixel 3a Guides, News, & Discussion] TheErasedChild:
I have done it and I have resolve the major issues, but the problem with the vibration remains. It vibrates for a half second when I power on the device in the screen with the Google logo, but when the system starts it doesn't work anymore

Nothing, I have restarted the phone for 3 or 4 times an now it works perfectly (also vibration!). I have also done the root with your metod and it works. Now I can relock the Bootloader?
[Google Pixel 3a Guides, News, & Discussion] pbanj:
NO! If you relock your bootloader you will brick your phone. Of you want to relock the bootloader you need to flash the factory image from Google and make sure everything is stock.
[Google Pixel 3a Guides, News, & Discussion] Fentadroid:
I run Android 10 with canary magisk. Any idea if I can update to the latest Canary version simply with direct install? Or should I patch again the original boot.img?