• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

Fishawy

Senior Member
Mar 26, 2010
3,176
520
Sydney
OnePlus 9 Pro
Haha cheers man,

I don't mind helping out. We've all been there and not all of us had help, so why let others suffer if you've had it happen to you? That's the way I see it anyway.

But cheers it's appreciated ;)

What's up with your phone? If I can help I will man.

Telegram user is just dlads

With an s not a z

PS: need to reinstall it, I barely use it.

Thanks mate.

Basically, kernel flashing gone wrong, flashing stock kernel fails, resetting fails, LOS recovery fails, and now can't even boot to EDL for MSM (instantly goes to bootloader the moment a cable is inserted).

I'll reach out to you after work. Cheers.
 

dladz

Senior Member
Aug 24, 2010
13,020
4,092
Liverpool
Huawei Watch 2
OnePlus 8
Thanks mate.

Basically, kernel flashing gone wrong, flashing stock kernel fails, resetting fails, LOS recovery fails, and now can't even boot to EDL for MSM (instantly goes to bootloader the moment a cable is inserted).

I'll reach out to you after work. Cheers.
For kernel just boot a stock or patched boot image. Depending on which ROM you're on..if it's a custom then it'd be that boot image..

Strange how MSM doesn't work.
Idk what happened, but suddenly everything google related is updating right now, can't complain I guess lol 😂
Nah that's just Google play services doing an update now everything else follows
 
  • Like
Reactions: Arksuga

dladz

Senior Member
Aug 24, 2010
13,020
4,092
Liverpool
Huawei Watch 2
OnePlus 8
Idk if you know why but viper4android doesn't work on my OnePlus 8 pro. Could you please tell me where I should ask for help in xda?? Like in which thread or something?
I've not actually used it but I've certainly heard it mentioned..

I was using a mod a little while back on Evo X before my last full wipe I'll see if I can grab the name of it but the audio was really good.

I suppose in regards to asking about it.. just pop a question in the Q&A section..
 

Arksuga

Member
Sep 20, 2021
33
18
I've not actually used it but I've certainly heard it mentioned..

I was using a mod a little while back on Evo X before my last full wipe I'll see if I can grab the name of it but the audio was really good.

I suppose in regards to asking about it.. just pop a question in the Q&A section..
Okay thanks, I'll ask it on the Q&A section :)
 
  • Like
Reactions: dladz

dladz

Senior Member
Aug 24, 2010
13,020
4,092
Liverpool
Huawei Watch 2
OnePlus 8

Arksuga

Member
Sep 20, 2021
33
18

gsser

Senior Member
Dec 22, 2012
1,339
531
Eskisehir
OnePlus 5T
OnePlus 8 Pro
Thanks mate.

Basically, kernel flashing gone wrong, flashing stock kernel fails, resetting fails, LOS recovery fails, and now can't even boot to EDL for MSM (instantly goes to bootloader the moment a cable is inserted).

I'll reach out to you after work. Cheers.
Try downgrade zip from oos repo thread. It works most of the time if msm doesnt fix. Someone was having crashdumps after getting on coloros to oos again. He fixed it by flashing downgrade oos zip from stock recovery when msm didnt fix his issue.
 

gsser

Senior Member
Dec 22, 2012
1,339
531
Eskisehir
OnePlus 5T
OnePlus 8 Pro
Idk if you know why but viper4android doesn't work on my OnePlus 8 pro. Could you please tell me where I should ask for help in xda?? Like in which thread or something?
Put these commands at /data/adb/modules/v4a folder. Edit the post fs data.sh file. Then save it. Reboot and enable legacy mode in v4a settings.

#!/system/bin/sh
# Kill audioserver PID if it was initialized already
SERVERPID=$(pidof audioserver)
[ "$SERVERPID" ] && kill $SERVERPID
magiskpolicy --live 'allow audioserver audioserver_tmpfs file { read write execute }'
magiskpolicy --live 'allow audioserver system_file file { execmod }'
magiskpolicy --live 'allow mediaserver mediaserver_tmpfs file { read write execute }'
magiskpolicy --live 'allow mediaserver system_file file { execmod }'
magiskpolicy --live 'allow audioserver unlabeled file { read write execute open getattr }'
magiskpolicy --live 'allow hal_audio_default hal_audio_default process { execmem }'
magiskpolicy --live 'allow hal_audio_default hal_audio_default_tmpfs file { execute }'
magiskpolicy --live 'allow hal_audio_default audio_data_file dir { search }'
magiskpolicy --live 'allow app app_data_file file { execute_no_trans }'
magiskpolicy --live 'allow mtk_hal_audio mtk_hal_audio_tmpfs file { execute }'
 
  • Like
Reactions: Arksuga and dladz

MR0808

Senior Member
Sep 13, 2010
68
4
Melbourne
Hi All,

I was rooted on 11.0.7.7IN11AA I did the OTA update for 11.0.8.8 and then went into Magisk and tried the install on inactive slot. This caused my phone not to boot, just hang in the boot image. I managed to get the stock boot image back, and have my phone running again fine, except it isn't rooted.

I have tried boot with the patched boot img (my phone is 11.0.8.8.IN11AA and I've grabbed the right one from another thread.) and it just hangs on boot and won't load. I have to reboot with stock boot to get my phone running again. Not sure how to debug or work out what is happening.

I've read about modules with Magisk etc, but not sure how to remove them or start again. Any hints would be greatly appreciated.

TIA
 

dladz

Senior Member
Aug 24, 2010
13,020
4,092
Liverpool
Huawei Watch 2
OnePlus 8
Hi All,

I was rooted on 11.0.7.7IN11AA I did the OTA update for 11.0.8.8 and then went into Magisk and tried the install on inactive slot. This caused my phone not to boot, just hang in the boot image. I managed to get the stock boot image back, and have my phone running again fine, except it isn't rooted.

I have tried boot with the patched boot img (my phone is 11.0.8.8.IN11AA and I've grabbed the right one from another thread.) and it just hangs on boot and won't load. I have to reboot with stock boot to get my phone running again. Not sure how to debug or work out what is happening.

I've read about modules with Magisk etc, but not sure how to remove them or start again. Any hints would be greatly appreciated.

TIA


The OP has a guide on how to remove modules using ADB.

This is it:

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.

Otherwise a safe mode boot will disable Magisk from being used until next boot.

Also don't flash the boot image, just boot it.

fastboot boot (name of image)

Also make sure you are patching it with stable Magisk not beta nor Canary..

If it fails to boot up after the fastboot command then obtain another boot image and re-patch it.

Should be fine then.

PS: ideally you want to stick with full updates (if available) not OTA's, I'd recommend oxygen updater for that reason.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    OP UPDATED: Boot images for 8.8

    sorry they're late, better late than never.
    2
    Hi All,

    I was rooted on 11.0.7.7IN11AA I did the OTA update for 11.0.8.8 and then went into Magisk and tried the install on inactive slot. This caused my phone not to boot, just hang in the boot image. I managed to get the stock boot image back, and have my phone running again fine, except it isn't rooted.

    I have tried boot with the patched boot img (my phone is 11.0.8.8.IN11AA and I've grabbed the right one from another thread.) and it just hangs on boot and won't load. I have to reboot with stock boot to get my phone running again. Not sure how to debug or work out what is happening.

    I've read about modules with Magisk etc, but not sure how to remove them or start again. Any hints would be greatly appreciated.

    TIA


    The OP has a guide on how to remove modules using ADB.

    This is it:

    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.

    Otherwise a safe mode boot will disable Magisk from being used until next boot.

    Also don't flash the boot image, just boot it.

    fastboot boot (name of image)

    Also make sure you are patching it with stable Magisk not beta nor Canary..

    If it fails to boot up after the fastboot command then obtain another boot image and re-patch it.

    Should be fine then.

    PS: ideally you want to stick with full updates (if available) not OTA's, I'd recommend oxygen updater for that reason.
    2
    OP UPDATE: Reworked order of guides.

    8.8 images incoming. Sorry it's taken so long.
    2
    Idk if you know why but viper4android doesn't work on my OnePlus 8 pro. Could you please tell me where I should ask for help in xda?? Like in which thread or something?
    Put these commands at /data/adb/modules/v4a folder. Edit the post fs data.sh file. Then save it. Reboot and enable legacy mode in v4a settings.

    #!/system/bin/sh
    # Kill audioserver PID if it was initialized already
    SERVERPID=$(pidof audioserver)
    [ "$SERVERPID" ] && kill $SERVERPID
    magiskpolicy --live 'allow audioserver audioserver_tmpfs file { read write execute }'
    magiskpolicy --live 'allow audioserver system_file file { execmod }'
    magiskpolicy --live 'allow mediaserver mediaserver_tmpfs file { read write execute }'
    magiskpolicy --live 'allow mediaserver system_file file { execmod }'
    magiskpolicy --live 'allow audioserver unlabeled file { read write execute open getattr }'
    magiskpolicy --live 'allow hal_audio_default hal_audio_default process { execmem }'
    magiskpolicy --live 'allow hal_audio_default hal_audio_default_tmpfs file { execute }'
    magiskpolicy --live 'allow hal_audio_default audio_data_file dir { search }'
    magiskpolicy --live 'allow app app_data_file file { execute_no_trans }'
    magiskpolicy --live 'allow mtk_hal_audio mtk_hal_audio_tmpfs file { execute }'
    1
    Thank you for this.

    This worked and I'm rooted again.

    Also, I misunderstood the terminology, byt OTA I did mean using Oxygen Updater.

    Thank you again
    AHH I see, Yea an OTA could be different, signifies 'over the air'

    If it's from OnePlus they're usually incremental, whereas you can grab them from oxygen as you did and it'll be a full, always go for the latter.

    Glad you're all sorted

    👍
  • 40
    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)



    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#SnssRugbc0sELF0ajSAEXg

    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
    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
    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
    4
    Have had a taste of the custom ROM's on the Oneplus device's.

    Bottom line is this:

    Pro's

    Superior OS
    Faster OS
    Ridiculous amount of options
    CRT (sweet jesus why did they ever remove this animation)
    Epic amount of options and tweaks
    You get to use Gcam (yay, sort of)

    Cons

    Truly HORRIFIC camera support, it utilizes none of the Oneplus' cameras capabilities, and i mean literally NONE!, it's diabolical
    Sub par battery life


    This is my last oneplus device, it's pixel for life now. Apparently they can port the original camera in.

    I need to change up.