Question How to downgrade N200 5G DE2118 to Android 11 from 12 - OnePlus Nord N200 5G

I have a T-Mobile OnePlus N200 5G DE2118 and want to downgrade from Android 12 to 11 (stable), how can I do this? I haven't found any relevant guides online.

[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com

Thanks

Related

REQUEST: oeminfo and cust files to rebrand CMR-W09 C567 to C432

As those affected know, C567 (US version) of MediaPad M5 is stuck at EMUI 8.0.
I managed to unlock the bootloader using the test point method (need to carefully open the device and use PotatoNV program).
However, after experimenting with a couple of Treble ROMS (pphusson's AOSP 11, for example), I decided EMUI was less buggy for me. However, I'd like to be able to upgrade to EMUI 9.1, for which I'd like to rebrand to C432 (Europe version). I understand it's possible to rebrand by changing the cust and oeminfo partitions.
QUESTION: does anyone have a method for modifying these files or can upload them if they have a C432? I understand there are some paid online services that may do rebranding, but would rather leverage the XDA hive!
BONUS QUESTION: if anyone has had a very good experience with some other ROM, would be glad to hear it.
Cheers and thanks in advance for any help or advice!
I've got a magisk rooted CMR-W09 C432 running 9.1.0.160. Maybe I can help you somehow...
But please care: I might have tempered something: I'm currently trying to upgrade to 9.1.0.371 but the updater fails consecutively: Maybe I've borked something e.g. in the bootloader or elsewhere...

Remove T-Mobile SW/ROM from SIM unlocked OnePlus 7T PRO Mclaren edition, Android 11

Guys,
I have read several topics, and got fully confused.
So I purchased in B&H OnePlus 7T Pro Mclaren edition 5G phone. It came unlocked - I'm living outside USA and local SIM network was detected correctly by just entering SIM and reboot the phone.
After factory reset I got Android 11 version ( most of the guides are referring to version 10)
So, my question is:
Shall I change the ROM/SW if this is working with not T-Mobile SIM card?
If its better to use global/international ROM, I will strongly appreciate to get a link to the guide or set of instructions how to do so.
Huge thanks in advance.

Question Confused: What Google Image File should I use

Have a New Pixel 6 (unlocked) I bought on PrimeDay. Currently on Xfinity which is Verizon MVNO. Do I install the Verizon VMNO image because I am using that carrier or do I install the regular image (non-Verizon) because it's not a Verizon phone? Also on a side note, some images are labeled as "softbank," "EMEA" and "APAC,"what do these refer to?
Thank you in advance
@Bad Bimr
12.1.0 (SQ3A.220705.003.A3, Jul 2022, Verizon, Verizon MVNOs)
Why?
The factory/OTA image are based on the carrier not the Manufacturer.
Pixel 6 Guide
Which Factory/OTA image should I Use?
Homeboy76 said:
@Bad Bimr
12.1.0 (SQ3A.220705.003.A3, Jul 2022, Verizon, Verizon MVNOs)
Why?
The factory/OTA image are based on the carrier not the Manufacturer.
Pixel 6 Guide
Which Factory/OTA image should I Use?
Click to expand...
Click to collapse
How did you come by this answer? Because I've been rocking Nexus and Pixel devices since 2014 and at no time have I ever installed a factory image based upon the source of my wireless service.
The correct image @Bad Bimr should be using is the non-Verizon image. Reason being his device is a) an unlocked model and b) does not have mmwave 5G, which Verizon uses in addition to standard sub-6 5G.
Installing a Verizon image on a non-Verizon device could lead to some VERY undesirable results, namely a permanently locked bootloader as Verizon locks bootloaders and will NOT unlock them.
I actually installed the Verizon/MVNO software. Bootloader is still unlocked. Phone seems to work OK but it's only been a day. When the August build comes out I may try the non Verizon build, best yet maybe I will call google and ask them, not that they would know.
Strephon Alkhalikoi said:
How did you come by this answer? Because I've been rocking Nexus and Pixel devices since 2014 and at no time have I ever installed a factory image based upon the source of my wireless service.
The correct image @Bad Bimr should be using is the non-Verizon image. Reason being his device is a) an unlocked model and b) does not have mmwave 5G, which Verizon uses in addition to standard sub-6 5G.
Installing a Verizon image on a non-Verizon device could lead to some VERY undesirable results, namely a permanently locked bootloader as Verizon locks bootloaders and will NOT unlock them.
Click to expand...
Click to collapse
My Google Pixel phone (with an unlockable bootloader) was purchased from Google but my carrier was Verizon. So, I used the Verizon Factory/OTA image when it was available. When it wasn't available I used the Global Factory/OTA image on my phone.
I think, IMHO, Google Pixel phone owners can use either the Carrier Factory/OTA image or Global Factory/OTA image.
Homeboy76 said:
@Bad Bimr
My Google Pixel phone (with an unlockable bootloader) was purchased from Google but my carrier was Verizon. So, I used the Verizon Factory/OTA image when it was available. When it wasn't available I used the Global Factory/OTA image on my phone.
I think, IMHO, Google Pixel phone owners can use either the Carrier Factory/OTA image or Global Factory/OTA image.
Click to expand...
Click to collapse
Except for the fact an unlocked device always downloads the unlocked update if you let the P6 update itself. Now, you may be totally on point about being able to use either image, but given Verizon's penchant for f**kery, why take the risk?
Strephon Alkhalikoi said:
Except for the fact an unlocked device always downloads the unlocked update if you let the P6 update itself. Now, you may be totally on point about being able to use either image, but given Verizon's penchant for f**kery, why take the risk?
Click to expand...
Click to collapse
I didn't know Google phones with unlocked bootloader's that take automatic updates always receive the Global OTA image because I do not take automatic updates.
If it is true all Google Pixel unlocked bootloader phones that receive automatic updates download the Global OTA image. I think people with Google Pixel phones that do not take the automatic updates should use the Global Factory/OTA image.
Strephon Alkhalikoi said:
How did you come by this answer? Because I've been rocking Nexus and Pixel devices since 2014 and at no time have I ever installed a factory image based upon the source of my wireless service.
The correct image @Bad Bimr should be using is the non-Verizon image. Reason being his device is a) an unlocked model and b) does not have mmwave 5G, which Verizon uses in addition to standard sub-6 5G.
Installing a Verizon image on a non-Verizon device could lead to some VERY undesirable results, namely a permanently locked bootloader as Verizon locks bootloaders and will NOT unlock them.
Click to expand...
Click to collapse
Installing a Verizon factory image or OTA on a non-Verizon model Pixel won't lead to a locked bootloader.
Lughnasadh said:
Installing a Verizon factory image or OTA on a non-Verizon model Pixel won't lead to a locked bootloader.
Click to expand...
Click to collapse
I admit to not having tried it myself. I still wouldn't risk it however, even though in this case "Verizon" applies to that variant of P6 and isn't a sign of Verizon digging its grubby paws into the system.
I simply feel it is better to be safe here than sorry.
EMEA - Europe - Middle East Asia
APAC - Asia - Pacific
Homeboy76 said:
@Bad Bimr
My Google Pixel phone (with an unlockable bootloader) was purchased from Google but my carrier was Verizon. So, I used the Verizon Factory/OTA image when it was available. When it wasn't available I used the Global Factory/OTA image on my phone: 12.1.0 (SQ3A.220705.004, Jul 2022)
I think, IMHO, Google Pixel phone owners can use either the Carrier Factory/OTA image or Global Factory/OTA image.
Click to expand...
Click to collapse
It all comes down which model you have, install according to that.
Check in About phone -> Regulatory labels
Cheers
Tom

Question Does 5G work with custom ROMs?

I am on OOS11 and haven't updated my phone to OOS12 or OOS13 due to multiple issues. Now however I have been offered a free upgrade to a 5G plan by my service provider and hence I want to update my phone so that it has 5G capabilities. I don't want to use OOS12/13 to have to be able to use 5G so I was wondering if custom Android 12/13 based ROMs support 5G. Apologies if this is a stupid question.
YES but first you update to android 12/13
then unlock bootloader go to developer option 5g mode must be sa/nsa

Question What are the different models of the OnePlus Nord N200 5G? (DE2117, DE2118, DE17AA)

I'm just collecting some info
What are all of the different models for the OnePlus Nord N200 5G?
The codename of the device is "dre".
DE2118 is the T-Mobile model when you buy through them (or Metro, I think).
I think DE2117 is the unlocked USA model? I'm not completely sure what the difference is between it and the DE2118.
DE17AA is apparently the global unlocked model.
Are there other models?
I also found DE18CB, which is apparently T-Mobile.
I'm confused if maybe this is actually an OS version number instead of a model number, but my phone clearly calls it a "Model" ID.
DE2117 is OEM unlocked USA. It's SIM unlocked / carrier unlocked and bootloader unlocked.
DE2118 is SIM locked / carrier locked to T-mobile or Metro-by-T-mobile. Some have reported that a DE2118 purchased from T-mobile or Metro also accepts Mint mobile (without needing to SIM unlock). It's possible they may also accept other MVNOs that use the T-Mobile network.
DE2118 is bootloader locked, "OEM unlocking" is off and greyed-out, not toggle-able. It becomes an option after the phone is SIM unlocked. Many have also been able to enable OEM unlocking with a bypass, using adb shell pm uninstall --user 0 com.qualcomm.qti.uim which a debloater script will also do for you. OnePlus might "fix" this loophole at some point. But if they do we can probably reverse it by downgrading.
I understand the DE2118 you get from either T-mobile or Metro loads the appropriate branded apps based on which SIM it first sees.
The different models are also listed in this guide Full convert Tmobile/MetroPCS to US OEM with Fastboot Enhance GUI Tool for dummies
dre is the general device codename, but you may also see dre9 (DE2117) or dre8t (DE2118).
Some may mistakenly refer to it as "holi" because that's seen in the bootloader menu, holi is just the codename for the Qualcomm SM4350 Snapdragon 480 platform. [1] [2]
angry_goldfish said:
I also found DE18CB, which is apparently T-Mobile.
Click to expand...
Click to collapse
I believe DE18CB is just from the build number. You have that actually in the Model field? Here's a picture of it in the build number, with in the Model field showing DE2118.
Lots of extremely helpful hints. I already knew most of them from reading today, but thanks!
That notes daboross/oneplus_dre8t_dre9_holi_notes link was perfect. That's what I was assembling for myself.
blueberry.sky said:
Some may mistakenly refer to it as "holi" because that's seen in the bootloader menu, holi is just the codename for the Qualcomm SM4350 Snapdragon 480 platform
Click to expand...
Click to collapse
Ahha! Now that's new to me. I had seen it in fastboot and was wondering about it. Thanks!
Further reading seems to confirm my previous assumption that there are only three models, but sometimes people are refering to software versions in the model numbers, which might just be part of the file names for those releases/recoveries.
I've seen the "DE17AA" model also referred to as "DE2117AA". I don't know which is true or what the best nomenclature is, since I don't actually have one of these international unlocked models.
"DE17AA" I believe is just from software build numbers. And not a model number. DE17AA seems to be in the build numbers intended for the DE2117 model. Whereas DE18CB is in build numbers intended for the DE2118 model.
OnePlus Nord N200
Contribute to OnePlusOSS/OpenSourceReleases development by creating an account on GitHub.
github.com
angry_goldfish said:
I also found DE18CB, which is apparently T-Mobile.
I'm confused if maybe this is actually an OS version number instead of a model number, but my phone clearly calls it a "Model" ID.
Click to expand...
Click to collapse
This is simply a OS version number. This is simply the T-Mobile model. I have the DE2118, but converted it to the DE2117.
Sprunglicious said:
This is simply a OS version number. This is simply the T-Mobile model. I have the DE2118, but converted it to the DE2117.
Click to expand...
Click to collapse
How do you convert DE2118 to DE2117
Tranken587 said:
How do you convert DE2118 to DE2117
Click to expand...
Click to collapse
Full convert Tmobile/MetroPCS to US OEM with Fastboot Enhance GUI Tool for dummies
CHANGELOG: Guide v1.0 - Warn that Lineage cannot be flashed on A12 firmware. Guide v1.1 - Update guide for flashing Lineage after complete conversion and updates so phone is fully converted first. There are THREE firmware versions for the N200...
forum.xda-developers.com

Categories

Resources