Question Magisk support for Nord CE2

Search This thread

rp1989

New member
Jan 25, 2009
3
0
The boot image is available however you won't be able to flash it because the bootloader isn't accessible after Android 12 update
That's disappointing hope its a bug and not a permanent issue. Has anyone tried installing the patched boot via the local update method mentioned for the rollback?

Are you able to share the boot.img for IV2201_11_C.05 please?

"Go back Settings -> About device -> Up to date -> Click the top right button -> Local install -> Click on the corresponding rollback package -> Extract -> Upgrade -> System upgrade completed to 100%."
 

@shobhitsk

New member
Aug 26, 2022
1
0
Here's my patched boot.img for A13. India.
Magisk works.
Hey buddy. , Have u insta or tele , if yes , then contact me , my tele id - @shobhitsk, can you tell me how to root this device , is it any need bootloader unlock or not... And A13 boot.img work on A11 Android version+A13update. Little bit confused ...
 
Mar 30, 2021
26
5
That's disappointing hope its a bug and not a permanent issue. Has anyone tried installing the patched boot via the local update method mentioned for the rollback?

Are you able to share the boot.img for IV2201_11_C.05 please?

"Go back Settings -> About device -> Up to date -> Click the top right button -> Local install -> Click on the corresponding rollback package -> Extract -> Upgrade -> System upgrade completed to 100%."
I already shared the patched boot image for Android 12 please check earlier post in the same conversation. I can't roll back rn because this is my only device and busy with some work. So need to find a way to root on Android 12 itself
 

zachabz

Member
Feb 17, 2017
5
2
23
UAE
nohello.net
Alright I'm confused (consider me a newbie, rooted a couple of times back in the andriod Icecream sandwich days)
My progress so far: Unlocked the bootloader. and I'm stuck there?
cause I got no clue on how to proceed.
My Build number is: CPH2409_11_A.11 (see photo attached)

What should I do next? I'm confused. Any help appreciated.
 

Attachments

  • Screenshot_2022-09-20-18-25-06-75_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    Screenshot_2022-09-20-18-25-06-75_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    96.2 KB · Views: 44

Avi69420Ezio

Member
Feb 3, 2022
7
0
Alright I'm confused (consider me a newbie, rooted a couple of times back in the andriod Icecream sandwich days)
My progress so far: Unlocked the bootloader. and I'm stuck there?
cause I got no clue on how to proceed.
My Build number is: CPH2409_11_A.11 (see photo attached)

What should I do next? I'm confused. Any help appreciated.
wrong thread mate
 

Avi69420Ezio

Member
Feb 3, 2022
7
0
Can someone patch this IV2201_11_C.07(Android 12) boot img for me. Whenever i try to patch using magisk it gets currupted.
 

Attachments

  • boot.img
    32 MB · Views: 37

Andoid23

New member
Sep 29, 2022
2
0
Can someone patch this IV2201_11_C.07(Android 12) boot img for me. Whenever i try to patch using magisk it gets currupted.
Hi,

I have successfully patched the boot.img with magisk on my Oneplus Nord CE 2, also in the version IV2201_11_C.07 (Android 12).

But I am afraid to root my phone.

Let us know if it worked.
 

Attachments

  • magisk_patched-25200_ExRNX.img
    32 MB · Views: 15

malwho

Member
Oct 2, 2022
6
0
Can anyone share the original Vbmeta.img from A11 Stock Rom?
Thanks in advance
 
Last edited:

Bebo541

Member
Apr 5, 2021
13
3
Lenovo ZUK Z2 (Plus)
I was able to root android 12. I rolled back to android 11 (rolling back to android 11 formats all data) and installed TWRP using https://forum.xda-developers.com/t/unofficial-twrp-3-6-2_11-0-oneplus-nord-ce-2-5g.4490091/. After that I downloaded full OTA zip for android 12 using Oxygen Updater app. modified the OTA zip with patched boot.img. I also had to modify updater-script file and put device id as IV2201. then flashed the modified OTA zip. After that magisk is working properly. but TWRP's touch screen became unresponsive. but adb commands are working fine in TWRP.
 
  • Like
Reactions: Mwadime143m

pester41

Member
Aug 27, 2020
5
0
I was able to root android 12. I rolled back to android 11 (rolling back to android 11 formats all data) and installed TWRP using https://forum.xda-developers.com/t/unofficial-twrp-3-6-2_11-0-oneplus-nord-ce-2-5g.4490091/. After that I downloaded full OTA zip for android 12 using Oxygen Updater app. modified the OTA zip with patched boot.img. I also had to modify updater-script file and put device id as IV2201. then flashed the modified OTA zip. After that magisk is working properly. but TWRP's touch screen became unresponsive. but adb commands are working fine in TWRP.
Could you share the patched boot.img you used?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    We can root using another method

    Before going further read @ko_hi's disclaimer here.
    Please do not tell how to root A12 for the sake of the phone!

    Why!?

    As we all know, magisk is very buggy on A11 (hence, even if you succeed to boot it, any modification can break the phones boot procedure) so it will be stuck on boot animation.

    But i have enabled USB debugging?! Won't that help me?

    Answer is simple: NO
    the adb access seems to be *revoked* or as system never boots up properly. It will not allow adb commands to be run due to unauthorized device!

    But that's okay right!?
    NO. if you get to this point, the only hope you have, is to let the phone try to boot. This will fail so it will reboot and try again. This will happen 3 times. Then it should go to recovery! And that will take approx 20-30 minutes! *Sounds fun right?*

    Then when were in recovery. Touch is broken so you must use a PC to restore the device. And if you have none nearby. Well YAY you're out of luck for the moment.

    But if i have a PC nearby?
    Well loose all your files and start over again. But don't be mad if it will happen suddenly again after some time 😴


    But can't this be prevented!!!?
    Sure, if my assumption is correct.

    Rootguard in kernel is causing the phone to not boot if using root access. (This isn't fully proven by me though) still in testing phase. But what I've found in kernel source is that they do try to kill root access? And this cause the device not to boot? (Haven't been able to log it either since i haven't had insecure me adb)

    Can't really tell fully since It was some weeks ago i browsed the code.

    But with this said,. For the sake of your phone. Don't root A12
    It can brick your device.

    Here are the instructions I followed
    • Download and install DSU sideloader app from https://github.com/VegaBobo/DSU-Sideloader/releases
    • Download Lineage OS rooted GSI from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/. I have downloaded the GSI with name lineage-19.1-20230112-UNOFFICIAL-arm64_bvS.img.xz
    • Go to DSU sideloader app and install the downloaded GSI. It will show some adb commands which you need to run using adb
    • Once installation is complete you will get a notification to boot to GSI. use that and boot into lineage OS
    • Once initial setup is completed in lineage os, enable usb debugging and run 'adb shell'
    • in the adb shell run 'su'
    • then run 'dd if=/dev/block/sdc49 of=/sdcard/boot.img; sync'
      • Now you should have boot.img file in your phone
    • Install magisk and patch the boot.img
    • then run 'dd if=/sdcard/<patched boot file> of=/dev/block/sdc49; sync'
    • Once it is complete reboot
    • Now it should be rooted
    • You can discard the GSI boot from the notification, which will delete all the data of lineageOS
    On the side note, you can try out custom roms using DSU sideloader. you can have look at list of GSIs available at https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list.
    The GSI roms have few bugs like on screen fingerprint does not work
  • 3
    I have successfully rooted my phone with Magisk on the A.12 update. Bluetooth/wifi are working. I was able to acquire the firmware files, and was able to extract the boot.img. Please note that my phone is the Indian Variant.

    Screenshot_2022-06-22-10-31-37-42_144d3b563413d7d0300db22090f32a96.jpgScreenshot_2022-06-22-10-30-59-40_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    3
    Can ou share the Boot.img?
    Also, are you able to upgrade to A.12?
    A11 boot image attached. I am able to see the A12 update, but have not tried yet.
    2
    While the device is the cheapest offering from OnePlus, it's quite difficult to root it still..

    * I somehow unlocked the bootloader after downloading dimensity drivers and using fastboot.
    * The immediate next step was to extract boot.img from stock rom using payload dumper.. easy enough right? Apparently not!!.. There is no stock rom available on the OnePlus site for this device and it doesn't even support local upgrades..

    There's no TWRP, Orangefox or any other recovery to install magisk as of yet.. I wonder what's wrong with the device and why one has to try so hard to root a simple phone..

    If you're reading this and know a way to root, please help out..
    2
    Say

    Says it's open beta based on android 12 unless I missed something
    There's a rollback file (if you want to stop using android 12) that contains the A.13 boot.img
    2
    Here's my patched boot.img for A13. India.
    Magisk works.