How To Guide PROPER CPH2451 Root and Update instructions
- Thread starter g96818
- Start date
Read through this finally sorted it, thank you.This might help you
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!forum.xda-developers.com
Just ran unsigned driver installs which fixed it#
You guys might stay with kernelsu instead of switching to magisk, it's less detectable if you go to telegram group they have zygisk module posted with shamiko then u can install some of zygisk modules. I use kernelsu instead of magisk on OnePlus 11. After booting up off kernelsu boot img I just flash anykernel kernel on OnePlus 11.
Have you tried updating via ota? The only reason why I would not flash the kernel is because we don’t have full rom updates so you might not be able to use ota updates.
ok, it work, but got strange issue now.
I flashed stock init_boot for A07. rebooted, check for updates, let OOS download and update my phone, rebooted. everything look good and shows me on A08, and FEb securirty patch, however when I go back to check for updates it 'checking for updates' then swithcing to installing system update. it does this no matter how many reboots or what. it like it stuck on installing A08 update
should it not say system up to date?
is there a fix for this?
I bought the phone, intended to see if I had the ability to figure this out, then ended up in the hospital for a week and a half with pancreatitis...
The return policy says 15 days, I bought mine on 3/2/2023
You still feel this is to much for a slightly seasoned but very much still a rookie?
I'm not sure about your question because when I attempt to install the 08 update it fails at about 4%. Every time! I read somewhere that if the update is not full released in your region there would be errors installing. Not sure if that is true either.
Usa have only incremental Updates .
And you are rootet (and you have the cph2451 ?)
Yes I have the 2541. I was rooted but I unrooted. Do I need to relock the bootloader? Shouldn't have to right? Won't do manual update either.
No just did a "uninstall/unroot" in Magisk. I can try flashing the init.boot.
Try it
(than when i remember me corect than makes magisk no longer an backup from your stock init_boot.img when you boot with kernelSu and flash than magisk to aktive slot .
And ) and when magisk have no backup from your stock init_boot.img
Than can magisk not flash back the stock init_boot.img when you say in magisk unroot
Sorry to hear about your hospital stay.I bought the phone, intended to see if I had the ability to figure this out, then ended up in the hospital for a week and a half with pancreatitis...
The return policy says 15 days, I bought mine on 3/2/2023
You still feel this is to much for a slightly seasoned but very much still a rookie?
You should be fine if you follow the guide, but I recommend updating to A.08 first.
As you see, some people who rooted incorrectly are having update issues that cannot be solved until a full rom is released.
Many of these are also slightly seasoned rooters whom have only been rooting phones that had the MSM tools. This phone does not so if you mess up, then it’s a trip to the service center or other people who will charge to unbrick your phone.
I am intending to follow this guide to root my 11 as well. As OP mentioned, I've really only done rooting on 1+ devices that have an MSM (ive rooted 7pro and 9pro) but I feel like i should be able to do the Magisk method. It seems pretty similar to do the updates as I had done with my 7pro before where everytime i have a system update I needed to disable the Magisk Modules I had then "Unroot" before rebooting.I bought the phone, intended to see if I had the ability to figure this out, then ended up in the hospital for a week and a half with pancreatitis...
The return policy says 15 days, I bought mine on 3/2/2023
You still feel this is to much for a slightly seasoned but very much still a rookie?
On my 9pro it was slightly different since I've been running a Custom ROM on it basically from day 1 and have always just flashed the Magisk apk after every update.
I've seen a few folks mention in here they plan to stick to the KernalSU method but I don't want to have to be flashing patched imgs and what not as im sure i would likely forget one time and ruin it when i attempt a system update.
Took your advice and updated first. Patiently read the whole thread before I started and was able to figure out everything with some stare time and successfully rooted. It took me four hours though, but it's done properly. Thank you very much!
I completed phase 4 and everything went fine. A couple of restarts later and I no longer have root. Magisk says I have root after repeating the process but none of my root apps work. I'm using magisk delta on beta since he said stable doesn't work.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
1
It's much easier with Partitions Backup appYeah that caught me off guard too! A.22 sounds so much simpler haha also, you can update your phone and then extract it using a terminal emulator BEFORE you root the inactive slot.
Example, if you're in slot a and updated slot b?
Su (enter)
dd if=/dev/block/by-name/init_boot_b of=/sdcard/Documents/init_boot.img (enter)
This command would extract init_boot from your b slot and save it to your Documents folder, swap letters if it's A slot. THEN root your inactive slot
1
Is this the one by Wanam? I was just looking around on apkmirror since i couldnt find a github or anything. I know we cant directly link to stuff like that but i was just curious.1
Had no idea this existed
Thanks for that heads up, I'm always doing things the hard way lol1
Good deal, I saw this post and figured it was the same. ThanksHere
And the Post in CDA
[App][Root] Partitions Backup & Restore
☆Root required☆ ☆Supports for all Android...
forum.xda-developers.com
1
Even I'm not sure. But I also read it in some post on xda. Maybe there is a step or flag set to complete upgrade or trigger something on next reboot after OTA extraction and verification. -
12This 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. I used Delta. Stable does not work.
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: 40F29889D68305B87ED8C0936F57F3F18A3A71D0init_boot_a.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes...www.androidfilehost.com
MD5: BF310CAEE6B1F176CA0A138BC3DB65CC
CPH2451_11.A.07 init_boot image
Stock
SHA-1: 22010F8F186F1438FFFEEC186014515F0C674F54init_boot_b.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes...www.androidfilehost.com
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.43For 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: 901EC0F5A2ECAF0F0B5472BA50A2C7B857C6D932boot_a.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes...www.androidfilehost.com
MD5: 96FFEAFC046C3F6B80B706694A46213B
CPH2451_11.A.07 boot image
Stock boot
SHA-1: FCB9964D9547363AB524C10BA2E15AAE8899DBC1boot_b.img | by Xi Jing Pooh for /e/OS supported models
Download GApps, Roms, Kernels, Themes...www.androidfilehost.com
MD5: DCFED50F37E79C272C954C9F6F1F82E23
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
New posts
-
Question Glucotrust Australia Experiences Test Preis
- Latest: glucotrustaustra
-
-
-
