yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] tgice:
Thanks! Sorry I missed that update.

Just a note, that above link does not jump you right to the 'Spoiler: Pass SafetyNet' button as I imagein you intended it to, but I found it fast enough.

Ugh, this sucks about Google's new direction, but at least the rest of us have some reprieve for awhile.

Once I applied the Displax USNF mod, things started working for me right away in Wallet.
[Google Pixel 6 Pro] V0latyle:
It does for me, even in an incognito window...

Right on
[Google Pixel 6 Pro] tgice:
Ah, I should've specified: doesn't work for me in Firefox! I see that it does work in Chrome & Edge. I'm embarrassed to admit I've not run across that Text Fragments feature before. Thanks for introducing me to it!
[Google Pixel 6 Pro] V0latyle:
People still use Firefox??? :P
[Google Pixel 6 Pro] Nergal di Cuthah:
I do mobile, but not desktop
[Google Pixel 6 Pro] Nergal di Cuthah:
{Mod edit: Quote post has been deleted}

Huh?
[Google Pixel 6 Pro] TescoBag:
So just to ask, is there a way to root my A12 pixel without losing all my data etc?
[Google Pixel 6 Pro] Lughnasadh:
Rooting itself doesn't cause any data loss. However, you do have to have your bootloader unlocked. If you don't currently have it unlocked, then unlocking it will cause you to wipe and there is no way around that.
[Google Pixel 6 Pro] tm2yl:
What image would I use if my provider is Comcast Xfinity Mobile using a Pixel 6 Pro?

I cannot find the answer
[Google Pixel 6 Pro] Nergal di Cuthah:
Either will work (I'm on vzw and used the non vzw until the release of vzw) but xfinity is a Verizon mvno so I'd suggest the verizon
[Google Pixel 6 Pro] Dragon Kumera:
Considering they are part of verizon. I suggest using the verizon image.
[Google Pixel 6 Pro] julerobb:
So I have a general question about adb. Is it similar to the Cisco IOS cli? Where you can for example tell it "do sh (sh= show) run | incl vlan. 1" basically can you do a direct grep or does it require a pipe ?
[Google Pixel 6 Pro] dilligaf56:
Yes. Citibank doesn't seem to want to let me use their credit card in Wallet, though Discover and a Barclay's MC work fine. Also, Chase won't let me use Zelle on my phone, as it detected root, this despite all of them being in the Zygisk deny list. Will check out the link in the following post soon.
[Google Pixel 6 Pro] julerobb:
Have you tried the hide root module thing in magisk? Assuming you're using magisk.
[Google Pixel 6 Pro] dilligaf56:
Just upgraded to the October factory image, have root after reboot, and YASNAC says it passes SafetyNet.

However, after the update, when I tried to update Magisk to the latest version (25205, from 25203), I kept getting a loop after it downloaded the .apk (the monolog box about download/install Magisk). After five or six attempts, I uninstalled and installed Magisk 25205 manually. It executes, but says it isn't installed, and Zygisk isn't enabled, though "Ramdisk" = "yes". Trying to install, only gives me "Select and Patch a File"., no option to direct-install. "Modules" is of course greyed-out.

In the logs, there is:

(Graphics Environment) - Neither updatable production driver nor prerelease driver is supported.

(libbusybox.so) type=1400 audit(0.0:4324): avc denied { search } for name="block" dev="tmpfs" ino=12 scantext="u: r: untrusted_app:s0:c171,c256,c512,c768 tcontext=u: object_r:block_device:s0 tclass=dir permissive=0 app=com.topjohnwu.magisk

(repeats once with "audit(0.0: 4325)")

(CompatibilityChangeReporter) - Compat change id reported: .... state: ENABLED

(opjohnwu.magisk) Cleared reference was only reachable from finalizer (only reported once)

(AppCompatDelegate) The Activity's LayoutInflater has a factory installed so we cannot install AppCompat's

Please advise - thanks!
[Google Pixel 6 Pro] Nergal di Cuthah:
Do you have two magisks installed? One hidden one not, this sounds like your issue
[Google Pixel 6 Pro] dilligaf56:
Doh! I'm an idiot. Forgot to unhide it first. Fixed. Thanks!
[Google Pixel 6 Pro] dilligaf56:
Yes. And the Chase and Citibank apps are in the denylist.
[Google Pixel 6 Pro] StanWiz:
I'm on my first pixel phone - way down there on the learning curve. I rooted my phone using instructions in this thread . Everything was fine until I received an ota notification, ended up updating using instructions from this thread . End result was the corrupt data problem which I fixed with adb.

Unfortunately when I try to reinstall magysk I end up with data corruption. Is there any way out of this with wiping data?

Thanks
[Google Pixel 6 Pro] westhaking:
When you get to the step of flashing the magisk image run

fastboot boot magisk_patched-xxxx.img

and NOT

fastboot flash boot magisk_patched-xxxx.img

Once it boots, go into your magisk app and install magisk using the Direct Install (Recommended) method. Reboot and hopefully you're good to go.
[Google Pixel 6 Pro] StanWiz:
@westhaking - better but not quite there yet. After fastboot boot it tries to reboot twice and gives a possible corrupt message. Retry boots - no error message but magysk is not installed.

(previously retry did not work)
[Google Pixel 6 Pro] westhaking:
Sorry I'm out of ideas
[Google Pixel 6 Pro] V0latyle:
What???

Android Debug Bridge is just that. You can use adb shell to run shell commands, but the purpose is to interface with Android and the device.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Here's a list of adb shell commands and there's at least one example of grep. There are probably other and official sources of this information, but this was one of the first Google search results.

ADB Shell Commands List - The Ultimate Collection (PDF)

Check out the directory of ADB Shell commands list with a cheat sheet PDF describing their functions and examples to use them.

technastic.com
[Google Pixel 6 Pro] StanWiz:
@westhaking Fyi - I downloaded the latest factory zip,patched the boot.img and flashed the patched image and everything is back to normal. The corrupt message is just a bad memory. I won't try to understand why lol

Thanks
[Google Pixel 6 Pro] westhaking:
Yeah there's been multiple reports of people taking the OTA with magisk installed and it giving them the corrupt data message and no boot. Best to always update directly with the factory image.
[Google Pixel 6 Pro] V0latyle:
The OTA shouldn't do this and is considered the "safest" way to update. I suspect the majority of issues have to do with Magisk or other modifications.
[Google Pixel 6 Pro] mydjtl:
I got the your device is corrupt. I think it was bc I accidentally did: fastboot flash boot magisk_patched-xxxx.img[/CODE] instead of fastboot boot magisk_patched-xxxx.img[/CODE]
[Google Pixel 6 Pro] V0latyle:
Shouldn't make any difference. What version of Magisk did you use to patch the boot image?
[Google Pixel 6 Pro] pontozero:
I would like to know what influences if I install only flash radio.img? will interfere with the cell phone's SIM network?! Or just wifi and bluetooth?
[Google Pixel 6 Pro] V0latyle:
The radio modem handles all wireless connectivity, so the radio image contains firmware for all wireless functions. It shouldn't "interfere" with anything - flashing the radio won't change your carrier provisioning, WiFi or Bluetooth settings.
[Google Pixel 6 Pro] pontozero:
It's ok! i asked the question because my phone corrupted my EID number i cant add e-sim anymore, thats why i thought it would solve this problem
[Google Pixel 6 Pro] V0latyle:
No, the firmware does not contain IMEI/EID information - that is hard coded into the phone, and if corrupted requires specialty repair.
[Google Pixel 6 Pro] pontozero:
What the hell! I searched and tried to repair it by software but I couldn't, because it seems that the service is not starting so it can't add the e-sim again
[Google Pixel 6 Pro] roirraW "edor" ehT:
Maybe the conversation here can help ->

https://xdaforums.com/t/solved-help-bricked-my-pixel-6-pro.4509831/post-87638787
[Google Pixel 6 Pro] Nawor81:
I'm at a loss, I have botted to the nov update so therefore any OTA's don't get installed. Now I keep losing root access and don't understand how to keep it
[Google Pixel 6 Pro] iwearthebelt:
Download and use the Pixel Flasher program. Take your time and read the instructions. It's not a difficult program to use, it's actually quite easy once you use it for the first time. It was a life saver for me, I tried to update my Pixel 6 Pro using a method I found on YouTube and ended up losing root also. Once I installed Pixel Flasher on my PC I ran the program, it was fully automated, it installs the November update including the latest version of magisk which automatically patches the boot img and installs without wiping data. Great program badabing created.
[Google Pixel 6 Pro] V0latyle:
All you should have to do is patch and flash the boot image...
[Google Pixel 6 Pro] iwearthebelt:
Sounds to me like he might be a novice user , that's why I recommended Pixel Flasher to him. Everything is done for you with that program. I'm sure he'll figure it out, you gotta learn somehow.
[Google Pixel 6 Pro] V0latyle:
Pixel Flasher is not a one click does all application. As @badabing2003 stresses in his OP, it simply automates ADB commands. It's still extremely important for anyone trying to modify their device to learn the details of how to patch and flash their device.
[Google Pixel 6 Pro] iwearthebelt:
I agree, but if you don't know how to patch and flash your device, using a program like Pixel Flasher simplifies the process and by doing some reading helps you understand how things are done (at least that's the way I see it). I was just trying to help the guy out, just giving a little advice. You can't learn this stuff overnight.
[Google Pixel 6 Pro] pojr:
Yikes. I may not have the right firmware. I have an unlocked bootloader and rooted device, so seems like things are running fine, but would not be surprised if I messed something up. Any idea what slider is? Ever seen something like this before? Not sure where I may have messed up.

Edit: I'll be honest, I feel like I followed the instructions to unlock the bootloader and root verbatim. So I'm not sure why the bootloader versions would be incorrect. Not saying I didn't mess up somewhere though.

I had a feeling boot.img wasn't the right way to go LOL.

I'm a little lost then, because I never needed to flash a bootloader update before. In the rooting instruction from This Thread, it says to grab the boot.img from the factory image, then patch with magisk, then "fastboot flash boot" that same boot image (which is now magisk patched). But we shouldn't use boot.img in the bootloader? Not trying to disagree, just wondering because clearly I'm a doofas lol. What would the magisk patched boot.img actually be for then??

Edit: Actually I think I understand. I can use boot.img in fastboot mode , but I just can't use the "bootloader" command for it while in fastboot, that should be for the bootloader img file that you referenced. That makes sense, if I understand.

Got it, so I should use fastboot flash boot_a and fastboot flash boot_b to update the fastboot version then?

Edit: Sorry, can't read. You said bootloader_a and bootloader_b, not boot_a and boot_b.

Anyway I greatly appreciate the help. If you want me to post in the other thread instead of here, I can do that. Trying to learn, but sometimes I break stuff in the process lol.

Edit: And yeah, the PixelFlasher looks cool. Might start using that for now on.
[Google Pixel 6 Pro] Lughnasadh:
Slider is the correct name used in the bootloader name for this device. Don't worry about that.

You should be able to use --slot all (or --slot=all) to flash the bootloader to both slots. For Tensor devices, you can't use --slot all (or --slot=all) when updating the whole firmware (e.g. when putting that command in update line in the flash-all.bat file when updating to a new monthly build). It will error out when you do that. But using --slot all (--slot=all) for flashing individual images/partitions should work.
[Google Pixel 6 Pro] pojr:
Thank you for explaining this. Not gonna lie, I only had a VERY basic understanding of a bootloader. It lets you change partitions. That's really all I knew. I still don't get everything that you're saying here (too advanced for me).

This is VERY helpful information, this I understand. You pointed this all out in a clear, concise manner and I appreciate this. Never realized fastboot was within bootloader mode. Not gonna lie. I know what a partition is, but didn't know what partitions existed within Android, and didn't realize there were 5+ of them. But still, a lot of this makes sense.

I'm actually glad you stated this, because it's a wake up call to me. Maybe I shouldn't be doing any of this.

Also small comment: seems like Lineage OS is easier to deal with than Stock. Is that just me? I haven't had near as many problems with Lineage OS as I have with Stock, but again, could just be me.

That last comment "Get someone who knows what they're doing to help you". Should I just give up? It's saying a lot when the teacher gives up on the student lol (I say teacher because you made this thread to begin with) but I don't blame you. I've rooted a few devices in the past and updated them with minimal problems, but I've always just followed the instructions from tutorials without understanding exactly what I'm doing. Anyone can write "fastboot flash boot_a boot.img", but doesn't mean they understand what it means or why they're doing it. That's where I'm at.

I know that. Because if anything goes wrong, or the program gets discontinued, or if I need to cease use of the program for whatever reason, I won't be able to do anything on my own. Would that be a fair assessment?

Nonetheless, I really do appreciate your time. I apologize for wasting your time. If you do have a way I can donate or something, I will do that.
[Google Pixel 6 Pro] V0latyle:
There's actually closer to 20 partitions. Fortunately we generally only have to concern ourselves with three: /bootloader, /radio, and /boot.

It just means you have more to learn. Don't be afraid to ask questions. While I have a multitude of technical knowledge, I'm not the best teacher. Fortunately, we have tons of other people here who can help explain things. None of this really comes naturally; while I'm a technically minded person, I've also been doing this for more than a decade, when the original Motorola Droid came out. I had to essentially relearn everything when I started using HTC devices, then again when I started using Samsung, and finally when I switched to Google.

I suppose it would depend on the device. LineageOS seems to work okay on my tablet; I just use the stock firmware with root on my Pixel 5.

No, don't give up. Just make sure you have a clear understanding of what you want to try to do, and how everything works. I would recommend not trying until you're at the point where you have a solid grasp of things, but sometimes we just have to yeet it because YOLO or whatever the kids say these days...

I don't think @badabing2003 will be discontinuing PixelFlasher anytime soon, but it is always wise to understand the concepts involved.

You aren't wasting my time. If I'm not able to help you learn somrthing, what am I really doing here?

As far as I know, moderators can't accept donations. I could be wrong. Still, I have never bothered to set anything up to receive donations, mostly because I take the most enjoyment out of simply being able to help others figure things out. The best way you can help me is by learning as much as you can and helping everyone else on XDA.
[Google Pixel 6 Pro] uzichan:
Is there a way to change IMEI on pixel 6

So far Im unable to find any method
[Google Pixel 6 Pro] V0latyle:
This question isn't relevant to the scope of this thread. Furthermore, as changing IMEI is illegal in many countries, we do not permit discussing it on XDA.
[Google Pixel 6 Pro] 73sydney:
Yup everyone should know how to do the process manually for a good base understanding of what theyre doing and what the process is doing, before letting a program or app do it

Trying to do things quickly and the easy way often disappoints, and i for one hate trying to troubleshoot an app wrapping a known process, when troubleshooting a known process is far easier...

Having said that, with plenty of Pixel (and general ROM) flash points under my belt i am looking forward to trying Pixel Flasher at some point soon
[Google Pixel 6 Pro] jackuphill:
Hi

My Pixel 6 was on A13 build P1A.221105.002, Nov 2022.

I then rooted the phone using Steps given for intial root with Master Root Image and Magisk. Used Magisk version 25.2.

Before updating with Dec OTA chad checked the current slot and it was "b"

For updating to Dec OTA followed the "Update and Root Automatic OTA" using Magisk. (inactive slot method).

After rebooting from Magisk got the error "your device is corrupt. It can't be trusted and may not work properly." with option to press power button to continue. But before I could press the power button the phone went blank and got switched off. So I turned it on again and now it booted normally, (with only warning of unlocked bootloader)

But now Magisk showed N/A and also the build was on P1A.221105.002, Nov 2022 itself and later when I checked the current slot, it was still slot "b"

As the Dec OTA and Magisk got installed in slot "a" and now that it is corrupted how to correct the inactive slot "a" so that slot "a" returns to the state before Magisk and OTA was installed to the inactive slot.
[Google Pixel 6 Pro] V0latyle:
If the update fails, the device automatically recycles back to the last working slot. You do not need to do anything to Slot A. You can try the OTA update again, maybe sideload it this time, or you can update via the factory image method.
[Google Pixel 6 Pro] fil3s:
I'd use flashtool then fastboot boot the patched image, direct install. Safest and easiest way.
[Google Pixel 6 Pro] jackuphill:
Thanks, will try the factory image method. One doubt I suppose I can flash the December build instead of the November build.
[Google Pixel 6 Pro] jackuphill:
Thanks will try to flash the factory image. One doubt I suppose I can flash the December build instead of the November build.
[Google Pixel 6 Pro] V0latyle:
You do not have to install updates incrementally. The December update contains all previous changes.
[Google Pixel 6 Pro] jackuphill:
I used your suggestion, plus then side loaded the OTA too, and re-rooted with Magisk. Thanks for the suggestion
[Google Pixel 6 Pro] jackuphill:
Thanks. Was able to side load the OTA via adb. and then re-rooted the device.
[Google Pixel 6 Pro] digger16309:
Odd finding in the December Raven update. When I extracted boot.img to patch it, Microsoft Defender stepped in and claimed it was infected with Trojan malware. I finally had to turn Defender off to complete the task. Windows 11 21H2 / Defender - Latest Update.

Anyone else experience this?
[Google Pixel 6 Pro] Nergal di Cuthah:
Same

this is what it thinks it is. A trojan from 2019

Trojan:Script/Wacatac.B!ml threat description - Microsoft Security Intelligence
[Google Pixel 6 Pro] Nergal di Cuthah:
No way to report false positives in defender boo
[Google Pixel 6 Pro] V0latyle:
Was this before or after patching? I haven't noticed this, but I also have Defender on a short leash
[Google Pixel 6 Pro] digger16309:
Before. It happens the instant I extract the file from the image archive. I couldn't even extract it to a cloud drive.
[Google Pixel 6 Pro] V0latyle:
Weird. I have all my phone software stuff in a Phone folder that I have added to Defender exceptions. In Windows 10, it's Settings > Update and Security > Windows Security > Virus and threat protection > Virus and threat protection settings > Exclusions
[Google Pixel 6 Pro] romaolp:
How can I install the new Android 13 QPR2 Beta 1 withou lose root? I'm running the stable version!
[Google Pixel 6 Pro] 73sydney:
i would hold off for the moment and monitor....there are reports of issues patching the boot image

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87852119
[Google Pixel 6 Pro] romaolp:
Yep! Already notice this! Thank you!
[Google Pixel 6 Pro] V0latyle:
You have to patch init_boot on the Pixel 7, so I wonder if that applies to the beta as well?
[Google Pixel 6 Pro] 73sydney:
Im still lagging in even finding time to install the december update, so i probably wont be the one to confirm/disprove that hypothesis sorry :)
[Google Pixel 6 Pro] Lughnasadh:
I don't believe the Pixel 6 series has an init_boot.img. But patching the Pixel 7 boot image and flashing it on the Pixel 6 works to root the Pixel 6 when on QPR2 Beta 1.
[Google Pixel 6 Pro] V0latyle:
That's odd. Magisk patches ramdisk, which on the Pixel 7 was moved into init_boot.img. Boot.img just contains the kernel. So, unless Magisk adds ramdisk back in somehow...that shouldn't work o_O
[Google Pixel 6 Pro] Lughnasadh:
Magisk can add a generic ramdisk to a boot image lacking one, e.g. Pixel 7.

Support GKIs without ramdisk · topjohnwu/Magisk@985249c

Fix #5819

github.com
[Google Pixel 6 Pro] V0latyle:
Well now that makes sense.
[Google Pixel 6 Pro] Lughnasadh:
https://twitter.com/i/web/status/1602774339224367104
[Google Pixel 6 Pro] StanWiz:
Third month in a row I'm getting corrupt data after doing an ota. There won't be a fourth ota lol .

I will be sideloading in January. I am a bit confused when it comes to the "master root file" - do I have to recreate it each time using the latest boot.img or will my/old patched boot.img work? The instructions would make me believe that it should work for future updates.

I tried using my previously patched imp the first time I got the corrupt data and it didn't seem to work (at least I don't think it did - i was even greener then than i am currently)

Could someone clarify?

Thsnks in advance
[Google Pixel 6 Pro] V0latyle:
It depends. The only absolute "right" way is to start with a clean copy of the boot image from whatever build you updated to, patch that, and flash it.

However...

You CAN sometimes (often) get away with live booting an older boot image. Since the kernel itself doesn't update all that often, there isn't much in the boot image that changes. The only caveat to this is that you CANNOT do it right after an OTA; the system still knows what version the boot image is, so if you just updated via OTA, it's expecting the new boot image after reboot, and if you live boot the old one, it'll assume the update failed.

So, if patching to the inactive slot hasn't been working, just dirty flash the factory image, live boot the older patched image (because update_engine isn't running) and perform Direct Install.
[Google Pixel 6 Pro] amritpal2489:
Can somebody provide me Pixel 7 Pro's magisk patched boot img from the latest QPR2 Beta 1 update?

The one which succesfully roots the Pixel 6 Pro
[Google Pixel 6 Pro] snovvman:
After years upon years of flashing factory image and rooting, onto A12 and A13, flashing every month and rooting without fail, I discovered today that I somehow lost root. My last flash was December's QPR.

My procedures were to patch boot.img, then flash all without -w and reboot, then issue:

fastboot --disable-verification --disable-verity --slot=all flash vbmeta vbmeta.img in both fastbootd and bootloader (for good measure, lost track of whether it needed it), then

fastboot flash boot --slot all magisk_patched.img

This has always worked.

I hide the Magisk app, so updates can cause problem sometimes. My procedures were to unhid, update, then re-hide. Today, when I launched Magisk, it gave an error (something about hidden). Once I got the Magisk app sorted, it showed that I was not rooted. To make things a bit more complex, there was a recent Magisk update-25206.

So far, I've reflashed the patched boot in bootloader using both the latest Magisk and 25205 (along with vbmeta disable). When the P6P boots, the Magisk app is not there. When I install the app, it shows that the phone is not rooted.

I've never lost root before, and recall that with A12 and 13, once root is lost, a factory reset is needed to get root back. Is this true? Any suggestions on what the problem might be and how I can get root back without factory reset?

Many thanks!