Hi, I have a device that does not allow the unlocking of the bootloader, obviously it is a mediatek, if I take the file lk.bin on HxD it says "oem unlock is false.cmd_boot", there is no way to modify the file Lk.bin and add the oem unlock command?
When I do oem unlock on fastboot it says unknown command.
Try This
Try this : Type: fastboot flashing unlock
SlendowManX said:
Try this : Type: fastboot flashing unlock
Click to expand...
Click to collapse
Not work
XRed_CubeX said:
Not work
Click to expand...
Click to collapse
A phone's Fastboot is not always the same as AOSP Fastboot. How Fastboot is implemented depends on OEM/Carrier. If a chipset related flash tool is provided then you can assume that Fastboot does not work as expected.
XRed_CubeX said:
Hi, I have a device that does not allow the unlocking of the bootloader, obviously it is a mediatek, if I take the file lk.bin on HxD it says "oem unlock is false.cmd_boot", there is no way to modify the file Lk.bin and add the oem unlock command?
When I do oem unlock on fastboot it says unknown command.
Click to expand...
Click to collapse
LK.BIN is ( Qualcomm's version of ) device's bootloader. Wondering why you want to modify it ( i.e. remove/change text in it ), this because of all settings related to device's bootloader are stored in Android's system file named build.prop?
FYI:
LK.BIN has the following:
Variety of nand devices for bootup
USB driver to enable upgrading images over usb during development
Keypad driver to enable developers enter ‘fastboot’ mode for image upgrades
Display driver for debugging and splash screen
Enable Android recovery image and image upgrades
jwoegerbauer said:
LK.BIN is ( Qualcomm's version of ) device's bootloader. Wondering why you want to modify it ( i.e. remove/change text in it ), this because of all settings related to device's bootloader are stored in Android's system file named build.prop?
FYI:
LK.BIN has the following:
USB driver to enable upgrading images over usb during development
Keypad driver to enable developers enter ‘fastboot’ mode for image upgrades
Display driver for debugging and splash screen
Enable Android recovery image and image upgrades
Click to expand...
Click to collapse
Ok if I don't have to edit LK then what should I edit on build prop to unlock the bootloader? Fastboot oem unlock and flashing unlock does not work, says unknown command
P.S: Everyone has the same problem as me and in any case my soc is Mt6737M and the OEM is Meizu, it has no official tools released to unlock the bootloader and I would like to know if there is another way
XRed_CubeX said:
P.S: Everyone has the same problem as me and in any case my soc is Mt6737M and the OEM is Meizu, it has no official tools released to unlock the bootloader and I would like to know if there is another way
Click to expand...
Click to collapse
I guess there is no other method.
Take note that carrier exclusive models (ex. Verizon, AT&T, Tracfone) are almost never unlockable. Probably your device is one of these.
BTW: To edit Android's system file build.prop device's Android must got rooted before what requires SuperSU ( or similar ) got installed before what requires device's bootloader got unlocked before ...
jwoegerbauer said:
I guess there is no other method.
Take note that carrier exclusive models (ex. Verizon, AT&T, Tracfone) are almost never unlockable. Probably your device is one of these.
BTW: To edit Android's system file build.prop device's Android must got rooted before what requires SuperSU ( or similar ) got installed before what requires device's bootloader got unlocked before ...
Click to expand...
Click to collapse
My meizu has a pre-installed Root (can be activated with the flyme account), it is also convertible into SuperSU. However my device is not part of any carrier.
So having the root I can easily modify build.prop
@XRed_CubeX
OK, then look inside here.
EDIT:
You additionally can try to replace existing ADB & Fastboot binaries by those as attached
jwoegerbauer said:
@XRed_CubeX
OK, then look inside here.
EDIT:
You additionally can try to replace existing ADB & Fastboot binaries by those as attached
Click to expand...
Click to collapse
Ok i try later but what i have to do with this binaries?
jwoegerbauer said:
@XRed_CubeX
OK, then look inside here.
EDIT:
You additionally can try to replace existing ADB & Fastboot binaries by those as attached
Click to expand...
Click to collapse
Anyway with mixplorer I tried to modify the build.prop and add "ro.oem_unlock_supported = 1" but nothing, if I restart in fastboot and I do fastboot flashing unlock this comes out:
Code:
D:\Users\XRed_CubeX\Desktop>fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
XRed_CubeX said:
Code:
D:\Users\XRed_CubeX\Desktop>fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
Remember I told you
A phone's Fastboot is not always the same as AOSP Fastboot. How Fastboot is implemented depends on OEM/Carrier.
Click to expand...
Click to collapse
Understand finally that implementation of Fastboot on your phone isn't the same as AOSP Fastboot.
jwoegerbauer said:
Remember I told you
Understand finally that implementation of Fastboot on your phone isn't the same as AOSP Fastboot.
Click to expand...
Click to collapse
Yes ok but anyway I did what you told me that is to modify the build prop as I told you before and nothing has changed, I don't know if I missed something but what I changed I wrote before
XRed_CubeX said:
Yes ok but anyway I did what you told me that is to modify the build prop as I told you before and nothing has changed, I don't know if I missed something but what I changed I wrote before
Click to expand...
Click to collapse
My last 2 cents here:
IIRC I never told you to modify build.prop entries to get things work as expected.
jwoegerbauer said:
My last 2 cents here:
IIRC I never told you to modify build.prop entries to get things work as expected.
Click to expand...
Click to collapse
So what should I do in my case?
jwoegerbauer said:
My last 2 cents here:
IIRC I never told you to modify build.prop entries to get things work as expected.
Click to expand...
Click to collapse
P.S:I tried to look at the build.prop better but there is nothing interesting or attributable to an unlocking of the bootloader, there is probably nothing to do, if you are interested, here is a site where there is the build.prop.
Related
Hello ?
I'm looking to root my m4 aqua E2303 6.0.1 Bootloader unlock: yes
However I don't want any twrp stuff, last time I rooted this phone I found something on this forum, connected my phone to a pc via USB ran an exe and it got rooted it was soooo simple, and everything worked great, however after Sony released the firmware update(from 5.0.0 to 6.0.1) root dissappeared. Isn't there a similar tool for 6.0.1? I really don't want to get into all the twrp stuff and ehhh you understand, I want to keep it simple.
Thanks in advance.
Procow said:
Hello
I'm looking to root my m4 aqua E2303 6.0.1 Bootloader unlock: yes
However I don't want any twrp stuff, last time I rooted this phone I found something on this forum, connected my phone to a pc via USB ran an exe and it got rooted it was soooo simple, and everything worked great, however after Sony released the firmware update(from 5.0.0 to 6.0.1) root dissappeared. Isn't there a similar tool for 6.0.1? I really don't want to get into all the twrp stuff and ehhh you understand, I want to keep it simple.
Thanks in advance.
Click to expand...
Click to collapse
in Android 6.0.1 Without Unlock Bootloader is Impossible, but if you have Unlock Bootloader Use it,( Just Flash boot.img) : http://forum.xda-developers.com/m4-aqua/general/root-twrp-sony-xperia-m4-aqua-t3503369
And you can try KingoRoot Soft for root without Unlockbootloader
Whaaaaatt?
It just says waiting for device,
Debugging on oem on
Procow said:
It just says waiting for device,
Debugging on oem on
Click to expand...
Click to collapse
Maybe its not working.
Good luck
Yo
EHSAN™ said:
Maybe its not working.
Good luck
Click to expand...
Click to collapse
Let me explain, I'm doing the adb method, when I say fastboot flash boot boot.img it just says waiting for device
My phone doesn't react at all
I haven't manually unlocked the Bootloader it's so hard and time consuming to download all those programs.
I want only the root nothing else.
Procow said:
Let me explain, I'm doing the adb method, when I say fastboot flash boot boot.img it just says waiting for device
My phone doesn't react at all
I haven't manually unlocked the Bootloader it's so hard and time consuming to download all those programs.
I want only the root nothing else.
Click to expand...
Click to collapse
Need to unlock Bootloader for Root With ADB.
I did now
EHSAN™ said:
Maybe its not working.
Good luck
Click to expand...
Click to collapse
EHSAN™ said:
Need to unlock Bootloader for Root With ADB.
Click to expand...
Click to collapse
I did but now when I type fastboot devices
Hdjebshshd(that phone ID u know)
Then I type
Fastboot flash boot boot.img
It says something about downloading, max file size and then says FAILED
Procow said:
I did but now when I type fastboot devices
Hdjebshshd(that phone ID u know)
Then I type
Fastboot flash boot boot.img
It says something about downloading, max file size and then says FAILED
Click to expand...
Click to collapse
You must be going on Fastboot Mod Then Type this in ADB, And Read There Topic that i give you.
Well
EHSAN™ said:
You must be going on Fastboot Mod Then Type this in ADB, And Read There Topic that i give you.
Click to expand...
Click to collapse
I just open a command prompt in the adb folder and type it, it says command line is not allowed even if I try doing it in the administrator rights.
First it says max file size
,,OKAY"
Loaded(0.703seconds)
....,,boot"
Failed(command line is not allowed)
Something similar to this.
What am I doing wrong? How can I check if I actually unlocked the Bootloader(pretty sure I did)
So weird.
Procow said:
I just open a command prompt in the adb folder and type it, it says command line is not allowed even if I try doing it in the administrator rights.
First it says max file size
,,OKAY"
Loaded(0.703seconds)
....,,boot"
Failed(command line is not allowed)
Something similar to this.
What am I doing wrong? How can I check if I actually unlocked the Bootloader(pretty sure I did)
So weird.
Click to expand...
Click to collapse
*#*#7378423#*#* > Service Info > Configuration > Rooting Status:
Figured everything out, just don't know how lol
In the end I now have root ty.
Tell me how you fixed it
Hi, I'm having issues trying to root brand new XZ1 following this guide: https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375 .
When I try to fastboot flash G8342 boot img I get "Flashing is not allowed in Lock State" error. I have made sure that OEM bootloader is unlocked in developer options...
I have tried updating drivers, using different boot img no luck. Anyone know what the solution is?
goldenboy23 said:
Hi, I'm having issues trying to root brand new XZ1 following this guide: https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375 .
When I try to fastboot flash G8342 boot img I get "Flashing is not allowed in Lock State" error. I have made sure that OEM bootloader is unlocked in developer options...
I have tried updating drivers, using different boot img no luck. Anyone know what the solution is?
Click to expand...
Click to collapse
Sounds like your bootloader is still locked, just because you flipped the OEM switch doesn't mean it's unlocked... Go read over here before you do anything else.. ( https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ )
lilbrat said:
Sounds like your bootloader is still locked, just because you flipped the OEM switch doesn't mean it's unlocked... Go read over here before you do anything else..
Click to expand...
Click to collapse
Thanks, that's a good guide. But when I try to run "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it always returns that the command's syntax is incorrect. Is this because I don't have 26.0.2 platform tools?
goldenboy23 said:
Thanks, that's a good guide. But when I try to run "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it always returns that the command's syntax is incorrect. Is this because I don't have 26.0.2 platform tools?
Click to expand...
Click to collapse
Did you get your unlock code?
lilbrat said:
Did you get your unlock code?
Click to expand...
Click to collapse
Actually I sorted that out, I was entering it with the brackets when I was meant to remove them. But when I enter it now, it doesn't tell me incorrect syntax, but tells me instead "unknown option: -- i" I wonder if this is an issue of using too new version of Platform tools? (I'm using 28.0.1)
Right I figured it out. Just omitted the -i option and it worked. So it looked like "fastboot oem unlock 0x<unlock code>"
no further issues cheers
I get same problem (bootloader unlocked, OEM unlocked .....But show I'm in lock state)
goldenboy23 said:
Hi, I'm having issues trying to root brand new XZ1 following this guide: https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375 .
When I try to fastboot flash G8342 boot img I get "Flashing is not allowed in Lock State" error. I have made sure that OEM bootloader is unlocked in developer options...
I have tried updating drivers, using different boot img no luck. Anyone know what the solution is?
Click to expand...
Click to collapse
Google 'unlock xperia bootloader', and check the xz1 compact forum for the DRM backup method for your phone. (I know you said you have a xz1)
You need to unlock the bootloader using a code from sony, and enter it via a fastboot command before twrp can be booted/installed.
UPDATE (03/09/2019):
This thread is now dedicated to the development of the Vertu Aster P replica, which has MTK's MT6755 Helios P10 chipset.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi All,
I've just recently bought a Vertu Aster P replica, which came pre-loaded with a Vertu-themed (skinned) version of Android 6.0 Marshmallow. In the 'About Device' menu, however, the developers have (not so cleverly) disguised it to say Android 8.1.0 (Oreo). Why they would do this, rather than just taking Oreo and skinning it with the Vertu theme, I don't know. Anyway, I've gone and hard bricked the phone while trying to install a custom recovery, and it will not turn on or charge. It is still recognised when plugged into the laptop, so if I had the original ROM that it came with, I would be able to reflash it and have a working phone again. Sadly, I cannot find the ROM for it anywhere online. I can find the ROM's for the Vertu Signature Touch replica and Vertu Ti, and others, but not for the new Aster P replica, which uses the MT6755 chipset. Here are a few photos of the phone's OS. So, I'm wondering if anyone might be able to point me in the right direction of where I might be able to find this ROM. I have already been in contact with the company I bought it from. Still waiting to hear back from them. Hopefully they can just send me a download link.
Chris
Still living in hope that someone has access to the ROM for this phone.
Someone kind enough eventually came along and sent me the ROM. Flashed it and my phone now works again. Lesson learnt. ALWAYS DO A BACKUP BEFOREHAND.
I will upload it myself and make it available on here for other Aster P (replica) owners shortly.
Chris
Here it is.
https://www.needrom.com/download/vertu-aster-p-mt6755-chinese-clone-firmware/
I have also successfully managed to root the device using Magisk. If anyone else has the same device and wishes to root it, I'll guide you through the method if need be.
Chris
chris8189 said:
I have also successfully managed to root the device using Magisk. If anyone else has the same device and wishes to root it, I'll guide you through the method if need be.
Chris
Click to expand...
Click to collapse
Chris are you fastbooting to Recovery or actually flashing to the recovery partition?
I found a TWRP on XDA forums which @lopestom made for the BLU Pure XR P0030UU smartphone -
https://forum.xda-developers.com/pure-xr/development/twrp-twrp-3-1-x-x-blu-pure-xr-p0030-t3623865
The above phone also has the MT6755 P10 Helios chip, same as the Vertu Aster P clone, so I thought I would try and port the ROM over for the Vertu Aster P replica.
I got an error while doing the repack, however @ashyx managed to perform a successful repack on the image file and the phone does indeed boot up the TWRP. Problem is, there is no touch functionality. Plugging in an OTG mouse however might work, or likewise flashing the recovery image file to the boot partition, doing what you need to do in TWRP, and then flashing the stock (or modified) boot image back. I have put the feelers out for the kernel source, so (hopefully) we can then do the necessary tweaks to make TWRP function correctly, or even better, build a TWRP from source (if we can get it). Below is the link to the TWRP file.
https://mega.nz/#!J45FWIzJ!aFyFooO5aOtxjFany_osL4BpRRQSMljQjtfnYSFKDis
Chris
ashyx said:
Chris are you fastbooting to Recovery or actually flashing to the recovery partition?
Click to expand...
Click to collapse
I am flashing the recovery using SP Flash Tool (for MTK devices) to the recovery partition.
Chris
chris8189 said:
I am flashing the recovery using SP Flash Tool (for MTK devices) to the recovery partition.
Chris
Click to expand...
Click to collapse
Does this device not support fastboot?
Also does touch work if flashed to the boot partition?
ashyx said:
Does this device not support fastboot?
Also does touch work if flashed to the boot partition?
Click to expand...
Click to collapse
Yes, the device does support fastboot mode.
When flashing this TWRP to the boot partition, touch functionality, and all aspects of TWRP work perfectly.
Chris
chris8189 said:
Yes, the device does support fastboot mode.
When flashing this TWRP to the boot partition, touch functionality, and all aspects of TWRP work perfectly.
Chris
Click to expand...
Click to collapse
What happens if you just Fastboot boot 'recovery.img' rather than flashing it?
ashyx said:
What happens if you just Fastboot boot 'recovery.img' rather than flashing it?
Click to expand...
Click to collapse
When I do that, it says that oem unlock is false, however in the developer options on my phone, I have the OEM Unlock turned on, so I don't understand why it's saying that. When type in 'fastboot oem unlock', my phone gives me the option to unlok the bootloader, or not, with the volume up and down keys. Volume up being unlock the bootloader and volume down being don't unlock the bootloader. When I press volume up, nothing happens. If I press volume down, however, it allows me to not unlock the bootloader, lol. Has an extra layer of security been added to this device? Is the OEM unlock option in my dev options just a fake toggle switch?
Chris
chris8189 said:
When I do that, it says that oem unlock is false, however in the developer options on my phone, I have the OEM Unlock turned on, so I don't understand why it's saying that. When type in 'fastboot oem unlock', my phone gives me the option to unlok the bootloader, or not, with the volume up and down keys. Volume up being unlock the bootloader and volume down being don't unlock the bootloader. When I press volume up, nothing happens. If I press volume down, however, it allows me to not unlock the bootloader, lol. Has an extra layer of security been added to this device? Is the OEM unlock option in my dev options just a fake toggle switch?
Chris
Click to expand...
Click to collapse
What result do you get for:
fastboot oem device-info
I tried it and the command doesn't work.
chris8189 said:
I tried it and the command doesn't work.
Click to expand...
Click to collapse
Try:
fastboot getvar unlocked
Typing 'fastboot getvar unlocked' confirms that the bootloader is locked. It says 'unlocked :no'
Chris
chris8189 said:
Typing 'fastboot getvar unlocked' confirms that the bootloader is locked. It says 'unlocked :no'
Chris
Click to expand...
Click to collapse
It definitely says OEM_UNLOCK enabled in developer settings and you're issuing the oem unlock command while in FASTBOOT mode?
ashyx said:
It definitely says OEM_UNLOCK enabled in developer settings and you're issuing the oem unlock command while in FASTBOOT mode?
Click to expand...
Click to collapse
Correct.
I read up online about it and some MTK devices don't support bootloader unlocking. Or, you have to obtain an 'unlock code' from the manufacturer.
Chris
chris8189 said:
Correct.
I read up online about it and some MTK devices don't support bootloader unlocking. Or, you have to obtain an 'unlock code' from the manufacturer.
Chris
Click to expand...
Click to collapse
Probably a daft question, but have you actually tried booting the unpacked twrp recovery image?
If these devices are so similar maybe the kernel is too.
ashyx said:
Probably a daft question, but have you actually tried booting the unpacked twrp recovery image?
If these devices are so similar maybe the kernel is too.
Click to expand...
Click to collapse
It doesn't load. It bootloops. So they have different kernels.
Chris
i try the version of Magisk 23.0 but this is not worked.
It's the same with all other Xperia devices without customise recovery.
You first use Unsin (can find it in XDA) to the boot_blahblahblah.sin from stock firmware for unsin it. Therefore you will see a .IMG is generated.
Second, you transfer the .IMG to your phone, and use Magisk to patch (install - select file and patch) the boot file.
After it's patched (you can find it in the Download folder). Transfer the patched one back to your PC, and make phone enter fastboot mode (or the blue light mode). Then you run this command on Windows Shell (Google it, it's easy)
Fastboot flash boot the_file_name.img
After it's done, boot into your phone, you can find icon of Magisk, install it, and your phone is rooted in this stage.
Nevermind figured it out
Kylewolf said:
Nevermind figured it out
Click to expand...
Click to collapse
Before you do anything, a unlocked bootloader is must required.
JaneValley said:
It's the same with all other Xperia devices without customise recovery.
You first use Unsin (can find it in XDA) to the boot_blahblahblah.sin from stock firmware for unsin it. Therefore you will see a .IMG is generated.
Second, you transfer the .IMG to your phone, and use Magisk to patch (install - select file and patch) the boot file.
After it's patched (you can find it in the Download folder). Transfer the patched one back to your PC, and make phone enter fastboot mode (or the blue light mode). Then you run this command on Windows Shell (Google it, it's easy)
Fastboot flash boot the_file_name.img
After it's done, boot into your phone, you can find icon of Magisk, install it, and your phone is rooted in this stage.
Click to expand...
Click to collapse
good job my friend.
JaneValley said:
Before you do anything, a unlocked bootloader is must required.
Click to expand...
Click to collapse
Hello
Did you find Xperia 1 iii on Sony Developer site?
Or how did you achieve the unlock file?
Regards,
Olavbson
Where the hell do i find the official firmware, thats where im stuck
ya id like to unlock bootloader so i can achieve root on us xperia 1 iii. nothing has worked. and xperia 1 iii isnt on sony develope site to unlock bootloader. either. how are people doing this.
jporter396 said:
ya id like to unlock bootloader so i can achieve root on us xperia 1 iii. nothing has worked. and xperia 1 iii isnt on sony develope site to unlock bootloader. either. how are people doing this.
Click to expand...
Click to collapse
same am stuck at bootloader unlock rn. Cannot flash
olavbson said:
Hello
Did you find Xperia 1 iii on Sony Developer site?
Or how did you achieve the unlock file?
Regards,
Olavbson
Click to expand...
Click to collapse
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
AJHutchinson said:
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
Click to expand...
Click to collapse
What about DRM keys? how do u deal with that.
AJHutchinson said:
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
Click to expand...
Click to collapse
Hey sorry another question, i know rooting will kill netfleex and such but did u notice any other side effects, can you still view HDR
rom4ster said:
Hey sorry another question, i know rooting will kill netfleex and such but did u notice any other side effects, can you still view HDR
Click to expand...
Click to collapse
I haven't noticed anything that's not working buddy
AJHutchinson said:
I haven't noticed anything that's not working buddy
Click to expand...
Click to collapse
Thanks, sorry to bother you more but how did you unlock the phone exactly?
I am getting this error on fastboot
fastboot oem unlock 0x2DC728328A49EEAB
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
rom4ster said:
Thanks, sorry to bother you more but how did you unlock the phone exactly?
I am getting this error on fastboot
fastboot oem unlock 0x2DC728328A49EEAB
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
Mine was doing the same buddy, make sure you have entered the correct IMEI and that you have OEM unlock and usb debugging turned on in the developer settings
AJHutchinson said:
Mine was doing the same buddy, make sure you have entered the correct IMEI and that you have OEM unlock and usb debugging turned on in the developer settings
Click to expand...
Click to collapse
i verified OEM unlock is on in settings I am copying the IMEI reported by ADB directly, and USB debugging is on yet the error persists. What solved it for you?
rom4ster said:
i verified OEM unlock is on in settings I am copying the IMEI reported by ADB directly, and USB debugging is on yet the error persists. What solved it for you?
Click to expand...
Click to collapse
Check the IMEI by dialing *#06# see if it matches up with that one, if using Dual SIM variant use the first code
AJHutchinson said:
Check the IMEI by dialing *#06# see if it matches up with that one, if using Dual SIM variant use the first code
Click to expand...
Click to collapse
Also is
Code:
Fastboot devices
showing a device? Maybe it's not installed properly?
same issue here. command not supported error. did everything on sony guide to the t. us variant, windows 10. not sure what to do
fastboot shows device too
jporter396 said:
same issue here. command not supported error. did everything on sony guide to the t. us variant, windows 10. not sure what to do
fastboot shows device too
Click to expand...
Click to collapse
Annoying aye, my issue was with the IMEI I must have been putting a wrong digit in but it worked eventually
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.