How To Guide Rooting OnePlus Nord 2 CE lite

Search This thread

PsYk0n4uT

Senior Member
checked and found nothing
Are u looking for info labelled CE2 Lite? Because it won't b labeled any differently, the method should b the exact same as the N20. Look for the how to root any N20 thread and u should b able to follow it. The nice thing about the method we r using is that your pulling your own firmware so u don't have to worry about firmware matching or not
 

equals2

Member
Dec 7, 2022
6
1
Everything worked until I got to flashing vbmeta, I got this error
C:\Users\samue\Desktop\extracted_20221207_020237>fastboot flash --disable-verity --disable-verification vbmeta .\vbmeta.img fastboot: unknown option -- disable-verity
C:\Users\samue\Desktop\extracted_20221207_020237>fastboot flash --disable-verification vbmeta .\vbmeta.img fastboot: unknown option -- disable-verification
But I could flash it without disable verity neither disable verification and it ended up working, just typed su in terminal emulator and got the pop up, thanks!!!
 

equals2

Member
Dec 7, 2022
6
1
One question, did you get the fake props working? I tried with props config but couldnt find the OP Nord CE 2 lite on the menu
 

keyra74

Senior Member
Aug 6, 2009
1,431
200
so i just do that without removing magisk ?

...after downloading the File, get the PayLoadDumperGo from XDA Member ssssut and extract the downloaded file ...maybe you will need to add "liblzma-5.dll" to the directory ...I think you will manage it by yourself ...you will only need the "boot.img" and "vbmeta.img"

...copy the boot.img to your phone and patch it with the usual Magisk method (install / choose file) and copy back the resulting magisk_boot.img to your pc.

...now the tricky part ...and yes, I got the "broken Boot/Recovery Image Screen" and yes I was scared for just a few seconds ...but I solved it and here is how:

reboot your Device to fastboot mode (unlocked) and type:

Code:

fastboot flash boot .\magisk_boot.img

DO NOT REBOOT NOW!!!

...you will have to flash vbmeta.img like this:

Code:

fastboot flash --disable-verity --disable-verification vbmeta .\vbmeta.img

...now it´s time to reboot and when it´s done just start up Magisk Manager and finish the setup and you´re done ...simple as can be :D

...best regards

derdoktor667
 

Matz125

Member
Dec 25, 2022
7
2
Ok, so I'm rather new to all this. I tried following a twrp based rooting tutorial but I can't quite get it to work.

It's currently stuck booting to the bootloader as the default. I can access fastboot tools, and when flashing the unofficial twrp, I can access adb tools. As I've understood now thanks to DerDoktore I should just need fastboot.

Since I didn't know exactly where I messed up I tried unpacking payload.bin from Oxygen Updater and flashed everything in there. To both A and B slots where applicable.

I then found this thread and tried the "patch boot.img with magisk and flash via fastboot" method but it still boots into the bootloader.

I'm quite confused. Shouldn't it at least boot into the normal OS after flashing the boot and vbmeta images directly from Oxygen Updater. I feel like I'm missing something vital here.

I have the European version of the CE 2 lite if it's relevant.

Any help is appreciated, I'm quite desperate at this point.
 

keyra74

Senior Member
Aug 6, 2009
1,431
200
Ok, so I'm rather new to all this. I tried following a twrp based rooting tutorial but I can't quite get it to work.

It's currently stuck booting to the bootloader as the default. I can access fastboot tools, and when flashing the unofficial twrp, I can access adb tools. As I've understood now thanks to DerDoktore I should just need fastboot.

Since I didn't know exactly where I messed up I tried unpacking payload.bin from Oxygen Updater and flashed everything in there. To both A and B slots where applicable.

I then found this thread and tried the "patch boot.img with magisk and flash via fastboot" method but it still boots into the bootloader.

I'm quite confused. Shouldn't it at least boot into the normal OS after flashing the boot and vbmeta images directly from Oxygen Updater. I feel like I'm missing something vital here.

I have the European version of the CE 2 lite if it's relevant.

Any help is appreciated, I'm quite desperate at this point.
there's no twrp... are you sure you're on right tracks
 

Matz125

Member
Dec 25, 2022
7
2
there's no twrp... are you sure you're on right tracks
Oh, not at all. The twrp was unofficial. Although twrp is nice and all, I primarily want to root the phone. As I've understood things I shouldn't need twrp to do that, but simply fastboot. I can't get it to work though, it always boots into the bootloader...
 

Matz125

Member
Dec 25, 2022
7
2
OMG IT'S WORKING!
I don't even know why it worked now and not before but I'll go through it in case someone else has a similar problem.

My current slot was B. I entered fastboot mode. I flashed the stock and vbmeta images as stated in DerDoktore's instruction but to both slots though the "--slot all" argument. After rebooting it went back to the bootloader again, but after changing my current slot to A and rebooting it worked.

I then tried to flash the magisk_boot image (and vbmeta) to slot B while in A and then changing to B, mirroring how I did it before but it just loaded into the bootloader again. Switching back to A still worked.

To fix root I just flashed magisk_boot and vbmeta with the "--slot all" argument rebooted while set to slot A. I now have root.

If I'd hazard a guess I'd say I messed something up with the B slot at some point and that's why it isn't working.
 
  • Like
Reactions: keyra74

TeunB

Member
Jan 4, 2023
12
3
I tried to root my device following this emthod but it seems to be soft bricked.
It boots into recovery mode or fastboot mode.
Device: CPH2409 (Nord CE 2 Lite) (EU)
OXygen download: CPH2409_11_A.14 (EUI)

I followed the steps:
  1. Downloaded the payload with oxygen updater
  2. extracted the boot.img & vbmeta.img with payload-dumper-go
  3. patched the boot.img with magisk
  4. flashed the patched "magisk_boot.img"
  5. flashed the vbmeta with the commands
  6. rebooted
When my device rebooted my screen was no longer responding to my finger/touching.
I tried to flash the original boot.img and vbmeta.img from the download but my screen still wouldn't respond to touch.
I cant use any of the recovery options as my screen wont respond to the touch.
Is there any way to restore the stock rom that I could try?
 

Matz125

Member
Dec 25, 2022
7
2
I tried to root my device following this emthod but it seems to be soft bricked.
It boots into recovery mode or fastboot mode.
Device: CPH2409 (Nord CE 2 Lite) (EU)
OXygen download: CPH2409_11_A.14 (EUI)

I followed the steps:
  1. Downloaded the payload with oxygen updater
  2. extracted the boot.img & vbmeta.img with payload-dumper-go
  3. patched the boot.img with magisk
  4. flashed the patched "magisk_boot.img"
  5. flashed the vbmeta with the commands
  6. rebooted
When my device rebooted my screen was no longer responding to my finger/touching.
I tried to flash the original boot.img and vbmeta.img from the download but my screen still wouldn't respond to touch.
I cant use any of the recovery options as my screen wont respond to the touch.
Is there any way to restore the stock rom that I could try?
Ok, let me preface this by saying that I'm a total noob when it comes to this.

I think what solved my problem was flashing with the "--slot all" command. You could try changing the current slot as well. Also make sure you're in recovery mode and not the bootloader.

I had the same problem with no touch in recovery mode (although mine was in Chinese for some reason), iirc I could still reboot it into the bootloader. I used the buttons (they still worked for me) but adb/fastboot commands might work as well.

Also if you've never specified a slot, it should default to the current one. I think changing to the other should let you boot into the OS normally but I might be wrong about that.

Now for some speculation; I wouldn't recommend trying this without a second opinion.
Maybe if the currently installed version was of an earlier version than the one from Oxygen Updater you'd need to flash the whole thing, like xbl and my_bigball.
Again I don't know if this will help or even if it's a good idea but after I thought I'd broken mine that's what I did and it's working now.
Note that unlike the boot partition, some of other ones aren't dependant on the slot, so you won't have a failsafe after flashing it.
 

TeunB

Member
Jan 4, 2023
12
3
Ok, let me preface this by saying that I'm a total noob when it comes to this.

I think what solved my problem was flashing with the "--slot all" command. You could try changing the current slot as well. Also make sure you're in recovery mode and not the bootloader.

I had the same problem with no touch in recovery mode (although mine was in Chinese for some reason), iirc I could still reboot it into the bootloader. I used the buttons (they still worked for me) but adb/fastboot commands might work as well.

Also if you've never specified a slot, it should default to the current one. I think changing to the other should let you boot into the OS normally but I might be wrong about that.

Now for some speculation; I wouldn't recommend trying this without a second opinion.
Maybe if the currently installed version was of an earlier version than the one from Oxygen Updater you'd need to flash the whole thing, like xbl and my_bigball.
Again I don't know if this will help or even if it's a good idea but after I thought I'd broken mine that's what I did and it's working now.
Note that unlike the boot partition, some of other ones aren't dependant on the slot, so you won't have a failsafe after flashing it.
I tried changing the slots from all to a/b but it didn't help. I think its probably because the Oxygen OTA is a higher version then my stock/originally installed version (I got the phone yesterday). Maybe that's also why the touchscreen doesn't work since the patched magisk boot.img? im not sure.

I can get to the Chinese recovery screen through the fastboot menu, but when i want to select an option with the keys a final touchscreen confirmation pops up, and i cant select it. When starting up it defaults to fastboot.

I think I need to flash all .img files from the downloaded files manually? or with flash-all?
Not sure what files i can/should and cannot/shouldnt flash.
 

Matz125

Member
Dec 25, 2022
7
2
Yeah, I had the same problem with recovery and constant fastboot. At the very least you probably won't need to actually use recovery mode, just enter it. When I flashed them, I did it all manually so if you're willing to try it, that might work.
 

TeunB

Member
Jan 4, 2023
12
3
Yeah, I had the same problem with recovery and constant fastboot. At the very least you probably won't need to actually use recovery mode, just enter it. When I flashed them, I did it all manually so if you're willing to try it, that might work.
So just manually flash all files from the downloaded payload?
The files that wont flash immediatly I can try again using the super/force flash command?

I saw sometimes the partition name are different from their respective .img file. Maybe there is a list somewhere?
Thanks for your help so far!
 

Matz125

Member
Dec 25, 2022
7
2
So just manually flash all files from the downloaded payload?
The files that wont flash immediatly I can try again using the super/force flash command?

I saw sometimes the partition name are different from their respective .img file. Maybe there is a list somewhere?
Thanks for your help so far!
I think they should all let you flash them if you do it from recovery mode. I never used the super/force command myself so I don't think it'll be necessary. You might want to try flashing it from the opposite slot though. I was on slot B when I flashed everything to A so that might have something to do with it.
As far as I know, all the partition names were the same as the image names so it should be rather straight forward.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I tried all of the above but failed huge. Now my phone is bricked I think, it keeps getting started in either bootloader or the message that the phone is corrupted. I found a working TWRP 3.7.0_12Beta_v1 but I can only use it to install magisk and nothing else will pass.
    I tried the origional boot.img that i got off my phone when it was working but if i try to install it with TWRP it fails. I found some boot.img online that matches the phone but they also fail.

    Can someone please help me. I'm currently stuck with an expensive paper weight.
    Thanks to the kind people at the Nord ce 2 ite telegram group I managed to find a way. I got it running again perfectly fine now.

    So what went wrong:
    My partition table was f*cked, so i couldn't flash any more. I also couldn't go into the "fastbootd" (to flash critical partitions) and my touchscreen didn't work.

    !!! Important !!!
    • These are my steps, it can always be different for you so dont blindly copy them
    • If you tried to root and something is wrong or looping etc. > FIRST TRY TO CHANGE THE SLOT TO A/B BEFORE FLASHING ALL KINDS OF STUFF LIKE I DID!!!
      (the other slot should still be clean and bootable)
    • My model (CPH2409)
    • The OTA I used is the A14 one
    • If the phone doesn't get detected in bootloader, fastbootd or Recovery: try the other slot a/b
    • delete COW files/partitions in fastboot enhance
    • always enable logging in fastboot enhance
    • fastboot enhance also has a payload extracter build in if you need a single img
    • If using a external SD card check if its fat32, if so format it to the other fat one (fat32 wont allow single big files)
    Key combos:
    • POWER + VOL UP = recovery/fastbootd
    • POWER + VOL UP + VOL DOWN = bootloader/normal fastboot\
    • VOL+UP+VOL DOWN + INSERT CABLE = edl mode (If an MSM tool ever gets released)

    The solution

    first:
    1. download the latest OTA (preferably via oxygen updater)
    2. download fastboot enhance (Ui makes it convenient and it can flash an entire payload.bin)
    3. download the TWRP from spector0
    4. extract the vendor_boot.img and dtbo.img from the downloaded OTA
    5. boot into the bootloader
    6. flash vendor_boot.img and dtbo.img with fastboot enhance
    7. flash the twrp.img from spect0r
    8. reboot to recovery
    Now I got Into the TWRP recovery screen and my touch screen was working again. Using TWRP I was able to reboot into fastbootd again. but my partition table was still messed up so I couldn't flash the super imgs properly (system, system_ext, etc).

    To fix this I needed a TWRP back up, restoring this will repair the partition table too:
    1. Download twrp back up
    2. extract the zip/rar if archived
    3. put the extracted back up folder on your phone somewhere where TWRP can reach it (I used an external micro sd)
    4. In TWRP go to restore
    5. Select the back up (if sd: select storage > select the mircroSD)
    6. select the twrp back_up
    7. restore the back up
    8. not sure if needed but I rebooted to be sure
    The partitions table should now be fixed. Now to restore the system/OS:
    1. boot into fastbootd/recovery
    2. open fastboot enhance (should show under basic properties which slot and if yoru'e in fastbootd)
    3. check: show logs & Ignore unknown Partitions
    4. flash the entire payload.bin file (from the downloaded OTA)
    5. after its done, check the logs for which partitions failed (probably most starting with: "my_")
    6. in fastboot enhance (fastbootd): partitions > Create > *name of failed partition* size: 12000b > ok
      (size will automatically be adjusted when flashing)
    7. Check the logs if nothing failed
    8. reboot to system
    9. You should now get into the setup screen
    My phone is now working again! yay! 🥳🥳🥳

    Once I made a back-up of my clean twrp I'll link it here and the OTA too if possible.

    OTA LINK

    TWRP-backup
    1
    I tried flashing these imgs:

    flashable/working img (both slot a & b):
    Code:
    fastboot flash boot boot.img
    fastboot flash dtbo dtbo.img
    fastboot flash modem modem.img
    fastboot flash oplusstanvbk oplusstanvbk.img
    fastboot flash oplus_sec oplus_sec.img
    fastboot flash splash splash.img
    fastboot flash vbmeta vbmeta.img
    fastboot flash vbmeta_vendor vbmeta_vendor.img
    fastboot flash vbmeta_system vbmeta_system.img
    fastboot flash vendor_boot vendor_boot.img
    fastboot flash core_nhlos core_nhlos.img
    fastboot flash engineering_cdt engineering_cdt.img
    fastboot flash bluetooth bluetooth.img
    fastboot flash featenabler featenabler.img
    fastboot flash dsp dsp.img

    The "--force" command also doesnt seem to work
    Not flashable due to critical partitions not allowed:
    Code:
    fastboot flash abl abl.img
    fastboot flash devcfg devcfg.img
    fastboot flash hyp hyp.img
    fastboot flash imagefv imagefv.img
    fastboot flash keymaster keymaster.img
    fastboot flash qupfw qupfw.img
    fastboot flash tz tz.img
    fastboot rpm rpm.img

    Probably also critical but partition not found / (img_a/b) no such partition
    Code:
    fastboot flash product product.img
    fastboot flash vendor vendor.img
    fastboot flash odm odm.img
    fastboot flash uefisecapp uefisecapp.img
    fastboot flash xbl xbl.img
    fastboot flash xbl_config xbl_config.img
    fastboot flash system_ext system_ext.img
    fastboot flash system system.img

    When i try to boot into the recovery screen or fastbootd ("fastboot reboot fastboot"), I get this text:


    Not sure how else to execute the "critical" flashes
    Maybe I should give up and try to send it to OnePlus for repairs?
    Yeah, I don't really know. I didn't get that, it just allowed me to flash them. Sending it in is probably the safest bet although unlocking the bootloader might've voided the warranty. If nothing else someone else here might know how to fix things. Sorry I could help.
    1
    thanks for the update,
    but i can't acces oxygen updater because the one plus is my only android phone in the house. Is there any other way to download a working OTA of oxygen?

    super thanks for all the help so far
    Check the link on the bottom, its official OTA i downloaded from the Oxygen updater 👍🏻
  • 3
    ...hello,

    first things first: ...you have to unlock your bootloader for get this working ...you will need Magisk and default ADB and fastboot tools ...I won´t get into the bootloader unlocking part or essentials

    ...I suggest getting "Oxygen Updater" at Google PlayStore and download your FULL rom ...maybe it will complain about the "wrong" version (India/Europe) but I know I´m in Europe and it´s a CPH2409 ...so I got the most recent full update, in my case: CPH2409_11_A.11 ...you have to download the same version as actually installed

    ...after downloading the File, get the PayLoadDumperGo from XDA Member ssssut and extract the downloaded file ...maybe you will need to add "liblzma-5.dll" to the directory ...I think you will manage it by yourself ...you will only need the "boot.img" and "vbmeta.img"

    ...copy the boot.img to your phone and patch it with the usual Magisk method (install / choose file) and copy back the resulting magisk_boot.img to your pc.

    ...now the tricky part ...and yes, I got the "broken Boot/Recovery Image Screen" and yes I was scared for just a few seconds ...but I solved it and here is how:

    reboot your Device to fastboot mode (unlocked) and type:
    Code:
    fastboot flash boot .\magisk_boot.img

    DO NOT REBOOT NOW!!!

    ...you will have to flash vbmeta.img like this:
    Code:
    fastboot flash --disable-verity --disable-verification vbmeta .\vbmeta.img

    ...now it´s time to reboot and when it´s done just start up Magisk Manager and finish the setup and you´re done ...simple as can be :D

    ...best regards

    derdoktor667
    2
    I tried all of the above but failed huge. Now my phone is bricked I think, it keeps getting started in either bootloader or the message that the phone is corrupted. I found a working TWRP 3.7.0_12Beta_v1 but I can only use it to install magisk and nothing else will pass.
    I tried the origional boot.img that i got off my phone when it was working but if i try to install it with TWRP it fails. I found some boot.img online that matches the phone but they also fail.

    Can someone please help me. I'm currently stuck with an expensive paper weight.
    Thanks to the kind people at the Nord ce 2 ite telegram group I managed to find a way. I got it running again perfectly fine now.

    So what went wrong:
    My partition table was f*cked, so i couldn't flash any more. I also couldn't go into the "fastbootd" (to flash critical partitions) and my touchscreen didn't work.

    !!! Important !!!
    • These are my steps, it can always be different for you so dont blindly copy them
    • If you tried to root and something is wrong or looping etc. > FIRST TRY TO CHANGE THE SLOT TO A/B BEFORE FLASHING ALL KINDS OF STUFF LIKE I DID!!!
      (the other slot should still be clean and bootable)
    • My model (CPH2409)
    • The OTA I used is the A14 one
    • If the phone doesn't get detected in bootloader, fastbootd or Recovery: try the other slot a/b
    • delete COW files/partitions in fastboot enhance
    • always enable logging in fastboot enhance
    • fastboot enhance also has a payload extracter build in if you need a single img
    • If using a external SD card check if its fat32, if so format it to the other fat one (fat32 wont allow single big files)
    Key combos:
    • POWER + VOL UP = recovery/fastbootd
    • POWER + VOL UP + VOL DOWN = bootloader/normal fastboot\
    • VOL+UP+VOL DOWN + INSERT CABLE = edl mode (If an MSM tool ever gets released)

    The solution

    first:
    1. download the latest OTA (preferably via oxygen updater)
    2. download fastboot enhance (Ui makes it convenient and it can flash an entire payload.bin)
    3. download the TWRP from spector0
    4. extract the vendor_boot.img and dtbo.img from the downloaded OTA
    5. boot into the bootloader
    6. flash vendor_boot.img and dtbo.img with fastboot enhance
    7. flash the twrp.img from spect0r
    8. reboot to recovery
    Now I got Into the TWRP recovery screen and my touch screen was working again. Using TWRP I was able to reboot into fastbootd again. but my partition table was still messed up so I couldn't flash the super imgs properly (system, system_ext, etc).

    To fix this I needed a TWRP back up, restoring this will repair the partition table too:
    1. Download twrp back up
    2. extract the zip/rar if archived
    3. put the extracted back up folder on your phone somewhere where TWRP can reach it (I used an external micro sd)
    4. In TWRP go to restore
    5. Select the back up (if sd: select storage > select the mircroSD)
    6. select the twrp back_up
    7. restore the back up
    8. not sure if needed but I rebooted to be sure
    The partitions table should now be fixed. Now to restore the system/OS:
    1. boot into fastbootd/recovery
    2. open fastboot enhance (should show under basic properties which slot and if yoru'e in fastbootd)
    3. check: show logs & Ignore unknown Partitions
    4. flash the entire payload.bin file (from the downloaded OTA)
    5. after its done, check the logs for which partitions failed (probably most starting with: "my_")
    6. in fastboot enhance (fastbootd): partitions > Create > *name of failed partition* size: 12000b > ok
      (size will automatically be adjusted when flashing)
    7. Check the logs if nothing failed
    8. reboot to system
    9. You should now get into the setup screen
    My phone is now working again! yay! 🥳🥳🥳

    Once I made a back-up of my clean twrp I'll link it here and the OTA too if possible.

    OTA LINK

    TWRP-backup
    2
    Epic Guide successfully managed to root my phone.
    Thanks for sharing the how to. <3
    2
    Comfirmed working over here, many thanks for the instructions :)
    1
    Thanks for the info but this the wrong phone for this forum
    OnePlus Nord CE 2 5G https://www.gsmarena.com/oneplus_nord_ce_2_5g-11269.php ie. chipset: MediaTek MT6877
    OnePlus Nord CE 2 Lite https://www.gsmarena.com/oneplus_nord_ce_2_lite_5g-11344.php ie. chipset: Qualcomm SM6375

    ...I´m not sure ....the Nord 2 CE lite is not listed at the moment ....I chose the closest match ;)