[OnePlus 11] qriozum:
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" :))