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

Search This thread

darkghost568

Senior Member
Jun 29, 2012
777
175
Bethesda
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
If you're coming from a T-Mobile N200, how did you OTA update to 11.0.4.0.DE17AA? The above guide is only applies for a Full OTA like 11.0.2.0.DE17AA, and incremental OTA updates on a converted device fail. To flash incremental updates, you'll want to patch the images extracted from the Full OTA with the Incremental OTA via the payload_extractor, then follow the OP's guide as normal.

In any case, the boot.img for the 11.0.4.0.DE17AA and 11.0.2.0.DE17AA OOS builds are identical (check the MD5), so you can just patch the boot.img you obtain via the OP in Magisk Manager.
 

cognitoinc566

Member
Jan 9, 2022
7
4
Mine updated on the incremental OTA update just fine.
Same, I didn't even realize that was a possible issue. Although my screen said "none" and so did the processor in the about phone settings lol. Didn't bother me, I just wanted a recent base to use for flashing a GSI, and once I found pixel experience it worked so well I stuck with it.
 

mingkee

Senior Member
What happened?
Code:
Invalid sparse file format at header magic
Sending sparse 'product_a' 1/8 (262112 KB)         OKAY [  6.698s]
Writing sparse 'product_a' 1/8                     OKAY [  1.366s]
Sending sparse 'product_a' 2/8 (262128 KB)         OKAY [  6.686s]
Writing sparse 'product_a' 2/8                     OKAY [  1.340s]
Sending sparse 'product_a' 3/8 (262124 KB)         OKAY [  6.692s]
Writing sparse 'product_a' 3/8                     OKAY [  1.352s]
Sending sparse 'product_a' 4/8 (262124 KB)         OKAY [  6.700s]
Writing sparse 'product_a' 4/8                     OKAY [  1.343s]
Sending sparse 'product_a' 5/8 (262128 KB)         OKAY [  6.671s]
Writing sparse 'product_a' 5/8                     OKAY [  1.340s]
Sending sparse 'product_a' 6/8 (262128 KB)         OKAY [  6.689s]
Writing sparse 'product_a' 6/8                     OKAY [  1.355s]
Sending sparse 'product_a' 7/8 (262120 KB)         OKAY [  6.681s]
Writing sparse 'product_a' 7/8                     FAILED (remote: 'Operation not permitted')
Finished. Total time: 79.020s
 

cognitoinc566

Member
Jan 9, 2022
7
4
That's normal, that looks like a successful GSI flash to me (y)

Edit: I didn't scroll to see number 8 failed, sorry :LOL:
 

drfsupercenter

Senior Member
Aug 21, 2010
84
14
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.
 
  • Like
Reactions: sleepybird

RainGater

Senior Member
Aug 5, 2013
1,169
715
OnePlus 8T
Samsung Galaxy Tab S7 FE
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 am in fastbootd but it keeps saying that "< waiting for any device >" although I have all the necessary drivers on the system. I can do adb reboot bootloader and it works fine. From there, I can do fastboot devices and so on... It works.

But, my device is not getting recognized in the fastbood (where you see Advanced and Exit buttons) mode. I have to run the fastboot commands from here, right?

My device manager also doesn't show any device conntected when in fastbootd mode. But, it shows as an Android device when I reboot to bootloader. Any ideas?

EDIT: I have the latest fastboot: fastboot version 31.0.3-7562133

EDIT 2: The build on my Nord N2005G is 11.0.1.9.DE18CB. Does this procedure on this build?
 
Last edited:

OLDWhite

Member
Sep 23, 2014
40
2
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.

View attachment 5419699
Sorry to bother you, can you tell me exactly how to solve this problem? I had the same problem.
Deleting 'system_a-cow' FAILED (remote: 'unknown comm
and')
fastboot: error: Command failed
Code: fastboot reboot fastboot
with the same problem.
platform-tools_r31.0.3-windows.zip
 

pwag

Senior Member
Feb 14, 2011
168
26
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
Which partition do these flash to?
 

winter23502

New member
May 14, 2022
1
0
Hey, I am new to this, just got my Tmobile Nord 200. Current OS is 11.0.1.11 DE18CB. I can't find any boot image or firmware to download to extract the boot image so I guess I need to use this process to convert the firmware to the latest stock firmware. I got the latest firmware from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
11.0.6.0.DE17AA (Updated on March 23, 2022)
When I use the Payload-dumper-go Tool to exact the payload.bin, i found that I am missing three files listed in the command.
I am missing the following files: ( I am afraid this will result in some error when the commands are executed). Any one can help with this?
core_nhlos core_nhlos.img
oplusstanvbk oplusstanvbk.img
rpm rpm.img

Attached is the screenshot of all the files from the extraction:
1652550479309.png
 
Sep 17, 2021
38
2
OnePlus Nord N200 5G
I have not been active for quite some time now. I see however that people have started having issues.

I haven't touched my oneplus in a couple of months, so I'll need some time to unfuck and edit my op,
 

sleepybird

Member
Sep 10, 2006
14
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.
Hi, i think I have exactly the same issue as you. Were you able to fix?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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.
  • 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.