Develop Bugs

[Question] How to apply security patch to rooted device.

Hey, I previously rooted my phone and would like to apply new the January Security update. I am wondering if someone can outline the steps to apply this new update without wiping any of the data off my phone.
From what I understand I need to do the following.
Download OTA image from google
Download newest Magisk image
Download TWRP
Extract OTA (Radio, Update and Bootloader)
Extract TWRP
Copy Magisk to Phone
Copy TWRP Installer (Optional)
Then the work on the phone
1.
Code:
fastboot-devices
fastboot flash bootloader new-bootloader-image (then reboot into bootloader)
fastboot flash radio new-radio-image (then reboot into bootloader)
fastboot flash update new-update-image (then reboot into twrp)
fastboot boot twrp-image
2.
In TWRP Decrypt data and install Magisk newest release
3.
Profit now it works?!
I just wanted some confirmations before I go and do this before I make a mess. Also has anyone had issues with TWRP being able to decrypt data with this security update

ericedg said:
Hey, I previously rooted my phone and would like to apply new the January Security update. I am wondering if someone can outline the steps to apply this new update without wiping any of the data off my phone.
From what I understand I need to do the following.
Download OTA image from google
Download newest Magisk image
Download TWRP
Extract OTA (Radio, Update and Bootloader)
Extract TWRP
Copy Magisk to Phone
Copy TWRP Installer (Optional)
Then the work on the phone
1.
2. In TWRP Decrypt data and install Magisk newest release
3. Profit now it works?!
I just wanted some confirmations before I go and do this before I make a mess. Also has anyone had issues with TWRP being able to decrypt data with this security update
Click to expand...
Click to collapse
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + January 2019 Security Patch
'If Stock'
Do #4 'keep data'' then do #8 to root/Reroot
'If Custom ROM'
Read #11

The above instructions are very ambiguous for a patch upgrade, i'm finding all kinds of inconsistencies with the directions. Currently stuck trying to flash payload.bin from the ota and it's saying cannot determine image filename for payload.bin.

dhufford81 said:
The above instructions are very ambiguous for a patch upgrade, i'm finding all kinds of inconsistencies with the directions. Currently stuck trying to flash payload.bin from the ota and it's saying cannot determine image filename for payload.bin.
Click to expand...
Click to collapse
Download stock factory image, decompress, open terminal or cmd line and change directories into the decompressed folder, remove -w from flash-all script, and run the script.
Then fastboot boot twrp on use booted twrp to flash twrp, kernel, & magisk.

smartymcfly said:
Download stock factory image, decompress, open terminal or cmd line and change directories into the decompressed folder, remove -w from flash-all script, and run the script.
Then fastboot boot twrp on use booted twrp to flash twrp, kernel, & magisk.
Click to expand...
Click to collapse
Thank you for clearing up that i shouldn't be trying to flash the OTA download, that's where i got hungup. Cheers!

dhufford81 said:
Thank you for clearing up that i shouldn't be trying to flash the OTA download, that's where i got hungup. Cheers!
Click to expand...
Click to collapse
TWRP had the ability to flash the OTA update on P2XL. It might be something that works again P3XL in the future.

Has anyone successfully updated to Android 11 with Magisk?

I see "11.0.0 (RQ1A.201205.003, Dec 2020" is available for Crosshatch and Blueline.
I'm still on Android 9 with Magisk installed by patching the boot image.
Is the following process still valid and supported for applying an OTA update to Android 11, and then re-installing Magisk?
1) Magisk Manager → Uninstall → Restore Images
2) Apply the OTA update :
__a) Boot into factory recovery
__b) Choose Apply update from ADB
__c) From windows: adb sideload crosshatch-ota-rq1a.201205.003-4d6e609b.zip
__d) Reboot phone and let the update finish in Android
3) Separately download the corresponding Factory image: crosshatch-rq1a.201205.003-factory-d5cb2a93.zip. Extract the boot.img, move it into the Pixel 3 XL's download folder
4) Uninstall old Magisk manager and install the latest Magisk Manager (Direct Install Magisk Manager v8.0.4 from here, per Magisk installation instructions)
5 ) Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file in "Download". It will be patched.
6) Copy the magisk_patched.img file to your computer's Platform-tools folder
7) Boot Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
8) Once phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
9) Once it's done then type the command : fastboot reboot
10) Open Magisk Manager and check if its rooted
This is based on the process from about a year ago. so please reply if anything has changed.

timg11 said:
I see "11.0.0 (RQ1A.201205.003, Dec 2020" is available for Crosshatch and Blueline.
I'm still on Android 9 with Magisk installed by patching the boot image.
Is the following process still valid and supported for applying an OTA update to Android 11, and then re-installing Magisk?
1) Magisk Manager → Uninstall → Restore Images
2) Apply the OTA update :
__a) Boot into factory recovery
__b) Choose Apply update from ADB
__c) From windows: adb sideload crosshatch-ota-rq1a.201205.003-4d6e609b.zip
__d) Reboot phone and let the update finish in Android
3) Separately download the corresponding Factory image: crosshatch-rq1a.201205.003-factory-d5cb2a93.zip. Extract the boot.img, move it into the Pixel 3 XL's download folder
4) Uninstall old Magisk manager and install the latest Magisk Manager (Direct Install Magisk Manager v8.0.4 from here, per Magisk installation instructions)
5 ) Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file in "Download". It will be patched.
6) Copy the magisk_patched.img file to your computer's Platform-tools folder
7) Boot Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
8) Once phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
9) Once it's done then type the command : fastboot reboot
10) Open Magisk Manager and check if its rooted
This is based on the process from about a year ago. so please reply if anything has changed.
Click to expand...
Click to collapse
You might be able to skip all the step 2's and just check for update after unrooting and take the ota normally. That has worked for me for quite awhile.
Other than that, your steps are spot on and work with 11.

TonikJDK said:
You might be able to skip all the step 2's and just check for update after unrooting and take the ota normally. That has worked for me for quite awhile.
Other than that, your steps are spot on and work with 11.
Click to expand...
Click to collapse
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?

timg11 said:
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?
Click to expand...
Click to collapse
Best practice would be to do an actual update and reboot bootloader to flash your patched boot.img. If you are jumping android releases problems might arise that no one can account for and generally you should do a full wipe when switching releases. Google has by no means accounted for any contingencies in the ota process, read the disclaimer they give upon an ota (any data lost in the process is never their fault, so backup you stuff). Patching the boot image through the manager is the preferred method, anything else is very difficult to troubleshoot.

timg11 said:
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?
Click to expand...
Click to collapse
By boot method do you mean unroot, do not boot, update do not boot, then root the inactive slot?
Do not do that, on 11 it can go bad in fact if you have 11 it will not even be available in Magisk. He took it out for now due to problems.
What I was suggesting bead unroot, boot, take the OTA, boot. Then patch the boot img and flash it.

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.

Question How to upgrade to the latest patch of Android 12

Hey guys recived an update through the OnePlus oxygen updater today, currently in the "Stable" Android 12 release but after downloading the latest patch i noticed that there is no local upgrade option like it used to be prior, am i missing something here ? Thanks.

How to update from OnePlus 9 Pro Oxygen OS 12.0.0.0.LE15 to today's fixed OOS 12? Local update no longer available in settings/update

This might help: https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk

Zip file not showing on update.. and yes is in main storage

Option 2: with incremental OTA Access (AA) :​
Step 1 - Get back your original boot image​1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
{
"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"
}
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 9 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot

Progaros said:
This might help: https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Click to expand...
Click to collapse
Thanks a ton! This helped me to upgrade my incremental update!

PKkeys said:
Thanks a ton! This helped me to upgrade my incremental update!
Click to expand...
Click to collapse
Didn't work for me guide above so used APK to bring back local upgrade

More importantly, now that you patched to the latest, is it still a cleveland steamer?

toolhas4degrees said:
Option 2: with incremental OTA Access (AA) :​
Step 1 - Get back your original boot image​1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock boot image that was backed up during the rooting process.
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 9 Pro
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Click to expand...
Click to collapse
any other option to install incremental update? because i am getting failed message during installation despite this procedures

AboAnas25 said:
any other option to install incremental update? because i am getting failed message during installation despite this procedures
Click to expand...
Click to collapse
No and it doesn't work on a12 as I have tried. You need to unroot. Install the update.
/save msm_pull
Using MSM tool to pull boot.img, vendor_boot.img, and vbmeta:
1) Find out what your current active slot with either adb shell getprop ro.boot.slot_suffix or fastboot getvar current-slot
2) Open the MSM tool select Other at the top and Next button if you have to
3) Hit F8. Put a checkbox in boot_a or boot_b, vendor_boot_a or vendor_boot_b, and vbmeta files (whichever is your current active slot.) Password is: oneplus (case sensitive.) There will be a new Read Back button at the top
3) Put the phone in EDL mode....adb reboot edl...is easier than buttons but whatever. As soon as you see it's connected, hit the Read Back button.
4) Read back will only take a few seconds. File(s) will end up on the root of your PC's C:\ drive.
Next put the vendor_boot and boot images on your phone patch each with magisk. Copy the patched images back to your fastboot folder and put the vbmeta image there as well.
Next Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
***_**_*Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform-tools
If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot

AboAnas25 said:
any other option to install incremental update? because i am getting failed message during installation despite this procedures
Click to expand...
Click to collapse
The problem is Google installer... And the fact you need to patch 2 images and remove verification and verity

toolhas4degrees said:
No and it doesn't work on a12 as I have tried. You need to unroot. Install the update.
/save msm_pull
Using MSM tool to pull boot.img, vendor_boot.img, and vbmeta:
1) Find out what your current active slot with either adb shell getprop ro.boot.slot_suffix or fastboot getvar current-slot
2) Open the MSM tool select Other at the top and Next button if you have to
3) Hit F8. Put a checkbox in boot_a or boot_b, vendor_boot_a or vendor_boot_b, and vbmeta files (whichever is your current active slot.) Password is: oneplus (case sensitive.) There will be a new Read Back button at the top
3) Put the phone in EDL mode....adb reboot edl...is easier than buttons but whatever. As soon as you see it's connected, hit the Read Back button.
4) Read back will only take a few seconds. File(s) will end up on the root of your PC's C:\ drive.
Next put the vendor_boot and boot images on your phone patch each with magisk. Copy the patched images back to your fastboot folder and put the vbmeta image there as well.
Next Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
***_**_*Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform-tools
If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
Click to expand...
Click to collapse
Makes sense. Thank you for this post.
If possible, I think it would be helpful to others if you (or somebody else) can upload and share those new stock vendor-boot/boot/vbmeta images that were dumped using the msmtool. Would save a lot of trouble to others.
Thanks again!

toolhas4degrees said:
No and it doesn't work on a12 as I have tried. You need to unroot. Install the update.
/save msm_pull
Using MSM tool to pull boot.img, vendor_boot.img, and vbmeta:
1) Find out what your current active slot with either adb shell getprop ro.boot.slot_suffix or fastboot getvar current-slot
2) Open the MSM tool select Other at the top and Next button if you have to
3) Hit F8. Put a checkbox in boot_a or boot_b, vendor_boot_a or vendor_boot_b, and vbmeta files (whichever is your current active slot.) Password is: oneplus (case sensitive.) There will be a new Read Back button at the top
3) Put the phone in EDL mode....adb reboot edl...is easier than buttons but whatever. As soon as you see it's connected, hit the Read Back button.
4) Read back will only take a few seconds. File(s) will end up on the root of your PC's C:\ drive.
Next put the vendor_boot and boot images on your phone patch each with magisk. Copy the patched images back to your fastboot folder and put the vbmeta image there as well.
Next Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
***_**_*Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform-tools
If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
Click to expand...
Click to collapse
You shouldn't need all those extra images/partitions if you use magisk alpha. Just boot patched boot.img then open magisk and do a direct install.

terlynn4 said:
You shouldn't need all those extra images/partitions if you use magisk alpha. Just boot patched boot.img then open magisk and do a direct install.
Click to expand...
Click to collapse
Where did you get a boot image from? This method will work on an6 magisk. You can't on a incremental update.. if you had a full zip yes I tried with alpha first the old method of removing and patching no longer works. So msm tool is your option... Other than that show me how you updated without pulling it. Since the ita won't work with payload dumper

toolhas4degrees said:
You can't on a incremental update.. if you had a full zip yes I tried with alpha first
Click to expand...
Click to collapse
There's no need to do vendor boot when using Magisk Alpha, even on instrumentals. All I had to do to root was restore stock c.36 boot and vbmeta, update to c.39 and then use MSM to pull vbmeta and boot. I patched the boot with Magisk Alpha, booted the patched boot.img and then when in OS did a direct install. Didn't have to re-disable verity or flash vbmeta again either after updating, only using patched boot.img.

toolhas4degrees said:
You can't on a incremental update.. if you had a full zip yes I tried with alpha first
Click to expand...
Click to collapse
If you're already rooted before updating you can just restore images from magisk, install the update, install magisk to inactive slot, then reboot. That's what I did for the incremental. But even if you're already rooted you shouldn't need vbmeta. Granted, things don't *always* work like they should.
jeffsga88 said:
There's no need to do vendor boot when using Magisk Alpha, even on instrumentals. All I had to do to root was restore stock c.36 boot and vbmeta, update to c.39 and then use MSM to pull vbmeta and boot. I patched the boot with Magisk Alpha, booted the patched boot.img and then when in OS did a direct install. Didn't have to re-disable verity or flash vbmeta again either after updating, only using patched boot.img.
Click to expand...
Click to collapse
Yeah, this is the behavior I would expect. So you didn't actually do anything with vbmeta, right? You just pulled it in case you needed it?

terlynn4 said:
If you're already rooted before updating you can just restore images from magisk, install the update, install magisk to inactive slot, then reboot. That's what I did for the incremental. But even if you're already rooted you shouldn't need vbmeta. Granted, things don't *always* work like they should.
Yeah, this is the behavior I would expect. So you didn't actually do anything with vbmeta, right? You just pulled it in case you needed it?
Click to expand...
Click to collapse
I did this others did this also it did not update it stayed on last version I was using latest alpha going from c36 to c39 global. Just stayed on 36 if I tried it again sent to boot loop. That method did not work
Would been nice if you read what I posted earlier

toolhas4degrees said:
I did this others did this also it did not update it stayed on last version I was using latest alpha going from c36 to c39 global. Just stayed on 36 if I tried it again sent to boot loop. That method did not work
Click to expand...
Click to collapse
Interesting. I never flashed vbmeta or vendor except when I was on open beta. I used the incremental method above for both the update to c38 "stable" and to c39. Folks in another thread lost root and re-rooted with only boot.img. Not sure what went wrong in your case.

terlynn4 said:
Interesting. I never flashed vbmeta or vendor except when I was on open beta. I used the incremental method above for both the update to c38 "stable" and to c39. Folks in another thread lost root and re-rooted with only boot.img. Not sure what went wrong in your case.
Click to expand...
Click to collapse
Maybe an issue from 36 to 39 you know 38 is basically 39 right. So you really didn't change anything

toolhas4degrees said:
Maybe an issue from 36 to 39 you know 38 is basically 39 right. So you really didn't change anything
Click to expand...
Click to collapse
It's still an install to inactive slot and reboot, regardless if there are any/many differences. The same process also worked from 36 to 38. And there are two threads besides this one with other people who rooted using only boot.img and direct install with alpha. Maybe you had issues because of skipping a version? In any case, the simple steps are the easiest path for most people. Great info in your post for anyone who has problems though.