Develop Bugs

Need help rooting

Hi guys, it's been several years since I last rooted phone. I got my Pixel 3 XL and tried to follow [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + instructions.
Did steps 4 and step 7.
TWRP installed and working. After Magisk 17.3 installation phone will not boot into system.
It will show G for 2 minutes and then it reboots back to TWRP.
I used provided links to latest files. I am lost. Am I missing some important step?
Thanks for help.. Charles

EvergreenExpert said:
Hi guys, it's been several years since I last rooted phone. I got my Pixel 3 XL and tried to follow [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + instructions.
Did steps 4 and step 7.
TWRP installed and working. After Magisk 17.3 installation phone will not boot into system.
It will show G for 2 minutes and then it reboots back to TWRP.
I used provided links to latest files. I am lost. Am I missing some important step?
Thanks for help.. Charles
Click to expand...
Click to collapse
SDK Platform-tools: r28.0.1
fastboot boot.img to both slots #6, fastboot boot twrp.img, install magisk's uninstaller, install magisk-17.3.zip, reboot system, done.

EvergreenExpert said:
Hi guys, it's been several years since I last rooted phone. I got my Pixel 3 XL and tried to follow [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + instructions.
Did steps 4 and step 7.
TWRP installed and working. After Magisk 17.3 installation phone will not boot into system.
It will show G for 2 minutes and then it reboots back to TWRP.
I used provided links to latest files. I am lost. Am I missing some important step?
Thanks for help.. Charles
Click to expand...
Click to collapse
Possible corrupted magisk file? Re-download the latest beta 17.3. I didn't have that problem but the general consensus has been to extract and flash the original boot.img and start over. Yes you will lose twrp, but from the PC you can flash the boot.img and then twrp.img right behind. Personally what I do on the phone is to queue up twrp.zip, kernel.zip, and magisk.zip and flash all 3 at the same time. Kernel is optional. Works well for me. Best of luck.

I am using Magisk v17.4.r18 which I understand is more reliable for rooting a Pixel 3 than 17.3.
You can find a link on to the newer Magisk from kantjer by searching XDA.

Homeboy76 said:
SDK Platform-tools: r28.0.1
fastboot boot.img to both slots #6, fastboot boot twrp.img, install magisk's uninstaller, install magisk-17.3.zip, reboot system, done.
Click to expand...
Click to collapse
No go..
I installed factory image - wiped data to start from clean slate using 9.0.0 (PQ1A.181105.017.A1, Nov 2018) SDK Platform-tools: r28.0.1
Boots fine... I setup the phone, gooole account, key pass etc.
Fastboot boot.img (extracted from PQ1A.181105.017.A1) - fastboot flash boot --slot all boot.img
All good booting fine.
fastboot boot twrp.img and install magisk's uninstaller
All good. Booting fine.
fastboot boot twrp.img and install magisk-17.3.zip
No more successful boot anymore.. Getting Big G for 2 minutes. Then reboot and error as shown on the picture. Something gets messed up after installation of magisk-17.3.zip
https://photos.google.com/share/AF1...?key=aW1ZQU14QVdVWGV6RTh4cWtTbkFhU3k1X25ZXzhn
I have downloaded all files again to start fresh..
Any suggestions? It sounds easy but something is not working for me..

Homeboy76 said:
SDK Platform-tools: r28.0.1
fastboot boot.img to both slots #6, fastboot boot twrp.img, install magisk's uninstaller, install magisk-17.3.zip, reboot system, done.
Click to expand...
Click to collapse
swieder711 said:
I am using Magisk v17.4.r18 which I understand is more reliable for rooting a Pixel 3 than 17.3.
You can find a link on to the newer Magisk from kantjer by searching XDA.
Click to expand...
Click to collapse
I tried to to download latest one from https://github.com/kantjer/MagiskFiles
Getting same error after installing Magisk.

EvergreenExpert said:
No go..
I installed factory image - wiped data to start from clean slate using 9.0.0 (PQ1A.181105.017.A1, Nov 2018) SDK Platform-tools: r28.0.1
Boots fine... I setup the phone, gooole account, key pass etc.
Fastboot boot.img (extracted from PQ1A.181105.017.A1) - fastboot flash boot --slot all boot.img
All good booting fine.
fastboot boot twrp.img and install magisk's uninstaller
All good. Booting fine.
fastboot boot twrp.img and install magisk-17.3.zip
No more successful boot anymore.. Getting Big G for 2 minutes. Then reboot and error as shown on the picture. Something gets messed up after installation of magisk-17.3.zip
https://photos.google.com/share/AF1...?key=aW1ZQU14QVdVWGV6RTh4cWtTbkFhU3k1X25ZXzhn
I have downloaded all files again to start fresh..
Any suggestions? It sounds easy but something is not working for me..
Click to expand...
Click to collapse
@EvergreenExpert
Never saw that error before.
So your bootloader is unlocked on your Pixel 3/Pixel 3 XL.
You have the latest SDK Platform-tools.
The following files are in the Platform-tools folder:
- fastboot
- Bootloader..img
- Radio...img
- Imagecrosshatch....zip
- flash-all.bat
- flash-base.sh
- Twrp.img (twrp-3.2.3-1...img)
You opened a command prompt in the Platform-tools folder (on your computer), booted the phone in fastboot mode, and did the following:
- installed the November factory image
- fastboot flash boot --slot all boot.img
- fastboot boot twrp.img
- installed magisk's uninstaller:
(Magisk-uninstaller-20181022.zip)
- installed Magisk-17.3.zip
In that order and got that error?
Was your pin set before you booted twrp?

Homeboy76 said:
@EvergreenExpert
Never saw that error before.
So your boot loader is unlocked on your Pixel3/ Pixel 3 XL.
You have the latest SDK Platform-tools.
The following files are in the Platform-tools folder:
- fastboot
- Bootloader..img
- Radio...img
- Imagecrosshatch....zip
Flash-all.bat
- Flash-base.sh
- Twrp.img (twrp-3.2.3-1...img)
You opened a command prompt in the Platform-tools folder (on your computer), booted the phone in fastboot mode, and did the following:
- installed the November factory image
- fastboot flash boot --slot all boot.img
- fastboot boot twrp.img
- installed magisk's uninstaller:
(Magisk-uninstaller-20181022.zip)
- installed Magisk-17.3.zip
In that order and got that error?
Was your pin set before you booted twrp?
Click to expand...
Click to collapse
Yes.. I did exactly that. Also tried to install newer version of Magisk.
Here is screenshot of folder with SDK Platform-tools: r28.0.1 and all files in it used.
https://photos.google.com/share/AF1...?key=U29nMDFYWFJnNnA4LTJNLTJTOWl3c3V1NFV0b3JB
Here are all files that I am working with including ones that go on the phone. All done from Windows 10 machine.
https://photos.google.com/share/AF1...?key=VnF4czY2OTZXS2JEdUJXcE50N3VJLXliVWlkYVVR
Bootloader unlocked on Pixel 3 XL. Pin set. Files on the phone copied over USB to Internal Shared Storage.
Phone boots fine even after Magisk uninstaller is installed. As soon as Magisk is installed it will not boot right. It will start booting, will show G for 2 minutes and reboots again just to show the error mentioned above. If I install TWRP on the phone it will reboot to TWRP instead of showing the error.
Got my phone on black Friday.. Maybe that why the phone was discounted.. LOL

Quick update... and one question.
So I did the same procedure again with exception of swipe to allow modifications.
Phone boots fine and appears to be rooted.
Does that provide any clues?
Also, what that means for me and updates? Do I need to watch and not allow OTA system updates or is there more to it?
Thanks Charles

EvergreenExpert said:
So I did the same procedure again with exception of swipe to allow modifications.
Phone boots fine and appears to be rooted.
Does that provide any clues?
Also, what that means for me and updates? Do I need to watch and not allow OTA system updates or is there more to it?
Thanks Charles
Click to expand...
Click to collapse
@EvergreenExpert
So you Added swipe to allow modifications after fastboot boot twrp.img? When you Reboot system did you skip (uncheck the two boxes - One is, "Install twrp as system")?
No. I always suggest twrp users swipe to allow modification (See guide below)
OTA System updates will unroot your phone. You can download the OTA image and sideload it.
After I root my phone, I go to Settings > System > Advanced > Deveoper options > turn off 'Automatic updates.
Then I do the following, monthly: Open this guide: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Do #4 'keep data' to update the factory image , then #8 to reroot.

Maybe I am doing something wrong after all.
My understanding is that I should always use Swipe to allow modification when installing TWRP, Magisk uninstall and Magisk.
In my case I did not permanently install TWRP just fastboot TWRP to install Magisk uninstall and Magisk.
When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked.
I have disabled automatic updates or your suggestion.

EvergreenExpert said:
Maybe I am doing something wrong after all.
My understanding is that I should always use Swipe to allow modification when installing TWRP, Magisk uninstall and Magisk.
In my case I did not permanently install TWRP just fastboot TWRP to install Magisk uninstall and Magisk.
When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked.
I have disabled automatic updates or your suggestion.
Click to expand...
Click to collapse
" When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked."
Please, share the exact other option you use to help other XDA members that are having problem installing Magisk-7.3.zip.

Homeboy76 said:
" When I use swipe to install Magisk it brakes system boot somehow. So I tried the other option something like read only option from desperation and it had worked."
Please, share the exact other option you use to help other XDA members that are having problem installing Magisk-7.3.zip.
Click to expand...
Click to collapse
I am referring to Keep Read Only button.. See the picture. I used that button instead of swipe button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

EvergreenExpert said:
I am referring to Keep Read Only button.. See the picture. I used that button instead of swipe button.
Click to expand...
Click to collapse
So instead of swiping to allow modifications you chose 'Keep read only' and it worked.
Great, thanks for sharing.

EvergreenExpert said:
Maybe I am doing something wrong after all....
Click to expand...
Click to collapse
No. I believe your intuition is correct. Ever since systemless root was the norm, I have *always* hit "keep read only" per Chainfire. I also install TWRP via the zip file (perm) because it is a Swiss Army knife I insist on having, and the stock recovery blows.. and IF for whatever reason I need blowing... I just flash the original boot.img. End of story. I also turn off the "twrp app install" and in settings turn off the screen timeout. Best of luck! :good:

EvergreenExpert said:
So I did the same procedure again with exception of swipe to allow modifications.
Phone boots fine and appears to be rooted.
Does that provide any clues?
Also, what that means for me and updates? Do I need to watch and not allow OTA system updates or is there more to it?
Thanks Charles
Click to expand...
Click to collapse
Where is the swipe to Allow modifications...never seen it

EvergreenExpert said:
I am referring to Keep Read Only button.. See the picture. I used that button instead of swipe button.
Click to expand...
Click to collapse
What was the exact build of TWRP that you used?

Everytime i install twrp i am asked to modify system. Or keep read only. Every version ive ever flashed

Hey guys, I am running into the same issue, with Magisk 18.1. Freezes on the load screen and then resets recovery (TWRP) after. The last time I tried to load the Magisk zip however, I got an error that read that vendor was not found or was busy.

How To Guide Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro

I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up!
Join our Discord Channel
Join the Red Magic 6 & 6 Pro [XDA Developers Forums] Discord Server!
Check out the Red Magic 6 & 6 Pro [XDA Developers Forums] community on Discord - hang out with 1 other members and enjoy free voice and text chat.
discord.gg
Youtube Video Tutorial:
UPDATED VIDEO:
For all those websites that claim the RM6 can be rooted with Kingroot, Kingoroot, iRoot, SuperSU... They are MISLEADING you into downloading their software. In other words, they are full of BS and you should INGORE them at all costs as Magisk is the ONLY proper way to root the RM6.
DO NOT USE KINGROOT, iROOT, KingoROOT, or ANY OTHER THIRD-PARTY ROOTING TOOLS PLEASE!! They steal your DATA and sell it. Magisk does not steal anything.​
This procedure will require a wipe of your data.. TWICE! I'll explain why.
When you unlock the bootloader, it wipes your data. Normally you only have to wipe it once, flash the patched boot.img file with magisk, and be done.
However, it seems that users will need to perform another factory reset after flashing the patched boot image. I have no idea why but it works. Please make a note of this as it will be required or you will be stuck in a bootloop.
Requirments
1. Global ROM file
2. A payload dumper
3. Magisk APK to patch the boot img
4. A computer!
Here are the steps!
​1. Unlock your bootloader. Make sure you enable OEM unlock in developer options. This WILL WIPE YOUR DEVICE! The command to unlock your bootloader is "fastboot flashing unlock"
2. Download the global rom from here: https://rom.download.nubia.com/Europe/NX669J/V312/NX669J-update.zip
3. You will need to download a payload dumper tool. This is due to the firmware being in a .bin file (payload.bin). Follow the link below on how to extract the global firmware:
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
I ended up Downloading Termux from the playstore and extracting it with python on my phone.
When you get it extracted, just move the boot.img and vbmeta.img files to your Desktop and on your phone Place it somewhere on your internal storage where you will remember!
4. Download Magisk Manager onto your phone and install it. Select install "patch a file" option and select the boot.img you put on your phone.
Let magisk patch it. It will end outputting a file like "Magisk_Patchedxxx.img" Go ahead and copy that file to your Desktop.
5. Go onto your computer and open up command prompt. Change your directory to the Desktop ex. cd c:/Users/Your Name/Desktop
6. Type fastboot flash boot magisk_patched.img
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. From the bootloader, reboot into your recovery and perform another factory reset!
9. Reboot the phone and voila! You now have root access!
Another thing to mention is that SafteyNet does NOT pass even with MagiskHide enabled. Please keep that in mind!
So far I've installed the Xposed Framework and some Magisk modules. All seems to work really well.
Happy Modding!
​

Do u have rom V3:10

chocolote4444 said:
I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up!
This procedure will require a wipe of your data.. TWICE! I'll explain why.
When you unlock the bootloader, it wipes your data. Normally you only have to wipe it once, flash the patched boot.img file with magisk, and be done.
However, it seems that users will need to perform another factory reset after flashing the patched boot image. I have no idea why but it works. Please make a note of this as it will be required or you will be stuck in a bootloop.
Requirments
1. Global ROM file
2. A payload dumper
3. Magisk APK to patch the boot img
4. A computer!
Here are the steps!
​1. Unlock your bootloader. Make sure you enable OEM unlock in developer options. This WILL WIPE YOUR DEVICE! The command to unlock your bootloader is "fastboot flashing unlock"
2. Download the global rom from here: https://rom.download.nubia.com/Europe/NX669J/V312/NX669J-update.zip
3. You will need to download a payload dumper tool. This is due to the firmware being in a .bin file (payload.bin). Follow the link below on how to extract the global firmware:
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
I ended up Downloading Termux from the playstore and extracting it with python on my phone.
When you get it extracted, just move the boot.img and vbmeta.img files to your Desktop and on your phone Place it somewhere on your internal storage where you will remember!
4. Download Magisk Manager onto your phone and install it. Select install "patch a file" option and select the boot.img you put on your phone.
Let magisk patch it. It will end outputting a file like "Magisk_Patchedxxx.img" Go ahead and copy that file to your Desktop.
5. Go onto your computer and open up command prompt. Change your directory to the Desktop ex. cd c:/Users/Your Name/Desktop
6. Type fastboot flash boot magisk_patched.img
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification vbmeta vbmeta.img
8. From the bootloader, reboot into your recovery and perform another factory reset!
9. Reboot the phone and voila! You now have root access!
Another thing to mention is that SafteyNet does NOT pass even with MagiskHide enabled. Please keep that in mind!
Edit:
Xposed Framework DOES work!
​
Click to expand...
Click to collapse
would be the same process for version V4.12?

Masacr3 said:
would be the same process for version V4.12?
Click to expand...
Click to collapse
Yes. Mine is showing up as still 4.12

Are you SURE it doesn't pass SafetyNet? The Magisk check is broken download SafetyNet Checker from the app store and see what it says...

mslezak said:
Are you SURE it doesn't pass SafetyNet? The Magisk check is broken download SafetyNet Checker from the app store and see what it says...
Click to expand...
Click to collapse
I does not pass safety net. I've tested every testing app on the Play Store. I'll keep looking for a solution though.

chocolote4444 said:
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
You're missing the "flash" command inside, as such:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
A couple of questions:
1: does the phone retain full functionality? radio (BT/A2DP/different wifi bands/fingerprint scanner/camera)?
2: have you tried using an empty vbmeta?

adwinp said:
You're missing the "flash" command inside, as such:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
A couple of questions:
1: does the phone retain full functionality? radio (BT/A2DP/different wifi bands/fingerprint scanner/camera)?
2: have you tried using an empty vbmeta?
Click to expand...
Click to collapse
Everything still works except the fingerprint. When the bootloader is unlocked, the fingerprint stops working.
As for flashing empty vbmeta images, I have not tried it. I know some devices you may have to flash an empty vbmeta img at last resort but I was able to boot it up using the stock vbmeta.

chocolote4444 said:
Everything still works except the fingerprint. When the bootloader is unlocked, the fingerprint stops working.
As for flashing empty vbmeta images, I have not tried it. I know some devices you may have to flash an empty vbmeta img at last resort but I was able to boot it up using the stock vbmeta.
Click to expand...
Click to collapse
Thx for responding.
1: Would you be able to test/comfirm if the fingerprint scanner is restored when relocking the bootloader using either the rooted boot.img or the stock one?
2: The same issue with fp calibration is faced by RM 5S/G users; can you check if the calibration fix in these forums works also for the RM6?
3: Lastly, have you tried flashing the latest phh GSI to see if it's working?

Yes usually you just flash stock vbmeta.img via fastboot: fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification should try it out...

adwinp said:
Thx for responding.
1: Would you be able to test/comfirm if the fingerprint scanner is restored when relocking the bootloader using either the rooted boot.img or the stock one?
2: The same issue with fp calibration is faced by RM 5S/G users; can you check if the calibration fix in these forums works also for the RM6?
3: Lastly, have you tried flashing the latest phh GSI to see if it's working?
Click to expand...
Click to collapse
Fingerprint scanner should work after relocking the bootloader. As for flashing a GSI, there's no custom recovery for this device yet so I can't test any GSI roms yet.

chocolote4444 said:
Fingerprint scanner should work after relocking the bootloader. As for flashing a GSI, there's no custom recovery for this device yet so I can't test any GSI roms yet.
Click to expand...
Click to collapse
In this case, would you be able to run the following tests & share findings?
1: reflash stock boot, relock BL - check if fingerprint scanner is fixed
2: flash rooted boot.img (disable vbmeta), relock BL - check if fingerprint is fixed
If that would be the case, we could copy the calibration data from such a device; the data would be in /mnt/vendor/persist/goodix - I checked the stock ROM & it's not in there meaning it probably gets copied over during boot or mount-binded.
The last theory I want to check is the link between BL lock status & the fingerprint scanner - if some people have reported success with fixing the scanner with the builtin tool, there's a chance that the system framework or some other app is checking for the bootloader lock status & disabling the fingerprint if the former is unlocked. I've dumped the stock firmware but couldn't find a goodix dedicated apk, hence my hunch that it's a framework overlay. We would need to identify where the code is stored, decompile, find the security checking routine, disable, recompile & check agian - assuming it's not in any of the native libraries or the binary.
Assuming the access to the fingerprint scanner is indeed baked into the framework, using an AOSP GSIs would mean that the system would get unrestricted access to the fingerprint scanner, thus no blocking issue.
Thus (& addressing the 2nd part of your previous response), I'd suggest a 3rd test:
3: flash phh GSI or LOS GSI. The reason for the latter is because LOS usually has a wider range of hardware supported via hardware overlays.
You don't need a custom recovery to flash GSIs as these are fastboot images, so the following should suffice:
Code:
fastboot flash system gsi.img
fastboot -w

Umm Sir, got some problem with the global rom i patched it from your link. i cannot save any photos even screenshot. its nothing on my gallery. it seems it is not saving any photo. i hope you can teach me to solve it. thanks in advance

whincloud01 said:
Umm Sir, got some problem with the global rom i patched it from your link. i cannot save any photos even screenshot. its nothing on my gallery. it seems it is not saving any photo. i hope you can teach me to solve it. thanks in advance
Click to expand...
Click to collapse
Do a factory reset as you need to properly reinitialize package IDs, SELinux contexts & permissions.

adwinp said:
Do a factory reset as you need to properly reinitialize package IDs, SELinux contexts & permissions.
Click to expand...
Click to collapse
thank you. it is working well now.

I did the root process, but the phone stayed in the redmagic logo and it does not start me, what is the next process? flash the stock boot.img and it won't start

@chocolote4444 please share the solution when it gets stuck on the logo

FFX2 said:
@chocolote4444 please share the solution when it gets stuck on the logo
Click to expand...
Click to collapse
I am currently looking into it

Thanks for the guide

Hi. Will this also work for Android 11 on RM 5s?

How To Guide [CLOSED] Firmware is out! Get your root on!

Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has - simply patch and flash the boot image.
Any update method can be used. If you've already disabled verity/verification, simply don't worry about it at next update; no need to re-enable.
I am closing this thread.
Spoiler: Deprecated
On Android 12, boot verification must be disabled in order to run a patched boot image. Unfortunately, if you have never disabled it before, it will require you to wipe data. To be clear:
***************************************************
PERMANENT ROOT CURRENTLY REQUIRES A DATA WIPE.
***************************************************
However, if you don't want to lose your data, you can "live boot" the patched image as long as /vbmeta and /boot are stock. This will allow you to use temporary root. DO NOT attempt to Direct Install Magisk to the boot image.
For subsequent updates, it is imperative that you do not allow the device to boot into system before you have disabled Verified Boot.
What this means: If you sideload the OTA, IMMEDIATELY reboot to bootloader and reflash /vbmeta with --disable-verity and --disable-verification. If you dirty flash the factory image, make sure you add these two switches to the command.
If you fail to do this, and allow the device to boot into system, you WILL have to wipe data to disable it again.
IF YOU ARE ROOTED, DO NOT USE AUTOMATIC UPDATES AS THIS WILL REFLASH /VBMETA WITHOUT DISABLING BOOT VERIFICATION!
Factory Images
OTA Images
Latest Magisk Canary
Spoiler: To root:
On your device, enable Developer Options (tap build number 8 times), and enable the OEM Unlocking toggle. Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader:
Code:
fastboot flashing unlock
Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img and vbmeta.img from this zip.
Flash vbmeta:
Code:
fastboot flash vbmeta --disable-verity --disable-verification <drag and drop vbmeta.img>
Allow the device to boot into Android. Once you have Magisk installed, copy the boot.img and patch it in Magisk, then copy it back to your PC.
Reboot to bootloader.
Flash patched boot image:
Code:
fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img>
Reboot into system.
Spoiler: For subsequent updates:
Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img from this zip.
Reboot to bootloader.
Update bootloader and radio if they are out of date. BE CAREFUL, A MISTAKE CAN BRICK YOUR DEVICE! If you update the bootloader, remember to reboot back to bootloader so that the update reads the correct bootloader version.
Update system:
Code:
fastboot update --disable-verity --disable-verification <drag and drop image-device-buildnumber.zip here>
Note: If you get an error for bootloader/radio version, this means you need to update bootloader and/or radio; go back to step 3.
Allow the device to boot into Android. Copy the boot.img and patch it in Magisk, then copy it back to your PC.
Reboot to bootloader.
Flash patched boot image:
Code:
fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img>
Reboot into system.
I personally do not recommend updating via OTA Sideload, as you would have to download and extract the factory zip anyway. AUTOMATIC OTA WILL LOSE ROOT AND REQUIRE A WIPE TO ROOT AGAIN.
Spoiler: If you choose to update via OTA Sideload:
Sideload the OTA. When complete, IMMEDIATELY reboot to bootloader.
Reflash vbmeta:
Code:
fastboot flash vbmeta --disable-verity --disable-verification <vbmeta.img>
Boot to system and allow the update to complete.
Patch and flash the boot image.
Note: If you run into a bootloader message
failed to load/verify boot images
this means you forgot to disable verity and verification. Reflash vbmeta with the --disable options.
If you run into this recovery message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This means that verity and verification were not disabled before, and a wipe is required to proceed.

one person had to wipe data otherwise it would not boot with verity disabled

Nekromantik said:
one person had to wipe data otherwise it would not boot with verity disabled
Click to expand...
Click to collapse
Yeah, this is an ongoing issue with the Pixel 5 as well.

Is the current belief that P6P/P6, like P4a and later will require a wipe when rooting after an update either by full image or OTA sideload?

If I disable verity and verification will it wipe my device? Also will this wipe remove my eSIM data?
I already unlocked bootloader and setup my device fully so I prefer to not have to start over.
Can I edit the flash.bat to disable verity and verification but remove the wipe flag?
fastboot update --disable-verity --disable-verification raven.zip
Click to expand...
Click to collapse

Wow, they are using an older image. I wonder if it includes the security update that we received when we first got the phone? The load that ends in .036....
EDIT: I am not sure I can do this since I updated to the .036 update. The boot image might be different.

V0latyle said:
Grab it here!
Factory image - SD1A.210817.015.A4
OTA - SD1A.210817.015.A4
Magisk 23011
To root:
Download the factory image. Extract it, then extract the raven-image.zip inside it
Copy boot.img to your phone. Patch with Magisk, then copy patched image back to PC.
Unlock bootloader:
Code:
fastboot flashing unlock
Flash vbmeta:
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Flash patched boot image:
Code:
fastboot flash boot magisk_patched-23xxx_xxxxx.img
Reboot, and you're done!
Note: If you run into a bootloader message
failed to load/verify boot images
this means you forgot to disable verity and verification.
If you run into a recovery message
Can't load Android system. Your data may be corrupted
Go ahead and factory wipe, it shouldn't be a big deal since you just did that with the bootloader unlock.
Click to expand...
Click to collapse
Thanks. Can confirm root is working perfectly
Didnt had to wipe data. Just did a clean wipe before doing rhe adb things

Goofy19882 said:
Thanks. Can confirm root is working perfectly
Didnt had to wipe data. Just did a clean wipe before doing rhe adb things
Click to expand...
Click to collapse
Did you have the Day 1 OTA security update before doing this?

rester555 said:
Did you have the Day 1 OTA security update before doing this?
Click to expand...
Click to collapse
No I havnt. Maybe this could be a problem

Super cool.
This isn't my bag anymore but I'm really pleased that Root is out already. It was only a matter of time and who knows what might be next with route.
Happy days with voice text (in the UK!)

Goofy19882 said:
No I havnt. Maybe this could be a problem
Click to expand...
Click to collapse
Agreed. I would be careful taking the OTA and trying to patch the boot image.

rester555 said:
Agreed. I would be careful taking the OTA and trying to patch the boot image.
Click to expand...
Click to collapse
I did that and it works fine. Im sure the kernel did not get updated in the OTA.

Nekromantik said:
I did that and it works fine. Im sure the kernel did not get updated in the OTA.
Click to expand...
Click to collapse
Just for clarity. You took the Day 1 OTA on the P6 Pro. You then extracted the boot.img and vbmeta.img from today's binaries and patched boot.img in magisk. Went to bootloader, did the disabling of verification with vbmeta and then flashed the patched magisk image?

rester555 said:
Just for clarity. You took the Day 1 OTA on the P6 Pro. You then extracted the boot.img and vbmeta.img from today's binaries and patched with magisk. Did the disabling of verification with vbmeta and then flashed the patched magisk image?
Click to expand...
Click to collapse
Yes
I had to factory reset after disabling verity.

Nekromantik said:
Yes
I had to factory reset after disabling verity.
Click to expand...
Click to collapse
Did you have to factory reset booted up or through recovery?

rester555 said:
Did you have to factory reset booted up or through recovery?
Click to expand...
Click to collapse
it wont boot after you disable verity so you get sent back to recovery where you can factory reset

Nekromantik said:
it wont boot after you disable verity so you get sent back to recovery where you can factory reset
Click to expand...
Click to collapse
I think I will do a wipe.

I just got my Pro and set it up and transferred data. Guess I'll have to start over when I unlock the bootloader.
Question though, when future OTAs release, what should we do? Okay to install and just lose root until new binaries are provided to re-root or would we install to new slot through magisk to keep root?

snovvman said:
Is the current belief that P6P/P6, like P4a and later will require a wipe when rooting after an update either by full image or OTA sideload?
Click to expand...
Click to collapse
The potential workaround, which doesn't seem to be solid, is to sideload the OTA, then immediately enter fastboot, and flash /vbmeta and /boot. Sometimes you'll still end up in Rescue Party, where you can either flash back to stock and try again, or give up and wipe. We are still testing over at the Pixel 5 forum.
Cares said:
If I disable verity and verification will it wipe my device? Also will this wipe remove my eSIM data?
Click to expand...
Click to collapse
No - these flags themselves do not command a wipe; data wipe is separate. I'm not sure about eSIM but I have never had an issue with my phone provisioning on Verizon after a wipe.
Cares said:
I already unlocked bootloader and setup my device fully so I prefer to not have to start over.
Can I edit the flash.bat to disable verity and verification but remove the wipe flag?
Click to expand...
Click to collapse
Yes.
rester555 said:
Wow, they are using an older image. I wonder if it includes the security update that we received when we first got the phone? The load that ends in .036....
EDIT: I am not sure I can do this since I updated to the .036 update. The boot image might be different.
Click to expand...
Click to collapse
Yeah, I would wait until the .036 firmware drops.

Well I removed the wipe flag and added disable verify and verification but got an error that didn't let me boot. I had to factory wipe unfortunately. So I guess I'm back to setting up my device.

How To Guide Method to upgrade every month, without wiping data and retaining root

Caution: I originally wrote this guide when it was necessary to disable verity and verification before flashing patched boot.img. Now Magisk has overcome this requirement and some users have reportedly flashed updates without disabling verification and verity and did not have to wipe their phones, but request everyone, who have verification and verity disabled and using this guide, make sure you backup all the data and post your results here (I suggest backing up data anyway for everyone).
Following is a guide to update Pixel 6 Pro (perhaps all Pixel devices) every month, without wiping and retaining root. I tested it on my Pixel 6 Pro from 12.0.0 (SD1A.210817.015.A4, Oct 2021) to 12.0.0 (SD1A.210817.036, Nov 2021). There is no reason that it should not work on subsequent monthly patches, but just take the backups to be sure.
1) Download the latest factory image for your device and platform-tools from the official Google site and extract them in one folder.
2) Extract the boot.img from image-raven-xxxxxxx.zip which was extracted from the image in the above step and patch it in Magisk Manager (latest canary build from https://github.com/topjohnwu/Magisk) on your phone and copy it back to the folder where you extracted the factory image and platform-tools. Rename the copied file to magisk_patched.img
3) Open flash-all.bat in notepad, add --skip-reboot and remove -w from the fastboot update line. Also add the following lines after the fastboot update line to flash the Magisk patched boot.img automatically:
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot magisk_patched.img
fastboot reboot
After editing, the edited part of your flash-all.bat should look something like this:
Code:
fastboot --skip-reboot update [****image_name****]
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot magisk_patched.img
fastboot reboot
echo Press any key to exit...
Note: [****image_name****] is just a placeholder and needs to be the name of zip file which was originally there in flash-all.bat, do not change that. Be careful to rename the Magisk patched boot.img to magisk_patched.img or in the alternative make appropriate modifications in the flash-all.bat
4) Open command prompt and go the folder where you extracted factory image and platform-tools. Type the following commands:
adb reboot bootloader
flash-all.bat
Your device should be upgraded to the latest factory image, while retaining root, without wiping data.
Update 1: I updated from 12.0.0 (SD1A.210817.036, Nov 2021) to 12.0.0 (SD1A.210817.037, Nov 2021) successfully using my method, without loosing data and root.
Update 2: I updated from 12.0.0 (SD1A.210817.037, Nov 2021) to 12.0.0 (SQ1D.211205.016.A1, Dec 2021) successfully using my method, without loosing data and root.
Update 3: I updated from 12.0.0 (SQ1D.211205.016.A1, Dec 2021) to 12.0.0 (SQ1D.220105.007, Jan 2022) successfully using my method, without loosing data and root.
Update 4: I updated from 12.0.0 (SQ1D.220105.007, Jan 2022) to 12.0.0 (SQ1D.220205.003, Feb 2022) successfully using my method, without loosing data and root.
Update 5: I updated from 12.0.0 (SQ1D.220205.003, Feb 2022) to Android 12L DP 3 successfully using my method, without loosing data and root.
Update 6: I updated from Android 12L DP 3 to Android 13 DP successfully using my method, without loosing data and root.

gururoop said:
Just a word of caution, I won't be able to support this guide every month because I am returning my Pixel 6 Pro. But it did give me a chance to experiment for the benefit of community, so here it is:
Note: I was already on the November patch, rooted before I tried flashing the November factory image again without wiping data and retaining root. There is no reason that it should not work on subsequent monthly patches, but just take the backups to be sure.
1) Download the latest factory image for your device and platform-tools from the official Google sites and extract them in one folder.
2) Extract the boot.img and patch it in magisk manager on your phone and copy it back to the folder where you extracted the factory image and platform-tools.
3) Open flash-all.bat in notepad and remove -w and add --disable-verity, -- disable verification and --skip-reboot to the fastboot update line. After editing, it should read as:
fastboot --disable-verity --disable-verification update image-raven-xxxxxxxxxxxx.zip --skip-reboot
4) Open command prompt and go the folder where you extracted factory image and platform-tools. Type the following commands:
adb reboot bootloader
flash-all.bat
5) After the factory image is flashed, use the volume down button to select reboot to bootloader option and press power button to execute. Then, open the command prompt again and go the folder where you extracted factory image and platform-tools. Type the following commands:
fastboot flash boot magisk_patched-xxxxx.img
fastboot reboot
Your device should be upgraded to the latest factory image, while retaining root, without wiping data.
Click to expand...
Click to collapse
Why did you return it?

Gytole said:
Why did you return it?
Click to expand...
Click to collapse
I've got Pixel 4 XL, which will get another OS upgrade. I don't want a big screen and I don't use camera. In 6 Pro, I was missing active edge (which I use for flashlight). Plus, I don't use my phone for gaming or any other heavy stuff, so I didn't feel as if it was a huge upgrade for me. Finally, I hate the huge camera module on the back.

gururoop said:
I've got Pixel 4 XL, which will get another OS upgrade. I don't want a big screen and I don't use camera. In 6 Pro, I was missing active edge (which I use for flashlight). Plus, I don't use my phone for gaming or any other heavy stuff, so I didn't feel as if it was a huge upgrade for me. Finally, I hate the huge camera module on the back.
Click to expand...
Click to collapse
Just about to try this method now as I too am on rooted 036 but want to dirty flash the latest factory image to hopefully fix some google play services bugs.
Did you buy the phone or get through a contract? Do Google/mobile network providers allow returns if it's been bootloader unlocked/relocked?

gururoop said:
I've got Pixel 4 XL, which will get another OS upgrade. I don't want a big screen and I don't use camera. In 6 Pro, I was missing active edge (which I use for flashlight). Plus, I don't use my phone for gaming or any other heavy stuff, so I didn't feel as if it was a huge upgrade for me. Finally, I hate the huge camera module on the back.
Click to expand...
Click to collapse
I hear yuh, I get mine today. I am coming from a Oneplus 6T, so it might be an upgrade for me. I understand though. Haha Thanks fam.

cd993 said:
Just about to try this method now as I too am on rooted 036 but want to dirty flash the latest factory image to hopefully fix some google play services bugs.
Did you buy the phone or get through a contract? Do Google/mobile network providers allow returns if it's been bootloader unlocked/relocked?
Click to expand...
Click to collapse
I got mine on a contract, but here in Canada, it is not allowed for the carriers to restrict bootloader unlocking. I will simply relock the bootloader before returning. That's what I did with Pixel 5 too.

Gytole said:
I hear yuh, I get mine today. I am coming from a Oneplus 6T, so it might be an upgrade for me. I understand though. Haha Thanks fam.
Click to expand...
Click to collapse
I am sure you will love it. I swapped my Oneplus 7 Pro for this Pixel 4 XL in 2020 and haven't regretted a single day. The monthly updates and betas are something that I love.

What's wrong with flashing the update, not rebooting, installing Magisk to the inactive slot, and then rebooting?

gururoop said:
Just a word of caution, I won't be able to support this guide every month because I am returning my Pixel 6 Pro. But it did give me a chance to experiment for the benefit of community, so here it is:
Note: I was already on the November patch, rooted before I tried flashing the November factory image again without wiping data and retaining root. There is no reason that it should not work on subsequent monthly patches, but just take the backups to be sure.
1) Download the latest factory image for your device and platform-tools from the official Google sites and extract them in one folder.
2) Extract the boot.img and patch it in magisk manager on your phone and copy it back to the folder where you extracted the factory image and platform-tools.
3) Open flash-all.bat in notepad and remove -w and add --disable-verity, -- disable verification and --skip-reboot to the fastboot update line. After editing, it should read as:
fastboot --disable-verity --disable-verification update image-raven-xxxxxxxxxxxx.zip --skip-reboot
4) Open command prompt and go the folder where you extracted factory image and platform-tools. Type the following commands:
adb reboot bootloader
flash-all.bat
5) After the factory image is flashed, use the volume down button to select reboot to bootloader option and press power button to execute. Then, open the command prompt again and go the folder where you extracted factory image and platform-tools. Type the following commands:
fastboot flash boot magisk_patched-xxxxx.img
fastboot reboot
Your device should be upgraded to the latest factory image, while retaining root, without wiping data.
Click to expand...
Click to collapse
Followed exactly, however it returned an error after running flash-all.bat and attempting to flash the boot.img (which had been patched).......

cd993 said:
Followed exactly, however it returned an error after running flash-all.bat and attempting to flash the boot.img (which had been patched).......
Click to expand...
Click to collapse
Are you sure you rebooted to bootloader after flash-all.bat finished?

gururoop said:
Are you sure you rebooted to bootloader after flash-all.bat finished?
Click to expand...
Click to collapse
flash-all.bat didn't finish as it stumbled when flashing the boot.img. It must not like the fact it's been extracted/patched/replaced?
Hmmmm

cd993 said:
flash-all.bat didn't finish as it stumbled when flashing the boot.img. It must not like the fact it's been extracted/patched/replaced?
Hmmmm
Click to expand...
Click to collapse
Did you replace the patched boot image in the zip file? You don't need to do that, just let flash-all.bat flash the original file and then flash the patched boot image as per the instructions.

spotmark said:
What's wrong with flashing the update, not rebooting, installing Magisk to the inactive slot, and then rebooting?
Click to expand...
Click to collapse
Some people have reported that it doesn't work because you need to disable verity and verification for new devices.

gururoop said:
Did you replace the patched boot image in the zip file? You don't need to do that, just let flash-all.bat flash the original file and then flash the patched boot image as per the instructions.
Click to expand...
Click to collapse
My bad, that's exactly what I did....
But now I'm getting this system 1/4 error?
I started a fresh with the extracted factory image too..... ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Just tried this on my P6Pro. Managed to update from .015 to .036 and retained root.
Also still passing SafetyNet with USNF 2.2 beta

cd993 said:
My bad, that's exactly what I did....
But now I'm getting this system 1/4 error?
I started a fresh with the extracted factory image too..... ?
View attachment 5447353
Click to expand...
Click to collapse
I am not sure, but these kind of errors are usually related to cables. Try switching the cable and see.

In the end, flashing should happen on both boot slots. I have come across various posts (including also my tries) where partition B was active afterwards and root was gone.
Details how it works described in this thread/post

In the other method, when sideloading the OTA, you have to make sure to not reboot so that you can flash vbmeta before restarting in order to avoid Rescue Party and wiping your device. In this method, isn't vbmeta flashed in the batch file with verity and verfication disabled? Why do you have to prevent restart?

Annil said:
In the end, flashing should happen on both boot slots. I have come across various posts (including also my tries) where partition B was active afterwards and root was gone.
Details how it works described in this thread/post
Click to expand...
Click to collapse
Well, I have used this method for several months on my Pixel 4 XL (without disabling verity and verification) and now even on Pixel 6 Pro with same results. I have never tinkered with slots, but still managed to keep data and root.

Cares said:
In the other method, when sideloading the OTA, you have to make sure to not reboot so that you can flash vbmeta before restarting in order to avoid Rescue Party and wiping your device. In this method, isn't vbmeta flashed in the batch file with verity and verfication disabled? Why do you have to prevent restart?
Click to expand...
Click to collapse
Just to avoid the hassle of another reboot to flash the Magisk patched boot image for root.

[GUIDE] Pixel 4a (5G) "bramble": Unlock Bootloader, Update, Root, Pass SafetyNet

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 5
Pixel 5a
Pixel 6
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!

V0latyle said:
DO NOT take the automatic OTA if you are rooted.
Click to expand...
Click to collapse
Well, that explains why I haven't been able to update boot with my patched file.
First I've heard of it and not sure I'm ready to wipe everything and start over.
Sucks to be an early adopter.
Thanks for the post.

Hi ! Thanks for the thread .
Just one question ?
Why they had "--slot=all" for flash vmbeta and patch boot.

ggkameleon said:
Hi ! Thanks for the thread .
Just one question ?
Why they had "--slot=all" for flash vmbeta and patch boot.
Click to expand...
Click to collapse
The OTA is an out of band update, meaning it installs to the inactive slot. I like to command a flash to both slots just to be safe. It may not really be necessary, but again, better safe than sorry.

V0latyle said:
The OTA is an out of band update, meaning it installs to the inactive slot. I like to command a flash to both slots just to be safe. It may not really be necessary, but again, better safe than sorry.
Click to expand...
Click to collapse
Ok Thank you I understand... Just I do it now. Have a good day

ggkameleon said:
Ok Thank you I understand... Just I do it now. Have a good day
Click to expand...
Click to collapse
NO U

V0latyle said:
As many of you know by now, in order to run a patched boot image on Android 12 requires disabling Android Boot Verification.
On Android 12, disabling verity and verification will require a data wipe if it hasn't been done before. What seems to "lock" the state of boot verification is booting into system; so, if you perform an update, or flash vbmeta without the disable flags, then reboot into Android, you have essentially enabled boot verification and will require a wipe to disable it again. Confusing, I know.
Click to expand...
Click to collapse
So, for all slow dumb ****s like me:
No permanent root possible on my 4a 5G when updating from A11 to A12 without a wipe?
Or is this tutorial the workaround for that?
Or is this tutorial the workaround for flashing patched boot for the monthly security updates for A12 so I don't have to wipe each month?
Or, I'm just a slow dumb ****?
¯\_(ツ)_/¯

j-a-d-z said:
So, for all slow dumb ****s like me:
No permanent root possible on my 4a 5G when updating from A11 to A12 without a wipe?
Or is this tutorial the workaround for that?
Click to expand...
Click to collapse
As it seems, yes. But I have a theory if you want to be a test subject....
j-a-d-z said:
Or is this tutorial the workaround for flashing patched boot for the monthly security updates for A12 so I don't have to wipe each month?
Or, I'm just a slow dumb ****?
¯\_(ツ)_/¯
Click to expand...
Click to collapse
This is meant for updating but still applies the first time you root on A12.

V0latyle said:
As it seems, yes. But I have a theory if you want to be a test subject....
This is meant for updating but still applies the first time you root on A12.
Click to expand...
Click to collapse
What does your "yes" stands for? Yes, no permanent root without wipe? Or yes, that may be the workaround?
If I wanna be your test subject, what could go wrong in the worst case scenario? (or the "Wurst-Käse-Szenario", as we like to say here in Germany )
Would I still be able to fastboot boot the magisked boot image to gain temp root and backup my in-app data?

j-a-d-z said:
What does your "yes" stands for? Yes, no permanent root without wipe? Or yes, that may be the workaround?
Click to expand...
Click to collapse
I mean yes as in "yes, it appears that wiping /data is required when disabling vbmeta for permanent root".
j-a-d-z said:
If I wanna be your test subject, what could go wrong in the worst case scenario? (or the "Wurst-Käse-Szenario", as we like to say here in Germany )
Click to expand...
Click to collapse
Das ist mir Wurst.
The sausage cheese scenario is that you lose your data and have to wipe anyway. What I have in mind is this: Reflash vbmeta with the disable flags while on Android 11, die Daumen drucken, see if it requires you to wipe /data. If not, proceed to dirty flash factory image with disable flags and see if the upgrade is successful.
j-a-d-z said:
Would I still be able to fastboot boot the magisked boot image to gain temp root and backup my in-app data?
Click to expand...
Click to collapse
Temp root does work on Android 12. And if my idea sorta works but you still get Rescue Party after upgrading to Android 12, then you should just be able to reflash /vbmeta and /boot with the stock images and use temp root.
I would advise, however, that if you're interested in trying my idea, make sure to back up your data first.

V0latyle said:
NO U
Click to expand...
Click to collapse
Thanks for all your search and works The month update after first wipe work fine .

V0latyle said:
The sausage cheese scenario is that you lose your data and have to wipe anyway. What I have in mind is this: Reflash vbmeta with the disable flags while on Android 11, die Daumen drucken, see if it requires you to wipe /data. If not, proceed to dirty flash factory image with disable flags and see if the upgrade is successful.
Click to expand...
Click to collapse
Does this vbmeta reflash warn me that a wipe is required before it does anything?

So can I update A11 to A12 and retain root as long as I don't boot into the system before flashing vbmeta.img and boot.img?

j-a-d-z said:
Does this vbmeta reflash warn me that a wipe is required before it does anything?
Click to expand...
Click to collapse
Reflashing vbmeta doesn't wipe your data. If you disable verity and verification, when they were previously enabled, the system will not boot, and you will instead land in Rescue Party - a screen telling you that your data may be corrupted.
So, when we say that a data wipe is required, it means you must do it yourself.
dneill2006 said:
So can I update A11 to A12 and retain root as long as I don't boot into the system before flashing vbmeta.img and boot.img?
Click to expand...
Click to collapse
As far as we know, no. The problem is, as I stated above, the first time verity and verification are disabled on Android 12 requires a clean system. We have not found a way to be able to keep data and re-root following an upgrade. You can keep your data and either go unrooted or use temporary root, or you can wipe data for permanent root.

Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before.
Q: "If verity/verification are disabled, do I need to enable them now?"
A: No. The only thing you have to do is update to Magisk 23016.
Q: "Will enabling verity/verification wipe my data?"
A: No.
I will be updating the OP to reflect this.

V0latyle said:
Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before.
Click to expand...
Click to collapse
So I did upgrading from latest 11 to latest 12 some minutes ago. Booted, patched boot.img with magisk 23016 and flashed the patched image to get back root. Worked like a charm just like any update before. So no more wipe needed.
So, it's time for the good old pal Stinky Wizzleteats and his song about being happy. That's right, it's the happy, happy, joy, joy song:
Happy, happy, joy, joy
Happy, happy, joy, joy
Happy, happy, joy, joy
Happy, happy, joy, joy
Happy, happy, joy, joy
Happy, happy, joy, joy
┌(・。・)┘♪

j-a-d-z said:
┌(・。・)┘♪
Click to expand...
Click to collapse
(ノಠ益ಠ)ノ彡/(.□ . \)

V0latyle said:
Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has.
If you have already disabled verity/verification, you do not need to re-enable them; they are enabled by default when the /vbmeta partition is written, unless the "--disable-" options are used. The only thing you have to worry about next update is literally just updating your device.
DO NOT substitute Magisk Stable, as it does not yet include the necessary fixes for this device!
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
"Installed" shows the version of patch in the boot image. If this says N/A, the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
Prerequisites:
Unlocked bootloader
Latest SDK Platform Tools
Spoiler: Deprecated - this is now irrelevant
As many of you know by now, in order to run a patched boot image on Android 12 requires disabling Android Verified Boot.
Verified Boot on Android 12 devices, at least Pixels with the SD765G and Tensor, is tied to device encryption. Therefore, disabling Verified Boot requires a wipe, if it was not previously disabled.
To make this clear:
Verified Boot is disabled by flashing /vbmeta with disable flags:
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Verified Boot is enabled by flashing /vbmeta without flags:
Code:
fastboot flash vbmeta vbmeta.img
Booting the device essentially "locks" the vbmeta state.
I know this is confusing, Bear with me:
If you previously disabled vbmeta, you MUST ensure it is disabled again when you update, BEFORE you boot. If you do not, you will have to wipe to regain root.
Unfortunately, the update process enables Verified Boot by default, because it writes /vbmeta without flags.
This means that the automatic OTA, or any other update process without intervention, WILL enable Verified Boot, which will require a wipe to disable!
****
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Canary
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to complete. Your device will reboot without root as the OTA overwrites the patched boot image.
Reboot your device to bootloader.
Boot the master root image (See note 1)
Code:
fastboot boot <drag and drop master root.img here>
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to bootloader".
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Check the "Skip reboot" box.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet
This is my configuration:
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Services
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
MagiskHide Props Config 6.1.2
Universal SafetyNet Fix 2.2.0
Note 1: If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
Note 2: If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Click to expand...
Click to collapse

Already rooted, do I need to uninstall magisk and delete all modules? Then OTA Android 12, and then install 230016.

proac said:
Already rooted, do I need to uninstall magisk and delete all modules? Then OTA Android 12, and then install 230016
Click to expand...
Click to collapse
First, update Magisk to 23016. Do this from within the Magisk app.
Next, follow the instructions under "Initial Root" to patch the boot image. You can then use any method to upgrade to Android 12; after you have upgraded, flash the patched boot image. I recommend using the factory image method seeing as you will have already downloaded the factory image.