How To Guide April 2, 2024 AP1A.240405.002 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet

[HiM@L]

If I were to flash factory image with verity disabled. what would the command be?
is it flash factory image then reboot to bootloader again and then, extract vbmeta and run fastboot command for disable-verity?

 

[badabing2003]

If I were to flash factory image with verity disabled. what would the command be?
is it flash factory image then reboot to bootloader again and then, extract vbmeta and run fastboot command for disable-verity?

Edit the flash-all script and on every line that you have fastboot, add the following option

--disable-verity

and if you also want to disable verification, add this too

--disable-verification

You need to make sure you add it right after the fastboot word to be certain you don't insert it wrongly

 

[Lughnasadh]

If I were to flash factory image with verity disabled. what would the command be?
is it flash factory image then reboot to bootloader again and then, extract vbmeta and run fastboot command for disable-verity?

The part you would change in the flash-all.bat file is highlighted in yellow, including removing the -w to preserve data during future updates. Then just run flash-all.bat

@Echo off
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-cheetah-cloudripper-1.0-9231809.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-cheetah-g5300g-220923-221028-b-9229469.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot --disable-verity --disable-verification update image-cheetah-t1b3.221003.008.zip

echo Press any key to exit...
pause >nul
exit

 

[Ytujok]

Hello! Pls, help me, I have communication problems on my p7p, I want to try to install the firmware TD1A.221105.001.A1, although I have an excellent operator from Telia, but suddenly it will help. Can you tell me if it can be done and where to download it?

 

[Ghisy]

⚠
Hmmm, there's an update on the Play Store for "Google Play Protect Service". I'm avoiding this update thinking it might mess up passing Safetynet with the modded USNF module...

 

[nicorvienne]

⚠
Hmmm, there's an update on the Play Store for "Google Play Protect Service". I'm avoiding this update thinking it might mess up passing Safetynet with the modded USNF module...

hi,
i updated and it has no effect passing Saftynet (USNF 2.3.1/kdrag0n-mod Displax) / PlayStore:33.0.16-21[0]

 

[roirraW "edor" ehT]

All: I'm a bit overwhelmed right now with real-life work and other responsibilities. I hope you all can continue to help each other in my absence, and that I don't have to stay away too long. Thank you.

 

[nicorvienne]

All: I'm a bit overwhelmed right now with real-life work and other responsibilities. I hope you all can continue to help each other in my absence, and that I don't have to stay away too long. Thank you.

Hi Dude,

first THX for all and take your time!

 

[vurtomatic]

All: I'm a bit overwhelmed right now with real-life work and other responsibilities. I hope you all can continue to help each other in my absence, and that I don't have to stay away too long. Thank you.

Take care, priorities!

 

[Schroeder09]

what are the ramifications of disabling verity and verification? does this make the phone less secure? does it trip safety net or something? I only ask because ive read through some of the rooting thread. I understand disabling these wipes the phone.

I received my pixel 7 pro yesterday and plan to root with these steps. I'd really like to start my phone up and root it before moving all my data to it. I'm confused about the kernel portion of instructions. It's listed last, but it really happens first in the process, right? Also, the process to get a custom kernel seems really daunting as compared to how it used to be where you just flashed a .zip file in TWRP or magisk. So, the questions are:
1.) do I disable verity and verification first? does this make the phone less secure? if so and there is a fix later so these don't need turned back on will I be able to flip them back ON without wiping the phone?

2.) does the kernel flashing portion happen right after unlocking the bootloader and disabling verity and verification?

3.) after that then proceed with the root instructions?

4.) then let the "welcome to your pixel" stuff start and run on the phone again?

 

[capntrips]

what are the ramifications of disabling verity and verification?

It allows the device to boot with modified partitions. A certain amount of that is allowed by simply unlocking the bootloader. Where exactly the line is drawn seems to be a bit hazy with the Pixel 7, as some modifications with verity and verification enabled require a data wipe and others don't.

does it trip safety net or something?

Simply unlocking the bootloader will trip SafetyNet, so you'll need the fix in any case.

1.) do I disable verity and verification first? does this make the phone less secure? if so and there is a fix later so these don't need turned back on will I be able to flip them back ON without wiping the phone?

Installing a custom kernel is optional, which is why it isn't rolled into the rooting instructions. Since you're already going to have to wipe to unlock the bootloader, you may as well go ahead and disable verity and verification while you're at it.

You can enable verity and verification without a wipe, but if you enable them (or forget to disable them during an upgrade), you'll have to wipe again to disable them.

2.) does the kernel flashing portion happen right after unlocking the bootloader and disabling verity and verification?

3.) after that then proceed with the root instructions?

Disabling verity and verification aside, it is probably easier to root first then install the kernel, since you can just flash the kernel zip with an app.

4.) then let the "welcome to your pixel" stuff start and run on the phone again?

Since you're going to wipe the device after unlocking the bootloader, just skip through the initial setup the first time to get to the box to allow oem unlocking, then go through the actual setup the second time, after wiping for the bootloader unlock and disabling verity and verification.

 

[Schroeder09]

It allows the device to boot with modified partitions. A certain amount of that is allowed by simply unlocking the bootloader. Where exactly the line is drawn seems to be a bit hazy with the Pixel 7, as some modifications with verity and verification enabled require a data wipe and others don't.

does it make the phone any less secure per say though? this reminds me of people getting stuff to work by disabling SELinux, and while people did it, it was not recommended because it made the phone more vulnerable from a security standpoint.

Installing a custom kernel is optional, which is why it isn't rolled into the rooting instructions. Since you're already going to have to wipe to unlock the bootloader, you may as well go ahead and disable verity and verification while you're at it.

You can enable verity and verification without a wipe, but if you enable them (or forget to disable them during an upgrade), you'll have to wipe again to disable them.

will they stay persisted as disabled so long as i flash each month without the "-w" or will i need to remember to disable them every month when flashing security updates?

Disabling verity and verification aside, it is probably easier to root first then install the kernel, since you can just flash the kernel zip with an app.

but to do this I should disable verity and verification at the onset with the fastboot commands before root is installed because if I install root and then disable these, isnt the root and everything I just did undone?

 

[capntrips]

does it make the phone any less secure per say though?

I would say unlocking the bootloader is a much higher security risk. As I said above, what exactly you can get away with changing without a data wipe by only unlocking the bootloader vs also disabling verification is still a bit of an unknown on the Pixel 7. On the Pixel 6, I would have said there was zero additional security risk, since you could flash whatever you wanted, so long as you didn't break a verity device (and you could and still can freely disable verity alone without wiping).

will they stay persisted as disabled so long as i flash each month without the "-w" or will i need to remember to disable them every month when flashing security updates?

You will have to remember to disable them with every update. If you ever forget and boot without them, you'll be forced to wipe to disable them again.

but to do this I should disable verity and verification at the onset with the fastboot commands before root is installed because if I install root and then disable these, isnt the root and everything I just did undone?

Root is persistent through a data wipe, but any changes you make (system setup, app installation, magisk modules, etc) will be lost. That said, yes, if you're going to install a custom kernel, you should disable verity and verification immediately after unlocking the bootloader, since you'll have to do a data wipe after either operation.

 

[T.A.R.D.I.S.]

Hello
I have a fail on the magisk_patched.img flash :
FAILED (remote: partition (init_boot) not found)

I take the last platform tool (r33.0.3), usb drivers on Android studio, flashing factory firmware as it said on tuto (november one).
So, what am i forgetting please?

Edit :
I tested this :
fastboot flash init_boot_b magisk_patched-25200_T9evv.img
And that's pass!!

 

[badabing2003]

Hello
I have a fail on the magisk_patched.img flash :
FAILED (remote: partition (init_boot) not found)

I take the last platform tool (r33.0.3), usb drivers on Android studio, flashing factory firmware as it said on tuto (november one).
So, what am i forgetting please?

Edit :
I tested this :
fastboot flash init_boot_b magisk_patched-25200_T9evv.img
And that's pass!!

replace init_boot_b with init_boot

 

[T.A.R.D.I.S.]

init_boot doesn't pass because i was blocked on slot b. So it passes with init_boot_b command.
When i try to flash factory firmware on the second slot, i have a "failed" too.
That the solution i try to flash the patched init_boot on slot b.

 

[capntrips]

When i try to flash factory firmware on the second slot, i have a "failed" too.

I saw your edit in your first post. Did you resolve this? If not, I just wanted to note another user had the exact same error message last month here. The issue ended up being an old version of fastboot on their PATH.

 

[Fentadroid]

The part you would change in the flash-all.bat file is highlighted in yellow, including removing the -w to preserve data during future updates. Then just run flash-all.bat

@Echo off
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-cheetah-cloudripper-1.0-9231809.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-cheetah-g5300g-220923-221028-b-9229469.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot --disable-verity --disable-verification update image-cheetah-t1b3.221003.008.zip

echo Press any key to exit...
pause >nul
exit

Just one question.
First time you disable verity and verification this way, you need to wipe.... right? (or maybe not..).

 

[capntrips]

Just one question.
First time you disable verity and verification this way, you need to wipe.... right? (or maybe not..).

Yes, a wipe is required. Also, if you ever boot into the system without them disabled (e.g. after an update without the flags or if the device switches to an unpatched slot), you would be required to wipe to disable them.

 

[Lughnasadh]

Just one question.
First time you disable verity and verification this way, you need to wipe.... right? (or maybe not..).

Correct.

EDIT: Oops, seems I've been Ninja'd once again