How To Guide January 3, 2023 (TQ1A.230105.002 - Global / .A1 Telstra) - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet

[badabing2003]

You don't need to. Some like to root both slots but I prefer to have my inactive slot unrooted just to eliminate any possibilities of a bootloop caused by a Magisk mod or the like.

I on the other hand have them both rooted.
I always alternate, ie each month I flash to the inactive slot (similar to what OTA does)
My thought process is that, if my current slot is bootable and functional (even rooted)
If I flash to inactive slot, one of two things can happen.
1- It works, which is the typical scenario, and wonderful
2- It fails to boot, something is not right (thankfully does not happen often), in which case the system will boot back to the previously active slot, which we know is still good, and gives me chance to figure out what might be going wrong.

I do understand the possibility of adding a Magisk module that could break booting to both slots, as /data/adb/magisk/modules is common to both, but I personally don't play with too many modules, and if this actually happens, I know I can flash stock boot to one of the slot and get out of it.

If I have to keep one slot stock, the process is quite lengthier if I also want to alternate slots.

Just my two cents,

 

[whitewallman]

I on the other hand have them both rooted.
I always alternate, ie each month I flash to the inactive slot (similar to what OTA does)
My thought process is that, if my current slot is bootable and functional (even rooted)
If I flash to inactive slot, one of two things can happen.
1- It works, which is the typical scenario, and wonderful
2- It fails to boot, something is not right (thankfully does not happen often), in which case the system will boot back to the previously active slot, which we know is still good, and gives me chance to figure out what might be going wrong.

I do understand the possibility of adding a Magisk module that could break booting to both slots, as /data/adb/magisk/modules is common to both, but I personally don't play with too many modules, and if this actually happens, I know I can flash stock boot to one of the slot and get out of it.

If I have to keep one slot stock, the process is quite lengthier if I also want to alternate slots.

Just my two cents,

Thank you.
I'm a bit confused..
To flash both partitions, after flashing the active partition, which is a, before flashing the 2nd partition, do I use the command:
fastboot --set-active=other or fastboot --set-active=b?
Then, once 2nd partition is flashed, do I go back to partition a via fastboot --set-active=a?
My ultimate goal is to stay on a which is how it came out of the box.
I've never flashed a monthly update before on anything other than the active partition, so this optional step is new to me, so pardon my ignorance here.

 

[badabing2003]

Thank you.
I'm a bit confused..
To flash both partitions, after flashing the active partition, which is a, before flashing the 2nd partition, do I use the command:
fastboot --set-active=other or fastboot --set-active=b?
Then, once 2nd partition is flashed, do I go back to partition a via fastboot --set-active=a?
My ultimate goal is to stay on a which is how it came out of the box.
I've never flashed a monthly update before on anything other than the active partition, so this optional step is new to me, so pardon my ignorance here.

both methods would work, make sure you do fastboot reboot bootloader after switching the slot.
and you don't have to go back to a, considering that both a and b are now identical.
I understand that you want to stay on a, but truly there is no difference if the current slot is a or b if they have the same content.
Let's say that you do that, you go back to a
Next month you flash a, and it all goes well, and you do this for several months, and one day something goes wrong during flashing a, and the system boots you to b
your b is several months behind a, whereas if you alternate each month (ie just flash to inactive slot) then your other slot is at most one month behind, which is better if things go wrong.
Of course, if you find switching slots too much effort, you're still good flashing only a, as long as you make sure b is functional.

 

[whitewallman]

both methods would work, make sure you do fastboot reboot bootloader after switching the slot.
and you don't have to go back to a, considering that both a and b are now identical.
I understand that you want to stay on a, but truly there is no difference if the current slot is a or b if they have the same content.
Let's say that you do that, you go back to a
Next month you flash a, and it all goes well, and you do this for several months, and one day something goes wrong during flashing a, and the system boots you to b
your b is several months behind a, whereas if you alternate each month (ie just flash to inactive slot) then your other slot is at most one month behind, which is better if things go wrong.
Of course, if you find switching slots too much effort, you're still good flashing only a, as long as you make sure b is functional.

Thanks for your clarification! Since I've been updating only the active partition (a) and applying magisk_patched each month, I assume then that partition b is the factory image that the phone came with.. So I see the advantage of flashing both, or alternatively each month so the "emergency" partition isn't too outdated. So then, the fastboot --set-active=other is a part of the monthly update task after the normal update process. And just to make sure, fastboot --set-active=other command alternates between partitions rather than specifying a or b, correct?

 

[badabing2003]

Thanks for your clarification! Since I've been updating only the active partition (a) and applying magisk_patched each month, I assume then that partition b is the factory image that the phone came with.. So I see the advantage of flashing both, or alternatively each month so the "emergency" partition isn't too outdated. So then, the fastboot --set-active=other is a part of the monthly update task after the normal update process. And just to make sure, fastboot --set-active=other command alternates between partitions rather than specifying a or b, correct?

Just to be super clear.
if your device has never taken an OTA update, then most likely your device's b partition is still in the state it shipped from the factory, which probably means it's not bootable.

So one time only, make sure you flash both slots.
You just have to add

--slot all

to flash_all script on every line that there is fastboot, put it right after the fastboot (with space)

Moving forward (next month)
You first do

fastboot --set-active=other
fastboot reboot bootloader

Before doing the flash_all, so that flash_all applies to the inactive slot (doing it after is no good)

 

[whitewallman]

Just to be super clear.
if your device has never taken an OTA update, then most likely your device's b partition is still in the state it shipped from the factory, which probably means it's not bootable.

So one time only, make sure you flash both slots.
You just have to add

--slot all

to flash_all script on every line that there is fastboot, put it right after the fastboot (with space)

Moving forward (next month)
You first do

fastboot --set-active=other
fastboot reboot bootloader

Before doing the flash_all, so that flash_all applies to the inactive slot (doing it after is no good)

Thanks again, and thank you for your patience!

 

[whitewallman]

Just to be super clear.
if your device has never taken an OTA update, then most likely your device's b partition is still in the state it shipped from the factory, which probably means it's not bootable.

So one time only, make sure you flash both slots.
You just have to add

--slot all

to flash_all script on every line that there is fastboot, put it right after the fastboot (with space)

Moving forward (next month)
You first do

fastboot --set-active=other
fastboot reboot bootloader

Before doing the flash_all, so that flash_all applies to the inactive slot (doing it after is no good)

And before I run the script, Once, the flash-all bat should read:
PATH-XPATHX;"%SYSTEMROOT%\System32"
fastboot --slot all flash bootloader bootloader-cheetah-cloudripper-1.8-9070028.img
fastboot --slot all reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot --slot all flash radio radio-cheetah-g5300g-220908-220908-b-9840061.img

fastboot --slot all reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot --slot all update image-cheetah-td1a.220804.031.zip

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

exit

 

[badabing2003]

And before I run the script, Once, the flash-all bat should read:
PATH-XPATHX;"%SYSTEMROOT%\System32"
fastboot --slot all flash bootloader bootloader-cheetah-cloudripper-1.8-9070028.img
fastboot --slot all reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot --slot all flash radio radio-cheetah-g5300g-220908-220908-b-9840061.img

fastboot --slot all reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot --slot all update image-cheetah-td1a.220804.031.zip

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

exit

I don't know what this line is doing
PATH-XPATHX;"%SYSTEMROOT%\System32"

You can remove the --slot-all from reboot command, although it is harmless if you keep it in.

I personally remove the exit line, so that in case anything goes wrong and I touch the keyboard, the window does not disappear on my and I get to review the errors.

 

[Lughnasadh]

So one time only, make sure you flash both slots.
You just have to add

--slot all

to flash_all script on every line that there is fastboot, put it right after the fastboot (with space)

Does the --slot all command work on this device while updating the whole image? For the Pixel 6 series we couldn't put the --slot all command in the update line of the flash-all.bat file because we would get an error saying the file was too large (or something to that effect). The command worked for flashing individual images/partitions, but not when flashing/updating the whole system.

Have things changed with the Pixel 7 series?

 

[whitewallman]

I don't know what this line is doing
PATH-XPATHX;"%SYSTEMROOT%\System32"

You can remove the --slot-all from reboot command, although it is harmless if you keep it in.

I personally remove the exit line, so that in case anything goes wrong and I touch the keyboard, the window does not disappear on my and I get to review the errors.

Excellent! Thanks again! And it's cool to remove the -w (which I did) to avoid a wipe on both partitions, correct?

 

[badabing2003]

Does the --slot all command work on this device while updating the whole image? For the Pixel 6 series we couldn't put the --slot all command in the update line of the flash-all.bat file because we would get an error saying the file was too large (or something to that effect). The command worked for flashing individual images/partitions, but not when flashing/updating the whole system.

Have things changed with the Pixel 7 series?

You're right, I forgot all about that, sorry I'm guilty, I don't manually modify the script
@whitewallman
You can't add --slot-all to the update image line

Your can refer to this as template, this one works to flash both slot.
In fact it even allows you to flash the patched file before rebooting to system

@ECHO OFF

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot.exe --slot all  flash bootloader bootloader-xxx.img
fastboot.exe reboot-bootloader 
ping -n 5 127.0.0.1 >nul
fastboot.exe --slot all  flash radio radio-xxx.img
fastboot.exe reboot-bootloader 
ping -n 5 127.0.0.1 >nul
fastboot.exe  --skip-reboot update image-xxx.zip
echo Switching active slot to the other ...
fastboot.exe --set-active=other
echo rebooting to bootloader ...
fastboot.exe reboot bootloader
ping -n 5 127.0.0.1 >nul
fastboot.exe  --skip-reboot update image-xxx.zip
echo rebooting to bootloader ...
fastboot.exe reboot bootloader
ping -n 5 127.0.0.1 >nul
echo flashing Magisk patched image ...
fastboot.exe --slot all  flash init_boot magisk_patched_xxx.img
echo rebooting to system ...
fastboot.exe reboot

 

[simplepinoi177]

Just to be super clear.
if your device has never taken an OTA update, then most likely your device's b partition is still in the state it shipped from the factory, which probably means it's not bootable.

So one time only, make sure you flash both slots.
You just have to add

--slot all

to flash_all script on every line that there is fastboot, put it right after the fastboot (with space)

Moving forward (next month)
You first do

fastboot --set-active=other
fastboot reboot bootloader

Before doing the flash_all, so that flash_all applies to the inactive slot (doing it after is no good)

So, I'm like whitewallman and have never done a flash-all to an inactive slot on my Pixel 2 XL or Pixel 5, so I also am unfamiliar with the practice and the benefits until now.
I have never taken an OTA, but I did flash the .031 in September and then the November full factory image a couple of weeks ago; does that count as taking the OTA and my inactive slot is still not bootable as it's still in the "state it shipped from the factory"?
If I never did the slot-all when I initially flashed the .031 full factory image, would anything bad happen if I were to do the slot-all with the next update (December)? Or would it be better to start with the flashing alternate slots and flash the December full factory image onto the other/inactive slot?--or would that be bad since I never did the slot-all initially before the first .031 update?

 

[badabing2003]

So, I'm like whitewallman and have never done a flash-all to an inactive slot on my Pixel 2 XL or Pixel 5, so I also am unfamiliar with the practice and the benefits until now.
I have never taken an OTA, but I did flash the .031 in September and then the November full factory image a couple of weeks ago; does that count as taking the OTA and my inactive slot is still not bootable as it's still in the "state it shipped from the factory"?

No it does not count as OTA, I asked about OTA because OTA flashes to inactive slot, unlike flash_all script which flashes to the active slot.
One slot at a time issue discussed above is only applicable to Pixel 6 and newer devices, for your older devices, you can safely flash both slots with --slot-all option if you wanted to.

If I never did the slot-all when I initially flashed the .031 full factory image, would anything bad happen if I were to do the slot-all with the next update (December)? Or would it be better to start with the flashing alternate slots and flash the December full factory image onto the other/inactive slot?--or would that be bad since I never did the slot-all initially before the first .031 update?

I suggest you do slot-all option instead of inactive option, because for inactive option you need to boot to it, and if your system is not bootable on that slot, it won't work.
once you do flash to both slots, then you can start doing the inactive flashing on subsequent months.

And yes you can wait for next Month's release and do it then, you don't have to do it now.

 

[renzgy]

@xike456 hello, what method did you used through Magisk or changing device sku only?

 

[xike456]

@xike456 hello, what method did you used through Magisk or changing device sku only?

I only changed device SKU. After that the camera app will show option to turn off shutter sound

 

[renzgy]

I only changed device SKU. After that the camera app will show option to turn off shutter sound

Okay. same HarryShan did. Anyway what app hex editor did you used because I have also Japan version and I want to do the same like you did. I hope you can help me I know already how to root the phone or unlock bootloader only my problem this shutter sound option in camera. And I never try using any hex editor application in PC. And which SKU model did you change?

 

[xike456]

Okay. same HarryShan did. Anyway what app hex editor did you used because I have also Japan version and I want to do the same like you did. I hope you can help me I know already how to root the phone or unlock bootloader only my problem this shutter sound option in camera. And I never try using any hex editor application in PC. And which SKU model did you change?
View attachment 5763721

Mine changed from GFE4J to GE2AE. I use vscode with hex editor extension on PC. Just search and replace string in Hex editor

 

[renzgy]

Mine changed from GFE4J to GE2AE. I use vscode with hex editor extension on PC. Just search and replace string in Hex editor

ok. Thank you!
I will try flashing the SKU. And one question if we change SKU still we can receive OTA update from Google?

 

[whitewallman]

You're right, I forgot all about that, sorry I'm guilty, I don't manually modify the script
@whitewallman
You can't add --slot-all to the update image line

Your can refer to this as template, this one works to flash both slot.
In fact it even allows you to flash the patched file before rebooting to system

@ECHO OFF

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot.exe --slot all  flash bootloader bootloader-xxx.img
fastboot.exe reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot.exe --slot all  flash radio radio-xxx.img
fastboot.exe reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot.exe  --skip-reboot update image-xxx.zip
echo Switching active slot to the other ...
fastboot.exe --set-active=other
echo rebooting to bootloader ...
fastboot.exe reboot bootloader
ping -n 5 127.0.0.1 >nul
fastboot.exe  --skip-reboot update image-xxx.zip
echo rebooting to bootloader ...
fastboot.exe reboot bootloader
ping -n 5 127.0.0.1 >nul
echo flashing Magisk patched image ...
fastboot.exe --slot all  flash init_boot magisk_patched_xxx.img
echo rebooting to system ...
fastboot.exe reboot

Thank you for all your assistance!
So... Starting with the next update, if I start with:
fastboot --set-active=other
fastboot reboot bootloader
Before my monthly update ritual, I'm basically replicating the OTA process in that I'm alternating partitions each month and my backup partition should always be a month behind, and a known working setup. Does that sound correct?
I'm just trying to simplify the monthly update process to avoid forgetting a step.
Thanks again!

 

[badabing2003]

Thank you for all your assistance!
So... Starting with the next update, if I start with:
fastboot --set-active=other
fastboot reboot bootloader
Before my monthly update ritual, I'm basically replicating the OTA process in that I'm alternating partitions each month and my backup partition should always be a month behind, and a known working setup. Does that sound correct?
I'm just trying to simplify the monthly update process to avoid forgetting a step.
Thanks again!

Correct