How To Guide PROPER CPH2451 Root and Update instructions

Search This thread

Philly@52

Senior Member
Feb 6, 2019
114
28
OnePlus 7 Pro
OnePlus 9 Pro
If it isn't too much trouble, what would be the steps to reflash everything back to stock and lock the bootloader.

What I understand is to get my hands on CPH2451-A.06 stock rom, but I'm having a hard time finding what commands I do to flash it.

Just need a dependable phone at this point. Thank you
I think I have a. 09 stock init on my PC. I will check soon
 

Philly@52

Senior Member
Feb 6, 2019
114
28
OnePlus 7 Pro
OnePlus 9 Pro
Android 13
Oxygen OS CPH2451_11_A.09
Here, this thread has some of the stock init_img's including A.09

 

random0munky

Member
Oct 22, 2013
30
1
OnePlus 11
Here, this thread has some of the stock init_img's including A.09

Thank you but I'm looking for boot.img not init_boot.img.
 

random0munky

Member
Oct 22, 2013
30
1
OnePlus 11
Awesome! I'll try that and see if that solves my boot loop issue on slot a
I took a look at page 4 of this thread and was unable to locate the A.09 boot.img file share that you mentioned.

I did find the A.09 boot.img and init_boot.img here on Page 2 by Steve00007:

Rebooted into fastboot
Set current-slot to a
Rebooted into fastboot again
fastboot flash boot boot.img
fastboot flash init_boot init_boot.img
fastboot reboot

The phone is still bootlooping. Can't get passed the 1+ logo screen.
 
Last edited:

Philly@52

Senior Member
Feb 6, 2019
114
28
OnePlus 7 Pro
OnePlus 9 Pro
I took a look at page 4 of this thread and was unable to locate the A.09 boot.img file share that you mentioned.

I did find the A.09 boot.img and init_boot.img here on Page 2 by Steve00007:

Rebooted into fastboot
Set current-slot to a
Rebooted into fastboot again
fastboot flash boot boot.img
fastboot flash init_boot init_boot.img
fastboot reboot

The phone is still bootlooping. Can't get passed the 1+ logo screen.
Hopefully this takes you directly to the post from MrSteelX where he linked the boot.img

 

g96818

Senior Member
Dec 27, 2014
1,006
439
I took a look at page 4 of this thread and was unable to locate the A.09 boot.img file share that you mentioned.

I did find the A.09 boot.img and init_boot.img here on Page 2 by Steve00007:

Rebooted into fastboot
Set current-slot to a
Rebooted into fastboot again
fastboot flash boot boot.img
fastboot flash init_boot init_boot.img
fastboot reboot

The phone is still bootlooping. Can't get passed the 1+ logo screen.
You flashed the wrong version. those are not for this phone. that's why you are bootlooping

Try flash the boot @Philly@52 linked to and this init_boot https://forum.xda-developers.com/t/...t-keep-root-oos-13-a-10.4571171/post-88389617
 
Last edited:

random0munky

Member
Oct 22, 2013
30
1
OnePlus 11
I went ahead and tried flashing the boot.img for A.09 as well as the init_boot.img that @Philly@52 linked above. Still unfortunately boot looping. Feeling a full stock image reflash is in order. Though haven't come across a guide that outlines the steps to flash all.
 

dmarden

Senior Member
Oct 30, 2008
2,083
527
Philadelphia, PA
Pardon me if I am missing anything... I tried to read and search. I am unlocked. Trying to root. I can boot those KernelSU android13 files (I tried android13-5.15.78_2022-05-boot.img.gz and android13-5.15.41_2022-05-boot.img.gz). But the KernelSU app still doesn't pick up any root access to grant Magisk so that it can directly install.

I just got the OnePlus 11 (NA version) and it is fully updated. Should I be booting something else for the temp root?

Edit: Nevermind. It wanted android13-5.15.74_2022-05-boot.img.gz specifically I guess.
 
  • Like
Reactions: g96818

asheroto

Senior Member
Apr 26, 2019
73
18

Yeah so just to clarify, you have to install KernelSU's APK first to get the type of kernel you need, then browse their releases for the associated Kernel image. Then boot to that.

For example, KernelSU shows my kernel is 5.15.41 -android 13-8 so I found that (I just pressed Ctrl+F and searched for 5.15.41). You may have to expand the "assets" with the arrow next to it.
ARzRS6c.jpeg

you just need the .img.gz and extract that with 7-Zip/WinRAR. Then you'll get the boot.img file which you can do

Code:
adb boot boot.img

with.
 
  • Like
Reactions: g96818

asheroto

Senior Member
Apr 26, 2019
73
18
WARNING: You might not be able to set your pin, password, fingerprint, and face unlock due to Oneplus incompetence.

Step 8: Let your phone do it's thing, don't worry about the Orange State warning message after it restarts. This is normal.

Step 9: Set up the phone, but don't waste your time logging into anything until you can successfully set up a pin or password. Skip to Step 11 if you can set up a pin or password. Continue to Step 10 if it hangs up on the second entry.

Step 10: Skip everything, enable USB debugging and reboot back into the bootloader.

This is the annoying part. You need to lock and unlock as many times as it takes for the pin or password setup to work. You might need to toggle the OEM unlocking switch in between lock and unlock cycles.
Use the following to lock the bootloader and then repeat all of Phase 1 and 3 as many times as it takes.

Code:
fastboot flashing lock

Step 11: Go ahead and setup your phone or continue to Phase 4.

Well crap. I missed that part and had already rooted my phone, then locked the phone back. That caused problems since it wouldn't boot the rooted boot image. Couldn't boot at all. So I changed the active slot to the other slot, then I couldn't boot at all, no fastboot, no recovery, only EDL mode. Had to perform MSM recovery.

Working now, but for a few hours I was worried!

It might helps others if you add another red warning that says DON'T SKIP THIS PART!!! or something at the top of the rooting section that says CHECK TO MAKE SURE YOU CAN SET A PASSWORD/PIN BEFORE CONTINUING haha although maybe it would only help me -1 day ago.
 
  • Like
Reactions: g96818

g96818

Senior Member
Dec 27, 2014
1,006
439

Yeah so just to clarify, you have to install KernelSU's APK first to get the type of kernel you need, then browse their releases for the associated Kernel image. Then boot to that.

For example, KernelSU shows my kernel is 5.15.41 -android 13-8 so I found that (I just pressed Ctrl+F and searched for 5.15.41). You may have to expand the "assets" with the arrow next to it.
ARzRS6c.jpeg

you just need the .img.gz and extract that with 7-Zip/WinRAR. Then you'll get the boot.img file which you can do

Code:
adb boot boot.img

with.
yup
 

g96818

Senior Member
Dec 27, 2014
1,006
439
Well crap. I missed that part and had already rooted my phone, then locked the phone back. That caused problems since it wouldn't boot the rooted boot image. Couldn't boot at all. So I changed the active slot to the other slot, then I couldn't boot at all, no fastboot, no recovery, only EDL mode. Had to perform MSM recovery.

Working now, but for a few hours I was worried!

It might helps others if you add another red warning that says DON'T SKIP THIS PART!!! or something at the top of the rooting section that says CHECK TO MAKE SURE YOU CAN SET A PASSWORD/PIN BEFORE CONTINUING haha although maybe it would only help me -1 day ago.
I already have a warning in red
 
  • Like
Reactions: asheroto
Jun 3, 2009
43
5
OnePlus 7T
CPH2451_13.1.0.501(EX01)

Hey just trying to make sure I'm on the latest update. System OTA check doesn't work? I don't have anything related to OTA disabled. Oxygen updater also says the update is not installed even though I did the update. So here are some screenshots. Am I on the latest version?
 

Attachments

  • Screenshot_2023-06-12-16-54-41-78_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    Screenshot_2023-06-12-16-54-41-78_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    170.6 KB · Views: 24
  • Screenshot_2023-06-12-16-54-12-33_1f7d930ac4546e961acbbe2ed3d9ab7f.jpg
    Screenshot_2023-06-12-16-54-12-33_1f7d930ac4546e961acbbe2ed3d9ab7f.jpg
    552.8 KB · Views: 26
Last edited:

MrSteelX

Senior Member
Jan 24, 2013
698
268
OnePlus 9
OnePlus 11

asheroto

Senior Member
Apr 26, 2019
73
18
FYI to fix Netflix, I was able to get it working with these modules:

Might be available on the regular Magisk modules listing, but since I'm using a debug version I had to install manually. Hope this helps someone else!
 
@everyone
To update from A10 to A22 and root
Go fastbootD and flash stock init boot A10
Boot
Update
Reboot again
Reboot to fast boot
Boot from the right kernelSU boot img
Allow magisk root access form kernelSU app
And flash Magisk
Reboot and you good
END
Thank you! This was indeed the only way to get up to the latest version without bootloops.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    regardless of when the backup happens, the a09 init boot image helped. i was able to take the ota and keep root. i upgraded from CPH2451_11_A.09 to CPH2451_11_A.10 to CPH2451_13.1.0.501 to CPH2451_13.1.0.590. i have 4 magisk backup directories under /data; 1 for each update.

    i did a binary file compare and my a9 init_boot image is the same as the one provided here and here.
    my a10 boot image is the same as the one provided here.
    attached are the stock unpatched init_boot images for 13.1.0.501 and 13.1.0.590.
    1
    thanks @g96818 for the guide! i upgraded from a oneplus 7 pro to an 11 and the process went smoothly. my phone came with oxygen os version CPH2451_11_A.09 and i was able to set the pin/password on the first try, so no relocking and unlocking.

    i did run into an issue where i had to install magisk twice. the first time, i did a direct install like the guide said. after rebooting, when i went into magisk, i got the message saying that it needed to be flashed again. i did and then everything seems to be ok. when i went into magisk again, no more message about needing reflashing and my apps that need root work.

    i did make one goof though. initially, i couldn't find the canary or debug builds of magisk. they're not that obvious to see. so i installed the stable version. i checked /data and there's no backup of the stock boot images. is that because i'm using the stable version? maybe the install 2x thing was because of the stable version too? anyway, i have a notification to upgrade to A.10 but since i don't have the stock boot images, i can't follow the instructions to do an upgrade and keep root. what are my options for upgrading and rooting? if i need to go the kernelsu route, that's fine with me.
    1
    thanks @g96818 for the guide! i upgraded from a oneplus 7 pro to an 11 and the process went smoothly. my phone came with oxygen os version CPH2451_11_A.09 and i was able to set the pin/password on the first try, so no relocking and unlocking.

    i did run into an issue where i had to install magisk twice. the first time, i did a direct install like the guide said. after rebooting, when i went into magisk, i got the message saying that it needed to be flashed again. i did and then everything seems to be ok. when i went into magisk again, no more message about needing reflashing and my apps that need root work.

    i did make one goof though. initially, i couldn't find the canary or debug builds of magisk. they're not that obvious to see. so i installed the stable version. i checked /data and there's no backup of the stock boot images. is that because i'm using the stable version? maybe the install 2x thing was because of the stable version too? anyway, i have a notification to upgrade to A.10 but since i don't have the stock boot images, i can't follow the instructions to do an upgrade and keep root. what are my options for upgrading and rooting? if i need to go the kernelsu route, that's fine with me.
    try this:
    1. uninstall magisk stable.
    2. install magisk debug
    3. download the attached init_boot.img and patch it in magisk
    4. you should now have a backup folder so check if you have a backup folder

    btw, the attached boot file was provided by another member earlier in this thread. i just happened to save it.
    1
    thanks for the quick reply! i tried patching the boot image you provided, with "select and patch a file" but no backup folder was created in /data. maybe it's because patching a file creates a new patched file and doesn't touch the original, so a backup isn't needed?
    I guess it's different on this phone. Magisk is supposed to create a backup if you manually patch the boot.

    You're going to need to flash that init_boot.img to the init_boot partition. It'll remove root. You can't update otherwise.

    Don't flash to boot, flash to init_boot
    1
    with safetynet-fix v2.4.0-MOD_2.0, my phone passed the safetynet basic integrity check but failed the cts profile match check. i reverted to v2.4.0-MOD_1.3 and both checks passed.

    https://github.com/displax/safetynet-fix/releases
  • 18
    DO NOT INSTALL TWRP!

    This is for the CPH2451 Rom, but should also work for other roms.

    I have returned my device so I will not be updating this with future updates.

    I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or not.

    Not my fault if your phone bricks.


    Phase 1: Unlocking the bootloader

    WARNING: This will erase all data on your phone.

    WARNING: Netflix will not work after bootloader unlock. OnePlus's fault.

    Step 1: Complete the initial setup. You don't have to waste time signing into anything.

    Step 2: Go into Settings and scroll down to About Device.

    Step 3: Scroll down and tap on Version.

    Step 4: Tap 7 times on Build number.

    Step 5: Go back to settings and go to Additional settings.

    Step 6: Go into Developer options and tap on OEM unlocking and USB debugging.

    Phase 2: Installing drivers

    Step 1: Install everything here,except for OPLocalUpdate_For_Android12.apk. Save that for later.

    https://www.androidfilehost.com/?w=files&flid=334530

    Phase 3: Recognizing the phone and unlocking the bootloader.

    Step 1: Connect the phone to the PC and accept the prompt on your phone. Don't worry if it doesn't show.

    Step 2: If you installed all the drivers correctly, then from any folder on your computer, hold Shift and right click your mouse and select Open PowerShell window here. Use CMD if you have issues.

    Step 3: Type the following code and if you didn't get the prompt earlier, then accept the prompt after entering this code.

    Code:
    adb devices

    You should get something like this:

    Code:
    List of devices attached
        6g73s2t1        device

    Step 4: Reboot to bootloader

    Code:
    adb reboot bootloader

    Step 5: Type the following code and you should get something similar like step 3. Skip to Step 7 if you do. Continue to Step 6 if you don't.

    Code:
    fastboot devices

    Step 6: On your computer, right click This PC and select Manage.

    Look for a yellow triangle. It probably says Android device.
    Right click it and select Update driver.
    Select Browse my computer for drivers.
    Select Let me pick from a list of available drivers on my computer.
    You should have a list of Google or Samsung bootloader drivers or adb drivers or similar.
    This just install one and see if the triangle disappears, if not they try another until it disappears.
    Retry the code above and it should work.

    Step 7: Type the following to unlock the bootloader

    Code:
    fastboot flashing unlock

    WARNING: You might not be able to set your pin, password, fingerprint, and face unlock due to Oneplus incompetence.

    Step 8: Let your phone do it's thing, don't worry about the Orange State warning message after it restarts. This is normal.

    Step 9: Set up the phone, but don't waste your time logging into anything until you can successfully set up a pin or password. Skip to Step 11 if you can set up a pin or password. Continue to Step 10 if it hangs up on the second entry.

    Step 10: Skip everything, enable USB debugging and reboot back into the bootloader.

    This is the annoying part. You need to lock and unlock as many times as it takes for the pin or password setup to work. You might need to toggle the OEM unlocking switch in between lock and unlock cycles.
    Use the following to lock the bootloader and then repeat all of Phase 1 and 3 as many times as it takes.

    Code:
    fastboot flashing lock

    Step 11: Go ahead and setup your phone or continue to Phase 4.

    Phase 4: Rooting

    Step 1: Download and install KernelSU.

    https://github.com/tiann/KernelSU/releases

    Step 2: Open the app to find the Kernel version to download.

    Should be something similar to 5.15.41-android...........
    NOTE: This number is old and will change with each update so use what your phone says.

    Step 3: Take the first 3 sets of numbers and download and save the corresponding boot.img.gz file somewhere convenient.

    https://github.com/tiann/KernelSU/releases

    Using the example above, you will download this file: ksu-10647-Image-android13-5.15.41_2022-05-boot.img.gz
    This file will change with each app update so use the latest available that matches your phone in Step 2.

    Step 4: Extract the .img file.

    Step 5: Reboot to bootloader.

    Code:
    adb reboot bootloader

    Step 6: BOOT the kernel. DO NOT EVER FLASH THIS PHONE!

    Code:
    fastboot boot ksu-10647-Image-android13-5.15.41_2022-05-boot.img

    You essentially have temp root at this point.

    Step 7: Download and install Magisk Canary or Delta Debug*. I used Delta Debug*. Stable does not work.
    *Name changed from Delta to Debug.

    https://github.com/topjohnwu/Magisk

    Step 8: Open KernelSU and select the middle Superuser tab

    Step 9: Scroll down and toggle Magisk

    Step 10: Open Magisk and perform a direct install.

    Step 11: Install safetynet-fix-v2.4.0-MOD_1.2

    https://github.com/displax/safetynet-fix/releases

    Step 12: Clear the data from Playstore app and any Google app that has issues.

    Step 13: Enjoy!

    Netflix:

    Netflix does work, but DRM will drop from L1 to L3. However, I'm not prepared to release the fix yet cause I don't want you guys using my Netflix account.

    Realistically, since I no longer have this phone, I can't test it anymore so those who don't have a working OP10 or OP10T, you're SOL for now.

    For those who do still have a rooted OP10 or OP10T with working Netflix, then download Swift Backup, back up the app settings from your OP10 or OP10T and restore the files on the OP11.

    https://play.google.com/store/apps/details?id=org.swiftapps.swiftbackup&hl=en_US&gl=US

    WARNING: IF YOU GIVE THE BACKUP FILES TO SOMEONE ELSE, THEN THEY WILL HAVE ACCESS TO YOUR NETFLIX ACCOUNT!

    OTA Updates:

    I have returned my device so this will be the only post I'm making for updates. Follow the Non-PC Method for future updates.

    Color/Oxygen OS android 13 update

    CPH2451_11.A.07 NA Update & ROOT

    CAUTION!
    Not my fault if your phone breaks.

    WARNING!!!
    Issues I've seen on previous devices:
    - A few people have had bootloop issues due to using the wrong rom on the wrong phone. (e.g. Installing the Global ROM on a NA, EU, IN, or CN model)
    - If you have "FLASHED" the patched boot vice "BOOT" at anytime prior to this, then you can NOT use OTA unless you want to bootloop or end up in EDL and wipe the phone.

    I can't help you if your phone doesn't update properly.

    -----------------------------------------------------------------------------------------

    NA CPH2451_11.A.07 OTA Incremental update:
    Official: https://android.googleapis.com/packages/ota-api/package/11ca82d836bbd2530659d57bca236d2da0caf5dd.zip
    Mirror: https://www.androidfilehost.com/?fid=4279422670115720937
    SHA-1: 11CA82D836BBD2530659D57BCA236D2DA0CAF5DD
    MD5: D0A498CBDC3DABB491FD2EC061CD05C0

    OnePlus Local Update Tool (OPLocalUpdate_For_Android12.apk). Works on 13.
    Mirror: https://www.androidfilehost.com/?fid=15664248565197176984
    SHA-1: 80707A75F7FA9E1864E84C7C7C270175A9FEC129
    MD5: ADF932B2FD4C2A2B379C9427197B6B6A

    Two methods are available, PC and non-PC. I refer the non-PC method since it's much easier and it hasn't failed me yet so I'm just going to post instructions for that. If you screw up and lose root, then repeat Phase 4 for the PC method.

    -----------------------------------------------------------------------------------------

    Non-PC Method

    See Warning above.

    Step 1: You must unroot first. You don't have to completely remove Magisk, just restore images. Open Magisk, click uninstall magisk, and only click restore images. DO NOT REBOOT!

    Step 2: Install OTA update using the OPLocalUpdate app or through the stock system update. DO NOT REBOOT!

    Note: Skip to the next section if you want to back up the new stock boot.img, init_boot.img, and persist.img files before rooting the update.

    Step 3: Open Magisk and install to inactive slot. Reboot.

    -----------------------------------------------------------------------------------------

    For those who followed other directions to FLASH the patched init_boot, then reflash the stock init_boot using the same directions you previously used to flash the patched file.

    Follow Phase 4 to root.

    CPH2451_11.A.06 init_boot image:
    Stock
    SHA-1: 40F29889D68305B87ED8C0936F57F3F18A3A71D0
    MD5: BF310CAEE6B1F176CA0A138BC3DB65CC

    CPH2451_11.A.07 init_boot image
    Stock
    SHA-1: 22010F8F186F1438FFFEEC186014515F0C674F54
    MD5: 592D48E06F7F4494937445F9910C1CC0

    Saving the stock boot, init_boot, and persist images after OTA updates:

    Connect your phone to your PC and run the following codes using CMD or Powershell and save the files to your computer.

    The new boot files will be either the _a.img or _b.img files, depending on which slot the update is installed to. You can save both and look to see which slot magisk is patching when you install to the inactive slot to know which are the new boot images. There is only one persist img file and it supposedly changes with each update so make sure you save it.

    Code:
    adb shell
    su
    dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
    dd if=/dev/block/by-name/boot_b of=/sdcard/boot_b.img
    
    dd if=/dev/block/by-name/init_boot_a of=/sdcard/init_boot_a.img
    dd if=/dev/block/by-name/init_boot_b of=/sdcard/init_boot_b.img
    
    dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img

    GPay no longer works, but Wallet does.
    4
    For those who accidentally flashed a patched init_boot over the boot file, here are the stock boot files:

    CPH2451_11.A.06 boot image:
    Stock boot
    SHA-1: 901EC0F5A2ECAF0F0B5472BA50A2C7B857C6D932
    MD5: 96FFEAFC046C3F6B80B706694A46213B

    CPH2451_11.A.07 boot image
    Stock boot
    SHA-1: FCB9964D9547363AB524C10BA2E15AAE8899DBC1
    MD5: DCFED50F37E79C272C954C9F6F1F82E2
    4
    So I would just need to do a full unroot, Flash the init_boot.img from the OP, do the update and then before I root again pull my own init_boot.img so I have a copy for the next update? And repeat next time?
    Read the entire first post as well as all the spoilers to know to do.
    3
    Yes, I've done this for the OP11. I was freaking out for a bit though; it took a while to get the phone to take a password/PIN when the bootloader was unlocked, but when I came back to a locked bootloader, it wouldn't take a password in THAT state. I finally realized that if I unlock, DON'T give it a password, then lock again, it took a password.

    So the solution might be the go to you undesired state, DON'T put in a password, and then your desired state will. Whole lot of good that knowledge will do me now. lol
    Yes.
    I set up the phone without any lock password nor pin.
    Unlocked bootloader (only one time), rooted and then I set up my screen lock and fingerprints without problem and without need to lock and unlock several times.
    3
    @JPower123 @cabagekiller

    I took my SIM card from my OP8 and put it in my OP11 and I had everything working fine until I rooted my phone. I took my SIM card out of my OP11 put it my OP8 and everything worked. Put it back into my OP11 and I couldn't make a phone call, no data by the way this is AT&T.

    I contacted AT&T and they told me that OP11 is NOT on their registered list of certified phones for their network. I asked to speak to a supervisor and he assured me that it is NOT on the list. This point I said I'm going to give you my IMEI number and I want you to try to couple it to my SIM card. They agreed to try and my phone has been working ever since. It is NOT on the certified list but it does work on the network you just have to tell them to replace your IMEI number on their end