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

Search This thread

jimger

Senior Member
Dec 13, 2012
263
37
Cambridge,UK
OnePlus 8 Pro
Actually you should be able to root, it's no different, why on earth did you wipe your phone?

You should just be trying to boot patched images, not flash them.

If you're already rooted and you're updating to a new OS then the install after ota method should work as expected..if not then just flash the stock boot image
Thanks for letting me know. Anyway I was fine flashing back stock but then tried some kind of weird op9 pro twrp thing from xda that someone suggested and phone was wiped without me being asked. I flashed original boot but phone just started empty... So nothing I could do. But feel free to try yourself and tell. Me if it works. I am just trying to warn people about this. Your phone your data. I just wish I had this warning before upgrading.
 

dladz

Senior Member
Aug 24, 2010
16,010
5,964
Liverpool
Nothing Phone 2
Thanks for letting me know. Anyway I was fine flashing back stock but then tried some kind of weird op9 pro twrp thing from xda that someone suggested and phone was wiped without me being asked. I flashed original boot but phone just started empty... So nothing I could do. But feel free to try yourself and tell. Me if it works. I am just trying to warn people about this. Your phone your data. I just wish I had this warning before upgrading.

You honestly don't need TWRP on any phone these days...unless you're into making nand back ups.

Definitely avoid installing anything from the OnePlus 9 as it most certainly won't work, you can test again by booting images, there's no risk to this method as it's only temporary until you reboot again.

I don't have the 8 pro any longer I'm on the 10 pro but the theory is still the same.
 

jimger

Senior Member
Dec 13, 2012
263
37
Cambridge,UK
OnePlus 8 Pro
You honestly don't need TWRP on any phone these days...unless you're into making nand back ups.

Definitely avoid installing anything from the OnePlus 9 as it most certainly won't work, you can test again by booting images, there's no risk to this method as it's only temporary until you reboot again.

I don't have the 8 pro any longer I'm on the 10 pro but the theory is still the same.
In theory I wouldn't have issue with rooting... But I did. Tbh I found open issue on magisk about same issues on 13.1. Anyway I said there I had op8 pro and tried that. Problem was as said that cleaned it self for no reason no warning... So even by booting might end up the same. Don't know. Anyway in theory should work but in reality it didn't...
 

dladz

Senior Member
Aug 24, 2010
16,010
5,964
Liverpool
Nothing Phone 2
In theory I wouldn't have issue with rooting... But I did. Tbh I found open issue on magisk about same issues on 13.1. Anyway I said there I had op8 pro and tried that. Problem was as said that cleaned it self for no reason no warning... So even by booting might end up the same. Don't know. Anyway in theory should work but in reality it didn't...
Yea I get it that it shouldn't wipe. I can't comment on that, however you shouldn't flash things meant for other devices, also by booting it will not have that effect it will just fail to boot, it 100% will not wipe so you must have flashed it or done something else, bare in mind by flashing you would have had to define a slot meaning your original would have been switched to the new, potentially forcing you to wipe, you probably could have swapped slots when it happened..

Saying that, all of this is meaningless as it's already done.

As a rule of thumb, just boot images don't flash and you'll be fine.
 

jimger

Senior Member
Dec 13, 2012
263
37
Cambridge,UK
OnePlus 8 Pro
Yea I get it that it shouldn't wipe. I can't comment on that, however you shouldn't flash things meant for other devices, also by booting it will not have that effect it will just fail to boot, it 100% will not wipe so you must have flashed it or done something else, bare in mind by flashing you would have had to define a slot meaning your original would have been switched to the new, potentially forcing you to wipe, you probably could have swapped slots when it happened..

Saying that, all of this is meaningless as it's already done.

As a rule of thumb, just boot images don't flash and you'll be fine.
Personally had problems just booting stuff the last couple years. But anyway. BTW I thought it was for op8 pro. Anyway....
 
  • Like
Reactions: dladz

jimger

Senior Member
Dec 13, 2012
263
37
Cambridge,UK
OnePlus 8 Pro
Yes it works perfectly here buddy..
Lucky you then.

That was similar issue for op9 pro. Had the same. Was first time ever that phone got wiped without noticing me 😭
 

dladz

Senior Member
Aug 24, 2010
16,010
5,964
Liverpool
Nothing Phone 2
Lucky you then.

That was similar issue for op9 pro. Had the same. Was first time ever that phone got wiped without noticing me 😭

And does this issue exist on previous versions? I'd probably avoid updating or go for a canary build until it's fixed..
 

Nimueh

Recognized Contributor
May 19, 2012
3,552
3,274
OnePlus 3
Samsung Galaxy Tab A series
And does this issue exist on previous versions? I'd probably avoid updating or go for a canary build until it's fixed..
I rooted my 9P on OOS 13 with 26.1 just fine 4 weeks ago when I got it, and again this week after updating to the latest OOS 13 (the "Install" button of the local update immediately rebooted, so I couldn't keep root but instead had to freshly root + flash TWRP all over again).

I don't know why some users are having those issues, or what they're doing differently. But for ME Stable Magisk 26.1 works just as 25.2 did - flawless :cool:
 
  • Like
Reactions: dladz

zioloiso

Senior Member
Mar 10, 2012
292
35
Actually you should be able to root, it's no different, why on earth did you wipe your phone?

You should just be trying to boot patched images, not flash them.

If you're already rooted and you're updating to a new OS then the install after ota method should work as expected..if not then just flash the stock boot image
Thx for info, I try install update and flashg boot and is ok.
 

dladz

Senior Member
Aug 24, 2010
16,010
5,964
Liverpool
Nothing Phone 2
I rooted my 9P on OOS 13 with 26.1 just fine 4 weeks ago when I got it, and again this week after updating to the latest OOS 13 (the "Install" button of the local update immediately rebooted, so I couldn't keep root but instead had to freshly root + flash TWRP all over again).

I don't know why some users are having those issues, or what they're doing differently. But for ME Stable Magisk 26.1 works just as 25.2 did - flawless :cool:

Just use the system update 13 APK.

I've attached it, it'll allow you to not reboot after an installation.
 

Attachments

  • OPLocalUpdate_For_Android13.apk
    3.3 MB · Views: 23
  • Like
Reactions: Nimueh

dladz

Senior Member
Aug 24, 2010
16,010
5,964
Liverpool
Nothing Phone 2
Thx for info, I try install update and flashg boot and is ok.
If you're already rooted just use the system update APK I just posted, grab your updates from oxygen updater...

Install it using the APK, don't reboot.

Open magisk then click install after ota.

If you're not rooted then yes take the full update, extract and patch the boot image then boot it then install directly..

Instructions in the OP.
 

Nimueh

Recognized Contributor
May 19, 2012
3,552
3,274
OnePlus 3
Samsung Galaxy Tab A series
Just use the system update 13 APK.

I've attached it, it'll allow you to not reboot after an installation.
That is what I used. Then I had an option to "local update" under system update. It "unpacked" for a long time, then "verified". After that I had the "Install" button and tapping it immediately made the device reboot 🤷‍♀️

No big deal though, I just patched the boot.img again and flashed it as well as TWRP and was back to normal. It just p*ssed me off that "Install" made the phone reboot without any further confirmation :mad:
 
  • Like
Reactions: dladz

dladz

Senior Member
Aug 24, 2010
16,010
5,964
Liverpool
Nothing Phone 2
That is what I used. Then I had an option to "local update" under system update. It "unpacked" for a long time, then "verified". After that I had the "Install" button and tapping it immediately made the device reboot 🤷‍♀️

No big deal though, I just patched the boot.img again and flashed it as well as TWRP and was back to normal. It just p*ssed me off that "Install" made the phone reboot without any further confirmation :mad:
Ah ok, I avoid the onboard system update, it just does its thing once you commit to installation.

I only use oxygen updater...haven't ever took an onboard update before.
 
  • Like
Reactions: Nimueh

Nimueh

Recognized Contributor
May 19, 2012
3,552
3,274
OnePlus 3
Samsung Galaxy Tab A series
Ah ok, I avoid the onboard system update, it just does its thing once you commit to installation.

I only use oxygen updater...haven't ever took an onboard update before.
Yea - I grabbed the update from Oxygen Updater, then went to System Update, 3-dot menu, Local Update (which is what that apk installed, right?).

Is there a different/better way to do a local update, one that doesn't sneakily reboot lol?
 
  • Like
Reactions: dladz

dladz

Senior Member
Aug 24, 2010
16,010
5,964
Liverpool
Nothing Phone 2
Yea - I grabbed the update from Oxygen Updater, then went to System Update, 3-dot menu, Local Update (which is what that apk installed, right?).

Is there a different/better way to do a local update, one that doesn't sneakily reboot lol?

So avoid the system update within settings/ about / system update.

Use system update as an app within your app drawer.

The app drawer one won't reboot.
 

Nimueh

Recognized Contributor
May 19, 2012
3,552
3,274
OnePlus 3
Samsung Galaxy Tab A series
So avoid the system update within settings/ about / system update.

Use system update as an app within your app drawer.

The app drawer one won't reboot.
Well I'll be damned LOL ... nobody told me there'd be a new app in the drawer and I just assumed the new "local update" entry in settings/system update was what I wanted!

Thank you so much - I'll try my luck with that one next time ... unless I've switched to a custom rom by then since OOS 13 is utter crap lol :sick:
 
  • Haha
Reactions: dladz

dladz

Senior Member
Aug 24, 2010
16,010
5,964
Liverpool
Nothing Phone 2
Well I'll be damned LOL ... nobody told me there'd be a new app in the drawer and I just assumed the new "local update" entry in settings/system update was what I wanted!

Thank you so much - I'll try my luck with that one next time ... unless I've switched to a custom rom by then since OOS 13 is utter crap lol :sick:
Haha no worries man, it'd be nice if it modded the system UI but alas we're stuck with an app I'm afraid..

Lol least you're good to go now.

😂 All good man

PS: custom ROMs, lol what are they? There's not a single one on the 10 pro...we can root etc but very little else.
 
  • Like
Reactions: Nimueh

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    UNPATCHED/STOCK boot for OP8 Pro OOS 13.1.0.582(EX01) (EU):
    1
    It was an error on naming it. I always copy the name of the previous to keep the pattern, but forgot to correct the version. My bad.

    It is the 582, assured.

    EDIT: replaced with the correct name.
  • 53
    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

    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:

    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 -

    Oxygen OS 11.0.3.3 - EU IN11BA -IN2023 Patched boot.img -

    Oxygen OS 11.0.4.4 - EU IN11BA -IN2023 Stock boot.img -

    Oxygen OS 11.0.4.4 - EU IN11BA -IN2023 Patched boot.img -

    Oxygen OS 11.0.5.5 - EU IN11BA -IN2023 Stock boot.img -

    Oxygen OS 11.0.5.5 - EU IN11BA -IN2023 Patched boot.img -

    Oxygen OS 11.0.6.6 - EU IN11BA -IN2023 Stock boot.img -

    Oxygen OS 11.0.6.6 - EU IN11BA -IN2023 Patched boot.img -

    Oxygen OS 11.0.7.7 - EU IN11BA -IN2023 Stock boot.img

    Oxygen OS 11.0.7.7 - EU IN11BA -IN2023 Patched boot.img

    Oxygen OS 11.0.8.8 - EU IN11BA -IN2023 Stock boot.img

    Oxygen OS 11.0.8.8 - EU IN11BA -IN2023 Patched boot.img

    Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Stock boot.img

    Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Patched boot.img

    Oxygen OS 11.0.10.10 - EU IN11BA -IN2023 Stock boot.img

    Oxygen OS 11.0.10.10 - EU IN11BA -IN2023 Patched boot.img

    Oxygen OS 11.0.11.11 EU IN11BA - IN2023
    Stock boot.img

    Oxygen OS 11.0.11.11 EU IN11BA - IN2023
    Patched boot.img


    Android 12 11.C.15 - Stock and patched images from. @tfae

    6
    Stock Boot Image
    Stock DTBO Image
    Magisk PATCHED Boot Image

    Happy unbricking :)

    OOS 11.0.8.8 BA version(Europe), my device is IN2020
    5
    Hi to everyone, I need your help: I am on oos 10 rooted 10.5.14IN11BA and I want to upgrade to oos11. Under settings-> update I find that the update for my phone is 11.0.8.8 IN11BA. If I want upgrade in this situation I have to follow the 2nd step of tutorial but I have a doubt: after update and no reboot I have to install Magisk in inactive slot(ota update) and reboot, right? There anything else that I have to do? Please answer me, I don't want brick my phone🙏
    Morning.

    Just follow the guide dude, just make sure you're on the latest stable Magisk.

    In short.

    1. Use oxygen updater to obtain a FULL update.

    2. Install the update but DO NOT REBOOT

    3. Open Magisk and click install (top button)

    4. Click install to inactive slot after OTA

    5. Take the reboot

    Done.


    Basically what's happening is you're priming your device with an update, but the slot switch does not really take place until you reboot, due to the fact that you're already rooted you have the ability to pre-load a prepared and patched boot image which is taken when you reboot and stop using the current boot slot.

    Alternatively just take a full update, reboot, then extract the boot image from payload bin and patch it, then open fasboot and boot it and Install directly.

    The first option I've listed is the easiest method, but just be safe in the knowledge that you aren't going to brick your device, that's almost impossible in all honesty..

    Obviously make a back up anyway, but that much should go without saying
    5
    OP UPDATED: 11.0.9.9 stock and patched images

    Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Stock boot.img

    Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Patched boot.img

    Enjoy ;)
    4
    OP UPDATED:

    Stock and patched boot images are both up.

    made with Magisk stable 22.1

    STOCK: https://mega.nz/folder/7J0mWYLL#6jr6SsV44Lz3V0A3QhgM-A

    PATCHED: https://mega.nz/folder/3MUxFSqL#Qsxp4ncferGLn_Oz0VwTZw