How To Guide Rooting OnePlus Nord 2 CE lite

[PsYk0n4uT]

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]

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]

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

 

[DerDoktore]

...V14 with December Patches is out now for Nord 2 CE lite 5G (EU) ...downloaded and patched with Magisk as usual ...no problems

best regards

 

[keyra74]

...V14 with December Patches is out now for Nord 2 CE lite 5G (EU) ...downloaded and patched with Magisk as usual ...no problems

best regards

ahaha you were faster than me, i should check the "don't lose magisk" tutorial again

 

[DerDoktore]

ahaha you were faster than me, i should check the "don't lose magisk" tutorial again

...you just don't uninstall Magisk ...prepare your Image first and foo, install the downloaded update as usual ...it will restart your device but don't worry ...just don't type in your pin and restart to fastboot and flash the Magisk patched Bootimage and you're done

 

[keyra74]

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

...best regards

derdoktor667

 

[keyra74]

done i'm stupid to think i should remove magisk, followed your tuto again

 

[DerDoktore]

...all good ...I hope it will work with Android 13, as well

 

[Matz125]

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]

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]

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]

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.

 

[keyra74]

android 13 stable is out for india version. can't wait for EU

 

[TeunB]

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]

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]

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]

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]

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]

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.