yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
I updated 5 devices to 19.1 (P3 stock, P3XL running dotOS, 2 Huawei Mate SEs running Oreo and a Samsung Galaxy Tab S2 SM-T713 on Nougat) last night all using direct method. The Pixels were coming from 19.0 beta, and the others all were coming from 18.1 stable. No issues on any of them running Manager install from the notification and then opening after complete and updating Magisk from there. 19 was already running root processes much faster on boot than 18.1 and 19.1 is doing even better. The one thing to remember if coming from anything before 19.0, the Magisk Hide check marks need rechecked.
[Google Pixel 3 Guides, News, & Discussion] 93Akkord:
When you guys say update via 'direct method', what do you mean?

I'm currently running 18.1, but I'm afraid to update via the Magisk Manager app. Got a bootloop when I originally installed.
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Direct method is through the app. Alternately you can install the magisk zip with twrp. I've not had an issue using the app.
[Google Pixel 3 Guides, News, & Discussion] 93Akkord:
Thanks for the clarification! Just updated through the app and everything went fine.
[Google Pixel 3 Guides, News, & Discussion] abracadabra11:
I downloaded the latest factory image for blueline and extracted the boot.img file and then used Magisk Manager to patch the file. The process was successful, but there's a significant size difference between the stock boot image (64MB) and the patched boot image (29MB). Is this normal?
[Google Pixel 3 Guides, News, & Discussion] CSX321:
It is normal, however I was getting a bootloop by doing it that way with the May update, even though that's always how I did it before. I don't know why, but this time I had to actually install TWRP and flash Magisk from there to get it to work.
[Google Pixel 3 Guides, News, & Discussion] abracadabra11:
I'd like to stay away from having to unlock the bootloader on this device. Can I just reflash stock boot image of it boot loops?
[Google Pixel 3 Guides, News, & Discussion] CSX321:
That's what I did.
[Google Pixel 3 Guides, News, & Discussion] 93Akkord:
Updated to Magisk Manager 7.2.0 and Magisk 19.2 this morning through the app (direct install). Everything went fine for me.

One thing I noticed, which could be unrelated, is that Night mode in the developer options was switch from always on to always off for me. Had to switch it back.
[Google Pixel 3 Guides, News, & Discussion] frakk_2000:
OTA update issue Pixel 3

Hi, I have a Pixel 3 with Magisk, no TWRP. Magisk just upgraded to the most recent version 19.2 as well as Magisk Manager to 7.2.0

Magisk + root were added when I have got the phone anew in March 2019.

I wanted to follow the Tutorial OTA Installation to upgrade to the most recent patch level.

Currently I have the March update (PQ2A.190305.002).

Automatic system updates is OFF.

In Magisk Manager, I choose Uninstall - Restore Images.

After that, I should be unrooted, and I should be able to download the most recent OTA as normal.

However, I am rooted, and, not surprisingly then, System update tells me '"Your system is up to date".

Any idea how to bring this to work. I don't have TWRP, I only want to do it with Magisk.

I think downloading the most recent OTA extracting the boot.img file, patch it, and then send it back (to both A and B slots?) should work, but I hoped for a method with less stress. (This process is identical to the first installation of Magisk + root, I thought I don't need to repeat all steps for an OTA update?).

Thanks,

frakk
[Google Pixel 3 Guides, News, & Discussion] jd1639:
You're not going to be able to do it with just magisk. Easiest way is to get the full factory image, edit the flash-all batch file to remove the -w you'll find in there. Then run the batch file. Afterwards you'll be updated and have the stock boot image. If you want root you'll have to do that thru twrp.
[Google Pixel 3 Guides, News, & Discussion] frakk_2000:
Hey jd1639, thanks for looking into this. Are you sure TWRP is a must? There are many reports out there confirming perfect root with Magisk only. Actually, I can confirm this too from my end.

topjohnwu's tutorial for OTA installation process ( https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 ) explains it quite well, it all makes sense, all sounds really straightforward. The flash.bat -w method may also work, but this is very similar to the manual boot.img processing (patch wih Magisk and then flash the patched image simply with adb, no TWRP or whatsoever) and the method from the tutorial is more elegant.

My problem is that in Magisk, Restore images is supposed to bring me back to unrooted status (and in turn, ready to receive the OTA as normal), but in reality, my rooted status is not changed at all (and I am not able to receive the OTA because of that).

I have the vague impression that the method described by topjohnwu assumes that one of the two slots (A or B) would contain the original boot image, which I could restore, but I may have the same (patched) image in BOTH slots, so Restore image in Magisk does nothing practically.

Am I missing something?
[Google Pixel 3 Guides, News, & Discussion] misslebulletttttt:
does anyone know whether magisk support the android-q preview for pixel 3, it seems to be a hurdle to root pixel 3 with q-preview, JohnWu tweeted that

it's coming, yet know how it was coming along ??
[Google Pixel 3 Guides, News, & Discussion] vonDubenshire:
He tweeted today he's getting it working all the way
[Google Pixel 3 Guides, News, & Discussion] Xdevillived666:
It is now
[Google Pixel 3 Guides, News, & Discussion] sk1rge:
Hey guys, Magisk 19.3 is not supposed to work with the July update, correct?
[Google Pixel 3 Guides, News, & Discussion] CSX321:
It works fine for me.
[Google Pixel 3 Guides, News, & Discussion] sk1rge:
Thanks, that was quick :)

Uninstalled (uninstaller script) and reinstalled Magisk, now it works.
[Google Pixel 3 Guides, News, & Discussion] rczrider:
Anyone having trouble with latest Magisk (19.3) and the latest ROM (July security patch)? I can successfully flash Magisk by booting (not installing) TWRP and flashing it there, but I get stuck when there's one unsuccessful boot attempt, a restart, and I end up in Android Recovery with the "Can't load Android system" message and the only options of trying again or doing a factory reset.

I can restore to stock using fastboot commands and removing the "-w" flag keeps my data intact, but no matter what I do, I can't seem to get Magisk to work with the latest factory image. I've tried flashing in a different slot and in both slots. Same problem.

I've also tried extracting the boot IMG and patching it via Magisk Manager (Install > Select and Patch a File), but I get a "unsupported/unknown image format" message and the installation fails. I've downloaded the files from Google again just in case it's corrupt, but no dice.

Thoughts? I feel like I'm missing something obvious.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I had something similar happen a couple of months ago. Try running the Magisk uninstaller, then actually install TWRP using the ramdisk method, then install Magisk again from within TWRP. Once I'd done that, it fixed whatever the problem was, and I've been able to go back to my normal update procedure since then.
[Google Pixel 3 Guides, News, & Discussion] rczrider:
Thanks for the suggestion. I'll give it a shot tomorrow and see if that takes care of it. I really haven't been keeping up with things, so I wasn't even aware of the direct install / ramdisk option available in TWRP 3.3.0+.

Nor did it occur to me to run the Magisk Uninstaller prior to re-rooting, though I can (sort of) see how that might be helpful since I'm not doing a data wipe. I saw a suggestion in a crosshatch thread about uninstalling Magisk Manager, too, just in case.

I'll report back with the steps and results. Thanks again!
[Google Pixel 3 Guides, News, & Discussion] CSX321:
It normally isn't necessary to uninstall either one, and I haven't needed to since, but then it was the only way I was able to recover from whatever was wrong. Back then I had switched channels several times, between release, beta, and canary, so I probably messed something up at some point.
[Google Pixel 3 Guides, News, & Discussion] rczrider:
Well, whatever caused it, you were right! I don't know if all of the steps were necessary, but here's what I did and it worked:

uninstall the Magisk Manager app

reboot to recovery

boot TWRP IMG via fastboot

flash Magisk Uninstaller ZIP

wipe Dalvik

flash Magisk ZIP

wipe Dalvik

reboot system (did not install TWRP)

Thanks and repped!
[Google Pixel 3 Guides, News, & Discussion] bmw9651:
I used TWRP and Magisk on my Pixel 3 with success. Magisk 19.0 TWRP 3.2.0.
[Google Pixel 3 Guides, News, & Discussion] vonDubenshire:
I've stopped using TWRP because I don't do much that needs it, and as of now we don't know how to make it work with Q.

It is so ridiculously easy to just flash the magisk patched boot -- install a kernel that went wrong and in a boot loop? Just flash it on to your phone again. And you can even do it within Android if you don't ahve a reboot problem

it's just great
[Google Pixel 3 Guides, News, & Discussion] georgs_town:
Hey peops

After the March Update, I didn't bother updating my P3, because that command-line stuff always gave me sweaty palms ;)

Now with the release of Android 10, that is of course another story. I would love to update, but want to keep root (YT Vanced, Adaway, Active Edge). Last time I updated, I did it following the step-by-step instructions of CSX321.

Can I do that with the Android 10 Version? Or do I have to wait for a new Magisk-Version? Thanks for your replies!
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I'd like to know, too! :) I'm 10 time zones away from home right now and don't have a computer. I'm hoping someone has tried it by the time I get back. I suspect the Active Edge module will need to be disabled and updated for Android 10, because it patches a system file or something, doesn't it?

I did see that [MENTION=4609886]sliding_billy[/MENTION] said he installed the 10 update just as if it were any other monthly update, and was still able to root it, but he didn't say how he installed Magisk.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
I installed the canary manager build (no debug installed from APK) the day before and had it completely running on the canary channel where it took a build of Magisk . When the Android 10 build came out, I installed with flash-all (minus -w). I rooted with patched boot.img. This phone (my P3) does not have Active Edge installed, but yes I would absolutely disable that module and not enable until there was a known working version. I might not even be comfortable then without a working TWRP to use the Magisk uninstaller if you get looped. I am using a custom ROM on the 3 XL, so no Active Edge module there (or 10 yet) either.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Thanks for the info! P.S. Get some sleep! Isn't it 1:30am there?!?
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
It is, but it's a new day. I slept for a few hours and woke back up at 2330. Good for another 18 hours
[Google Pixel 3 Guides, News, & Discussion] linqdesires:
I extracted the boot.img from a10 stock image, patched through MManager Canary, flashed with fastboot:

fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img

A10 is booting correctly and MMC says Magisk is installed.

For Adaway to work now you need to enable the systemless module in Magisk settings.

Reboot.

Enable adaway block.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
FYI about Active Edge.

https://xdaforums.com/showpost.php?p=80180160&postcount=176
[Google Pixel 3 Guides, News, & Discussion] acidspider:
Ok so I upgraded to android 10 all well and good and rooted but then went and install a magisk module I shouldnt of and it out me in bootloop, I managed to boot again but lost root, now every time I try to root it bootloops because of the previously install modules, how do I start fresh magisk without a full wipe?
[Google Pixel 3 Guides, News, & Discussion] georgs_town:
Hey guys, I'm getting closer to really wanting to update! One guy over in the Android 10 Root thread posted this very interesting and easy method and said it worked for him:

https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

any experiences with that? It sounds really tempting...

One thing I don't really get is the whole Magisk Canary story: can somebody try and explain it to a dummy?

Also in the xda thread for magisk canary it says, it's for developers only, unstable and whatnot.

How would I change from my current Magisk to Magisk Canary (it seems I would have to do that with any update-method...)

Cheers
[Google Pixel 3 Guides, News, & Discussion] coachmarino:
I went through this process:

- Uninstalled Magisk

- A10 factory image

- Download and Installed Canary build of Magisk

- Installed and patched boot.img

...you know the method

So now everything says it's working, but it's not. I can't install modules (says Magisk is not activated).

I do have root though. I can give superuser access, I can access root files, but I can't edit. For example I can't edit build.prop. I can see it, I can open it in the editor, but then it won't save.

Not sure what I'm doing wrong...
[Google Pixel 3 Guides, News, & Discussion] georgs_town:
Update: I went through with the process described under the link above. It worked like a charm, this is by far the easiest Update-process I've come across so far on my Pixel 3. I switched to Magisk Canary Build before updating.
[Google Pixel 3 Guides, News, & Discussion] hovah51:
Hmm I'm not lucky as I did this method and on reboot I got a message telling me impossible load the system and that my data are corrupted. I have to do factory reset :(
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I'm home from my trip, and I got everything updated successfully without much drama. The most painful part was that I was using an oldish version of Lawnchair v2 as a launcher, it didn't work with A10, and updating it meant setting up the icons and widgets on my homescreen again. I installed the updated Edge Sense Plus module, and everything is working normally, including Pay.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
Good deal. Not sure if you are aware, but Lawnchair v2 is now on the Play Store in beta and is getting regular updates. https://play.google.com/store/apps/details?id=ch.deletescape.lawnchair.plah&hl=en I have it installed on Pixel 3 running 10 and 3 XL running 9 (Havoc). It is running great. I had been running an older version of v2 direct from them but quit using it since it was still buggy.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Yep, that's what I switched to.

I may have spoken too soon about everything working. Wi-Fi has been acting very flakey. Sometimes it won't connect to my normal home and work networks, and when it does it's slow. :-/ I'm thinking about flashing the old radio from A9, like I used to have to do in the old days when certain radio versions worked better on my first Android phone, an LG Optimus. I guess we can still do that, can't we, or is the radio signed or something so that it only works with the build it's part of?

I also am wondering about the 19 vs. 20 builds. Did we ever figure out what the difference is? I flashed the 20 version, but maybe it's for Verizon, and that's not what I have. It would maybe make sense for there to be a radio difference.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
I'm pretty sure there is no signature that compares radio to the build, but whether it will help is anyone's guess.

As for the .19 vs .20 question, the difference is anyone's guess. Until someone quotes a real source instead of just sounding authoritative, it will be just that. When the update first hit, it was stated in a very authoritative manner that .19 was for folks updating from beta to public and .20 for 9>10 updates. Very recently, the exact opposite has been claimed in a very authoritative post. I have been of the opinion since the beginning that it is carrier specific and in no way related to beta. Since Google is now tailoring the builds to multiple carriers, it is likely a bunch of waste code that only works on certain devices but is different than the carrier agnostic version (which has always been the lowest numbered one). I compared .19 and .20 for the 3XL, and the radio is certainly different. That makes zero sense if the logic has to do with 9>10 vs beta>public. No matter what, the radio difference would not be there when updating from beta>public. It is a single file in the package that wouldn't care what method you were updating with. It would flash it and be done with it. The difference being carrier related makes perfect sense.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I just flashed the entire 19 version (not only radio) without -w, so we'll see what happens with that. Seems fine so far, but the Wi-Fi problems were worse at home and on another network I admin. It's working okay so far here at work. Says it's got a 400Mbps connection, anyway.

Edit...Well, that didn't help at home. Wi-Fi keeps disconnecting, only running at 2Mbps, etc., while all other devices are still fine. So, I just flashed the radio from the August update, and--Hey Presto!--back to normal full-speed Wi-Fi. I suspect it's an artifact of dirty flashing A10, and that it might be fixed by doing a network reset in Settings. But I really don't want to lose my networks and Bluetooth device pairings ATM, because I have quite a few. If this continues to work, I can live with using the old radio for the time being.
[Google Pixel 3 Guides, News, & Discussion] georgs_town:
Sad to hear! Did you uninstall all the Module in Magisk beforehand? especially Edge Sense Plus?!
[Google Pixel 3 Guides, News, & Discussion] hovah51:
I still had Youtube Vanced from Magisk installed. I never installed Edge Sense Plus.

I don't know if vanced cause the problem.

Thanks to google back up it's not that bad. Only problem now, my RCS is stuck at "configuration".. but it's another problem :)

Thanks
[Google Pixel 3 Guides, News, & Discussion] CSX321:
[MENTION=4609886]sliding_billy[/MENTION], or anyone else who updated to A10 without -w, does your Play Store say the device is certified? I've cleared the data for it several times, both through Settings and from the command line ("pm clear" command for the package), waited 24 hours or more, and it still doesn't say certified. I guess it's not a huge problem. It really only affects the Netflix app for me, which I use for checking whether things are available more than actually watching on the phone.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
glitch
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
It takes a little work sometimes. If clearing cache and data doesn't do it, go to the Play Store application page in settings and (after clearing cache and data for the app) delete updates from the hamburger to return it to "factory." That will take it back to whichever version was on it at the "beginning." I believe that will be the version when you took Android 10. The update should happen pretty quick, but you can force it by going to Play Store settings and clicking the build number at the bottom. If there is a new version, it will queue it up. Updating is what triggers a certification check.

As for Netflix, I assume you already have it on the device since certified or not it will not show in the Play Store on a BL unlocked Pixel 3. The last version on APK Mirror works for sideload.

P.S. Be sure to hide the Play Store in Magisk Hide before starting all this.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Hmm, when I hide the Play Store it will only hide the main package. If I try to hide the other services under the Play Store, it doesn't stick. Is that normal?
[Google Pixel 3 Guides, News, & Discussion] acidspider:
Has anyone managed to get the sky go app working with root and magisk?
[Google Pixel 3 Guides, News, & Discussion] deprito:
anyone having issue when boot TWRP with magisk installed?

i'm on QO1A.190711.020 with september 5th security update.

i have do patch twrp.img with magisk, but no positive results.

i have boot only twrp.img with adb, but still no luck.

Any suggestion for me to install TWRP?

MAGISK :

> 19.4-f383d11d (19309)

> 7.3.3-f383d11d (234)

Thanks.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
TWRP is not compatible with Android 10 yet. I have no idea what you are talking about patching twrp.img You patch stock boot.img with canary Magisk and then flash it. Start by reading the guide carefully.

Also, there is no need to double post. I replied to your post in the TWRP thread as well. https://xdaforums.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Hey! After I updated to the latest canary this morning, suddenly Netflix showed up in Play and updated itself. At first the listing said it wasn't compatible with my device, although it updated and runs fine, but now that message is gone and everything looks completely normal. :) Play settings still doesn't say the device is certified, but maybe it is and they did away with the message.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
Not sure what you are seeing or why. I just checked my 3XL and my wife's 3. I did the canary update on both early this morning. Both devices already have Netflix on them. Hers updated from an actual Play Store install until the unlocked Pixels disappeared and quit updating and the device has never been wiped so that version just stays there. Mine has a sideloaded APK Mirror version. Neither one showed an update in store, the app doesn't show in installed or library. I checked the PC store, and both show installed but show "your device is incompatible" and no devices available to install. It would be really funny if it was a certified issue. Both of my devices are certified and on the newest Play Store version which is hidden. Did you uninstall updates to Play Store? Are you possibly on a really old version of Play Store that hasn't updated and certified? I actually pondered that in the Netflix thread a while back if someone wanted to revert their Play Store version to before they started blocking unlocked Pixels. Since I have it working on all of my devices, I am hesitant to play around too much with Play Store versions or uninstall Netflix.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I did a while back, but it's almost back up-to-date now, on the Sept. 10 version of the Play Store. I don't know how I got to this state, but it's a desirable state, so I won't argue with it. :) It happened immediately after I installed the new canary update, so it seems likely to be related.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
How did you install the new canary build? I just took the inline update in MM.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Same
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
Crazy. Maybe just a fluke of timing somehow.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I've been hoping to have the dark mode Play Store option show up, but I haven't seen it on my device yet.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
I'd be happy with dark Gmail on my 3XL.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Edit:

/data/data/com.google.android.gm/shared_prefs/FlagPrefs.xml​

and change this to "true" (it was the first line in mine):

<boolean name="DarkThemeSupport__dark_theme_support" value="false" />​

Then force close Gmail and restart it, and you can pick the dark theme in its settings.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
Tried it when it first got posted. Does nothing. I think it is server side by user.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Ah. Bummer.