General Nord20 GN2200 {ROOT}10100010100101010101100

Search This thread

Natesu53

Member
Feb 3, 2023
47
4
OnePlus Nord N20 5G

Right here is the link to the tool I used

Once I figure out how to reduce the size of the partition, or make more available space to flash it . The moment it successfully flashed you'll have true root privileges. Change your boot animation. Create you own boot animations. Edit and delete system apps that are useless. I have true root privileges on my_product.img. I haven't tried the rest of the partitions . The smaller partitions seem to work I've only tried system image and my_product.

But anyways the rest of the partitions are tied to system.img when I tried to use a custom boot animation it just reverts to a android boot . Since my_product is under the system. When I try to swap out animation with the carriers it reverts to one plus.

Once you root there is only a limited amount you can do with your rooted device having a read only file system.
 

Natesu53

Member
Feb 3, 2023
47
4
OnePlus Nord N20 5G
Note if you're new to this flash them like this .

Fastboot flash boot boot.img

Fastboot flash system system.img

Fastboot flash vendor vendor.img

"Fastboot flash product_a product.img"
"Fastboot flash product_b product.img" - flash both slots manually

"Fastboot flash product product.img" -flashes to either active or inactive slot.

"Fastboot flash --slot all keymaster keymaster.img" flashes to both slots at the same time...
 
  • Like
Reactions: termux4life

termux4life

Member
Jan 27, 2023
12
3
Note if you're new to this flash them like this .

Fastboot flash boot boot.img

Fastboot flash system system.img

Fastboot flash vendor vendor.img

"Fastboot flash product_a product.img"
"Fastboot flash product_b product.img" - flash both slots manually

"Fastboot flash product product.img" -flashes to either active or inactive slot.

"Fastboot flash --slot all keymaster keymaster.img" flashes to both slots at the same time...
If I have the exact same model and coming from the same android 12 11_C.10 can't I just flash your patched boot.img to gain root?? Reason I ask is because I had android 11 rooted but I forgot to turn off automatic update. So it did one update to Android 12 (11_C.10) and I realized I lost root so I turned off updates so no more cpuld come through. I've been searching for 11_C.10 boot.img so I could patch it. Now since your upload I don't need to patch it I can just flash it correct? Thanks in advance and great job capturing the OTA like you do.

Here is the link to all the partition.img's


I've even included a patched boot.img , and the unpatched version is in there .

Ready to download and flash.
So I can flash your patched boot.img correct? Here is what I have now. Screenshot_2023-02-13-02-53-21-20_1f7d930ac4546e961acbbe2ed3d9ab7f.jpg
 
Last edited by a moderator:

Natesu53

Member
Feb 3, 2023
47
4
OnePlus Nord N20 5G
If I have the exact same model and coming from the same android 12 11_C.10 can't I just flash your patched boot.img to gain root?? Reason I ask is because I had android 11 rooted but I forgot to turn off automatic update. So it did one update to Android 12 (11_C.10) and I realized I lost root so I turned off updates so no more cpuld come through. I've been searching for 11_C.10 boot.img so I could patch it. Now since your upload I don't need to patch it I can just flash it correct? Thanks in advance and great job capturing the OTA like you do.
Yes you can, if it's the same version then yes you can flash my patched boot image to gain root access.

It's yours

Now if it were a different version. It would possibly brick your phone.

...

Hey dude with the same version as me ,or anybody. Can someone please do me a kind favor . So I deleted partitions... I need someones logs. I need someone to " adb reboot boot loader " . Into fastboot. And then once in fastboot. " Fastboot reboot fastboot " into fastbootD . Then a " fastboot getvar all " I need a terminal log of all the partition sizes. Copy and paste everything after " fastboot getvar all " ...

I need all these logs please.

I'm trying to test something I'm trying to install like lineage os , or pixel experience, and so on. I want to delete some partitions to make room for the custom os . If it doesn't work I wanna recreate the partitions .
 

Attachments

  • Screenshot_2023-02-13-08-15-23-30_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    Screenshot_2023-02-13-08-15-23-30_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    90.2 KB · Views: 30
  • Screenshot_2023-02-13-08-14-59-05_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    Screenshot_2023-02-13-08-14-59-05_fc704e6b13c4fb26bf5e411f75da84f2.jpg
    75.6 KB · Views: 32
  • Screenshot from 2023-02-13 09-50-47.png
    Screenshot from 2023-02-13 09-50-47.png
    163.7 KB · Views: 31
  • Screenshot from 2023-02-13 09-50-40.png
    Screenshot from 2023-02-13 09-50-40.png
    149.5 KB · Views: 27
  • Screenshot from 2023-02-13 09-50-57.png
    Screenshot from 2023-02-13 09-50-57.png
    120.4 KB · Views: 24
  • Screenshot from 2023-02-13 09-50-29.png
    Screenshot from 2023-02-13 09-50-29.png
    133.4 KB · Views: 30

rlilbun1

Member
Oct 14, 2014
6
0
i am still bricked at the moment but if these .imgs you posted work ill gladly pull whatever you need. ill keep you posted

Here is the link to all the partition.img's


I've even included a patched boot.img , and the unpatched version is in there .

Ready to download and flash.
having trouble downloading. it lets me view but when i try to download a copy i get nothing its wierd
 

Natesu53

Member
Feb 3, 2023
47
4
OnePlus Nord N20 5G
Another update , so I bricked my phone , but 🤯

I keep bricking it messing with stuff on it . tryna get a custom os. I also have a revvl 6 pro .which I'm currently on . So my revvl 6 pro has has a super.imh partition which contains vendor product and system. In the payload that I extracted for the nord n20 gn2200 there was no super.img in the update . I didn't think it even had a super .omg ...img. but playing around with fastboot , and fastbootd . I corrupted my super.img partition idek if it's a image, but it's a partition. So I corrupted it . I hit " fastboot erase super " " fastboot delete-logical-partition super " blah blah blah . There was no way I was getting a new super.img/partition. Playing around with commands , and lots of research. Trying to figure a way to repair the super or recreate it . Just studying how all of it's made up. Cause it's got to be a way to modify everything. They let you right.

So that's a lot of work to do to figure out what goes in super.img cause I never had a physical/digital copy of it to mount it ect... Recreations********* So I found a Unofficial TWRP on the web . I tried to do this before it didn't work . But anyways . I named the TWRP whatever they named it to . changed it to TWRP.img lowercase TWRP flashed it to my boot_b slot I switched the active to b it boot " fastboot reboot" right into team win recovery project.

I'm taking logs of everything.

But anyways I can upload a video for proof this TWRP not Official works on Nord gn200 , and maybe other OnePlus devices

I don't know what I did I tried to do this before It didn't work .
 

Attachments

  • IMG_20230213_010544.jpg
    IMG_20230213_010544.jpg
    1.1 MB · Views: 20

Natesu53

Member
Feb 3, 2023
47
4
OnePlus Nord N20 5G
It couldve been cause I corrupted super . Maybe not. I most definitely got it done tho . Maybe it's cause you do have to change the name to twrp.img whatever TWRP you download. It has to be meant for your device tho.

thats the exact same thing mine shows were you able to recover?
Yes I keep recovering it somehow

Someway

But anyways I can post a video here if it lets me of the physical phone with TWRP.

Or send it via . Whats that app that you can message on. That I gotta download on my revvl 6
 
Mar 18, 2023
6
0
Hey All,

I managed to install TWRP to boot_a partition, boot TWRP, extract my firmware off the phone as a backup called boot_b.img (b is my active slot) and patch boot_b.img with Magisk. I am too scared to flash the patched boot_b.img over boot_b partition so I am trying to flash the patched boot_b.img over the boot_a partition which currently has TWRP. However, when I try to boot boot_a partition where TWRP was, I get a boot loop. A couple questions:
  1. What am I doing wrong?
  2. Why do we have to flash both boot_a and boot_b at the same time?
  3. Should I be flashing vbmeta_a also? I am using the attached vbmeta.img and flashing with “fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img”
  4. When I try to flash vbmeta_a, fastboot flash says it uploaded 0KB. Any idea why? DDing to it from TWRP and then rereading the device I just DDed to, shows that DD didn't write anything.

Version Info:
android 12
Build: GN2200_11_C.11 Kernel:5.4.147-qgki-ga9e7460afd8c

Thanks in Advance!
 

Attachments

  • vbmeta.img
    256 bytes · Views: 7
Last edited:

SayntzEcho

New member
Jun 30, 2022
3
1
I got you . And the thing about twrp . You gotta flash it to your recover.img. it replaces your recovery. I've flashed it to my boot.img , and that's what bricked my phone.

And Nord doesn't have an official twrp that works. And I'm not seeing any recovery.img partitions.

Once I upload to Google drive . I will upload the link to all the images for download. I just need set my computer down and let them upload it'll take a lil time .
Has anyone got it yet? I'm gonna try later, just got a T-Mobile branded GN2200. I'm thinkin recovery is gonna have to be flashed to the inactive part. I remember the 7pro had a way to dual ROM boot the parts and still have a working recovery with Orangefox I believe.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    You just have to flash the unofficial twrp to your boot partition then once in TWRP, flash your stock boot image to your boot partition once more and without rebooting, go to the advanced menu in TWRP and choose flash current TWRP
    1
    You initially flash TWRP to your boot partition while in fastboot since the recovery is now located in the boot partition.. then once booted straight into TWRP, you wanna flash your bone stock boot image back into your boot partition, almost as if you were be resetting it so to speak.. then under the advanced tab in TWRP, choose flash current TWRP to splice the custom recovery back into your boot partition because uf you didn't do this then it'd really start causing problems if you decide to obtain root by way of flashing magisk..

    It's a bit convoluted but it's the state of chaos we currently find ourselves with this device

    So double flash either or as long as you make it the boot.img? Dammmmmm, now I'm interested in ****in around with the other. a/b sucked when they first started dual, but now I love it. Trying to pull the radio for someone ATM but it keeps getting fragmented. I've even done full dumps. TG4 payload dumper.
    1
    Hey All,

    I managed to install TWRP to boot_a partition, boot TWRP, extract my firmware off the phone as a backup called boot_b.img (b is my active slot) and patch boot_b.img with Magisk. I am too scared to flash the patched boot_b.img over boot_b partition so I am trying to flash the patched boot_b.img over the boot_a partition which currently has TWRP. However, when I try to boot boot_a partition where TWRP was, I get a boot loop. A couple questions:
    1. What am I doing wrong?
    2. Why do we have to flash both boot_a and boot_b at the same time?
    3. Should I be flashing vbmeta_a also? I am using the attached vbmeta.img and flashing with “fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img”
    4. When I try to flash vbmeta_a, fastboot flash says it uploaded 0KB. Any idea why? DDing to it from TWRP and then rereading the device I just DDed to, shows that DD didn't write anything.

    Version Info:
    android 12
    Build: GN2200_11_C.11 Kernel:5.4.147-qgki-ga9e7460afd8c

    Thanks in Advance!
    You should also try:

    fastboot flash --disable-verity --disable-verification vbmeta_system_a vbmeta_system.img

    fastboot flash --disable-verity --disable-verification vbmeta_vendor_a vbmeta_vendor.img

    fastboot flash --disable-verity --disable-verification vendor_boot_a vendor_boot.img

    If that still doesn't work then try switching slots after flashing and worst case scenario just format your data partition and try again
    1
    You initially flash TWRP to your boot partition while in fastboot since the recovery is now located in the boot partition.. then once booted straight into TWRP, you wanna flash your bone stock boot image back into your boot partition, almost as if you were be resetting it so to speak.. then under the advanced tab in TWRP, choose flash current TWRP to splice the custom recovery back into your boot partition because uf you didn't do this then it'd really start causing problems if you decide to obtain root by way of flashing magisk..

    It's a bit convoluted but it's the state of chaos we currently find ourselves with this device
    Aight cool. Yeah I just wanted to make sure it wasn't like the 7 & 8 where you had to boot straight into recovery from Fastboot then flash from recovery..... Has anyone tried fukin around with some of the more flexible recoveries like 🍊🦊 or Pitch Black? SkyHawk is always a thought too. 🧐 Damn, now I'm gonna be runnin it in my head all day, till I'm done making the donuts.
  • 1
    I managed to capture a full ota, and a --diff-incremental ota...
    well, would youliek to share your capture or you just gonna flaunt it? lol.. and were you able to achieve root and succesful boot thereafter ?
    1
    well, would youliek to share your capture or you just gonna flaunt it? lol.. and were you able to achieve root and succesful boot thereafter ?
    Yes sir

    I was able to capture ota extract the "payload.bin" get the boot image patched it with magisk app . Then I flashed it using fastboot on the computer.

    I booted up the device installed root checker and it worked.
    1
    I'm trying to show you but it won't let me post the pics cause too much too process with xda
    I could definitely use a copy of the recent OTA mine is soft bricked right now. in the boot_b. in boot_a I flashed twrp to boot, the touchscreen doesnt work so i use my mouse on it.
    1
    I got you . And the thing about twrp . You gotta flash it to your recover.img. it replaces your recovery. I've flashed it to my boot.img , and that's what bricked my phone.

    And Nord doesn't have an official twrp that works. And I'm not seeing any recovery.img partitions.

    Once I upload to Google drive . I will upload the link to all the images for download. I just need set my computer down and let them upload it'll take a lil time .