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

Search This thread

sleepybird

Member
Sep 10, 2006
14
1
Hello everyone, I'm a newbie and need help. I tried the commands above but got the below error messages and now my Nord is on endless loop. I can boot into fastboot or recovery and that's about it. Please help me and I greatly appreciate it.

C:\Users\platform-tools>fastboot create-logical-partition system_a 0x6342E000
Creating 'system_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot create-logical-partition system_ext_a 0x55225000
Creating 'system_ext_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot create-logical-partition system_ext_a 0x55225000
Creating 'system_ext_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot create-logical-partition system_ext_a 0x55225000
Creating 'system_ext_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot create-logical-partition product_a 0x6BD93000
Creating 'product_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot create-logical-partition vendor_a 0x3ED70000
Creating 'vendor_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed
 

sleepybird

Member
Sep 10, 2006
14
1
Hello everyone, I'm a newbie and need help. I tried the commands above but got the below error messages and now my Nord is on endless loop. I can boot into fastboot or recovery and that's about it. Please help me and I greatly appreciate it.

C:\Users\platform-tools>fastboot create-logical-partition system_a 0x6342E000
Creating 'system_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot create-logical-partition system_ext_a 0x55225000
Creating 'system_ext_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot create-logical-partition system_ext_a 0x55225000
Creating 'system_ext_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot create-logical-partition system_ext_a 0x55225000
Creating 'system_ext_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot create-logical-partition product_a 0x6BD93000
Creating 'product_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot create-logical-partition vendor_a 0x3ED70000
Creating 'vendor_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed
Just to add below additional info:

C:\Users\platform-tools>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.016s]
Finished. Total time: 0.016s
 
Just to add below additional info:

C:\Users\platform-tools>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.016s]
Finished. Total time: 0.016s
fastboot oem unlock_critical
or try running the unlock command again, I think this happened to someone else.
 

ddggttff3

Inactive Recognized Developer
Dec 13, 2009
815
1,542
Minnesota
Just want to say thank you for this thread. I was able to follow the steps, and take the A12 update. Once I got on A12, I re-locked the bootloader without issue and my T-Mobile N200 now shows as an DE2117 (Unlocked model)
 
Last edited:

Metconnect2000

Senior Member
Dec 5, 2015
119
17
Moto G 5G
Just want to say thank you for this thread. I was able to follow the steps, and take the A12 update. Once I got on A12, I re-locked the bootloader without issue and my T-Mobile N200 now shows as an DE2117 (Unlocked model)
I thought someone had mentioned that you would lose the ability to get ota using this method. But looks like you are not affected by it. Is that right?
 

ddggttff3

Inactive Recognized Developer
Dec 13, 2009
815
1,542
Minnesota
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.
 
  • Like
Reactions: Metconnect2000

radekmazur

Senior Member
Sep 20, 2015
92
15
So, I reached the same point:
C:\Users\platform-tools>fastboot create-logical-partition system_a 0x6342E000
Creating 'system_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true

How do I get to create the partitions so I can convert Tmo to OEM version?
 

Metconnect2000

Senior Member
Dec 5, 2015
119
17
Moto G 5G
So, I reached the same point:
C:\Users\platform-tools>fastboot create-logical-partition system_a 0x6342E000
Creating 'system_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed

C:\Users\platform-tools>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true

How do I get to create the partitions so I can convert Tmo to OEM version?
Are you on a gsi rom by any chance?
 

pot315

Senior Member
Weird, T-mo N200

Screenshot_2022-06-21-08-40-43-57_fc704e6b13c4fb26bf5e411f75da84f2.jpg
 

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.