yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] gazdajezda:
Does that mean that it's now possible do an OTA update on P6 (oriole) without problem? I still have november patch (i know, old) and would like to update it to last version? I have canary 24306 Magisk installed. Would updating via Magisk OTA work? (Uninstall, flash to inactive partition, reboot...) Thankx!
[Google Pixel 6] V0latyle:
In theory, it should.

If you're concerned, simply dirty flash the factory image.
[Google Pixel 6] gazdajezda:
10x. Will try tommorow.
[Google Pixel 6] V0latyle:
I'm going to add this comment to the OP:

If you flash the patched image to both slots, Magisk will not be able to restore the factory image for OTA. This is why I have suggested booting a patched image, then using Direct Install, as Magisk will ensure an unpatched backup is retained for future restoration.
[Google Pixel 6] gazdajezda:
Nah, installing OTA via Magisk uninstall, OTA install, install Magisk to inactive slot, didn't work. Phone were booting for 20 mimutes, get hot and then i forcibly reboot it. It booted to old systrm, but I lost root. Now i will try to dirty flash april update and root via image patching...
[Google Pixel 6] lackalil:
I had the same issue. Used latest Magisk but it showed the corrupted error message when it rebooted. Flash without wipe using the flashtool worked without a hitch and is what I'll use going forward. I have a feeling it's even quicker than the OTA given how long "optimizing" takes.
[Google Pixel 6] V0latyle:
So to clarify, Canary 24306 did not work when flashing inactive slot after OTA?
[Google Pixel 6] lackalil:
Correct. Note that I disabled modules before uninstalling but forgot to unhide/restore the app. Don't know if that had anything to do with it.
[Google Pixel 6] gazdajezda:
Not in my case. I also forgot that after first restart i also get "Phone is corrupted..." message, which dissapear after old system restored. I re-rooted and will dirty flash april update later.
[Google Pixel 6] gazdajezda:
Flashtool - you mean web page controled or manual adb, fastboot commands?
[Google Pixel 6] lackalil:
The web page linked here: https://developers.google.com/android/images#oriole. Basically automates the flashing process and has a few options. You still need to use adb to boot/flash the patched boot.img.
[Google Pixel 6] V0latyle:
Usually this won't cause boot problems - it just results in loss of root.

I think you're talking about flash.android.com
[Google Pixel 6] gazdajezda:
Yes, i meant that. Thanx. I only do not understand what is master root boot image which is used for booting and then using Magisk to patch directly? Previous patched image or?
[Google Pixel 6] kariem112:
You need to get the original boot.img from the factory image. Extract it on a PC, copy it to your phone. Then patch that file with magisk.
[Google Pixel 6] V0latyle:
Yes, previously patched image.
[Google Pixel 6] krotin:
Anyone succeeded with latest canary and taking OTA ?
[Google Pixel 6] gazdajezda:
THANK YOU GUYS! I just flash latest security patch (april) old-fashioned style (flash-all.bat without -w flag and patch, flash boot.img) - so far all good! I just hope that bluetooth will now work with my car as it should (like old Pixel 2 XL, without a hitch)...
[Google Pixel 6] gazdajezda:
Heh, it's kind of strange. Root function for majority applications i need it (Swift, Total commander, Power toggles...) but somehow not for AdAway. It reports "Root access denied" and does not offer root allow dialog. I already install Magisk app and patch directly again, reboot but same. Also noticed that also when app gets root, toast (message) is not shown. There is something not as it should be, any hint?
[Google Pixel 6] gazdajezda:
I guess i'm too old... I figure it out that i need to disable Magisk hide and use only Zygisk with Deny list and all is fine. Revolut, N26, Bitstamp all works. With all other Magisk root functionality of course. All seems fine again.
[Google Pixel 6] V0latyle:
This happened for me too the first time I set everything up after a clean install. Just go into Magisk, tap Superuser at the bottom, and enable for AdAway. All applications that request root should show up in that list. I'm not sure why Magisk automatically denies some of them.
[Google Pixel 6] gazdajezda:
I set it back. It was bacause i somehow had enabled hiding of magisk application and when i disable that, zygisk became active (not only ramdisk) and then all starts to work again. Except bluetooth connection with car (Toyota). This obviously is and will stay broken 😀
[Google Pixel 6] XMAN365:
My flash all restores factory stock. Are you installing a later date or a different model with the original factory built boot.img?

I can't seem to get my OTA to update on my November build
[Google Pixel 6] badabing2003:
for flash all, did you follow the guide and remove the -w to keep data?

OTA is a differential / incremental update, you're on November build, why do you even bother with that OTA, just go factory image, remove the -w and you're set, just follow the guide in OP.
[Google Pixel 6] XMAN365:
Yes, I remove -w from the bat. I'm trying to install a custom kernel.

Tying to edit cpu frequencies so they stay maxed and it seems updating the firmware could be the only way
[Google Pixel 6] badabing2003:
You'd have to follow the guide of the custom Kernel you're trying to update to, but I would think no matter what, following this guide's steps to be on the latest firmware first and then installing a custom firmware would be the proper path to take.

Good luck.
[Google Pixel 6] XMAN365:
Unfortunately it doesn't seem to take for any method tried, on this thread or the kernel's. Going to yolo the latest pixel 6 build with November boot image. Probably won't work
[Google Pixel 6] badabing2003:
Are you saying that you do flash all with -w removed of the April drop and it fails?

What error message do you get?
[Google Pixel 6] gazdajezda:
I used latest (april) factory image without -w flag in batch file. And yes, I flash it over november 2021 on Pixel 6 (oreole). Lost root but after flashing a patched boot.img and disabling root hide all is normal now (everything works - Revolut, N26, Bitstamp...). OTA in my case wasn't working - ended with bootloop first time and second I was able to boot from second slot. In a future I think factory image will do just fine for me.
[Google Pixel 6] XMAN365:
This is what I just did and it worked for me, thank you gaz
[Google Pixel 6] V0latyle:
I believe that if you sideload the OTA, it still incorporates all previous changes. The factory image on the other hand can be used for a "bare" device as it contains many components the OTA doesn't because it's assumed those components are already installed.
[Google Pixel 6] badabing2003:
I've been doing this for so many years, and never once had any issues flashing factory image to update my phone.

Granted I don't do OTA, but all I read is how people are having issues with OTA.

With the exception of one, and only one benefit that I see OTA presents, which is being able to update without needing a computer, I honestly don't see any other value in it.

If I'm wrong about it, I'm open to learning from my mistakes.
[Google Pixel 6] V0latyle:
I'm with you. I always use the factory image. I don't modify system or use a custom kernel, either. In fact I flash to both slots when I update.

At some point someone is going to have to be willing to take a day or two to experiment and find out exactly what situations cause what problems. As @Lughnasadh pointed out in the 6 Pro thread, OTAs will fail if any read only partitions are modified, or if a custom kernel is used.
[Google Pixel 6] hanni2301:
I would love to use OTAs, because the P6 is owned by my mother and then she would be able to pull of the update and keeping root.

On the other hand, I'm very familiar with the factory image method, so it should be no problem to instruct her. One question I have:

If I flashed to both slot's, it always said something like "not enough space on partition XY".

I helped myself with flashing the first slot and then switch to the other slot via Fastboot and then flash the second slot. Are you doing it the same way?
[Google Pixel 6] V0latyle:
No, I use the --slot=all argument.

But, I am using a Pixel 5. I don't have a Pixel 6.
[Google Pixel 6] ratrat420:
Hi guys, thanks to you, I've managed to root my Pixel 6 after number of tries somehow.

Now, my safetynet is passing (both CTS and Basic Integrity) however, my device is still not certified. I've tried clearing the storage of Google Play services and Playstore and added them to deny list on Magisk and it still doesn't work.

Is there any other workaround?
[Google Pixel 6] in_dmand:
does anyone know where I can get the systemless hosts module for Magisk? I see with their recent update it's no longer available directly from the app and when I check the repository on Github it's not there...

*edit: nvm I found it in the settings... apparently it's the one module they incorporated into the settings themselves.

but while I'm here... has anyone found a good adblocker? I've been using adaway but it doesn't work w/ Amazon app so every time I use Amazon I have to disable adaway and it's annoying lol
[Google Pixel 6] phaino00:
If you're referring to amazon prime video app, you only need to disable AdAway to login and after you're logged in, you can enable AdAway and the world is right. 😎 At least this is what I do. If you're referring to regular Amazon app, I cannot speak of since I shop through my browser on the site.

Hope it helps.
[Google Pixel 6] in_dmand:
yeah I'm referring to their normal shopping app... thanks though!!
[Google Pixel 6] V0latyle:
Since Play Services is a system process, DenyList won't work on it.

Have you already installed Universal SafetyNet Fix and MagiskHide Props Config?
[Google Pixel 6] badabing2003:
It's in magisk settings

you can add *amazon* into allowed list
[Google Pixel 6] airtower:
Disable web server will allow it to function without a *amazon* in the whitelist
[Google Pixel 6] V0latyle:
Yeah I had this problem too. I tried setting up the local web server and for some reason that broke Amazon. Just blocking the domains works fine
[Google Pixel 6] capntrips:
Amazon app does not work after installing AdAway · Issue #2436 · AdAway/AdAway

Amazon app (India) cannot load any pages. The home screen of the app crashes as soon as the apo is loaded. Search function does not work as well. No items can be viewed. However Amazon does work th...

github.com

Amazon app error when web server enabled (5.0.10) · Issue #2266 · AdAway/AdAway

Describe the bug When using version AdAway 5.0.10 with local web server enabled when the user attempts to browse the Amazon app, an error is displayed after the home page loads. To Reproduce Steps ...

github.com
[Google Pixel 6] in_dmand:
I know there's a way to also use a private DNS (dns.adguard.com) but that also has the same issue w/ the Amazon app and I don't think that one has a work around like Adaway does

...ps, the *amazon* thing worked, thanks @badabing2003
[Google Pixel 6] ratrat420:
Yes, I did. Is there something else I should do?
[Google Pixel 6] V0latyle:
You've done everything I have. Are you using a custom ROM or kernel?
[Google Pixel 6] ratrat420:
No, I am on Stock Android latest April build.

I have tried the device registration thing but it is still not working
[Google Pixel 6] V0latyle:
I can't think of anything else. I'm on a Pixel 5 but it shouldn't matter. I'm passing SafetyNet with the configuration at the bottom of the OP.
[Google Pixel 6] Uunderfire:
Hello everyone,

Something very strange happened today. While rooted, I very recently (2 days ago I think) installed the April Security update through OTA after following the correct procedure (uninstalling Magisk and any modules, then installing on the other slot). It worked just fine. However today, I got the same exact notification than the same security update was installed and ready to reboot.

Confused, I went to magisk and chose to install & boot on the other partition as I thought that the system would overwrite my root image. Yet now I'm in a bootloop with the message "Cannot load Android system" on the Android recovery. How should I proceed from now ? Is there a way to boot from the other slot ?

EDIT : I managed to boot to the correct slot in fastboot with fastboot --set-active=b and everything works fine. However I suppose that my slot A is not in a correct shape right now, should I reflash something to this slot ?
[Google Pixel 6] V0latyle:
If you want, you can flash the factory image to Slot A, but it really isn't necessary if you choose to update via OTA. The next update will be here in a few days and will overwrite that slot. Just follow the same procedure you did before.
[Google Pixel 6] airtower:
FYI May update via OTA process failed. Actually got the red corrupt device screen for the first time, then the device hung at the GOOGLE screen until I gave up. Booted back April fine, so flash tool it is again.
[Google Pixel 6] manjaroid:
I've never had corruption or hanging but I'm getting accustomed to OTAs failing. I've never installed a custom kernel and never messed with /system. The only cause I can think of is that _a and _b slots rotate between patched boot images and maybe I need to be flashing both slots. Sideloading works but it would be nice to skip that step every month and update unattended.
[Google Pixel 6] airtower:
I've been using the flash tool lately which won't flash all partitions without wiping, but if I knew --flash-all would get me fixed I'd happily do it (I just don't think it's the fix). Sideloading for me isn't worth it since I still need the boot.img to patch.
[Google Pixel 6] dilruk:
Is the automatic OTA and installing magisk to the inactive slot method working while rooted? Last I tried was February and it failed on me.
[Google Pixel 6] V0latyle:
What version of Magisk are you using?

It's supposed to be, using Canary 24306. Stable does not yet have the appropriate fixes.

The safest and most successful method of updating remains the factory image.

In other news, my wife just saw an actual oriole on our bird feeder this morning...
[Google Pixel 6] airtower:
I used 24306. There was definitely different behavior, but still not successful
[Google Pixel 6] Uunderfire:
Thanks for your answer, I'm going to wait for the next update.

I thought that it worked for me in the sense that I booted correctly to the other slot, however I have just realized that the OTA wasn't performed. Indeed, I still have the Android 12 notification with the message "Reboot now" which pops up everyday (here is a Screenshot in French), and the "Android Version" panel still indicates a March 5th 2022 security update.

I have no idea what would happen if I rebooted my phone right now, since Magisk indicates that it is installed on this slot in the Magisk manager. I just hope that it won't bootloop.

Spoiler content hidden.
[Google Pixel 6] capntrips:
It worked for me using 24307, fwiw.
[Google Pixel 6] airtower:
Did 23407 drop today? I swear I didn't see an update yesterday, but nor is anything in the changeling leading me to believe it no would have made a difference.
[Google Pixel 6] capntrips:
Yes, 8 hours ago (release notes). I'm not sure what changed.
[Google Pixel 6] airtower:
Odd timing, but still think there's an outstanding issue with magisk. I did get the verified boot (red text) warning, followed by a lock up on the google screen (not G, not a bootloop) which is different behavior than I've gotten in prior update attempts.

I'll capture logs again next month.
[Google Pixel 6] V0latyle:
## Magisk (63a89d9f) (24306)
## Magisk (cc79a96f) (24307)

- [App] Fix incorrect superuser snackbar text
- [MagiskInit] Improvements to sepolicy hijack
- [MagiskInit] Use `LD_PRELOAD` on 2SI init to assist hijack
- [MagiskInit] Support Oculus Go
- [MagiskSU] Fix a possible crash in `magiskd`
- [App] Update libsu with 100% new I/O layer
- [MagiskInit] Mock enforce file with regular file to prevent possible race condition
- Switch normal NDK with ONDK, preparing the toolchain to introduce Rust
[Google Pixel 6] Nightf0x_007:
im using magsik alpha 24306 after may update i cant root the device also i flashed april image again using flash tool but device wont boot also showing either try again or data reset so reflashed may update using flash tool and installed magisk canary 24307 but app stucks and i cant patch may boot image
[Google Pixel 6] pa.pn2:
Did someone successfully rooted may build with magisk beta 24.3 yet?
[Google Pixel 6] Nightf0x_007:
Can someone upload a magisk 24307 patched may boot image TIA
[Google Pixel 6] manjaroid:
Good luck.
[Google Pixel 6] Admiral2145:
Did it work for you?
[Google Pixel 6] manjaroid:
Yep, no problems. For root I patched with 24306 yesterday. Magisk upgraded to 24307 today. The boot.img was still on my phone so I just did another patch and sent it your way.
[Google Pixel 6] Nightf0x_007:
may update magisk beta 24307, in denylist gms wont stick and keeps getting unticked after reboots and cant get my device certified and cant pass yasnac test cts profile mismatch hardware backend
[Google Pixel 6] manjaroid:
Don't deny system apps. Did you install the safetynet-fix and Props Config modules?
[Google Pixel 6] V0latyle:
Magisk no longer blocks system processes, due to John Wu's position in Android Security being a potential conflict of interest.
[Google Pixel 6] Nightf0x_007:
Yes
[Google Pixel 6] Lughnasadh:
If you have the USNF installed, it will automatically untick gms as the mod won't work correctly if it is ticked. The mod actually "hides" gms in the background so you don't have to worry about adding it to the deny list. So having it unticked after a reboot is normal.

You may need to do some other things if not passing SafetyNet, like the MHPC mod, as @manjaroid mentioned. Once you pass SafetyNet, clear data and cache from Play Store and reboot and you should be certified.
[Google Pixel 6] Admiral2145:
Where can I download 24.307 from?
[Google Pixel 6] manjaroid:
On this page scroll down to Downloads and click the gray and red Magisk/Canary button.
[Google Pixel 6] airtower:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
[Google Pixel 6] V0latyle:
Magisk page, the Canary link.
[Google Pixel 6] Zanzibar:
Magisk Manager 24306 loads up just fine on my Pixel 6. However, 24307 starts to open and won't get past the screen of the Magisk logo with the mask. It just sits there indefinitely. After reinstalling 24306, it loads just fine.

On my Pixel 6 Pro, 24307 works fine.

Any ideas?
[Google Pixel 6] Zanzibar:
Sorry, I forgot to mention this. This happens with just the Magisk Manager app on the Pixel 6. I haven't unlocked the bootloader yet, so I'm not even attempting root at this point. I need to wait a few more days for T-Mobile to let me unlock the bootloader. I just want to be able to patch the boot.img file ahead of time.
[Google Pixel 6] capntrips:
See here. For now, you'll have to initially root with 24306 then upgrade to 24307, though I bet it won't be long before 24308, due to this bug.
[Google Pixel 6] r00tcracker:
Hi all, this is probably a stupid question but, I'm still on the November build and want to flash the May one (the factory image, no OTA).

If I flash with the -w removed in the FLASH ALL file, will that keep all my apps, accounts, home screen etc as they were, or will I need to re install apps, set up accounts again??
[Google Pixel 6] Lughnasadh:
Yes, it will keep everything as it is.
[Google Pixel 6] Zanzibar:
Thanks! I'm glad to know it's not just me experiencing this. I'll see if 24308 is out by sometime next week when I'm finally able to unlock my bootloader, and apply root. Otherwise, I'll root with 24306, then update as you suggested.

I appreciate your reply!
[Google Pixel 6] r00tcracker:
Thank you!!!!
[Google Pixel 6] Ictcreations:
Hi all, so i have a REALLY STUPID question. I first rooted after april's patch. I have the modded boot image for that particular OTA. What the instructions for this month don't make clear are whether I have to download the ota for may and patch that boot image before doing the automatic phone system update?

I understand i have to uninstall magisk, disable addons etc before doing it, its just that boot image thing i'm not certain about.

Because if i've got this right in my head, as it stands while i've got root access, i could install to 2nd slot now, then uninstall magisk etc and then do ota with current patched boot image in slot 2?
[Google Pixel 6] phaino00:
Always patch the boot image of the ROM/os/factory image you installed and are using.
[Google Pixel 6] capntrips:
When installing the automatic OTA, you don't download the boot image. When you install Magisk to the inactive slot after taking the OTA, it patches the newly installed boot image in the inactive slot. You perform a Restore Images before the OTA so update_engine finds the stock image before update; otherwise, it will fail. You don't lose root unless you reboot after Restore Images. Do not reboot when System Update prompts you.

Be sure you're on Magisk 24307 before starting the process.

Edit: or the newly released 24308, though I haven't seen any reports using that version.
[Google Pixel 6] Zanzibar:
Unfortunately, 24308 didn't fix the bug of Magisk Manager not loading properly on an un-rooted device (Pixel 6).
[Google Pixel 6] V0latyle:
Using an old kernel on the new build may cause problems; if you updated via OTA, it will cause a boot failure.

That being said, you can temporarily boot an older patched boot image then use Direct Install in Magisk to patch your current boot image. This is not always successful, and again will cause issues if you updated via OTA.
[Google Pixel 6] capntrips:
This has not worked for me since at least the March update, since I've been using that exact method to clear the eio screen in testing. It causes an instant boot loop. I can't say if it worked or not on any of the updates prior to that on this device.

Edit: In retrospect, I'm not 100% if I've used a patched boot image for this, but I know the stock one from a the previous update bootloops, lately.
[Google Pixel 6] V0latyle:
It may also be an issue specific to the Tensor platform. This works without a problem on the 765G; I used the January boot image to re-root my P5 and wife's P5a after the May update using the factory image.
[Google Pixel 6] squidbutt:
Will this method work with Android 13
[Google Pixel 6] V0latyle:
Rooting on Pixels has stayed the same since Android 9. The only thing that has changed has been Android itself; rooting on Android 12 was originally troublesome because the Boot Image Header was updated to version 4.

So, assuming nothing significant changes between Android 12.1 and 13, this method should work; the most likely outcome in case it doesn't is that Magisk will need to be updated to work properly with Android 13.
[Google Pixel 6] krotin:
I had the same problem and did not understand at first.

While flashing from march to april I tried booting an earlier rooted boot versions which resulted in a bad bootloop. I now always root the boot from the image I'm flashing.
[Google Pixel 6] lackalil:
I just did V0latyle's suggested path: root with 24306, update in app to 24308 and it worked fine.
[Google Pixel 6] V0latyle:
Magisk Canary 24309 is out with support for the Pixel 6 Android 13 beta.

Download
[Google Pixel 6] lackalil:
After installing and rebooting, zygisk wasn't working even though the toggle was on. I turned it off/on/reboot and it's good.
[Google Pixel 6] V0latyle:
To report issues with Magisk, either use the XDA threads or report via the Github.
[Google Pixel 6] V0latyle:
Canary 24310 has been released; this incorporates fixes for an AVB issue that was causing bootloops on the Pixel 6 / 6 Pro.
[Google Pixel 6] gazdajezda:
Does that mean that rooting May security update is now reliable? 10x
[Google Pixel 6] V0latyle:
I'm not aware of any specific issues with the May update. There have been some bootloops especially after OTA when people don't disable Magisk modules, but that wasn't limited to a particular update or version of Magisk.