How To Guide Rooted my Pixel 7

[Regys]

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.

I just wanted to know if you did.

Thanks !

 

[bizkit_120]

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.

Thanks y'all , indeed it works!

 

[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

 

[EduardBT]

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

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)

 

[p4ra]

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

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.

 

[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?

 

[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...

 

[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...

 

[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

 

[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.

 

[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?

 

[simplepinoi177]

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?

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...

 

[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.

 

[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.

 

[Magnivore]

You didn't try the steps I listed as I never said to flash a rooted bootloader

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?

 

[simplepinoi177]

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?

So you can't boot into bootloader/fastboot mode?

 

[Magnivore]

So you can't boot into bootloader/fastboot mode?

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.

 

[simplepinoi177]

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.

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...

 

[Magnivore]

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...

I will try it when I get a break at work. Assuming it does work then what are my steps from there?

 

[simplepinoi177]

I will try it when I get a break at work. Assuming it does work then what are my steps from there?

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...