WARNING: DO NOT ATTEMPT TO USE THE BOOT.IMG ON ANY DEVICE OR FIRMWARE VERSION EXCEPT THE ONE STATED!!! IT WILL MOST LIKELY RESULT IN A SOFT BRICK/BOOTLOOP!
Hello everyone,
Today my Xiaomi Mi 11 received its MIUI 12.5 OTA update. I snagged the OTA update and extracted the boot.img from the payload.bin. Thought I would save you all some trouble since the Rom can currently not be downloaded online (c.miui, etc). If you need any of the other files, let me know. I already have 12.5.1.0 installed on mine with Magisk working.
Device: Xiaomi Mi 11 (VENUS)
MIUI: 12.5.1.0 (RKBMIXM) - Global Rom
If you need it for a different xiaomi device/variant:
Snagging the OTA
Start update in Updater.
Use a file explorer and go to the "Download" folder. There should be a folder named "downloaded_rom" go into it.
Wait for OTA to download, it will start the "updating" phase and will say "updating" instead of "downloading." Copy the zip that is in the "downloaded_rom" folder somewhere else.
Now you have the OTA rom.
** This has to be done during the updating phase since the folder is deleted, otherwise.
Extracting the boot.img
Copy rom zip to a PC (Windows)
Extract .zip
Download and Extract the Payload Dumper Tool from here: Payload Dumper Tool (make sure you have Python Installed)
Copy the Payload.Bin and Payload.Properties files to the extracted payload dumper tool folder.
Click Shift+Right-Click in the folder with Payload_Dumper.py file and the Payload files in it. Select the option to open Powershell
Type "python -m pip install protobuf" and hit enter. Let it install.
Type "python payload_dumper.py payload.bin" and hit enter.
Now you should have the boot.img file.
iamrance.asa said:
AVISO: NÃO TENTE USAR O BOOT.IMG EM QUALQUER DISPOSITIVO OU VERSÃO DE FIRMWARE, EXCETO O INDICADO !!! PROVÁVEL RESULTARÁ EM UM TIJOLO MACIO / BOOTLOOP!
Olá a todos,
Hoje meu Xiaomi Mi 11 recebeu sua atualização MIUI 12.5 OTA. Eu peguei a atualização OTA e extraí o boot.img do payload.bin. Pensei em poupar alguns problemas para vocês, já que a ROM atualmente não pode ser baixada online (c.miui, etc). Se você precisar de qualquer um dos outros arquivos, me avise. Já tenho 12.5.1.0 instalado no meu com Magisk funcionando.
Dispositivo: Xiaomi Mi 11 (VENUS)
MIUI: 12.5.1.0 (RKBMIXM) - Rom global
Click to expand...
Click to collapse
Works with version EEA?
g0mes1 said:
Works with version EEA?
Click to expand...
Click to collapse
It's not pulled from it but if you want to try, you can use "fastboot boot " then the location of where you downloaded the boot.img. If it doesn't work, then you can just restart the phone and it will boot with the oem boot.img. If it does work, then you should patch it in magisk and use the "fastboot boot" command with the patched img, then "direct install" with magisk manager. That's the safest method to use it on the EEA ROM since this is from the Global ROM.
iamrance.asa said:
WARNING: DO NOT ATTEMPT TO USE THE BOOT.IMG ON ANY DEVICE OR FIRMWARE VERSION EXCEPT THE ONE STATED!!! IT WILL MOST LIKELY RESULT IN A SOFT BRICK/BOOTLOOP!
Hello everyone,
Today my Xiaomi Mi 11 received its MIUI 12.5 OTA update. I snagged the OTA update and extracted the boot.img from the payload.bin. Thought I would save you all some trouble since the Rom can currently not be downloaded online (c.miui, etc). If you need any of the other files, let me know. I already have 12.5.1.0 installed on mine with Magisk working.
Device: Xiaomi Mi 11 (VENUS)
MIUI: 12.5.1.0 (RKBMIXM) - Global Rom
Click to expand...
Click to collapse
Hi,
Where did you find the OTA update file?
Want to update my EEA but need the boot.img to patch with Magisk after updating.
Thanks in advance!
rippledrums said:
Hi,
Where did you find the OTA update file?
Want to update my EEA but need the boot.img to patch with Magisk after updating.
Thanks in advance!
Click to expand...
Click to collapse
When you download in Updater, it is stored in /sdcard/download/downloaded_rom but it deletes itself so you'll need to grab it while it's in the updating phase.
iamrance.asa said:
WARNING: DO NOT ATTEMPT TO USE THE BOOT.IMG ON ANY DEVICE OR FIRMWARE VERSION EXCEPT THE ONE STATED!!! IT WILL MOST LIKELY RESULT IN A SOFT BRICK/BOOTLOOP!
Hello everyone,
Today my Xiaomi Mi 11 received its MIUI 12.5 OTA update. I snagged the OTA update and extracted the boot.img from the payload.bin. Thought I would save you all some trouble since the Rom can currently not be downloaded online (c.miui, etc). If you need any of the other files, let me know. I already have 12.5.1.0 installed on mine with Magisk working.
Device: Xiaomi Mi 11 (VENUS)
MIUI: 12.5.1.0 (RKBMIXM) - Global Rom
If you need it for a different xiaomi device/variant:
Snagging the OTA
Start update in Updater.
Use a file explorer and go to the "Download" folder. There should be a folder named "downloaded_rom" go into it.
Wait for OTA to download, it will start the "updating" phase and will say "updating" instead of "downloading." Copy the zip that is in the "downloaded_rom" folder somewhere else.
Now you have the OTA rom.
** This has to be done during the updating phase since the folder is deleted, otherwise.
Extracting the boot.img
Copy rom zip to a PC (Windows)
Extract .zip
Download and Extract the Payload Dumper Tool from here: Payload Dumper Tool (make sure you have Python Installed)
Copy the Payload.Bin and Payload.Properties files to the extracted payload dumper tool folder.
Click Shift+Right-Click in the folder with Payload_Dumper.py file and the Payload files in it. Select the option to open Powershell
Type "python -m pip install protobuf" and hit enter. Let it install.
Type "python payload_dumper.py payload.bin" and hit enter.
Now you should have the boot.img file.
Click to expand...
Click to collapse
No matter what I do, I just get this error :
payload_dumper\payload_dumper.py", line 86, in <module>
assert op.type in (op.REPLACE, op.REPLACE_BZ, op.REPLACE_XZ), \
AssertionError: unsupported op
Even tried doing the extraction on my phone using Termux and get the same error. I'm trying to extract boot.img from EEA 12.5.1.0.RKBEUXM OTA ROM.
Sld_Ultra said:
No matter what I do, I just get this error :
payload_dumper\payload_dumper.py", line 86, in <module>
assert op.type in (op.REPLACE, op.REPLACE_BZ, op.REPLACE_XZ), \
AssertionError: unsupported op
Even tried doing the extraction on my phone using Termux and get the same error. I'm trying to extract boot.img from EEA 12.5.1.0.RKBEUXM OTA ROM.
Click to expand...
Click to collapse
That is referring to the type of compression so it could be a number of things. If you have python3 installed (and working), then check the your payload.bin to see if it's healthy (should be around 3GB in size). I wouldn't imagine they'd use a different compression type on it.
iamrance.asa said:
That is referring to the type of compression so it could be a number of things. If you have python3 installed (and working), then check the your payload.bin to see if it's healthy (should be around 3GB in size). I wouldn't imagine they'd use a different compression type on it.
Click to expand...
Click to collapse
Around 3GB?! Okay, you meant extract the boot.img from a full OTA ROM of 12.5.1.0.RKBEUXM. I was using the OTA incremental ROM which is 656MB in size, which I copied from the download folder during it's update phase.
The zip file name was "miui-blockota-venus_eea_global-V12.0.13.0.RKBEUXM-V12.5.1.0.RKBEUXM-9a04415c08-11.0", that I was using. But the full OTA ROM I find for 12.5.1.0.RKBEUXM is stable beta, ctsprofile for safetynet won't pass so I installed the safetynet fix module in magisk. The magisk props module wouldn't work.
Sld_Ultra said:
Around 3GB?! Okay, you meant extract the boot.img from a full OTA ROM of 12.5.1.0.RKBEUXM. I was using the OTA incremental ROM which is 656MB in size, which I copied from the download folder during it's update phase.
The zip file name was "miui-blockota-venus_eea_global-V12.0.13.0.RKBEUXM-V12.5.1.0.RKBEUXM-9a04415c08-11.0", that I was using. But the full OTA ROM I find for 12.5.1.0.RKBEUXM is stable beta, ctsprofile for safetynet won't pass so I installed the safetynet fix module in magisk. The magisk props module wouldn't work.
Click to expand...
Click to collapse
Oh. This is how large the 12.5.1 update was on my phone when I updated with updater. I just pulled it from the downloaded_rom folder from the official update. The payload.bin on it is 3.03GB. I did this because the stable 12.5.1 ROM isn't available online yet.
What should I do, if my device is Poco F2 Pro?
AniTigerRu said:
What should I do, if my device is Poco F2 Pro?
Click to expand...
Click to collapse
Snagging the OTA and unloading the bin should be the same for the Poco F2 Pro. That's if you have a new OTA that isn't available in a full zip yet.
You can check here for full official ROM downloads if it is available. Just make sure you use the right variant if your bootloader isn't unlocked.
Hope some people smarter than me use this as a method of developing some Custom ROMs for our device
Related
Here are all the boot.img and recovery.img of OxygenOS 11.0.0. Since TWRP isn't ready yet, I guess a lot of people need it if they didn't keep their root permissions.
As I only have a EU device I can only provide a patched boot.img for that device. But with the original .img files it should be easy to patch and flash it yourself. To make it clear: boot.img and recovery.img are stock unless said otherwise. They've just been extracted from the payload.bin inside the respective OOS update zip file.
OOS 11.0.0 EU:
boot.img
boot.img (Magisk v22 patched)
recovery.img
OOS 11.0.0 GLOBAL:
boot.img
recovery.img
OOS 11.0.0 INDIA:
boot.img
recovery.img
Please note: I'm not responsible for anything you do to your device. You use these files at your own risk. I will not provide any further .img files nor ask me for patched files. Any contribution with patched boot.img files is welcome of course. Also note although I'm a moderator, this thread is neither official nor in any way more or less trustworthy than any other contribution by other awesome members!
Would I be able to keep my phone rooted with this after updating?
This is very useful
thanks
jman12311 said:
Would I be able to keep my phone rooted with this after updating?
Click to expand...
Click to collapse
No, unless you use the Magisk patched EU version. Otherwise always install the update, then use the Magisk Manager to patch the inactive slot and then (only then!) reboot. Then you'll keep root.
Otherwise use the stock boot.img and patch with Magisk Manager. Then flash the patched image via fastboot. There are plenty of tutorials on XDA
Hi i installed the update already but didn't reboot what is the solution to keep root ?
Janusk22 said:
Hi i installed the update already but didn't reboot what is the solution to keep root ?
Click to expand...
Click to collapse
1. Install Magisk manager app
2. Open the app and choose "Install to inactive slot (After OTA)"
3. Reboot!
already now i have a magisk module who is making bootloop i already have access to adb via recovery how to remove it
Janusk22 said:
already now i have a magisk module who is making bootloop i already have access to adb via recovery how to remove it
Click to expand...
Click to collapse
Use USB debugging and a PC with the code:
Code:
adb wait-for-device shell magisk --remove-modules
If USB debugging isn't enabled, flash the stock boot.img (without root), boot it, enable ADB debugging and allow the connection to the PC. Then flash the patched boot.img and execute the command above
That is assuming you have a OnePlus 7T Pro which doesn't have a decryptable recovery. Otherwise you can simply flash the Magisk uninstaller
But i have a error I think that i cannot write in system
I have always : cannot be accessible
Thanks i just had to run the command when i rebooted
Is just me or GPS takes more time to "fix" satellites?
FSadino said:
Is just me or GPS takes more time to "fix" satellites?
Click to expand...
Click to collapse
Not longer than usual. But I often had GPS fix issues with my 7T Pro where it takes 5-10 minutes despite using A-GPS.
Macusercom said:
Not longer than usual. But I often had GPS fix issues with my 7T Pro where it takes 5-10 minutes despite using A-GPS.
Click to expand...
Click to collapse
I calibrated the A-Gps again, let's see if that was it. Thank you
Hi I was wondering if you could possibly share the android 11 update file I have a Oneplus 7T Pro HD1910 currently on OOS 10.1.14 It would be awesome if you can PM me. I've tried downloading from Oygen Updater it fails at 98% also on XDA forum the download fails. I'd really appreciate it. Thanks
Macusercom said:
As I only have a EU device I can only provide a patched boot.img for that device. But with the original .img files it should be easy to patch and flash it yourself. To make it clear: boot.img and recovery.img are stock unless said otherwise. They've just been extracted from the payload.bin inside the respective OOS update zip file.
Click to expand...
Click to collapse
Hey, could you please share the payload.bin extract procedure?
Ia possible to use this files to back to stock rom from lineageos 18.1? If yes, can someone help me and give me the procedure how to do this?
For all the "EU" and "global" files, I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.
Hello Shark's,
I have managed to get the link for downloading Android 11 OTA.
https://ota-oversea-1256119282.file.myqcloud.com/KLE-H0/20210904132110-klein-deltaota_MK-R-H0_2021-02-02_c0b9b6c8fc.zip
You can update the phone to MR0 from MP4 or MP3 by following the steps below.
1) Copy the downloaded file to Phone Storage
2) Create a new folder called ota on the root of the storage
3) Inside ota folder copy the downloaded zip file
4) Rename the zip to update.zip
5) Go to dialer
6) Enter *#*#1027#*#* code. Thanks to wertus33333
7) Press Local Update and Wait.
In order to Root the Shark 3 with Global Android 11 follow the steps below.
Perquisites
1) Unlocked Bootloader. Follow this guide.
Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix
Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix Greetings fellow Black Shark users! This guide is made for Black Shark 3 Pro Global version, but in theory it should work with any version if the bootloader is...
forum.xda-developers.com
2) Platform tools on Windows or Mac
3) Basic Knowledge and confidence
* All data will be erased so backup before you do anything.
Steps
1) Download this file and extract it.
https://ota-oversea-1256119282.file.myqcloud.com/KLE-H0/20210904132110-klein-deltaota_MK-R-H0_2021-02-02_c0b9b6c8fc.zip
2) Use Payload dumper by ssssut to extract the boot.img from Payload.bin
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
3) Patch boot.img using Magisk.
4) Go to Fastboot
5) Flash the patched boot.img using
fastboot flash boot boot.img
6) Done
if you don't have stock recovery with the exact same version with your ROM (exp. MP4 ROM with MP4 recovery), the 1027 method won't work, it will give error 20 or something.
slashyuz6 said:
if you don't have stock recovery with the exact same version with your ROM (exp. MP4 ROM with MP4 recovery), the 1027 method won't work, it will give error 20 or something.
Click to expand...
Click to collapse
True it won't work but I have solution for that as well but I am afraid the firmware is paid so I won't be able to share here.
Hey man thanks for the sharing this, i was wondering i have the KLEN2110261CN00MR3, it this rom the global one or the CN00MR0?
Thanks in advance
can you share boot.img of S00MR0 ?
Can someone extract boot and recovery?
arjun_m4 said:
Hello Shark's,
I have managed to get the link for downloading Android 11 OTA.
https://ota-oversea-1256119282.file.myqcloud.com/KLE-H0/20210904132110-klein-deltaota_MK-R-H0_2021-02-02_c0b9b6c8fc.zip
You can update the phone to MR0 from MP4 or MP3 by following the steps below.
1) Copy the downloaded file to Phone Storage
2) Create a new folder called ota on the root of the storage
3) Inside ota folder copy the downloaded zip file
4) Rename the zip to update.zip
5) Go to dialer
6) Enter *#*#1027#*#* code. Thanks to wertus33333
7) Press Local Update and Wait.
In order to Root the Shark 3 with Global Android 11 follow the steps below.
Perquisites
1) Unlocked Bootloader. Follow this guide.
Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix
Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix Greetings fellow Black Shark users! This guide is made for Black Shark 3 Pro Global version, but in theory it should work with any version if the bootloader is...
forum.xda-developers.com
2) Platform tools on Windows or Mac
3) Basic Knowledge and confidence
* All data will be erased so backup before you do anything.
Steps
1) Download this file and extract it.
https://ota-oversea-1256119282.file.myqcloud.com/KLE-H0/20210904132110-klein-deltaota_MK-R-H0_2021-02-02_c0b9b6c8fc.zip
2) Use Payload dumper by ssssut to extract the boot.img from Payload.bin
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
3) Patch boot.img using Magisk.
4) Go to Fastboot
5) Flash the patched boot.img using
fastboot flash boot boot.img
6) Done
Click to expand...
Click to collapse
この方法でboot.imgを抽出しようとしましたが、データが0KBでルートできません。
Mod Edit: English Translation Below
I tried to extract boot.img this way, but the data is 0KB and cannot be rooted.
@natsume.port
Spoiler: English / 英語
Hi! I see that you're new here. Welcome to XDA! Please note that XDA is an international forum, and hence only English is permitted to be used across the website.
The above is as per the Forum Rules:
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Click to expand...
Click to collapse
As a courtesy, I've added the English translation to your post. Going forward, kindly use English to post/reply on the forum.
Regards,
shadowstep
Forum Moderator
Spoiler: Japanese / 日本
こんにちは！ あなたはここで新しいようです。 XDAへようこそ！ XDAは国際フォーラムであるため、Webサイト全体での使用は英語のみに許可されていることに注意してください。
上記はフォーラムルールによるものです。
4。英語を使用してください。
国籍が違うので、英語が上手に話せるわけではないので、ぜひお試しください。 本当に英語で投稿できない場合は、オンライン翻訳者を使用してください。 英語の翻訳の下に、元のメッセージを自国語で自由に含めることができます。 （このルールは、投稿、プロファイルエントリ、および署名を対象としています）。 次のことを試すことができます:- https://translate.google.com/またはhttps://www.babelfish.com/または、いずれかを使用してください。
Click to expand...
Click to collapse
礼儀として、私はあなたの投稿に英語の翻訳を追加しました。 今後は、英語を使用してフォーラムに投稿/返信してください。
よろしく、
shadowstep
フォーラムモデレーター
The update has arrived.
Oh my God! I used the payload dumper to dump recovery.IMG flashed it, then re locked the phone, so I could update it with the OTA. However, afterwards it wouldn't boot, so I unlocked it, and now I'm locked out of my own phone. It says I have to activate it and asks for a password to an account I don't recognize. I've tried everything I can think of I've watched every YouTube video that that deals with this issue sort of, most of which I can't understand and most of them that I can understand are fake. Any thoughts on that? Looks like I'm going to have to buy a new phone.
fayherwingnut said:
Oh my God! I used the payload dumper to dump recovery.IMG flashed it, then re locked the phone, so I could update it with the OTA. However, afterwards it wouldn't boot, so I unlocked it, and now I'm locked out of my own phone. It says I have to activate it and asks for a password to an account I don't recognize. I've tried everything I can think of I've watched every YouTube video that that deals with this issue sort of, most of which I can't understand and most of them that I can understand are fake. Any thoughts on that? Looks like I'm going to have to buy a new phone.
I think Your talking about Mi Account. There is paid service to unlock it.
Click to expand...
Click to collapse
Hi everyone,
How can I get the boot.img (either patched with magisk or clean) for the 13.0.8.0.SKDEUXM (11TPro vili - EEA)?
I've performed an OTA update, patched with magisk 24.1 with the option to "install to inactive slot (after OTA)" and now I can't boot into the device.
This is the process I've followed in previous updates, but this time it hasn't worked.
I've tried changing active slots (A/B) and trying to boot, without any luck.
Many thanks!
FYI, i've extracted boot.img from the recovery file:
https://bigota.d.miui.com/V13.0.8.0.SKDEUXM/miui_VILIEEAGlobal_V13.0.8.0.SKDEUXM_5142aa18f5_12.0.zip
Using those instructions: https://www.droidwin.com/extract-pa...The_Need_to_Extract_payload_bin_File_using_PC
If someone needs the untouched boot.ini 13.0.8.0.SKDEUXM (11TPro vili - EEA) file, just let me know.
I have seen that there are problems after updating to miui 13 with the option to "install to inactive slot (after OTA)". How to do it in good way? I have last time almost bricked my device and i don't want to have same ****ty feeling again...
Did you manage to patch with Magisk and install SafetyNet?
shr3kull said:
FYI, i've extracted boot.img from the recovery file:
https://bigota.d.miui.com/V13.0.8.0.SKDEUXM/miui_VILIEEAGlobal_V13.0.8.0.SKDEUXM_5142aa18f5_12.0.zip
Using those instructions: https://www.droidwin.com/extract-pa...The_Need_to_Extract_payload_bin_File_using_PC
If someone needs the untouched boot.ini 13.0.8.0.SKDEUXM (11TPro vili - EEA) file, just let me know.
Click to expand...
Click to collapse
ciao, i am not able to extract boot.img 13.0.8.0 dispitee i follow the procedure above, could you put the boot.img uou extract here. thanks in advance
Just download a fastboot rom(tgz) the boot img is inside the img folder.
https://xiaomifirmwareupdater.com/miui/vili/stable/V13.0.8.0.SKDEUXM/
Hi all,
Thought i'd share a guide on how to get these boot images 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 NE2213 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:
NE2213_11_A.12
Magisk Manager v24.3 (24300) Stable
NE2213_11_A.13
Magisk Manager v24.3 (24300) Stable
NE2213_11_A.14
Magisk Manager v25 (25000) Stable this version retains root after a restart, more stable version over previous iterations.
NE2213_11_A.16
Magisk Manager v25.2 (25200) Stable
NE2213_11_C_20
Magisk Manager v25.2 (25200) Stable
NE2213_11_C_21
Magisk Manager v25.2 (25200) Stable
NE2213_13.1.0.520 (EX01)
Magisk Manager v26.1 (25200) Stable
Oxygen OS NE2213_13.1.0.521 (EX01)
Magisk Manager v26.1 Stable
1st
Extracting a boot.img using Fastboot Enhance
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.
An unlocked bootloader.
The local System Update Installer : normal local system update will not allow a reboot during installation, the one I've linked will.
Process
On your computer
1. Download and copy the fastboot enhance folder to your desktop or a location of your choosing.
Download from here: https://github.com/libxzr/FastbootEnhance/releases
2. Download the firmware of your choice (always use full zips, not incremental) and open it using Winrar or a similar zip program, extract the file called payload.bin to a folder of your choosing.
3. Run the program FastbootEnhance.exe, a window will appear, click Payload Dumper, then click browse and point to the payload.bin file, the contents of that payload.bin will now be shown, bare in mind you'll need to check the box "Allow incremental" even if it's a full zip
4. One of the files will be called boot.img, this is the file we'll be patching, click extract then 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, do 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 output into the Downloads folder)
You now have a patched boot.img ready to boot or flash to either slot with fastboot or boot via fastboot.
I 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 will 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 it twice but it won't hurt if you do.
2nd
Update from XX stable to XX+ stable whilst retaining root
Guide
**NOTE- Although this may work, the system may be unstable, especially when changing bases, eg: Android 11-12 or 12-13, so if you encounter strange behaviour then a factory wipe is advised.
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. Install the OnePlus local install apk listed below in downloads. 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.
3rd
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.
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 (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.
Bootloader unlock
Boot to the bootloader with adb reboot bootloader
type fastboot flashing unlock
Agree to unlock - allow to boot.
If you can't see the device using ADB
Make sure USB Debugging is turned on
Connect your cable to your phone and computer, when asked what you want your phone to do, click on transfer files, a driver will be installed.
After this reconnect your phone and it'll prompt you with a disclaimer with a check box, check the box and click ok, ADB / Fastboot should now work.
Files:
Local System update APK, this must be used as the local OnePlus 10 Pro one will not allow a reboot during the installation, so you cannot install the Magisk boot image during an upgrade, the android 13 local update apk is also required for rolling back to android 12.
Android 13 local update apk
3.27 MB folder on MEGA
mega.nz
Android 12 local update apk
3.27 MB folder on MEGA
mega.nz
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
Oxygen OS NE2213_11_A.12 Stock boot image
0 byte folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.12 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.13 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.13 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.14 Stock boot image
384 MB folder on MEGA
2 files
mega.nz
Oxygen OS NE2213_11_A.14 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.16 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.16 Patched boot image
192 MB folder on MEGA
mega.nz
Android 13
Oxygen OS NE2213_11_C_20 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_C_20 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_C_21 Stock boot image https://mega.nz/folder/LNVxTDYA#yly9xpjFjQhe4De_jqyzbw
Oxygen OS NE2213_11_C_21 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.520 (EX01) Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.520 (EX01) Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.521 (EX01) Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.521 (EX01) Patched boot image
192 MB folder on MEGA
mega.nz
Glad to see you here bro with the 10 Pro and helpful guide's!!
Cheers
galaxys said:
Glad to see you here bro with the 10 Pro and helpful guide's!!
Cheers
Click to expand...
Click to collapse
Slowly coming around to this phone mate, we desperately need a few custom ROMs..
EvoX on this would be phenomenal.
Nudge nudge @AnierinB
UPDATE: First patched boot image is up, using the latest stable Magisk v24.3 (24300)
dladz said:
Slowly coming around to this phone mate, we desperately need a few custom ROMs..
EvoX on this would be phenomenal.
Nudge nudge @AnierinB
Click to expand...
Click to collapse
Yeh, it's early but hopefully a few Developer's will get this badboy device!
Thank you thank you THAAAANK YOOOOUUUU
meowmeowpewpew said:
Thank you thank you THAAAANK YOOOOUUUU
Click to expand...
Click to collapse
Lol welcome mate
meowmeowpewpew said:
Thank you thank you THAAAANK YOOOOUUUU
Click to expand...
Click to collapse
I honestly hope so..
I'm having a few issues isolating the correct files to make the center clock Magisk mod, but that's in the works. Will have it done soon hopefully.
OnePlus thought it would be a good idea to get rid of OPSystemUI.apk in place of systemui.apk so maybe more in line with stock android. But we'll see
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
dladz said:
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
Click to expand...
Click to collapse
Hey that's great news and something to definitely look forward to!
Cheers
Very happy to see guides! Nice, thank you so much !
dladz said:
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
Click to expand...
Click to collapse
I cannot find that Evo X 10 Pro channel, have you got a link?
kouzelnik3 said:
I cannot find that Evo X 10 Pro channel, have you got a link?
Click to expand...
Click to collapse
If you have telegram just search for evo x up the top, you'll see the main channel.
The the other is in that, i'm just in the middle of something, i'll send it once i'm done.
kouzelnik3 said:
I cannot find that Evo X 10 Pro channel, have you got a link?
Click to expand...
Click to collapse
Evolution X - OnePlus 10 Series
Telegram: Contact @EvolutionXOnePlus10
t.me
Macke93 said:
Evolution X - OnePlus 10 Series
Telegram: Contact @EvolutionXOnePlus10
t.me
Click to expand...
Click to collapse
Oh I've found it.
Hello All,
Very many thanks for your guide. It really helped me root my OP 10 PRO
I was wondering if it is possible to flash my OP ColorOS with OxygenOS EU/UK version you have uploaded?
I copied the 02b0d1b2508744e3a41115aeb274cccf.zip to the root folder and I tried installing via Oxygen Updater using the automatic method, but it fails every time.
If I try installing it manually, I have to download the Oxygen Updater via oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk.zip and rename to .apk. - I then launch System Update , click on settings and it says 'Move installation package into root directory' (which it is).
Have I missed a step?
kouzelnik3 said:
Oh I've found it.
Click to expand...
Click to collapse
Ah was just about to post it mate.
Glad you found it, it's only new but that fact that it's here is brilliant . I'm hoping AnierinB is the dev who makes the rom for the 10.
Lynxy0 said:
Hello All,
Very many thanks for your guide. It really helped me root my OP 10 PRO
I was wondering if it is possible to flash my OP ColorOS with OxygenOS EU/UK version you have uploaded?
I copied the 02b0d1b2508744e3a41115aeb274cccf.zip to the root folder and I tried installing via Oxygen Updater using the automatic method, but it fails every time.
If I try installing it manually, I have to download the Oxygen Updater via oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk.zip and rename to .apk. - I then launch System Update , click on settings and it says 'Move installation package into root directory' (which it is).
Have I missed a step?
Click to expand...
Click to collapse
Honestly mate i'm not sure, you're essentially changing region.
Have you looked into fastboot enhanced?
You can obtain the firmware from oxygen updater (it's 4.15GB the one i uploaded is only the boot image and patched boot image)
Then copy it to your computer and allow it to flash to your phone.
This isn't without risk mate and i've not done this before myself.
dladz said:
Ah was just about to post it mate.
Glad you found it, it's only new but that fact that it's here is brilliant . I'm hoping AnierinB is the dev who makes the rom for the 10.
Click to expand...
Click to collapse
I am hoping too, because in this state oxygen os in this device is bad. Yeah, it is quite new, but hey, it is halfly baked. And not only evo x, but other ROMs I hope will come.
dladz said:
Honestly mate i'm not sure, you're essentially changing region.
Have you looked into fastboot enhanced?
You can obtain the firmware from oxygen updater (it's 4.15GB the one i uploaded is only the boot image and patched boot image)
Then copy it to your computer and allow it to flash to your phone.
This isn't without risk mate and i've not done this before myself.
Click to expand...
Click to collapse
Thanks for your swift reply. I will wait until there is a verified method. For now, I will tread lightly with the rooted version hehe
Pre requisites
• Unlocked Bootloader (probably only Indian variant?)
• ADB and Fastboot drivers (I'm assuming you've set that up since you unlocked bootloader)
• Python (used to extract boot image)
• Your stock rom (I found it here: https://realmefirmware.com/)
• time (need some time to download your stock rom and get a hold of your boot image)
Steps:
1) Download Oppo_Decrypt tool from here:
https://github.com/bkerler/oppo_decrypt
2) Extract the contents and place in a folder
3) go to that folder and open a command prompt/power shell in the folder
4) Use commands accordingly
If you've added pip to path:
pip install -r requirements.txt
If you've not added pip to path:
Python -m pip install -r requirements.txt
done? Everything installed?
now get your rom zip file, inside it you'll find a big .ofp file, extract that ofp file and place in the folder where you've extracted your tools
now inside this very folder where ur tools are, create another folder and name it "extract" (tbh u can name the folder anything you want but for the sake of explanation I named it that)
now open a command prompt in the folder where the tools are kept
type: Python
Press space
drag and drop the "ofp_qc_decrypt.py" file in the command prompt
Press space
Drag and drop the large .ofp file you extracted
Press space
Drag and drop the extract folder
Press enter
Wait for a while till there's a message saying
"Extracting super.img" or something along the lines
Exit out of command prompt
Go to the extract folder you'll see a file called "boot.img"
Send this boot.img file to your phone
(Also recommend keeping a copy of the boot.img on your PC for safety)
Install Magisk Manager Apk from the official website on your phone
Open Magisk manager
Click on Install
Click on select and patch a file
Choose the boot.img file you just sent from your PC
after done send the magisk_patched.img to your PC
Now boot your phone into Fastboot mode
(I'll assume you know how to since you've unlocked bootloader)
Connect your phone to your PC using USB cable
open a command prompt and check if your device is connected by typing:
fastboot devices
if it shows up then proceed
type:
fastboot flash boot magisk_patched.img
(Your file name can be different you can just drag and drop the file)
after it says success, type:
fastboot reboot
after reboot open Magisk manager app (might ask u to download?)
and reboot if it asks you to
Congratulations you now have root access!
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
Spoiler: Video instructions
//seems to work for others, i thought it's only for indian roms, because of other posts and EU was locked out for so long, seems to work for EU, too.
IMEI and Baseband only get lost if you unlock the bootloader with the wrong version or boot.img.
smashda said:
BEWARE:Only Indian variant, you lose your IMEI and Baseband!
Click to expand...
Click to collapse
I test it on RMX3311 EU and work fine.
Deleted
Can we make a boot.IMG for the RMX3311 so we can flash in Magisk ?
Hello,
Is there a easy way to hide banking apps some function don't work because my device is unlocked.
karayemis said:
Can we make a boot.IMG for the RMX3311 so we can flash in Magisk ?
Click to expand...
Click to collapse
It is the same method to extract boot image just get your corresponding rom and either use oppo decrypt tool if on version the phone ships with otherwise use payload dumper with correct ota
karayemis said:
Hello,
Is there a easy way to hide banking apps some function don't work because my device is unlocked.
Click to expand...
Click to collapse
Safetynet fix may help but you need root
BR4UTAL said:
It is the same method to extract boot image just get your corresponding rom and either use oppo decrypt tool if on version the phone ships with otherwise use payload dumper with correct ota
Click to expand...
Click to collapse
Hi,
Thanks, worked for me my device it is rooted now and banking apps are working now.
Device: RMX3311 EU
2 more questions:
1. is there a module i can use to activate call recorder on google dialer ?
2. When there is a new OTA can I just install and repeat all above ?
karayemis said:
2 more questions:
1. is there a module i can use to activate call recorder on google dialer ?
2. When there is a new OTA can I just install and repeat all above ?
Click to expand...
Click to collapse
When there is an ota update download it from software update and wait for it to finish extracting
DO NOT CLICK ON INSTALL
Go into Magisk
Do Uninstall Magisk > Restore System Images
Now Click on Install Magisk > Click Install to Inactive slot (after ota)
click ok and let's go
DO NOT CLICK ON THE REBOOT BUTTON
Now go to software update and click Install, your phone will reboot with root available still and ota update applied
For the model 3311 (EU) is there a step by step guide for root? Please, if exists, drop it here. Thank you
geovision said:
For the model 3311 (EU) is there a step by step guide for root? Please, if exists, drop it here. Thank you
Click to expand...
Click to collapse
The process is the same but instead of IN rom you need to get boot image from EU rom
karayemis said:
Hi,
Thanks, worked for me my device it is rooted now and banking apps are working now.
Device: RMX3311 EU
Click to expand...
Click to collapse
Banking app stops working after a while, this is the second time it stopped working.
karayemis said:
Banking app stops working after a while, this is the second time it stopped working.
Click to expand...
Click to collapse
Here's the Thread for it, you can just use the search on top of the page for things you want to fix, the banking issues come with root and you can find the appropriate Threads when searching for Magisk.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Currently iam on this version rmx3312_11_A.20 of realme ui so how can i get the boot image of this version
_PsyDuck_ said:
Currently iam on this version rmx3312_11_A.20 of realme ui so how can i get the boot image of this version
Click to expand...
Click to collapse
The Ota server only offers the latest version of Android 12 with the A.22 software