Just wanted to say thanks for your time and effort on this @V0latyle - Very Cash Money
Just wanted to say thanks for your time and effort on this @V0latyle - Very Cash Money
Magisk 23017 is supposed to work that way, not sure if it's working for the P6 though. Until we know it's working for sure, the best way to update is by dirty flashing the factory image.I want to ask about OTA: Whether can I update OTA but won't lose Magisk root ?
I have another phone - Oneplus8pro. I can OTA and won't lose the magisk root.
1. Donwload full OTA file and flash it ... BUT DON'T REBOOT phone after
finishing it;
2. Open Magisk manager to install Magisk to another inactive slot;
3. Then rebooting phone...
Whether it works at Pixel6 pro OTA ?
I didnt deal with all that and everything is working....curious if others had to do this....Just wanted to throw in, as V0latyle did'nt cover it: the google services: Zygist, Magisk Hide Props Config Module, Universal Safetynet Fix module
A Brilliant video going through installation:
Maybe you could pin this so people can easily follow![]()
yeh i had to. unsure why. But the video is very good. ez to follow and working now (google pay issues)I didnt deal with all that and everything is working....curious if others had to do this....
Just wanted to throw in, as V0latyle did'nt cover it: the google services: Zygist, Magisk Hide Props Config Module, Universal Safetynet Fix module
A Brilliant video going through installation:
Maybe you could pin this so people can easily follow![]()
Those things aren't necessary for root proper. They're only necessary for Google Pay, some banking apps, and probably a very few non-banking apps. It's also covered at a high-level in the OP. Just click on the "Spoiler: Pass SafetyNet" in the first post.I didnt deal with all that and everything is working....curious if others had to do this....
Yeah I didnt run any su commands like the video does....my banking app and gpay works as advertisedThose things aren't necessary for root proper. They're only necessary for Google Pay, some banking apps, and probably a very few non-banking apps. It's also covered at a high-level in the OP. Just click on the "Spoiler: Pass SafetyNet" in the first post.
I never fooled with those steps before a few months ago but they work perfectly for me to get working Google Pay and a few bankings apps I use.
If you need more detail than @V0latyle gives in the OP, at the top of the list of Pixel 6 Pro threads, click the How To Guide filter:
View attachment 5514969
Then look for (or Control-F to search/find for) the thread by @Pekempy called "Working SafetyNet with Pixel 6 Pro Android 12". That first post will give you the detail you need. Please ask any questions if necessary in that thread.
We must connect to Internet first then the OEM Unlocking will come available. (except carrier devices)Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
You didn't read the OP. I absolutely did cover this under "Pass SafetyNet". Don't hijack my thread. I tried to keep instructions relatively simple. I am passing SafetyNet on my Pixel 5 using the modules I mentioned, and did not have to run any commands.Edit : If your having google pay issues or other random google issues/ bank app issues follow this:
Just wanted to throw in, as V0latyle did'nt cover it: the google services: Zygist, Magisk Hide Props Config Module, Universal Safetynet Fix module
A Brilliant video going through installation:
Maybe you could pin this so people can easily follow![]()
NoJust curious -
I recently rooted my new unlocked Pixel 6 Pro using the January update, Magisk 23016, Zygisk, etc. Everything worked fine until I tried to activate it with the eSIM on Verizon. There was no second IMEI number available, and I was unable to activate it through the usual routine of scanning the eSIM QR code provided by Verizon. Their level 2 tech worked with me for a couple of hours off and on, then punted and contacted Google tech support without any luck. Does rooting by flashing the factory image kill the eSIM capability? Just curious.
Unfortunately I can't provide any insight to that issue.I finally got it activated by using a physical SIM and all is working well - but I would like to have the capability to use it if possible.
Doesn't work for anyone, and problems with unlocking the bootloader are outside the scope of this thread.We must connect to Internet first then the OEM Unlocking will come available. (except carrier devices)
This has been confusing for a lot of people.I tried to apply the Jan update using the android flash tool. There was no 'skip reboot' option (yes, I looked at the 'advanced' options) but I proceeded anyway (prob a very bad decision). Now I cannot boot successfully with a magisk-patched boot image. (Phone evetually winds up in recovery with a 'try again' choice) Did the vbmeta flag get re-enabled?
No. If this happens again, you can always reflash the unpatched boot image to get back to system. You won't have root. But, you can get temporary root by live booting the patched image:
fastboot boot <patched boot image>
It's been a little while since I used it; the skip reboot option is not available with the Android Flash Tool. My mistake. After the device boots, just reboot to bootloader and flash the patched image.Finally... how did others use the flash tool? Was 'skip reboot' missing for others?
Glad you got it straightened out. There's been some weird things going on back and forth with the December and January updates on the P6/P6Pro.UPDATE2: back in business w/root. Booting immediately after the flash tool update didn't do any lasting damage (data is intact and readable). I tried the fastboot update as well. The key to getting root back was re-creating my 'master magisk patched' boot image using the latest boot image from the Jan factory image.
It should.I reallllllly thought a 'recent' patched boot image (from Dec in this case) would be sufficient. I still plan to go back and retry the flash tool update (despite the missing 'skip reboot') and see if the updated patched boot image allows root after that.
that a lot of tinkering when it is not needed. But maybe they just had bad luck or are on an older magisk version.Edit : If your having google pay issues or other random google issues/ bank app issues follow this:
Just wanted to throw in, as V0latyle did'nt cover it: the google services: Zygist, Magisk Hide Props Config Module, Universal Safetynet Fix module
A Brilliant video going through installation:
Maybe you could pin this so people can easily follow![]()
In one of the unlocking threads it stated it had to do with the date on the P6. Setting the date a month back removed the greyed out OEM lock....thats what I did and no issues...fwiwWe must connect to Internet first then the OEM Unlocking will come available. (except carrier devices)
Interesting!In one of the unlocking threads it stated it had to do with the date on the P6. Setting the date a month back removed the greyed out OEM lock....thats what I did and no issues...fwiw
Yeah it was the first I read about anything like that IIRC, it said something about the phone needing to be alive for a week....so if you set the date back further than that you should get OEM Unlock to be un-greyed.....wish I could find that again to link but havent yet
That's an excellent idea for @android_dan.Have you tried live booting followed by a direct install?This way if it fails , android will just boot the stock boot image
I suggested the Official Google Android Flash Tool site because it has fixed things that manually flashing the factory image hasn't, in at least a dozen examples I've read about in this section alone in the six months the P6P has been out.Thanks for the reply. Maybe 'm being dense but not sure how the flash tool is going to help. The problem isn't recovering from the bootloop. That's just a matter of flashing an unpatched boot image. The problem is what could be causing the patched file to bootloop the phone. I've updated this rooted phome 3 or 4 times now by flashing a patched boot file with no issues and have changed nothing on the phone
No idea.. this was the 1st time it's happened to me on A12. Do you think I should use canary? Mind you, I should note the 'direct install' option was still available, but when I tried it it failed , can't remember the error.
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash boot <drag and drop master root.img here>
adb reboot sideload
adb sideload ota.zip
fastboot boot <drag and drop master root.img here>
fastboot flash bootloader <drag and drop new bootloader.img here>
fastboot flash radio <drag and drop radio.img here>
fastboot update --skip-reboot image-codename-buildnumber.zip
fastboot boot <drag and drop master root.img here>
flash-all
script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w
option so it doesn't wipe your device.fastboot update bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot --slot=all <image-device-buildnumber.zip>
fastboot boot <drag and drop master root.img here>
Part of it is due to device differences - non A/B devices can't use seamless updates, so re-rooting is only possible by either patching the boot image directly, or by flashing Magisk in a custom recovery.I just used this method, (same one described on Magisk website here https://topjohnwu.github.io/Magisk/ota.html) and it worked perfectly, both root and safetynet.
Can someone explain to me why you see all kind of guide to update which are far more complicated than that ?
Notice the date of that post, 16 months ago. Magisk Canary 23017 re-incorporated the ability to install to inactive slots.Are you 100% sure?
Cause topjohnwu said that OTA patching from within Magisk was broken for Pixel devices.
See here