yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] missionman:
When I rooted my pixel 7 pro with magisk and pixel flasher it was a combination of many things to get it to work right. You must be on older security patch first of all. Mine was on May 5th 2023. CTS profile was mismatching until I picked a older model phone, I think nexus 5 or pixel 3. Safetynet fixes I had to install one over another to get it to work with CTS testing and passing.

I had LSposed and many good modules. I was loving it. Phone ran fine but due to my phones thumbprint I encountered a app or 2 that wouldn't install from playstore but would install via 3rd party install.

I ended up with a corrupted phone after a year. No recovery effort worked. None. I even contacted the creator of pixel flasher and all he did was get annoyed at me from the start. Even his "fixes" didnt work to save my data.

In the end, I had to restore my phone and wipe it and I lost all kinds of data.

However I found using ADB AppControl (I paid for full version) was all the control I needed on my phones. To me it's way better. I debloated every app associated with Google except 2 for functionality and deleted GBs of apps and spy crap. I highly recommend going this route.

If you root ANY pixel 7 pro, it's a fact, it's a matter of time before your phone randomly gets corrupted, especially if you accidently reinstall a system app on a rooted phone that previously removed it. Do that and your root will instantly go corrupt and it'll boot to a corruption message and stay there. I tried every method of pixel flasher to save data and none worked.

If you want to be happy, ADB AppControl is the only tool you need. In the end I just wanted root for old reasons that are obsolete today.

You can achieve privacy and debloat and all kinds of manipulation with ADB AppControl.

That's my 25¢
[Google Pixel 7 Pro] BunnyPig1:
Are you working for Google and trying to convert us to the PI gods?

Joking aside, I'm happy that you feel the need for root/unlocked bootloader is behind you. But this statement you made is not true at all. Just because it has happened to you, and I'm sorry it did, doesn't mean that it will happen to all of us. It is not a fact and I am proof of this. I have debloated, rooted, messing around with system files etc. and never gotten a corrupted system from this.
[Google Pixel 7 Pro] missionman:
It is a fact. Try re-installing a cellular provider system app and watch your phone go corrupt.

This happens 10 times out of 10. It only depends on which cellular provider system app it is that overwrites the current cellular app handling hotspot.

No offense but what i said isn't Google propaganda dude. I hate Google. Im just warming and advising that root is pretty much I needed to achieve debloating and privacy security and if you want it for further modding, sure, I get it, but given time and tinkering it will lead to system corruption.
[Google Pixel 7 Pro] Lughnasadh:
What exactly do you mean by corrupt? Do you get a message such as "Your device is corrupt. It can't be trusted and may not work properly.".
[Google Pixel 7 Pro] missionman:
No that's a bootloader message. The message I'm talking about is red and simply says your system IS corrupt. You can look it up. Sorry I don't have time to upload a pic. But yea it does happen and it WILL happen simply by installing the wrong app, ESPECIALLY if you have trouble with hotspot not working after root with Verizon. Happens ALL THE TIME. happened to me, then I saw on xda how many it has happened to, mostly with trying to get root settings to work like hotspot for example.

my bootloader is still unlocked but after all was said and done and being a root fan since XDA began (rooting every brand phone) I pretty much gave up on root.

Infact, phones are being updated to go corrupt on purpose when you combine certain sequences like these app swaps. DO NOT INSTALL A OLD VERSION OF SYSTEM APPS YOU PREVIOUSLY REMOVED OVER AN UPDATED SYSTEM APP. The result is filesystem corruption and good luck saving data with pixel flasher.
[Google Pixel 7 Pro] Fishawy:
Apologies, I won't debate whether root is worth it or not, but to me this sounds like it's not a root problem or a PixelFlasher problem, it's an issue you faced after trying to reinstall a system app that shouldn't have been debloated in the first place (referring to your words about deleting GBs of apps).

Please correct me if I'm wrong.
[Google Pixel 7 Pro] BunnyPig1:
I have not tried to uninstall and re-install any cellular provider system app but your statement:

If you root ANY pixel 7 pro, it's a fact, it's a matter of time before your phone randomly gets corrupted, especially if you accidently reinstall a system app on a rooted phone that previously removed it.

implies that no matter what you do, as long as you're rooted, your system WILL be corrupted, it's only a matter of time. This is not true.

I can uninstall any specific system apps and it will corrupt my system, sure, but that is because it's needed to run. That doesn't mean that root itself will cause system corruptness, only your actions.

You said specifically "especially", which might be true but further implies that it's not just because you're modifying system files that's making it corrupt, but root itself.

I'm not trying to be rude, it's just that you're blaming root for making your system corrupted, not your own actions. I don't want misinformation to spread in case someone new is watching this thread and gets scared for the wrong reasons.
[Google Pixel 7 Pro] Lughnasadh:
The message I quoted is the RED eio dm-verity corruption message (see pic below). I was just curious if this was the message you received because if it is it's very easy to get rid of it. If it's not, then nevermind.
[Google Pixel 7 Pro] missionman:
Yes You are partially correct. While this can be avoided, it sadly won't be because it happens during troubleshooting when someone tries to revert to a "working" method or version app that was working prior. Many many people on Pixel 7 pros run into issues with hotspot or types of connections that require subscriptions that work by code reading commands to that specific toggle or service.

My recommendation is stuck with Android 13 or 12 for root. Root on Android 10 is great.

But android 14 and so on is getting SO bad eventually it'll be history.

All I'm saying is root is now SUPER tricky. And it's getting worse. Root is best on slightly older models that don't mix related settings that cause systemwide corruption. Android now is getting so entangled with apps that changing one forward or back can permanently corrupt your data.
[Google Pixel 7 Pro] missionman:
Look us there ANYONE here that doesn't follow everything their told?

DISCLAIMER on root? IT CAN CORRUPT YOUR PHONE. it's a matter of time especially if you tinker a specific way or just allow auto updating.

So many ways root goes bad and very little that keep it running smooth.
[Google Pixel 7 Pro] Fishawy:
Apologies again, what hotspot issues and what subscriptions? And how are these relevant to deleted system apps? I thought this was about debloating things that shouldn't have been debloated.

I've never heard of "connections that require subscriptions", and if there were generic hotspot issues or otherwise, you'd find XDA/reddit/Telegram flooded with reports, which I've never seen.

If the "corrupted system" error you got is what @Lughnasadh referred to, then yes it's easily fixed (using PixelFlasher amongst other tools).
[Google Pixel 7 Pro] HippoMan:
Agreed.

The only way that root *might* be involved in these scenarios is indirectly; i.e., because root is normally needed to "reinstall a system app". In other words, it's not root itself, but the *misuse* of one of the capabilities that's associated with root (messing with system apps in this way is indeed often an example of misuse).

I have run rooted Pixel phones -- including Pixel 7 -- for literally *years*, and nothing like this has ever happened ... and I have successfully installed, un-installed, re-installed, replaced, etc. etc. etc. literally dozens of different non-system apps during this time. I can say the same thing about the non-Pixel phones I have also owned over the years: Samsung, OnePlus, and a few other brands.

But I never tried to reinstall or uninstall a system app that came with the phone ... because many people (including myself) know how dangerous that can be. @missionman's problems are specifically involved with that kind dangerous and non-recommended action, and not with rooting itself.
[Google Pixel 7 Pro] BunnyPig1:
Exactly.

I've been rooted ever since my first smartphone and I've never had a system go randomly corrupted. If it has happened it's because of my own actions, not only by rooting.

There is always a risk by modifying your device if you're not careful enough.

It feels like @missionman didn't understand his/her own post. Mentioned a disclaimer pretty much all custom roms or modifying tools uses. This disclaimer they give is to let you know that the tools/methods might cause damage in case the user is not certain in what they do. Everytime my system gets corrupted I never get mad, because I am aware of the consequenses.

Blaming root for damage when root in itself never does anything at all is just odd to me. It's like saying everytime I get a bluescreen/crashed harddrive on my pc I blame administrator rights on windows.
[Google Pixel 7 Pro] simplepinoi177:
I've owned and rooted a Pixel 2, Pixel 2 XL, two Pixel 5's, and two Pixel 7 Pros, all for 2 or 3 years of use -- it is not a "matter of time" that it gets corrupted. I've never had such issues for the last 7 years. And it's only been a superior & smooth experience being rooted -- other than the recent (since Nov.) root detecting from Play Integrity checking.

Messing with system files is always a risk -- it has nothing to do with having root access, it's what you choose to do with said access (like messing with system files).

If anything, this is why you take backups before doing anything of the sort -- nandroid reigns supreme but unavailable currently -- or you use proper root backup app options that know how to properly backup and re-implement them (Titanium Backup, Swift Backup). You're not supposed to try and troubleshoot it with tools (PixelFlasher, ADB App Control)

after the fact

and expect to be able to recover all the data -- then blame the tool for not being able to!
[Google Pixel 7 Pro] HippoMan:
I totally agree with @Fishawy, @BunnyPig1, and @simplepinoi177 .

Another way to state the point that all four of us have been making here is this:

If you're careless and inattentive and unwilling learn how to avoid known risky and unrecommended actions associated with rooting an Android device, then you probably should not even try to root any Android phones ... unless you *want* to eventually end up with a hosed device.
[Google Pixel 7 Pro] simplepinoi177:
As great as a resource this thread is, why aren't you posting it in the actual PixelFlasher support thread (we even have a dedicated one for our specific device!)

📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.

This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...

xdaforums.com

Be sure to "@" badabing2003 (i.e.:@badabing2003) so he sees your post. Also, be sure to make a support .zip file and include it (read the OP or the main thread OP to see how).
[Google Pixel 7 Pro] HippoMan:
But keep in mind that if PixelFlasher crashes right away as it's trying to launch, there might not be any support zipfile associated with that crash.
[Google Pixel 7 Pro] humb13:
To the moderators: Please accept my apologies for the wrong place post. When I realized the mistake I tried to delete it and saw no way to do so. Please show me how so that when I make that mistake again I'll be able to fix it. In the mean time can you delete the post for me?

Please pardon my ignorance. :-(
[Google Pixel 7 Pro] badabing2003:
I'm putting this here in case anyone sees the above posts, but doesn't see this.
[Google Pixel 7 Pro] simplepinoi177:
no worries @humb13 . It happens to the best of us sometimes. It wasn't really an admonishment, but a way for me to bring the idea of posting there up for you in the hopes you get a better response there where the developer of it frequents more.

Members can't delete their own posts, but they can report the post requesting deletion (Report button is for any rule breaking or forum maintenance) or are free to edit the post. I have deleted the post as you directed/requested.

Hopefully you get your issue figured out!

simplepinoi177 FSM (Forum Specific Moderator)
[Google Pixel 7 Pro] jova33:
So, I was able to take the OTA with magisk installed. Before rebooting, I installed magisk to the inactive side, and everything worked.
[Google Pixel 7 Pro] simplepinoi177:
Yeah...it's nice that Magisk devs eventually cracked that issue and are able to install to inactive now, huh.... i'm glad it worked out for you...

I recall when panther/cheetah first came out, everyone was attempting to do it that way, but with the change to patching init_boot, it didn't work right and everyone that used to do that method had to figure out another and all helpers had to pretty much inform/declare that to not attempt that method. It was a pretty confusing time....

Sorry, but this comment just brought me back to that time and the instinct against installing to inactive side....
[Google Pixel 7 Pro] mcwups1:
Hey guys. Says Jan 3, but I'm guessing you're still active up to the new updates.

I'm up to date and running well, but have a small issue here.

I flashed a SafetyNet Fix from Magisk, but still see this.

Anyone know of my blunder here?

Thanks
[Google Pixel 7 Pro] JakeDHS07:
You have to enable Zygisk within Magisk settings and reboot
[Google Pixel 7 Pro] justDave:
That is true but it won't help. That module doesn't work anymore. Try this one instead but be sure to read the PIF FAQ.

GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com
[Google Pixel 7 Pro] mcwups1:
Interesting.

Says you need 1 of 3 things. I have Magisk with Zygisk enabled. Not the other 2.

Yet, still doesn't work after flashing in Magisk.

Must be more I need to look at.
[Google Pixel 7 Pro] JakeDHS07:
Probably because you don't have custom fingerprint. Most don't. I use this module

GitHub - chiteroman/PlayIntegrityFix: Fix Play Integrity (and SafetyNet) verdicts.

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com

And the playcurl module here

GitHub - daboynb/PlayIntegrityNEXT

Contribute to daboynb/PlayIntegrityNEXT development by creating an account on GitHub.

github.com

Those two combined has been working for a couple months now
[Google Pixel 7 Pro] mcwups1:
I do have a fingerprint I set up with my phone. Are you talking an extra FP?

I flashed both, did the Termux setup, and still doesn't work.

Seems like a lot of steps just to be able to use apps that know you're rooted.

Gets harder and harder every year.
[Google Pixel 7 Pro] JakeDHS07:
This isn't the same as the fingerprint lock. This is a custom fingerprint for passing play Integrity. Different kind of fingerprint. It certainly does get harder. They intend it too. But the Magisk DenyList and hiding the app still works for me for most apps that need root hidden. Sometimes it's just trial and error or resetting/reinstalling an app after hiding so that it forgets it saw the root 😂
[Google Pixel 7 Pro] samdaman91:
i want to buy a pixel 7 pro that is carrier locked to Mint Mobile. I want to unlock it so that i can use tmobile on it. What steps from this guide should i follow? or is it a different process? or do i need to ask Mint mobile to unlock the device?
[Google Pixel 7 Pro] Slim2none4u:
You will need to ask Mint Mobile to Carrier unlock your phone.
[Google Pixel 7 Pro] samdaman91:
is there anyway to bypass that? i remember i bypassed it with my tmobile oneplus 9 pro. i put the stock firmware on it, it went from LE1217 to LE1215
[Google Pixel 7 Pro] Slim2none4u:
https://www.mintmobile.com/mint-mobile-device-unlock-policy/
[Google Pixel 7 Pro] samdaman91:
i guess thats the only way to get the "oem unlocking" option ungreyed out. there has to another way outside of contacting mint mobile?
[Google Pixel 7 Pro] GuyInDogSuit:
If there was, I would have done it with my T-Mobile 7 Pro already.
[Google Pixel 7 Pro] showstopper1:
currently on a custom rom without root,

can i use android flash tool with wipe device, force flash partitions and lock bootloader options enabled to return to stock firmware ?
[Google Pixel 7 Pro] scorpio76r:
Yes.
[Google Pixel 7 Pro] tomsanity:
Great writeup, thanks! But I think something is missing from the "Make Both Slots Bootable:

Manually

, Flash the OTA Image to Both Slots - One

bootable and rooted

, the other slot

bootable without root

." section. Aren't you supposed to switch between the active boot slots at some point with something like "fastboot --set-active=a" if you're going to distinguish between which one you're flashing to and flash a different thing to each boot slot?
[Google Pixel 7 Pro] badabing2003:
Nope,

OTA flashing does the switching if it is successful.
[Google Pixel 7 Pro] Psychlone:
EDIT: I fixed it.

I have no idea how, but my computer didn't have the latest driver for both adb and fastboot. How does that even change? I've literally updated this phone on this computer every month since the P7P came out!

Anyway, it's all better now.

I've just updated to the latest July update on my P7P.

Somehow I lost root and it shouldn't be a big deal.

I've copied the magisk patched image to the latest platform tools 34 05 folder, restarted to fastboot, opened the command prompt and no matter what, I get a < waiting for device > after fastboot flash init_boot . I've done this a half dozen times.

This is using the same cable and same USB drivers that I literally just updated the phone to the July update with. But I've tried another USB cable as well.

Advice?
[Google Pixel 7 Pro] scorpio76r:
If you are using windows 11 try adding . / before your commands.
[Google Pixel 7 Pro] HippoMan:
From the Magisk thread, concerning Pixel phones ...

Can anyone point me to info about how to get the exact, proper tools for a Pixel 7 Pro that has gotten into serial mode? I got mine into that serial mode state 2-3 months ago, and I now finally have some time to try to fix it.

Thank you in advance.
[Google Pixel 7 Pro] badabing2003:
Take a look at this thread.

Guide: Unbrick Pixel 6 Oriele or Pixel 6 Pro "Raven"

Pixel 6 Pro runs on a Google Tensor CPU which is in fact an Exynos CPU This means that there is Exynos boot recovery in the CPU You can repair the bootloader using the Samsung Exynos Tool Nothing could be flashed from the mode, however it...

xdaforums.com

Not for Pixel 7, but available tools (or lack thereof) apply to all Pixels.

I have never heard of a success story, so I doubt that you'd get far.
[Google Pixel 7 Pro] HippoMan:
I recently started re-using my P7P (just as a "test bed" for various features, modules, etc.). I'm running the latest A14 on this device, and I successfully rooted it with TJW Magisk 27006. It mostly seems to be working OK.

However, I have noticed that PlayStore=>Settings=>General does not contain a "Developer options" entry on this device/OS combination.

Is the lack of Developer options in PlayStore=>Settings=>General some sort of "enhancement" under Pixel 7 Pro A14? Or is there something I must do on this device/OS in order to enable these PlayStore developer options?

Thank you in advance.
[Google Pixel 7 Pro] badabing2003:
No it's there.

Have you clicked on play store version several times to enable it?
[Google Pixel 7 Pro] HippoMan:
Oh, I forgot about clicking on PlayStore version. Yes, that worked.

Thank you.
[Google Pixel 7 Pro] EtherealRemnant:
I mean they charge customers for a board replacement so that's clearly what they're doing. I'm sure they turn around and refurbish the board and use it for the next phone that comes in but out of warranty bricks that I've seen people complain about always mentioned Google charging them for a board replacement. It's very well possible that Samsung doesn't give Google access to their tools seeing how Google is a leaky faucet and everything ends up in public hands.
[Google Pixel 7 Pro] Elastep:
I’ll update you how mine goes :) Interesting experience. But it’s really dumb that there’s no way to re-flash to stock with locked bootloader…
[Google Pixel 7 Pro] foamerman:
Guys got a question. I've been at this for a few days now. I'm having trouble getting root.

1 Bootloader is unlocked

2 SDK is updated

3 Used 2-3 usb cables changed usb slots

But I'm still getting error cannot load magisk_patched-25200_OKTza.img also getting FAILED: (remote partition (init_boot) not found)

What the h#ll am I doing wrong?
[Google Pixel 7 Pro] Lughnasadh:
Are you using the command fastboot flash init_boot <nameofpatchedinit_boot.img>?
[Google Pixel 7 Pro] badabing2003:
Had to ask, I know you're posting in Pixel 7 Pro thread, just making sure, your device is Pixel 7 / 7 Pro?

That partition only exists on Pixel 7 / 7 Pro.

Perhaps post the exact command you're typing and the exact response,

Screenshot can do.
[Google Pixel 7 Pro] foamerman:
Yes fastboot flash init_boot magisk_patched-25200_OKTza,img

Yes Pixel 7 pro

fastboot flash init_boot magisk_patched-25200_OKTza.img First time came up error cannot load magisk_patched-25200_OKTza.img

Second time FAILED: (remote partition (init_boot) not found)

Did I do something wrong?
[Google Pixel 7 Pro] badabing2003:
Can you please issue the command

fastboot --version

See what version you are using?
[Google Pixel 7 Pro] Lughnasadh:
Make sure you don't have any other/older versions of adb/fastboot on your computer and only the latest Platform Tools.
[Google Pixel 7 Pro] foamerman:
Yes I had a older version so I deleted it rebooted and downloaded the new one 33.0.3. Got it all set up. Still got error cannot load magisk_patched-25200_OKTza.img

OK when I ran the code it came up with (unknown option --version)

Ok guys I guess I'm in a pickle lol
[Google Pixel 7 Pro] badabing2003:
You had a typo earlier on , instead of .

Make sure your command is correct.

1- Run the fastboot version check again, make sure it is the latest version, and no other is being picked up.

2- Double check your command

3- If you still get errors, screenshot please.
[Google Pixel 7 Pro] foamerman:
Still got unknown option --version
[Google Pixel 7 Pro] badabing2003:
Please provide the out of these commands

adb --version
fastboot --version
where adb
where fastboot
dir
[Google Pixel 7 Pro] foamerman:
adb --version 1.0.32

fastboot --version unknown option --version

C: \Platform-Tools>
[Google Pixel 7 Pro] badabing2003:
Ok you have a really old version in your path which is being picked up.

You did not provide the results of where adb and where fastboot so that I could tell your where is it being picked up from.

Also I wanted to see the directory contents to make sure magisk_patched is found.
[Google Pixel 7 Pro] foamerman:
OK The sdk files that I downloaded are from AUG 2022 version 33.0.3

adb and fastboot are in Windows C: \Platform-Tools

Here are the directory contents

Ok for some reason I can't post the contents of the dir. so adb fastboot files and magisk_patched-25200_OKTza.img are in the Platform-Tools directory. Is that what your asking?