so i bought this nord n10 from ebay and apparently when i got to the settings to try rooting it, the oem unlocking is greyed out. any solutions? i tried to find online but there wasnt really any so, i need to keep looking in these forums. someone said a solution about sim card unlocking or something
edit: shouldve mentioned this, its a t-mobile phone
also im very new to this
OnePlus Nord pure debloat follow guid it will enable oem unlocking. If it's a carrier locked phone you will have to get a oem unlock token via oneplus
if its a metro phone you wont be able to get a unlock token via oneplus they dont have the imei in there data base and are clueless how to do it
Fastboot oem get unlock data
Send the string of numbers to oneplus
Along with the IMEI number
after talking with oneplus they say they do not support MertoPCS N10 5G via unlock page and i have to ask MetroPCS for unlock token MetroPCS says its oneplus that has to supply the unlock token there has been a few user that are getting the same runaround one even filed a complaint with the FCC over it
BTK19 said:
after talking with oneplus they say they do not support MertoPCS N10 5G via unlock page and i have to ask MetroPCS for unlock token MetroPCS says its oneplus that has to supply the unlock token there has been a few user that are getting the same runaround one even filed a complaint with the FCC over it
Click to expand...
Click to collapse
I was the one who contacted fcc they contacted OnePlus on my behalf haven't heard anything yet. I don't know why it's such an issue for them I've heard people say they have metro n200 unlocked from the page
I don't know either but I will not be buying a OnePlus again
You can try oem brute force fastboot script it's actually for Huawei devices but Iv used it on other devices
scottlam1 said:
I was the one who contacted fcc they contacted OnePlus on my behalf haven't heard anything yet. I don't know why it's such an issue for them I've heard people say they have metro n200 unlocked from the page
Click to expand...
Click to collapse
I have unlocked the bootloader of metropcs Nord N200 successfully. The metropcs N200 has the same model number as T-Mobile version while the metropcs nord N10 has a different model number from t-mobile N10.
googlephoneFKLenAsh said:
I have unlocked the bootloader of metropcs Nord N200 successfully. The metropcs N200 has the same model number as T-Mobile version while the metropcs nord N10 has a different model number from t-mobile N10.
Click to expand...
Click to collapse
Could be why I don't know if model number has anything to do with imei generation though
googlephoneFKLenAsh said:
I have unlocked the bootloader of metropcs Nord N200 successfully. The metropcs N200 has the same model number as T-Mobile version while the metropcs nord N10 has a different model number from t-mobile N10.
Click to expand...
Click to collapse
Was the n200 a 64 character key too
scottlam1 said:
Was the n200 a 64 character key too
Click to expand...
Click to collapse
Yes.
Clearly oneplus only added the imeis of t-mobile model number to the bootloader unlock data base.
For N200, metropcs version has the same model number so we can unlock the bootloader of metropcs n200.
The N10 can be flashed with the international rom via msm tool and the bootloader can be unlocked that way
BTK19 said:
if its a metro phone you wont be able to get a unlock token via oneplus they dont have the imei in there data base and are clueless how to do it
Click to expand...
Click to collapse
Just wait until you can unlock your phone via the unlocker app.
I literally just unlocked everything a few minutes ago without messing with my phone.
ninjasinabag said:
Just wait until you can unlock your phone via the unlocker app.
I literally just unlocked everything a few minutes ago without messing with my phone.
Click to expand...
Click to collapse
You have no idea about what bootloader unlock actually is.
Your bootloader is still locked unless you get the unlock token from oneplus and flash it in fastboot.
googlephoneFKLenAsh said:
You have no idea about what bootloader unlock actually is.
Your bootloader is still locked unless you get the unlock token from oneplus and flash it in fastboot.
Click to expand...
Click to collapse
My guy, I've been doing this since 2008.
My phone actually booted the dynamic system image and hit a DMverity wall. Previously, my phone wouldn't even attempt to install the DSU because because of the bootloader being locked.
bruh i tried looking up rooting beginner's guide and it was stilll complicated so is the other beginner's guide online, i really don't know what to do when im stuck, no tutorials on youtube to root the N10 5G...
Greetings all, I have come to ask for advice on how to debrick my lg v60 version V600TM20n. First, how I ended up in this situation.
To begin, I followed this guide to unlock bootloader and root my phone then I followed this guide in an attempt to install a custom rom however, i did not get too far.
I tried to remove vbmeta verity as per the requirements of the form and in doing so input this line into my bootloader fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img with the file provided by this form I think this is where the issue I have is comming from but moving on.
I then attempted to download lineage os following the guide but it did not work and I was fed up by this point to I began the process of reverting everything I did. I downloaded SuperSu to deroot my device. After derooting my device I went to the bootloader and typed in fastboot oem lock, locking my device and dooming me.
In my attempts to escape from the hell I am currently in I downloaded LGUP v1.16.03 and v1.14 (I tried them both deleting the previous one before installing the new one) yet each time I was stuck with the this error code Error Code = 0x2000, Invalid command response when the progress bar reach 9%.
The dll i used is version 0.0.3.23 and the one provided by LGUP v.1.16.03, and the firmware I attempted to download was V600TM20n_02_TMO_US_OP_0111.kdz on LGUP it says V600TM20n oh and also I did try UPPERCUT, no resuts
Currently on my phone's download mode screen at the bottom in red it says Modified / E / L / RO / id : 3(NA2_US) I have also tried LGUP Cmd but same results
I have tried LG bridge but it says connecting and then no device found :/
I wish i could say i tried lg flash tool but i have no idea on how to use it
Possibly another big mistake (idk what im doin) I used the QFIL and restore the abl_a and abl_b to their original versions after locking the bootloader.
Please tell me if there is anything else I can do or if I now own a $300 brick. If I do have a $300 brick is there any value I can get from it to fund my walmart flip phone that I will have to buy?
unregisteredhypercam said:
Greetings all, I have come to ask for advice on how to debrick my lg v60 version V600TM20n. First, how I ended up in this situation.
To begin, I followed this guide to unlock bootloader and root my phone then I followed this guide in an attempt to install a custom rom however, i did not get too far.
I tried to remove vbmeta verity as per the requirements of the form and in doing so input this line into my bootloader fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img with the file provided by this form I think this is where the issue I have is comming from but moving on.
I then attempted to download lineage os following the guide but it did not work and I was fed up by this point to I began the process of reverting everything I did. I downloaded SuperSu to deroot my device. After derooting my device I went to the bootloader and typed in fastboot oem lock, locking my device and dooming me.
In my attempts to escape from the hell I am currently in I downloaded LGUP v1.16.03 and v1.14 (I tried them both deleting the previous one before installing the new one) yet each time I was stuck with the this error code Error Code = 0x2000, Invalid command response when the progress bar reach 9%.
The dll i used is version 0.0.3.23 and the one provided by LGUP v.1.16.03, and the firmware I attempted to download was V600TM20n_02_TMO_US_OP_0111.kdz on LGUP it says V600TM20n oh and also I did try UPPERCUT, no resuts
Currently on my phone's download mode screen at the bottom in red it says Modified / E / L / RO / id : 3(NA2_US) I have also tried LGUP Cmd but same results
I have tried LG bridge but it says connecting and then no device found :/
I wish i could say i tried lg flash tool but i have no idea on how to use it
Possibly another big mistake (idk what im doin) I used the QFIL and restore the abl_a and abl_b to their original versions after locking the bootloader.
Please tell me if there is anything else I can do or if I now own a $300 brick. If I do have a $300 brick is there any value I can get from it to fund my walmart flip phone that I will have to buy?
Click to expand...
Click to collapse
Here,try this copy.Make sure you delete all previous versions of LGUP.
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T and Nord N10 5G here is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.
You should be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
DE17AA tools (global firmware):
ANDROID 11:
OOS 11.0.3
Mirror: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@drfsupercenter for testing 11.0.3 version on his device
OnePlus for the device and OS
I can confirm this works for the "unlocked" version that I bought at Best Buy. Thanks for posting!
Here is a question
Can I convert T-Mobile version to global this way?
mingkee said:
Here is a question
Can I convert T-Mobile version to global this way?
Click to expand...
Click to collapse
No, you can't convert T-Mobile variant to unlocked one with this tool.
Some_Random_Username said:
No, you can't convert T-Mobile variant to unlocked one with this tool.
Click to expand...
Click to collapse
The scenario is like 8T.
I remember somebody alter the project code to cross flash.
I have to find out
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
THANK YOU!!!! My paperweight is a phone again!
edale1 said:
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
Click to expand...
Click to collapse
I bricked my phone messing with it after the recent update they pushed out to official phones which broke 5g. Maybe more people than I did, I was pretty happy until then.
edale1 said:
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
Click to expand...
Click to collapse
I don't know how he got it, but it does work.
mingkee said:
Here is a question
Can I convert T-Mobile version to global this way?
Click to expand...
Click to collapse
I'd imagine it would be the same as when I tried to flash the T-Mobile MSMTool to my unlocked phone. It just said wrong model and wouldn't continue.
It seems like oneplus finally released the msmtool for global/unlocked version.
Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):
Flash international ROM to Tmobile/Metro w/ locked bootloader
MAJOR UPDATE: Managed to flash Global stock rom to the MetroPCS variant Pros: Stock Oneplus and everything works Cons: OEM unlock is still greyed out Before you go any further: THERE IS NO ROOT FOR THIS DEVICE WITH A LOCKED BOOTLOADER (YET)...
forum.xda-developers.com
Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.
After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.
The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
Some_Random_Username said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T and Nord N10 5G here is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.
You should be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
DE17AA tools (global firmware):
ANDROID 11:
OOS 11.0.3
Mirror: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@drfsupercenter for testing 11.0.3 version on his device
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
Click to expand...
Click to collapse
great thanks lol
googlephoneFKLenAsh said:
It seems like oneplus finally released the msmtool for global/unlocked version.
Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):
Flash international ROM to Tmobile/Metro w/ locked bootloader
MAJOR UPDATE: Managed to flash Global stock rom to the MetroPCS variant Pros: Stock Oneplus and everything works Cons: OEM unlock is still greyed out Before you go any further: THERE IS NO ROOT FOR THIS DEVICE WITH A LOCKED BOOTLOADER (YET)...
forum.xda-developers.com
Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.
After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.
The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
Click to expand...
Click to collapse
I changed everything related to project ID and everything in that post, but mine still says
{
"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"
}
justauserthatusesaphone said:
I changed everything related to project ID and everything in that post, but mine still says
View attachment 5652955
Click to expand...
Click to collapse
The project code should be for N200 not other models
mingkee said:
The project code should be for N200 not other models
Click to expand...
Click to collapse
That's what I put.
I even control+f'd it for anything that says "2083c" or "ID" and "project", yet it still somehow got that error.
justauserthatusesaphone said:
I changed everything related to project ID and everything in that post, but mine still says
View attachment 5652955
Click to expand...
Click to collapse
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
googlephoneFKLenAsh said:
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
Click to expand...
Click to collapse
ok i'll do that in a bit and i'll probably release it here.
googlephoneFKLenAsh said:
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
Click to expand...
Click to collapse
well
okay i give up
justauserthatusesaphone said:
View attachment 5653443
well
okay i give up
Click to expand...
Click to collapse
You didn't follow the instructions correctly.
Re-read the instructions, especially the editing project id step.
The error message mentioned "image 2083c", which means there are lines from 2083c ops not replaced with values from 20818 ops yet.
You need to replace all those lines:
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
in the settings.xml from unlocked 2083c ops with the values in the settings.xml from metro/tmo 20818 ops. (better to use copy&paste to avoid typos).
Also you need to copy the modified unlocked/global ops to the msmtool folder of the metro/tmo version and replace the original metro/tmo ops.
I believe 2083c is the unlocked version and 20818 is the metro/tmo version.
googlephoneFKLenAsh said:
You didn't follow the instructions correctly.
Re-read the instructions, especially the editing project id step.
The error message mentioned "image 2083c", which means there are lines from 2083c ops not replaced with values from 20818 ops yet.
You need to replace all those lines:
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
in the settings.xml from unlocked 2083c ops with the values in the settings.xml from metro/tmo 20818 ops. (better to use copy&paste to avoid typos).
Also you need to copy the modified unlocked/global ops to the msmtool folder of the metro/tmo version and replace the original metro/tmo ops.
I believe 2083c is the unlocked version and 20818 is the metro/tmo version.
Click to expand...
Click to collapse
I can't tell what's wrong.
XML:
<BasicInfo Project="20818" TargetName="SM4350" Version="dre8t_10_O.05_210713" MemoryName="ufs" GrowLastPartToFillDisk="true" LogEnable="false" LogPositionIndex="-1" DelayStartTime="0" UseGPT="true" CheckImage="false" CheckHwVersion="false" NeedUsbDownload="true" BackupPart="false" BackupPartId="" ChipType="1" FactoryID="20818US" MinToolVersion="5.0.3" SupportHwID="false" SupportRfID="false" SupportPrjID="false" CheckRfVersion="false" CheckProjectVersion="false" SkipImgSHA256Check="true" ParamVersion="1" SkipParamProcess="false" ModelVerifyVersion="0" ModelVerifyPrjName="" SkipCheckHWVerByCustFlag="false" DefaultCleanFRP="true" FrpPartitionLabel="frp" CarrierID="0" AutoDetectDDR="false" DPPackingVer="0" ProjectSoftwareIDSupport="false" ATOBuild="false" SkipMultiImageIdentify="true" RandomPadding="anxKohPaJKUq2kVPIbXgD7RXNa96iUeGFZa1GzbYH6OIorf7RCneJCCgkJlSlN" ModelVerifyRandom="RG8sc2EUOj51TeCw" ModelVerifyHashToken="F9417334897C488DEA1DA5AC787906F743E85C17B47EB9669FFE96F11529D33C" Applicant="Unknown" Hostname="rd-build-77" BuildTime="1631716601" ApplicantIP="not sure if this is sensitive" />
Everything you listed is changed, the unlocked ops is also put into the tmobile msm
for example, here's the tmobile one
XML:
<BasicInfo Project="20818" TargetName="SM4350" Version="dre8t_10_O.05_210713" MemoryName="ufs" GrowLastPartToFillDisk="true" LogEnable="false" LogPositionIndex="-1" DelayStartTime="0" UseGPT="true" CheckImage="false" CheckHwVersion="false" NeedUsbDownload="true" BackupPart="false" BackupPartId="" ChipType="1" FactoryID="20818US" MinToolVersion="5.0.3" SupportHwID="false" SupportRfID="false" SupportPrjID="false" CheckRfVersion="false" CheckProjectVersion="false" SkipImgSHA256Check="true" ParamVersion="1" SkipParamProcess="false" ModelVerifyVersion="0" ModelVerifyPrjName="" SkipCheckHWVerByCustFlag="false" DefaultCleanFRP="true" FrpPartitionLabel="frp" CarrierID="1" CarrierNoneEnable="true" AutoDetectDDR="false" DPPackingVer="0" ProjectSoftwareIDSupport="false" ATOBuild="false" SkipMultiImageIdentify="true" RandomPadding="CQLTBL0oxs4BM2pdtK1y8Q1rvzgUtd033KWDfU1dM3mh3bKuwJs4jrtcqa6iB7lERIP4kOf5RRmS16MxPDz74tjvRq" ModelVerifyRandom="RG8sc2EUOj51TeCw" ModelVerifyHashToken="F9417334897C488DEA1DA5AC787906F743E85C17B47EB9669FFE96F11529D33C" Applicant="Unknown" Hostname="rd-build-74" BuildTime="1626183302" ApplicantIP="eeeeeeee" />
You are a godsend. Thank you so much, this is exactly what I needed!!
Recently I bought used OnePlus Nord n200 from a website which is locked to T-Mobile carrier in about device option.
Though device carrier is locked but when I enable developer options bootloader unlock option is not greyed out also in engineer mode it shows device carrier is unlocked.When I insert sim into phone sim toolkit with sim card company name appears in apps but there are no sim signals is there any fix for this
Screenshots are attached
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
Did you check this thread?
Is your bootloader unlocked?
Yes I can turn it on from developer options
Did you ever get this figured out? Learn anything new about the SIM unlocking for this phone on T-Mobile?
I have a device stuck telling me I need to be on the network for 40 days, but it's been a whole lot longer than that. Very strange.
angry_goldfish said:
Did you ever get this figured out? Learn anything new about the SIM unlocking for this phone on T-Mobile?
I have a device stuck telling me I need to be on the network for 40 days, but it's been a whole lot longer than that. Very strange.
Click to expand...
Click to collapse
If you still need help with this get me back in DM.
I'll tell you how to network unlock any OP device
Hi. Saw on the thread about DMing you about sim/network unlock for OnePlus Nord n200. Are you able to help?