• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Found a chink in the armor... Just enabled OEM unlocking after 11 update...

Search This thread
I haven't got a lot of time to get this out before heading out on a job, so here's the nitty gritty. A few days ago I flashed over "OnePlus_Nord_N10_5G_Metro_by_T-Mobile_OxygenOS_10.5.8" to get a clean start. I then allowed 10.5.14 to install OTA. Then last night I saw 11 was available and went for it. While I'm not crazy about 11's overall feel I've still come out ahead.

I came across a thread titled "Oneplus pure debloat". Within that thread is a zipped bat file. I checked it out and didn't see anything to scary being removed, so I ran it. After a reboot I wanted to run the unlock app to see if it still worked (it didn't). But I figured that might be the case as some of the bloatware removed is related. However the response I then received was totally different than what i'd seen before. To my amaze I look under developer and "hot damn!" oem unlocking is no longer greyed out.

Screenshot_20210716-083146.jpg


I haven't anytime to take this further until tonight, so I leave my discovery to you gents. Hope my results are replicated. I look forward to reading your replies when I get home later.
 
Script ran through console...

D:\Downloads>adb devices
List of devices attached
******** device


D:\Downloads>adb shell pm uninstall --user 0 com.tencent.soter.soterserver
Failure [not installed for 0]

D:\Downloads>adb shell pm uninstall --user 0 com.google.android.apps.googleassis
tant
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oem.autotest
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.backuprestore.remoteser
vice
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.bttestmode
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.opbugreportlite
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.carrierlocation
Success

D:\Downloads>adb shell pm uninstall --user 0 com.google.android.ims
Success

D:\Downloads>adb shell pm uninstall --user 0 com.android.carrierdefaultapp
Success

D:\Downloads>adb shell pm uninstall --user 0 cn.oneplus.oemtcma
Success

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.qti.cne
Success

D:\Downloads>adb shell pm uninstall --user 0 com.android.backupconfirm
Success

D:\Downloads>adb shell pm uninstall --user 0 com.android.ons
Success

D:\Downloads>adb shell pm uninstall --user 0 com.example.tmo
Failure [not installed for 0]

D:\Downloads>adb shell pm uninstall --user 0 com.oem.logkitsdservice
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.factorymode.specialtest

Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.sdcardservice
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.setupwizard
Success

D:\Downloads>adb shell pm uninstall --user 0 com.qti.service.colorservice
Success

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.embms
Success

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.qti.dynamicddsservice

Success

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.qti.qtisystemservice
Failure [not installed for 0]

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.qti.qwes.AndroidServic
e
Failure [not installed for 0]

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.qti.remoteSimlockAuth

Success

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.qti.uim
Success

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.qti.uimGbaApp
Success

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.uimremoteclient
Success

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.uimremoteserver
Success

D:\Downloads>adb shell pm uninstall --user 0 net.oneplus.commonlogtool
Success

D:\Downloads>adb shell pm uninstall --user 0 com.google.android.as
Success

D:\Downloads>adb shell pm uninstall --user 0 com.google.android.apps.work.oobcon
fig
Success

D:\Downloads>adb shell pm uninstall --user 0 com.google.android.apps.wellbeing
Success

D:\Downloads>adb shell pm uninstall --user 0 com.android.emergency
Success

D:\Downloads>adb shell pm uninstall --user 0 com.facebook.system
Failure [not installed for 0]

D:\Downloads>adb shell pm uninstall --user 0 com.facebook.appmanager
Failure [not installed for 0]

D:\Downloads>adb shell pm uninstall --user 0 com.facebook.services
Failure [not installed for 0]

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.factorymode
Success

D:\Downloads>adb shell pm uninstall --user 0 com.google.android.documentsui
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.gamespace
Success

D:\Downloads>adb shell pm uninstall --user 0 com.google.android.inputmethod.lati
n
Success

D:\Downloads>adb shell pm uninstall --user 0 com.google.android.gms.location.his
tory
Success

D:\Downloads>adb shell pm uninstall --user 0 org.ifaa.aidl.manager
Success

D:\Downloads>adb shell pm uninstall --user 0 net.oneplus.odm
Success

D:\Downloads>adb shell pm uninstall --user 0 net.oneplus.odm.provider
Success

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.location
Success

D:\Downloads>adb shell pm uninstall --user 0 com.qti.ltebc
Success

D:\Downloads>adb shell pm uninstall --user 0 com.android.cellbroadcastreceiver
Success

D:\Downloads>adb shell pm uninstall --user 0 cn.oneplus.nvbackup
Success

D:\Downloads>adb shell pm uninstall --user 0 com.android.hotwordenrollment.okgoo
gle
Success

D:\Downloads>adb shell pm uninstall --user 0 com.android.hotwordenrollment.xgoog
le
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.account
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.camera.service
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oem.oemlogkit
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.backuprestore
Failure [not installed for 0]

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.collectiondata
Failure [not installed for 0]

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.diagnosemanager
Success

D:\Downloads>adb shell pm uninstall --user 0 com.android.egg
Success

D:\Downloads>adb shell pm uninstall --user 0 net.oneplus.push
Success

D:\Downloads>adb shell pm uninstall --user 0 com.quicinc.voice.activation
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oem.rftoolkit
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.screenrecord
Success

D:\Downloads>adb shell pm uninstall --user 0 com.google.android.apps.setupwizard
.searchselector
Failure [not installed for 0]

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.qti.seccamservice
Success

D:\Downloads>adb shell pm uninstall --user 0 com.android.traceur
Success

D:\Downloads>adb shell pm uninstall --user 0 com.qualcomm.qti.uceShimService
Success

D:\Downloads>adb shell pm uninstall --user 0 com.android.managedprovisioning
Success

D:\Downloads>adb shell pm uninstall --user 0 com.oneplus.brickmode
Success

D:\Downloads>adb reboot

D:\Downloads>
 

Neverfalter2015

Senior Member
I had the same result as far as the greyed out OEM unlocking toggle becoming moveable. That said getting the 64 digit unlock code from Metro or OnePlus is turning in to a chore. OnePlus says metro has it, metro says they don't have the code. I took a screenshot of my Conversation with Metro and sent it to OnePlus in hopes they can add my IMEI to the list for bootloader unlock tokens.

Please note that unless you specify bootloader unlock to metro they will assume you mean carrier unlock and tell you to wait the 180 days. If you wait the 180 days all you will get is the carrier unlock Which does nothing in the way of unlocking your bootloader.
 

scottlam1

Senior Member
Aug 16, 2011
106
29
More OnePlus bs lies
 

Attachments

  • Screenshot_20210728-181832.jpg
    Screenshot_20210728-181832.jpg
    372.6 KB · Views: 137
  • Screenshot_20210728-181821.jpg
    Screenshot_20210728-181821.jpg
    330.6 KB · Views: 136
  • Screenshot_20210728-181827.jpg
    Screenshot_20210728-181827.jpg
    387.3 KB · Views: 137

Neverfalter2015

Senior Member
Ya most definitely. I've been a squeaky wheel for almost 2 weeks to both metro and OnePlus. I finally got metro to state that they don't have access to the bootloader unlock tokens. I screenshotted that conversation and sent it to OnePlus. That was the point that I finally gained some traction. I think there is some language barrier issues going on in regards to bootloader unlock and network unlock-i had to specifically state "bootloader unlock token, not network unlock" before they actually knew what I wanted.
 

Neverfalter2015

Senior Member
Yeah I'm sick of their crap I just filed an fcc complain with OnePlus I'll see if that gets the ball rolling. I got my sim unlock early from fcc so it may work
Ya for sure. It's b.s. that we're even having this difficulty. I'm not planning on giving up. The fact that it's an option from other carriers but not metro means it's just some red tape in the way. Hopefully.
 
  • Like
Reactions: BTK19

googlephoneFKLenAsh

Senior Member
Jul 31, 2017
146
52
From oneplus website:

FAQS​

Q1: Why do I need to apply for a token?​

Answer: If you want to root your device or flash a customer ROM, OEM unlock is the first technical step for those operation after you have the SIM unlocked. Please note that:

  1. OEM unlock service is provided for T-Mobile version user, non TMO user can unlock the device without this service.
  2. Unlock device is not a totally safe operation, there are risks in this unlock operation. So, please be very careful to do this operation.

If oneplus treats metropcs as part of t-mobile, oneplus must provide us the unlock token.
Even if oneplus says metropcs is not t-mobile, oneplus still has responsibility to unlock the bootloader of metropcs version because "non TMO user can unlock the device without this service".

Either way, oneplus has to give us the unlock token. Otherwise we can send a letter to their legal department or file a complaint with FCC or BBB.
 
  • Like
Reactions: BTK19

googlephoneFKLenAsh

Senior Member
Jul 31, 2017
146
52
I contacted oneplus and finally reached a higher level agent and he asked me wait for futher update. Hope they can make it happen this time.

BTW: the nord N200 from metropcs is bootloader unlockable from the same website. I requested the unlock token from oneplus's t-mobile portal. So oneplus is treating metropcs as part of T-Mobile.
One difference though is that the metropcs version N200 has same model number as t-mobile version while the metropcs version N10 has different model number than the t-mobile version, which may be the reason oneplus hasn't add metropcs n10's imei to the bootloader unlock system.


I have my Metropcs N200 sim unlocked and bootloader unlocked. Currently the N200 doesn't have stock rom yet so I haven't root it.
 
Last edited:

Top Liked Posts