How To Guide [GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet

[badabing2003]

Simply typing flash-all in the command line should load and execute the correct script, regardless of what you're using.

And wipe the phone if done blindly without first editing it.

@itamargs just follow the guide or better yet what V0latyle said here

[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet

⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...

forum.xda-developers.com

 

[V0latyle]

And wipe the phone if done blindly without first editing it.

@itamargs just follow the guide or better yet what V0latyle said here

[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet

⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...

forum.xda-developers.com

True. My assumption was that he'd already edited the script. One can always perform the commands manually, or use your tool! (I still haven't tried Pixel Flasher yet)

 

[phaino00]

Not quite correct...

flash-all.sh is a shell script for a Linux terminal and won't work on Windows.
flash-all.bat is a batch file that contains scripts for the Windows command line.

Simply typing flash-all in the command line should load and execute the correct script, regardless of what you're using. You are correct in that it's not a fastboot command in of itself; the script contains the fastboot commands used for flashing the device.

@C5Longhorn if you wanted to flash manually, here is the correct sequence to dirty flash the factory image to both slots:

1. Download and extract factory package. Extract boot.img from image-oriole-buildnumber.zip. Patch boot.img in Magisk and copy back to the factory package folder. This can be done before or after the update; I personally prefer to do it before.
2. Reboot to bootloader:

   adb reboot bootloader

3. Compare bootloader and baseband versions on device screen to the radio and bootloader files in the factory package. If different, or if you just want to be safe, update them:
   

   fastboot flash bootloader --slot=all <drag and drop bootloader.img>

   Wait for flash to complete.
   

   fastboot flash radio --slot=all <drag and drop radio.img>

   Wait for flash to complete
   

   fastboot reboot bootloader

   Observe updated bootloader and baseband versions
4. Dirty flash the factory image:
   

   fastboot update --slot=all --skip-reboot <drag and drop image-oriole-buildnumber.zip>

   Wait for update to complete; watch command line. Device will reboot to fastboot mode during the process.
5. When update completes, reboot to bootloader:

   fastboot reboot bootloader

6. Flash patched boot image:

   fastboot flash boot --slot=all <drag and drop patched boot.img>

   Wait for flash to complete.
7. Reboot to system:

   fastboot reboot

8. Your device should boot into updated system with root.

Do you have a specific reason for flashing to both slots, adding '--slot=all' to the fastboot update command? Or is it just a habit from past flashing/updating, thus don't fix what's not broke?

 

[V0latyle]

Do you have a specific reason for flashing to both slots, adding '--slot=all' to the fastboot update command? Or is it just a habit from past flashing/updating, thus don't fix what's not broke?

It's not a necessity, but because I always update with the factory image, I flash both slots to ensure a failover if there's a problem with one.

 

[badabing2003]

It's not a necessity, but because I always update with the factory image, I flash both slots to ensure a failover if there's a problem with one.

Actually it is safer without --slot=all

Let me give a scenario

Let's say in April you flashed to All and it is working, so both slots are good.
In May you flash to all and it turns out to be a bad one.
Now both slots are bad

On the other hand if you only flash to one, then you can change the slot and boot to the older image, granted it will get too old over time since flash all flashes to the active slot and not inactive one, but at least you still have a bootable older option.

Of course almost always flashing stock would fix it, but why risk messing both at the same time.
A better option (however takes more time) is once you confirm that it worked, switch the slot and flash to it as well, this way both slots would be current and functional.

I personally don't bother, I just flash to the active one, but that is a personal choice.

Thinking about it, perhaps the best option would be is to mimic the OTA slot approach with flash_all
basically just change the slot first, and then flash to the active slot, if it works you're good, if it doesn't you switch back and you only go back to the last month's version.
With this approach the inactive slot will only be 1 version behind.

 

[V0latyle]

Actually it is safer without --slot=all

Let me give a scenario

Let's say in April you flashed to All and it is working, so both slots are good.
In May you flash to all and it turns out to be a bad one.
Now both slots are bad

On the other hand if you only flash to one, then you can change the slot and boot to the older image, granted it will get too old over time since flash all flashes to the active slot and not inactive one, but at least you still have a bootable older option.

Of course almost always flashing stock would fix it, but why risk messing both at the same time.
A better option (however takes more time) is once you confirm that it worked, switch the slot and flash to it as well, this way both slots would be current and functional.

I personally don't bother, I just flash to the active one, but that is a personal choice.

Thinking about it, perhaps the best option would be is to mimic the OTA slot approach with flash_all
basically just change the slot first, and then flash to the active slot, if it works you're good, if it doesn't you switch back and you only go back to the last month's version.
With this approach the inactive slot will only be 1 version behind.

I see what you're saying, and for the most part I agree. The only thing is, you'll always be flashing the factory image with a PC, so if something goes wrong you can just dirty flash the last working image.

 

[badabing2003]

I see what you're saying, and for the most part I agree. The only thing is, you'll always be flashing the factory image with a PC, so if something goes wrong you can just dirty flash the last working image.

Yep, so true.

 

[soodz]

I did the slot b trick with magisk for the July update and everything was smooth as usual for me... Passing safetynet, modules still working, all systems go

 

[soodz]

Oops

 

[V0latyle]

I did the slot b trick with magisk for the July update and everything was smooth as usual for me... Passing safetynet, modules still working, all systems go

What version of Magisk?

 

[soodz]

What version of Magisk?

 

[V0latyle]

Do you have your Magisk app hidden? Your package name is odd.

And you said "slot B method", do you mean you downloaded the OTA then patched inactive slot in Magisk?

 

[soodz]

Do you have your Magisk app hidden? Your package name is odd.

And you said "slot B method", do you mean you downloaded the OTA then patched inactive slot in Magisk?

I do have magisk hidden as 'Safari' and yes by Slot B method I mean patched inactive slot in Magisk before rebooting to complete the OTA update.

 

[V0latyle]

I do have magisk hidden as 'Safari' and yes by Slot B method I mean patched inactive slot in Magisk before rebooting to complete the OTA update.

Interesting. How did you command the reboot?

When I tried to update this way on my wife's 5a, it bootlooped back to the original slot.

 

[soodz]

Interesting. How did you command the reboot?

When I tried to update this way on my wife's 5a, it bootlooped back to the original slot.

I always follow these steps once I know the OTA is available:

1. Open Magisk and select 'Uninstall Magisk -> Restore Images'
2. Open Settings and Download/Install OTA *DO NOT REBOOT*
3. Go back to Magisk and select 'Install -> Install to Inactive Slot (After OTA)' *DO NOT REBOOT*
4. Go back to Settings and 'Reboot' to finalize the OTA

 

[V0latyle]

I always follow these steps once I know the OTA is available:

1. Open Magisk and select 'Uninstall Magisk -> Restore Images'
2. Open Settings and Download/Install OTA *DO NOT REBOOT*
3. Go back to Magisk and select 'Install -> Install to Inactive Slot (After OTA)' *DO NOT REBOOT*
4. Go back to Settings and 'Reboot' to finalize the OTA

Interesting. Maybe it's something specific to the 765G devices that broke the out of band method.

 

[Uunderfire]

I always follow these steps once I know the OTA is available:

1. Open Magisk and select 'Uninstall Magisk -> Restore Images'
2. Open Settings and Download/Install OTA *DO NOT REBOOT*
3. Go back to Magisk and select 'Install -> Install to Inactive Slot (After OTA)' *DO NOT REBOOT*
4. Go back to Settings and 'Reboot' to finalize the OTA

Just a warning with this method, I tried it myself in order to update to July's security update. The download worked correctly once Magisk was uninstalled, however after I chose to install to the inactive slot I went back to the OTA screen, pushed the "Reboot now" button and then the OTA started to install again. Then it showed a message saying that the update is impossible (as if it had detected magisk again on the current slot). I am sure that I chose the "Install to inactive slot" button and not the classic install.

I then tried to flash manually with the factory image with the --slot=all command, however I had quite a scare as the update failed due to a lack of space on slot B (I was on slot A at the beginning so slot B was the one where the OTA was performed). I tried without the --slot=all and it failed again on slot A due to an error with the product image. After another try it worked on slot A and I could boot again and then patch the boot with Magisk.

I think that the OTA temporary corrupted one of my slots, I am going to stick to the manual method from now on.

 

[V0latyle]

Just a warning with this method, I tried it myself in order to update to July's security update. The download worked correctly once Magisk was uninstalled, however after I chose to install to the inactive slot I went back to the OTA screen, pushed the "Reboot now" button and then the OTA started to install again. Then it showed a message saying that the update is impossible (as if it had detected magisk again on the current slot). I am sure that I chose the "Install to inactive slot" button and not the classic install.

I then tried to flash manually with the factory image with the --slot=all command, however I had quite a scare as the update failed due to a lack of space on slot B (I was on slot A at the beginning so slot B was the one where the OTA was performed). I tried without the --slot=all and it failed again on slot A due to an error with the product image. After another try it worked on slot A and I could boot again and then patch the boot with Magisk.

I think that the OTA temporary corrupted one of my slots, I am going to stick to the manual method from now on.

Why did you go back to the OTA restart screen? When you patch the inactive slot in Magisk, Magisk will then prompt you for a reboot.

I don't know if it makes any difference whether you reboot via system or via Magisk.

 

[Uunderfire]

Why did you go back to the OTA restart screen? When you patch the inactive slot in Magisk, Magisk will then prompt you for a reboot.

I don't know if it makes any difference whether you reboot via system or via Magisk.

Since I had an issue in May with the OTA update and since soodz succeeded in performing the update, I wanted to follow the exact steps written in his post to see if it made a difference.

Thinking about it, it may have made a difference in my case as it triggered this weird reinstall behavior of the OTA. I may try to directly reboot from magisk next time to see if it makes a difference ! And switch to a manual install again if it wreaks havok on my other slot ahah

 

[airtower]

Anyone lose Google Wallet tap to pay recently?