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

[forever_omkar]

Same... I had the same issue .. Got new Phone And I did all procedure in OnePlus Store itself the next time. Some OnePlus engineers where staring at me

Lol lol

 

[forever_omkar]

Same... I had the same issue .. Got new Phone And I did all procedure in OnePlus Store itself the next time. Some OnePlus engineers where staring at me

Bro dm me on telegram
I need some help from you! 🥹🥹

Forever_Omkar

 

[forever_omkar]

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" )

hmmm......!
Everything working fine.
but now viper4android is making issue

it's saying driver not found pls install -- again and again
hashhhhhh

for this module i rooted my phn and now it hurted me


any fix for it????????????
I think this happening due to dolby which is pre installed on our phn

 

[ChrisFeiveel84]

hmmm......!
Everything working fine.
but now viper4android is making issue

it's saying driver not found pls install -- again and again
hashhhhhh

for this module i rooted my phn and now it hurted me


any fix for it????????????
I think this happening due to dolby which is pre installed on our phn

No you need an Other driver
Idk the name from the other v4d with the other driver (this is working )

 

[forever_omkar]

If you have it pls send it to me bro

I really want it! 🥹🥹🥹🥹

 

[forever_omkar]

If you have it pls send it to me bro

I really want it! 🥹🥹🥹🥹

 

[sefai77]

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" )

is this safe ?

 

[forever_omkar]

is this safe ?

Yes ofcourse!

 

[forever_omkar]

hmmm......!
Everything working fine.
but now viper4android is making issue

it's saying driver not found pls install -- again and again
hashhhhhh

for this module i rooted my phn and now it hurted me


any fix for it????????????
I think this happening due to dolby which is pre installed on our phn

Anyone have its solution? 🥹🥹🥹

V4a saying while installing drivers that "path not found"
Is it happening because of magisk 26.0???
Or anything else? 🥹🥹🥹

 

[ChrisFeiveel84]

Anyone have its solution? 🥹🥹🥹

V4a saying while installing drivers that "path not found"
Is it happening because of magisk 26.0???
Or anything else? 🥹🥹🥹

No it from v4d is to old and can nit Work with new oos you need an other driver

V4A Working?

has anyone got viper4android working? I try every way I could when using OnePlus 9Pro A11, A12, and A13 where it work. are the partitions different where the post-fs-data.sh file redirects?

forum.xda-developers.com

 

[forever_omkar]

No it from v4d is to old and can nit Work with new oos you need an other driver

V4A Working?

has anyone got viper4android working? I try every way I could when using OnePlus 9Pro A11, A12, and A13 where it work. are the partitions different where the post-fs-data.sh file redirects?

forum.xda-developers.com

You saved my life brother thank you sooooo muchhhhhh
🥹

 

[appileh]

Hi Everyone, do we have also an option to lock bootloader? My device is not ok, so need to go to factory reset and then lock te bootloader.

 

[ChrisFeiveel84]

Hi Everyone, do we have also an option to lock bootloader? My device is not ok, so need to go to factory reset and then lock te bootloader.

When you lock.your bl this wiped your phone
When you look your bl make all stock no root

 

[Spieleckecker]

Hi all, I am looking for advice on updating my CPH2449 EU (A.08) model:

I downloaded the full ROM (A.09) and updated via local update in settings. Then I went to magisk and flashed to other slot. I forgot to deactivate my only magisk module, the safetynet-fix. When rebooting, my phone bootlooped at the OnePlus logo about 6-7 times, then it automatically booted the old slot again.

I now disabled the safetynet-fix module and haven't restarted since. How would you proceed with the update? Just reboot?

Thank you in advance for any advice!

 

[qriozum]

Hi all, I am looking for advice on updating my CPH2449 EU (A.08) model:

I downloaded the full ROM (A.09) and updated via local update in settings. Then I went to magisk and flashed to other slot. I forgot to deactivate my only magisk module, the safetynet-fix. When rebooting, my phone bootlooped at the OnePlus logo about 6-7 times, then it automatically booted the old slot again.

I now disabled the safetynet-fix module and haven't restarted since. How would you proceed with the update? Just reboot?

Thank you in advance for any advice!

After flashing the full OTA update, you do not select "Install now" but go to "Magisk" and in it you do as before - "Installs to inactive slot".
The only difference is that after patching is complete, you do not reboot from "Magisk" but return to the screen from "loading local copy" and on it you select the "Install now" button.

This is how I did the upgrade from A.07 to A.08 and then from A.08 to A.09. It works without having to disable the "SafetyNet-fix" module in magisk.


regards
q.

 

[Spieleckecker]

After flashing the full OTA update, you do not select "Install now" but go to "Magisk" and in it you do as before - "Installs to inactive slot".
The only difference is that after patching is complete, you do not reboot from "Magisk" but return to the screen from "loading local copy" and on it you select the "Install now" button.

This is how I did the upgrade from A.07 to A.08 and then from A.08 to A.09. It works without having to disable the "SafetyNet-fix" module in magisk.


regards
q.

Thank you so much!
I didn't know the "install now" button does something different than rebooting.

Again, you saved my week thank you so much! Hope this helps other people too.

 

[takui]

Hi guys... sorry to bother you (I've asked this on another thread, frankly...idk which one is the most correct)..

I've unlocked the phone but I had the fingerprint still there, so I've the issue now... what I've tried so far:

lock it back, phone goes to inifinite fastboot loop

unlock it, it boot, but with still the issue

I've read here and there that maybe, if I lock it back AND flash the stock, I should be able to boot again with locked phone and so, remove the finger print and start again the process correctly...

my current issue is: I can't find the right way to flash back the stock rom, I've tried fastboot enhanced tool but when I reboot the phone to fastbootD, the phone isn't recognized anymore...

what can I do? I can get access to fastboot or normal system in one partition (the other one has infinite fastbook loop now, idk why frankly).

thx

ps.: if there's a guide with the correct way to flash back the stock, would be nice...also with the correct link...i've dl some roms but from a chinese site so not totally 100% sure they works

 

[surajpai524]

Hi guys... sorry to bother you (I've asked this on another thread, frankly...idk which one is the most correct)..

I've unlocked the phone but I had the fingerprint still there, so I've the issue now... what I've tried so far:

lock it back, phone goes to inifinite fastboot loop

unlock it, it boot, but with still the issue

I've read here and there that maybe, if I lock it back AND flash the stock, I should be able to boot again with locked phone and so, remove the finger print and start again the process correctly...

my current issue is: I can't find the right way to flash back the stock rom, I've tried fastboot enhanced tool but when I reboot the phone to fastbootD, the phone isn't recognized anymore...

what can I do? I can get access to fastboot or normal system in one partition (the other one has infinite fastbook loop now, idk why frankly).

thx

ps.: if there's a guide with the correct way to flash back the stock, would be nice...also with the correct link...i've dl some roms but from a chinese site so not totally 100% sure they works

 

[lassetth]

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

I had the same problem and tested FastbootEnhance, Take a loooooong time.
The tool worked perfect, some reboots but no other problem. Follow the maual carefully and don`t forget to delete the files you get adviced about, before start flashing. The process took a loooooong time to finsh, about 1.5 hours to compete.

https://droidwin.com/how-to-flash-rom-unbrick-oneplus-via-fastboot-enhance-tool/#google_vignette

 

[jim4652000]

Can i use the packages in OP for OTA CPH2449_11_A.07 package to patch the latest CPH2449_11_A.10 (eu) or do i need a different img file?