Try "adb shell pm uninstall --user 0 com.qualcomm.qti.remoteSimlockAuth" and let us know if that worked.
How To Guide The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)
- Thread starter edale1
- Start date
Try going to Settings, select Advanced Mode, and see if it gives you the option to download full image.
Someone would need to go through the debloat script and run each command manually one at a time, checking after each item, to figure that out.
Though "com.qualcomm.qti.remoteSimlockAuth" is my uneducated guess as to the culprit.
If you want to keep the bloat, and have the T-Mobile variant, then you should probably just use the SIM Unlocker service here:
[CLOSED][T-Mobile USA] Free SIM Unlocking Service - [OnePlus/Samsung/Google/LG/Moto]
Hello XDA, I am back at it again with the free T-Mobile network unlocks. Yep, you heard that right... 100% FREE. This service will allow you to go into your Settings and perform a network unlock. I've been doing this for over 3 years now with...
forum.xda-developers.com
That was my guess as well, but removing com.qualcomm.qti.remoteSimlockAuth did not enable it. I guess I will go with the service.Someone would need to go through the debloat script and run each command manually one at a time, checking after each item, to figure that out.
Though "com.qualcomm.qti.remoteSimlockAuth" is my uneducated guess as to the culprit.
If you want to keep the bloat, and have the T-Mobile variant, then you should probably just use the SIM Unlocker service here:
I can personally vouch that it works.[CLOSED][T-Mobile USA] Free SIM Unlocking Service - [OnePlus/Samsung/Google/LG/Moto]
Hello XDA, I am back at it again with the free T-Mobile network unlocks. Yep, you heard that right... 100% FREE. This service will allow you to go into your Settings and perform a network unlock. I've been doing this for over 3 years now with...
I suppose the real question now is... Is that service necessary for Mobbdeep's SIM Unlock to work...
I'd imagine a factory restore (via booting to the recovery partition) would re-install that no problem. Also wipe your data, but that's gonna happen when you get to the bootloader unlock anyways.
As to specifically reinstalling just that? I honestly have no clue how to go about that, I'm not knowledgeable enough about Android's inner workings to even guess. I rarely ADB for anything but the rooting process when I get a new phone. There's a reason I said this guide was more for collecting the info in one place than providing a step-by-step guide, lol. I'm just trying to help everyone else, considering I spent days digging up all the info to try and get my bootloader unlocked.
Probably a dumb question, as I am not sure if the file remains or how obvious this might be, but have you tried issuing this through from CMD with the phone plugged in and ADB enabled?
adb shell pm install --user 0 com.qualcomm.qti.remoteSimlockAuth
The app you have uninstalled is not really uninstalled. It has just been marked as removed for the default user. It is still there on your phone. There are 2 ways you can "install" it back.
1. Run the following command - "adb shell cmd package install-existing com.qualcomm.qti.remoteSimlockAuth"
OR
2. If you don't have anything important on the phone to lose, simply do a factory reset in Settings.
Let us know how that goes for you.
Was the N200 activated on Tmobile data plan with a Tmobile SIM card, when you ran the debloat script and got the OEM unlock ungrayed? Or were you on WiFi with no Tmobile SIM card?
Also, how long did you have to wait between running the debloat script and the OEM Unlocked becoming ungrayed?
Last edited:
Was your N200 activated on Tmobile data plan with a Tmobile SIM card, when you ran the debloat script and got the OEM unlock ungrayed? Or were you on WiFi with no Tmobile SIM card?
Also, how long did you have to wait between running the debloat script and the OEM Unlocked becoming ungrayed?
Last edited:
My understanding is the debloat script is removing whatever component blocks the OEM Unlock option. The debloat script does NOT SIM Unlock the phone. It shouldn't require a SIM card in the phone at all to ungrey the option, nor should it require a WiFi connection..
From what's been said, I believe the option ungrayed instantly, without even needing a restart of the phone (still always good practice to restart a device after a change to it's system).
Thanks. It seems it needs WiFi but not SIM for the debloat to work on OEM Unlock option. You are right that does not sim unlock the phone.
Top Liked Posts
-
There are no posts matching your filters.
-
14OK, this process has been hell, but I'm gonna try and consolidate everything I've worked out so far in one place. This all applies only to the T-Mobile variant (ie. it comes preloaded with all the T-Mobile bloatware) of the N200 on the T-Mobile network; and a Windows PC, where a PC is used (though I imagine the Mac/Linux commands are quite similar). This is more to gather the info in one place than to provide step-by-step instructions.
SIM/NETWORK UNLOCK
Before you can unlock the bootloader, the N200 needs to be SIM unlocked. The option to Enable OEM Unlock won't even show up in the developers options until then. A temporary SIM unlock won't work, it needs to be a permanent SIM unlock.
If your N200 is the T-Mobile variant, you can get it SIM unlocked free here (be sure to read the first post thoroughly to be sure you qualify):
@mobbdeep had my SIM unlocked within 24 hours of sending him the required info.[CLOSED][T-Mobile USA] Free SIM Unlocking Service - [OnePlus/Samsung/Google/LG/Moto]
Hello XDA, I am back at it again with the...
forum.xda-developers.com
You MUST have an active T-Mobile network (not Sprint or Metro) SIM card in the N200 for at least 3 full days before sending your SIM Unlock request in.
---
*edit-
An alternate is to use this debloat script:
Which should unlock the OEM Unlock option in the developer options.Found a chink in the armor... Just enabled OEM unlocking after 11 update...
I haven't got a lot of time to get this out...
forum.xda-developers.com
This should work with non-T-Mobile variants of the N200 as well.
Thanks to @PopCaps1996 for pointing this option out.
---
*edit2-
Thanks to user @DeadDjembe we now know the specific command from the debloat script which enables OEM Unlocking.
Running this ADB command on a stock T-Mobile variant N200 should enable the greyed-out Allow OEM Unlock option in the developers settings, without needing to run the full debloat script.Code:adb shell pm uninstall --user 0 com.qualcomm.qti.uim
---
Once your N200 is SIM Unlocked, the Enable OEM Unlock option will show up in the developers options.
USB DRIVERS
You may need to use the Google USB Driver from Android Studio to allow your PC to recognize your phone when it's in fastboot mode.
Android Studio won't install the USB Drivers by default, you'll need to install them through the SDK Manager (Android Studio -> Projects -> More Actions -> SDK Manager -> SDK Tools -> Google USB Driver checkbox -> Apply)Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an...
developer.android.com
You'll need to manually install the drivers through the device manager while the phone is in fastboot mode and connected to the PC (right-click -> Update Drivers -> Browse Computer -> Let Me Pick -> Have Disk).
The drivers should be located at:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
You'll want the 'Android Bootloader Interface' driver.
UNLOCK CODE/TOKEN
Once you can access your phone in fastboot mode, you can try:
'fastboot oem unlock'
But, you'll just get a message asking for an unlock token. Doesn't hurt to try, just in case, though.
What you need to do now, is type:
'fastboot oem get_unlock_code'
This will display both the phone's serial number, plus a 64 digit unlock code. (you might not be able to select the code to copy it, but a ctrl-a / ctrl-c should work, then just paste it in notepad)
Now, on your phone (still in fastboot mode) hit up/down on the volume buttons, until you see "Show Barcode", then tap the power button to select it.
This will bring up a barcode, as well as listing you devices IMEI number. (there are other ways to get the IMEI, but this is quick, and you're already right there)
Copy the IMEI down.
Now go to:
https://www.oneplus.com/unlock_token
You'll need to create an account.
In that form, you'll need to select the phone's model, and then enter the serial number, 64 digit unlock code (no spaces), the IMEI, and your email, as well as checking a box that you acknowledge that you void the warranty by bootloader unlocking the phone.
If all goes well, It should take about a week from submission for them to send you the unlock token.
------
I've just sent in my info an hour or two ago, and am now waiting for my unlock token.
I'll update this with what you need to do with the token once I've gotten mine and figure it out myself, lol.
------
Exactly 7 days (nearly to the minute) after sending the request in, I received the unlock code. So here's the update:
APPLYING THE UNLOCK CODE
You can use this URL to check the status of your Unlock Coed request:
unlock token - OnePlus (United States)
www.oneplus.com
Once your Status is listed as "Finished", there will be a download button at the lower right corner.
Download the "unlock_code.bin" file to your PC.
Place 'unlock_code.bin' in:
C:\Users\[user name]\AppData\Local\Android\Sdk\platform-tools\
Or where ever you have your fastboot.exe file.
If you don't know where it is, the command:
will give your it's location.Code:fastboot --version
Now in command line, navigate to the folder "fastboot.exe" and "unlock_code.bin" are located in. Get your phone connected via USB, and in fastboot mode, and use the following command:
(Thanks to @lentm for posting this command)Code:fastboot flash cust-unlock unlock_code.bin
After checking the output, to be sure it worked, use this command:
Follow the on-screen instructions on your phone to finish the bootloader unlock.Code:fastboot oem unlock3
I'd imagine a factory restore (via booting to the recovery partition) would re-install that no problem. Also wipe your data, but that's gonna happen when you get to the bootloader unlock anyways.
As to specifically reinstalling just that? I honestly have no clue how to go about that, I'm not knowledgeable enough about Android's inner workings to even guess. I rarely ADB for anything but the rooting process when I get a new phone. There's a reason I said this guide was more for collecting the info in one place than providing a step-by-step guide, lol. I'm just trying to help everyone else, considering I spent days digging up all the info to try and get my bootloader unlocked.2you do NOT need to carrier unlocked for bootloader unlock use this...... debloat script oneplus through ADB an once finished OEM UNLOCK will be ungrayed. then you can request a unlock token from oneplus then wait 7 days then flash an unlock bootloader.
im still carrier locked2
OK, that's neat.
I can't personally test it, as I'm already SIM unlocked; but all comments in the thread seem to indicate it working.
It'd be quite interesting if someone could narrow down exactly which of the removed apps enables the OEM Unlock option (as an uninformed guess: adb shell pm uninstall --user 0 com.qualcomm.qti.remoteSimlockAuth).
I'd need to research what all those different apps do, but at a glance I see at least 2 or 3 on that list I'd want to keep. At any rate, I'd rather wait until after I get TWRP Recovery on my phone (once we get a release for the N200) before debloating it, just to be safe. I'm far more knowledgeable about computers than phones, which gives me just enough knowledge to seriously screw up my phone by doing the wrong thing, lol.
