How To Guide Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar) - 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.

---

Free SIM Unlocking service for T-Mobile variants:
[CLOSED][T-Mobile USA] Free SIM Unlocking Service - [OnePlus/Samsung/Google/LG/Moto]
Hello XDA, I am back at it again with the free T-Mobile network unlocks. Yep, you heard that right... 100% FREE. This service will allow you to go into your Settings and perform a network unlock. I've been doing this for over 3 years now with...
forum.xda-developers.com
Make sure you read the prerequisites to ensure you qualify before making a request.

---

getting this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

l0csta said:
getting this error
View attachment 5419571
Click to expand...
Click to collapse
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}

---

Winnower Amber said:
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.
Click to expand...
Click to collapse
Yeah I already did that before I started. I run cmd from this directory and do everything on there.

---

Add me on discord it's nullpoint#5559
Is your bootloader fully unlocked from the bin file OnePlus support gave you?

---

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.

---

Having same problem, if you guys figure out what's the issue please let me know.

---

what he is implying is. make sure you reboot to fastbootd. you can tell your in this mode when you actually have an advanced and exit option. this implies your in the actual bootloader

---

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!

---

l0csta said:
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!
Click to expand...
Click to collapse
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!

---

xentonix said:
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!
Click to expand...
Click to collapse
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.

---

I'm honestly just going to make a zip file for this and upload it here, via Google drive.

---

Winnower Amber said:
I'm honestly just going to make a zip file for this and upload it here, via Google drive.
Click to expand...
Click to collapse
Got that zip handy?
Getting this error in fastbootd when trying to delete or create partitions:
FAILED (remote: 'Could not open super partition')
fastboot: error: Command failed

---

Oh for the entire toolkit? I haven't gotten around to it. Been busy with school. Apologies.

---

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.

---

kdm6389 said:
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.
Click to expand...
Click to collapse
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.

---

cognitoinc566 said:
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.
Click to expand...
Click to collapse
Yes, the ROM detects whether a T-Mobile or Metro SIM card is inserted on first boot to determine what carrier apps to load.

---

Guide worked great on my T-Mobile N200. Phone feels slightly faster on the OEM ROM. Doing the OTA updates hopefully I'll get the boot.img soon so I can make a patch Magisk image for everyone for the current OEM ROM.
Current build is 11.0.4.0.DE17AA
Edit: And here they are.... this is for the OEM ROM 11.0.4.0.DE17AA working great on my end!
OEM Boot Img: https://www.androidfilehost.com/?fid=17825722713688266077
Magisk Patched Img: https://www.androidfilehost.com/?fid=17825722713688266078

---

darkghost568 said:
Yes, the ROM detects whether a T-Mobile or Metro SIM card is inserted on first boot to determine what carrier apps to load.
Click to expand...
Click to collapse
Very clever, wow. I would never have thought of something like that