Sorry if this has been asked a *.* times. Is there a way to unlock the BL (OEM)? I see that there has not been any traction on this subject lately. The guy that used to do it seems to be gone.
Am I missing something?
Thanks,
-V
...?
unlock token - OnePlus (United States)
www.oneplus.com
I needed to let all the updates to complete before running the debloater. Now the OEM unlock can be enabled.
You don't need to run the full debloat script, the only command you need to run is:
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
That will allow you to Enable OEM Unlock. You still need an unlock token from OP to unlock the bootloader itself though.
edale1 said:
You don't need to run the full debloat script, the only command you need to run is:
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
That will allow you to Enable OEM Unlock. You still need an unlock token from OP to unlock the bootloader itself though.
Click to expand...
Click to collapse
i got a questions, i have my Oneplus Nord N200 and this worked perfectly, would you know if there is a similar way to do this on a Samsung Device?
rinnycoop121 said:
i got a questions, i have my Oneplus Nord N200 and this worked perfectly, would you know if there is a similar way to do this on a Samsung Device?
Click to expand...
Click to collapse
That was figured out by a user experimenting with the commands in the debloat script to figure out exactly which command from it un-greyed out the 'Enable OEM Unlock' option. You can check this thread to see how that happened:
The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)
OK, 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...
forum.xda-developers.com
I have no idea if a similar method exists for other model phones.
rinnycoop121 said:
i got a questions, i have my Oneplus Nord N200 and this worked perfectly, would you know if there is a similar way to do this on a Samsung Device?
Click to expand...
Click to collapse
US Sammys do more than just hiding the switch, forget about it.
Related
So I got the T-Mobile Variant of the LG V30 and ran command to unlock the bootloader and it seems to have unlocked it as well as wiping the data and cache. I know with previous LG devices with T-mobile that the there were no commands to be able to write to the device. Is there anyway to verify if this is the case?
Following
Binary Flood said:
So I got the T-Mobile Variant of the LG V30 and ran command to unlock the bootloader and it seems to have unlocked it as well as wiping the data and cache. I know with previous LG devices with T-mobile that the there were no commands to be able to write to the device. Is there anyway to verify if this is the case?
Click to expand...
Click to collapse
This is very interesting, I wonder if bootloader is unlocked on the upcoming "sim unlocked" US998 as well? If the T-Mobile bootloader is unlocked this may be a game changer.
Apparently you can unlock bootloader but cannot run ANY other commands. So, its basically useless.
Binary Flood said:
So I got the T-Mobile Variant of the LG V30 and ran command to unlock the bootloader and it seems to have unlocked it as well as wiping the data and cache. I know with previous LG devices with T-mobile that the there were no commands to be able to write to the device. Is there anyway to verify if this is the case?
Click to expand...
Click to collapse
You have already verified by the fastboot oem id command
Killua96 said:
You have already verified by the fastboot oem id command
Click to expand...
Click to collapse
It's a damn shame, thanks for letting me know. Hopefully we could get another dirty santa type exploit.
I wonder what's up with that flashall command...
Sent from my VS995 using Tapatalk
Whatever you do, don't use fastboot flashing unlock_critical ... it'll factory reset your phone and won't unlock a damn thing ... not that I know from experience or anything.
gogozombiii said:
Whatever you do, don't use fastboot flashing unlock_critical ... it'll factory reset your phone and won't unlock a damn thing ... not that I know from experience or anything.
Click to expand...
Click to collapse
if only i would've seen this earlier because that's what i ended up trying out in adb and boom a voided warranty and i didn't get time to take up the daydream offer since i'm sure they will be able to see i already voided my warranty. . In the mean time i have pulled a couple of files out like for example system(i used the adb pull /system), vendor( adb pull /system/vendor) and frameworks(adb pull /system/framework). ive just been poking around trying to see if there is any way to find the boot image. any ideas where it could be located?
If you have pulled system. can you please check if you have any *.mbn files there. If yes then copy, zip and attach them here.
These are lte modem configuration files which interest me much.
Thank you
Binary Flood said:
So I got the T-Mobile Variant of the LG V30 and ran command to unlock the bootloader and it seems to have unlocked it as well as wiping the data and cache. I know with previous LG devices with T-mobile that the there were no commands to be able to write to the device. Is there anyway to verify if this is the case?
Click to expand...
Click to collapse
It has been discussed in the LG V30 Unlock bootloader and Root thread as well as the more specific T-mobile LG V30 root effort thread.
This post (October 7) shows commands a T-mobile LG V30 user tried after unlocking his bootloader:
https://forum.xda-developers.com/showpost.php?p=74080195&postcount=112
And here's other exchanges in that same thread:
bp328i said:
Try "fastboot oem device-id"
I bet it fails which means yes the bootloader can be unlocked but adb is disabled so no way to load TWRP or any custom recovery. This would be the same as on the T-Mobile G6.
Click to expand...
Click to collapse
ShadowDXS said:
It does fail. That means we will have to download the image for TWRP on the device, and if root is gained we can then cp the file to the recovery directory. That blows.
Click to expand...
Click to collapse
bacon612 said:
So there we have it. It's locked just like previous models. Now we wait for the unlocked variant...
Edit: locked as in the fastboot commands have been disabled the same was they were on the g6
Click to expand...
Click to collapse
With the fastboot commands disabled you need root to install TWRP or you need TWRP to get root, and neither is possible right now.
The posts above are from the more general LG V30 Unlock bootloader and Root -- general because it covers ALL LG V30 models, and it's pretty much agreed only the official carrier unlocked LG V30 US998 and H930 will have "real" bootloader unlock with full ADB fastboot commands. That doesn't exclue that some exploit might be found by devs, but just if you want easy bootloader unlock and root -- like with the LG G6 carrier unlocked models, which have root, recovery, ROMs, kernels.
_________
However, this is the thread below is to specifically discuss the T-mobile LG V30 root efforts:
T-mobile LG V30: Progress Towards Root/TWRP/ROMs (not achieved yet)
If there's any dev magic, that will be the thread to watch.
Initially the op did not specify he wished to only talk about the T-mobile LG V30 instead of all LG V30 models -- but once we got that clarified (the first few posts on page 1) then that's what the rest of the thread is about.
---------- Post added at 07:26 AM ---------- Previous post was at 06:38 AM ----------
_______________________
arh2o said:
This is very interesting, I wonder if bootloader is unlocked on the upcoming "sim unlocked" US998 as well? If the T-Mobile bootloader is unlocked this may be a game changer.
Click to expand...
Click to collapse
Been discussed in depth since early September in the bootloader unlock and root thread -- even before the LG V30 was released. Well known, the T-mobile LG V30 would have an "unlocked" bootloader -- but it doesn't do any good because the ADB fastboot commands are removed. (September 3)
The official carrier unlocked US998 and H930 models -- the ones NOT sold by any carriers, what LG calls for the "open market" will be placed on the LG Developer Bootloader Unlock list AFTER release, and will be eligible for bootloader unlock. They will have full ADB fastboot commands. Just like the LG G6 models then they will quickly get dev support for root, recovery, ROMs, kernels.
The official carrier unlocked LG G6 US997 was released May 12, 2017 but was not placed on the the Bootloader Unlock list until June 29. SIX WEEKS. However, there's now tons of dev work available.
Let's hope it doesn't take that long after the LG V30 US998 is released!
Whereas, the T-mobile LG G6 while ostensibly having an unlocked bootloader still has no root or recovery. Six or seven months later, still no dev work available.
R800x_user said:
if only i would've seen this earlier because that's what i ended up trying out in adb and boom a voided warranty and i didn't get time to take up the daydream offer since i'm sure they will be able to see i already voided my warranty. . In the mean time i have pulled a couple of files out like for example system(i used the adb pull /system), vendor( adb pull /system/vendor) and frameworks(adb pull /system/framework). ive just been poking around trying to see if there is any way to find the boot image. any ideas where it could be located?
Click to expand...
Click to collapse
Can't pull boot without root access.
Sent from my VS995 using Tapatalk
Out of curiosity, has anyone tried
Code:
fastboot oem ?
command?
gokart2 said:
Out of curiosity, has anyone tried
command?
Click to expand...
Click to collapse
Deleted
Hi everyone, long time xda lurker, first post. I bought a family member an unlocked Moto G Power (2020) for Xmas and 5 months later it took a fatal ride in the laundry machine The prices now for an unlocked phone aren't so great, so I bought the Tracfone version (XT2041DL) that I hoped to be able to modify back into a vanilla "Retail" phone. My problem isn't with the carrier lock (it will stay on a Tracfone carrier for many years), but with the bootloader lock. If I understand correctly, Tracfone won't unlock the bootloader even after carrier unlocking, so there's no way to install the vanilla "retail" ROM on it? Even if not possible to load a different ROM, at the very least I want the ability to remove the added carrier bloatware that Tracfone installs, but doesn't this require root?
I believe that one other user of this forum mentioned getting XT2041DL root, but with a locked bootloader, won't that still prevent me from making any permanent changes to the system folder? I did manage to find one guide at the following website, but I don't know if it's a reliable source of information [link] or if it will allow me to accomplish my goal. If I'm stuck with Tracfone's version of the ROM I will probably just return it and take the financial hit of the unlocked retail. Also, forgive me if I sound uninformed, I'm still very much a novice although I've managed to root a few items previously with the help of xda guides. Really appreciate the insight or advice from the community here.
You can remove bloatware with ADB shell commands.
same question, can anyone suggest?
bizkit_120 said:
same question, can anyone suggest?
Click to expand...
Click to collapse
TracFone won't unlock the bootloader. I've tried the guide in the link OP posted and it doesn't work. One of the ADB commands does bring up the unlock warning but does nothing from there. Unfortunately the only way to unlock the BL is through Motorola's website. If you're phone is eligible, they'll send a code to unlock the phone.
Shponglehead said:
You can remove bloatware with ADB shell commands.
Click to expand...
Click to collapse
I don't think tracfone is eligible to be boatload unlocked that is the whole question where it started..not sure what adb shell cmd you are referring too? Is that work for your XT2041DL? Or you have other moto g power variants?
https://www.tfwunlockpolicy.com/wps/portal/home
youreethra said:
https://www.tfwunlockpolicy.com/wps/portal/home
Click to expand...
Click to collapse
That is carrier network unlock, not bootloader unlock.
After that, moto still refuses to unlock bootloader.
OK, 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):
[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
@mobbdeep had my SIM unlocked within 24 hours of sending him the required info.
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:
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 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...
forum.xda-developers.com
Which should unlock the OEM Unlock option in the developer options.
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.
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
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.
---
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.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
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)
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:
Code:
fastboot --version
will give your it's location.
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:
Code:
fastboot flash cust-unlock unlock_code.bin
(Thanks to @lentm for posting this command)
After checking the output, to be sure it worked, use this command:
Code:
fastboot oem unlock
Follow the on-screen instructions on your phone to finish the bootloader unlock.
you 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 locked
PopCaps1996 said:
you 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 locked
Click to expand...
Click to collapse
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.
edale1 said:
OK, that's neat.
I can't personally test it, as I already have that 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.
Click to expand...
Click to collapse
i can confirm it works that's the method i used to unlock my bootloader for my n200
Using the debloater worked beautifully to get ability to enable OEM Unlocking. Now it's just the week wait to get the code.
Really wish they'd speed that up; I've had to do this for four devices through them. Major benefit to buying direct from OnePlus, IMO. The last one I did was unlocked moments after getting home...(and is now running crDroid which I really hope comes to the N200)
PhoenixPath said:
Using the debloater worked beautifully to get ability to enable OEM Unlocking. Now it's just the week wait to get the code.
Really wish they'd speed that up; I've had to do this for four devices through them. Major benefit to buying direct from OnePlus, IMO. The last one I did was unlocked moments after getting home...(and is now running crDroid which I really hope comes to the N200)
Click to expand...
Click to collapse
you will not be able to modify anything anyways once you get the bootloader unlocked because oneplus has not released stock rom for the N200 on their website yet. so there for we do not have stock boot.img to be able to patch an root but i heard they will be uploading the rom soon. unless we can figure out how to back up boot img through fastboot but don't think that's possible
Yes, but to my knowledge unlocking the bootloader is the only part of the entire process of installing a custom recovery and rooting that wipes the device. So it's best to get that out of the way ASAP, before the phone's loaded with stuff you don't want to lose.
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
lentm said:
View attachment 5377289
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
Click to expand...
Click to collapse
can you send me the extracted payload.bin pm me please
PopCaps1996 said:
can you send me the extracted payload.bin pm me please
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/2c0d5671fc9a0f7829ab54b08139378afc295f46.zip
lentm said:
https://android.googleapis.com/packages/ota-api/package/2c0d5671fc9a0f7829ab54b08139378afc295f46.zip
Click to expand...
Click to collapse
the payload bin that you extracted? can you zip up the extractred imgs from payload . bin. an send them to me?
lentm said:
View attachment 5377289
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
Click to expand...
Click to collapse
Maybe it's because the ota is just an update, not a full zip?
PopCaps1996 said:
the payload bin that you extracted? can you zip up the extractred imgs from payload . bin. an send them to me?
Click to expand...
Click to collapse
I can get you the boot.img, not every img files. Check the attached.
lentm said:
I can get you the boot.img, not every img files. Check the attached.
Click to expand...
Click to collapse
When trying to patch the boot.img file with Magisk Stable version 23.0 (23000) (21) and Canary version f822ca5b (23001) (21), I get "Unsupported/Unknown image format. Installation failed".
dragonnightx said:
When trying to patch the boot.img file with Magisk Stable version 23.0 (23000) (21) and Canary version f822ca5b (23001) (21), I get "Unsupported/Unknown image format. Installation failed".
Click to expand...
Click to collapse
Yea, that's what I get too.
How long does OnePlus usually take in processing the bootloader unlock request?
TheLoonyRebel said:
How long does OnePlus usually take in processing the bootloader unlock request?
Click to expand...
Click to collapse
7 days
PopCaps1996 said:
you will not be able to modify anything anyways once you get the bootloader unlocked because oneplus has not released stock rom for the N200 on their website yet. so there for we do not have stock boot.img to be able to patch an root but i heard they will be uploading the rom soon. unless we can figure out how to back up boot img through fastboot but don't think that's possible
Click to expand...
Click to collapse
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
jilebi said:
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
Click to expand...
Click to collapse
I tried it and even I set it manually to N200, but no full ROM available
PopCaps1996 said:
you 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 locked
Click to expand...
Click to collapse
Do you know which specific app to uninstall removes the OEM unlock restriction? I want to unlock the bootloader, but would rather keep the other preinstalled software.
I don’t know the step By step process if someone could explain it to me the way they would explain it to someone who will be attempting to root for the first time I’d appreciate it
[email protected]@death said:
I don’t know the step By step process if someone could explain it to me the way they would explain it to someone who will be attempting to root for the first time I’d appreciate it
Click to expand...
Click to collapse
Look for the magisck thread. Read it and it's simple. I'm not bright and got it first go.
alarmdude9 said:
Look for the magisck thread. Read it and it's simple. I'm not bright and got it first go.
Click to expand...
Click to collapse
Thanks for the direction. I’m not sure if oem unlock and unlocked bootloader are the same thing, in developer option on my oneplus n200 g5 metro by T-Mobile the option to unlock oem is grayed out and I can’t unlock it from that setting is there another way
This thread has the information on unlocking your bootloader (yes, the OEM Unlock is the same as a bootloader unlock, but the option in the developers option is just one part of unlocking the bootloader, it doesn't unlock it by itself):
The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)
OK, 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...
forum.xda-developers.com
If you can run ADB commands, there's one singular command you can run to un-grey out the Enable OEM Unlock option, it's explained in that thread.
So, am I correct in assuming I’m unable to do anything with this device until I can sim unlock? Seems that’s a requirement for boot loader unlock. I got one of these for cheap cheap because I need an android device with out gapps but I’m thinking that’s not going to work until it’s sim unlocked. Any info would be appreciated. Thanks!
rcartaz09 said:
So, am I correct in assuming I’m unable to do anything with this device until I can sim unlock? Seems that’s a requirement for boot loader unlock. I got one of these for cheap cheap because I need an android device with out gapps but I’m thinking that’s not going to work until it’s sim unlocked. Any info would be appreciated. Thanks!
Click to expand...
Click to collapse
A couple pages back there is a thread on how to oem unlock without sim unlock. It involves running a debloat script or using adb to get rid of one service. It goes through every step you need to do to unlock.
Link575 said:
A couple pages back there is a thread on how to oem unlock without sim unlock. It involves running a debloat script or using adb to get rid of one service. It goes through every step you need to do to unlock.
Click to expand...
Click to collapse
Thanks! Found it and so far it’s worked. Waiting for response from OnePlus.
rcartaz09 said:
Thanks! Found it and so far it’s worked. Waiting for response from OnePlus.
No problem, it takes almost exactly a week to the hour to get the code. Rest of the guide should be fairly easy to follow too. Just remember if you ever you the MSMTool to get back to stock it relocks your bootloader. You'll need to unlock it again by using the file OP sends you before flashing other nonstock firmwares again
Click to expand...
Click to collapse
rcartaz09 said:
Thanks! Found it and so far it’s worked. Waiting for response from OnePlus.
Click to expand...
Click to collapse
Once you get the code, you can simply use my dummies guide to full rom backup, convert to US OEM (DE2117), and root and has the "oem unlock bypass" command in the guide.
scanman0 said:
Once you get the code, you can simply use my dummies guide to full rom backup, convert to US OEM (DE2117), and root and has the "oem unlock bypass" command in the guide.
Click to expand...
Click to collapse
Saw that, thanks!