How To Guide PROPER CPH2451 Root and Update instructions
- Thread starter g96818
- Start date
Delta reinstalled itself after a restart but I removed it. Little affrsid to restart again lol
Yes. Magic Mount works. All modules except Systemless Hosts. They messed up loading the host file.
Also other major thing is only /system/etc/hosts can be changed anymore. All other mounts are read only. Meaning any changes to system should be updated to /data/adb/modules/<module-name>/<edit-path> instead of direct <edit-path>
Alright, thanks for the update, all good info! Does this mean that 25211 breaks Adaway at this time?
YesAlright, thanks for the update, all good info! Does this mean that 25211 breaks Adaway at this time?
It was already logged. Just use Canary 25208 if you need everything working fine. If you don't want Systemless Hosts, Just use Canary 25211. Everything works fine.
Guys is it possible to unroot and relock my phone as I am unable to use passkeys which is required for some apps like Binance. I have backed up boot a,boot b, init_boot_a,init_boot_b right after I did a direct install in magisk..I have lost the restore images option in magisk due to formatting data by mistake..So what if I just flash init_boot_b to both init_boot_a and init_boot_b? OR maybe I can just switch to b partition and get the unrooted and locked bootloader back and whenever I want root I would just switch to "init_boot_a" partition. Is this possible?
I also see that Magisk stable v26 is out! Question, I kept a stock init_boot image of A.09 Should I used Magisk app to patch that and then flash it? Or update Magisk DIRECTLY from manager? What's the safe bet?
I tried to unroot the booloader by switching from "a partition" to "b partition" as magisk didn't had the original init_boot images to restore and phone ended up in bootloop, tried changing it back to "partition a" but still bootlooping continued then i went to the service center and the service center guy told me you have unlocked the bootloader and rooted the device soo your warranty is void even thou he cannot prove that I have rooted the device as system was unable to boot and go paas through OnePlus logo .after some arguments somehow he agreed that this time he will replace the motherboard because he couldn't fix the phone even after flashing the stock rom and told me never to unlock the bootloader again and if you do, you are done with your device.lol. Now I have a device which has been opened and motherboard's replaced, who knows how long this replaced motherboard gonna work as I have heard replaced motherboards don't work long enough after warranty ends. Soo guys don't switch partitions or you might end up like this.just letting you all know.
I installed the incremental OTA 11_A.09 by removing root and the installing via the OnePlus local install. However after unrooting my phone rebooted, so long story short I lost root. I extracted the payload.bin file for A.09, but the init_boot.img file is 0 bytes. Can anyone provide a patched init_boot.img file for US version, CPH245, A.09 or provide insight where i can find the stock init_boot.img for this OTA to patch myself?
Thanks, in advance!
Thanks, in advance!
Last edited:
Use the kernelSu way
To boot your phone with root and Patch than your init_boot.img diretly with magisk
Thanks! However, the instructions on the first page reference to download and install KernelSU. However, the link provided is a duplicate link to the one below it. I don't see an option for the App.
[EDIT]
I expanded the list and see the APK now. Thanks!
I downloaded AnyKernel3-android13-5.15.41_2022-05.zip to my machine, and extracted it. There's not a .img file in the contents. There is an Image file without an extension, but that's 42,239kb. Can you provide some insight on how I can get the .img file? Thanks!
[edit]
Looks like those are also located below. Thanks.
Last edited:
@ChrisFeiveel84 Got my device rooted and running. Hardest part was understanding the instructions....lol Thanks again for the assistance.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
1If you are in need of the NA init_boot - see here. I just used it and then followed instructions for "Bootloader already unlocked" on page 1 and it worked without issue. Rooted A10 NA.
https://forum.xda-developers.com/t/...t-keep-root-oos-13-a-10.4571171/post-88503369 @r1pp3d2
@scottlam1 - thanks again!11
Just pointing out that he is using Delta Magisk which is different from magisk1The Magisk Restore image option can be accessed by clicking Uninstall Magisk. This option with reflash the stock init_boot or boot img depending on what is in the backup. This option will unroot your phone after you reboot but retains root till you reboot. Also since stock init_boot or boot img is reflashed, OTA updates will not fail since signatures match.1
Thanks! That worked even using Delta Magisk. My mistake last time was I didn't restore images and immediately uninstalled which rebooted. This way was super easy. I now have the latest incremental OTA and retained root.
Thanks! -
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...........
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.
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
-
[WINDOWS/LINUX][TOOL]Fire Toolbox V30.2- Latest: braveheartleo
-
