yashsingh1/xdaforums huggingface dataset:
[OnePlus Nord N200 5G] Maatt_OG:
it says extracting files in the log but i have eeven waited and ignored the windows pop up error saying , Program has stopped working, we will let you know if theres a solution, but it doesnt proceed any further.

AND... DO NOT USE MSM TOOL AFTER CONVERTING. modem and core-nhlos and a few other partitions are a bit different along with the hardware versions and all and youll bootloop.
[OnePlus Nord N200 5G] Maatt_OG:
as for memory, i am running pretty low tbh....
[OnePlus Nord N200 5G] Link575:
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
[OnePlus Nord N200 5G] katooom:
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.

We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.

Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
[OnePlus Nord N200 5G] katooom:
And the only reasonable explanation for this is that among my many confused attempts to make things work this was the time that I did not actually do the backup, just pressed the start button. I would hate to think that I made such a ridiculous blunder but what else could it be. Oh my .....
[OnePlus Nord N200 5G] scanman0:
You need to have enough memory free for the program to unpack the .zip file in ram. If Windows is crashing the process with "program is not responding" then your pc (or is it a vm?) does not have enough memory.
[OnePlus Nord N200 5G] scanman0:
Lineage has one build that is compatible with both versions and reports that either is DE2117.
[OnePlus Nord N200 5G] scanman0:
I have updated the guide to reflect that you need to run as administrator on Windows 7 and to run the windows 7 .exe file.

I have only tested under Windows 10 and Windows 11 and the program demanded administrator mode to run.

The msmtool always dumps to the root of the working system boot drive that is usually C:

I made a screen shot of the F8 windows as you must select the boxes and place the password to place the tool in the backup mode.

I never said in the guide to look at the phone when in EDL mode as the screen is black.

I have updated the guide to inform people that are not familiar with EDL mode to expect that it is blank.

This is the reason I had people go to EDL mode with the pc with adb is the fact that it is a blank screen mode and people can be confused if the phone is in EDL or off.

I cannot tell by your condescending comments if you actually did the F8 procedure correctly to place msmtool in backup mode.

There is no indicator before it starts (other than the window closing without an error) and the tool will indicate as shown in the screenshot that it is "Reading back <Partition name>" as it reads the partitions from the phone.

If you simply press start as you implied you "tried" the tool will flash the phone to default factory state and NOT do a backup.

You do realize I wrote this guide to try to help people and cannot test every possible configuration as I don't have Windows 7 anymore.

People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
[OnePlus Nord N200 5G] Link575:
Got it, thanks.
[OnePlus Nord N200 5G] katooom:
Whoa, I have to apologize for making you think that I was in any way critical or dissatisfied! I was merely making fun of myself for messing up the process in spite of how well you explained it. I actually hoped that you would be amused by my errors and the silly reasons that I made them. It is deeply upsetting to me to have offended someone who puts so much effort into helping. I can only apologize again for expressing myself so poorly.
[OnePlus Nord N200 5G] CmdrCrichton:
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
[OnePlus Nord N200 5G] scanman0:
Nothing dumb about this question!

I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware

And put warning to only install Lineage with Android 11 firmware.

I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:

https://xdaforums.com/t/downgrade-u...android-11-before-installing-lineage.4488485/
[OnePlus Nord N200 5G] CmdrCrichton:
After completing this, would it be possible

You are awesome! Thank you!
[OnePlus Nord N200 5G] Link575:
Hey I think I may have found little error in the guide. You say to hit start after doing the firehose readback menu, but hitting start just factory reset my phone. Did you mean to click the new button that says 'read back'?

Edit: I just went for it, read back gave expected results, but now I'm stuck at Fastboot enhance. It says to click "reboot to fastbootd" but once I do that Fastboot enhance just freezes up and doesn't recognize the phone unless I boot back into normal fastboot. Am I doing something wrong? I know when i run adb reboot fastboot it actually brings to fastbootd so I'm not sure if you actually mean fastbootd or normal fastboot/bootloader. I'm sorry if this should be simple.

Edit2: Got it to work on laptop but would still be interested if you know why it was freezing on other computer so I can maybe fix it. Any way, did whole procedure and when the phone booted up there was no more Tmobile splash screen, and build said it was de2117 fw but under about phone it said the model was still de2118, is this normal? Sorry for all the edits and info.
[OnePlus Nord N200 5G] scanman0:
Are you using Windows 7, a very old computer with very limited ram, or a VM?

It is starting to look like Fastboot Enhance is running out of memory for some people with very old computers. You're the first person to have problems with the button to switch modes from fastboot to fastbootd. You should be able to toggle back and forth without any issues.

Obv. wait till till phone reboots into new mode and screen refreshes and shows it's in now changed mode (15-20 seconds) before you hit it and change mode again. You should also hear the usb disconnect and connect sound on the PC.

Did you flash the Android 12 firmware directly or flash the Android 11 firmware and let the phone upgrade from A11 to A12?

I cross flashed all my phones before A12 was released, so I am thinking now that the OTA update from A11 to A12 was what actually caused the re-write of the initial XBL (ELF) to DE2117. (see page 5 of PDF in link)

All my phones are 100% converted as DE2117.

I had already re-written the guide to have people flash the final Android 11 firmware and do the Android 12 update OTA so people can just stop if they want to stay on Android 11 for Lineage.

If you use the OP downgrade flash tool and then take the Android 12 OTA update, we will know for certain that this is a required part of the complete conversion process.

https://xdaforums.com/t/downgrade-u...d-11-before-installing-lineage.4488485/unread

View attachment 5704571View attachment 5704573
[OnePlus Nord N200 5G] Link575:
No I'm using Windows 10 but I do only have 6gigs of RAM. It is an old computer, perhaps that is the issue.

Yea I was waiting, the program just always stalled after switching to Fastbootd. Memory issue above may be what caused it but I feel like 6 should still be enough.

I followed the guide until the end and then chose to flash the final DE2117 OTA of 11 and then went straight to Lineage. Do you suggest flashing final DE2117 OTA of 11 again through Fastboot Enhance, allowing update to 12, then proceeding to downgrade back to 11 and then finally Lineage? I can try that later today if so.

Edit: Ok so I flashed Final OTA of 11 again through Fastboot Enhance. It couldn't resize vendor_b and now can only boot into fastboot/bootloader and fastbootd, no recovery. If I switch to slot a it can do fastboot, fastbootd and lineage recovery. Any suggestions?
[OnePlus Nord N200 5G] scanman0:
Did you check for _cow files and delete them before you flashed?

_cow files are the main reason that there is a space issue that would prevent the flash from completing.

I would re-flash Lineage from the Lineage boot loader as you did before and get the phone working on Lineage on slot a.

Then you could manually delete the slot_b files and then switch to slot b and try flashing A11 oem on slot b again.

Do not reboot phone or exit Fastboot Enhance until this completes successfully.

If you still have space issues, you can switch back to slot a and go back to Lineage again.
[OnePlus Nord N200 5G] Link575:
No _cow files were there. I'll see if I can flash Lineage again. When you say manually delete slot_b files do you mean delete all the partitions that show up? Also, if nothing works would the back up originally made with the MSM Tool be of any use and if so how would I go about using them? thanks

Edit: Managed to switch slot to a and follow lineage installation again. Slot A is now running Lineage correctly but now I have no idea if the phone is fully converted or some sort of frankenfirmware. I'll wait until I hear back but I'm assuming I need to use Fastboot Enhance, click switch to slot b (do I just click so it says active slot b? or do I click that and then click to enter fastbootd? im a little hazy on this part), then erase all partitions on b?, and then flash A11 like you said.
[OnePlus Nord N200 5G] scanman0:
The saved msmtool images can be restored with root or fastboot. The backup includes critical user data that can be restored if you somehow manage to delete everything and hard brick the phone. This phone cannot actually be hard bricked as the EDL mode is always available and burned into the chipset and with Sahara/Firehose tools, you can load the .elf file and then re-flash boot.img to re-boot into and re-flash normally with:

GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)

Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - bkerler/edl

github.com

If you can open adb shell and reply with a .txt file showing your current partitions, it would help in determining why there was not enough space when you were re-flashing the oem image to slot b. Here is an example of the current partitions while on latest A12 image as an example:
[OnePlus Nord N200 5G] Link575:
Ok here's a file with the partition info like you did.
[OnePlus Nord N200 5G] scanman0:
I edited the file to combine the data from the two commands and don't see any differences between slot_a and slot_b common file sizes or anything that jumped out at me like _cow files or bloated logs. Attached is the edited file. Mabe someone else can see something I'm overlooking.

You did do a user data wipe before you tried to write OEM to slot b, right?
[OnePlus Nord N200 5G] Link575:
Appreciate that. I'm assuming everything was clean, I followed the guide exactly. I used MSM Tool, setup the phone to unlock the bootloader and then attempted to use Fastboot Enhance to flash final A11. Am I wrong in assuming MSM wipes user data?
[OnePlus Nord N200 5G] CmdrCrichton:
Excellent guide! This worked exactly as advertised and was pretty straight forward. I flashed OEM Android 11 as mentioned in the guide. Metro bloatware and flash screen were removed even though it still said DE2118. On top of the bloatware being gone, what confirmed it was OEM is when updating the update version was DE2117. After updating to Android 12 via OTA the device info changed to recognize it being DE2117 now. I decided to install lineageOS too so I followed your downgrade guide too, which also worked perfectly. Installed lineage which is working perfectly and also says DE2117. Great guide and much appreciated! Will be doing a second device either this evening or tomorrow now that I’ve seen how straight forward it is. Thanks!
[OnePlus Nord N200 5G] scanman0:
I had already converted my devices before A12 was released and they are all fully converted and all took the OTA DE2117 update to A12. It appears that the EDL boot area is re-written during the OTA upgrade from A11 to A12. Now that this is proven, I'm going to modify the guide so that everyone completes the OTA to A12 and then does the downgrade procedure if they want to install Lineage. I'll call this guide v1.1.

Thanks for posting the positive results!
[OnePlus Nord N200 5G] CmdrCrichton:
Followed the guide a second time on my second device.

First screenshot is before, 2nd is after flashing OEM, 3rd and 4th are the 2 OTA updates to upgrade to A12 (notice the versions), and final is after 12 upgrade (notice DE2117!).

View attachment 5706885View attachment 5706887View attachment 5706889View attachment 5706891View attachment 5706893
[OnePlus Nord N200 5G] Link575:
Well I'm at a loss. I have lineage running fine on slot b but I can not for the life of me get any stock firmware running again. I deleted the logical partitions in a and recreated them which solved the issue of it being unable to resize anything and the flash in fastboot enhance finished without any errors. Rebooted to recovery, wiped, and still can only boot into fastboot/d, and recovery.

I'm not sure if I should cut my losses and just stay with lineage or try to flash back to Tmobile firmware with fastboot enhance and then MSM Tool back to stock to try and start all over. Would that even work?

Edit: Ignore everything I've said I'm an idiot. I renamed the dynamic paritions without appending _b or _a for the active slot. Im back on DE2117 A11 final and about to OTA to 12. Sorry for all the hassle.
[OnePlus Nord N200 5G] scanman0:
Glad you figurred out what you were doing wrong. Good job!
[OnePlus Nord N200 5G] Link575:
Hey appreciate all the help you've been giving my. I edited the post above yours but I did end up fixing it. The initial error with resizing wasn't me but everything after It was a stupid mistake on my end. Again sorry for the trouble and thanks for remaining patient.
[OnePlus Nord N200 5G] T3CHN0T33N:
Is there something I'm missing here? My device isn't visible in EDL or Fastboot...
[OnePlus Nord N200 5G] TheGhost1951:
Drivers maybe?
[OnePlus Nord N200 5G] zahidm:
Hi, In A12 they nuked Always On ambient from Customization?

I am not having it after update to A12 in Unlocked DE2118.

And even after downgrading to A11 unable stop auto overnight update even disabling from dev mode.

Asking question out of thread subject.

Even I am dev of Nord 5G & OnePlus 6/6T but unable to figure out 😂

Edit: Now i am thinking to convert to OEM as my device already carrier unlocked, let see if I can disable updates after conversion. But i have no confirmation about Always on Display in A12 at DE2118_C..16

Also attached SS of Customization after A12 update.

Thanks in advance 🙏

View attachment 5712039
[OnePlus Nord N200 5G] T3CHN0T33N:
While I didn't install them, the same thing is happening with them...
[OnePlus Nord N200 5G] TheGhost1951:
Have the latest Platform Tools.... Are you on a windows PC? Does you PC connect to phone and show it in windows file explorer?
[OnePlus Nord N200 5G] T3CHN0T33N:
I have grabbed the version of PT previded and have installed the drivers from the device itself.

I'm not sure if this would be a problem or not, but I have ArtiicPanda's kernel...
[OnePlus Nord N200 5G] TheGhost1951:
Oh, you are getting deeper than I can go. That is why I stay with stock rims...sorry
[OnePlus Nord N200 5G] T3CHN0T33N:
I figured it out! I had to go under optional updates in windows update.... Also I see that the instructions are a bit unclear. Just to clarify: When you reboot into fastboot using adb reboot fastboot, it reboots into fastbootd not fastboot. So you need to reboot into fastboot by selecting you language of choice then advanced then reboot to fastboot. I thing there is a command, something live fastboot reboot fastboot i think...

Edit: fastboot reboot fastboot is for fastboot to fastbootd... I got it mixed up :P
[OnePlus Nord N200 5G] CmdrCrichton:
I noticed the same thing.

adb reboot bootloader

This will take you to normal fastboot.
[OnePlus Nord N200 5G] T3CHN0T33N:
I am in the middle of updating to C_17 via OTA and I'm wondering: Did OP fix their RAM management and if so, how easy is it to update via OTA with root on OEM vs LineageOS?
[OnePlus Nord N200 5G] Link575:
I haven't updated rooted stock but when I was on LineageOS update was simple, just used system updater in settings and everything worked out fine.

@scanman0 Just an FYI I downgraded from 12 to 11 after doing the convert because I was going to switch over to Lineage again but I noticed once back in 11 the About Device section once again said DE2118 even though it was running DE2117's A11 so definitely not a full conversion happening. Must be something in A12 that's causing the About Device to change and downgrading just reverts that.
[OnePlus Nord N200 5G] scanman0:
When upgrading to A12, OP is no longer a seperate software devision, and have merged 100% to a standardized Oppo ColorOS kernel that is shared with every other device using the same base architecture.

Basically, OxygenOS no longer exists after A11 and all the OxygenOS things that were not ported over to ColorOS, the A12 rom does not do the same checks to the customer data to determine it is actually a phone wiith IMEI in the non-OEM range.

You will find that after A12 update, the Engineering, Bug recording/reporting, and other dialer code software has been replaced with the Oppo apps/codes.

You can look at dialer code guides for the Oppo A53 5G as the N200 A12 is that phones firmware with a lower quality camera, less ram and then they added a few OxygenOS app's back that they could with no effort.

OP will also not allow you to join the red cable club and get the points, as they will see the IMEI is not oem and will come back with "invalid IMEI". Other than that, thee OEM firmware works 100%.
[OnePlus Nord N200 5G] Link575:
I see, that's interesting. So in other words it's basing the new About device section on what the firmware version it upgraded from, ie. whether it sees 2117 or 2118 whereas A11 was based on IMEI?

Also off topic and obviously you can't know definitively, but do you think Lineage for this phone will eventually allow install from 12 rather than 11?
[OnePlus Nord N200 5G] scanman0:
It appears this way.
[OnePlus Nord N200 5G] Kifett:
I have a De2117AA device even if it was bought in the us trough bestbuy.

Can I use this guide to convert it to the oem us version to get de2117?
[OnePlus Nord N200 5G] scanman0:
Please make a full backup with msmtool before you try anything.

What is your phone not doing that you require of it?

The Int'l phone supports FM radio without any hacks and also has 2 fully supported SM card slots.

Is it US VoWIFI and/or VoLTE that are not working?

I would really love to get ahold of the FM tuner APP from your Android V12 rom from that phone to see if it can work on the US OEM version.
[OnePlus Nord N200 5G] rrjudice:
Thank you scanman0 for one of the best written guides I have followed on xda yet! However, I still think I managed to miss something. After running the command in step 23 and receiving "success", the "OEM Unlocking" is still greyed out. Since no one else has reported having this issue, I'm sure I have missed something, but I can't figure out what it is. I hope someone can reorient me in the right direction.
[OnePlus Nord N200 5G] Link575:
If your phone is not connected to wifi or cell network I don't think it will ungrey. At least in my experience I had to let it have wifi for a couple minutes then it was ungreyed and I turned data back off.
[OnePlus Nord N200 5G] rrjudice:
Thank you so much!! That was all I needed to get over that hump. I finished the conversion. Good bye to Tmobile bloatware and that annoying jingle.
[OnePlus Nord N200 5G] rrjudice:
I still have one more problem if anyone can help. After converting to the DE2117 firmware, I finished setting up the phone with all my apps and everything that I wanted. I installed my T-mobile sim card, and could not connect to any network. I rolled back to the A11 firmware as if to install lineage OS, and still failed to connect to the t-mobile network. Full disclosure: I had never activated a sim in this phone before converting it to OEM. ( I had been waiting for better deployment of the 5G network) Do I need to MSM back to the original DE2118 firmware and start over, or is there a simpler solution? Also, is this exploit still viable or has t-mobile blocked it in a recent update? TIA
[OnePlus Nord N200 5G] michaelwaycraig67:
maybe apn or youll get service during activation when i inserted my straightalk into my unlocked version i got no service until i activated and added a plan
[OnePlus Nord N200 5G] rrjudice:
Thanks, but my sim is already activated on T-mobiles network in my other phone. I'm just seeking advice about the remaining viability of this exploit and whether I can fix my problem without starting over.
[OnePlus Nord N200 5G] weirdfate:
assuming i can relock the bootloader not rooting and staying OEM stock
[OnePlus Nord N200 5G] kiyip:
Is anyone having issues downloading these files?
[OnePlus Nord N200 5G] _mrbrown_:
Are these files available from another place? I don't think androidfilehost.com paid their bills.
[OnePlus Nord N200 5G] squirms00:
Hey how do I flash the Backup? I did the Readback thing.
[OnePlus Nord N200 5G] Galaxy-Geek#1:
I just purchased a OnePlus Nord N200 5G, I am waiting on my bootloader token to get it unlocked. Should I follow this guide to change it from T-Mobile to the OEM? Then I can root it correct?
[OnePlus Nord N200 5G] Tyreethetruth:
Bump
[OnePlus Nord N200 5G] kiyip:
I had my bootloader unlocked, after flashing the original android 11 firmware using the msm tool I am no longer able to oem unlock the bootloader. I uninstalled the qualcomm app

adb shell pm uninstall --user 0 com.qualcomm.qti.uim

But I still don't have the option in settings.
[OnePlus Nord N200 5G] Link575:
Phone needs some sort of connection to internet for a very brief time before the oem unlock option gets ungreyed out after running that command. Then you can turn of the connection again so it doesn't download any updates.
[OnePlus Nord N200 5G] kiyip:
I connected and still I can't turn on oem unlocking. It also finished downloading the update.
[OnePlus Nord N200 5G] Link575:
You are talking about the option in developer options right? That should ungrey out after being connected to the internet for a little. If it's not perhaps you did not run the adb command correctly? It should be toggle-able after that, if it isn't then either something didn't run correctly or perhaps an update you took before reverting with the MSM tool did something to block it.
[OnePlus Nord N200 5G] X_shinobi.apk_X:
im a bit confused, the guide specifies 11.0.1.7 but the file comes with 10_O.0.7. am i missing something?
[OnePlus Nord N200 5G] kiyip:
Yes, I am talking about the seeing in developer options. Is the command from above not the correct command? I haven't actually updated anything yet. So I think it is unlikely that is the case, but it could definitely be possible.
[OnePlus Nord N200 5G] scanman0:
The file name is confusing, but this is the file name that OP gave the ROM.

As a rule, I don't rename any files from a vendor as this causes MORE confusion.

When you flash it, you will see it is the correct version.

I have not figured out what that internal file name actually means myself.