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

[V0latyle]

I'm at a loss, I have botted to the nov update so therefore any OTA's don't get installed. Now I keep losing root access and don't understand how to keep it

All you should have to do is patch and flash the boot image...

 

[iwearthebelt]

All you should have to do is patch and flash the boot image...

Sounds to me like he might be a novice user , that's why I recommended Pixel Flasher to him. Everything is done for you with that program. I'm sure he'll figure it out, you gotta learn somehow.

 

[V0latyle]

Sounds to me like he might be a novice user , that's why I recommended Pixel Flasher to him. Everything is done for you with that program. I'm sure he'll figure it out, you gotta learn somehow.

Pixel Flasher is not a one click does all application. As @badabing2003 stresses in his OP, it simply automates ADB commands. It's still extremely important for anyone trying to modify their device to learn the details of how to patch and flash their device.

 

[iwearthebelt]

Pixel Flasher is not a one click does all application. As @badabing2003 stresses in his OP, it simply automates ADB commands. It's still extremely important for anyone trying to modify their device to learn the details of how to patch and flash their device.

I agree, but if you don't know how to patch and flash your device, using a program like Pixel Flasher simplifies the process and by doing some reading helps you understand how things are done (at least that's the way I see it). I was just trying to help the guy out, just giving a little advice. You can't learn this stuff overnight.

 

[pojr]

Slider? This seems odd....Are you sure you have the right firmware for your device?

Yikes. I may not have the right firmware. I have an unlocked bootloader and rooted device, so seems like things are running fine, but would not be surprised if I messed something up. Any idea what slider is? Ever seen something like this before? Not sure where I may have messed up.

Edit: I'll be honest, I feel like I followed the instructions to unlock the bootloader and root verbatim. So I'm not sure why the bootloader versions would be incorrect. Not saying I didn't mess up somewhere though.

No - boot.img is not the same as bootloader.img. Getting this wrong can brick your device. The image you need is in the root of the factory package, and is titled bootloader-raven-1.x-xxxxxxx.img

Here is an example using firmware for my Pixel 5:
View attachment 5763207

See above. The boot image only contains kernel and ramdisk, and is contained in the image-device-buildnumber.zip. This is what you patch in Magisk.

I had a feeling boot.img wasn't the right way to go LOL.

I'm a little lost then, because I never needed to flash a bootloader update before. In the rooting instruction from This Thread, it says to grab the boot.img from the factory image, then patch with magisk, then "fastboot flash boot" that same boot image (which is now magisk patched). But we shouldn't use boot.img in the bootloader? Not trying to disagree, just wondering because clearly I'm a doofas lol. What would the magisk patched boot.img actually be for then??

Edit: Actually I think I understand. I can use boot.img in fastboot mode , but I just can't use the "bootloader" command for it while in fastboot, that should be for the bootloader img file that you referenced. That makes sense, if I understand.

Tensor devices do not seem to permit using --slot all so the proper way to update bootloader on the Pixel 6 series is thus:

fastboot flash bootloader_a <bootloader image>
fastboot flash bootloader_b <bootloader image>
fastboot reboot bootloader

Got it, so I should use fastboot flash boot_a and fastboot flash boot_b to update the fastboot version then?

Edit: Sorry, can't read. You said bootloader_a and bootloader_b, not boot_a and boot_b.

Anyway I greatly appreciate the help. If you want me to post in the other thread instead of here, I can do that. Trying to learn, but sometimes I break stuff in the process lol.

Edit: And yeah, the PixelFlasher looks cool. Might start using that for now on.

 

[Lughnasadh]

Yikes. I may not have the right firmware. I have an unlocked bootloader and rooted device, so seems like things are running fine, but would not be surprised if I messed something up. Any idea what slider is? Ever seen something like this before? Not sure where I may have messed up.


I had a feeling boot.img wasn't the right way to go LOL.

I'm a little lost then, because I never needed to flash a bootloader update before. In the rooting instruction from This Thread, it says to grab the boot.img from the factory image, then patch with magisk, then "fastboot flash boot" that same boot image (which is now magisk patched). But we shouldn't use boot.img in the bootloader? Not trying to disagree, just wondering because clearly I'm a doofas lol. What would the magisk patched boot.img actually be for then??


Got it, so I should use fastboot flash boot_a and fastboot flash boot_b to update the fastboot version then?

Anyway I greatly appreciate the help. If you want me to post in the other thread instead of here, I can do that. Trying to learn, but sometimes I break stuff in the process lol.

Slider is the correct name used in the bootloader name for this device. Don't worry about that.

You should be able to use --slot all (or --slot=all) to flash the bootloader to both slots. For Tensor devices, you can't use --slot all (or --slot=all) when updating the whole firmware (e.g. when putting that command in update line in the flash-all.bat file when updating to a new monthly build). It will error out when you do that. But using --slot all (--slot=all) for flashing individual images/partitions should work.

 

[V0latyle]

Yikes. I may not have the right firmware. I have an unlocked bootloader and rooted device, so seems like things are running fine, but would not be surprised if I messed something up. Any idea what slider is? Ever seen something like this before? Not sure where I may have messed up.

Edit: I'll be honest, I feel like I followed the instructions to unlock the bootloader and root verbatim. So I'm not sure why the bootloader versions would be incorrect. Not saying I didn't mess up somewhere though.


I had a feeling boot.img wasn't the right way to go LOL.

I'm a little lost then, because I never needed to flash a bootloader update before. In the rooting instruction from This Thread, it says to grab the boot.img from the factory image, then patch with magisk, then "fastboot flash boot" that same boot image (which is now magisk patched). But we shouldn't use boot.img in the bootloader? Not trying to disagree, just wondering because clearly I'm a doofas lol. What would the magisk patched boot.img actually be for then??

This is where you need to understand the difference.

Bootloader is the first thing that starts on your phone when you power it on. It is responsible for finding and loading the system kernel - literally, it boots and loads - as well as writing images to partitions when flashing. If this is damaged or corrupted, the phone will not work at all, because the bootloader won't start and won't load the kernel (which is in the boot image). Therefore, bootloader is an absolutely critical partition, because if something goes wrong with this, the entire phone is useless. I cannot stress this enough, you DO NOT want to do something wrong when flashing the bootloader.

The boot image contains the system kernel, the recovery kernel, and ramdisk. This is what the bootloader loads from memory. This is what you patch in Magisk - the patching process modifies ramdisk. If something goes wrong with your boot image, your device will fail to boot, but fixing it should be as easy as reflashing it.

Edit: Actually I think I understand. I can use boot.img in fastboot mode , but I just can't use the "bootloader" command for it while in fastboot, that should be for the bootloader img file that you referenced. That makes sense, if I understand.

You flash both in bootloader mode. The difference is which image you're using and which partition you're flashing it to. While the bootloader is running, it is able to update its own partitions, as well as write, modify, and reformat any other partition on the device.

To use my Pixel 5 as an example again:

This is how I update bootloader:

fastboot flash bootloader bootloader-redfin-r3-0.5-8906128.img
fastboot reboot bootloader

Reboot is necessary when updating the bootloader; it loads the new bootloader after rebooting.

The syntax here is thus:

• fastboot is the program you are using to interface with the bootloader over USB; fastboot only works in bootloader mode and fastbootd mode, while adb is used in recovery and Android system
• flash is telling the bootloader what you want to do - in this case, you want to flash a partition
• bootloader is the partition you want it to flash, in this case /bootloader. This can be any partition that exists on the device: /bootloader, /radio, /system, /vbmeta, /boot, /dtbo, etc
• bootloader-device-buildnumber.img is the name of the file you're instructing the bootloader to flash to the specified partition. It is your responsibility to make sure the right binary goes in the right partition; the bootloader is "dumb" and will simply attempt to flash the specified partition with whatever binary you tell it to, even if it's wrong.

To flash the boot image:

fastboot flash boot boot.img <<< assuming I wanted to flash the factory boot image
fastboot flash boot magisk_patched-25200_xxxxx.img <<< in this case, I'm flashing the patched boot image

Similar to above, this is the syntax:

• fastboot is the program you're using to interface with bootloader
• flash is the command
• boot is the partition, in this case /boot
• boot.img is the name of the file you want to flash to the specified partition

Got it, so I should use fastboot flash boot_a and fastboot flash boot_b to update the fastboot version then?

Edit: Sorry, can't read. You said bootloader_a and bootloader_b, not boot_a and boot_b.

Honestly, you're starting to scare me a bit. If you don't know or understand the difference between these two, as I've tried to make abundantly clear, you should not be doing this. Get someone who knows what they're doing to help you.

Anyway I greatly appreciate the help. If you want me to post in the other thread instead of here, I can do that. Trying to learn, but sometimes I break stuff in the process lol.

Edit: And yeah, the PixelFlasher looks cool. Might start using that for now on.

It is helpful because it automates the commands, but it is NOT a substitute for knowing what you are doing.

Slider is the correct name used in the bootloader name for this device. Don't worry about that.

You should be able to use --slot all (or --slot=all) to flash the bootloader to both slots. For Tensor devices, you can't use --slot all (or --slot=all) when updating the whole firmware (e.g. when putting that command in update line in the flash-all.bat file when updating to a new monthly build). It will error out when you do that. But using --slot all (--slot=all) for flashing individual images/partitions should work.

Thanks for clarifying, I felt like I was missing something.

 

[pojr]

This is where you need to understand the difference.

Bootloader is the first thing that starts on your phone when you power it on. It is responsible for finding and loading the system kernel - literally, it boots and loads - as well as writing images to partitions when flashing. If this is damaged or corrupted, the phone will not work at all, because the bootloader won't start and won't load the kernel (which is in the boot image). Therefore, bootloader is an absolutely critical partition, because if something goes wrong with this, the entire phone is useless. I cannot stress this enough, you DO NOT want to do something wrong when flashing the bootloader.

Thank you for explaining this. Not gonna lie, I only had a VERY basic understanding of a bootloader. It lets you change partitions. That's really all I knew. I still don't get everything that you're saying here (too advanced for me).

You flash both in bootloader mode. The difference is which image you're using and which partition you're flashing it to. While the bootloader is running, it is able to update its own partitions, as well as write, modify, and reformat any other partition on the device.

To use my Pixel 5 as an example again:

This is how I update bootloader:

fastboot flash bootloader bootloader-redfin-r3-0.5-8906128.img
fastboot reboot bootloader

Reboot is necessary when updating the bootloader; it loads the new bootloader after rebooting.

The syntax here is thus:

• fastboot is the program you are using to interface with the bootloader over USB; fastboot only works in bootloader mode and fastbootd mode, while adb is used in recovery and Android system
• flash is telling the bootloader what you want to do - in this case, you want to flash a partition
• bootloader is the partition you want it to flash, in this case /bootloader. This can be any partition that exists on the device: /bootloader, /radio, /system, /vbmeta, /boot, /dtbo, etc
• bootloader-device-buildnumber.img is the name of the file you're instructing the bootloader to flash to the specified partition. It is your responsibility to make sure the right binary goes in the right partition; the bootloader is "dumb" and will simply attempt to flash the specified partition with whatever binary you tell it to, even if it's wrong.

To flash the boot image:

fastboot flash boot boot.img <<< assuming I wanted to flash the factory boot image
fastboot flash boot magisk_patched-25200_xxxxx.img <<< in this case, I'm flashing the patched boot image

Similar to above, this is the syntax:

• fastboot is the program you're using to interface with bootloader
• flash is the command
• boot is the partition, in this case /boot
• boot.img is the name of the file you want to flash to the specified partition

This is VERY helpful information, this I understand. You pointed this all out in a clear, concise manner and I appreciate this. Never realized fastboot was within bootloader mode. Not gonna lie. I know what a partition is, but didn't know what partitions existed within Android, and didn't realize there were 5+ of them. But still, a lot of this makes sense.

Honestly, you're starting to scare me a bit. If you don't know or understand the difference between these two, as I've tried to make abundantly clear, you should not be doing this. Get someone who knows what they're doing to help you.

I'm actually glad you stated this, because it's a wake up call to me. Maybe I shouldn't be doing any of this.

Also small comment: seems like Lineage OS is easier to deal with than Stock. Is that just me? I haven't had near as many problems with Lineage OS as I have with Stock, but again, could just be me.

That last comment "Get someone who knows what they're doing to help you". Should I just give up? It's saying a lot when the teacher gives up on the student lol (I say teacher because you made this thread to begin with) but I don't blame you. I've rooted a few devices in the past and updated them with minimal problems, but I've always just followed the instructions from tutorials without understanding exactly what I'm doing. Anyone can write "fastboot flash boot_a boot.img", but doesn't mean they understand what it means or why they're doing it. That's where I'm at.

It is helpful because it automates the commands, but it is NOT a substitute for knowing what you are doing.

I know that. Because if anything goes wrong, or the program gets discontinued, or if I need to cease use of the program for whatever reason, I won't be able to do anything on my own. Would that be a fair assessment?

Nonetheless, I really do appreciate your time. I apologize for wasting your time. If you do have a way I can donate or something, I will do that.

 

[V0latyle]

Thank you for explaining this. Not gonna lie, I only had a VERY basic understanding of a bootloader. It lets you change partitions. That's really all I knew. I still don't get everything that you're saying here (too advanced for me).


This is VERY helpful information, this I understand. You pointed this all out in a clear, concise manner and I appreciate this. Never realized fastboot was within bootloader mode. Not gonna lie. I know what a partition is, but didn't know what partitions existed within Android, and didn't realize there were 5+ of them. But still, a lot of this makes sense.

There's actually closer to 20 partitions. Fortunately we generally only have to concern ourselves with three: /bootloader, /radio, and /boot.

I'm actually glad you stated this, because it's a wake up call to me. Maybe I shouldn't be doing any of this.

It just means you have more to learn. Don't be afraid to ask questions. While I have a multitude of technical knowledge, I'm not the best teacher. Fortunately, we have tons of other people here who can help explain things. None of this really comes naturally; while I'm a technically minded person, I've also been doing this for more than a decade, when the original Motorola Droid came out. I had to essentially relearn everything when I started using HTC devices, then again when I started using Samsung, and finally when I switched to Google.

Also small comment: seems like Lineage OS is easier to deal with than Stock. Is that just me? I haven't had near as many problems with Lineage OS as I have with Stock, but again, could just be me.

I suppose it would depend on the device. LineageOS seems to work okay on my tablet; I just use the stock firmware with root on my Pixel 5.

That last comment "Get someone who knows what they're doing to help you". Should I just give up? It's saying a lot when the teacher gives up on the student lol (I say teacher because you made this thread to begin with) but I don't blame you. I've rooted a few devices in the past and updated them with minimal problems, but I've always just followed the instructions from tutorials without understanding exactly what I'm doing. Anyone can write "fastboot flash boot_a boot.img", but doesn't mean they understand what it means or why they're doing it. That's where I'm at.

No, don't give up. Just make sure you have a clear understanding of what you want to try to do, and how everything works. I would recommend not trying until you're at the point where you have a solid grasp of things, but sometimes we just have to yeet it because YOLO or whatever the kids say these days...

I know that. Because if anything goes wrong, or the program gets discontinued, or if I need to cease use of the program for whatever reason, I won't be able to do anything on my own. Would that be a fair assessment?

I don't think @badabing2003 will be discontinuing PixelFlasher anytime soon, but it is always wise to understand the concepts involved.

Nonetheless, I really do appreciate your time. I apologize for wasting your time. If you do have a way I can donate or something, I will do that.

You aren't wasting my time. If I'm not able to help you learn somrthing, what am I really doing here?

As far as I know, moderators can't accept donations. I could be wrong. Still, I have never bothered to set anything up to receive donations, mostly because I take the most enjoyment out of simply being able to help others figure things out. The best way you can help me is by learning as much as you can and helping everyone else on XDA.

 

[uzichan]

Is there a way to change IMEI on pixel 6
So far Im unable to find any method

 

[V0latyle]

Is there a way to change IMEI on pixel 6
So far Im unable to find any method

This question isn't relevant to the scope of this thread. Furthermore, as changing IMEI is illegal in many countries, we do not permit discussing it on XDA.

 

[73sydney]

Pixel Flasher is not a one click does all application. As @badabing2003 stresses in his OP, it simply automates ADB commands. It's still extremely important for anyone trying to modify their device to learn the details of how to patch and flash their device.

Yup everyone should know how to do the process manually for a good base understanding of what theyre doing and what the process is doing, before letting a program or app do it

Trying to do things quickly and the easy way often disappoints, and i for one hate trying to troubleshoot an app wrapping a known process, when troubleshooting a known process is far easier...

Having said that, with plenty of Pixel (and general ROM) flash points under my belt i am looking forward to trying Pixel Flasher at some point soon

 

[jackuphill]

Hi
My Pixel 6 was on A13 build P1A.221105.002, Nov 2022.
I then rooted the phone using Steps given for intial root with Master Root Image and Magisk. Used Magisk version 25.2.
Before updating with Dec OTA chad checked the current slot and it was "b"
For updating to Dec OTA followed the "Update and Root Automatic OTA" using Magisk. (inactive slot method).
After rebooting from Magisk got the error "your device is corrupt. It can't be trusted and may not work properly." with option to press power button to continue. But before I could press the power button the phone went blank and got switched off. So I turned it on again and now it booted normally, (with only warning of unlocked bootloader)
But now Magisk showed N/A and also the build was on P1A.221105.002, Nov 2022 itself and later when I checked the current slot, it was still slot "b"
As the Dec OTA and Magisk got installed in slot "a" and now that it is corrupted how to correct the inactive slot "a" so that slot "a" returns to the state before Magisk and OTA was installed to the inactive slot.

 

[V0latyle]

Hi
My Pixel 6 was on A13 build P1A.221105.002, Nov 2022.
I then rooted the phone using Steps given for intial root with Master Root Image and Magisk. Used Magisk version 25.2.
Before updating with Dec OTA chad checked the current slot and it was "b"
For updating to Dec OTA followed the "Update and Root Automatic OTA" using Magisk. (inactive slot method).
After rebooting from Magisk got the error "your device is corrupt. It can't be trusted and may not work properly." with option to press power button to continue. But before I could press the power button the phone went blank and got switched off. So I turned it on again and now it booted normally, (with only warning of unlocked bootloader)
But now Magisk showed N/A and also the build was on P1A.221105.002, Nov 2022 itself and later when I checked the current slot, it was still slot "b"
As the Dec OTA and Magisk got installed in slot "a" and now that it is corrupted how to correct the inactive slot "a" so that slot "a" returns to the state before Magisk and OTA was installed to the inactive slot.

If the update fails, the device automatically recycles back to the last working slot. You do not need to do anything to Slot A. You can try the OTA update again, maybe sideload it this time, or you can update via the factory image method.

 

[fil3s]

Hi
My Pixel 6 was on A13 build P1A.221105.002, Nov 2022.
I then rooted the phone using Steps given for intial root with Master Root Image and Magisk. Used Magisk version 25.2.
Before updating with Dec OTA chad checked the current slot and it was "b"
For updating to Dec OTA followed the "Update and Root Automatic OTA" using Magisk. (inactive slot method).
After rebooting from Magisk got the error "your device is corrupt. It can't be trusted and may not work properly." with option to press power button to continue. But before I could press the power button the phone went blank and got switched off. So I turned it on again and now it booted normally, (with only warning of unlocked bootloader)
But now Magisk showed N/A and also the build was on P1A.221105.002, Nov 2022 itself and later when I checked the current slot, it was still slot "b"
As the Dec OTA and Magisk got installed in slot "a" and now that it is corrupted how to correct the inactive slot "a" so that slot "a" returns to the state before Magisk and OTA was installed to the inactive slot.

I'd use flashtool then fastboot boot the patched image, direct install. Safest and easiest way.

 

[jackuphill]

If the update fails, the device automatically recycles back to the last working slot. You do not need to do anything to Slot A. You can try the OTA update again, maybe sideload it this time, or you can update via the factory image method.

Thanks, will try the factory image method. One doubt I suppose I can flash the December build instead of the November build.

 

[jackuphill]

I'd use flashtool then fastboot boot the patched image, direct install. Safest and easiest way.

Thanks will try to flash the factory image. One doubt I suppose I can flash the December build instead of the November build.

 

[V0latyle]

Thanks, will try the factory image method. One doubt I suppose I can flash the December build instead of the November build.

You do not have to install updates incrementally. The December update contains all previous changes.

 

[jackuphill]

I'd use flashtool then fastboot boot the patched image, direct install. Safest and easiest way.

I used your suggestion, plus then side loaded the OTA too, and re-rooted with Magisk. Thanks for the suggestion

 

[jackuphill]

You do not have to install updates incrementally. The December update contains all previous changes.

Thanks. Was able to side load the OTA via adb. and then re-rooted the device.