yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] almahix:
My mistake. I have a pixel 6 pro.., not oneplus
[Google Pixel 6 Pro] almahix:
My bad. I meant pixel 6 pro.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Your best bet is

Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). If it can't fix it, then probably nothing can.
[Google Pixel 6 Pro] fil3s:
You can run the command 'adb reboot sideload' if you need to sideload' an ota. Btw if you're stuck with the android lying down with an exclamation mark, just press volume up. That will take you to android recovery
[Google Pixel 6 Pro] sronweb:
As July OTA update has failed in my device (rooted, then I removed root from Magisk, tried to install from automatic update, then the message "installation problem" appear and I may retry again...but no luck.

I wonder if I can install the OTA from Magisk directly instead.... or I should do it from adb.

Thanks for the suggestion
[Google Pixel 6 Pro] roirraW "edor" ehT:
Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)

Their flash site fixes problems that sometimes all other methods including flashing the full factory image (which is what you should try next, with the -w removed from the flash script) doesn't fix.
[Google Pixel 6 Pro] sronweb:
Thanks. But using the Google Flash Tool will also erase my data as for past experience, isn't so?
[Google Pixel 6 Pro] Nergal di Cuthah:
No just make sure wipe device is unchecked (which was the default when i flashed yesterday)
[Google Pixel 6 Pro] V0latyle:
There is no dedicated recovery partition in the Pixel series. Recovery lives in the boot image, along with the kernel. If you're unable to access recovery for whatever reason, simply reflash the stock boot image.

That being said, unless you're flashing custom ROMs through TWRP, there's no reason to mess with recovery on the Pixel.

Magisk does not install the OTA for you; you have to do that through System options. However, the July update seems to have broken out of band patching, so I recommend you update using the factory image method. The easiest way to do this would be using Pixel Flasher.

As @Nergal di Cuthah said, you simply need to change the flash options. But, if you intend to re-root after updating, Pixel Flasher might work better for you.
[Google Pixel 6 Pro] sronweb:
Then I should follow the steps in the first post?

Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.

When the update completes, the device will be in fastbootd. Reboot to bootloader.

Boot the master root image (See note 1):

Code:

fastboot boot <drag and drop master root.img here>

Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.

Your device should boot with root. Open Magisk, tap Install, and select Direct Install.

Reboot your device. You should now be updated with root.
[Google Pixel 6 Pro] V0latyle:
If you have a previously patched boot image somewhere, then yes you could do this....but honestly it doesn't matter how you update, you could update via OTA if you wanted.

For the sake of simplicity, again I recommend Pixel Flasher. @badabing2003 has done a fantastic job streamlining the update process via factory image, and the program does everything for you, including patching the new boot image.
[Google Pixel 6 Pro] almahix:
I have never had a successful OTA update on my Pixel 6 Pro. It always halts part way through. That is why I usually used Android Flash Tool until you guys taught me how to use side loading. And I sincerely appreciate all that I've learned here. Youz guyz are da best!
[Google Pixel 6 Pro] Nergal di Cuthah:
Sideload OTA didn't work for me this time, kept freezing (yes left it alone for twenty min with no progress). First time at 15% second time at 7% and (after a complete reinstall of platform tools and google driver) 0% twice.

Used official flasher and got updated
[Google Pixel 6 Pro] V0latyle:
It's actually pretty hard to brick these, so long as you don't screw up the bootloader.

The OTA can be kind of tricky because it "checks" after installation to make sure the kernel version is up to date. So, if you're using an older boot image, it will fail this check, and bootloop back to the old slot. Sometimes it seems to do this anyway even with the new boot image.

I'd suggest just using the factory image method.
[Google Pixel 6 Pro] sronweb:
Pixel Flasher is really great!. I just tried for the first time and it worked fine, so I could easily update the device to July patches, this time (finally) without losing data...and time to recover and configure. It deserve a donation!
[Google Pixel 6 Pro] elknetld2kil:
The first thing I tried was sideloading the OTA and then flashing the patched boot file (using the boot file from the new image).

Second thing was using Pixel Flasher and I got to a bootloop.

Third thing was the Android Flash Tool (without wiping data).

None of them worked after I tried flashing the patched boot image from Magisk. Maybe I am patching a wrong file? I got that from the factory image that just came out.
[Google Pixel 6 Pro] Nergal di Cuthah:
It should be boot.img from the second nested folder in the update zip
[Google Pixel 6 Pro] almahix:
I saw that same thing. I gave up. Glad it wasn't just me. I didn't know what I was doing wrong!
[Google Pixel 6 Pro] almahix:
I'll try it with next month's update. This is the first I've heard of it. Sounds interesting.
[Google Pixel 6 Pro] Nergal di Cuthah:
Was it on the vzw firmware too?
[Google Pixel 6 Pro] V0latyle:
To be clear, the boot image you're starting with is actually named boot.img, correct?

What version of Magisk are you using?
[Google Pixel 6 Pro] almahix:
Nergal, I don't believe so. I saw that listed but didn't intentionally select it. I have a direct from Google phone and use it on T-Mo.
[Google Pixel 6 Pro] elknetld2kil:
Indeed, that is the file. Magisk is 25.1.
[Google Pixel 6 Pro] V0latyle:
So you're able to boot with the untouched boot image, but the patched one causes a bootloop?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Did you disable all Magisk Modules? If not, then flash the Magisk-rooted boot.img, then use Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
[Google Pixel 6 Pro] elknetld2kil:
Exactly
[Google Pixel 6 Pro] JimbaJumbo:
Why do you guys root your phone anymore ?
[Google Pixel 6 Pro] V0latyle:
Because root access (essentially administrator privileges) allows you to do much more with your device than you could otherwise.

Also, simply because we can.
[Google Pixel 6 Pro] V0latyle:
This is strange indeed. Start over with the stock boot image; make sure you don't have any leftovers on your device, and follow the process to copy the image to your phone, patch it, copy back to PC, then flash it. Or, if you just want to test it, you can live boot it from fastboot.
[Google Pixel 6 Pro] elknetld2kil:
I ended up doing a flash using the online tool and wiping everything and it worked. I was trying to avoid it but I don't think there was any other way really. Thanks for the help.
[Google Pixel 6 Pro] almahix:
I root my phone so I can back it up in order to restore stuff after sideloads go wrong like they just did. Some data doesn't get backed up otherwise.,
[Google Pixel 6 Pro] sronweb:
Different reasons: full app and data back up, some magisk modules ie to implement call recording, ad block, timer control to force the phone to switch offline after a defined time. Of course it's quite personal decision, but I think that there are some benefits.

PS: root is nothing else than getting admin privilege, as you may do on your pc, but sometime is considered something to avoid. I agree we should not root without a basic understanding, because of the correlated security risks (the same happen with pc when we execute admin rights), but mostly it's should be your right as you are the owner of your phone, pc etc. even if in some cases the industry would like to prevent it, mainly for DRM, and to be merely users without control.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Just one of many reasons I have - with root, I can make my Quick Settings look like the following:
[Google Pixel 6 Pro] Dragon Kumera:
did you try unplugging the phone cable and replugging it back in after it stopped?
[Google Pixel 6 Pro] Nergal di Cuthah:
That was the only way i could stop it was to remove cable caused super amount of read errors. Still had to reboot via power volup
[Google Pixel 6 Pro] almahix:
I tried different cables, rebooting the phone, rebooting the computer.. I even repeated the download of the factory image and everything else I could think of. Sideloads continually failed. It wasn't meant to be. I had to use Android Flash Tool which wiped my phone. I was not happy.
[Google Pixel 6 Pro] Dragon Kumera:
that is indeed strange.

The only way I can flash (full flash factory image). I just edited the bat file to remove -w. Was to when doing it I had to constantly unplug and replug back in on certain steps. It would not auto do it.

I can only update my phone by manual ota sideload or full factory image since ota update causes my phone to brick itself. (Recoverable by manually reflashing the update).
[Google Pixel 6 Pro] Nergal di Cuthah:
That's weird, mine was default don't wipe
[Google Pixel 6 Pro] dilligaf56:
Just updated via the factory-image method. The only thing I have noticed is that for the past two months (June and July) - after writing the system image to the phone, attempting to boot with a prior patched boot image (May's in this case, but also tried an older one) did not work - it looped twice, then went into fastbootd. Trying again booted the July image from the phone without root, so I had to go through the procedure of patching the new boot image, then flashing it. All's good now, but wondering why live-booting with the older rooted boot image didn't work. Maybe because I update the bootloader each time as well?
[Google Pixel 6 Pro] roirraW "edor" ehT:
It's not unusual for an old kernel not working with a new update.
[Google Pixel 6 Pro] dilligaf56:
Yeah, makes sense, though it seemed to work fine prior to last month. Were they using the same stock kernel for several months? No matter, all's good - up, running, rooted. Thanks!

Interesting, though - I can boot my Linux boxes, even after dist-upgrades, with older kernels - there may rarely be issues with necessary modules getting loaded - but they do boot up. But Android is a different animal, even though the roots are there.
[Google Pixel 6 Pro] roirraW "edor" ehT:
No, the kernel does definitely change every single month. I'm no expert but a lot of security vulnerabilities that get fixed are fixed in the kernel.

It just depends on the magnitude of the changes, for whether a previous months will work.

I never try using an old kernel, with the only exception being a custom kernel that doesn't change for a new month, but that's also rare. I just go ahead and manually patch the new boot.img before I flash the full firmware (without the -w) each month.
[Google Pixel 6 Pro] mcwups1:
And how can I do this, Hmmmm?

Looks good.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I use both of the first two right now for different features, although I've used the third in the past - maybe sometime I'll revisit the third one.

[MOD] RENOVATE ICE - raven & oriole - Android 12L

[MOD][Xposed+Magisk] AOSP Mods - System modifications for AOSP-based Android 12+

Project Themer · Android 12⁺
[Google Pixel 6 Pro] Ghisy:
Wait, both RENOVATE ICE and AOSP Mods modify the system framework. Is it recommended to use both at the same time? Are you seeing bugs or worse (bootloop and such)?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Recommended? Probably not. :D But I can only report what results I had, which were that Renovate ICE appeared to override AOSP Mods where they overlapped in features, but I was still able to use AOSP Mods features (that Renovate ICE doesn't have) as well.

No bugs due to having both of them - only the same bugs that the individual mods have (nothing major). No, no bootloops.

Your mileage may vary, so be prepared just in case. Good luck!
[Google Pixel 6 Pro] vibrantliker:
V4a!!
[Google Pixel 6 Pro] vibrantliker:
Anyone see a big upgrade with the July release. I heard it's minimal plus reading people having issues with V4a.
[Google Pixel 6 Pro] fil3s:
You have to kinda know what you're doing if you're gonna root android. For example, one could install an incompatible module like a riru module when they have zygisk enabled. I personally have made the mistake of doing this and felt like banging my head against the wall until I learnt my mistake.

I personally root for full access to my device. Without root pretty much the only partition the user has access to is /data which won't allow much in terms of customisation etc.

Edit: actually the partitions on non rooted Android are recovery, data and int. storage my mistake.
[Google Pixel 6 Pro] snovvman:
I did not find an A13 root specific thread, so posting here. For an already rooted phone on A12, Magisk 25101, I read that the process to flash A13 is the same. I even read that disabling verity ("flash vbmeta --disable-verity....) may no longer needed. I read something similar in John Wu's thread about disabling verity being a part of Magisk now.

Is all of the above true?

Is there any harm in manually disabling verity before first boot anyway?

Along with SafetyNetFix 2.3.1, are there any new root issues on A13?

Many thanks.
[Google Pixel 6 Pro] Lughnasadh:
Root process is the same for A13 as it is on A12.

Disabling verity and/or verification is not required, but can be of help when unexpected things arise. I've had both disabled since I got the phone with no problems. If you are disabling them for the first time you will have to wipe (except if you just disable verity alone, then it's likely you won't have to wipe). If you want to keep them disabled you will have to disable with each monthly update. You won't have to wipe when updating unless you boot with them enabled and then want to disable. So disable before booting when doing monthly updates.

Magisk does not disable verity and verification and no longer strips the avb key from fstab entries as it did before.
[Google Pixel 6 Pro] snovvman:
Thanks for your reply and information. This is what caused me to assume that Magisk somehow disabled verity

https://twitter.com/i/web/status/1525034917670756353
[Google Pixel 6 Pro] Lughnasadh:
That just refers to a specific bug that cropped up on A13B2, Canary 24309, if I remember correctly, where it was required that verity and verification be disabled in order to avoid a bootloop. It was fixed in the next Canary.
[Google Pixel 6 Pro] snovvman:
Appreciate the clarification!
[Google Pixel 6 Pro] whatsisnametake2:
has anyone updated google pay to google wallet? any problems with root?
[Google Pixel 6 Pro] Ghisy:
I did. Wallet doesn't seem to detect root as before with Pay (using Magisk hide + deny list + universal safetynet fix module).
[Google Pixel 6 Pro] andreipaval:
For me GPay started detecting root about a week ago, but definitely before the update to Wallet.

Just updated Magisk canary and rebooted and bam GPay complained about software integrity.

I also have magisk, zygisk, universal safetynet, magisk props config. All Google services are in the deny list.

Safety Net passes in Yasnac and Google Play Store shows certified, but Pay still complains.

I've also cleared data of GPay but no luck.

Don't know what else to try?
[Google Pixel 6 Pro] sronweb:
I didn't notice any issue in the transition from GPay to GWallet.
[Google Pixel 6 Pro] V0latyle:
I assume you have GPay itself blocked in DenyList?

Make sure you tap on the app, not just the check box, and enable DenyList on all processes, as shown.
[Google Pixel 6 Pro] jcp2:
No problems here in Canada. Google wallet is not available in the USA. Magisk zygisk 25.2 and kirisakura kernel. All good.
[Google Pixel 6 Pro] V0latyle:
Not true. Works fine for me, and I'm about as American as you can get
[Google Pixel 6 Pro] jcp2:
My bad. The articles I have seen the past couple of days stated that Google pay was being replaced by Google wallet every where except the US and I think Singapore. I presumed that the US was not getting wallet. I stand corrected. :)
[Google Pixel 6 Pro] V0latyle:
I believe some Wallet functions are limited in the US, such as being able to upload your driver's license. But, for payment, mine seems to work fine.
[Google Pixel 6 Pro] andreipaval:
Yup, all processes for GPay are selected.
[Google Pixel 6 Pro] Spookymyo:
In step 8 you say to do the usual drag and drop thing. But in windows 11 this isn't working. Do you know how to enable drag and drop into CMD/power shell/terminal on windows 11? I know I can right click the file and select "copy as path" and then paste that into CMD but that isn't as efficient as the usual drag and drop.
[Google Pixel 6 Pro] V0latyle:
No idea, sorry. I'm a cantankerous old coot who refuses to use Windows 11. Google search says there's an update coming, but personally this makes me even less willing to use newer versions when Microsoft has been adamant about removing even the most basic functions.

You could try this...
[Google Pixel 6 Pro] NippleSauce:
This makes sense. Most of us in the US cannot get Google Wallet yet though. We can, however, get Google Pay - which is what will eventually be updated to Google Wallet (and I'm not sure if the interface will change when this update occurs). We all have access to "GPay" - which is different from Google Pay - as it comes pre-installed on this phone.

The funny thing about this app change is that Google Pay is just a small feature rip right out of GPay, haha. Otherwise, the apps are identical (same features and same interface). GPay just has a few additional features that I actually prefer having access to (even though I rarely use them, haha).
[Google Pixel 6 Pro] V0latyle:
Have you checked to see if you can download Wallet? I was able to on my Pixel 5.
[Google Pixel 6 Pro] NippleSauce:
I have and I cannot. I am in every single Google beta test app program, however, I cannot yet see or use Google Wallet as it seems to be restricted in the US - as @jcp2 was saying - or perhaps it just isn't available on the P6?

But we can, however, find and download "Google Pay" on the Play Store- which states in its app description that it will be updated and will become Google Wallet in the future. =)

*Edit* - I had to edit this comment like fifty times for spelling and other issues lmao. This is why I rarely drink lol
[Google Pixel 6 Pro] lattosimbaste:
Lost contactless NFC payment back on the 20th after the Wallet update and upgraded Magisk and Safetynet module only to lose root today. Guess I'll see if Wallet somehow works again tomorrow but given unlocked bootloader and custom kernel I figure I'll be in for an hour or two of fun tomorrow.
[Google Pixel 6 Pro] fil3s:
It works great on my p6pro , I'm in Australia 🤠
[Google Pixel 6 Pro] whatsisnametake2:
I just noticed something weird. much of the time I keep google wallet frozen using titanium, to avoid any magisk interaction mishaps. even with google wallet frozen, the shortcut on the lockscreen still launches google wallet! how is that even possible?
[Google Pixel 6 Pro] V0latyle:
I didn't lose root, but with Wallet and GPay installed, device fails security and NFC doesn't work.

Strangely enough, with both apps gone, it does through the Quick Settings tile...
[Google Pixel 6 Pro] acwcanada:
Mine is working properly including security. You may already tried: Install the Shamiko module and then configure the DenyList in Magisk but "DO NOT" enable the "Enforce DenyList", it works for me.
[Google Pixel 6 Pro] kevinkoo:
Jesus! I'm experiencing the OTA issue now as you described! OTA sideload is working for me for months but July NOT, as I'm in Asia, I sideload EMEA/APAC OTA firstly, stuck at 8%, then I changed to Global OTA, stuck at 2%. Also I thought the same might be platform tools version issue, then I reinstall platform tools and try again, stuck at 1%! Then I thought that's cable issue, I just tried another Type-C cable not working either...I'm nearly desperate... Now I know from you I should use Android Flash Tool, thanks!!
[Google Pixel 6 Pro] V0latyle:
Correction: NFC does work with embedded GPay. Just used it earlier.

Android Flash Tool doesn't help you re-root. I recommend Pixel Flasher as a powerful GUI tool to update using the factory image.
[Google Pixel 6 Pro] whatsisnametake2:
I read elsewhere on here about a recent google wallet update breaking use on rooted phones, and a safety net fix update sorting it out. anyone experienced any problems? it's still working fine for me with the safety net fix from ages ago (2.21?).
[Google Pixel 6 Pro] Nergal di Cuthah:
Don't know about wallet but newest safetynet fix is 2.3.1
[Google Pixel 6 Pro] whatsisnametake2:
yes that's the one i've seen mentioned having the new fix. still using 2.21 here. no problems. maybe it's device specific?
[Google Pixel 6 Pro] stroke55:
deleted
[Google Pixel 6 Pro] V0latyle:
It's not Wallet itself, it's the whole underlying security platform Google is using. Previously, they depended almost solely on SafetyNet. Then, they introduced more software methods with Play Protect Certification. Now, they're replacing both of these with the Play Integrity API, which for as yet unknown reasons is still able to detect root.

USNF 2.3.1 has been out for nearly a month, and as far as I know does not incorporate anything for the Play Integrity API.
[Google Pixel 6 Pro] whatsisnametake2:
so has this not fully rolled out yet or something? wondering why my device is unaffected?
[Google Pixel 6 Pro] V0latyle:
It's in the process.

More information here

Details on what it is and how it works
[Google Pixel 6 Pro] whatsisnametake2:
apparently this update does bypass the play integrity API problem

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517
[Google Pixel 6 Pro] V0latyle:
Except it doesn't. I've had it installed since release and I still get the GPay security message.
[Google Pixel 6 Pro] whatsisnametake2:
have you hidden/renamed magisk then frozen the renamed app?
[Google Pixel 6 Pro] NippleSauce:
Exactly. Having NFC payments work isn't necessarily based on what you have installed, but it is based on the order in which you set things up on your phone after an update and/or after rooting.

I am in the same boat as you and it always works for me without using Shamiko or using the DenyList. #IYKYK =)
[Google Pixel 6 Pro] V0latyle:
Folks, I'm going to ask that for further discussion of GPay/Wallet vs Magisk, please take it to this thread. The issues you are having are not isolated to the Pixel 6 / 6 Pro; many other users are having the same problems.

Let's keep this thread on topic, please.
[Google Pixel 6 Pro] EastonCo:
Update and Root Factory Image is the one I use everytime. I can never get it to work without getting a "corrupt" notice by simply using the OTA. I don't mind though, I prefer just manually doing it every update then I know exactly what is going on.
[Google Pixel 6 Pro] V0latyle:
Yeah, patching the out of band OTA has been troublesome for a lot of people.
[Google Pixel 6 Pro] mkhcb:
Finally installed an update without losing all my data and keeping root! On Android 13 now :).