How To Guide Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)

Search This thread
Sep 17, 2021
38
2
OnePlus Nord N200 5G
Hey there. i'm a new XDA Member myself. i've been mostly stalking these forums for the N200 Ever since people started the root phase and twrp projects for codename HOLI. but i'm here to convert @summersofar's guide in order to make it more comfortable for windows users... (Credit to the people who helped make this happen. i take no credit as i am only posting this guide for windows users.)

Now lets get on with the process.

Requirements: Your Bootloader MUST Be unlocked. not just oem Unlocking enabled. NO. that only sets a flag in the bootloader telling the chip that the board can be unlocked. 2nd, you must have sim unlocked your phone in order for the oem unlocking option to appear, Be it t-mobile customer support via 611. or try twitter. there have been cases where users have gotten a free sim unlock from tmobile if you're a veteran customer (Veteran implies you've been with them for a couple of years now and they trust you. this isn't always guaranteed but its worth a shot honestly.) Twitter support will do. (Then unlock the bootloader permanently from oneplus's unlock token website and apply the unlock. they'll get back to you in7 business days.)

Now onto the actual process...

Make sure you first extract your stock image, You can do this by using a well known program called Payload Dumper Go. Note: you no longer need to do any sort of Mumbo jumbo in order to actually extract your stock img. You can download the stock image directly from Oneplus's support website located Here.

Step 1> Enable USB Debugging in the developer options and connect your phone. wait a couple of seconds and authorize the fingerprint on your devices screen. We can move onto step 2.

2>
Code:
/Next reboot into fastboot by typing the command below.\

fastboot reboot fastboot

3> Copy and paste these commands in cmd. (MAKE SURE YOUR COMMAND PROMPT DIRECTORY IS SET IN THE LOCATION WHERE YOUR EXTRACTED PAYLOAD FILES ARE!, or else you'll get an error saying the file cannot be found or executed.

Code:
fastboot delete-logical-partition system_a-cow
fastboot delete-logical-partition odm_a
fastboot delete-logical-partition system_a
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition product_a
fastboot delete-logical-partition vendor_a
fastboot create-logical-partition odm_a 0x37ED000
fastboot create-logical-partition system_a 0x6342E000
fastboot create-logical-partition system_ext_a 0x55225000
fastboot create-logical-partition product_a 0x6BD93000
fastboot create-logical-partition vendor_a 0x3ED70000
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img

Then reboot into fastboot once all those commands Above are executed..

Code:
fastboot reboot fastboot

Next we'll actually tell the bootloader to CREATE And delete the partitions. in order to finalize the process.

Code:
fastboot flash --slot=all boot boot.img
fastboot flash --slot=all dtbo dtbo.img
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot flash --slot=all core_nhlos core_nhlos.img
fastboot flash --slot=all oplusstanvbk oplusstanvbk.img
fastboot flash --slot=all rpm rpm.img
fastboot flash --slot=all vendor_boot vendor_boot.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash --slot=all vbmeta vbmeta.img
fastboot flash --slot=all vbmeta_system vbmeta_system.img

Once thats been done. just go ahead and execute the commands below to boot to the RECOVERY this time.

Code:
fastboot reboot recovery

Once done. Wipe your user cache and settings. you have to press two buttons to execute this. Enjoy a fully (Clean?) stock rom.

The issues and problems post installation can be found in @summersofar's guide Here.

Too long to type out all of them.
 

edale1

Senior Member
Sep 5, 2016
138
75
Free SIM Unlocking service for T-Mobile variants:
Make sure you read the prerequisites to ensure you qualify before making a request.
 

l0csta

Member
Aug 30, 2021
17
0
getting this error
Screenshot 2021-09-26 155430.png
 
Sep 17, 2021
38
2
OnePlus Nord N200 5G
If you have discord. I can help you setup an environment variable so you can run fastboot commands from anywhere on your system.

But as for this error. Make sure the extracted payload files are in the same directory as fastboot execution files and all the other stuff.

{Mod edit: Quotation fixed and two posts merged - regards Oswald Boelcke}
 
Last edited by a moderator:

l0csta

Member
Aug 30, 2021
17
0
Looks like one of them didn't unlock. I tried running fastboot oem unlock_critical but it didn't work, got an error saying the device was already unlocked.

1632702456045.png
 

l0csta

Member
Aug 30, 2021
17
0
i see... yeah that fixed the issue. I was rebooting into fastbootd but i was selecting the reboot to fastboot option from there. thanks for the help!
 

xentonix

New member
Nov 30, 2011
4
0
i see... yeah that fixed the issue. I was rebooting into fastbootd but i was selecting the reboot to fastboot option from there. thanks for the help!

Yep, I was doing same thing.
So I got it all done and I have bloat free system. YEY!
However, I did notice couple of things and would like to check with rest of you if you have same issues:
- settings -> system -> about phone: 2nd tab just says "verification" and it's missing "Regulatory labels"
- settings -> system -> about phone -> OxygenOS version: says "unknown"
- settings -> buttons & gestures --> alert slider: it just crashes (idk why this option is on when this phone does not have alert slider?)

That's what I noticed so far.
Thanks!
 
Last edited:

l0csta

Member
Aug 30, 2021
17
0
Yep, I was doing same thing.
So I got it all done and I have bloat free system. YEY!
However, I did notice couple of things and would like to check with rest of you if you have same issues:
- settings -> system -> about phone: 2nd tab just says "verification" and it's missing "Regulatory labels"
- settings -> system -> about phone -> OxygenOS version: says "unknown"
- settings -> buttons & gestures --> alert slider: it just crashes (idk why this option is on when this phone does not have alert slider?)

That's what I noticed so far.
Thanks!
yeah i'm having the first two issues as well, never really did anything with buttons & gestures so i don't know if i have the slider issue, i'll take a look when i get home. if you check summersofar's post they did say that the missing info in about phone is an issue they are having as well.
 

cognitoinc566

Member
Jan 9, 2022
7
4
can we flash T-Mobile's Stock-ROM on MetroPCS both have same model DE2118? I have unlocked bootloader, but locked SIM and 0day on Metro Network.
Yes, I accidentally bricked my bootloader locked MetroPCS model DE2118 (by going into developer options and attempting to load a GSI through dynamic system updates, which fails on a locked bootloader because GSIs aren't signed by oneplus) and I saved it by using the MSMtool for the standard T-mobile edition. Strangely, all the metro stuff is still there including the metroPCS boot animation. Now I'm just waiting on my unlock token so I can bootloader unlock and convert it to the oneplus unlocked firmware, install TWRP, and properly load GSIs.
 

darkghost568

Senior Member
Jun 29, 2012
777
175
Bethesda
Yes, I accidentally bricked my bootloader locked MetroPCS model DE2118 (by going into developer options and attempting to load a GSI through dynamic system updates, which fails on a locked bootloader because GSIs aren't signed by oneplus) and I saved it by using the MSMtool for the standard T-mobile edition. Strangely, all the metro stuff is still there including the metroPCS boot animation. Now I'm just waiting on my unlock token so I can bootloader unlock and convert it to the oneplus unlocked firmware, install TWRP, and properly load GSIs.
Yes, the ROM detects whether a T-Mobile or Metro SIM card is inserted on first boot to determine what carrier apps to load.
 

TheLoonyRebel

Senior Member
Mar 20, 2010
2,364
1,265
Amazon Fire TV
Nexus Player
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Guys, I need help.

    I have the factory unlocked version of the N200, and bricked it by trying to flash a GSI ROM and apparently doing it wrong.

    I can get into fastboot mode, but it won't boot past that point.

    Trying to flash the extracted firmware files from the payload.bin, I get messages that it can't resize partitions as needed; doesn't have enough space to flash, and so on.

    I'll post the results here shortly.

    So I downloaded the MSM flashing thingy for T-Mobile that's been shared here, but the program gives an error that it's the wrong device (because it is, technically).

    I contacted OnePlus support asking for a remote session, as I thought maybe they could give me the files and I could then share them here with you guys - but I just heard back from them after 3 days that "we can't do a remote session, wait for the next firmware update"

    So now I have a phone that won't get past fastboot mode - when I try, it loads a Qualcomm CrashDump screen.

    The commands posted above seemed to work for some files, but not the important ones like system. It can't resize the partitions as specified because, I presume there's something else taking up that space

    Is there a way to completely wipe those partitions and recreate them all with the correct sizes? I have the OxygenOS 11.0.5.0.DE17AA files.
    1
    You lose ability to flash OTA until I fix TWRP for flashing OTAs 🤷 that's all I've noticed

    But you can still update using fastboot enhanced to push the payload without factory reset 👍
    Sounds good to me! I already lost the ability to get OTAs when I rooted XD
    1
    Thanks! To confirm, the steps from the original post? I'll have to try it then.

    Correct, I followed the steps in the OP and used the 11.0.6.0.DE17AA full firmware from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161

    Once that was flashed, it took a small OTA to 11.0.7.0 IIRC, and after that, then the full OTA to Android 12 (was 3.8GB~).

    Once I was on Android 12, I just rebooted to bootloader, re-flashed the cust-unlock, and then OEM locked it.
    1
    Hey does converting to firmware to OEM version make the Oem Unlocking option Ungrayed out and Toggleable ?
    Check this post for how to un-grey the OEM Unlock option. There's a single ADB command you can use to do so.