How To Guide Root permissions guide for OP11 EU (2449) & backup partition "Persist.img"

[_Johnito_]

@qriozum thank you very much for taking the time for this thorough tutorial. Root and persist.img backup works.

 

[vimal chauhan]

Lots of use when you root OP 11. I can go on and on about issues I am facing. First of all, screen lock is not working, charging stops at 75%, some process feels super slow, and many features of the phone are gone. Will unroot the phone. My OP 11 was boot looping, solved it by flashing the Rom by using fastboot enhance software. Don't have to go to the service center anymore.

 

[vimal chauhan]

Also, you can solve the Netflix and other banking apps not working by installing an app called Island which works in WORK MODE. So all the above apps will work in rooted OP 11.

 

[vimal chauhan]

@qriozum after rooting, my screen lock is not working and phone does not charge above 75%. Do I have to flash persist.img or something?

 

[Svid]

Do we actually need to flash the init_boot.img or it's possible to just boot it?
On the oneplus 10 pro i used to patch the boot.img, temp boot it and did a direct install via Magisk.
Did something changed that we need to patch a different file now and flash it via fastboot?

 

[ChrisFeiveel84]

Do we actually need to flash the init_boot.img or it's possible to just boot it?
On the oneplus 10 pro i used to patch the boot.img, temp boot it and did a direct install via Magisk.
Did something changed that we need to patch a different file now and flash it via fastboot?

Init_boot.ing you can not boot
You uave to flash it

 

[Svid]

Init_boot.ing you can not boot
You uave to flash it

Yea i figured it out by doing some research today.
Any device that shipped with Android 13 out of the box (New devices) have their ramdisk in a seperate partition called init_boot.img and even in Magisk documentation it needs to be flashed as boot and ramdisk now in their own partitions (boot and init_boot)

 

[ChrisFeiveel84]

Yea i figured it out by doing some research today.
Any device that shipped with Android 13 out of the box (New devices) have their ramdisk in a seperate partition called init_boot.img and even in Magisk documentation it needs to be flashed as boot and ramdisk now in their own partitions (boot and init_boot)

No mqgisk only need patched init_boot.img

 

[Svid]

I had an issue here when flashed patched init_boot.
fastboot flash init_boot magisk_XXXXX.img
fastboot reboot

after slow boot and opening magisk app it still showed N\A
Should i next time manually flash it to each slot instead?

 

[ChrisFeiveel84]

I had an issue here when flashed patched init_boot.
fastboot flash init_boot magisk_XXXXX.img
fastboot reboot

after slow boot and opening magisk app it still showed N\A
Should i next time manually flash it to each slot instead?

Fastboot flash init_boot "and the name from patched init_boot.img"

 

[Svid]

Fastboot flash init_boot "and the name from patched init_boot.img"

I know how to use fastboot the problem is that after flashing the patched init_boot magisk still as N\A so i had to use unpatched init_boot, temp boot with patched GSK kernel and using KernelSU grant superuser to magisk and from there to perform a direct install

 

[Muricann]

I'v bought Chinese Oneplus 11 with ColorOS. There was PHB110_11_A.07 version patch that was basic as i understand, after a few hours Upgrade has came from air with patch version is PHB110_11_A.10 and i have sucessfully upgraded my phone to it. Now i need a root for some reasons. The question is should i get my own Init_boot.img from my type of patch but from which one i have to take it? From PHB110_11_A.07 (the basic version which was in my phone when i bought it 1 time) or from this PHB110_11_A.10 patch version which i was updated to ?

 

[ChrisFeiveel84]

I'v bought Chinese Oneplus 11 with ColorOS. There was PHB110_11_A.07 version patch that was basic as i understand, after a few hours Upgrade has came from air with patch version is PHB110_11_A.10 and i have sucessfully upgraded my phone to it. Now i need a root for some reasons. The question is should i get my own Init_boot.img from my type of patch but from which one i have to take it? From PHB110_11_A.07 (the basic version which was in my phone when i bought it 1 time) or from this PHB110_11_A.10 patch version which i was updated to ?

Download the full rom coloros 13 a10
And unpack the payload.bin with payload dumper and you have all images.
Than Patch the init_too.img (form colors 13 a10) with magisk manager and flash the patched image with fastboot

 

[Muricann]

Download the full rom coloros 13 a10
And unpack the payload.bin with payload dumper and you have all images.
Than Patch the init_too.img (form colors 13 a10) with magisk manager and flash the patched image with fastboot

Thank you for your answer Bro. But there is some things that i can't understand, you wrote filename as init_too.img but the author named it as Init_boot.img which one is correct name of the file?
Where i may download the "full rom coloros 13 a10" ?

if it is whether not hard to you, please can you write what should i do and where can i get like
1) Do .....
2) Then Do ..... ?

 

[Muricann]

Is it this file? I mean the "full rom coloros 13 a10" ?

https://support.halabtech.com/index.php?a=downloads&b=file&id=728696

 

[Steps Parku]

You do everything you do according to this guide only at your own responsibility.

There were a lot of contradictory and various complications during the process of rooting the new OnePlus 11 model.
The process described below was performed on my own copy of OnePlus 11 (model EU, CPH2449) with an OTA installed with the number CPH2449_11_A.07.


Necessary:
- Android SDK Platform eg. Android SDK Platform,
- fastboot/adb drivers to the operating system,
- Magisk V25.2 - Magisk,
- payload-dumper-go_1.2.2 and/or fastbbot enhance v1.4.0 - Payload-dumper-Go/Fastboot Enhance,
- OTA CPH2449_11_A.07 package - CPH2449_11_A.07 (Eu) - thnx @ChrisFeiveel84
- safetynet-fix-v2.4.0 - Safety-Net Fix - MOD SafetyNet-Fix_2.4.0-MOD_1.2 (Displax)


Here is the whole process of obtaining a root after which there are no problems with the automatic brightness of the screen, changing the color of the display, setting PIN/fingerprints/Facial unlock:

A. Factory Reset:

1. Complete reset for factory settings,​

B. Unlocking bootloader:

2. After launching, the basic configuration without setting locks, logging in to the Google account,​

3. Turn on the programmer's options (click 7 times in the "Compilation number" field in the "device information/version" section),​

3. Go to "Additional settings/programmer options" enable "USB debugging" and connect a USB cable and agree with remembering the imprint of our computer address,​

4. Being still in "Additional Settings/Programmer Options" Turn on "OEM blocking",​

5. We run the CMD console in the system from the "Android SDK Platform" directory,,​

6. In the console window, enter:​

7. Just in case, we check whether the controller works correctly by entering the command in CMD:​

After completing the command, it should be displayed:​

8. Now it remains only to unlock the bootloader by entering the command in CMD:​

Now information about the consistency of unlocking will be displayed on the OP11 screen, there are two options at the bottom of the screen:​

- resignation from unlocking and the second about starting unlocking. We make the choice of calm volume. We use the "Power" key for approval.​

9. After unlocking the bootloader in the CMD window, the status will be displayed:​

10. Now only restart is left. Remember that it may take a while!​

You will see text information on the start screen that the device has no integrity (or something similar).​

C. First start after unlocking the bootloader:

11. After launching, the basic configuration without setting locks, logging in to the Google account,​

12. Turn on the programmer's options (click 7 times in the "Compilation number" field in the "device information/version" section),​

13. Go to "Additional settings/programmer options" enable "USB debugging" and connect a USB cable and agree with remembering the imprint of our computer address,​

D. Preparation for rooting:

14. We copy a file called "payload.bin" to the Payload-Dumper directory from our Ota archive,​

16. In the open command line window in the "Payload-Dumper" directory, enter the command:​

there will be a process of extraction of partition images, which will be presented in the CMD window,​

17. After the process is completed in the Payload-Dumper catalog, a subdirectory called "extracted_data unpacking" was created,​

18. In this subdirectory we find a file called "Init_boot.img" and copy it to the catalog with "Android SDK Platform",​

19. You can close the CMD window with payload-dumper,​

20. Copy the "Init_boot.img" file from the computer to our OP11 is the best for the main memory catalog or to the Download subdirectory on OP11,​

21. We copy the Magisk installation file from the computer to our OP11,​

22. In OP11 we install "Magisk V25.2",​

23. After installing, we run Magisk and in the upper right corner we will see the "Install" field, click it and select the only "Select and Patched File" option,,​

24. We indicate the file that we copied to the OP11 called "Init_boot.img" - the process of its patch by Magisk will begin,​

25. After the process is completed in the "Download" subdirectory, a modified file was created called more or less such "magisk_patched_25200_xxxx.img",​

26. We copy this file to our hard disk for the "Android SDK Platform" directory,​

E. Starting root:

27. In the CMD console opened in the "Android SDK Platform" catalog, enter:​

We check the correctness of the connection and drivers by entering:​

After completing the command, it should be displayed:​

28. Now the key moment, we flash the dealing init_boot by entering the command in a dollar CMD window:​

29. The status of the process should be displayed:​

30. Make a restart by entering the command:​

Remember that it may take a while!​

You will see text information on the start screen that the device has no integrity (or something similar).​

F. First launch after obtaining root:

31. After starting OP11, we check if it went properly. We run "Magisk" and in the upper part there should be the status that Ramdisk is enabled.​

It is recommended to include in the "magciscus" options "zygisk" and "forcing the refusal list".​

After turning it on, "Set the refusal list" will be activated and after selecting it will be displayed a list of installed applications, click in the upper corner​

Three dots and select "System applications". Press the applications that we intend to use and which are "allergic" for root (e.g. banking applications, proximity payments).​

32. Make a reboot from the "Magisk" level,​

G. Final configuration:

33. After starting OP11, you can easily set and turn on PIN/Pattern/fingerprints/Facial unlock.​

It also works without any problems automatically set screen brightness, change of color mode​

H. Hiding "Magisk":

34. In Magisk options, select "Hide Magisk applications",​

35. A prompt for permission will be displayed for installation,​

36. We give our name of the "Magisk" application.​

I. Safety-Net Fix:

37. In "Magisk" we enter the "Modules" section,​

38. We indicate the archive "SafetyNet-Fix-V2.4.0" and after loading the module from the "Magisk" level we make a reboot.​

J. Copy of security of the "Persist" partition:

39. In the opened CMD window launched in the "Android SDK Platform" catalog, enter:​

We will then enter the shell op11 shell and we will have a similar sign of encouragement:​

Now we simply enter the command:​

The OP11 screen will display a prompt for granting root - we accept, after that, the console will change the sign with "$" to "#", meaning:​

40. Now we will make a copy of the "Persist.img" partition by entering the command:​

After completing the command, the state will be returned:​

41. We can enter the exit and simply closing the CMD console window.​

42. Now you should copy to your hard disk and/or in your cloud image file "Persist.img" partitions from the memory of our OP11.​

​

​

​

​

State on 2023.02.17:
The official script "SafetyNet-Fix_2.4.0" despite the fact that it goes through all integrity tests, you can't add your cards to the "Google wallet".
The situation is changed by the mod of this script by Displax:
SafetyNet-Fix_2.4.0-MOD_1.2

Now cards added to the "Google wallet" )

did everything but stuck in boot loop

 

[Steps Parku]

You do everything you do according to this guide only at your own responsibility.

There were a lot of contradictory and various complications during the process of rooting the new OnePlus 11 model.
The process described below was performed on my own copy of OnePlus 11 (model EU, CPH2449) with an OTA installed with the number CPH2449_11_A.07.


Necessary:
- Android SDK Platform eg. Android SDK Platform,
- fastboot/adb drivers to the operating system,
- Magisk V25.2 - Magisk,
- payload-dumper-go_1.2.2 and/or fastbbot enhance v1.4.0 - Payload-dumper-Go/Fastboot Enhance,
- OTA CPH2449_11_A.07 package - CPH2449_11_A.07 (Eu) - thnx @ChrisFeiveel84
- safetynet-fix-v2.4.0 - Safety-Net Fix - MOD SafetyNet-Fix_2.4.0-MOD_1.2 (Displax)


Here is the whole process of obtaining a root after which there are no problems with the automatic brightness of the screen, changing the color of the display, setting PIN/fingerprints/Facial unlock:

A. Factory Reset:

1. Complete reset for factory settings,​

B. Unlocking bootloader:

2. After launching, the basic configuration without setting locks, logging in to the Google account,​

3. Turn on the programmer's options (click 7 times in the "Compilation number" field in the "device information/version" section),​

3. Go to "Additional settings/programmer options" enable "USB debugging" and connect a USB cable and agree with remembering the imprint of our computer address,​

4. Being still in "Additional Settings/Programmer Options" Turn on "OEM blocking",​

5. We run the CMD console in the system from the "Android SDK Platform" directory,,​

6. In the console window, enter:​

7. Just in case, we check whether the controller works correctly by entering the command in CMD:​

After completing the command, it should be displayed:​

8. Now it remains only to unlock the bootloader by entering the command in CMD:​

Now information about the consistency of unlocking will be displayed on the OP11 screen, there are two options at the bottom of the screen:​

- resignation from unlocking and the second about starting unlocking. We make the choice of calm volume. We use the "Power" key for approval.​

9. After unlocking the bootloader in the CMD window, the status will be displayed:​

10. Now only restart is left. Remember that it may take a while!​

You will see text information on the start screen that the device has no integrity (or something similar).​

C. First start after unlocking the bootloader:

11. After launching, the basic configuration without setting locks, logging in to the Google account,​

12. Turn on the programmer's options (click 7 times in the "Compilation number" field in the "device information/version" section),​

13. Go to "Additional settings/programmer options" enable "USB debugging" and connect a USB cable and agree with remembering the imprint of our computer address,​

D. Preparation for rooting:

14. We copy a file called "payload.bin" to the Payload-Dumper directory from our Ota archive,​

16. In the open command line window in the "Payload-Dumper" directory, enter the command:​

there will be a process of extraction of partition images, which will be presented in the CMD window,​

17. After the process is completed in the Payload-Dumper catalog, a subdirectory called "extracted_data unpacking" was created,​

18. In this subdirectory we find a file called "Init_boot.img" and copy it to the catalog with "Android SDK Platform",​

19. You can close the CMD window with payload-dumper,​

20. Copy the "Init_boot.img" file from the computer to our OP11 is the best for the main memory catalog or to the Download subdirectory on OP11,​

21. We copy the Magisk installation file from the computer to our OP11,​

22. In OP11 we install "Magisk V25.2",​

23. After installing, we run Magisk and in the upper right corner we will see the "Install" field, click it and select the only "Select and Patched File" option,,​

24. We indicate the file that we copied to the OP11 called "Init_boot.img" - the process of its patch by Magisk will begin,​

25. After the process is completed in the "Download" subdirectory, a modified file was created called more or less such "magisk_patched_25200_xxxx.img",​

26. We copy this file to our hard disk for the "Android SDK Platform" directory,​

E. Starting root:

27. In the CMD console opened in the "Android SDK Platform" catalog, enter:​

We check the correctness of the connection and drivers by entering:​

After completing the command, it should be displayed:​

28. Now the key moment, we flash the dealing init_boot by entering the command in a dollar CMD window:​

29. The status of the process should be displayed:​

30. Make a restart by entering the command:​

Remember that it may take a while!​

You will see text information on the start screen that the device has no integrity (or something similar).​

F. First launch after obtaining root:

31. After starting OP11, we check if it went properly. We run "Magisk" and in the upper part there should be the status that Ramdisk is enabled.​

It is recommended to include in the "magciscus" options "zygisk" and "forcing the refusal list".​

After turning it on, "Set the refusal list" will be activated and after selecting it will be displayed a list of installed applications, click in the upper corner​

Three dots and select "System applications". Press the applications that we intend to use and which are "allergic" for root (e.g. banking applications, proximity payments).​

32. Make a reboot from the "Magisk" level,​

G. Final configuration:

33. After starting OP11, you can easily set and turn on PIN/Pattern/fingerprints/Facial unlock.​

It also works without any problems automatically set screen brightness, change of color mode​

H. Hiding "Magisk":

34. In Magisk options, select "Hide Magisk applications",​

35. A prompt for permission will be displayed for installation,​

36. We give our name of the "Magisk" application.​

I. Safety-Net Fix:

37. In "Magisk" we enter the "Modules" section,​

38. We indicate the archive "SafetyNet-Fix-V2.4.0" and after loading the module from the "Magisk" level we make a reboot.​

J. Copy of security of the "Persist" partition:

39. In the opened CMD window launched in the "Android SDK Platform" catalog, enter:​

We will then enter the shell op11 shell and we will have a similar sign of encouragement:​

Now we simply enter the command:​

The OP11 screen will display a prompt for granting root - we accept, after that, the console will change the sign with "$" to "#", meaning:​

40. Now we will make a copy of the "Persist.img" partition by entering the command:​

After completing the command, the state will be returned:​

41. We can enter the exit and simply closing the CMD console window.​

42. Now you should copy to your hard disk and/or in your cloud image file "Persist.img" partitions from the memory of our OP11.​

​

​

​

​

State on 2023.02.17:
The official script "SafetyNet-Fix_2.4.0" despite the fact that it goes through all integrity tests, you can't add your cards to the "Google wallet".
The situation is changed by the mod of this script by Displax:
SafetyNet-Fix_2.4.0-MOD_1.2

Now cards added to the "Google wallet" )

C:\Users\DJ STEPS\Desktop\ONEPLUS 11\WHEN STUCK IN BOOT LOOP\platform-tools_r34.0.1-windows\platform-tools>fastboot flash init_magisk_patched.img
unknown partition 'init_magisk_patched.img'
fastboot: error: cannot determine image filename for 'init_magisk_patched.img'

After i fixed my bootloop, issue, this is what i keep getting while flashing the init patched file. i am on A.08 could that be the reason?

 

[Steps Parku]

Hi,
i did exactly what you wrote before. (not my first device rooting. Also had Opo9P etc)

But by mistake, i did instead of

fastboot flash init_boot magisk_patched_25200_xxxx.img

->

fastboot boot magisk_patched_25200_xxxx.img


Now the device constantly restarts with the Oneplus logo, and does not show the yellow text of an unlocked bootloader.
After that, i did:

fastboot flash init_boot magisk_patched_25200_xxxx.img

-> was successfull, but still bootloop.

I'm able to enter bootloader.
Will

fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash init_boot_a init_boot.img
fastboot flash init_boot_b init_boot.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img

Help reactivating the device?
Thanks

have u been able to fix this?

 

[MrSteelX]

C:\Users\DJ STEPS\Desktop\ONEPLUS 11\WHEN STUCK IN BOOT LOOP\platform-tools_r34.0.1-windows\platform-tools>fastboot flash init_magisk_patched.img
unknown partition 'init_magisk_patched.img'
fastboot: error: cannot determine image filename for 'init_magisk_patched.img'

After i fixed my bootloop, issue, this is what i keep getting while flashing the init patched file. i am on A.08 could that be the reason?

Fastboot flash init_boot init_magisk_patched.img

 

[d1nd141]

have u been able to fix this?

Nope, returned the device, and cancelled order.