Hi Friends,
I got a OnePlus N200 5G from T mobile, how can get it unlocked. please advise ..TIA
SIM (network) Unlock: https://forum.xda-developers.com/t/...rvice-oneplus-samsung-google-lg-moto.4231597/
Read the instructions carefully before sending your request.
Bootloader Unlock: https://forum.xda-developers.com/t/...-may-work-for-metropcs-metro-variant.4313525/
If you need to SIM unlock your phone, do that before Bootloader Unlocking (remote SIM Unlocking won't work after running the debloat script that lets you Bootloader Unlock without the SIM Unlock).
Hi Edale1,
Wonderful, thank you.I am completly new for XDA, i am not getting sure how to send a PM for the mobbdeep
edale1 said:
SIM (network) Unlock: https://forum.xda-developers.com/t/...rvice-oneplus-samsung-google-lg-moto.4231597/
Read the instructions carefully before sending your request.
Bootloader Unlock: https://forum.xda-developers.com/t/...-may-work-for-metropcs-metro-variant.4313525/
If you need to SIM unlock your phone, do that before Bootloader Unlocking (remote SIM Unlocking won't work after running the debloat script that lets you Bootloader Unlock without the SIM Unlock).
Click to expand...
Click to collapse
do I have to have my phone SIM unlocked in order to get the bootloader unlocked. I'm only asking because I'm actually not using a SIM with my Nord N200, I'm just using it to play around with, but it is locked to T-Mobile. I just bought the phone off of ebay. I want to convert it to DE2117 firmware so i can install LineageOS.
BranBro365 said:
do I have to have my phone SIM unlocked in order to get the bootloader unlocked.
Click to expand...
Click to collapse
No, though you'll need to use an ADB command to enable the "unlock oem" option in the dev settings.
ADB command:
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
For more detail, read my post on that second link (the bootloader unlock one).
edale1 said:
No, though you'll need to use an ADB command to enable the "unlock oem" option in the dev settings.
ADB command:
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
For more detail, read my post on that second link (the bootloader unlock one).
Click to expand...
Click to collapse
oem unlock is already enabled. I commented in your other post, it's enabled but I can't access fastboot mode, it doesn't give me the option in the recovery menu.
this adb command should get you into the fastboot:
Code:
adb reboot bootloader
If that doesn't work.... I have no idea. been a while since I did any work on my phone.
BranBro365 said:
oem unlock is already enabled. I commented in your other post, it's enabled but I can't access fastboot mode, it doesn't give me the option in the recovery menu.
Click to expand...
Click to collapse
Other than the ADB command, you can always enter fastboot mode by powering off your phone and holding down all three buttons while it's unplugged.
Related
Having trouble rooting my LG K40. I have the same problem as this person when trying to boot into fastmode: https:// youtu.be/yQ99lQv0rQk?t=26
You can find his post here explaining the process more in detail: https:// lgk20.com/root-lg-k40-lm-x420-bootloader-unlock-twrp/
MODEL #: LM-X420MM
Any help is appreciated,
Thanks in advance.
im having the same problem. i must have a proclivity towards phones with what seems impossible rooting methods. the first was the samsung j7 prime and now the lg k40 lmx420mm. ive gotten as for as adb reboot-bootloader, just restarts device, fastboot commands are either not recognized or i receive "waiting on device". Ive updated drivers, followed a diff. method found on reddit posted by jamesrascal (i cant post url here because of my newb status). Phone just stays stuck in firmware update. i feel as if ive exhausted all resources, any direction or help would be appreciated, im not educated on rooting ive been successful a few times on other phones and jailbroken some iphones, im mostly doing this to learn and teach myself so it isnt urgent but i need help to continue any further. thank you
Same problem for me. Because the device has good value for the money it would be nice someone can help us here.
Further this device seems to be full android treble conform I like to know how benefit from this circomstance.
I have LG K40 LM-X420EMW with dualsim.
Thanks for every hint!
@blanksus
IIRC an Android user can not unlock the bootloader without first OEM unlocking, because without this process the device will not accept the bootloader unlocking command.
jwoegerbauer said:
@blanksus
IIRC an Android user can not unlock the bootloader without first OEM unlocking, because without this process the device will not accept the bootloader unlocking command.
Click to expand...
Click to collapse
OK, but it is not possible to get into fastboot mode to enable the OEM unlocking. I marked the slider in developer option butz still there is no chance to get in fastboot mode.
After command "adb reboot bootloader" the device always reboots in normal system mode.
@baerenbisch
Once you enabled the OEM unlock on your Android, the “unlock ability” flag is set to 1, which allows you to use the
Code:
fastboot flashing unlock
command what unlocks device's bootloader.
BTW: Once you have enabled OEM unlock, it stays on. Even if you do a factory reset, it stays unlocked until the setting is manually altered again by going into the Developer options section.
jwoegerbauer said:
@baerenbisch
Once you enabled the OEM unlock on your Android, the “unlock ability” flag is set to 1, which allows you to use the
Code:
fastboot flashing unlock
command what unlocks device's bootloader.
BTW: Once you have enabled OEM unlock, it stays on. Even if you do a factory reset, it stays unlocked until the setting is manually altered again by going into the Developer options section.
Click to expand...
Click to collapse
Hm,
may be it is "allowed" to unlock but in the "LG K40 (LM-X420EMW) real world" it is not possible.
You dont reach fastboot mode which could enable using the order you proposed.
Device reboots into standard mode instead of wanted fastboot mode after sending "adb reboot bootloader"
I think thats the problem.
Code:
[email protected]:/# adb devices
List of devices attached
LMX4205P4TU4S4HEOJ device
[email protected]:/# adb reboot bootloader
[email protected]:/# fastboot flashing unlock
< waiting for any device >
^C
[email protected]:/#
OK, good news. One can get root with this method:
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Works for LG K40 (LM-X420EMW) Android 9 Kernel 4.9.117 Patch Level January 1, 2020 Build Nr. PKQ1.190522.001 Software-Vers. V20d-EEA-XX
baerenbisch said:
OK, good news. One can get root with this method:
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Works for LG K40 (LM-X420EMW) Android 9 Kernel 4.9.117 Patch Level January 1, 2020 Build Nr. PKQ1.190522.001 Software-Vers. V20d-EEA-XX
Click to expand...
Click to collapse
Temp root does sound nice, but what can you actually do with it. Can you change the OEM unlock key?
roycrt said:
Temp root does sound nice, but what can you actually do with it. Can you change the OEM unlock key?
Click to expand...
Click to collapse
Device can be bootloader unlocked now. MtkClient on github. I have the Harmony 3 bl unlocked and twrp for it
Can confirm, I was just able to unlock the bootloader with mtkclient and root with Magisk from there.
BenTheTechGuy said:
Can confirm, I was just able to unlock the bootloader with mtkclient and root with Magisk from there.
Click to expand...
Click to collapse
Please elaborate steps taken to unlock bootloader using mtkclient. Thanks
I wrote a guide as part of my porting of postmarketOS to my K40.
LG K40 (lg-mmh4x) - postmarketOS
wiki.postmarketos.org
Hello guys, recently I bought Chinese AllCall Madrid phone. I was searching for twrp port for that phone and I have found it on {MOD EDIT: reference to warez site} forum, only twrp for this phone on internet. I tried to flash it using flash tool it failed(flashing stock rom fails too), then I rebooted to fastboot to OEM unlock and no OEM unlock is available, output is remote failed unknown command, ofc I enabled OEM unlock developer options.. I managed to use mtk-su exploit to gain root, and I can run adb and apps with root permission. My real question is has anyone unlocked this phone? If yes pm me please :laugh:
@Mr nobody 1312
Assuming you want to unlock the bootloader.
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
If it's supported then you run
Code:
fastboot flashing unlock
to unlock the bootloader.
Yeah output is 1 but no OEM command is found in lk.bin I decompiled it, they locked it to push their malware I have found addups fota malware and virus in helper apk, anyway is it possible to crack bootloader with custom lk.bin, where I should look for exoloitable bugs? Is there any freaking way to crack it?
Hi! My name is Bautista.
This is my first post well explained, I already asked this question before but I did not express myself well (I hope to do it correctly in this attempt)
My problem happens with my Samsung Galaxy A01 SM-A015M, Running on OneUI 2.0/Android 10 with 2gb of ram, a Snapdragon 439, the stock rom/firmware and 32GB of storage, from Argentina.
Things I tried so far, and didn't work for me:
Unlocking the bootloader by following the Gearallnews and Cyanogenmods guides to the letter.
When trying to unlock the bootloader with the guides on the aforementioned pages, when starting the device a sign should appear saying that the bootloader is unlocked, which did not appear.
The device started correctly in the process to configure the device the first time it is turned on, connect the wifi as the guides said. Followed by that I went to the developer options and the option "Oem unlock" was still activated and in blue (which should not happen, it should appear grayed) I heard that some Samsung devices with snapdragon processors had a bootloader that cannot be unlocked
Unlocking the bootloader using ADB AND Fastboot. (ADB detects my device fine, but fastboot doesn't detect it at all)
Using Fastboot from Windows 7, Windows 10, and Kali Linux.
Installing TWRP.
Use rooting apps. (the ones that appear on the XDA rooting page)
What I am going to with this thread, is:
Can my device's bootloader be unlocked? And if so, how?
If the bootloader cannot be unlocked, how can I root or install TWRP?
Please, if you don't understand something or need more information, let me know by replying to this thread or sending me a private message.
Look inside here.
jwoegerbauer said:
Look inside here.
Click to expand...
Click to collapse
it's the same as Gearallnews and Cyanogenmods guides, i already did that, it dont work
Like the original poster I also have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) Panama. I have gone through all the aforementioned procedure and the bootloader does not unlock. There is no bootloader unlock warning on reboot and the OEM Unlock in developer option does not grey out. Does the Snapdragon processor not allow bootloader unlock or is anyone aware of a solution. Thanks for any assistance.
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
jwoegerbauer said:
@mullerh
If in Settings -> Developer Option the option "OEM unlock" is present then unlocking the bootloader obviously isn't denied by OEM/Carrier.
But you can check it at your own:
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
Click to expand...
Click to collapse
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
mullerh said:
Thanks for your response and assistance. The command:
adb shell "getprop ro.oem_unlock_supported" returns a 1
I googled it but found no clarification but I assume that means it is supported.
Therfore there is something else that is blocking the bootloader from unlocking from the unlock mode screen and just prior to reset.
There is also no unlock bootloader warning during the reset.
The more I have Googled this problem the more it seems to indicate that many newer Samsung phones released in North/Latin America with Qualicom Snapdragon 439 processors, have the the bootloaders locked down with a new "security" feature called SecureBoot. Would be interested in getting the experience of others. Thanks
Click to expand...
Click to collapse
Hi! Did you manage to find a way to unlock the bootloader?
I have not been able to unlock the bootloader on this SM-A015M/DS (Latin American) model with Snapdragon processor. I have done a lot of searching but found little info except articles stating Samsung had gone through some extra effort to secure their latest phones. That also means I can not root it. I was hoping to get some feedback from other who may have had a better experience,
have you tried using the twrp app to install twrp?
i had an old galaxy grand prime which was impossible to unlock, but the app worked without issues
the only thing i had to pay attention is to turn it off right before ir reboots after installing and then loading into recovery
letting the mobile startup without doing this overrieded the command to install twrp
Thanks for your response. It is my understanding (I could be wrong) that before TWRP can be installed the Bootloader needs to be unlocked. The older Samsung usually allowed the Bootloader to be unlocked even if there was difficulty in rooting them. It appears that some of the newer Samsung's with the Snapdragon processors have added an additional security feature called SecureBoot which blocks the Bootloader from being unlocked.
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
For what it's worth, when I flashed the firmware onto the phone in the first place, I had to enable the developer option manually- I did this by booting into download mode and then a long press on the volume up button when prompted by the menu. I don't see why this wouldn't work for other devices. There are youtube videos that explain in greater detail if you haven't tried this yet.
Newiser7 said:
Does anyone have a definitive answer for how to turn the bootloader on? I recently purchased a SM-A015M/DS and didn't have issues with the OEM bootloader option appearing in the options. But when I enter fastboot mode it says my device status is locked. I can't work out if that means it's locked or not.
Click to expand...
Click to collapse
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
jwoegerbauer said:
Enabling OEM unlock option in Developer options does NOT UNLOCK the bootloader. Once you enable the OEM unlock on your device, the unlock ability flag is set to 1, which will allow users to use the fastboot flashing unlock command, the command what starts the "unlocking the bootloader" procedure.
FYI:
After the command is executed, you will see an option for bootloader unlock on your device’s screen.
Use the volume buttons to move up and down and select the option to unlock the bootloader.
A prompt will pop up, asking for confirmation. Use the power button to confirm your selection as yes, and you are done.
The phone will now reboot to fastboot mode. Enter the command “fastboot reboot,” and it will boot into PC.
Click to expand...
Click to collapse
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
mullerh said:
FYI:
Samsung devices do not support fastboot command, you use Odin or Heimdall to flash what you need.
The answer you provide is misleading
Click to expand...
Click to collapse
You are right: I was mistaken.
Thank you for clarifying that the bootloader is still locked. But how can I unlock it? Odin will let me flash the files, but I keep getting AUTH errors when I try to flash magisk patched files to root the phone. I'm assuming this is because the bootloader preventing the files from transferring. Is there a way to unlock it using ADB without fastboot, or a way using Odin? It seems crazy that unlocking the bootloader is enabled but I am still unable to actually unlock it.
I have also tried the CROM Service app (couldn't get it to install on my phone, error 3003 with ADB install), as well as the bootloader unlock method where I boot into download mode, hold the volume up key, and unlock the bootloader that way. I have done the latter at least 5 times and the bootloader is still locked. Ridiculous.
This prop apparently only confirms that the phone supports being unlocked, not that it is actually unlocked.
adb shell "getprop ro.oem_unlock_supported"
Check a few others, also see the official docs.
sys.oem_unlock_allowed
androidboot.flash.locked (the docs say this, but I think Samsung uses something different)
ro.boot.flash.locked
ro.boot.other.locked
Maybe also check these:
ro.boot.verifiedbootstate
ro.boot.veritymode
The docs indicate that the verifiedbootstate should be orange if the bootloader is unlocked. I don't know much about it, though.
You can always use grep to search for any interesting values, like "lock" or "boot" or "flash":
adb shell getprop | grep lock
adb shell getprop | grep boot
adb shell getprop | grep flash
Maybe report any interesting values you have with and without OEM Unlock checked. Maybe someone smarter than us will find it useful.
I would really like to see an A01 root happen, it's such an affordable and accessible device for all sorts of things. Great as a backup device or for a project. You think someone would've released some goods for it by now. It's been out all year.
And for the 16GB model, it's absolutely terrible because Samsung eats up so much space, then has the nerve to remove the Adoptable Storage feature. So even if you get a fast SD card, you can't install apps on it. Other than that, it's a perfectly serviceable phone. I would think with root we could get Adoptable Storage working.
To summarize what has been previously stated the Samsung Galaxy A01, version SM-A015M/DS is the Latin American version of this cellphone. This cellphone has a Snapdragon processor. This version is very similar to the versions (also Snapdragon processors) used by some US Carriers. Many current versions of Samsung cellphones have an additional security feature called "SecureBoot" which blocks bootloader unlocking. Some say this features was added at the request of US Carriers
The Asian version of the A01 has a Exynos processor. It is my understanding that with these it is very easy to unlock the bootloader and root the phone using the usual conventional methods. The Asian variant unfortunately does not cover some of the wireless bands used in the US/Canada/Latin America.
I have a Samsung Galaxy A01 SM-A015M/DS, OneUI 2.0/Android 10, 2GB ram, 32GB storage, Snapdragon 439, stock firmware (TPA) for Panama.
My research indicates that there is not yet an available bootloader unlocking and easy root method for this (A01) phone. For some other current Samsung models there does appear to be a method of flashing certain custom ROMs without a bootloader unlock but they appear to come with problems which include loss of some cellphone functions and a reduction in the charged battery life. So it seems hardly worth it.
It also appears that it is current well known that all current Samsung phones with Snapdragon processors have not allowed bootloader unlocking and rooting due to the enhanced security feature.
At this time we can only complain and/or not buy any additional Samsung phones
Perhaps with time skillful developers will come up with a method to solve this problem with this inexpensive A01.
Please provide any new or updated info if you have it.
Any solution for rooting Galaxy A01 ?
I use A015f region SER (Russia) In Russia, too, the device is locked (bootloader) of course, give any solution
One thing I know is that a fellow SM-M015f, which is almost identical, which is with the same Snapdragon 439, except for the battery capacity and screen size and gigabytes of internal memory, successfully unlocks and gets Magisk root.
this phone actually has a fastboot mode, from recover mode select reboot to bootloader, it will boot to fastboot mode,but ive still been unsucessful in getting fastboot mode to work, devices manager reports device error,
I can start the unlock proccess.
But after it is done and the data is wipped,
It keeps locked.
Sad
There's a good black friday deal for this phone, but the Mint Mobile variant doesn't seem to really be mentioned here. What are the odds it can be unlocked like the TMobile version?
I'd imagine that the Mint variant of this phone is the same as the T-Mobile variant. If that's the case, the official way to unlock the bootloader requires SIM unlocking the device. However, Mint's unlock policy kinda sucks...
Customers must have had their locked device activated on Mint Mobile service for no fewer than 12 months...
Click to expand...
Click to collapse
However, you can also try running this ADB command to enable the OEM unlock option in Developer options without SIM unlocking the device (from this thread):
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
If that works, you can just request an unlock code from OnePlus and get your bootloader unlocked. See the linked thread for details.
Yes I unlocked mine with fastboot oem commands
This is regarding unlocking bootloader on T-Mobile varient. There are two observations.
1) After device is SIM unlocked modification of the setting that was greyed out, 'OEM Unlocking' will be possible..2) Without device being SIM unlocked, modification of same setting is possible by performing the ADB command ("adb shell pm uninstall --user 0 com.qualcomm.qti.uim")Surely the manufacturer wouldn't make SIM unlocking as easy as performing a simple ADB command. But if not, wouldn't that imply that it is, in fact, NOT necessary for device to be SIM Unlocked to Unlock bootloader? It Don't make any sense.
Has anyone tried to unlock bootloader on SIM Locked device and did it work? what happened?
I took my SIM Locked T-Mobile N200 that I never paid a single month for and that was blacklisted and account sent off to collections.
I did ADB command to enable OEM Unlocking. Went to FASTBOOT and acquired the unlocking key. I sent key to ONEplus via their T-Mobile Unlocking webpage. And Oneplus responded a week later with my unlock_code.bin file.. DEVICE UNLOCKED
So I guess this would imply that ability to modify the greyed out OEM unlocking is the only way to unlock bootloader and NOT that 'device must SIM Unlocked' as instructed in the unlocking process.. Device being SIM unlocked is simply just ONE method of allowing modification of that setting? Right??
If you use the adb command and send your IMEI through the device unlock portal on OnePlus.com, you can be bootloader unlocked without being sim unlocked.
It just seems too easy for a T-Mobile locked Contract phone to be unlocked, don't they check the Device against some sort of database or something before providing you the unlock_code.bin??
alienG0D said:
It just seems too easy for a T-Mobile locked Contract phone to be unlocked, don't they check the Device against some sort of database or something before providing you the unlock_code.bin??
Click to expand...
Click to collapse
Nope, mine is still on bill credits.
alienG0D said:
It just seems too easy for a T-Mobile locked Contract phone to be unlocked, don't they check the Device against some sort of database or something before providing you the unlock_code.bin??
Click to expand...
Click to collapse
The unlock_code.bin file lets you bootloader unlock the phone. This does NOT SIM/network unlock your phone... Though with T-Mobile you're supposed to be SIM unlocked before you can bootloader unlock, we just figured out how to bypass that.
They just linked the SIM unlock to the same thing we've been using, is my guess. I'd be interested to know if I'm right, but at this point, it's moot.
SIM UNLOCKED (bought in September/2021)
It got sim-unlocked after 180day, by simply pressing "unlock permanently" without using Metro or T-Mobile sim ever. after 180day however the phone is seems out of time (outdated).