Database Info

[Stock/Rooted Boot Images] Pixel 4a [NOV 02]

We have stock factory boot images, I'm only posting the latest builds.
The rooted android 10 images are rooted with latest Magisk 20.4
The rooted 11 images are rooted with latest Magisk Canary 4e0a3f5e
You will still need to install the Magisk Manager to use root. Root will not work without it.
You HAVE to be bootloader unlocked in order to flash a boot image, meaning these Verizon images are likely useless but google does say it covers extra carriers too. The 11 images seem to be unified in terms of Verizon and other carriers, but do NOT cover
Make sure to match the boot image build number to your own build number. (Settings/about/android version/build number)
-
Android 11 - RP1A - NOV - Stock Factory Boot
Stock Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
AFH
Old Stock Boot Versions
Android 11 - RP1A - Oct - Stock Factory Boot
Stock Boot Image - Global - rp1a.201005.006 - All carriers except EMEA, SG, and IN
AFH
Android 11 - RP1A - Sept - Stock Factory Boot
Stock Boot Image - Global - rp1a.200720.011 - All carriers except EMEA, SG, and IN
AFH
Android 11 Beta R3 - RPB3 - Stock Factory Boot
Stock Boot Image - Global - rpb3.200720.005
AFH
Android 10 - QD4A - Aug - Stock Factory Boot
Stock Boot Image - Global - QD4A.200805.003
AFH
Stock Boot Image - VZW/JP - QD4A.200805.001
AFH
--
Android 11 - RP1A - Nov - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
AFH
Old Rooted Boot Versions
Android 11 - RP1A - Oct - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.201005.006 - All carriers except EMEA, SG, and IN
AFH
Android 11 - RP1A - Sept - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.200720.011 - All carriers except EMEA, SG, and IN
AFH
Android 11 Beta R3 - RPB3 - Rooted Factory Boot - Thanks to @Xenanthropy !
Rooted Boot Image - Global - rpb3.200720.005
AFH
Android 10 - QD4A - Aug - Rooted Factory Boot
Rooted Boot Image - Global - QD4A.200805.003
AFH
Rooted Boot Image - VZW/JP - QD4A.200805.001
AFH
--
For root on Android 11, you need the latest Magisk Canary that can be found here
Steps to proceed:​Unlock Bootloader
Ensure you are on latest android version
Ensure you have the latest versions of adb/fastboot tools
Download the desired boot image and place where adb tools have access
Connect phone to pc and open terminal/cmd prompt to where you put that desired boot image
On the phone:
Go to Settings/About and scroll to the bottom
tap 'Build Number' 7 times
type password/pincode if you have it otherwise don't worry
Go to Settings/System/Developer Options
Enable OEM Unlocking
Enable USB Debugging
Accept USB Debugging prompt on phone - If this doesn't pop-up by itself, unplug phone and plug back in to pc and then it should pop-up, HAVE to allow access..
On pc type:
adb reboot bootloader
fastboot flashing unlock
On phone:
Volume up/down to YES and press power button to proceed with bootloader unlock and wiping data partition
fastboot reboot
--
Flash Boot Image on Bootloader Unlocked Device
Ensure you are on an android version matching the boot image you want to download(Check Settings/About - Click on Android Version - Look at 'Build Number')
Download desired boot image on pc and place it where somewhere you have adb/fastboot access
Connect phone to pc and open terminal/cmd prompt to where you put that desired boot image
Reboot phone to bootloader
on pc type:
fastboot flash boot desired-bootimage-name.img
fastboot reboot
--
To Pass CTS w/root- Courtesy of @quangtran1
After flashing rooted kernel:
In Magisk Manager, install the MagiskHide Props Config module;
Execute command 'su -c props' using a terminal app on the phone;
Choose 'Force BASIC key attestation' option from menu;
Choose from fingerprints list, it should default to Pixel 4a, just Confirm
Reboot
?????
Profit
--
If you want or need to make your own rooted boot image
You need the latest Magisk Manager installed.
Stable Magisk for Android 10, maybe 11 | Canary Magisk for Android 11 for sure.
Download the desired Stock Boot Image from here or extract it yourself from Google's Factory Image zip.
Copy to sdcard of your device.
Open Magisk Manager, click the first 'Install' button next to 'Magisk is up to date'.
Click 'Install'.
Click 'Select and Patch a File'
Find and select the desired Stock Boot Image.
You will find the magisk patched, Rooted Boot Image in the sdcard/Download folder titled 'magisk_patched.img'
Copy that to your pc and flash your pixel 4a from fastboot or copy to the phone and flash with exkm/fkm/etc.
Reboot
Install Magisk Manager
Enjoy being rooted.
XDA:DevDB Information
[Stock/Rooted Boot Images] Pixel 4a [NOV 02], Tool/Utility for the Google Pixel 4a
Contributors
HolyAngel
Source Code: https://developers.google.com/android/images#sunfish
Version Information
Status: Snapshot
Created 2020-08-24
Last Updated 2020-11-02

thank you very much good man. if you can do that also for the beta version it would be great.
https://developer.android.com/preview/download#

@dark8899
Ah I had forgotten about the beta, thanks! And added!

Before I mess up my phone, Do I just run "adb reboot bootloader" then "fastboot flashing unlock" then "fastboot flash boot [Android11RootPatch].img" then "fastboot reboot", set up the phone, install magisk?
I haven't rooted in a while and I'm also just a user not a developer.

@DJesri13
Yep that would pretty much do it exactly.

Hmm, not seeming to work on mine... I tried both flashing my own acquired (and patched with magisk) boot.img as well as your patched boot, and neither seem to want to boot when I reboot, it just boots back into fastboot and says "reason: no valid slots to boot" (or something to that effect, i've already patched the original boot.img back) Tried flashing the patched img to both slot A and B, nothing seemed to work. Got the furthest with my own patched image, the google logo would turn to the G and act like it was loading but it continued to "load" for a good 10 minutes so I just gave up.

Xenanthropy said:
Hmm, not seeming to work on mine... I tried both flashing my own acquired (and patched with magisk) boot.img as well as your patched boot, and neither seem to want to boot when I reboot, it just boots back into fastboot and says "reason: no valid slots to boot" (or something to that effect, i've already patched the original boot.img back) Tried flashing the patched img to both slot A and B, nothing seemed to work. Got the furthest with my own patched image, the google logo would turn to the G and act like it was loading but it continued to "load" for a good 10 minutes so I just gave up.
Click to expand...
Click to collapse
It also isn't working for me. It won't let me flash the boot image. I also tried my own image patched with magisk.
Edit: I all my attempts to flash the boot partition failed so I can still boot the OS

@DJesri13
 @Xenanthropy
Sounds like possibly not flashing correctly or you weren't already on the latest firmware. You need to be on the firmware matching the boot.img. This is pulled directly from the factory image. Try flashing that first and then this image and see what happens.
For flashing this after flashing same firmware on android 10 for instance:
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
make sure you're flashing to 'boot', the 3rd word in the command. if you don't put that it won't flash or if you put something other than 'boot' you could have other issues.. Should still be fixable by flashing the factory images.

HolyAngel said:
@DJesri13
@Xenanthropy
Sounds like possibly not flashing correctly or you weren't already on the latest firmware. You need to be on the firmware matching the boot.img. This is pulled directly from the factory image. Try flashing that first and then this image and see what happens.
For flashing this after flashing same firmware on android 10 for instance:
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
make sure you're flashing to 'boot', the 3rd word in the command. if you don't put that it won't flash or if you put something other than 'boot' you could have other issues.. Should still be fixable by flashing the factory images.
Click to expand...
Click to collapse
I just checked my build version (i'd upgraded to android 11 beta via the ota update by signing up for the beta) and it matches the boot img, RPB3.200720.005.
When I run "fastboot flash boot root.boot.sunfish-rpb3.200720.005.img" it flashes it properly, but upon rebooting it just reboots back into fastboot stating that there was an error. It wouldn't boot on my custom patched boot.img either so i'm not sure what the issue is here.
My current steps were:
1. get phone, immediately unlock bootloader
2. opt-in to android 11 beta, check for updates and upgrade to the beta (rpb3.200720.005)
3. extracted boot.img from the Android 11 beta OTA update, patch it with magisk and attempt to flash (doesn't work, google logo just loads indefinitely)
4. Try flashing your patched boot.img, which results in the phone immediately rebooting and stating an error with the boot slot
If i'm doing something wrong, i'm not sure what it is. I can provide more details if necessary

Xenanthropy said:
I just checked my build version (i'd upgraded to android 11 beta via the ota update by signing up for the beta) and it matches the boot img, RPB3.200720.005.
When I run "fastboot flash boot root.boot.sunfish-rpb3.200720.005.img" it flashes it properly, but upon rebooting it just reboots back into fastboot stating that there was an error. It wouldn't boot on my custom patched boot.img either so i'm not sure what the issue is here.
My current steps were:
1. get phone, immediately unlock bootloader
2. opt-in to android 11 beta, check for updates and upgrade to the beta (rpb3.200720.005)
3. extracted boot.img from the Android 11 beta OTA update, patch it with magisk and attempt to flash (doesn't work, google logo just loads indefinitely)
4. Try flashing your patched boot.img, which results in the phone immediately rebooting and stating an error with the boot slot
If i'm doing something wrong, i'm not sure what it is. I can provide more details if necessary
Click to expand...
Click to collapse
Ah ok gotcha. it sounds like you did everything right too. Might need a magisk update or something else for that then. May remove the beta root image then..

Are you currently running the Android 11 beta? It would be nice to know if someone was able to get the beta rooted properly so we could see what steps they took.

When I try to flash the boot img I get
FAILED (remote: Failed to write to partition Not Found)
Should I try to flash to the boot slot?
EDIT: I flashed and it went through but now it just boots to the bootloader, flashing the stock boot img doesn't fix it. Ill reflash the factory image and again later maybe

DJesri13 said:
When I try to flash the boot img I get
FAILED (remote: Failed to write to partition Not Found)
Should I try to flash to the boot slot?
EDIT: I flashed and it went through but now it just boots to the bootloader, flashing the stock boot img doesn't fix it. Ill reflash the factory image and again later maybe
Click to expand...
Click to collapse
i am also in the same boat here. unlocked and then fastboot flash boot root.boot.sunfish-qd4a.200805.003.img (to slot a)
it booted to Google logo then restarted into bootloader fastboot mode.
it says no valid slot to boot. see attached image

xxTECRAxx said:
i am also in the same boat here. unlocked and then fastboot flash boot root.boot.sunfish-qd4a.200805.003.img (to slot a)
it booted to Google logo then restarted into bootloader fastboot mode.
it says no valid slot to boot. see attached image
Click to expand...
Click to collapse
Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.
Anyone know if it is possible to sideload magisk as a zip?

i relfashed the factory image, then dropped magisk into phone with windows explorer. installed magisk then redid the fastboot flash boot root.boot.sunfish-qd4a.200805.003.img and she just booted up. unsure if i have root though
EDIT: i have root!
---------- Post added at 11:23 PM ---------- Previous post was at 11:03 PM ----------
DJesri13 said:
Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.
Anyone know if it is possible to sideload magisk as a zip?
Click to expand...
Click to collapse
if you're stuck inside fastboot, then reflash the factory image from this file sunfish-qd4a.200805.003-factory-fac7c08d.zip using the included "flash-all.bat". once that completes, boot phone back up and go to settings to enable developer options. then enable USB debugging and finally transfer the magisk.apk into the phone using windows explorer. once all this is done, start over at the top:
adb reboot bootloader
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
fastboot reboot
get paid

xxTECRAxx said:
i relfashed the factory image, then ....
.....
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
fastboot reboot
get paid
Click to expand...
Click to collapse
This is for android 10 or 11 beta?

Zlatty said:
This is for android 10 or 11 beta?
Click to expand...
Click to collapse
10

Can anyone confirm if Rooted 10 + Magisk passes SafetyNet on the 4a?

You need to patch boot-s by latest canary magisk, especially if it`s BETA 11.
https://github.com/topjohnwu/magisk_files/raw/canary/app-debug.apk

Can someone help me out, I don't understand why I can't boot up after flashing the stock or the batched boot image. My bootloader says slot a and that's the one I flashed to. I tried the beta but right now I'm back on Android 10 and neither will let me boot up.

Android 11 Open beta Stuck on Fastboot Mode While Rooting

Hi Everyone
I was rooting My op7 pro after updating to open beta android 11. While i was booting twrp it shows Fastboot Mode screen And stuck on that
Hope i ll find possible solution from the community
Regards
ali_hamza

I went through something similar. I'm reading that TWRP does not support Android 11 yet, so I think we have to do without it for now.
Steps I took:
Disconnect any USB
Hold down vol up, vol down, and power until screen goes black
Do this again until you actually get to normal fastboot mode
Connect to your PC
On your PC if you haven't already, download and install adb/fastboot tools, python, and the payload dumper tool - see Extract Android OTA Payload.bin File using Payload Dumper Tool (thecustomdroid.com)
On your PC, download the ROM zip of the Android 11 beta for OnePlus 7 Pro from the OnePlus forums
Open the Zip and extract the payload.bin file
Follow the instructions above to extract boot.img from payload
Open an admin command prompt and cd to a folder where you have adb/fastboot and this boot.img file
To make sure your phone is properly connected to your PC with correct drivers etc, run fastboot devices
Run fastboot flash boot boot.img
Run fastboot reboot
This got me back into an unrooted Android 11 system. My recovery is messed. I think there's a way to directly patch the boot.img file with Magisk and flash that. Will need to work on getting TWRP back if/when someone figures that out (or when it is supported)
Once you're unrooted and running on the Android 11 beta:
connect to your PC
tell Android to go into file transfer mode
take boot.img file from above instructions and copy it to the root of your phone storage
open the Magisk Manager app, click to install Magisk, and then choose Patch boot image
resulting patched boot image file will be saved to your phone's Downloads folder
back on the PC, pull this patched boot img file back onto your PC and into your fastboot folder
reboot phone into fastboot mode (using volup+voldn+power)
Run fastboot flash boot magisk_patched_?????.img (your file will have a unique name)
Run fastboot reboot
Now you're rooted.

benjaminries said:
I went through something similar. I'm reading that TWRP does not support Android 11 yet, so I think we have to do without it for now.
Steps I took:
Disconnect any USB
Hold down vol up, vol down, and power until screen goes black
Do this again until you actually get to normal fastboot mode
Connect to your PC
On your PC if you haven't already, download and install adb/fastboot tools, python, and the payload dumper tool - see Extract Android OTA Payload.bin File using Payload Dumper Tool (thecustomdroid.com)
On your PC, download the ROM zip of the Android 11 beta for OnePlus 7 Pro from the OnePlus forums
Open the Zip and extract the payload.bin file
Follow the instructions above to extract boot.img from payload
Open an admin command prompt and cd to a folder where you have adb/fastboot and this boot.img file
To make sure your phone is properly connected to your PC with correct drivers etc, run fastboot devices
Run fastboot flash boot boot.img
Run fastboot reboot
This got me back into an unrooted Android 11 system. My recovery is messed. I think there's a way to directly patch the boot.img file with Magisk and flash that. Will need to work on getting TWRP back if/when someone figures that out (or when it is supported)
Once you're unrooted and running on the Android 11 beta:
connect to your PC
tell Android to go into file transfer mode
take boot.img file from above instructions and copy it to the root of your phone storage
open the Magisk Manager app, click to install Magisk, and then choose Patch boot image
resulting patched boot image file will be saved to your phone's Downloads folder
back on the PC, pull this patched boot img file back onto your PC and into your fastboot folder
reboot phone into fastboot mode (using volup+voldn+power)
Run fastboot flash boot magisk_patched_?????.img (your file will have a unique name)
Run fastboot reboot
Now you're rooted.
Click to expand...
Click to collapse
You should just be able to run direct install after you boot to A11 with the patched boot image.

Some of us will have followed a standard Oxygen OS beta update flash cycle of:
Download the beta update
Reboot to recovery (TWRP)
Flash update, wipe dalvik
Flash TWRP installer to patch new boot image
Reboot to recovery (from recovery, to get A/B slot switched)
Flash Magisk to patch boot image for root
Reboot to system
I bricked at step 5 because TWRP installer didn't play nice with the new Android 11 boot image. Even when I flashed the latest unofficial TWRP from fastboot, the best I could get was a TWRP that couldn't decrypt filesystem... and after that, a bootloop that just flashed the TWRP load screen briefly every second, between black screens.
I'm super appreciative of OnePlus for having such a reliable way to get back to fastboot no matter what. I take it that when I extracted the OP stock boot image from beta and flashed it in fastboot, I also overwrote TWRP with stock recovery? It no longer seems like recovery is a separate partition to be flashed - nothing from the payload file seemed to be it.

calripkenturner said:
You should just be able to run direct install after you boot to A11 with the patched boot image.
Click to expand...
Click to collapse
Wait... you don't mean "direct install" of TWRP, do you? Is there a version that supports Android 11 filesystem decryption? Wouldn't that also get rid of root? What is it that you think should be directly installed after successful boot of Android 11 with Magisk patched boot image?

benjaminries said:
Wait... you don't mean "direct install" of TWRP, do you? Is there a version that supports Android 11 filesystem decryption? Wouldn't that also get rid of root? What is it that you think should be directly installed after successful boot of Android 11 with Magisk patched boot image?
Click to expand...
Click to collapse
No, direct install of magisk. Check the twrp thread in the rom and development section. There is already a patched boot image and instructions on rooting. Twrp isnt working yet as far as I know.

calripkenturner said:
No, direct install of magisk. Check the twrp thread in the rom and development section. There is already a patched boot image and instructions on rooting. Twrp isnt working yet as far as I know.
Click to expand...
Click to collapse
Got it. Yeah my Magisk Manager was still installed from previous beta, but it took away the "direct install" option when I lost root from flashing the unpatched boot.img. Personally I would always rather patch my own boot.img file than rely on something from a filesharing service, especially when trying to get out of brick...
But I can see how until proper TWRP support comes, we can just use Magisk to patch alternate boot slot before rebooting but immediately after flashing the latest OOS beta using the regular system update process. Hindsight...

benjaminries said:
Some of us will have followed a standard Oxygen OS beta update flash cycle of:
Download the beta update
Reboot to recovery (TWRP)
Flash update, wipe dalvik
Flash TWRP installer to patch new boot image
Reboot to recovery (from recovery, to get A/B slot switched)
Flash Magisk to patch boot image for root
Reboot to system
I bricked at step 5 because TWRP installer didn't play nice with the new Android 11 boot image. Even when I flashed the latest unofficial TWRP from fastboot, the best I could get was a TWRP that couldn't decrypt filesystem... and after that, a bootloop that just flashed the TWRP load screen briefly every second, between black screens.
I'm super appreciative of OnePlus for having such a reliable way to get back to fastboot no matter what. I take it that when I extracted the OP stock boot image from beta and flashed it in fastboot, I also overwrote TWRP with stock recovery? It no longer seems like recovery is a separate partition to be flashed - nothing from the payload file seemed to be it.
Click to expand...
Click to collapse
need to use orangfox recovery

esi2121 said:
need to use orangfox recovery
Click to expand...
Click to collapse
Hard to find documentation suggesting OrangeFox works with Android 11 filesystem encryption or OOS 11 beta specifically. Does it?

benjaminries said:
Hard to find documentation suggesting OrangeFox works with Android 11 filesystem encryption or OOS 11 beta specifically. Does it?
Click to expand...
Click to collapse
Check the orangefox ,it's only recovery support a11 for now

esi2121 said:
Check the orangefox ,it's only recovery support a11 for now
Click to expand...
Click to collapse
Yeah I did, and I could not find any evidence that it supports the new Android 11 filesystem encryption.
Changelog suggests much of the core functionality is ported from TWRP - that OrangeFox is more or less a fork with extra functions and a better interface.
The reason users of both TWRP and OrangeFox have been able to use custom Android 11 ROMs is that those roms are kind of a Frankenstein - they're based on Android 10 AOSP with Project Treble packages from Android 11. OOS 11 beta seems to have different partition architecture?
I think we need to wait until somebody reports their actual experience with OOS 11 beta on a custom recovery.

Yesterday i download and tried to flash Pitch Black Recovery Project but results were same.
I think there should be some changes regarding A11 in any recovery so the best is that we should wait for their( Devs) further response

benjaminries said:
Yeah I did, and I could not find any evidence that it supports the new Android 11 filesystem encryption.
Changelog suggests much of the core functionality is ported from TWRP - that OrangeFox is more or less a fork with extra functions and a better interface.
The reason users of both TWRP and OrangeFox have been able to use custom Android 11 ROMs is that those roms are kind of a Frankenstein - they're based on Android 10 AOSP with Project Treble packages from Android 11. OOS 11 beta seems to have different partition architecture?
I think we need to wait until somebody reports their actual experience with OOS 11 beta on a custom recovery.
Click to expand...
Click to collapse
yup thats it , but in orangefox git said official support A11

esi2121 said:
yup thats it , but in orangefox git said official support A11
Click to expand...
Click to collapse
Check out this (now locked) thread though: it seems like there's no working port of OrangeFox for guacamole that supports OOS11 yet... lots of people bricking and boot-looping on the hope that there might have been!
[UNOFFICIAL] [RECOVERY] [OnePlus 7 Pro] OrangeFox Recovery Project [R10.1] | XDA Developers Forums (xda-developers.com)

Common method to apply OTA and regain root

There's a method on Magisk to let you to revert boot and apply OTA, and install root again.
This method applied to most Moto phones.
1. Check for update. Settings >>> System >>> update.
2. If you found a new version available, go to Magisk and "uninstall" and revert to original boot.
3. Install OTA system update. DO NOT REBOOT!
4. Go back to Magisk and install on "unused partition". Reboot when finished
If there's an error "unable to revert", you need to get ROM matched the build number, and get the boot.img, copy the boot to the phone and let Magisk "install and patch". This method will give an original boot to revert, and run step 2 again.
If the method above didn't work, you need to do the following.
1. Assume you have original boot and updated boot. Reboot in fastbootd (only for models shipped with Android Q, R, S) or bootloader (shipped with Android P or earlier)
Code:
fastboot reboot fastboot
or
Code:
adb reboot fastboot
2. From there, you can flash original boot
Code:
fastboot flash boot
Press spacebar once and drag and drop the patched boot into command window, and press enter.
Reboot when finished
3. Install OTA, and hopefully you have updated boot with matched build number. When OTA installation finished, copy updated boot to the phone and patch it with Magisk, and copy back to host computer, and reboot.
4. Once the phone finished post update, reboot to fastbootd
Code:
adb reboot fastboot
, and flash patched boot.
Done

Wish it would have worked. After reverting to stock boot it still wouldn't install. Had to LMSA the phone and then patch and fastboot the patched image. *sigh*
Regardless, this may work for others, but my phone was jacked up after reverting to stock boot.

noobtoob said:
Wish it would have worked. After reverting to stock boot it still wouldn't install. Had to LMSA the phone and then patch and fastboot the patched image. *sigh*
Regardless, this may work for others, but my phone was jacked up after reverting to stock boot.
Click to expand...
Click to collapse
I've never had success trying to revert Magisk, update with OTA, then restoring Magisk.
I've tried before on my Z3 Play and Moto G Stylus.
I just don't do updates anymore and don't have to mess with it. Seems like these days updates just block things I want to do anyway, like Screen2Auto working and hotspot bypassing.

gullzway said:
I've never had success trying to revert Magisk, update with OTA, then restoring Magisk.
I've tried before on my Z3 Play and Moto G Stylus.
I just don't do updates anymore and don't have to mess with it. Seems like these days updates just block things I want to do anyway, like Screen2Auto working and hotspot bypassing
Click to expand...
Click to collapse
Well, fastest method for me was:
1. Boot to twrp>backup data. Copy backup off phone.
2. Update phone from LMSA.
3. Follow previous root guide to patch the boot.img (extract from LMSA folder on computer).
4. Fastboot flash the patched boot image.
5. Boot to twrp>copy backup to twrp folder on device>restore data.
You don't have to setup your phone for any of this.
Edit: Obviously you have to setup your phone to install magisk and patch the boot.img. I mean minimal, like skipping all the account .

[Help!] Can't root my OnePlus 7 Pro

Hi,
with the latest Magisk update I noticed the missing Magisk Hide and SafetyNet fix. So I decided to go back to Magisk 23. After a few unsuccessful attempts, I don't know what happened but now my phone is no longer rooted. So I tried some usual methods to re-root the device but nothing to do, still no root
I have used boot.img patching way with Magisk but when I send ADB command "fastboot flash boot magisk_patched.img", it seems to work fine but after reboot there is no root
So I tried the other method by booting the device with patched boot.img using ADB ("fastboot boot magisk_patched.img") then I open Magisk Manager but in the installation section there is no "direct install" option as it should be.
I also tried flashing Magisk.zip via TWRP as I did long ago and TWRP seems to do the job well but after rebooting again no root...
Any suggestions?

even though you don't have root, i suggest flashing the stock boot.img and then rebooting to be really sure that root has been removed. and then flash the magisk patched boot.img.
are you using the latest adb and fastboot? you can get the latest from here. https://developer.android.com/studio/releases/platform-tools
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.

altwu said:
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.
Click to expand...
Click to collapse
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.

¿GotJazz? said:
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.
Click to expand...
Click to collapse
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?

altwu said:
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?
Click to expand...
Click to collapse
Yes, I used the stock boot.img that I extracted from the 11.0.5.1 file that was downloaded as the normal OTA update from OnePlus. I patched that boot image with Magisk v24.1 that was already installed on my OP7P.
Then, I flashed that Magisk patched boot.img using fastboot onto both A and B slots (I switched slots by booting into TWRP 3.6, since I didn't see a way to switch slots with the now-loaded OnePlus Recovery Mode).
When I rebooted through the patched image, the phone came up (which is good!), but Magisk says that I don't have root (which is bad!). I haven't figured out how to fix that.
Could you PM me your patched boot.img? I could try flashing that to see if my OP7P acts any differently.
Thanks!

OK, I'm 100% positive that Magisk v24.1 patched my OP7P OOS 11.0.5.1 boot.img properly.
I extracted the 11.0.5.1 boot.img file from the OTA image that was in my .Ota folder from my phone. I extracted boot.img from the payload.bin file using two different methods of payload-dumper. Both boot.img files had the same SHA-512 checksums, so they were identical.
I also downloaded a copy of the Magisk v24.1 patched boot.img from the intenet and compared it to my Magisk v24.1 patched boot.img file. Again, the SHA-512 checksums matched for the two patched files, so I am sure that I have a properly patched boot.img file.
Note that my OP7P has loaded the full OOS 11.0.5.1 Stock image, so I currently have the OOS Recovery Mode and I do not have TWRP Recovery Mode.
Maybe I am doing something else wrong during my installation that is keeping me from getting root?
Here is the process I followed with my patched boot.img file:
I boot into Fastboot Mode
In Fastboot Mode, I go into TWRP Recovery Mode by typing: fastboot boot twrp-3.6.0_11-0-guacamole.img
After rebooting into TWRP Recovery, I installed the 11.0.5.1 OTA by doing an Install > Browse to the .Ota folder for the OTA .Zip file.
After the OOS 11.5.0.1 OTA installed, I rebooted back to Fastboot Mode (before booting normally) by selecting: Reboot > Slot A > Home > Reboot > Bootloader
Once I am back into Fastboot Mode, I type: fastboot flash boot magisk_patched_boot.img
In Fastboot Mode, I type: fastboot reboot
After I have rebooted back to normal mode, Magisk v24.1 is already installed and I don't do any updates to that. When opening Magisk, my screen flashes a couple of times before giving me a Toast pop-up that Magisk was denied Super User access. When I look at the Magisk App screen, it says that the App is installed, but that Magisk is not installed.
Are there any steps that I am missing?

Well, I finally got OOS 11.0.5.1 rooted with Magisk v24.1.
I ended up wiping my data and installing a fresh install of OOS 11.0.5.1 (Not sure if this is necessary, but I skrood up along the way and had to wipe as a result).
The one thing that was different this time around was that I disabled encryption/lock before flashing the Magisk-v24.1 patched boot image. I suspect that was what helped me make it to the finish line this time.
Good luck out there!
¿GJ?

i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!

altwu said:
i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!
Click to expand...
Click to collapse
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?

¿GotJazz? said:
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?
Click to expand...
Click to collapse
you can use fastboot to switch slots.
fastboot --set-active=a or b
i don't know if it's necessary, but i reboot the bootloader with "fastboot reboot bootloader" after switching slots.
i've never tried this, but you can also specify what slot when running fastboot flash, like "fastboot flash boot magisk_patched.img --slot a".
check out "fastboot help" to see the different options.
i haven't had to play around with slots though. when an update is available, i'll download the zip to a computer and then go through the normal update process via the os. after the update is done, the phone reboots and the correct active slot is set.

Thanks for the feedback, @altwu.
I am having issues getting my SMS notification sound working on my fresh(er) 11.0.5.1 installation. I haven't seen anybody respond back yet, and I am beginning to suspect it's just a problem on my OP7P. If I don't see anybody responding back by tomorrow, I'll assume it's "just me".
I am thinking about doing a total wipe again to see if it will clear up the issue I am seeing. I will end up trying your installation route this time to see if it helps at all.

Question OnePlus 9 / boot.img C61

Hi guys,
I've crashed my OP9 due flash an older boot.img.
Today I updated to C61, flashed a patched C46 boot image for root.
Now the phone holds on at the OnePlus Start logo.
Has anyone an untouched boot.img from C61 Firmware?
I've installed the global Firmware, but I believe, it doesn't matter.
Thanks and regards!

[email protected] said:
Hi guys,
I've crashed my OP9 due flash an older boot.img.
Today I updated to C61, flashed a patched C46 boot image for root.
Now the phone holds on at the OnePlus Start logo.
Has anyone an untouched boot.img from C61 Firmware?
I've installed the global Firmware, but I believe, it doesn't matter.
Thanks and regards!
Click to expand...
Click to collapse
Search online I find it there 2

I'm searching for boot.img of EU version. Could you please share where you found yours?

Method confirmed to work for OnePlus 9 EU (LE2113) and OnePlus 9 Global (LE2115) - Enjoy!
Update rooted C.47 to C.61:
Open magisk, click 'Uninstall magisk'
Reboot
Updated via standard system update to C.61 . (At first it failed at 99% for me, but on second try it completed successfully). Alternatively: try the Oxygen updater to download the C.61 OTA incremental update.
Reboot
Easy way to root C.61:
Download the patched boot.img:
EU (LE2113 - Europe) from Mega
or Global (LE2115) from GDrive or Mega
Place the downloaded boot file in the same folder as your adb.
Open a terminal or command prompt in that folder and execute: "adb reboot bootloader"
Execute "fastboot boot .\C.61_boot_magisk_patched-25100_Bvj5U.img" to temporarily boot the patched boot file.
Download & install Magisk 25.1.
Open Magisk. If it indicates 'Installed Magisk: n/a', you're device was not correctly rooted. If it says 25.1, you can patch your boot to make the root stay:
Select 'Direct Install' and reboot.
Congrats!
DIY way:
All files here on a Mega folder if it helps you guys save time
Download C.61 OTA incremental update from the cellphone (both in-built system update and Oneplus Updater give the same download).
Use Payload dumper to extract the stock boot.img and copy it to your phone.
Download and install Magisk 25.1 on your phone, use 'Select and Patch a File' to patch the stock boot.img which creates magisk_patched-25100_4vi6c.img
Copy this file to your desktop and run the following commands to boot the patch:
boot in fastboot: "adb reboot bootloader" in terminal
temporarily boot the patched boot file: "fastboot boot .\magisk_patched-25100_4vi6c.img"
After reboot, open Magisk. If it indicates 'Installed Magisk: n/a', you're device was not correctly rooted. If it says 25.1, you can patch your boot to make the root stay:
Select 'Direct Install' and reboot.
Congrats!
(Optional) Way to extract your current boot file from a rooted phone:
Ensure you're rooted
Execute "adb reboot bootloader" on your pc
To check the current active boot partition execute "fastboot getvar all" on your pc and look for "(bootloader) current-slot:a" meaning you'll be using boot_a.img later on or "(bootloader) current-slot:b" for boot_b.img
Execute the following commands on your pc:
adb shell
su
dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/Download/boot_a.img
dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/Download/boot_b.img
exit
adb pull /sdcard/Download/boot_a.img boot_a.img
adb pull /sdcard/Download/boot_b.img boot_b.img
Whichever boot partition was active in step 3 is the one you want

xHalt said:
Same here. I can find boot.img for the OnePlus 9 Pro (EU) but not for the OnePlus 9 (EU).
I tried the payload dumper on the incremental update (instructions do tell you it doesn't work on incremental .zip, only on full .zip). I got the boot.img out of it and was able to patch with Magisk 25.1, but when booting it's not rooted yet.
All files here on a Mega folder if it helps you guys save time :
My phone: OnePlus 9 EU - LE2113
Issue I had: Couldn't update to C.61
I was on C.47, rooted with Magisk 25.1. Tried to update through the system pop-up as well as through the Oxygen Update to update to C.61. It kept failing at 21%.
Steps I took to update:
Uninstalled magisk
Updated via standard system update failed at 99%.
I retried with the Oxygen updater and now it succeeded to 100%
Rebooted
Issue: now I'm no longer rooted.
Steps I took to root again:
Downloaded C.61 OTA incremental update from the cellphone (both in-built system update and Oneplus Updater gave the same download).
Used Payload dumper to extract the stock boot.img and copied it to my phone.
Installed Magisk 25.1 on my phone, used 'Select and Patch a File' to patch the stock boot.img which created magisk_patched-25100_4vi6c.img
Copied this file to my desktop and ran the following commands to try and boot the patch:
boot in fastboot: "adb reboot bootloader" in terminal
termporarily boot the patched boot file: "fastboot boot .\magisk_patched-25100_4vi6c.img"
It takes a LONG time to boot, but eventually it does boot correctly.
Issue: however, Magisk is NOT installed and I'm not rooted yet.
I also tried to install TWRP recovery but keep getting the Qualcomm Crashdump Mode.
boot in fastboot: "adb reboot bootloader" in terminal
temporarily boot the TWRP recovery: "fastboot boot .\twrp-3.6.2_11-0-lemonadep.img" in terminal
Issue: Qualcomm Crashdump Mode pops up and is stuck there
Anyone able to figure the last step out?
Appreciated!
Click to expand...
Click to collapse
i am in a similar situation. my OP 9 (EU) is (still) on the c47 build with the latest magisk. I never updated to c48 but have now decided to give c61 a try. But iam not able to install the OTA, inbuild system is crashing @ 35%, even with the local install method and the loaded update from the oxygen updater, its still crashing. Today i uninstall magisk, flash the c47 stock boot.img and vendor_boot.img but it still crashing. After some research I tried to reset the phone. Device is now fully wiped, only the bootloader is unlocked. But i still got this crashes What did you do to install the update ? my next try is to use the MSN tool from this forum, but i'm afraid to brick my device.

I have extracted the original boot.img and vendor_boot.img from LE2115_11_C.61 using MsmDownloadTool (F8 > select the desired partitions > ReadBack) and uploaded to GoogleDrive.

My OP 9 EU version is on build C.48 (rooted with Magisk) and I also have the issue where the update crashes at 21%.
Did anyone already find a solution on how to upgrade to C.61 without data loss?

MrMagic said:
My OP 9 EU version is on build C.48 (rooted with Magisk) and I also have the issue where the update crashes at 21%.
Did anyone already find a solution on how to upgrade to C.61 without data loss?
Click to expand...
Click to collapse
I spent a few hours trying to solve the problem. no chance. I ended up using the msm tool. after that it was possible to update from C37 to C48 and finally to C61.

I just found this in the OP9 Root topic:
Root OnePlus 9
This is for Europe (11.2.2.2.LE25DA). If you are on Global, EU version works, but up to you. It appears for last year, unless you are from India, OnePlus doesn't care. It might be a while before a Full OTA update for Global is released, you'll...
forum.xda-developers.com
Apparently you can use the boot.img from the C.61 OP9 Pro build on the regular OP9.

I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?

aldoc01 said:
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
Click to expand...
Click to collapse
Try the updated instructions above. Can confirm it works now.

@xHalt Did you do anything else besides uninstalling Magisk to get the C.61 OTA update to install?
I am on C.48 and uninstalled Magisk, but I still cannot install the C.61 OTA. Tried both the standard system updater and Oxygen Updater.
Not sure why it's failing because it doesn't give any meaningful error message.
Is there a stock boot image I can flash to get past this error?

Daeril said:
I have extracted the original boot.img and vendor_boot.img from LE2115_11_C.61 using MsmDownloadTool (F8 > select the desired partitions > ReadBack) and uploaded to GoogleDrive.
Click to expand...
Click to collapse
Amazing, @Daeril ! Thank you. It works.
Updated the instructions for everyone.

MrMagic said:
@xHalt Did you do anything else besides uninstalling Magisk to get the C.61 OTA update to install?
I am on C.48 and uninstalled Magisk, but I still cannot install the C.61 OTA. Tried both the standard system updater and Oxygen Updater.
Not sure why it's failing because it doesn't give any meaningful error message.
Is there a stock boot image I can flash to get past this error?
Click to expand...
Click to collapse
I updated from C.47 and only had to reboot.
Try with the stock boot indeed: I included the stock boot for C.47 in the Mega folder or direct link here.
Alternatively: revert to C.47 first? Files also in the Mega folder.

aldoc01 said:
I was finally able to go from c47 rooted to c61.
Now I have no root.
Any way to get it?
Click to expand...
Click to collapse
Please see the updated instructions above and let me know if it works for you.

xHalt said:
Try with the stock boot indeed: I included the stock boot for C.47 in the Mega folder or direct link here.
Alternatively: revert to C.47 first? Files also in the Mega folder.
Click to expand...
Click to collapse
I tried with the stock boot already. Flashed it with fastboot, but didn't make any difference.
Do you know how I would go about reverting to C.47 without data loss? I have the ZIP file on my phone, but the updater says I cannot install it because the version is older than what I'm already running.

MrMagic said:
I tried with the stock boot already. Flashed it with fastboot, but didn't make any difference.
Do you know how I would go about reverting to C.47 without data loss? I have the ZIP file on my phone, but the updater says I cannot install it because the version is older than what I'm already running.
Click to expand...
Click to collapse
Only way is sadly with data loss/reset afaik.

xHalt said:
Please see the updated instructions above and let me know if it works for you.
Click to expand...
Click to collapse
working!!
thanks mate