Develop Bugs

[EU][boot][stock] Boot.img and patched_boot.img for OP8 pro 10.5.10BA & 10.5.10AA

10.5.10.IN11BA (European version):
I dumped the boot.img with payload dumper from the "OnePlus8ProOxygen_15.E.19_OTA_019_all_2007021957_d0064.zip" file and patched it with magisk
Note: This is for the European variant of version 10.5.10(.IN11BA)
Download links:
boot.img: https://drive.google.com/file/d/1q9BP31PO6tELbTR-4bWD8pP19_g_VSU0/view?usp=sharing
patched boot.img: https://drive.google.com/file/d/1peDOwsvoUVIoEkp8WZ3jGoRvyqd46MOo/view?usp=sharing
You can use these files to root your OP8Pro with the following guide: https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-how-to-root-oneplus-8-pro-twrp-t4083981
10.5.10.IN11AA (global version):
I dumped the boot.img with payload dumper from the "OnePlus8ProOxygen_15.O.19_OTA_019_all_2005301411_63c531a1a94a4fc1.zip" file, you'll have to patch it yourself with magisk
Here is the boot.img file for 10.5.10.IN11AA : https://gofile.io/d/yavZRg
You can patch it using the following steps (source: Magisk github)
Copy the boot.img file to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. (If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img)
Flash the patched boot image to your device with adb:
Code:
fastboot flash boot /path/to/magisk_patched.img
reboot
Please give me feedback if it worked or not

Hello, Thanks for this work. Just a beginner's question, I suppose you must already have an unlocked bootloader to use your files.

vigneras said:
Hello, Thanks for this work. Just a beginner's question, I suppose you must already have an unlocked bootloader to use your files.
Click to expand...
Click to collapse
Yes of course.
Is this patched with magisk 20.4,not magisk canary? And fingerprint sensor works after that?

Thanks, I would come back after unlocking the bootloader

janitor9 said:
Yes of course.
Is this patched with magisk 20.4,not magisk canary? And fingerprint sensor works after that?
Click to expand...
Click to collapse
Yes indeed, patched with 20.4 and fingerprint works fine. I recommend backing up the persist.img just to be sure

Hey brother, any chance of patching 10.5.10AA? Thank you in advance. Cheers
Sent from my IN2025 using Tapatalk

rawhide85 said:
Hey brother, any chance of patching 10.5.10AA? Thank you in advance. Cheers
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
Here is the boot.img file for 10.5.10.IN11AA : https://gofile.io/d/yavZRg
You can patch it using the following steps (source: Magisk github)
Copy the boot.img file to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. (If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img)
Flash the patched boot image to your device with adb:
Code:
fastboot flash boot /path/to/magisk_patched.img
reboot

Unable to boot from patched image. Unable to boot from normal boot patched with magisk ... as a hole - no root with 10.5.10BA
Can someone suggest solution?

Lucifer4o said:
Unable to boot from patched image. Unable to boot from normal boot patched with magisk ... as a hole - no root with 10.5.10BA
Can someone suggest solution?
Click to expand...
Click to collapse
Boot the twrp and flash magisk

cultofluna said:
Boot the twrp and flash magisk
Click to expand...
Click to collapse
Same result - boot loop.

Does anyone have the stock boot.img for the Global version of 10.5.10? For the IN2017 OnePlus 8. IN21AA.

10.5.11 EU Patched pls ??

alxioa said:
10.5.11 EU Patched pls ??
Click to expand...
Click to collapse
Found it here:
https://forum.xda-developers.com/showpost.php?p=83137417&postcount=424

Flying Fox said:
Found it here:
https://forum.xda-developers.com/showpost.php?p=83137417&postcount=424
Click to expand...
Click to collapse
Thanks my friend

hi, sadly the payload unzip doesn't work on my computer. I am urgently looking for the boot.img for 10.5.10.IN21BA. Can anyone help me? i can't find it on the net.

(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides

Hi all,
Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself
Please read the process before committing to proceeding, so you know what's required and what you should and shouldn't use!
Stock and patched images are UK/ EU but the guides are universal and could be used on multiple devices.
NOTE:
For these guides the versions used are:
Stable, Canary or BETA depending on firmware, simply change the channel in Magisk settings then select install / update:
11.0.1.1
Magisk Manager - Magisk (Canary) version: 1469b82a (21101)
11.0.2.2
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
11.0.3.3
Boot img patched using Magisk beta 21.4 (21400)
11.0.4.4 (DO NOT UPDATE TO 22.0 YOU WILL BOOTLOOP!
Boot Img patched using Magisk beta
21.4 (21400)
11.0.5.5
Boot img patched using Magisk Stable 22.0 (22000) (18)
11.0.6.6
Boot img patched using Magisk Stable 22.1 (22100)
11.0.7.7
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.8.8
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.9.9
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.10.10
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.11.11
Boot.img patched using Magisk 24
https://forum.xda-developers.com/attachments/11-0-11-11-europe-patched-24303-zip.5566283/
Thanks @tfae
12 11.C.15 EU. Thanks @tfae
1st
Extracting a boot.img using Payload dumper
Pre-requisites
A device with a working version of magisk manager installed, simply change the channel to the version outlined in the list above relevant to your firmware then select install / update:
A Windows 10 computer / laptop
A full update downloaded firmware zip for your model (recommend oxygen updater)
Payload dumper program for Windows.
Process
On your computer
1. Download and copy the PAYLOAD DUMPER folder to your desktop, there will be one folder with 2 files and 2 folders inside.
Download from here: https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
2. Download the firmware of your choice and open it using Winrar or a similar zip program, extract the file called payload.bin to the folder within the payload folder called payload_input.
3. Run the program payload_dumper.exe, a Command prompt will open to show extraction progress (this will extract a bunch of files to the payload_output folder) allow it to completely finish (the CMD window will close automatically)
4. One of the files will be called boot.img, this is the file we'll be patching, copy this to your phone, root of storage which is called /sdcard.
On your phone
5. Open up Magisk and click Install / Update, if you don't see update then change channel, so this by changing the channel in magisk settings, it'll then show the install/ update buttons.
6. Select "Select and Patch a file" it'll open up a file browser, navigate to the boot.img you copied earlier and select it, allow it to complete (this will output a file called "magisk_patched" (which will be in the Downloads folder)
You now have a patched boot.img ready to flash to either slot with fastboot or boot via fastboot, would recommend booting as this is risk free, if it's a bad image for whatever reason and you choose to flash then your phone may bootloop.
NOTE** Some people have noticed that an already patched boot.img when flashed can fail and cause a boot loop when flashed,so if you have downloaded a magisk_patched img from somewhere else then you WILL need to re-patch it on your own device preferably using the afore mentioned magisk manager based on what firmware it's from.
If you intend to follow the guide below with your own patched img then you shouldn't need to patch twice but it won't hurt if you do.
2nd
Upgrading from rooted Android 10 to rooted Android 11
Pre-requisites
A rooted device running Android 10
Canary magisk manager or beta version that works:
Windows 10 computer / laptop
Process
On your phone
1. Disable all Magisk mods
2. Download the Android 11 firmware using Oxygen updater DO NOT INSTALL AUTOMATICALLY, WE NEED TO INSTALL MANUALLY!!!
3. Once downloaded; open settings / system / system updates
4. Click the settings cog and click 'install from local storage'
5. Locate the firmware you downloaded, it's in the root of storage.
6. Click install and allow it to finish, DO NOT CLICK THE REBOOT BUTTON YET!
7. Open Magisk. manager and click "Install / Update"
8. Click "Install to Inactive slot (After OTA) (Once complete, click reboot)
As this is a new base the first boot may take a little longer.
Your phone will now boot with Android 11.0.0 and will have retained root, all your apps will remain as you left them.
Be careful what mods you re-enable as they may not be 11 compatible.
3rd
Update from 11 stable to 11+ stable whilst retaining root
Guide
1. Download the relevant firmware for your device via oxygen updater
2. Open Magisk and remove all the modules you have installed, then reboot
**NOTE- At this point I tend to copy out the whole firmware to my computer, incase I need it in the future, the boot img and patched boot img are at the foot of this guide, I'll always upload the latest firmware as soon as it comes out for the UK/EU model
3. Open up settings / system / system updates , click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage.
4. Click install and allow it to go through the process
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS "INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES"
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select "Install to Inactive slot (After OTA)" then select "LET'S GO" once complete click reboot.
7. Once your phones booted back up your system / files should all remain as they were and you should have root access.
You can now install all your modules again so long as they're compatible with the firmware you've just updated to.
4th
Rooting using fastboot commands
Method 1
Booting the patched image
1. Obtain a patched boot image for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - The above suggested downloads are for the EU / UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager to avoid a bootloop, if you still get a bootloop it's best to obtain one yourself using the guide at the top of this post.
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
You should now boot and remain rooted.
Method 2
Flashing to both slots
1. Obtain a patched boot img for your device variant or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, if you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
Command: adb reboot bootloader
3. Open a command prompt on your computer and navigate to your ADB/fastboot folder.
4. Type the following.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter
6. Your phone should now boot, open magisk and verify you're rooted.
Troubleshooting
If flashing succeeds but you don't have root and you've followed all the instructions, you may have some magisk modules still active, try performing the following.
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation enter this command via ADB.
adb wait-for-device shell magisk --remove-modules
3. Allow to boot, modules will be removed and root should then be active.
Thanks @nycdiplomat for this tip.
If there is no magisk install / update buttons.
1. Make sure you have granted permission to magisk in settings / apps / magisk / permissions
2. Make sure that the update channel is on canary, then force close magisk and then re-open
3. If it still doesn't work then update magisk using canary
4. Last method to check would be to change to the beta channel in magisk settings, then install it.
Or change the update channel, install the version on offer, then change back to canary, install and you should be good to go.
Window's version
Windows 7 will not work with fastboot, please use Windows 10
USB
Use USB 2.0 not 3.0 or 3.1
ADB
These are the files i use for ADB (1st in the below list) tested these on fresh installs of windows on several windows machines, all win 10
Place them into the root of C so it reads C:\ADB much easier to navigate to that way.
Files:
ADB Files for Windows 10:
7.69 MB folder on MEGA
5 files
mega.nz
Payload dumper program for Windows-
https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
Full OTA - Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 FIRMWARE -
https://mega.nz/file/TZl2WIBR#wSP3_bkoWl1FZZX7zfhobo3cYIAhWvDQ9f0ot3_qNFo
Oxygen OS 11.0.0 EU 11.IN11BA - IN2023 Patched boot.img -
https://mega.nz/folder/TE8yWbIL#a6woc43pCpTX_URX5dWr1A
Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 Stock boot.img -
https://mega.nz/folder/6d1mVYgJ#tE90TcwqTLp71SgZX9Xxhg
Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 Patched boot.img -
https://mega.nz/folder/CINjAQCZ#Sns
sRugbc0sELF0ajSAEXg
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
Oxygen OS 11.0.2.2 - EU IN11BA -IN2023 Stock boot.img -
https://mega.nz/folder/PFsmFDKY#01sGzxzVpiAELjcT0LuZmQ
Oxygen OS 11.0.2.2 - EU IN11BA -IN2023 Patched boot.img -
https://mega.nz/folder/vJs0FRBD#SisIJ5FrmkJ3ej1RB6Yz3Q
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
Oxygen OS 11.0.3.3 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.3.3 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.4.4 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.4.4 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.5.5 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.5.5 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.6.6 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.6.6 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.7.7 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.7.7 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.8.8 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.8.8 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.10.10 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.10.10 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.11.11 EU IN11BA - IN2023
Stock boot.img
16.98 MB file on MEGA
mega.nz
Oxygen OS 11.0.11.11 EU IN11BA - IN2023
Patched boot.img
https://forum.xda-developers.com/attachments/11-0-11-11-europe-patched-24303-zip.5566283/
Android 12 11.C.15 - Stock and patched images from. @tfae
File on MEGA
mega.nz

Hi bro thank you so much for this. I don't understand what to do next now. My phone is already updated to 11 and I want to root it and install masigk etc how do I do that? Its already on version 11 I installed normal version 11 stock rom.
So I was on version 10 before and it was rooted and I had magisk I updated and lost root access and magisk. So now I'm on version 11. I have downloaded your patched boot image but what do I do next could you please hell me?

dblane82222 said:
Hi bro thank you so much for this. I don't understand what to do next now. My phone is already updated to 11 and I want to root it and install masigk etc how do I do that? Its already on version 11 I installed normal version 11 stock rom.
So I was on version 10 before and it was rooted and I had magisk I updated and lost root access and magisk. So now I'm on version 11. I have downloaded your patched boot image but what do I do next could you please hell me?
Click to expand...
Click to collapse
Ah so you're on 11 stock? Have you unlocked the bootloader?
I have a guide based on android 10 here for unlocking the bootloader, lot of similarities.
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
Please don't dive in without reading first.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section.
Please let me know before you start.
PS: thanks for not quoting the entire post

Bootloader is already unlocked.
Yes I'm on stock 11.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section. (Where is this section?)
I'm about to start the process now.

dblane82222 said:
Bootloader is already unlocked.
Yes I'm on stock 11.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section. (Where is this section?)
I'm about to start the process now.
Click to expand...
Click to collapse
Yep that should be fine. I think you can also do this from magisk under direct install but I've not tried before and I think it's possible that this may require twrp. So yea go with the root guide.
Should be ok.

Could you give me the link to the Rooting section you have referred too so I know what to do please?
And magisk won't install for me won't let me. So I can't do that. I even tried installing twrp but it won't work.

dblane82222 said:
Could you give me the link to the Rooting section you have referred too so I know what to do please?
And magisk won't install for me won't let me. So I can't do that. I even tried installing twrp but it won't work.
Click to expand...
Click to collapse
No don't install twrp it doesn't work..
Rooting should be a case of installing the magisk_patched IMG to the active slot, you can do both..
The root process is at the bottom of the link i sent you mate.

This is the section on root.
You'll need the magisk_patched file from the OP
Rooting
1. On your computer
Get the magisk_patched file
2. Copy "magisk_patched.img" to C:\Android
3. Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
4. Type the following into the window
adb reboot fastboot
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
On your computer
5. Type the following into the window
fastboot flash boot_a magisk_patched.img
press enter
then
fastboot flash boot_b magisk_patched.img
press enter
NOTE* THIS WILL FLASH THE PATCHED BOOT IMG TO BOTH SLOTS, THIS IS WHAT I DID, I HAVEN'T EXPLORED IF ONE SLOT IS ADEQUATE OR NOT, IT MAY BE POSSIBLE TO ONLY FLASH THE BOOT.IMG TO ONE SLOT BUT AS I HAVEN'T I CAN'T ADVISE.
6.. Once complete, type in the following command
fastboot reboot
press enter, your device will reboot
7. On your phone open up "Magisk Manager" you should now have two green ticks signifying that you now have root access.

So long as you have magisk manager installed that's all you need to do besides that guide

Let me know how u get on

dladz said:
Let me know how u get on
Click to expand...
Click to collapse
so every time i do this on my cmd it says unknown partition 'magisk_patched.img'
error cant determine image file name for 'magisk_patched.img'
sorry if i seems stupid.
---------- Post added at 09:44 PM ---------- Previous post was at 09:34 PM ----------
dladz said:
Let me know how u get on
Click to expand...
Click to collapse
okay so its worked now. i managed to flash it but once i restarted the phone its stuck in a loop keeps going to bootloader menu what do i do now?
---------- Post added at 09:57 PM ---------- Previous post was at 09:44 PM ----------
okay so now its gone to crashdump mode?

dblane82222 said:
so every time i do this on my cmd it says unknown partition 'magisk_patched.img'
error cant determine image file name for 'magisk_patched.img'
sorry if i seems stupid.
---------- Post added at 09:44 PM ---------- Previous post was at 09:34 PM ----------
okay so its worked now. i managed to flash it but once i restarted the phone its stuck in a loop keeps going to bootloader menu what do i do now?
---------- Post added at 09:57 PM ---------- Previous post was at 09:44 PM ----------
okay so now its gone to crashdump mode?
Click to expand...
Click to collapse
? What did you flash?

dladz said:
? What did you flash?
Click to expand...
Click to collapse
the file you gave .. the bootimage please help me because im screwed now i dont have a working phone...
so basicaly before i installed what u gave me and it was just stuck on the bootloader screen it wouldnt go off it. at all
so i installed twrp and then it jut crashed mode... please please help me?

So you needed the magisk_patched from the beginning of this thread (the OP)
Then boot to fastboot mode and flash to both slots using ADB / fastboot from Windows..
Then fastboot reboot.
That's literally it mate..that's all I did.
If you're in crashdump mode then i have no idea what you flashed or how you flashed it..shouldn't have done that.
You're on the EU/UK model right?
No reason why it wouldn't have worked.

dblane82222 said:
the file you gave .. the bootimage please help me because im screwed now i dont have a working phone...
so basicaly before i installed what u gave me and it was just stuck on the bootloader screen it wouldnt go off it. at all
so i installed twrp and then it jut crashed mode... please please help me?
Click to expand...
Click to collapse
Ok so do not install twrp it does not work on 11.
Calm down a moment you haven't broken anything so don't worry..
Tell me what screen you're on please. Also can you boot to fastboot mode? Or even bootloader?
Worse case scenario you will have EDL mode and the MSM tool which can get you back up and running..
Do not attempt to install twrp as it will not work and will cause more harm than good.

If you add steps besides what you're meant to do I can't help you pal.

dladz said:
Ok so do not install twrp it does not work on 11.
Calm down a moment you haven't broken anything so don't worry..
Tell me what screen you're on please. Also can you boot to fastboot mode? Or even bootloader?
Worse case scenario you will have EDL mode and the MSM tool which can get you back up and running..
Do not attempt to install twrp as it will not work and will cause more harm than good.
Click to expand...
Click to collapse
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
dblane82222 said:
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
Click to expand...
Click to collapse
do you have anything that i can speal to u on thats more instant such as whts app or discord or icq or anything ??

dblane82222 said:
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
do you have anything that i can speal to u on thats more instant such as whts app or discord or icq or anything ??
Click to expand...
Click to collapse
I'm actually in bed at the moment pal.
Here's the MSM thread
https://forum.xda-developers.com/on...-tool-to-restore-device-t4084953/post82327013
I think it may have been trying to install twrp.
Before you go down the MSM route.
Try to power off the device without the cable connected..press and hold power and vol down..until the phone turns on.
Should go to bootloader.
If not try it the above with the cable connected to your phone and computer.
If you still can't get in then yes it's MSM time..
Personally have never used it but it's an active thread so always people in there and 10000% someone will have been in the same boat as you.
Not sure what happened with your situation tbh..I tested all the files again myself and they're all legit. I used them before I spoke with you and again just now.
Please though, try not to worry, you'd have to do something mental to break a OnePlus.
You'll be fine.
Let me know how your get on and I'll answer when I can..quite tired at moment.

yeah tried all of that still nothing. going to try the msm solution see what that does its downloading as we speak. but even before the twrp i done what u said and it was stuck on bootloader any idea why that would be ? i can understand it happened becuase i installed twrp and that casued the phone ot enter edl mode. but prior to it it was stuck on bootloader. following just the steps u had said ? once i have got he phone back up and running should i try your mehtod again and see what happens again ?
no problem really apprecite all the help you have given me thank so much.

dblane82222 said:
yeah tried all of that still nothing. going to try the msm solution see what that does its downloading as we speak. but even before the twrp i done what u said and it was stuck on bootloader any idea why that would be ? i can understand it happened becuase i installed twrp and that casued the phone ot enter edl mode. but prior to it it was stuck on bootloader. following just the steps u had said ? once i have got he phone back up and running should i try your mehtod again and see what happens again ?
no problem really apprecite all the help you have given me thank so much.
Click to expand...
Click to collapse
Nah no worries man, just trying to work out what happened..
Once you're back up, maybe ask another thread just to confirm as I'm second guessing myself now..
Don't want you to end up like this again..
See what the chap says in the MSM thread too, his telegram username is in his profile.
To confirm you do have a UK phone right? IN2023 BA
Could have just been the flash didn't go through. You did do a flash and not boot right? To get out of that. Could have just flashed the stock boot.img and that would have saved you

[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)

Root Motorola Devices with Magisk
Note:
This method has been working with most Moto Devices that the Bootloader can be UnLocked.
If the Bootloader cannot be Unlocked this method will not work.
Please only use this as a reference. If you require more help please post in your device's forum.
Mention me with @sd_shadow
Quick Steps
Unlock the Bootloader
Note: Unlocking will wipe Userdata
Install Magisk manager app
Spoiler: Check ramdisk status
{
"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"
}
If Ramdisk is Yes continue to Download Firmware
If Ramdisk is anything else see
New check ramdisk status -26 March 2021
Download Firmware Rescue and Smart Assistant(LMSA)(PC)
Spoiler: Check the Current software version with the download version.
If the download is newer, now is a good time to flash the update.
The newer boot.img may not work correctly with the older software on the device.
If you want to keep the firmware version that is on the device see Other Firmware Options
Other Firmware options
Find the boot.img in the LMSA Downloads Folder
"ProgramData\LMSA\Download\RomFiles\"
Copy boot.img to Moto Device
Spoiler: Tap Magisk > Install
Spoiler: Tap "Select and Patch a File"
Spoiler: Check the Patched.img Filename and Location
Copy magisk_patched.img to PC
Flash magisk_patched.img
Reboot
Open Magisk manager to verify you have the current version.
Hide Magisk
If you use apps the won't work if rooted devices (Banking apps) Enable Hide Magisk
Safetynet fix (21 March 2022)
https://github.com/kdrag0n/safetynet-fix
More​
Magisk Hide: Using banking Apps
Magisk Recovery Mode
Install Updates and Keep Root
Root with Magisk Twrp method
https://github.com/topjohnwu/Magisk/releases/

Troubleshooting
If you get a "no ramdisk" error​
Try flashing patched.img anyway it may still work
https://github.com/topjohnwu/Magisk/issues/3239
You may need to also patch the recovery.img
Like in this Post

Additional Links
[Stock ROM] How to root the Snapdragon Moto E 2020
Moto One 5G Ace root guide
Motorola One Macro [Root Tutorial]

Flashing magisk_patched.img
Change .img name to exact file name.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
or
Code:
fastboot flash boot magisk_patched.img
fastboot reboot

Magisk in recovery
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Click to expand...
Click to collapse
This does not replace stock recovery.
Installation
The Magic Mask for Android
topjohnwu.github.io

Magisk
Magisk Manager is dead.​Long live the Magisk app!​Ever since the first Magisk release, Magisk (the core components) and Magisk Manager (the companion app) are released separately and isn't necessarily always in sync. This leads to some confusion and a lot of complexity when downloading/installing Magisk through the app. Starting from v22.0, the Magisk app (renamed from Magisk Manager) includes everything it needs within the APK itself, making installation a 100% offline process.
Custom recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC™. Check out the updated installation guide for more info.
Click to expand...
Click to collapse
Installation
The Magic Mask for Android
topjohnwu.github.io

Magisk Recovery mode
[DEPRECATED] [2019.4.4] Magisk Manager for Recovery Mode (mm)
THIS PROJECT IS NO LONGER SUPPORTED. # Magisk Manager for Recovery Mode (mm) ## LEGAL Copyright (C) 2017-2019, VR25 @ xda-developers This program is free software: you can redistribute it and/or modify it under the terms of the GNU General...
forum.xda-developers.com

New Magisk Instructions
Installation
The Magic Mask for Android
topjohnwu.github.io

Hiding root and bootloader from Banking apps
Magisk and MagiskHide Installation and Troubleshooting guide : MagiskHide
Magisk renaming is maybe required.
Try using VD INFOS, you can see every detectable thing. (Root/Magisk/Xposed/Riru/and others.)
[APP][v1.10] VD Infos (Package: com.vitaodoidao.vdinfos)
(Para quem fala PORTUGUÊS, o próximo post está totalmente traduzido !) VD Infos v1.10 As we all know, Android is a super powerful and super versatile operating system. What nobody tells you is that all your personal details and confidential...
forum.xda-developers.com

Wow, thanks so much for the comprehensive reply @sd_shadow. Think I may take a look at the non-TWRP method.
Interesting that you install Magisk immediately after unlocking bootloader. I had been following these instructions: https://appuals.com/root-Motorola-moto-g5-g5-plus/ which doesn't install Magisk until after TWRP - but then you're not using TWRP!
In answer to @Wolfcity, yes I had tried reboot to TWRP, but get the following:
C:\adb>fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
I should've said, that's mostly why I figured it had failed.
I'm actually rooting to make use of Nethunter on the device. It's an old device, so not one I'll be using for any everyday apps or accounts. It'll be dedicated to Nethunter - for legit purposes only!

sd_shadow said:
Root Motorola Devices with Magisk
Note:
This method has been working with most Moto Devices that the Bootloader can be UnLocked.
If the Bootloader cannot be Unlocked this method will not work.
Please only use this as a reference. If you require more help please post in your device's forum.
Mention me with @sd_shadow
Quick Steps
Unlock the Bootloader
Note: Unlocking will wipe Userdata
Install Magisk manager app
Spoiler: Check ramdisk status
If Ramdisk is Yes continue to Download Firmware
If Ramdisk is anything else see
New check ramdisk status -26 March 2021
Download Firmware Rescue and Smart Assistant(LMSA)(PC)
Spoiler: Check the Current software version with the download version.
If the download is newer, now is a good time to flash the update.
The newer boot.img may not work correctly with the older software on the device.
If you want to keep the firmware version that is on the device see Other Firmware Options
Other Firmware options
Find the boot.img in the LMSA Downloads Folder
"ProgramData\LMSA\Download\RomFiles\"
Copy boot.img to Moto Device
Spoiler: Tap Magisk > Install
Spoiler: Tap "Select and Patch a File"
Spoiler: Check the Patched.img Filename and Location
View attachment 5384841
Copy magisk_patched.img to PC
Flash magisk_patched.img
Reboot
Open Magisk manager to verify you have the current version.
Hide Magisk
If you use apps the won't work if rooted devices (Banking apps) Enable Hide Magisk
More​
Magisk Hide: Using banking Apps
Magisk Recovery Mode
Install Updates and Keep Root
Root with Magisk Twrp method
https://github.com/topjohnwu/Magisk/releases/
Click to expand...
Click to collapse
Question, when I did all of this through magisk everything went swell but my moto Touchscreen stopped working but booted just fine not sure if it was a one time fluke or not gonna try again any suggestions? Should I also Flash Recovery?

Jr.17 said:
Question, when I did all of this through magisk everything went swell but my moto Touchscreen stopped working but booted just fine not sure if it was a one time fluke or not gonna try again any suggestions? Should I also Flash Recovery?
Click to expand...
Click to collapse
If the touchscreen stopped working you likely used the wrong boot.img
You don't need a custom recovery just for root.

Sweet thanks I'll look again at what I got

Jr.17 said:
Sweet thanks I'll look again at what I got
Click to expand...
Click to collapse
boot.img must match build version and channel that is on the device.

Ok I see Where I messd up now looks like I used wrong channel

sd_shadow said:
Flashing magisk_patched.img
Change .img name to exact file name.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
or
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
I can't get my pc to see the phone when the phone is in fastboot mode

Grimace78 said:
I can't get my pc to see the phone when the phone is in fastboot mode
Click to expand...
Click to collapse
See device manager, how is it listed?

@sd_shadow My devices is edge xt2063-2 （USA，5G brand N71），It’s can't connect to chinatelecom（5G band N78）
But xt2603-3（Europe）ROM include N78 band
Can I flash XT2063-3 EU ROM on mydevices just by fastboot mode?
Or Just need modify some .img files

Vger20192019 said:
@sd_shadow My devices is edge xt2063-2 （USA，5G brand N71），It’s can't connect to chinatelecom（5G band N78）
But xt2603-3（Europe）ROM include N78 band
Can I flash XT2063-3 EU ROM on mydevices just by fastboot mode?
Or Just need modify some .img files
Click to expand...
Click to collapse
If the bootloader is unlocked, no problem.
If the bootloader is still locked, just flash the radio part.
Flashing the Radio Firmware

Grimace78 said:
I can't get my pc to see the phone when the phone is in fastboot modemak
Click to expand...
Click to collapse
Also Make sure To Update Drivers

How To Guide [CLOSED] [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13-A.10

This tutorial will :​
Provide you with all the steps to unlock your Oneplus 11 bootloader
Provide you with all the steps to root your Oneplus 11 (with your bootloader already unlocked)
Provide you with all the steps to keep root during/after an OTA (system update)
Provide you with some Interesting Magisk Modules
Provide you with a lot tricks if you have troubleshooting questions
Provide you with a lot of solutions of you have softbricked your Oneplus 11
Provide you with all the ways if you want to bring back your Oneplus 11 to unroot & lock back the bootloader
PHB110 - China : ColorOS
CPH2447 - India : DA
CPH2449 - EU : BA
CPH2449 - GLO: International
CPH2451 - NA/Global : AA / North America
Original_Init_boot images : Extracting Payload.bin
use payload dumper go from https://github.com/ssut/payload-dumper-go
Guide: how to extract payload from the OTA Package and get the init_boot.img ?
And share the Original_init_boot.img with us by posting them in this thread.
All init_boot.img are Orginals (not patched with Magisk, that will be your job to patch them following the guide below!)
OxygenOS 13.1.0.501_init_boot :
CPH2451 Init_Boot (AA) / Not yet available
CPH2449 Init_Boot (BA/GLO) / Not yet available
CPH2447 Init_Boot (DA)
Full OTA packages / Not yet available
OxygenOS 13 A.10_init_boot :
CPH2451 Init_Boot (AA)
CPH2449 Init_Boot (BA/GLO)
CPH2447 Init_Boot (DA)
Full OTA Packages / Full OTA EU A10 / Full OTA DA/India A10
OxygenOS 13 A.09_init_boot :
CPH2451 Init_Boot (AA)
CPH2449 Init_Boot (BA/GLO)
CPH2447 Init_Boot (DA)
Full OTA packages
OxygenOS 13 A.08_init_boot :
Init_Boot (AA)
Init_Boot (BA) / Not yet available
Init_Boot (DA)
OxygenOS 13 A.07_init_boot :
Init_Boot (AA)
Init_Boot (BA)
Init_Boot (DA)/ Not yet available
OxygenOS 13 A.06_init_boot :
Init_Boot (AA)
Init_Boot (BA) / Not yet available
Init_Boot (DA) / Not yet available
PHB110 - China : ColorOS
CPH2447 - India : DA
CPH2449 - EU : BA
CPH2449 - GLO: International
CPH2451 - NA/Global : AA / North America
STEPS to root your device:
I recommand to update first your device with all OTA available using Settings/updates before unlocking & rooting it. It is also recomended not to set any lockscreen password before unlocking the bootloader/rooting. So if you have a lockscreen password / fingerprint just remove it, root your device and set it up after rooting your device.​Unlock the Bootloader and Root the OnePlus 11​Step 1 – Enable OEM unlocking​You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings > About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
{
"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"
}
Step 2 – Unlock your bootloader​Set up adb, reboot into your bootloader, and run the following command. Yes, it’s really that simple!
"fastboot flashing unlock"
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Unlocking the bootloader wipes your device :
Root your Oneplus 11 (with Bootloader already unlocked)​
Patch OnePlus 11 Init_Boot.img via Magisk​
Download and install the lastest Stable Magisk App starting from v26.1 works fine.
Then launch it and tap on the Install button next to Magisk.
After that, choose ‘Select and Patch a File’, and navigate to the stock init_boot.img file, and select it.
Then tap on the Let’s Go button situated at the top right.
The init_boot.img file will now be patched and placed under the Downloads folder on your device. You should transfer this file to the platform-tools folder on your PC and rename it to magisk_patched_boot.img.
Boot OnePlus 11 to Fastboot Mode​
Now connect your device to the PC via a USB cable. Make sure USB Debugging is enabled.
Then head over to the platform-tools folder, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt.
Type in the following command in the CMD window to boot your device to Fastboot Mode "adb reboot bootloader"
To verify the Fastboot connection, type in the below command and you should get back the device ID.fastboot devices
Flashing the magisk_init_boot​1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 9 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot flash init_boot magisk_init_boot.img"
Change to the exact name "magisk_init_boot.img" of the init_boot that has been patched
"fastboot reboot"
Step 2 - Reboot and your device is now rooted !​
Keep Root after OTA Updates​
How to update OTA and KEEP ROOT
It is advised to disable or even uninstall all magisk modules to be safe!
How: go to Magisk application/modules/disable &/or uninstall
Option 1: With full OTA Access (BA/DA) :
Step 1 - Get & install the full OTA zip file​1. Go to System-Update or update get the OTA using Oxygen Updater
2. Tap OK when the message that you are rooted appears
3. Tap "Download and install" or local update if OTA from Oxygen Updater
For Android 13, install this APK "OPLocalUpdate_For_Android13.apk"
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW! Use the above application to make sure your device will not reboot
5. Open Magisk Application
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​​Option 2: with incremental OTA Access (AA) :​
Option 2A : Get back your original init_boot image using Magisk Manager
1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock init_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 11
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Reboot and enjoy​
Option 2B : Get back your original init_boot image
You can find your originel init_boot.img in our thread from your current OTA.
Go to fastboot.
Code once in fastboot mode:
"fastboot flash init_boot original_init_boot.img"
You will obviously loose Root access once you have flash the originel_init_boot.
Then just flash the incremental OTA using your system OTA or Oxygen Updater.
To get root again just read the above guide :
Patch OnePlus 11 Init_Boot.img via Magisk​
Troubleshooting questions :​
Before reporting any trouble, follow the steps below in order to have GooglePlay certified, keep L1 Widevine & pass CTS :
Step 1 - Magisk Settings​1. Once rooted, in Magisk setting, select MagiskHide and Systemless host
2. In MagiskHide select GMS, Netflix, Google Store & any application you may find sensitive to Magisk detection
For Netflix, go to Settings, Appplications & select Netflix:
a-force stop the app
b-clear cache and storage
c-hide the App in magisk
d-restart phone to recovery and clear cache
Hide everything under Google play services and store.:
3. Reboot
Step 2 - Clear caches​Clear caches of Google Play Service & Play Store
Go to Settings, Applications & select Google Play Service, delete data
Go to Settings, Appplications & select Play Store, delete data
Step 3 - Safetynet Fix​Install Safetynet Fix Magisk Module
Step 4 Optional - Shamiko Module​Install Shamiko Module​How to use it : guide
How to fix Netflix ? :​​If you can't install/update Netflix thru Google Play install the latest Netflix from apkmirror manually (like any other apk file)
Option 1 - Follow this guide​
Option 2 - Flash the DRM module attached
Option 3 - Flash another DRM module attached
Usefull Magisk Modules For Oneplus 11:​Google materials:
Enable Call Recording with native
Enable unlimited storage Google photos
Music & Video materials:
Viper 4 Android
Revanced Manager to get Revanced Youtube & others Revanced applications
Theming materials:
- Substratum lite : Liv Dark theme & OOS Outher theme
- Cyberpunk Bootanimation
- OOS Status bar magisk module (see attached)
- Repainter application
- Seeker application
- LWP+ application
- OOS themer by Oneplus
Tools materials:
Enable Volte
Enable Engineering unlock
Enable IPV6
Disable Flag secure
Magisk Bootloop Protect
Modules Management materials:
Fox Module Manager
Phone Bricked ? :​
Five options (ranked from the easiest to tougher method):
Option 1 - Reboot to Safe mode & remove Magisk modules​
Option A : Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Option B : thru adb command
1. Code with phone connected with USB debugging on (from developpers options):
"adb wait-for-device shell magisk --remove-modules"
2. reboot
Option 2 - Get back the original init_boot.img​If your device can go to fastboot mode:
Flash back the original init_boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash init_boot.img" (use the "Original_init_boot.img" from the above zip file)
Change to the exact name "Original_init_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Option 3 - Flash the rollback full OTA file (will wipe data)​
OnePlus 11 / Rollback packages :
OnePlus 11 NA Version (A.09)
OnePlus 11 IN Version (A.09)
OnePlus 11 EU Version (A.09)
OnePlus 11 GLO Version (A.09)
Flash it using local update or thru the application OPLocalUpdate_For_Android13.apk
You can also flash it by extracting and flashing the partitions using fastboot and fastbootd manually.
You may also use Fastboot Enhance.
​Option 4 - Flash back full OTA file​If you can still go to Settings:
Flash back the OTA RUU full package and reboot
Option 5 - Change the active slot​If your device can go to fastboot mode:
"fastboot getvar current-slot"
This will tell you what (corrupted) slot you are currently booting from (either a or b).
Then just change to the other slot with the following command:
"fastboot --set-active=a"
or
"fastboot --set-active=b"
Then reboot with the command:
"fastboot reboot"
Option 6 - Wipe data with fastboot command​
Code once in fastboot mode:
"fastboot- w"
Option 6 - OFD/EDL​
Option 1, 2 & 4 would normally not alter your personal data, applications and own set-up​Option 3 and 6 will wipe your personal data and applications
Return your phone to unlock and unroot? :​Option 1 : Original init_boot & relock with fastboot command​Step 1 - Restore orignal init_boot.img​Option A : Thru Magisk App
Open Magisk App on your phone. You will see the Uninstall button in the app. Just click on Uninstall button.
Then you need to click on Complete Uninstall. Your phone will be rebooted automatically.
Option B : Thru fastboot mode
Flash back the original init_boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash init_boot.img" (use the "Original_lnit_boot.img" from the above zip file)
Change to the exact name "Original_init_boot.img" of the init_boot that has been posted in the above zip file
"fastboot reboot"
Once booted, remove Magisk application
Option C : after removing Magisk app entirely Flash the current or latest full OTA zip twice. Why twice, to ensure both slot have the latest update flashed with original init_boot.
Step 2 - Relock the bootloader​1. Execute the following command to proceed for bootloader unlocking: ""fastboot flashing unlock""
2. A verification window will appear on your mobile device asking to confirm the action. Just highlight “Relock Bootloader”using volume buttons and hit the power button to confirm.
3. The phone will initialize to relock the bootloader. It will take some time to reboot after resetting the whole phone into a locked stage.
4. Your device is now locked again !
Do any process described at your own risk. None Xda none the author are responsible for your own choice to unlock & root your Device.

Great job, @Steve0007! That looks like an incredibly helpful and well-written tutorial. You've done an excellent job breaking down a complex process into easy-to-follow steps, making it accessible for users of all levels. Your attention to detail and clear explanations make it a valuable resource for anyone looking to learn and improve their skills. Keep up the great work!

Sorry for the pollution, but : just WOW. Thank you for your valued time and gathering all this here.
> I didnt know you can skip uninstalling magisk if you do a full OTA update, nice.
> You actually cannot clear cache from the recovery on this phone (with included recovery that is)
> Despite following the instructions thoroughly (except the full wiping cache), i still cannot use Netflix. Might be really device related though since i never had issues will my previous devices

Thank
_Johnito_ said:
Sorry for the pollution, but : just WOW. Thank you for your valued time and gathering all this here.
> I didnt know you can skip uninstalling magisk if you do a full OTA update, nice.
> You actually cannot clear cache from the recovery on this phone (with included recovery that is)
> Despite following the instructions thoroughly (except the full wiping cache), i still cannot use Netflix. Might be really device related though since i never had issues will my previous devices
Click to expand...
Click to collapse
Thank you for your comments.
Just updated the guide included 2 options to get Netflix working while rooted !

Thank you and @qriozum , i have netflix working following this steps. Didnt even need to hide it in magisk.

Can I extract the stock init_boot after unlocking bootloader cause I didn't do that before unlocking bootloader. Plus, can anyone teach me on how to extract the stock init_boot. I'm using OxygenOS 13 A.08 CPH2449- EU : BA.

kairukaizer99 said:
Can I extract the stock init_boot after unlocking bootloader cause I didn't do that before unlocking bootloader. Plus, can anyone teach me on how to extract the stock init_boot. I'm using OxygenOS 13 A.08 CPH2449- EU : BA.
Click to expand...
Click to collapse

Thanks. Rooted successfully. Btw how to get root with locked bootloader? Cause I want to get L1 for netflix. I could get root with locked bootloader on my rog 6.

kairukaizer99 said:
Thanks. Rooted successfully. Btw how to get root with locked bootloader? Cause I want to get L1 for netflix. I could get root with locked bootloader on my rog 6.
Click to expand...
Click to collapse
You can't get root with locked bootloader on this (and most) phones.
Anyway, root doesn't necessarily mean that you won't get L1. On my rooted OnePlus 8T I still have L1.

i am on cph2451_11_A09...patching above a06 initA06 and flashing on this build works or not?

N
vnod said:
i am on cph2451_11_A09...patching above a06 initA06 and flashing on this build works or not?
Click to expand...
Click to collapse
No, you should better use your current init_boot.img to patch it. Now we can use the latest v26.0 Magisk app

Hello @Steve0007 ,
What is the correct command to enter please, the first or the second?
Thanks !

zeldomar said:
Hello @Steve0007 ,
What is the correct command to enter please, the first or the second?
Thanks !
View attachment 5881975
Click to expand...
Click to collapse
I tried the second:
And since my OnePlus 11 is in bootloop (the animated OnePlus logo never appears).
Can you help me, please?
Thanks a lot

zeldomar said:
Hello @Steve0007 ,
What is the correct command to enter please, the first or the second?
Thanks !
View attachment 5881975
Click to expand...
Click to collapse
"Fastboot flash init_boot NAME_OF_YOUR_Magisk_init_boot.img"

zeldomar said:
I tried the second:
View attachment 5881985
And since my OnePlus 11 is in bootloop (the animated OnePlus logo never appears).
Can you help me, please?
Thanks a lot
Click to expand...
Click to collapse
My OP 11 works again thanks to this tutorial : https://forum.xda-developers.com/t/...ock-oxygenos-firmware-on-oneplus-10r.4465077/

Hi ,can someone please post boot.img for CPH2449 (EU) A.09? I accidentally flashed init_boot over boot... what a silly move.
Alternatively, the link to the A.09 OTA, I can extract it myself, I tried looking for it but for now nobody posted it.

@geomass this is untouched boot.img for CPH2449 (EU) A.09
But FWI you could just retrieve it yourself easily with lets say Fastboot Enhance and the firmware itself of course.

Thank you so much @_Johnito_ . The timing of your response is insane
I don't use windows so can't run fastboot enhance. How can it be done with fastboot?

You are welcome. I am not the most informed guy here by far but my guess is that if you borked boot.img on your phone, it is probably better to recover it from the vanilla firmware more than from the phone (with fastboot commands). I hope i get your question right though.
For general cases, instructions on "how to backup persist.img" on this great tutorial can be applied for any android partition / any desktop OS with a command line software.

I tried booting into that image you provided, and while it correctly sends it to the device and reboots the device, it goes into fastboot every time.
Flashing it fails every time, like so:
fastboot flash boot boot_CPH2449_11_A.09.img
Sending 'boot' (196608 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed

How do I update rooted rom Android 11 to 12 or 13?

Hello, I want to update my device to Android 12 or 13. This is my device:
xiaomi redmi note 8 pro (begonia)
Miui Global Stable 12.5.7.0 (RGGEUXM)
Android Version: 11 RP1A.200720.011
Bootloader: unlocked
I flashed twrp with BRP3.5.2v3.1. Device is rooted, SafetyNet check in magisk failed.
How do I update to Android 12 or 13 and where do I get the images from or do I have to build them?
Will I still have root access after update?

What are you talking about?
For root:
- Unlocked Bootloader
- Working rom
- By TWRP method: Working TWRP. Flash Magisk.apk
- By Fastboot method: Take boot.img. Patch boot.img. Flash patched boot.img
- Patch vbmeta if you are using Miui. Custom rom don't need this
For pass Safetynet (Magisk v25.2)
- Enable Zygisk
- Enable Enforce Denylist
- Flash Safetynet fix 2.4.0
- Configure Denylist:
+ Google Play Store
+ Google Play Services
- Reboot
- Setting>Apps
- Clear data + storage of 2 Google stuff above
- Check if it show devide certified or not.
Some old rom need to change many props to make rom work. I will not write details here. You can search on YouTube. But i recommend to use new roms to prevent that.

Kirasu2080 said:
For root:
- Working rom
Click to expand...
Click to collapse
What means a working rom?
Kirasu2080 said:
- By TWRP method: Working TWRP. Flash Magisk.apk
Click to expand...
Click to collapse
You wrote in https://forum.xda-developers.com/t/soft-brick-bootloop-after-twrp-flash.4570389/ that twrp-3.3.1-0-begonia.img supports Android 9 only. If I want to use TWRP for A11, I should find an unofficial one by searching "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1).
How do I know, which twrp is fitting my device? Does 'working' in this case mean, the software is penetrate the system to access recovery mode or something else?
Kirasu2080 said:
- By Fastboot method: Take boot.img. Patch boot.img. Flash patched boot.img
Click to expand...
Click to collapse
Is it the same patching as mentioned here https://topjohnwu.github.io/Magisk/install.html?
Patching Images
Copy the boot/init_boot/recovery image to your device
Press the Install button in the Magisk card
If you are patching a recovery image, check the “Recovery Mode” option
If your device does NOT have a separate vbmeta partition, check the “Patch vbmeta in boot image” option
Choose “Select and Patch a File” in method, and select the boot/init_boot/recovery image
Start the installation, and copy the patched image to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Flash the patched boot/init_boot/recovery image to your device;
for most devices, reboot into fastboot mode and flash with command:
fastboot flash boot[_x] /path/to/magisk_patched_[random_strings].img or
fastboot flash init_boot[_x] /path/to/magisk_patched.img_[random_strings] or
fastboot flash recovery /path/to/magisk_patched.img_[random_strings],
where [_x] should be _a or _b or empty depending on your device
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img (note that it may wipe your data)
Reboot and launch Magisk app (you will see a stub Magisk app if you have wipped your data; use it to bootstrap to a complete Magisk app), and you will see a prompt asking for environment fix; click and wait for the reboot
Voila!
Click to expand...
Click to collapse
Kirasu2080 said:
- Patch vbmeta if you are using Miui. Custom rom don't need this
Click to expand...
Click to collapse
What exactly is vbmeta for? For preventing to remove the custom recovery loader? Or do I mistake it with avb close 2.0?
Kirasu2080 said:
Some old rom need to change many props to make rom work.
Click to expand...
Click to collapse
What is an old rom? By date or by software?

liltechie said:
What means a working rom?
You wrote in https://forum.xda-developers.com/t/soft-brick-bootloop-after-twrp-flash.4570389/ that twrp-3.3.1-0-begonia.img supports Android 9 only. If I want to use TWRP for A11, I should find an unofficial one by searching "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1).
How do I know, which twrp is fitting my device? Does 'working' in this case mean, the software is penetrate the system to access recovery mode or something else?
Is it the same patching as mentioned here https://topjohnwu.github.io/Magisk/install.html?
What exactly is vbmeta for? For preventing to remove the custom recovery loader? Or do I mistake it with avb close 2.0?
What is an old rom? By date or by software?
Click to expand...
Click to collapse
Working rom/TWRP mean rom/TWRP that you can boot on your phone.
Ex: Official TWRP can't boot with your Miui rom. So it's not working TWRP.
For knowing which is suitable TWRP, you need to know all about unofficial TWRP and it's changelog.
Fastboot method: it's working with almost device that don't have TWRP.
Patch vbmeta or avb close 2.0 with do same purpose. You can read about vbmeta in Official TWRP flash guide
Old rom is by date. Google update many stuff but old rom can't catch up.