Database Info

Root mate 9 oreo with magisk

Hello guys I just want an explanation on how to root mate 9 c185 (370) oreo from scratch explain it to a noob cause I just soft broke my phone trying to do it thank you
From 0 step please

Please anyone

Iloudsan said:
Please anyone
Click to expand...
Click to collapse
1. Unlock bootloader
2. Download magisk manager and install it
3. Extract ramdisk.img from fw
4. Run magisk manager and choose the ramdisk.img u copied on ur phone internal memory and create the patched_boot.img
5. Flash the patched_boot.img through fasboot flash ramdisk patched_boot.img
Done

Addymore said:
1. Unlock bootloader
2. Download magisk manager and install it
3. Extract ramdisk.img from fw
4. Run magisk manager and choose the ramdisk.img u copied on ur phone internal memory and create the patched_boot.img
5. Flash the patched_boot.img through fasboot flash ramdisk patched_boot.img
Done
Click to expand...
Click to collapse
Sorry if I sound noob but from where to extract the ram disk exactly do I extract it from the main update.zip?

Iloudsan said:
Sorry if I sound noob but from where to extract the ram disk exactly do I extract it from the main update.zip?
Click to expand...
Click to collapse
Yep.... Using Update Extractor Tool.... Remember to uncheck "Verify header checksum" in settings for oreo fw.... Otherwise it fails to extract

Addymore said:
Yep.... Using Update Extractor Tool.... Remember to uncheck "Verify header checksum" in settings for oreo fw.... Otherwise it fails to extract
Click to expand...
Click to collapse
and is there any way to Disable Encryption ? in oreo i only know how to do it in android 7

Addymore said:
Yep.... Using Update Extractor Tool.... Remember to uncheck "Verify header checksum" in settings for oreo fw.... Otherwise it fails to extract
Click to expand...
Click to collapse
rooted successfully but would love to have it encrypted cause i dont have SD card as i use 2 sim cards so i cant flash anything in twrp

Iloudsan said:
rooted successfully but would love to have it encrypted cause i dont have SD card as i use 2 sim cards so i cant flash anything in twrp
Click to expand...
Click to collapse
Actually twrp cannot decrypt the internal storage...! U have to use external sd.... No other choice for now....

Hello,
Based on instructions below I managed to install Magisk via patched_boot.img onto Mate9 Oreo 8.0.0.363(C432). I downloaded few modules like Xposed etc, after restarting I got a bootloop. When I back install ramdisk.img phoneboots but magisk is not installed. Any help is appreciated.

no need to extract ramdisk no more....the new one will install with twrp from sd card....starting 15v and also has to have bootloader unlock and be on stock oreo....

cross1989 said:
no need to extract ramdisk no more....the new one will install with twrp from sd card....starting 15v and also has to have bootloader unlock and be on stock oreo....
Click to expand...
Click to collapse
It cannot be installed any other way. Says no boot image.

Are you on stock android... I did root my mate 9...you need the special twrp for mate 9..its in the forum for magisk... Then just boot into twrp, do normal wipe, then install magisk, start with 15.4 version... Then it should update to 16..

Hi,
I've found an simpler method to root my Oreo Mate 9, which does not involve extracting the ramdisk.img of your rom.
This method comes for @ante0 in this post.
In my case (Mate9 with stock rom L29C432B366), this is what I did:
1) Start from an unrooted stock Oreo rom
2) Unlock bootloader
Note: Unlocking the bootloader will completely erase your phone, so backup before hand!
3) Download and flash (via fastboot) TWRP recovery TWRP-3.2.1-Oreo_FBE_Mate9.img
This recovery can be downloaded from the link in here
Note: to flash the recovery in Fastboot mode you have to type from the command line on the PC :
fastboot flash recovery_ramdisk TWRP-3.2.1-Oreo_FBE_Mate9.img
4) Reboot in recovery and mount the System and Vendor partitions
Note: if you skip this step, your phone will NOT reboot after step (5) :crying: (I know, I have tested this )
5) In recovery, flash the latest Magisk. I Have used the latest beta, Magisk 16.4 which can be downloaded from here.
6) Reboot system, and you're good to go, rooted and passing safetynet
What I like about this method is (1) no need to extract a ramdisk.img specific to the rom you are rooting , and (2) I'm still decrypted in recovery
Note: Not tested with other rom versions than L29C432B366

how magisk works in mate9 C432 B369 ??
i try 16.0 cust and my mate9 soft brick

I need help guys.
I tried installing xposed from magisk app. After reboot, am stuck on bootloop after several retries. Was forced to flash new firmware using HWOTA8.Now,i have tried getting magisk to work but result to boot loop after boot is patched and flashed via fastbokt.Have also tried flashing through twrp by mounting system, vendor but still stuck on Huawei logo and reboot . Have tried flashing supersu but that does get root to work.
Please help because most of the app I use need root access and don't want to perform fresh installation.
Thanks.

Jodin3 on Samsung Phones, .PIT and Magisk (Under Linux Virtual Machine)

I downloaded Odin3 and Heindall, Samsung A01 core stock rom, and pacthed the AP file with magisk (https://topjohnwu.github.io/Magisk/install.html). My phone is Samsung A01 core, have OEM disabled, and have Ramdisk. I am using usb 3 and a official samsung usb cable.
i had Patched the Boot.img from AP file, and Patched the whole AP file on Magisk . so i tried to flash Boot.img with "fastboot" and tried to flash AP file on download mode with odin. Fastbot is not working to flash the "Boot.img", because the command `fastbot boot Boot.img` is not recognized (FAILED (remote: unknown command)), i had try `fastbot flash:raw boot boot.img` with no sucess too, giving me the same error.
so i am tried Jodin3, and keep trying to flash the whole magiskAP file. following the tutorial above, and Jodin3 always tell .PIT is corrupted (even generated by heimdall or using the .pit inside CSC file). but is not to work, Jodin3 keep give me errors, it say .pit is corrupted.
Some versions of ODIN for windows, don't ask for .PIT... so what i can do? Can i regenerate a PIT from a "patched AP" ?

Hey! As I see that no one has responded to you in two years, I will give you some tips.
First of all, I need to warn you that the Samsung system does not have fastboot, unlike other devices, so there is no way to use commands like that on any Galaxy device.
And secondly, I noticed that you are a Linux user. From my own experience, I recommend you try using Odin on Windows, as I've tried several times to use Jodin, and I've only had problems.
As for the .PIT, I don't know how to help you, since I don't remember anything about the procedure.
I hope I was helpfull. If you're still trying, try my tips and let me know if it worked!

adonisSMS said:
I downloaded Odin3 and Heindall, Samsung A01 core stock rom, and pacthed the AP file with magisk (https://topjohnwu.github.io/Magisk/install.html). My phone is Samsung A01 core, have OEM disabled, and have Ramdisk. I am using usb 3 and a official samsung usb cable.
i had Patched the Boot.img from AP file, and Patched the whole AP file on Magisk . so i tried to flash Boot.img with "fastboot" and tried to flash AP file on download mode with odin. Fastbot is not working to flash the "Boot.img", because the command `fastbot boot Boot.img` is not recognized (FAILED (remote: unknown command)), i had try `fastbot flash:raw boot boot.img` with no sucess too, giving me the same error.
so i am tried Jodin3, and keep trying to flash the whole magiskAP file. following the tutorial above, and Jodin3 always tell .PIT is corrupted (even generated by heimdall or using the .pit inside CSC file). but is not to work, Jodin3 keep give me errors, it say .pit is corrupted.
Some versions of ODIN for windows, don't ask for .PIT... so what i can do? Can i regenerate a PIT from a "patched AP" ?
Click to expand...
Click to collapse
This is working for me on Ubuntu.
OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux​
OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux
Try out my new Linux flash tool called Thor - https://forum.xda-developers.com/t/dev-thor-flash-utility-the-new-samsung-flash-tool.4597355, which has all the features of this tool + extras, like the usual Windows Odin ones which are missing in...
forum.xda-developers.com

[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.

Note 20 Ultra 5G (Exynos) Rooting Problem

Hello everyone.
I've been trying to root my Note 20 Ultra 5G (N986B/DS) running on android 12 using different instruction on YouTube and other websites, but so far I haven't had any lock and it's driving me crazy.
Here's what I have done so far:
1) I activated developer mode/unlocked OEM/activated debugging mode
2) Via Recovery Mode unlocked the bootloader so after doing a factory reset, when device turns on, there is a warning sign telling me that the bootloader is unlocked.
3) Downloaded the exact android 12 stock rom running on my device. (February security patch - XSG-N986BXXU3EVA9-N986BOXM3EVA9)
4) Extracted the rom in my computer (there are two different steps from two different sources):
4-1-1) Transferred the AP_N986BXXU3EVA9_N986BXXU3EVA9_MCL23524635_MQB48657513_REV01_user_low_ship_MULTI_CERT_meta_OS12.tar.md5 file to the device.
4-1-2) Using latest canary build of the Magisk installed on the device, I patched the ap file and then transferred it back to computer. (I also tried with the recent stable version of Magisk and the same occurred)
4-1-3) Put the device in recovery mode and then loaded BL/CP/CSC slots of the Odin3 v3.14 with the rom files and the AP slot with the patched file and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) since the operation didn't finish, I had to flash original stock files via Odin in order to boot to my device.
4-2-1) Extracted the AP file and changed the format of the file boot.img.lz4 to .tar file using 7zip and then transferred the file to my device.
4-2-2) Using latest canary build of the Magisk installed on the device, I patched the boot.img.tar file and then transferred it back to computer.
4-2-3) Put the device in recovery mode and then loaded the patched version of boot.img.tar file into AP slot of the Odin3 v3.14 and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) failing the flash process doesn't break the device and I was able to boot to my device.
Please if anyone has a clue, tell me the solution. I'm so desperate now. I've tried different workarounds in internet and non worked. I even tried installing unofficial version of TWRP and still the same message appears.
UPDATE:
I found a solution to install twrp using adb and fastboot commands. I got the device to be recognized by computer. but unfortunately "fastboot flash recovery boot.tar" command doesn't work and it sticks in sending the image state. So this method isn't working either.
UPDATE 2:
I found this post on xda dating back to 2018. According to this post I should wait 7 days (like "the ring" movie!) so that the message i referred to is gone and I can flash whatever I want.
I have had a galaxy s7 edge for some time now and I have experienced a lot of flashings with that device and never came across sth like this. Now I have to wait and see unless someone or me come up with a better solution.
P.S. I have some trust issues and I can't give team viewer or anydesk access to those who are able to help. So please don't ask for any. I kindly ask you guys to help me in anyway possible under this thread. If more information is required I will make sure to provide you with that.
Thanks in advance.

codenamefred said:
Hello everyone.
I've been trying to root my Note 20 Ultra 5G (N986B/DS) running on android 12 using different instruction on YouTube and other websites, but so far I haven't had any lock and it's driving me crazy.
Here's what I have done so far:
1) I activated developer mode/unlocked OEM/activated debugging mode
2) Via Recovery Mode unlocked the bootloader so after doing a factory reset, when device turns on, there is a warning sign telling me that the bootloader is unlocked.
3) Downloaded the exact android 12 stock rom running on my device. (February security patch - XSG-N986BXXU3EVA9-N986BOXM3EVA9)
4) Extracted the rom in my computer (there are two different steps from two different sources):
4-1-1) Transferred the AP_N986BXXU3EVA9_N986BXXU3EVA9_MCL23524635_MQB48657513_REV01_user_low_ship_MULTI_CERT_meta_OS12.tar.md5 file to the device.
4-1-2) Using latest canary build of the Magisk installed on the device, I patched the ap file and then transferred it back to computer. (I also tried with the recent stable version of Magisk and the same occurred)
4-1-3) Put the device in recovery mode and then loaded BL/CP/CSC slots of the Odin3 v3.14 with the rom files and the AP slot with the patched file and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) since the operation didn't finish, I had to flash original stock files via Odin in order to boot to my device.
4-2-1) Extracted the AP file and changed the format of the file boot.img.lz4 to .tar file using 7zip and then transferred the file to my device.
4-2-2) Using latest canary build of the Magisk installed on the device, I patched the boot.img.tar file and then transferred it back to computer.
4-2-3) Put the device in recovery mode and then loaded the patched version of boot.img.tar file into AP slot of the Odin3 v3.14 and then clicked start.
4-1-4) The result in devices recovery mode is: only official released binaries are allowed to be flashed (recovery) (photo attached)
4-1-5) failing the flash process doesn't break the device and I was able to boot to my device.
Please if anyone has a clue, tell me the solution. I'm so desperate now. I've tried different workarounds in internet and non worked. I even tried installing unofficial version of TWRP and still the same message appears.
UPDATE:
I found a solution to install twrp using adb and fastboot commands. I got the device to be recognized by computer. but unfortunately "fastboot flash recovery boot.tar" command doesn't work and it sticks in sending the image state. So this method isn't working either.
UPDATE 2:
I found this post on xda dating back to 2018. According to this post I should wait 7 days (like "the ring" movie!) so that the message i referred to is gone and I can flash whatever I want.
I have had a galaxy s7 edge for some time now and I have experienced a lot of flashings with that device and never came across sth like this. Now I have to wait and see unless someone or me come up with a better solution.
P.S. I have some trust issues and I can't give team viewer or anydesk access to those who are able to help. So please don't ask for any. I kindly ask you guys to help me in anyway possible under this thread. If more information is required I will make sure to provide you with that.
Thanks in advance.
Click to expand...
Click to collapse
EXACTLY AFTER 7 DAYS I WAS ABLE TO ROOT MY DEVICE FOLLOWING THE FIRST METHOD, AND THERE WAS NO ERROR THIS TIME. THANKS XDA.
DEAR MODERATORS CAN DELETE THIS POST.

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