yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] valeri_s_k:
Well, first scenario doesn't seem possible because xposed is not installed/ used, and only 2 modules were installed from here- VOLTE and Safety net fix. Do not think they were infected.

PC is protected and regularly checked, but who knows- seems possible.

Non direct root- do not know, may be...

The attack started with receiving sms. Just saw a new message and read it. Didn't tap anything inside the message. It was that my Facebook pass was reset. Tried to open Facebook app and couldn't . Reset all, entered and forgot. My fault I didn't pay more attention on this.

Not sure, but I suppose that the sms somehow opened the gate for the further attack. Unlocked bootloader and probably root made it easier.

So, I am not an expert in this matter, just guessing how it could happen and would like to alarm other people to pay more attention on security...
[Google Pixel 7] nikitasius:
Well, rooted device with magisk will ask you every time for root access for new apps.

Also system apps are system apps ran by system, here i idk which access they have.

All what related to SMS is vulnerable to SS7 attacks. Also if you had FB app AND you got an SMS with kind of code AND you gave all access to FB app AND probably FB app (it will) was triggered by your SMS and used the code AND probably it;s broken flow in FB app if someone else got changing pwd confirmed and not you. Thats a theory.
[Google Pixel 7] humb13:
I don't know as much about any of this as the rest of you guys, but the point you make is correct. By default Magisk grants root access only when you authorize it. In order for the attacker to get root access he has to break into your phone and essentially tell Magisk to grant him root access. He can't give himself root access without breaking in.

I've had rooted phone forever and I've never had any issue. Maybe the Facebook app spits out all kinds of private information nobody should know.
[Google Pixel 7] nikitasius:
me also. I run rooted phones since 2013, when it was 1st root for my nexus4 (which is still alive btw).

But before we had root via exploits, now it's via patching boot/init_boot.

So i never had viruses or any issues, also i never had facebook on my phone.
[Google Pixel 7] valeri_s_k:
Well, I also ran rooted phones for years and never had issues. Probably that made me less careful....

I suppose will never find out how tha attack was done, but for now I will keep the phone stock - there should be reasons why banking apps are checking safety net and we have to apply fix to make them working...

The most possible scenario is that the phone was infected during the process of FB pass reset from my side... Probably it could happen on a fully stock phone, but I still think that unlocked bootloader and/or root made the hacking easer.

One thing is wondering me - how my phone was targeted immediately after rooting - coincidence or ....

@nikitasius

FB seems to be one most attacked profiles, so you may be right of keeping it away from your phone...

Anyway my friends, be careful when doing something on your phones, not to learn that in a hard way as me....
[Google Pixel 7] nicorvienne:
Not knowing how this Pixel device was rooted, this security warning is unnecessary (!!Rooting is alwas a risk!!)

There are countless pages on the web that give false or misleading recipes for rooting and obviously do not link to the original source of "MAGSIK". [eg: SELINUX enforcing --> permissive]
[Google Pixel 7] nikitasius:
yep, always is better to get from the official github
[Google Pixel 7] valeri_s_k:
Everything was downloaded from official sourses... I am not that much stupid or inexperienced...

Obviously I missed something in the first monent of FB attacking. And the moment af the attack bothers me too- immediately after bootloader unkock/ root.

Everyone could decide to get or dismiss the warning. Everyone also couldn't explain how stupid I am, but for me this is the end of discussion.
[Google Pixel 7] matrix0027:
I used the 'debloater' magisk module to remove YouTube. When I rebooted, YouTube was still installed but it was no longer a system app which allowed me to uninstall it. And then installed YouTube from vanced manager with no issue.
[Google Pixel 7] SOCOM-HERO:
Used Pixel Flasher, worked perfectly. Will make things much easier as monthly updates come through.
[Google Pixel 7] Ma61187:
Interesting I couldnt even install the update regardless of what I tried. I even flashed the stock init_boot.img to be unrooted and tried installing the update.
[Google Pixel 7] nujackk:
disregard, i've been told it doesn't work.
[Google Pixel 7] SR3TLAW:
Have you been able to confirm this? I'm considering rooting my Pixel and this is my largest worry.
[Google Pixel 7] SOCOM-HERO:
If you use the corrected version of it from @Displax , yes.

Releases · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Displax/safetynet-fix

github.com

The P7P forum is your best friend here, most of the root specific guides are available there. Just choose Panther instead, as that is the P7 codename.
[Google Pixel 7] SR3TLAW:
Ok that makes sense. So most of the Pixel 7 Pro development, command-line stuff and guides also apply to our standard Pixel 7 ?

Also - should I expect to frequently see links to GitHub? Seems a lot has changed since I last rooted my Moto X devices years back!
[Google Pixel 7] SOCOM-HERO:
yes, almost 100% applicable to the P7 short of the flashing file itself being device specific. Updates are usually monthly. There are some great guildes there and if you aren't sure plenty of folks to help out. I used a GUI tool called PixelFlasher to root since I was having some driver issues early on to flash/root. But I always manually unlock the bootloader through CMD line.
[Google Pixel 7] humb13:
Why do you go through all that to remove Youtube, or any other system app for that matter? There are apps that can do that for you if you're rooted. My favorite is App Manager. Go here and check it out. It'll disable or remove ANY system app you don't want, not to mention other features. You can also use it on non-rooted phones without root permissions.

Incidentally, I don't recommend removal. Disabling is better. First, you never know when you might need it, and and second, when there is a system update these apps will be restored. This forces you to repeat the procedure. If they're disabled they'll stay disabled.
[Google Pixel 7] matrix0027:
Because I wanted to remove YouTube so I can reinstall a custom version (YouTube Vanced) which has a version number slightly prior to the version installed . If the app is disabled , it will reenable when installing the Vanced version and not allow the install of a lower version .

As far as "you never know when you might need it"... This is done systemlessly through Magisk so disabling Magisk or simply disabling the "debloater" Magisk module will restore any changes .
[Google Pixel 7] humb13:
Thanks for answering me. Honestly I had no idea there was a better mousetrap. You learn something new every day. I went to magiskroot.net and picked up the files. Do you:

1) Click on the apk to install Magisk

2) Use it to remove Youtube -- uninstall if it becomes a non-system app.

2) Install the zip via Magisk's module installer

Am I missing something or is this correct?

What is the difference between Youtube Vanced and Revanced?

When an installation comes down the pipe, will it reinstall Youtube and force you to repeat the procedure?

BTW someone here promoted me to Senior Member. I'm honored. :)
[Google Pixel 7] hammered58:
I did a re-edit for ota if anyone is interested!!
[Google Pixel 7] Cpm0813:
I don't know what I am doing wrong, but the root process isn't working. Following the steps on https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-7-pro/. I unlocked the bootloader. But when I try to flash the IMG file that was patched by Magisk, I keep getting "FAILED (remote: partition (init_boot) not found)".
[Google Pixel 7] hammered58:
Sounds like maybe the path to the init_boot is wrong, I just drag and drop the file I want flashed into the adb command promt "fastboot flash init_boot patched.img, If that doesn't work double check that it is the init_boot your patching
[Google Pixel 7] Cpm0813:
I used PixelFlasher to restore the phone back to stock. Then I used the Canary build of Magisk to patch the init_boot file. Finally, I had to use Step 7 from here, https://www.droidwin.com/root-pixel..._Pixel_7Pro_using_Magisk_Patched_Init_Bootimg, to get it to work. I had to individually flash init_boot_a and init_boot_b to flash the individual slots.
[Google Pixel 7] mat-sie:
Good tutorial that worked for me (I am not related to the author of these videos):

Bootloader Unlock Tutorial

Root Tutorial with Magisk
[Google Pixel 7] jmalenko:
Hello,

I just root my Pixel 7.

I followed the intructions at https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-7-pro/ which are exactly the same as in this thread, on practical level.

Though, there are some tips that I want to add for beginners. These are just clarifications.

- The image you want is NOT the OTA image (in this list: https://www.xda-developers.com/how-to-download-android-13/ ) nor Flash (in this list: https://developers.google.com/android/images#panther ).

- Use Magisk canary (using stable doesn't work, you$ill be stucked in bootloader with a "reason to enter" something like "cannot boot"). Trying to get over this got me to this thread and only tried this after @Cpm0813 explicitely mentioned Magisk canary (using init_boot without _a or _b worked for me).

Happy rooting.

J.
[Google Pixel 7] bizkit_120:
Thanks for sharing, one question,i see some other guide mentioned something adb update flash all .bat.. your steps doesn't have those,are these not required ?
[Google Pixel 7] hammered58:
I would have to see in what situation or step they are using it, usally thats for factory image restore, afaik
[Google Pixel 7] bizkit_120:
Newbie to Pixel family, current run everything out of box, going to root once understand it better..I use Samsung and OnePlus prior to switch..I don't remember I ever use flash all bat per my previous experience.

https://xdaforums.com/t/december-5-...r-root-pixel-7-pro-cheetah-safetynet.4502805/

This is the post I was referring to, step 7 and 10 i don't know why it's necessary..
[Google Pixel 7] bizkit_120:
**** Update: Never mind,I figured..****
[Google Pixel 7] bizkit_120:
👍 Great detail explanations. No sure if you ever use intune company Portal..it's a hard one,are you able to successfully avoid intune detect ur device root status?
[Google Pixel 7] humb13:
What is intune company portal? Is that an app that won't work on rooted phones? If so, my advice is to install Shamiko and add it to the list of apps that won't work with root. The 3 I have work perfectly despite the phone being rooted.
[Google Pixel 7] happynexuss:
Intune is a pain to get to work right. I had to install Shamiko then add Company Portal (Intune) to Magisk > Settings > Configure DenyList making sure to 100% deny it. Then add Autenticator, Teams, Outlook, Google Play Services, and Google Play Store to the list. If you opened any of those apps before setting this up you'll have to delete all data in them or they'll report root. I think I set it up right because it works. But I keep the Magisk > Settings > Enforce DenyList turned off because Shamiko module is turned on and enforcing the DenyList (that took me a while to realize).
[Google Pixel 7] happynexuss:
I'm also running the MagiskHide Props Config and Universal SafetyNet Fix modules... I think this was the thread that helped me get it running https://xdaforums.com/t/tutorial-ro...t-intune-to-make-it-work-with-magisk.4402273/ but it seems people are having issues currently (I haven't noticed any)
[Google Pixel 7] bizkit_120:
👍Noted..will try this approach.thanks
[Google Pixel 7] humb13:
If what you're trying to do is hide root, all you need is Shamiko. Once you install it, reboot immediately. Then back to Magisk to the settings cog on the upper right.

Zygisk should be enabled. Enforce Denylist disabled. Then press Configure Denylist and select the apps you want to hide root from. Check if the app works. If not, reboot and try again. It should work now. The only modules I have are Shamiko, Seamless Hosts and Youtube Revanced and I have no complaints. All my non-root only app work without a hitch and so does everything else. Just keep in mind rebooting is important. I'm under the impression Shamiko and it's settings don't fully load unless there's a reboot.
[Google Pixel 7] GoodSoul:
https://xdaforums.com/t/thread.4402273/ - Tutorial has been updated. Also noted that Shamiko makes it work again. Follow the updated guide and Teams etc should work again. Enjoy.
[Google Pixel 7] Regys:
Hi, you fine ?

Root exist for Pixel 7
[Google Pixel 7] V0latyle:
My friend, you've been around long enough to know better. Your question does not belong in this thread. Root on the Pixel 7 is achieved in much the same way as previous Pixels, except that instead of patching boot.img, you must patch init_boot.img.
[Google Pixel 7] Regys:
I just wanted to know if you did. :)

Thanks !
[Google Pixel 7] bizkit_120:
Thanks y'all , indeed it works! 👍
[Google Pixel 7] Ganzdroid:
Hello everybody.

I'm going to ask the noob questions and i'm sorry for that.

I rooted many phones but the last one was maybe 10 years ago, so plaese... be gentle :/

1) if i root the P7 (without changing ROM) will i get the OTA updates of the official google ROM?

2) is root reversable without a factory reset?

3) does root block some apps (video app, banking app, ecc)?

4) Is there a way with rooted phone to get full screen app and not cropped video?

Thanks
[Google Pixel 7] EduardBT:
Hi, there are some backing apps (even meal vouchers apps) that don't work on a rooted phone. (in my case I had to revert back the root for my Pixel 7 because of this)
[Google Pixel 7] p4ra:
1. Yes, but you have to do it manually. Either by sideloading or using PixelFlasher tool (very easy to do).

2. No.

3. Yes, but there are ways around it with using some mods after installation of Magisk.

4. Can't say. Not been an issue for me.
[Google Pixel 7] donniegalaxy2:
I just got my P7 from Xfinity. Upon entering Developer Option, OEM UNLOCK is greyed out amnd won't turn on. Any work around for that?
[Google Pixel 7] teddysx3:
Hello everyone, I'm afraid I'm in the boot loop. I did everything as listed above...

I have tried rooting my Pixel 7 running android 13. I have downloaded my current build number. Unlocked the boot loaded, got the init_boot.img file and ran it through magisk. After that I loaded that file onto with fastboot, and got the boot failure. Then I tried loding with fastboot flash boot back the init_boot.img file, does't work. I also tried the boot.img file too, but this doesn't also work... Any ideas how I can fix this? Have I bricked it or is there a way to get out of this boot loop. I read somewhere that there are slot's for the boot's and init_boot, but I don't know how to manually put them there...
[Google Pixel 7] teddysx3:
I think I know what I did wrong. I was watching a pixel 6 rooting video, but I knew and did the init_boot.img file. The problem I have done is at the end, i have placed this command. fastboot flash boot magisk.img, I have placed the magisk init file on the boot.img on the file, I should have done fastboot flash init_boot magisk.img to my udnerstanding....So Now I tried to flash back the stock boot.img to the boot_b, as this was used, and not I get NO COMMENT android logo with red exclemation mark...
[Google Pixel 7] teddysx3:
I was able to get into recovery mode, somehow wow....after trying to flash the original boot and init_boot, got into fastboot mode, then it tried to boot, held the volume down button and somehow it worked!!! What didn't work was choosing "Recovery Mode" from the fastboot, never worked, wow what a loooooop
[Google Pixel 7] BajaBlast4Life:
My Pixel 7 came with Android 13 out of the retail box. The default boot slot was A. I flashed the patched Magisk file and it resulted in a bootloader bootloop where you restart the phone and it keep rebooting back into the bootloader screen. I came across this YouTube video:

and saw his device was on boot slot B.

Use this command in ADB to change from boot slot A to B before you flash the patched Magisk file.

fastboot --set-active=b

If you flashed the patched Magisk file to boot slot A, you can fix the problem by going to https://developers.google.com/android/images#panther and downloading the "flash" version. This is where you will use Chrome internet browser to restore your device. Make sure to select "keep data" because this will remove the boot failure error.
[Google Pixel 7] Juza89:
I have a problem with rooting my Pixel 7. have done it many times before on older phones using twrp and such, but this new method does not seem to be working for me.

Bootloader is unlocked and usb debugging works fine.

Problem is that i simply cant get root access with magisk.

First I tried patching the init.boot file with magisk and flash it. -> remote partition not found.

then i separately flashed it to init_boot_a and init_boot_b. -> flashing works but still no root.

Then i found the "patch the boot.img" method. tried that also. flashed it to both boot slots. still no root.

I have also tried to boot the patched magisk_modified_boot.img from fastboot but still no root. what am I doing wrong here?
[Google Pixel 7] simplepinoi177:
Flashing Magisk through TWRP was so much simpler in the past, I do miss TWRP a lot....but I fear they will never catch up to the current version of Android as once they seem to finally support it, a new version of Android comes out which it won't work with; I don't blame them though, as I understand it, they don't find enough testers and code-writers when a new Android version comes out each time....

It's not like the older devices where you can temporarily boot with root anymore; fastboot boot magisk.img will no longer allow you to boot temporarily with root -- at least with Pixel 7's.

What is the exact command syntax you are exactly inputting in your cmd/powershell? What does it return when you enter it? I'm thinking that's where things might be going wrong...
[Google Pixel 7] Juza89:
Ok I got it to work. Some problem with magisk installed on nonrooted pixel or something.

Or the fact that it was canary -version.

Uninstalled magisk from pixel 7.

Uploaded init.boot to old OP6 with root and magisk 25.2 stable installed already. Patched init_boot with old phones magisk.

Flashed the patched init_boot to pixel 7 slot a with no magisk installed beforehand and now it seems to work!

Problem solved.
[Google Pixel 7] doggydog2:
Also got delayed by canary version (use stable) and also flashing into boot instead of init_boot:)

I noticed a great function in the dev settings: hide notch in OnePlus6 style. So the clock is next to notch, but apps don't expand to it. Choice: "Render apps below cutout area". Good.

After 10minuts, gesture navigation stops working in all recent builds. Fingerprint icon is positioned wrong. That's two issues i've got so far.
[Google Pixel 7] Magnivore:
I'm in the same spot at hammered was. I wasn't making progress with this tutorial as there were a bunch of steps missing, though thanks to a post linked by rspkt in the second page it started to help. Once I got to the final steps this same thing happened to me; boots to the fastboot page and says it can't be trusted, says something about it being corrupt, and then boots to just showing the Google logo. My computer is no longer able to detect the device so I can't flash the default boot image to it from Google's page.

Anyone have any advice on how I can fix this?
[Google Pixel 7] simplepinoi177:
So you can't boot into bootloader/fastboot mode?
[Google Pixel 7] Magnivore:
It boots to a bootloader-type screen where it says it can't be trusted and wants me to press the power button to continue, then after that it shows another similar screen with a message saying the bootloader is unlocked and may vulnerable to attackers that automatically continues unless I press the power button to pause, then the Google logo.

So no it's not the normal bootloader screen with the ability to cycle boots that also has info on the bottom left.
[Google Pixel 7] simplepinoi177:
can you boot into bootloader/fastboot mode using the button combination? Power+Vol-Down at the same time from when the phone is off...

*You may need to hold down for what seems an inordinate amount of time; I would say as high up to 2 whole minutes...

If you can get into bootloader/fastboot mode, we should be able to correct this well enough; either enabling verity & verification and/or by flashing a Full Factory image to try and reset all the necessary partitions and permissions...
[Google Pixel 7] Magnivore:
I will try it when I get a break at work. Assuming it does work then what are my steps from there?
[Google Pixel 7] simplepinoi177:
There wouldn't be much you could do until you can connect your device to your computer so you could attempt to enable verity &/or verification (which I believe might be the issue), or try to correct the boot partition by flashing older & newest boot images which might be the cause of said "can't be trusted" "being corrupt" error message...
[Google Pixel 7] Magnivore:
Got it. A quick look does show that Vol + Power does get it to the fastboot menu so that's good.
[Google Pixel 7] Magnivore:
Now that I'm plugged in my computer isn't detecting the phone. The pixel is on the fastboot mode menu, unlocked, but adb devices doesn't show it's plugged in.

Okay the computer is detecting it but I can't send commands to it. Okay it does detect it but it's in recovery mode right now. Is there a way I can flash a new version of the OS onto it form the computer? I feel like the phone doesn't have an OS.
[Google Pixel 7] simplepinoi177:
Don't worry about adb devices not showing...in fastboot mode, it doesn't show up as Android Composite ADB Interface, but should show up as Android Bootloader Interface.

I just want to confirm, you are not in "Recovery Mode" correct? Because there is a Fastboot/Bootloader Mode, FastbootD Mode, and a Recovery Mode...

It needs to state "Fastboot Mode".

I thought you stated that you followed THIS GUIDE? It should be the same steps...

But after checking, you were following the steps for the Pixel 7 Pro -- you may have took things too literally and accidentally flashed the Full Factory images for cheetah(Pixel 7 Pro) instead of panther(Pixel 7 non-Pro; your device; this forum). This may be why you ran into trouble.

In this case, it seems that you may not be too knowledgeable & familiar with this and I would suggest that you download the Full Factory image for panther

HERE

and use THIS TOOL: PixelFlasher to flash. You'll need the .zip file (Full Factory image)I had you download. Make sure to check "keep data" or "don't wipe" (sorry, can't remember from memory), and be sure to use platform-tools version r33.0.3;

not

r34.0.0 or higher -- PixelFlasher will warn you about this anyways, but I wanted to make sure to warn you about it here as well...

And then after you load into the OS, if you are still interested and

I strongly suggest

you research more(!), you can use the same tool to root.

Doing these should "flash [the] new version of the OS" onto your device; basically it will re-establish your OS as your OS may be corrupted/missing(in a sense).
[Google Pixel 7] Magnivore:
After some intense research I happened across a site that helped me to sideload the original (actually updated) OS so I'm back to normal, except with an updated build and my bootloader unlocked.

You're right I did follow that guide, though I didn't use the 7Pro's software. I know my way around a computer decently but rooting a phone is new to me, so give me a bit of credit.

I also tried playing with the PixelFlasher though it wouldn't detect my phone despite the phone being on route to root (bootloader and unlocked, detected by the computer) but maybe it was because I was using the newest platform tools. Unsure about that part of it yet, I'll have to mess with it when I get home.