Related
I created a detailed set of step by step instructions for unlocking and rooting the HTC One (M8). This process will work for other HTC models as well, however, obviously I have not tested every phone, and as I have just upgraded to the M8, this process will apply directly to it. I apologize in advance if this steps on anyone's toes, as I will be including download links for specific tools needed. These steps can be found in different threads and guides, but I had not seen one that detailed the entire process from start to finish. Basically, I wrote it in layman's terms so that I was easily able to understand the process. Hopefully this will help anyone having any sort of issues. If anyone feels that this guide is inappropriate, please feel free to delete it, as this is my first "how to"
- Unlocking your AT&T HTC One (M8)
The first thing you will need to do is create a folder labeled "Android". Different guides recommend that you place it on your desktop for easy reference, however, it can actually be placed wherever you wish, as long as you feel confident in navigating to the folder via a command prompt or terminal. For my purposes, I host the folder on my D:\ drive. If you are unable to navigate folders using a command prompt or terminal, Windows 7 and Windows 8 will allow you to right click on a folder and open a command prompt that way.
Downloading the necessary drivers - Drivers can be found by following the link found here:
http://forum.xda-developers.com/showthread.php?t=2019615
CNexus was nice enough to point out that HTC Sync is a lot of bloatware and not required, but can be downloaded if you wish. I opted to download the drivers only. This is a matter of personal preference for me. If you wish to install HTC Sync, then by all means do so.
You will also need to download the ADB/Fastboot files for Windows which can be found here:
ADB/Fastboot files for Windows: https://dl.dropboxusercontent.com/u/1360819/adb-windows.zip
01. Determine if your system is 32-bit or 64-bit and follow the installation instructions for the appropriate software/drivers.
(If drivers have already been installed, then skip this installation step and start with the next).
02. Extract the contents of adb-windows.zip to your "Android" folder.
03. Open a command prompt in, or use a command prompt to browse to the "Android" folder you previously created.
04. On your HTC One (M8) go to Settings > Power, and then uncheck the "Fast Boot" option.
05. Once step 4 is completed, switch your device OFF.
06. Now that the device is powered down, Press the Volume Down and the Power buttons simultaneously to boot the HTC One (M8) into "HBOOT" mode.
07. Using the Volume buttons, navigate to the "Fastboot" option and select it using the Power button.
08. Connect your HTC One (M8) to your PC.
09. On the command prompt you previously opened in step 2, type in the following command "fastboot devices" (do not include the quotation marks).
**At this point, if all steps have been followed properly, you should receive a message in the command window similar to the following:
C:\Users\XXX\Desktop\Android>fastboot devices 011aa0a1a01aaaa1 fastboot
10. Now we will need to go to the HTC Developer website to get an "Identifier Token" before the bootloader can be unlocked. The URL to the HTC Developer website is www.htcdev.com. If you do not already have an account, you will need to register and sign in before you're able to proceed.
11. Once your account has been created and you are logged in, click on the "Development Center" link at the top of the screen.
12. Under the "Unlock Bootloader" option in the center of the page, click on "Get Started".
13. Next, under "Supported Devices" click on "Select your Device" and find the HTC One (M8) and then select "Begin Unlock Bootloader". (This process works for several other HTC devices as well).
14. Accept all warnings and agreements and keep proceeding forward by clicking the "Next" button. When you reach step 8 on the site, enter the following command in the command prompt:
"fastboot oem get_identifier_token" (without the quotation marks).
15. Copy the message seen in the command prompt to notepad or your clipboard.
16. ONLY KEEP THE RANDOM SERIES OF ALPHANUMERICS FROM THE OUTPUT YOU JUST COPIED. Remove everything else such as <<<, (bootloader), Info, or any other piece of text. DO NOT EDIT THE IDENTIFIER TOKEN START OR END LINE!!!
Example:
<<<< Identifier Token Start >>>>
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A
<<<<< Identifier Token End >>>>>
17. Paste the edited output inside the "My Device Identifier Token" box on the HTC Developer website and press "Submit". Once you have submitted the identifier token, you will receive your unlock code binary file via email.
18. Upon receiving the "unlock_code.bin" file from HTC (this file is specific to your phone), transfer the file to your "Android" folder that was previously created at the start of this document.
19. With your command prompt still open, enter the following command:
"fastboot flash unlocktoken Unlock_code.bin" (without the quotation marks).
20. After entering this command, a message should appear on your HTC One (M8) screen asking if you really want to unlock the bootloader. Use the Volume key to highlight the YES option and press the Power button to select it.
21. At this point your phone's bootloader will be unlocked and it will restart automatically. The first boot could potentially take some time. If this happens, it is normal. Be patient and wait for the reboot.
22. After your device reboots, any previous settings that you may have saved will be lost with the unlocking of the bootloader. Be prepared for this, as you will need to redo them all. If it is your intention to unlock your bootloader, I highly suggest doing it on a fresh ROM install, so you only have to deal with it once. This means that "fastboot" will be re-enabled in the power settings. If you wish to continue to rooting your device, you will need to go to Settings > Power and un-check the "fastboot" option before proceeding.
- ROOTING YOUR DEVICE
The first thing you will need to do to root your device is to download the following files
TWRP Recovery for the AT&T (M8): http://androidfiles.org/getdownload.php?file=M8/Recoveries/openrecovery-twrp-2.7.0.4-m8_ul_ca.img
SuperSU: download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
1. Once downloaded it is advised to rename the TWRP Recovery file to either "twrp.img" or "m8recovery.img". (I renamed mine to m8recovery).
2. Once renamed, copy TWRP image file into your previously created "Android" folder.
3. Open a command prompt and browse to the same "Android" folder where you placed the adb/fastboot and TWRP Recovery files.
4. Make sure your HTC One (M8) is powered off. Boot the phone into fastboot mode by pressing the Volume down and Power buttons at the same time. Once booted, select "fastboot" by pressing the Power button.
5. Connect the HTC One (M8) to your PC.
6. Enter "fastboot devices" (without the quotation marks) in the command prompt to verify that the device has been detected by your PC. If the device is connected you should receive a message similar to the following:
C:\Users\XXX\Desktop\Android>fastbootdevices
010AA1A0A10AAAA1 fastboot
7. Once verified, type "fastboot flash recovery m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
8. After TWRP Recovery has been successfully flashed, the device needs to be restarted manually. To do so, enter the command "fastboot reboot" (without the quotation marks).
9. Upon reboot, transfer the SuperSU zip file to the root directory of your HTC One (M8) via your PC.
10. Turn off your HTC One (M8) and reboot into Bootloader mode by holding the Volume Down and the Power button at the same time.
11. Navigate to the "Recovery" option and select it by pressing the power button. (After following this step, TWRP will load on the device rather than the stock HTC Recovery).
12. Now that TWRP Recovery has loaded, tap the "Install" button and select the UPDATE-SuperSU-v1.94.zip file you previously downloaded.
13. One the SuperSU zip file has been flashed, select the "Reboot System" option to reboot your device.
14. After the device restarts, you have successfully rooted your HTC One (M8). From here, you are now free to install custom Kernels, ROMs, and other mods as you see fit.
I hope this helps everyone out. I am not a developer, nor do I pretend to be. Please give thanks to the people that made all rooting and modding our phones possible
Special thanks to gdnewsevry1 for recognizing a missed step and command.
Very nicely written and well put together. Thank you for taking the time to share this.
Scott
Sent from my HTC One_M8 using XDA Free mobile app
This guide is very well made!
I did figure out that you can root the phone without unlocking the boot loader (with Towelroot modstrings), SOff that way, then just follow your instructions to get TWRP on. You might want to add that in to, for people who don't want to use HTCDev.
suggestion
Thanks for your guide. I just used it and it helped a ton. I would suggest the change and addition below based on my experience.
liquidaluminum said:
TWRP Recovery for the AT&T (M8)
[...]
7. Once verified, type "fastboot flash m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
Click to expand...
Click to collapse
7. Once verified, type "fastboot flash recovery m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
liquidaluminum said:
9. Upon reboot, transfer the SuperSU zip file to the root directory of your HTC One (M8) via your PC.
10. Turn off your HTC One (M8) and reboot into Bootloader mode by holding the Volume Down and the Power button at the same time.
Click to expand...
Click to collapse
Insert: 9a. Turn off fastboot in settings.
gdnewsevry1 said:
Thanks for your guide. I just used it and it helped a ton. I would suggest the change and addition below based on my experience.
7. Once verified, type "fastboot flash recovery m8recovery.img" (or whatever you renamed your .img file to and without the quotation marks) in the command prompt and wait for fastboot to flash the TWRP Recovery on your HTC One (M8).
Insert: 9a. Turn off fastboot in settings.
Click to expand...
Click to collapse
Good observation. Thank you. I added a line item numbered 22 under the unlocking portion in substitution of 9a. I did it this way, because all settings are reset unlocking the bootloader. For those that are going to proceed to the rooting instructions, I thought it might be smart to go on and take care of disabling the fastboot options right off the bat, so it's no longer a concern.
You were 100% correct about adding the recovery line. I must have missed it while typing this up. Good looking out!
This is almost certainly the best guide I have seen on XDA to unlock/root a device.
I've added it to my Index thread under "Unlock Bootloader, ROOT, S-Off": http://forum.xda-developers.com/showthread.php?p=52653939
Also, one suggestion is to add an alternate section/branch to flash straight to a custom ROM (rather than stay stock and root).
redpoint73 said:
This is almost certainly the best guide I have seen on XDA to unlock/root a device.
I've added it to my Index thread under "Unlock Bootloader, ROOT, S-Off": http://forum.xda-developers.com/showthread.php?p=52653939
Also, one suggestion is to add an alternate section/branch to flash straight to a custom ROM (rather than stay stock and root).
Click to expand...
Click to collapse
I'm definitely thinking about doing that very thing. The only thing that prevented me originally is because of the way I have to use my phone. I've never owned an HTC device before, so I'm not sure if the same issue would exist, but in regards to ROM swapping, when I was running Samsung devices, I found a proprietary problem with the devices themselves that prevented me from running custom ROMs.
I have an Appradio 2 in my car that relies on the MHL output to mirror my device to my dash. When using custom ROMs of any kind (that I tried), I MHL never worked. I addressed the issue with a couple of developers, I was told that because MHL isn't used by many people, support for it isn't focused on. Since that has seemed to hold true for any of the ROMs that I've tried, I've always been limited to rooted stock ROMs. Hence my not including the suggested addition.
I see, it makes sense to write a guide for only what you know about.
I wouldn't necessarily avoid custom ROMs just for the MHL issue. There are a good number of great custom ROMs that are built on the "stock" Sense base, but with varying degrees of optimizations and cool customization options. Its just a gut feel, but with many of these ROMs I would think the MHL function would work fine. In any case, just make a nandroid backup of your current setup (which I highly recommend when flashing just about anything) and if you don't like the current ROM, its easy to revert.
Missing file
Nice writeup, thanks.
FYI, the M8 TWRP link is dead.
I'll see if I can find another. If not, I'll host it somewhere.
About to do this when I get home...
just wanted to know if anything has changed since the last time this was updated. Appreciate the time put into this guide!
Thank you so much. Directions and attatchments worked like a charm. I found another image to use as a recovery since your link was dead. :good:
Great write-up. I'm going to run through this with my new M8. Just one question - can Philz recovery be used with the HTC?
CanuckinPA said:
Just one question - can Philz recovery be used with the HTC?
Click to expand...
Click to collapse
Yes.
If you ever have time..perhaps you should write up a detailed thread about RUUs. There are a few good ones, but most of them written are from guys either stuck on HTC devices or have used android for years. It might knock out the traffic from unnecessary comments on Dev threads. Perhaps letting others know that you can flash RUUs without a computer simply by renaming to 0P6BIMG. AFAIK you can not change CID without access to a computer. I've tried finding out how I can, but I haven't found out anything. I wanted to do a straight GPE conversion considering I never use SENSE based Roms. A few weeks ago my computer crashed, and I figured that idea was out the window til wonder_never_cease told me to rename the file to 0P6BIMG, but to receive OTA updates I'd have to change the CID from SUPERcid to the google gpe CID
---------- Post added at 05:21 AM ---------- Previous post was at 05:20 AM ----------
Isn't philz recovery discontinued ?
hey, thanks for the detailed guide!
do your steps include s-off?
moreover, what is s-off (I am very new to m8) and is it necessary after rooting? what does it provide?
question #2, will I be able to get OTA updates (if I replace TWRP with stock recovery) ?
thanks in advance!
ksoze11 said:
do your steps include s-off?
moreover, what is s-off (I am very new to m8) and is it necessary after rooting? what does it provide?
question #2, will I be able to get OTA updates (if I replace TWRP with stock recovery) ?
Click to expand...
Click to collapse
1) Guide doesn't include s-off. Look for threads/guides on firewater or (more likely) sunshine s-off methods.
S-off is a HTC-specific security flag that means "all security off". S-off isn't required for most root functions, flashing ROMs, etc. Its only needed to flash some protected partitions (hboot, radio), SIM unlock, and a few other things.
S-off also means that things like device check and version check are bypassed. This can sometimes give you more recovery options (for instance "downgrade" by RUU which is not possible with S-on). But it also makes it possible for your to flash mods meant for other devices and possibly brick the phone. So care needs to be taken when s-off, and it shouldn't be taken lightly.
2) You need to be on the stock ROM (with no system files modified) and stock recovery to receive and install OTA. If you have that, it will OTA fine. But you will need to root again afterwards.
Help -- Phone Keeps Rebooting
I went through the entire procedure to unlock and root and all was fine for a week or so until earlier this week.
I'm not sure what I did prior to the problem, but suddenly the phone started rebooting every minute or so. I shut the phone down for a couple of hours, but when I restarted it the rebooting continued.
I booted into Philz recovery and did a restore to stock, reinstalled all of my apps and all was well until this morning. I have Link2SD and after installing Handcent I opened the Link2SD app. Then the reboot returned.
Is there a fix for this issue, or do I have to go back to stock again?
BTW - I haven't flashed a custom ROM yet, still running the stock ATT HTC ROM
CanuckinPA said:
I went through the entire procedure to unlock and root and all was fine for a week or so until earlier this week.
I'm not sure what I did prior to the problem, but suddenly the phone started rebooting every minute or so. I shut the phone down for a couple of hours, but when I restarted it the rebooting continued.
I booted into Philz recovery and did a restore to stock, reinstalled all of my apps and all was well until this morning. I have Link2SD and after installing Handcent I opened the Link2SD app. Then the reboot returned.
Is there a fix for this issue, or do I have to go back to stock again?
BTW - I haven't flashed a custom ROM yet, still running the stock ATT HTC ROM
Click to expand...
Click to collapse
If the phone was working fine for a week, then it must be due to some more recent change made to the phone or app your installed. Did you try to uninstall Link2SD?
Hi
help me how to install .bin file
Standin.Weed said:
Hi
help me how to install .bin file
Click to expand...
Click to collapse
If you are asking this question (with no additional detail) you are in no position to be messing with this device. Mostly likely end up bricking it. There is a ton of information in these forums. Spend some time reading.
Davey126 said:
If you are asking this question (with no additional detail) you are in no position to be messing with this device. Mostly likely end up bricking it. There is a ton of information in these forums. Spend some time reading.
Click to expand...
Click to collapse
I have the kindle fire hdx 7 13.3.2.4 and I also have file:
mod-update-kindle-thor-13.3.2.8_user_713328020.bin
I do not know how to manually install this file
these words are translated by google because I have bad english
I don' know what you're up to, on 3.2.4 I'd suggest to downgrade to 3.1.0, install TWRP, update the bootloader to 3.2.3.2, unlock the bootloader. and use ROM of your choice.
3.2.8 would remove this option - probably forever. You can NOT downgrade below 3.2.8 once you're on 3.2.8 or higher due to rollback protection by Amazon (attempt would brick the device!).
Cl4ncy said:
I don' know what you're up to, on 3.2.4 I'd suggest to downgrade to 3.1.0, install TWRP, update the bootloader to 3.2.3.2, unlock the bootloader. and use ROM of your choice.
3.2.8 would remove this option - probably forever. You can NOT downgrade below 3.2.8 once you're on 3.2.8 or higher due to rollback protection by Amazon (attempt would brick the device!).
Click to expand...
Click to collapse
teach me how to install 13.3.1.0 install TWRP, update the bootloader to 3.2.3.2
Ok, listen - this is NOT for the faint of heart, 'cause it comes with a certain likelihood to brick the HDX, so if in doubt leave it be!
I'll give you all the info to read, you must understand what you have to do. If in doubt, ask before you brick your HDX!
First of all the easiest way (and this won't get any easier) is to root with HDX Toolkit, and install Safestrap v3.75 - if you haven't done it yet. Be sure to know what you're doing with rooting and Safestrap! Note that factory reset means the standard wipe only! Do NOT go into advanced wipe! Do NOT wipe System!
You can use the downgrade images provided by @ggow then, check page 2 her (page 1 is about 3.2.5/3.2.6 users who can NOT use those images).
After the downgrade to 3.1.0 you won't have Safestrap anymore, so you can Flash TWRP (either via adb or Flashify, if you use the latter be sure to backup the stock recovery, and to flash the image to the recovery partition!). Update the bootloader to 3.2.3.2 via TWRP then (TWRP can be accessed by pressing and holding both Power and Vol Up buttons during power on, release both when the grey Kindle Fire logo appears on screen).
Unlock the bootloader with the one click solution, if it fails, we'll have to do it the hard way, i.e. manually.
After unlocking you can use the available ROMs, i.e. CM11, CM12, SlimLP, Nexus or the (still in beta stage) new CM13.
Happy reading.
Be sure to Keep WLAN off/flight mode active so you won't get updated by Amazon!
Cl4ncy said:
Ok, listen - this is NOT for the faint of heart, 'cause it comes with a certain likelyhood to brick the HDX, so if in doubt leave it be!
I'll give you all the info to read, you must understand what you have to do. If in doubt, ask before you brick your HDX!
First of all the easiest way (and this won't get any easier) is to root with HDX Toolkit, and install Safestrap v3.75 - if you haven't done it yet. Be sure to know what you're doing with rooting and Safestrap! Note that factory reset means the standard wipe only! Do NOT go into advanced wipe! Do NOT wipe System!
You can use the downgrade Images provided by @ggow then, check page 2 her (page 1 is about 3.2.5/3.2.6 users who can NOT use those images).
After the downgrade to 3.1.0 you won't have Safestrap anymore, so you can Flash TWRP (either via adb or Flashify, if you use the latter be sure to backup the stock recovery, and to flash the image to the recovery partition!). Update the bootloader to 3.2.3.2 via TWRP then (TWRP can be accessed by pressing and holding both Power and Vol Up buttons during power on, release both when the grey Kindle Fire logo appears on screen).
Unlock the bootloader with the one click solution, if it fails, we'll have to do it the hard way, i.e. manually.
After unlocking you can use the available ROMs, i.e. CM11, CM12, SlimLP, Nexus or the (still in beta stage) new CM13.
Happy reading.
Be sure to Keep WLAN off/flight mode active so you won't get updated by Amazon!
Click to expand...
Click to collapse
I do not know to do this step:
cuberHDX from here: http://forum.xda-developers.com/showpost.php?p=58864282&postcount=46
then open another DOS box, change dir to your Python Directory with the .py script (enter cd\python27 or whatever the path of your Python directory is), then
python.exe cuberHDX.py 0xmmssssssss
with mm being the last two digits of your ID, and the ssssssss being your serial, the script should create the .unlock file then.
So assuming the numbers you mentioned are correct the python command would be
python.exe cuberHDX.py 0x45f0bf7e1d
Copy/move the .unlock file to your ADB directory then, open another DOS box for the adb reboot-bootloader command, and yet another DOS box for the fastboot commands (change dir cd\adb both times before you enter the adb & fastboot commands):
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot
this is not have to be?
That's the manual unlock procedure. Try the one-click-solution mentioned above first, should be a lot easier.
Cl4ncy said:
That's the manual unlock procedure. Try the one-click-solution mentioned above first, should be a lot easier.
Click to expand...
Click to collapse
Hi cl4ncy!
I can not unlock bootloader one lick and manual. See my picture:
http://www.upsieutoc.com/images/2016/01/21/12420d.png
http://www.upsieutoc.com/images/2016/01/21/29b3da.png
it just stops here although I did all the steps
Standin.Weed said:
Hi cl4ncy!
I can not unlock bootloader one lick and manual. See my picture:
http://www.upsieutoc.com/images/2016/01/21/12420d.png
http://www.upsieutoc.com/images/2016/01/21/29b3da.png
it just stops here although I did all the steps
Click to expand...
Click to collapse
Using the manual unlock procedure, try these drivers, if possible with Win7 (could be a pain in the ass to install them in Win8/10 x64). Should fix the "Waiting for device" issue.
Cl4ncy said:
Using the manual unlock procedure, try these drivers, if possible with Win7 (could be a pain in the ass to install them in Win8/10 x64). Should fix the "Waiting for device" issue.
Click to expand...
Click to collapse
tks you so much.
I did all :laugh:
Standin.Weed said:
tks you so much.
I did all :laugh:
Click to expand...
Click to collapse
You're welcome - enjoy your "free" HDX.
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.
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.
A lot less of a guide than a compilation of links and steps I followed a few days ago to get this working. Can confirm everything's going smoothly without hitch. Credit to the respective authors of these threads and tools, and the helpful replies I've got from a few members of this forum. You guys are the real ones.
First, and perhaps most importantly, I can confirm that the N200 T-Mobile MSM tool DOES work on the MetroPCS variant (which I own) and WILL save you from a hard brick if anything goes horribly WRONG. Just boot to EDL by holding both volume up and down and run the MSM tool from Windows, and let it work its magic.
Run the debloater script linked here to gain access to the OEM unlock slider in developer options.
Enable ADB Debugging and `adb reboot bootloader` and follow the steps on the Oneplus site to unlock your bootloader (took me exactly one week for them to email me the unlock key).
I had a lot of trouble getting the posted version of TWRP to mount partitions, wipe, or flash ROMs properly, so:
Follow this guide over on the OP8T forum (thanks to @Ethanvio for pointing this my way) to extract the partition images from the latest N200 OxygenOS OTA and flash them manually in fastbootd (`adb reboot fastboot`). I ran into the `product.img FAILED (remote: 'Not enough space to resize partition')` error, so I also had to do the part in the spoiler. Some things of note are to remember to flash the vendor_boot partition as well (present for the N200 but not OP8T), and you can also include the flag `--disable-verity` when flashing the vbmeta & vbmeta_system images if you'd like it disabled.
For root, download Magisk Manager, patch the boot.img, then flash it via fastboot. You can have Magisk persist after OTA by first installing the update through system updates, then before rebooting, opening Magisk Manager and selecting "Install to Inactive Slot (After OTA)" - reboot via Magisk after this completes.
As I understand it, you can call up T-Mobile request a PIN unlock, so this shouldn't affect your ability to carrier unlock (and the carrier unlock button in the OxygenOS settings suggests this as well), despite this process removing the unlocker app from your phone. Maybe someone can correct me in the comments if I'm way off on this lol.
Posting this mostly for myself to remember the steps, but maybe someone else will find it helpful as well.
No matter what I do, I can't get the debloat script to allow to unlock the bootloader.
I have 3 DE2118 - I've tried it on all of them. I've also flashed them using MSM tool to enure the software is fresh.
Any suggestions on what or how I could be using the debloater script wrong? This is what I'm doing:
1) Flashing phones with MSM tool
2) Developer Tools > OFF automatic updates
3) Run debloater script - it says 'successful" for most of them
4) Restarting phone
bouyakasha said:
No matter what I do, I can't get the debloat script to allow to unlock the bootloader.
I have 3 DE2118 - I've tried it on all of them. I've also flashed them using MSM tool to enure the software is fresh.
Any suggestions on what or how I could be using the debloater script wrong? This is what I'm doing:
1) Flashing phones with MSM tool
2) Developer Tools > OFF automatic updates
3) Run debloater script - it says 'successful" for most of them
4) Restarting phone
Click to expand...
Click to collapse
I found the solution. Maybe this will help somebody else:
1) Flashing phones with MSM tool
2) Developer Tools > OFF automatic updates
3) You will noticed that phone will say (a) "OEM Unlocking - Connect to the internet or contact your carrier" it will NOT say (b) "OEM Unlocking - Allow the bootloader to be unlocked" and greyed out. If it says (a) as I think it always will after the MSM tool, you need to insert a TMO SIM, let it connect to the network, and restart.
3) Run debloater script - it says 'successful" for most of them
4) Restarting phone
5) Now it will say "OEM Unlocking - Allow the bootloader to be unlocked" and not be greyed out, thanks to the debloater.
Something that is not well known, is that the OEM unlocking toggle is grayed out with that "OEM Unlocking - Connect to the internet or contact your carrier" message until you have allowed google play services to run with internet access. I suspect it submits and checks hardware ID's against a blacklist before Google sends a response whether to allow the device to allow OEM unlocking. For the unlocked version, this was all that was required. For the T-mobile / Metro versions, you have the extra SIM unlock software restriction steps afterwards.
oCAPTCHA said:
Something that is not well known, is that the OEM unlocking toggle is greyed out until you have allowed google play services to run with internet access. I suspect it submits and check the hardware ID's against a blacklist before they send a response to allow the device to be OEM unlocked.
Click to expand...
Click to collapse
You are correct. That is not well known, that one needs internet access before it can be ungreyed. Thanks for sharing.
Thanks @darkghost568 and @bouyakasha for your info in this thread!
After 5 months of waiting (1 month on Metro to start the process), I finally SIM unlocked both of my parents Metro N200s today. From a software standpoint, it sounds like I can "convert" these Metro phones to the OEM version (direct from OnePlus) and get OTAs, right? Is this the same as a bootloader unlock? I've done SIM unlocks and bootloader unlocks before, but the term "OEM unlock" is new to me.
Just want to confirm before I start looking into this.
Thanks!
yellowsnow4free said:
Thanks @darkghost568 and @bouyakasha for your info in this thread!
After 5 months of waiting (1 month on Metro to start the process), I finally SIM unlocked both of my parents Metro N200s today. From a software standpoint, it sounds like I can "convert" these Metro phones to the OEM version (direct from OnePlus) and get OTAs, right? Is this the same as a bootloader unlock? I've done SIM unlocks and bootloader unlocks before, but the term "OEM unlock" is new to me.
Just want to confirm before I start looking into this.
Thanks!
Click to expand...
Click to collapse
Not quite. The legit OnePlus OEM can get OTA updates, but the converted models tend to fail some checks during the on-device upgrade process, especially when it comes to incremental OTA update packages (@ / AndyYan has talked about this a bit across other threads before). However, you can still install the full update packages manually via the steps in the OP, and for incremental updates, following my guide here. It's worked fine for me until the most recent 11.0.7.0 incremental OTA since that required recent versions of packages that contained breaking dependencies/version mismatches for the update_payload_extractor tool, which hasn't been updated, so ymmv
darkghost568 said:
Not quite. The legit OnePlus OEM can get OTA updates, but the converted models tend to fail some checks during the on-device upgrade process, especially when it comes to incremental OTA update packages (@ / AndyYan has talked about this a bit across other threads before). However, you can still install the full update packages manually via the steps in the OP, and for incremental updates, following my guide here. It's worked fine for me until the most recent 11.0.7.0 incremental OTA since that required recent versions of packages that contained breaking dependencies/version mismatches for the update_payload_extractor tool, which hasn't been updated, so ymmv
Click to expand...
Click to collapse
Thanks for the prompt reply!
I'd really like OEM OTA updates, but since the phones are working OK for now perhaps I'll leave the phones as-is.