How To Guide [Guide] Root Pixel 6 with Magisk, Android 12.1

Search This thread

Lughnasadh

Senior Member
Mar 23, 2015
3,326
3,293
Google Nexus 5
Huawei Nexus 6P
People flashing kernels builds over another kernel build without going back to the stock images (e.g. boot image, dtbo image, vendor_boot image, vendor_dlkm image) is definitely one of the problems that does mess people up, unless the kernel developer has said it's ok to flash their kernel over another.

Dirty flashing a factory image (with the -w removed), however, shouldn't be a problem as that method replaces everything with stock, including the kernel (just preserves you data). I've done this almost every month for years with no problems, including on the Pixel 6 Pro with a custom kernel installed. It seems that for whatever reason, however, some people have ran into the corrupt message while doing this, especially on the December build.

Also, some people get a corrupt message but everything still works, and some people can't even boot their phone after getting it.
 
  • Like
Reactions: vandyman

phoenixpb

Senior Member
Dec 18, 2010
103
22
This is how i updated to dec.
-Executed flash-all flashed bootloader & radio but didnt want to update the device
- fastboot update the image
- fastboot boot magisk patched image
- opened magisk and directly installed magisk
Is it not safer to uninstall magisk, reboot the device, do a normal update on the air and install magisk again ?

i never had problems with this method.
 

bobbarker2

Senior Member
Aug 30, 2013
1,571
569
Google Pixel 6 Pro
Google Pixel 6
Just to be a little more clear.
Are you talking about the boot up screen with the orange triangle? If so, that is normal for an unlocked bootloader.

Or when does this messege appear in the boot process?

No I am not. Every time I reboot I get a message in red stating "your device is corrupt" along with some other text and must press the power button to continue. Then I get the typical "bootloader unlocked" warning which displays for a few seconds, then the phone boots. As I've said previously I'm on the latest Magisk Canary, rooted, safetynet passing.
 

bobbarker2

Senior Member
Aug 30, 2013
1,571
569
Google Pixel 6 Pro
Google Pixel 6
It looks like I may have solved the bobbarker2 mystery.
After doing some reading in the Pixel threads I noticed the same questions were asked in the Blu Sparks kernel thread.

Diry flashing back and forth with kernel builds and factory images is the cause of the corrupt system.

Factory wipe is the only way I know to fix that issue.

As a side note : the only kernel that I trusted was EX kernel by Flar2. But he has not built it for the Pixel 6 because of issues.
I did not try a dirty flash. Flash-all of January without data wipe, flash Magisk patched boot img, attempted to flash custom kernel made device soft-brick.

Any custom kernel I've tried hasn't worked or forced me to do a factory reset. Tried flashing with EXKM and FKKM.. no difference.
 

Lughnasadh

Senior Member
Mar 23, 2015
3,326
3,293
Google Nexus 5
Huawei Nexus 6P
No I am not. Every time I reboot I get a message in red stating "your device is corrupt" along with some other text and must press the power button to continue. Then I get the typical "bootloader unlocked" warning which displays for a few seconds, then the phone boots. As I've said previously I'm on the latest Magisk Canary, rooted, safetynet passing.
I'm curious. Did you disable vbmeta verity and verification at anytime in the past and do you currently have it disabled? Because that screen you are encountering is an indication of a dm verity corruption.

Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up.

But what I'm wondering is how you got that message to begin with and if it's related to disabling vbmeta verity and verification in the past, or currently.
 
Last edited:
  • Like
Reactions: bobbarker2

bobbarker2

Senior Member
Aug 30, 2013
1,571
569
Google Pixel 6 Pro
Google Pixel 6
I'm curious. Did you disable vbmeta verity and verification at anytime in the past and do you currently have it disabled? Because that screen you are encountering is an indication of a dm verity corruption.

Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up.

But what I'm wondering is how you got that message to begin with and if it's related to disabling vbmeta verity and verification in the past, or currently.
Actually now that you mention it, someone said they had the same problem I was having at the time and they recommended I try --disable-verity --disable-verification arguments in the flash-all.bat, even though it shouldn't be needed. I've done so many flashes on this device trying to fix something, I can't even remember what it was I was trying to fix by doing that.

Currently verity isn't disabled in the slot that boots to January/rooted. So I think you're right, the only solution is a factory reset to erase the /data partition. I'll try it when I have the time/feel like rebuilding my phone.

I miss Titanium Backup, I wish it was maintained. Swift Backup works pretty well but Titanium was better.
 
  • Like
Reactions: Lughnasadh

Lughnasadh

Senior Member
Mar 23, 2015
3,326
3,293
Google Nexus 5
Huawei Nexus 6P
Actually now that you mention it, someone said they had the same problem I was having at the time and they recommended I try --disable-verity --disable-verification arguments in the flash-all.bat, even though it shouldn't be needed. I've done so many flashes on this device trying to fix something, I can't even remember what it was I was trying to fix by doing that.

Currently verity isn't disabled in the slot that boots to January/rooted. So I think you're right, the only solution is a factory reset to erase the /data partition. I'll try it when I have the time/feel like rebuilding my phone.

I miss Titanium Backup, I wish it was maintained. Swift Backup works pretty well but Titanium was better.
Yeah, disabling verity & verification by itself shouldn't cause the problem, but I'm wondering if when going back to having verity and verification enabled while doing a dirty flash (removing the -w from the flash-all.bat file) may have caused it. Not really sure, just trying to fit some pieces together.
 

vandyman

Senior Member
Jul 30, 2012
821
428
S.Jersey
Google Pixel 5
Google Pixel 6
I did not try a dirty flash. Flash-all of January without data wipe, flash Magisk patched boot img, attempted to flash custom kernel made device soft-brick.

Any custom kernel I've tried hasn't worked or forced me to do a factory reset. Tried flashing with EXKM and FKKM.. no difference.
Your systemUI is corrupt somehow from flashing. This can happen with simple mistake as flashing a December kernel on top of the January factory image.

The only way to fix this is to a factory reset or
Install the January full factory image with a complete wipe. Use the flash-all command in adb. This will wipe the system data as well, that is where your problem is. If you do not wipe data, it will keep your storage data and system data settings. You need to get rid of your system data.....
 

Lughnasadh

Senior Member
Mar 23, 2015
3,326
3,293
Google Nexus 5
Huawei Nexus 6P
magisk 24 just got release. Is it the same as the canary version?
Pretty much the same as Canary 23019 except for some translation updates, typo fixes and updated guides. Canary 24001 has a couple extra commits, but nothing of significance. The new release is a Beta release by the way. If everything goes well, he'll release it to stable in a few days.
 
  • Like
Reactions: mixtapes08

gazdajezda

Senior Member
Apr 24, 2011
394
79
Hmm, so SQ1D.220105.007 is still not recommended to be flashed without -w (wipe) in flash-all script? Eh, until i find a way how to quickly and without much effort return all settings / apps to the fresh system i will stay on november (SD1A.210817.037) update. I not have time to play with it after flash. But also I need root, since I use rsync on my phone to backup images, swift backups and rest to my home server. Tricky Google, tricky...
 

Nimueh

Recognized Contributor
May 19, 2012
3,183
2,627
OnePlus 3
Samsung Galaxy Tab A series
Hmm, so SQ1D.220105.007 is still not recommended to be flashed without -w (wipe) in flash-all script? Eh, until i find a way how to quickly and without much effort return all settings / apps to the fresh system i will stay on november (SD1A.210817.037) update. I not have time to play with it after flash. But also I need root, since I use rsync on my phone to backup images, swift backups and rest to my home server. Tricky Google, tricky...
I have no idea why all those guides have such complicated ways of updating ... when I updated from rooted December to 007 it was basically 3 steps:

Patch boot.img with Magisk, disable all modules
Reboot to recovery, sideload the OTA zip
Reboot to bootloader, boot patched img and then once booted direct install in Magisk

That worked fine for me, without all those bells + whistles. There might be instances where the "complicated" way is needed but I have no idea when or why 🤷‍♀️
 

t-ryder

Senior Member
Feb 23, 2011
1,389
1,068
www.t-ryder.de
Google Pixel 6
Patch boot.img with Magisk, disable all modules
Reboot to recovery, sideload the OTA zip
Reboot to bootloader, boot patched img and then once booted direct install in Magisk
Even what you do seems complicated to me.
I download the factory image, patch the boot image with magisk, flash all needed stuff with 0riole-Flasher in one single step, done.

No disabling modules, no sideloading, booting images and whatever.

Works all fine here.
 
  • Like
Reactions: co9

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Update
    Magisk Canary (c11ccbae) (24310)
    3
    Update
    Magisk Canary (756d8356) (24312)
    2
    Hi guys, my phone is bootlooping when I am trying to root through the latest Magisk Canary app, (tried the stable magisk version and it didn't work either). If I flash the stock boot image, the phone loops into the system just fine.

    I am using the latest platform tools(33.0.1) and my active boot slot is 'b'. I am on (SP2A.220405.004, Apr 2022) build.

    Could someone post a video or detailed instructions on rooting through OTA? I have no clue how to do it?

    If there is any other method also, I'd be willing to try. Please help me!
    Try booting 'Safe mode' then reboot and flash the magisk patched boot.img
    fastboot flash boot magisk_patched_boot.img

    ...rooting through OTA...
    OP, Part II - Instructions, 3. Take the OTA...
    2
    Hi guys, my phone is bootlooping when I am trying to root through the latest Magisk Canary app, (tried the stable magisk version and it didn't work either). If I flash the stock boot image, the phone loops into the system just fine.

    I am using the latest platform tools(33.0.1) and my active boot slot is 'b'. I am on (SP2A.220405.004, Apr 2022) build.

    Could someone post a video or detailed instructions on rooting through OTA? I have no clue how to do it?

    If there is any other method also, I'd be willing to try. Please help me!
    This is probably because the magisk_pacthed.img is not good, which could be due to how you transferred it to the phone, I have seen many reports that transfer through file manager is not always very reliable.

    In addition to what @Homeboy76 suggested, you can also try transferring the boot.img through adb.
    Test it first before flashing to see if it boots to root ok (without the flash option)
    Code:
    fastboot boot magisk_patched_boot.img

    One last thing, make sure when using Magisk canary (recommended) you set the channel to canary.
    2
    Hey folks. I'm a bit confused about the procedure to take an OTA and keep root, and would really appreciate some pointers.

    I have patched my boot.img as per the initial instructions (extracted boot.img from factory image, patched with magisk, and flashed it with fastboot).

    It's my understanding that to take the May OTA (I'm on the April one) I have to:
    • Go to magisk, uninstall, remove images
    • Install the OTA (both steps, DO NOT REBOT)
    • Go to magisk again, install to inactive slot
    • Reboot the device
    Is that it?

    What's confusing me is that the instructions for this on the OP (which link to the official instructions) says that "install to inactive slot" has been removed because Google changed how OTAs are taken, and that magisk does not quite have support for that. However, I'm using magisk 24.3, and the option is there. So, I'm bit unsure if it's safe to do this procedure or not.

    Some pointers in the right direction would be really appreciated.

    P.S. I disabled automatic system updates in the developer settings, but I opened the system updates screen in the settings, and now it says that the update will resume when the device is inactive. Is the update going to be automatically installed during the night? I hope not, until I figure out the right procedure to keep root.
    That note you are referring to in the instructions is old and there is currently a Pull Request to remove it, so you can ignore it as Magisk has been updated to support "Install to Inactive Slot" on Pixels. You may want to use Canary 24307 though. This method did not work with Stable 24.3 on the April build but was fixed with Canary 24306/7.

    However, this method is really hit and miss, to be honest.
  • 17
    [Guide] Root Pixel 6 with Magisk, Android 12.1
    Android Security Bulletin—May 2022
    Pixel Update Bulletin—May 2022

    Introduction
    This Guide is for Pixel 6 owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.

    ~ ~ ~ Part I - INFORMATION ~ ~ ~
    1. Disclaimer

      • I assume no responsibility for the malfunctioning/bricking of your phone.
      • The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
    2. Prerequisites

    3. Update(s)

    4. NEW

    5. My Other Guides
    6. Credits/Thanks/Recognitions

      • Google - Android 12 factory/OTA images.
      • @topjohnwu - Magisk.
      • vvb2060 - Magisk alpha.
      • Those I may have, inadvertently, forgotten.
    ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
    1. Unlock Bootloader/Return Phone to Stock/Lock Bootloader

      • Unlock Bootloader

        1. This will erase all user data from the device!
        2. Backup your data
        3. Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
        4. Boot fastboot mode
        5. Connect the phone to the Computer with USB cord.
        6. Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
        7. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        8. Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
        9. When your phone reboots disconnect your usb cable.
          Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
          Do not relock your bootloader until you have returned the device to Stock.
      • Return Phone to Stock

        1. Backup your data/Internal storage
        2. Settings > System > Advanced > Reset Options > Erase all data (factory reset)
        3. Log in
        4. Set up phone
      • Lock Bootloader

        1. Return the phone to Stock before locking the bootloader, failure to do so could brick your phone
        2. This will erase all user data from the device!
        3. Boot fastboot mode
        4. Open a Command Prompt and type this at the Prompt: fastboot flashing lock
        5. You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
        6. Allow the process to complete, then type this at the Command Prompt: fastboot reboot
        7. Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
        8. Tap Back > Developer options and toggle OEM Unlock off.
    2. Install/Update Factory Image keep data or wipe data

      • Important Note(s):
        1. When doing a Major Upgrade Android 12 (12.0.0) to Android 12.1 (12.1.0), I recommend doing a Clean Install: Do Flash Factory Image Wipe Data (below).
        2. Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 6 - oriole.
        3. If you get an error while flashing, try one of these options:
          • Change the USB port to a non charging USB port.
          • Change the USB cord.
          • Change Computers.
        4. If you phone bootloops
          • force Safe Mode by continually pressing volume down button during boot animation.
          • After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled).
          • Thanks @Typhus_ for the instructions to force Safe Mode.
        5. Backup your data
        6. Download the latest Factory Image: Pixel 6 - oriole to your Computer.
        7. Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the flash-all.bat file.
      • Flash Factory Image Keep Data

        • Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e., DroidEdit app.
          1. Change this line: fastboot -w update image-oriole-sq9d.999999.999.zip
          2. to this: fastboot update image-oriole-sq1d.999999.999.zip
          3. Note: If you do not remove the -w your internal storage will be wiped.
        • After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
          1. bootloader-oriole-....img
          2. flash-all.bat
          3. image-oriole-....zip
          4. radio-oriole-....img
        • On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
        • Connect your phone to the computer.
        • Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        • The phone will reboot when flashing is completed.
        • Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
      • Flash Factory Image Wipe Data

        • This will wipe your phone's Internal Storage.
        • Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
          1. bootloader-oriole-....img
          2. flash-all.bat
          3. image-oriole-....zip
          4. radio-oriole-....img
        • On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
        • Connect your phone to the computer.
        • Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
        • The phone will reboot when flashing is complete.
        • Setup phone
        • Enable Developer Mode and USB Debugging
          1. Setup => About phone => Tap Build number 7 times or untill you see you are a 'Devloper'.
          2. Setup => System => Developer options => Enable Developer options => enable USB Debugging
        • Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
    3. Take the OTA Update and Maintain Root

      • All the credit for this set of instructions goes to @topjohnwu for writing the instructions: Install Magisk to Inactive Slot , use Magisk Beta, Stable 24.3.
      • NOTE: If you had a Custom Kernel installed, after you Open Magisk and Restore Images. Do the following to return your phone to Stock:
        • fastboot flash dtbo dtbo.img
        • fastboot flash vendor_boot vendor_boot.img
        • fastboot flash vendor_dlkm vendor_dlkm.img
        • There may be more .img files you need to flash. Please check the OP of the Custom Kernel thread you install for instruction to remove the Custom Kernel and return your phone to Stock. Additionally, if you installed Mods Please check the OP of the Mod thread you installed for instruction to remove the Mod and return your phone to Stock before you download the OTA.
      • If you phone bootloops
        • force Safe Mode by continually pressing volume down button during boot animation.
        • After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled).
        • Thanks @Typhus_ for the instructions to force Safe Mode.
    4. Extract Files from Factory Image/Flash boot.img

      • Extract Files from Factory Image

        1. Extract flash-all.bat and boot.img file
        2. Download the latest Factory image to your phone.
        3. Extract the Factory Image file (bramble-r2d1a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
        4. Open the folder you extracted the Factory image to and, extract the Image file (image-bramble-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this folder.
      • Flash boot.img

        1. Flashing the boot.img removes root.
        2. Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
        3. Boot fastboot mode
        4. Connect the phone to the Computer
        5. Open a Command Prompt and type the following command at the prompt:
          fastboot flash boot --slot all boot.img
        6. Reboot
    5. Root/Reroot with Magisk and Pass SafetyNet.

      • Android 12

        • Upgrade to Android 12: OP, Part II - INSTRUCTIONS, 2. Install/Update Factory Image keep data or wipe data, Keep data
      • Patching the boot.img - to root/reroot.

        1. Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the boot.img file.
        2. Install Magisk Canary
          Note: Tap 3 dot menu across from canary => Tap Go to file => Download, app-debug.apk
          or
          Magisk 24.1 Beta/Stable App - Under Downloads
        3. Open Magisk Beta/Canary/Stable App
        4. Set the Update Channel Beta/Canary/Stable.
        5. Tap Install (next to Magisk)
        6. Tap, Select and Patch a File
        7. Select the boot.img file you extracted from the latest factory image.
        8. Tap the ✓ (Check Mark)
        9. Tap Let's Go
        10. When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
        11. Reboot
        12. Copy/Move the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
          • Copy it to a USB drive and transfer it to your computer.
          • Move it to your computer using adb push
        13. Boot fastboot mode
        14. Connect the phone to the Computer with USB cord.
        15. Open a Command Prompt in the folder you copied the patched boot.img to.
        16. Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
        17. Type fastboot reboot at the Prompt and press enter.
        18. Important Notes: If your phone boot loops try one of the following options:
          • Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
          • Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
      • Pass Safety Net with SafetyNet Fix 2.2.1

        1. Download File(s)
        2. Install SafetyNet Fix 2.2.1
          • Open Magisk
          • Tap Modules icon
          • Tap Install from storage
          • Navigate to the SafetyNetFix file you downloaded
          • Tap the SafetyNetFix file
          • Tap the check mark (✓ at the bottom) to start the installation.
          • After it installs tap the Save icon to save the log
          • Tap Reboot.
        3. Settings for Magisk Canary
          • Open Magisk App
          • Tap the Setup icon.
          • Scroll down to App and set the Update Channel to Canary.
          • Scroll down to Check Updates and enable it.
          • Scroll down to Magisk and enable Zygisk and Enforce DenyList.
          • Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, etc.
          • Optional Scroll down to Superuser and enable Enable Biometric Authentication.
        4. Get Device Certified Clear Google Play Services, Google Play Store, Google Pay, etc. data
          • Turn Airplane mode on
          • Open Settings
          • Tap Apps & notifications
          • Tap see all...
          • Tap three dot menu
          • Tap Show system
          • Scroll down to Google Play Store
          • Tap Storage and Cache
          • Tap Clear storage
            Note: Repeat the 3 steps above for Google Play Services, Google Pay, etc.
          • reboot
          • Turn Airplane mode off
        5. Check Device Certification
          • Open Google Play Store app
          • Tap Menu - Circle top right
          • Tap Settings
          • Tap About
          • Check Play protect certification.
    6. Set Magisk App Update Channel/Update Magisk

      • Set Magisk App Update Channel

        • Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
      • Update Magisk

        1. When Magisk App notifies you of an update:
        2. Tap install.
        3. Select, Direct Install (Recommended)
        4. When it finishes installing
        5. Tap, Save Log
        6. Log location: /storage/emulated/0/Download
        7. Tap, Reboot
        8. Done!
    7. Install/Update Magisk Modules

      • Download Modules
      • Install Modules

        1. Open Magisk
        2. Tap the Modules icon
        3. Tap Install from storage
        4. Navigate to the folder with the Module you want to install.
        5. Tap the Module to highlite it and tap Select.
        6. After it installs, tap the Disc Icon to save the install log.
        7. Tap Reboot
      • Update Modules

        1. Open Magisk
        2. Tap the Modules icon
        3. You, will see the Modules that have Updates.
        4. Tap the Module you want to update.
        5. Tap install.
        6. After it installs, tap the Disc Icon to save the install log.
        7. Tap Reboot
    8. Open a Command Prompt/Boot Fastboot Mode/Boot Recovery

      • Open a Command Prompt on Computer
        1. Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
        2. Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
        3. Notes:
          • Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
          • When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
          • If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
      • Boot fastboot mode (bootloader):
        • Power off phone, press and hold the power and volume down buttons until you see Start.
      • Boot Recovery
        • Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
    9. Test fastboot

      • Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
      • Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
        Enable USB Debugging.
      • Open a Command Prompt on your computer in the Platform-tools folder.
      • Boot fastboot mode on your phone
      • Connect the phone to the Computer.
      • At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
    10. ADB Sideload

    ~ ~ ~ Part III - OTHER ~ ~ ~
    1. Custom ROMs

      • Need help with a Custom ROM?
        • First, read and follow the Installation Instructions. The installation instructions are in the OP.
        • Second, if you have a problem Installing it, Search the thread of the Custom ROM you are trying to install for a solution to problem: If you don't find a solution post your request for help on the thread.
      • ROMs
        1. Alpha/Beta

          • None
        2. Official

          • None
        3. Unofficial
    2. Mods
    3. T.W.R.P. Backup/Restore

      • Waiting for Android 12 T.W.R.P.
    5
    I have modified the OP to make it easier to use. It has been divided into three parts: Information, Instructions, and Other.
    Tip: Read the, entire, Information Part first, then the Instructions for the operation you want to preform i.e., Install Factory image: Read Install/Update Factory Image keep data or wipe data, etc.
    3
    That screen doesn't have a "device corrupt" message on it though, so I assumed he wasn't talking about that.
    Twice in one day, you're gooooood! :)
    3
    Update
    Magisk Canary (756d8356) (24312)