How To Guide [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root-Update

[Az Biker]

But what best now, flash the patched boot or boot into it and direct install in magisk app? This confuses me.

You patch the boot.img in magisk, put that patched image back on your pc, in fastboot flash the patched boot.img, let it boot, reboot and you're done.

Like I said, follow the below instructions in the OP.


9- After the install, it will reboot into system, let everything settle, skip start up options and get to where you can download the latest MAGISK apk on your device (downloads folder)
***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***

10- Connect your device and PC and put the extracted BOOT.img file (from the CURRENT factory image you are flashing FOUND IN THE SECOND ZIP FOLDER) that you placed on your PC, put it on your mobile device where you can easily find it (I created a folder FILES TO FLASH)


11- Install Magisk (use Canary 24310 linked above), follow instructions to allow files like this to be installed) ***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***


12- Open Magisk and choose SELECT AND PATCH FILE (select the BOOT.img you just put on your device


13- Copy the new PATCHED BOOT.img from your download folder back into your PLATFORM TOOLS folder where the fastboot application is located on your PC


14- Boot device into fastboot/bootloader, connect device and PC


15- Type CMD in address bar and verify fastboot connection (step 4)


16- Type fastboot reboot bootloader


17- Type fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img)


18- Reboot into System

 

[abalam]

You patch the boot.img in magisk, put that patched image back on your pc, in fastboot flash the patched boot.img, let it boot, reboot and you're done.

Like I said, follow the below instructions in the OP.


9- After the install, it will reboot into system, let everything settle, skip start up options and get to where you can download the latest MAGISK apk on your device (downloads folder)
***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***

10- Connect your device and PC and put the extracted BOOT.img file (from the CURRENT factory image you are flashing FOUND IN THE SECOND ZIP FOLDER) that you placed on your PC, put it on your mobile device where you can easily find it (I created a folder FILES TO FLASH)


11- Install Magisk (use Canary 24310 linked above), follow instructions to allow files like this to be installed) ***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***


12- Open Magisk and choose SELECT AND PATCH FILE (select the BOOT.img you just put on your device


13- Copy the new PATCHED BOOT.img from your download folder back into your PLATFORM TOOLS folder where the fastboot application is located on your PC


14- Boot device into fastboot/bootloader, connect device and PC


15- Type CMD in address bar and verify fastboot connection (step 4)


16- Type fastboot reboot bootloader


17- Type fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img)


18- Reboot into System

I understand the whole operation, but my question is why one flashes the patched boot.img and the other boots the patched in fastboot. I know back in the day you had to boot the proton kernel too and not flash it. Furthermore the continue installation in magisk by direct install. Do you understand my question, yes my english in not my native language

 

[Az Biker]

I understand the whole operation, but my question is why one flashes the patched boot.img and the other boots the patched in fastboot. I know back in the day you had to boot the proton kernel too and not flash it. Furthermore the continue installation in magisk by direct install. Do you understand my question, yes my english in not my native language

Patching the boot.img IN MAGISK is required for magisk to remain active after the device boots up. The patched magisk boot.img replacs the original factory image boot.img file.

Otherwise, you would lose root tghe next time you booted up.

Flashing that patched boot.img in fastboot installs the patched image to both slots so regardless of which slot your device boots from, it will retain magisk (root).

If I am not understanding your question, my apologies.

 

[abalam]

Patching the boot.img IN MAGISK is required for magisk to remain active after the device boots up. The patched magisk boot.img replacs the original factory image boot.img file.

Otherwise, you would lose root tghe next time you booted up.

Flashing that patched boot.img in fastboot installs the patched image to both slots so regardless of which slot your device boots from, it will retain magisk (root).

If I am not understanding your question, my apologies.

Never mind bro.

 

[morphvale]

If I am not understanding your question, my apologies.

But you are, that is what he was trying to say.

I can't speak about other phones but, for my previous OP7T the root process was as follows:
1. Install Magisk
2. Patch boot image with Magisk and copy to PC
3. Fastboot boot patched image
4. Open Magisk and Install - Direct Install
5. Reboot. You are now rooted

While for Pixel 6 the process is, as described:
1. Install Magisk
2. Patch boot image with Magisk and copy to PC
3. Fastboot flash boot image
No more steps, you are now rooted

Note the difference in step 3 and and missing extra step.
So he's asking why the difference for the Pixel in step 3.

 

[Az Biker]

But you are, that is what he was trying to say.

I can't speak about other phones but, for my previous OP7T the root process was as follows:
1. Install Magisk
2. Patch boot image with Magisk and copy to PC
3. Fastboot boot patched image
4. Open Magisk and Install - Direct Install
5. Reboot. You are now rooted

While for Pixel 6 the process is, as described:
1. Install Magisk
2. Patch boot image with Magisk and copy to PC
3. Fastboot flash boot image
No more steps, you are now rooted

Note the difference in step 3 and and missing extra step.
So he's asking why the difference for the Pixel in step 3.

I'm not sure why the difference outside of diff manufacturers...

That's more of a question for a developer. I just post the process that works for my device

 

[Lughnasadh]

But you are, that is what he was trying to say.

I can't speak about other phones but, for my previous OP7T the root process was as follows:
1. Install Magisk
2. Patch boot image with Magisk and copy to PC
3. Fastboot boot patched image
4. Open Magisk and Install - Direct Install
5. Reboot. You are now rooted

While for Pixel 6 the process is, as described:
1. Install Magisk
2. Patch boot image with Magisk and copy to PC
3. Fastboot flash boot image
No more steps, you are now rooted

Note the difference in step 3 and and missing extra step.
So he's asking why the difference for the Pixel in step 3.

Even though you aren't the one asking the question, I'm quoting your post because you describe the differences well and just makes for a good segue.

Either way will work. Some people like to fastboot boot the patched boot.img (gives you temporary root) first just to make sure everything is good and Magisk mods, etc. are working. If not, you can just reboot and you won't be rooted. If all is good then you can install "permanently" via direct install.

Others just like to fastboot flash the patched boot.img so it's "permanently" installed in one step (disabling Magisk mods that may potentially need updating beforehand is always good practice using this method).

Either way, it will only be installed to your current/active slot. Also know that if for some reason you want to flash the patched image to both slots you can't just switch slots and boot up you inactive slot (for a couple of reasons). You can only boot the slot in which the last firmware was installed. Therefore, say your current slot is slot A. If you flash the patched image to both slots you can't just switch to slot B and boot up and be rooted. You would first have to flash the firmware again to slot B to be able to boot up in slot B and then re-root while that slot is active in this scenario.

 

[Nergal di Cuthah]

But what best now, flash the patched boot or boot into it and direct install in magisk app? This confuses me.

Neither is better than the other. Booting allows you to preview that boot prior to comitting. Flashing gets it in right away.
Personally i always flash with zero problem. I use a hybrid of @Az Biker and @V0latyle methods and have no problem.

 

[RicoMartins]

Hey guys! I was successful in the process, thanks for sharing. Someone was successful in everything, saftnet passed banks, Google play and I have Widevone L1, hob and Disney hdr but Netflix was in FHD and HDR is now in SD Widevone L1. Any suggestion?

 

[RicoMartins]

After many attempts, I managed to solve it... To whom it may concern: UNSF 2.40 was my problem, I went back to 2.31 and everything works fine now.

 

[Nergal di Cuthah]

After many attempts, I managed to solve it... To whom it may concern: Magisk 2.40 was my problem, I went back to 2.31 and everything works fine now.

I assume you mean usnf 2.40 and 2.31, as those are the versions of usnf not magisk which is version 25 i believe

 

[RicoMartins]

Perfect, sorry for the mistake I'm Brazilian and my English is only by translator. I will edit, thanks!

 

[dacapho]

Hey guys, first time needing to downgrade and I need a bit of help. Going from the Feb '23 rooted update to the Jan '23. and then re-root. What is the correct process to avoid a bootloop or corrupt data while avoiding wiping or performing a factory reset?

 

[Az Biker]

Hey guys, first time needing to downgrade and I need a bit of help. Going from the Feb '23 rooted update to the Jan '23. and then re-root. What is the correct process to avoid a bootloop or corrupt data while avoiding wiping or performing a factory reset?

AFAIK, once you're updated to Android 13 on both slots (per OP) you should be able to flash the January Android 13 factory image using the same process as updating to the latest factory image.

The only thing you can't fo from Android 13 is go back to Android 12 or earlier. Again, this is my understanding.

Luckily there are several people watching this thread who know way more than I do, abd csn correct me if I'm wrong.

@V0latyle @Lughnasadh any insight either of you?

 

[Lughnasadh]

AFAIK, once you're updated to Android 13 on both slots (per OP) you should be able to flash the January Android 13 factory image using the same process as updating to the latest factory image.

The only thing you can't fo from Android 13 is go back to Android 12 or earlier. Again, this is my understanding.

Luckily there are several people watching this thread who know way more than I do, abd csn correct me if I'm wrong.

@V0latyle @Lughnasadh any insight either of you?

Correct. Just remove the -w from the flash-all.bat script (to keep data) and flash the January image, then re-root.

As for the red eio dm-verity corruption message, people have gotten this in all sorts of circumstances. It's not a big deal when you get this as usually there is just a hash mismatch and it usually goes away after an update. It's mostly a "cosmetic" warning and won't impact you in a negative way. You can safely ignore it. Probably the best way to avoid getting the message, though, is to disable verity and verification, but that will wipe your phone.

@dacapho

 

[dacapho]

Correct. Just remove the -w from the flash-all.bat script (to keep data) and flash the January image, then re-root.

As for the red eio dm-verity corruption message, people have gotten this in all sorts of circumstances. It's not a big deal when you get this as usually there is just a hash mismatch and it usually goes away after an update. It's mostly a "cosmetic" warning and won't impact you in a negative way. You can safely ignore it. Probably the best way to avoid getting the message, though, is to disable verity and verification, but that will wipe your phone.

@dacapho

Ok, so I disabled Magisk modules, copied all the files back over into my folder from the Jan zip, removed the -w and saved. Ran the flash all script and all seemed fine except when it went to reboot, it bootlooped to the red corruption message cannot load Android system, data may be corrupt..blah blah. Try try again, still the same screen. It wont ever boot to the OS.

So then I did the whole thing over with the current Feb 23 files and it boots like normal and all is fine. Confucius
@Lughnasadh

 

[Az Biker]

Ok, so I disabled Magisk modules, copied all the files back over into my folder from the Jan zip, removed the -w and saved. Ran the flash all script and all seemed fine except when it went to reboot, it bootlooped to the red corruption message cannot load Android system, data may be corrupt..blah blah. Try try again, still the same screen. It wont ever boot to the OS.

So then I did the whole thing over with the current Feb 23 files and it boots like normal and all is fine. Confucius
@Lughnasadh

Make sure you're patching the boot.img from the January factory image, and not recycling the Feb image. The patched boot.img must match the factory image it came from.

 

[Lughnasadh]

Ok, so I disabled Magisk modules, copied all the files back over into my folder from the Jan zip, removed the -w and saved. Ran the flash all script and all seemed fine except when it went to reboot, it bootlooped to the red corruption message cannot load Android system, data may be corrupt..blah blah. Try try again, still the same screen. It wont ever boot to the OS.

So then I did the whole thing over with the current Feb 23 files and it boots like normal and all is fine. Confucius
@Lughnasadh

Odd. Should have worked as I've done it before and I know several people who are always go back and forth to different builds with no problems.

Wondering if you booted into the bootloader (or even recovery mode) and then rebooted from there if it would have booted...

 

[V0latyle]

AFAIK, once you're updated to Android 13 on both slots (per OP) you should be able to flash the January Android 13 factory image using the same process as updating to the latest factory image.

The only thing you can't fo from Android 13 is go back to Android 12 or earlier. Again, this is my understanding.

Luckily there are several people watching this thread who know way more than I do, abd csn correct me if I'm wrong.

@V0latyle @Lughnasadh any insight either of you?

When downgrading it's generally smart to do a data wipe, although it probably wouldn't be required. If you don't flash the old bootloader and radio, you'll need to use the --force flag when flashing the image package: fastboot update image-device-buildnumber.zip --force

You can use this same method to flash the Android 12 builds on the Android 13 bootloader. They won't work properly but it can be done.

 

[dacapho]

Thanks for the help guys, although nothing worked, I will just stick with the Feb update as I am definitely not willing to wipe data.