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.
Related
Huami started to lock the bootloader of the Amazfit watch in their official release 1.2.13 and 1.3.2b onwards.
If you want to keep the possibilty to flash custom software on your watch, DO NOT UPGRADE TO THESE VERSIONS. You will not be able to flash any other firmware afterwards.
PACEfied firmware is safe, and does NOT lock your bootloader.
UPDATE 14.07.17:
We have heard several times now via inofficial sources that Huami is working on an official bootloader unlocking service. So far, we, however, have no official information here.
On the other hand, Olivier (french developer on xda) has spent a significant amount of time to understand the unlocking process and we have succeeded to successfully unlock two watches. We are currently in the process of setting up a (free) unlocking web service, allowing individual xda users to unlock their watches for private usage (and accepting loss of warranty from Huami).
In case, Huami may ever come out with their service, we will stop our service, as we do not want to compete with Huami here, just filling the gap if Huami doesn't move forward with their unlocking service.
Please give us some time (we expect 2-3 weeks) to setup the unlock service.
UPDATE 7.08.17:
The unlock service is live now. Head over to https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unlock-bootloader-warning-void-t3654011, if you want your bootloader unlocked!
Fastboot oem unlock
And the command to unlock the bootloader does not work?*
Code:
Fastboot oem unlock
scrubber said:
And the command to unlock the bootloader does not work?*
Code:
Fastboot oem unlock
Click to expand...
Click to collapse
No, neither does
Code:
fastboot flashing unlock
I wouldn't expect Huami to put efforts into locking the bootloader and at the same time making it that easy to unlock it again. This is no coincidence. They saw our work and reacted. That's what happened. Very sad
Neuer_User said:
No, neither does
Code:
fastboot flashing unlock
I wouldn't expect Huami to put efforts into locking the bootloader and at the same time making it that easy to unlock it again. This is no coincidence. They saw our work and reacted. That's what happened. Very sad
Click to expand...
Click to collapse
Perhaps we need to find the Fastboot oem command, they can be different for different devices
https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
scrubber said:
Perhaps we need to find the Fastboot oem command, they can be different for different devices
https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
Click to expand...
Click to collapse
Well, the strings dump shows that the "oem unlock" command seems to exist, but it indicates that an unlock code is necessary, probably based on the serial number of the watch:
strings dump extract:
Code:
oem:
unlock
serial no length is null
magic_serialno:%s
, len:%d
%02x
uncrypted_str_serialno:%s
Unlocked code sucess
Unlocked code is error
Unsupport oem cmd
FAILED: The command is not recongized
So, we have three possibilities:
We find the method on how the code is calculated based on the serial of the watch
We find the location, where u-boot stores the variable, if the device is locked or not (EDIT: I would expect that in the Misc partition.)
We just reflash the old bootloader (easiest, but only temporary until next OTA update)
Neuer_User said:
So, we have three possibilities:
We find the location, where u-boot stores the variable, if the device is locked or not (EDIT: I would expect that in the Misc partition.)
Click to expand...
Click to collapse
Drop me stock ota 1.2.11c and 1.2.13
scrubber said:
Drop me stock ota 1.2.11c and 1.2.13
Click to expand...
Click to collapse
You will only need the bootloaders (rest of the OTA is just modified apks). I will send them both (old and new one) to you via PM. It would be necessary to disassemble and understand the new bootloader (the old one does not have any OEM commands and also did not read the serial no at all, instead displayed always a dummy serial).
The serial is stored on the misc partition, so the bootloader now needs to read this partition. That's why I believe they probably stored the lock/unlock flag also there. We just need to know which byte.
Of course, if there were someone with a functioning unlock code, he could dump his misc partition before and after unlocking. That would make it pretty clear
so I now have no way to flash a stable version starting from 1.2.13?
It's safe to update 1.3.2b ? English version
zbuh said:
It's safe to update 1.3.2b ? English version
Click to expand...
Click to collapse
No, also locks bootloader. But there is a good chance that we can unlock or reflash the bootloader, if someone wants to switch firmware later.
I also have this problem. I accidentally updated my Amazfit to the latest version official rom. Now I wanted to upgrade to PACEfied, but the bootloader is locked.
Do you have any ideas how to unlock it?
Hi neur_user will I be losing the interval timer and countdown timer app that I installed in pace 1.3.1m rom if update it to 1.3.2b since you said it is bootloader locked? And can you still install developers app in 1.3.2b?
powerforward said:
Hi neur_user will I be losing the interval timer and countdown timer app that I installed in pace 1.3.1m rom if update it to 1.3.2b since you said it is bootloader locked? And can you still install developers app in 1.3.2b?
Click to expand...
Click to collapse
Instalation of additional apps like those timer apps should still work.
barciol said:
I also have this problem. I accidentally updated my Amazfit to the latest version official rom. Now I wanted to upgrade to PACEfied, but the bootloader is locked.
Do you have any ideas how to unlock it?
Click to expand...
Click to collapse
I have an idea how we can unlock the bootloader. In the weekend I will see if I can post a tutorial.
Well, I don't know what I could gain by flashing PACEified FW on my watch... all I've really been looking for is working notifications from my phone to the watch. I'm coming from wearing a Samsung Gear Live that's now worn-out, and it integrated into my life by bringing notifications to my wrist. The Amazfit was perfect for fitness, runtime, and notifications -- but notifications have never worked despite all my hacking and flashing (originally came with Chinese ROM). My saga so far is detailed here: https://www.reddit.com/r/amazfit/comments/61w4ga/most_notifications_not_coming_through_facebook
I flashed the English ROM to it tonight, and proceeded to OTA it (because newer is better, right?). The update failed as I still had the Chinese recovery on it. When it failed, I decided to try intercepting the update bundle before it rebooted. I succeeded, by kicking it into Fastboot mode using the power-button trick, then I pulled the 1.3.2b update.zip file through the "mod recovery". That file is here: https://mega.nz/#!nIBDhLrR!7nQlWsn-TF4bsMNBSaTOfimY-vo-Z2R3dSavrDp1wsA
I fixed my recovery with help of another thread, and OTA'd again to success - the darn thing took a good solid 10 minutes to run the ~33MB update! The progress bar hung the longest (~2 mins each) near the "w", "c", and at the end of "watch" in the message about not powering off the watch. Rather surprising, and wasn't sure if it hung due to my mods or what it was doing...
Hopefully this helps someone interested in looking into how the bootloader gets locked (IDK if Amazfit expected someone to intercept this, being as it's near impossible to intercept except with a MitM on WiFi), perhaps in exchange for some help with these notifications?
Neuer_User said:
I have an idea how we can unlock the bootloader. In the weekend I will see if I can post a tutorial.
Click to expand...
Click to collapse
I'm stuck in 1.2.13 dev, if u want i can test the unlock
Cracklydisc said:
I'm stuck in 1.2.13 dev, if u want i can test the unlock
Click to expand...
Click to collapse
OK, will prepare it today and send it to you.
Neuer_User said:
OK, will prepare it today and send it to you.
Click to expand...
Click to collapse
I also want test the unlock. Please contact with me
barciol said:
I also want test the unlock. Please contact with me
Click to expand...
Click to collapse
Just to clarify: Technically, it is not "unlocking" the bootloader. It just reflashes the old one (which did not have the locking function). That implies that the "unlocked" bootloader will only stay "unlocked" until you install the next official OTA update (which again flashes the locked bootloader). If you move to PACEfied, then that is ok, as PACEfied certainly does not lock your bootloader.
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
1: Preparing to Unlock Bootloader
Moto does a fine job of breaking down how to unlock the bootloader, but they do not give you much information on using the adb and fastboot programs that are part of the "Android Software Developer Kit(SDK) Platform Tools" which contain over 700+ files. For the procedures listed in this guide, we only need 2 files, adb and fastboot. XDA Moderator @hackslash has created a tool to simplify using adb and fastboot that doesn't include the other 700+ files you don't need.
1A. ADB and Fastboot Installer for Windows - (Download) - When prompted to install a driver type the number 0 and hit enter. This will install the latest version of adb and fastboot where it is system-wide. This eliminates the need for adb.exe or fastboot.exe to be in the same folder as the files you will be working with. NOTE: Windows will flag this as a virus! The installer is open source and made by a Moderator here on XDA. It is a False Positive. You can view a VirusTotal report (https://www.virustotal.com/en/file/25dc5dca2494d1b1d93832b37ba9852b4f076bba86cf5029b4c944a28a1a01a1/analysis/]HERE[/url]). 26 out of 67 virus scanners report it as a virus. If your Anti-Virus is one of the ones that flag it as a virus, I would suggest you explore other Anti-Virus software, but that’s not what this guide is about.
1B. As per the instructions on Moto’s site, you need to download and install the latest official drivers from Moto. (Download)
1C. Head over to the Moto website and follow the instructions to unlock your bootloader. (Moto Website)
After you are done on the Moto website your bootloader will be unlocked! This is necessary to be able to modify system files for root, roms, and other various tweaks!
Hi, the official drivers link not working for me.
https://motorola-global-en-roe.cust...prod_answer_detail/a_id/99344/p/30,6720,10383 <-- Installs the whole Motorola Device Manager along with the usb drivers, which can be also used to update firmware. I don't know if this is good or bad for rooted phones.
https://motorolausbdriver.com/download/motorola-moto-g6-plus <-- just the driver for windows
Thanks for this article and the work that has gone into it.
Just a quick editing note. The 1B line includes a typo in the href attribute, the value of which is:
http://https//motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Click to expand...
Click to collapse
Thanks.
Will the bootloader unlock trigger a factory reset?
Hobbygamer27 said:
Will the bootloader unlock trigger a factory reset?
Click to expand...
Click to collapse
Yes
Sent from my SM-A505U using Tapatalk
I can get into the bootloader on my phone, with `adb reboot bootloader` or pressing the power and volume down key. The problem is that once I'm in the bootloader in fastboot on my pc it doesn't recognise my phone, usb debugging + oem unlock is on in dev settings. I got in once, but after many tries I wasn't able to have a connection anymore. On my phone it says that the usb is connected, so that isn't the problem. I haven't tried it on a 2.0 usb slot yet.
Xplorer4x4 said:
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
1: Preparing to Unlock Bootloader
Moto does a fine job of breaking down how to unlock the bootloader, but they do not give you much information on using the adb and fastboot programs that are part of the "Android Software Developer Kit(SDK) Platform Tools" which contain over 700+ files. For the procedures listed in this guide, we only need 2 files, adb and fastboot. XDA Moderator @hackslash has created a tool to simplify using adb and fastboot that doesn't include the other 700+ files you don't need.
1A. ADB and Fastboot Installer for Windows - (Download) - When prompted to install a driver type the number 0 and hit enter. This will install the latest version of adb and fastboot where it is system-wide. This eliminates the need for adb.exe or fastboot.exe to be in the same folder as the files you will be working with. NOTE: Windows will flag this as a virus! The installer is open source and made by a Moderator here on XDA. It is a False Positive. You can view a VirusTotal report (https://www.virustotal.com/en/file/25dc5dca2494d1b1d93832b37ba9852b4f076bba86cf5029b4c944a28a1a01a1/analysis/]HERE[/url]). 26 out of 67 virus scanners report it as a virus. If your Anti-Virus is one of the ones that flag it as a virus, I would suggest you explore other Anti-Virus software, but that’s not what this guide is about.
1B. As per the instructions on Moto’s site, you need to download and install the latest official drivers from Moto. (Download)
1C. Head over to the Moto website and follow the instructions to unlock your bootloader. (Moto Website)
After you are done on the Moto website your bootloader will be unlocked! This is necessary to be able to modify system files for root, roms, and other various tweaks!
Click to expand...
Click to collapse
I need to lock my bootloader again, how do I do that?
andreym_costa said:
I need to lock my bootloader again, how do I do that?
Click to expand...
Click to collapse
Same as unlocking but in reverse order.
Unlocking:
- activate OEM unlocking
- use command 'fastboot oem unlock'
=> First boot with an unlocked bootloader loads your unmodified stock ROM until you flash another ROM.
Here you start locking the bootloader with the same conditions. This means you have to flash the latest stock ROM before doing anything else.
Then (after you successfully boot your unmodified stock ROM once!!) you can boot into fastboot mode and execute 'fastboot oem lock'.
NEVER EVER deactivate the OEM unlock option before everything is ok!! The meaning of ok is, that your locked device will boot into system AND you have a functional Wifi and mobile connection. After this step (and only after that!) you can deactivate the OEM unlocking option.
This is the OnePlus 7T Pro McLaren's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
mauronofrio said:
This is the OnePlus 7T Pro McLaren's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Click to expand...
Click to collapse
This states that you can flash TWRP with this tool. Is that actually accurate? We haven't had a working custom recovery that can be flashed onto the device thus far. Sorry if it sounds overly skeptical, I'm just going based off the information we've had so far.
champ784 said:
This states that you can flash TWRP with this tool. Is that actually accurate? We haven't had a working custom recovery that can be flashed onto the device thus far. Sorry if it sounds overly skeptical, I'm just going based off the information we've had so far.
Click to expand...
Click to collapse
The TWRP in the tool is not fully functional, but you can use it to root your device.
Root Guide:
So you should go in "recovery flasher and rooter" option, there you have to select the only TWRP available, check if "only boot" is checked, check "root after boot", select magisk 20.4 and click on the button at the bottom of the page. The TWRP will be booted and magisk flashed, and then from TWRP you can manually reboot to system and your device will be correctly rooted.
mauronofrio said:
The TWRP in the tool is not fully functional, but you can use it to root your device.
Root Guide:
So you should go in "recovery flasher and rooter" option, there you have to select the only TWRP available, check if "only boot" is checked, check "root after boot", select magisk 20.4 and click on the button at the bottom of the page. The TWRP will be booted and magisk flashed, and then from TWRP you can manually reboot to system and your device will be correctly rooted.
Click to expand...
Click to collapse
Gotcha, thanks for the clarification!
Thanks for the download and thank you so much for creating this tool! I haven't yet rooted my 7T Pro McLaren on T-Mobile yet but this is definitely going to make it a lot easier by the looks of it.
I assume this requires you already have your unlock token?
I installed RR the other day but it is not seeing my SIM card and won't connect to WiFi so I'm looking for a tool that will help me revert back to stock OS for my HD1925 OP7TPro McLaren device. I downloaded OB11-OnePlus7ProOxygen_13.W.29_OTA_029_all_2003130822_1b7c-FASTBOOT.zip and tried to flash using this tool but the installation fails at ODM saying that there is no such partition. Is there any advice you could offer it would be very much appreciated!
I was able to boot into EDL and restore then update the OS so everything is working great now. Thank you so much for your amazing work!
Confirming I was able to root without issue using this method.
Hi, every time I do the install for TWRP and magisk I try to boot the phone afterwards and I get a message that says "no OS installed" is there anything that I need to do after installing TWRP and magisk? Because I can't boot the phone cause installing TWRP apparently deletes the OS completely. The bootloader unlock method works perfectly, it's just the TWRP and magisk that are messing up my phone.
Thanks in advance.
I dont suppose you will be making a Linux version would you? Only have linux on my computers
I think you need to switch a or b partition with fastboot after you are done with flashing magisk. Maybe the function to switch from a to b or b to a works inside twrp but I just read that this is not a fully functional version and I haven't decided if I want to use your tool or just root the traditional way. The command is fastboot --set-active=a
Or fastboot --set-active=b
---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------
Naruyasha said:
Hi, every time I do the install for TWRP and magisk I try to boot the phone afterwards and I get a message that says "no OS installed" is there anything that I need to do after installing TWRP and magisk? Because I can't boot the phone cause installing TWRP apparently deletes the OS completely. The bootloader unlock method works perfectly, it's just the TWRP and magisk that are messing up my phone.
Thanks in advance.
Click to expand...
Click to collapse
I answered you two posts up but didn't reply directly to you so it's just a couple comments into the next page.
am i right that bootloader unlock formats your install? also i saw in may saying twrp wasnt fully functional yet is it now? if it is is there a zip for it?
Did you find out if you have to get an unlock token from tmobile for this to work? Does the bootloader need to be unlocked in order to run twrp.
unlock without root
Hi will this tool allow you to carrier unlock the phone From my understanding you can unlock boot loader and then root and unlock
Is there a way to not keep the root and still carrier unlock the phone it’s a 7t pro maclaren
It’s got a user that is kit very tech savvy and he would like to keep the update os without any extra steps
or is there a step to root unlock then remove the root
will this tool work on oneplus 7t pro mclaren sold in india, it does not have 5g
smehra said:
Hi will this tool allow you to carrier unlock the phone From my understanding you can unlock boot loader and then root and unlock
Is there a way to not keep the root and still carrier unlock the phone it’s a 7t pro maclaren
It’s got a user that is kit very tech savvy and he would like to keep the update os without any extra steps
or is there a step to root unlock then remove the root
Click to expand...
Click to collapse
Carrier unlock cannot be achieved without T-Mobile white listing and carrier unlocking the device. This tool allows you to unlock the bootloader without needing to have a carrier unlock. By unlocking the bootloader you gain the ability to fastboot boot TWRP, although the available ports of TWRP for this device is not yet fully functional.
if your device has an unlocked bootloader then you will not be able to take OTA updates from OnePlus/TMO. So if your friend is not tech savvy and does not want to manually install stock firmware... Then you should not use this tool at all or unlock his bootloader.
Your desire to carry your unlock can only be satisfied by having the device paid off in full and requesting a carrier unlock from T-Mobile. OnePlus can only provide and unlock token for the bootloader, they have nothing to do with the stock T-Mobile firmware nor the ability to carry your unlock. And this tool allows you to bypass the carrier unlock to achieve a bootloader unlock without needing the token from OnePlus.
Hope that clears up any confusion for you :good:
---------- Post added at 10:21 AM ---------- Previous post was at 10:15 AM ----------
smehra said:
Hi will this tool allow you to carrier unlock the phone From my understanding you can unlock boot loader and then root and unlock
Is there a way to not keep the root and still carrier unlock the phone it’s a 7t pro maclaren
It’s got a user that is kit very tech savvy and he would like to keep the update os without any extra steps
or is there a step to root unlock then remove the root
Click to expand...
Click to collapse
You do not need to unlock the bootloader or root the device in order to do a carrier unlock. You just need to satisfy the terms and conditions set by T-Mobile and they will provide you with a carrier unlock.
Although this device is LTE only as the international version, and 5G capable for the T-Mobile version. Carrier unlocking the T-Mobile version and using with a different carrier.... You will still require firmware which is only provided by T-Mobile so it has their branding and bloatware included. Not sure if that would conflict with another carrier. And 5G will only work on T-Mobile's Network.
ElfinJNoty said:
Carrier unlock cannot be achieved without T-Mobile white listing and carrier unlocking the device. This tool allows you to unlock the bootloader without needing to have a carrier unlock. By unlocking the bootloader you gain the ability to fastboot boot TWRP, although the available ports of TWRP for this device is not yet fully functional.
if your device has an unlocked bootloader then you will not be able to take OTA updates from OnePlus/TMO. So if your friend is not tech savvy and does not want to manually install stock firmware... Then you should not use this tool at all or unlock his bootloader.
Your desire to carry your unlock can only be satisfied by having the device paid off in full and requesting a carrier unlock from T-Mobile. OnePlus can only provide and unlock token for the bootloader, they have nothing to do with the stock T-Mobile firmware nor the ability to carry your unlock. And this tool allows you to bypass the carrier unlock to achieve a bootloader unlock without needing the token from OnePlus.
Hope that clears up any confusion for you :good:
---------- Post added at 10:21 AM ---------- Previous post was at 10:15 AM ----------
You do not need to unlock the bootloader or root the device in order to do a carrier unlock. You just need to satisfy the terms and conditions set by T-Mobile and they will provide you with a carrier unlock.
Although this device is LTE only as the international version, and 5G capable for the T-Mobile version. Carrier unlocking the T-Mobile version and using with a different carrier.... You will still require firmware which is only provided by T-Mobile so it has their branding and bloatware included. Not sure if that would conflict with another carrier. And 5G will only work on T-Mobile's Network.
Click to expand...
Click to collapse
Just to expound on this very concise reply, I have had good luck on multiple occasions getting Tmo to carrier unlock the devices ( I have 2 of the HD1915's on my account ) using their Twitter support group. I find that the Tmo Business Support is quicker to unlock than the standard consumer support staff. It makes no difference that you don't have a business account/etc, they will help you regardless. I simply tell them that I'm going out of the country for several months and want to be able to use my shiny new device while I'm away- they will tell you lots of things about temporary unlocks for 30 days, and permanent unlocks, and the requirements to satisfy to be qualified for each, but at the end of the day all you need them to do is grant you a temporary 30-day carrier unlock. When you follow the instructions to go into your settings and unlock the device you'll see two options: the temp unlock and a PERMANENT unlock. It doesn't matter that you've said you want only the temp unlock, once they update their system to allow the unlock just select the PERMANENT UNLOCK anyway and it WILL successfully and PERMANENTLY unlock your device. I've done this several times and can confirm it DOES work. I think the only requirement for a temp unlock is to have two EIP payments made on the device if you've just purchased. You can make those payments at once or however you'd like, but that's really all they are going to REQUIRE from you to provide you with a "TEMP" unlock.....except the "temp" unlock is going to actually allow you to PERMANENTLY unlock the device.....capisce?
Just got a TMobile Oneplus 7T Pro Mclaren edition from offer up. I was somehow able to carrier unlock my using the service unlock tool with the SIM card it came with ??.
I noticed it has a Retail Mode app and Tech Specs app so I'm thinking it used to be a Retail unit but everything else works fine. I was able to add my Gmail account and setup the device just fine.
The only issue I have it is stuck on the October 2019 software version. Could somebody tell me if I can use this stuff on this thread to install the normal software because I think maybe that's why it won't update my phone to the latest software. I just want the phone to be in normal software version with no root or anything special. Just want it stock. Thanks in advance
mexicandroid said:
Just got a TMobile Oneplus 7T Pro Mclaren edition from offer up. I was somehow able to carrier unlock my using the service unlock tool with the SIM card it came with ??.
I noticed it has a Retail Mode app and Tech Specs app so I'm thinking it used to be a Retail unit but everything else works fine. I was able to add my Gmail account and setup the device just fine.
The only issue I have it is stuck on the October 2019 software version. Could somebody tell me if I can use this stuff on this thread to install the normal software because I think maybe that's why it won't update my phone to the latest software. I just want the phone to be in normal software version with no root or anything special. Just want it stock. Thanks in advance
Click to expand...
Click to collapse
If it's been rooted before, you may need to be rooted to have a working fingerprint. Do you still have contact info from the previous owner to see if they have any info about what's happened with the phone?
OK, this process has been hell, but I'm gonna try and consolidate everything I've worked out so far in one place. This all applies only to the T-Mobile variant (ie. it comes preloaded with all the T-Mobile bloatware) of the N200 on the T-Mobile network; and a Windows PC, where a PC is used (though I imagine the Mac/Linux commands are quite similar). This is more to gather the info in one place than to provide step-by-step instructions.
SIM/NETWORK UNLOCK
Before you can unlock the bootloader, the N200 needs to be SIM unlocked. The option to Enable OEM Unlock won't even show up in the developers options until then. A temporary SIM unlock won't work, it needs to be a permanent SIM unlock.
If your N200 is the T-Mobile variant, you can get it SIM unlocked free here (be sure to read the first post thoroughly to be sure you qualify):
[CLOSED][T-Mobile USA] Free SIM Unlocking Service - [OnePlus/Samsung/Google/LG/Moto]
Hello XDA, I am back at it again with the free T-Mobile network unlocks. Yep, you heard that right... 100% FREE. This service will allow you to go into your Settings and perform a network unlock. I've been doing this for over 3 years now with...
forum.xda-developers.com
@mobbdeep had my SIM unlocked within 24 hours of sending him the required info.
You MUST have an active T-Mobile network (not Sprint or Metro) SIM card in the N200 for at least 3 full days before sending your SIM Unlock request in.
---
*edit-
An alternate is to use this debloat script:
Found a chink in the armor... Just enabled OEM unlocking after 11 update...
I haven't got a lot of time to get this out before heading out on a job, so here's the nitty gritty. A few days ago I flashed over "OnePlus_Nord_N10_5G_Metro_by_T-Mobile_OxygenOS_10.5.8" to get a clean start. I then allowed 10.5.14 to install...
forum.xda-developers.com
Which should unlock the OEM Unlock option in the developer options.
This should work with non-T-Mobile variants of the N200 as well.
Thanks to @PopCaps1996 for pointing this option out.
---
*edit2-
Thanks to user @DeadDjembe we now know the specific command from the debloat script which enables OEM Unlocking.
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
Running this ADB command on a stock T-Mobile variant N200 should enable the greyed-out Allow OEM Unlock option in the developers settings, without needing to run the full debloat script.
---
Once your N200 is SIM Unlocked, the Enable OEM Unlock option will show up in the developers options.
USB DRIVERS
You may need to use the Google USB Driver from Android Studio to allow your PC to recognize your phone when it's in fastboot mode.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Android Studio won't install the USB Drivers by default, you'll need to install them through the SDK Manager (Android Studio -> Projects -> More Actions -> SDK Manager -> SDK Tools -> Google USB Driver checkbox -> Apply)
You'll need to manually install the drivers through the device manager while the phone is in fastboot mode and connected to the PC (right-click -> Update Drivers -> Browse Computer -> Let Me Pick -> Have Disk).
The drivers should be located at:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
You'll want the 'Android Bootloader Interface' driver.
UNLOCK CODE/TOKEN
Once you can access your phone in fastboot mode, you can try:
'fastboot oem unlock'
But, you'll just get a message asking for an unlock token. Doesn't hurt to try, just in case, though.
What you need to do now, is type:
'fastboot oem get_unlock_code'
This will display both the phone's serial number, plus a 64 digit unlock code. (you might not be able to select the code to copy it, but a ctrl-a / ctrl-c should work, then just paste it in notepad)
Now, on your phone (still in fastboot mode) hit up/down on the volume buttons, until you see "Show Barcode", then tap the power button to select it.
This will bring up a barcode, as well as listing you devices IMEI number. (there are other ways to get the IMEI, but this is quick, and you're already right there)
Copy the IMEI down.
Now go to:
https://www.oneplus.com/unlock_token
You'll need to create an account.
In that form, you'll need to select the phone's model, and then enter the serial number, 64 digit unlock code (no spaces), the IMEI, and your email, as well as checking a box that you acknowledge that you void the warranty by bootloader unlocking the phone.
If all goes well, It should take about a week from submission for them to send you the unlock token.
------
I've just sent in my info an hour or two ago, and am now waiting for my unlock token.
I'll update this with what you need to do with the token once I've gotten mine and figure it out myself, lol.
------
Exactly 7 days (nearly to the minute) after sending the request in, I received the unlock code. So here's the update:
APPLYING THE UNLOCK CODE
You can use this URL to check the status of your Unlock Coed request:
unlock token - OnePlus (United States)
www.oneplus.com
Once your Status is listed as "Finished", there will be a download button at the lower right corner.
Download the "unlock_code.bin" file to your PC.
Place 'unlock_code.bin' in:
C:\Users\[user name]\AppData\Local\Android\Sdk\platform-tools\
Or where ever you have your fastboot.exe file.
If you don't know where it is, the command:
Code:
fastboot --version
will give your it's location.
Now in command line, navigate to the folder "fastboot.exe" and "unlock_code.bin" are located in. Get your phone connected via USB, and in fastboot mode, and use the following command:
Code:
fastboot flash cust-unlock unlock_code.bin
(Thanks to @lentm for posting this command)
After checking the output, to be sure it worked, use this command:
Code:
fastboot oem unlock
Follow the on-screen instructions on your phone to finish the bootloader unlock.
you do NOT need to carrier unlocked for bootloader unlock use this...... debloat script oneplus through ADB an once finished OEM UNLOCK will be ungrayed. then you can request a unlock token from oneplus then wait 7 days then flash an unlock bootloader.
im still carrier locked
PopCaps1996 said:
you do NOT need to carrier unlocked for bootloader unlock use this...... debloat script oneplus through ADB an once finished OEM UNLOCK will be ungrayed. then you can request a unlock token from oneplus then wait 7 days then flash an unlock bootloader.
im still carrier locked
Click to expand...
Click to collapse
OK, that's neat.
I can't personally test it, as I'm already SIM unlocked; but all comments in the thread seem to indicate it working.
It'd be quite interesting if someone could narrow down exactly which of the removed apps enables the OEM Unlock option (as an uninformed guess: adb shell pm uninstall --user 0 com.qualcomm.qti.remoteSimlockAuth).
I'd need to research what all those different apps do, but at a glance I see at least 2 or 3 on that list I'd want to keep. At any rate, I'd rather wait until after I get TWRP Recovery on my phone (once we get a release for the N200) before debloating it, just to be safe. I'm far more knowledgeable about computers than phones, which gives me just enough knowledge to seriously screw up my phone by doing the wrong thing, lol.
edale1 said:
OK, that's neat.
I can't personally test it, as I already have that unlocked; but all comments in the thread seem to indicate it working.
It'd be quite interesting if someone could narrow down exactly which of the removed apps enables the OEM Unlock option (as an uninformed guess: adb shell pm uninstall --user 0 com.qualcomm.qti.remoteSimlockAuth).
I'd need to research what all those different apps do, but at a glance I see at least 2 or 3 on that list I'd want to keep. At any rate, I'd rather wait until after I get TWRP Recovery on my phone (once we get a release for the N200) before debloating it, just to be safe.
Click to expand...
Click to collapse
i can confirm it works that's the method i used to unlock my bootloader for my n200
Using the debloater worked beautifully to get ability to enable OEM Unlocking. Now it's just the week wait to get the code.
Really wish they'd speed that up; I've had to do this for four devices through them. Major benefit to buying direct from OnePlus, IMO. The last one I did was unlocked moments after getting home...(and is now running crDroid which I really hope comes to the N200)
PhoenixPath said:
Using the debloater worked beautifully to get ability to enable OEM Unlocking. Now it's just the week wait to get the code.
Really wish they'd speed that up; I've had to do this for four devices through them. Major benefit to buying direct from OnePlus, IMO. The last one I did was unlocked moments after getting home...(and is now running crDroid which I really hope comes to the N200)
Click to expand...
Click to collapse
you will not be able to modify anything anyways once you get the bootloader unlocked because oneplus has not released stock rom for the N200 on their website yet. so there for we do not have stock boot.img to be able to patch an root but i heard they will be uploading the rom soon. unless we can figure out how to back up boot img through fastboot but don't think that's possible
Yes, but to my knowledge unlocking the bootloader is the only part of the entire process of installing a custom recovery and rooting that wipes the device. So it's best to get that out of the way ASAP, before the phone's loaded with stuff you don't want to lose.
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
lentm said:
View attachment 5377289
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
Click to expand...
Click to collapse
can you send me the extracted payload.bin pm me please
PopCaps1996 said:
can you send me the extracted payload.bin pm me please
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/2c0d5671fc9a0f7829ab54b08139378afc295f46.zip
lentm said:
https://android.googleapis.com/packages/ota-api/package/2c0d5671fc9a0f7829ab54b08139378afc295f46.zip
Click to expand...
Click to collapse
the payload bin that you extracted? can you zip up the extractred imgs from payload . bin. an send them to me?
lentm said:
View attachment 5377289
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
Click to expand...
Click to collapse
Maybe it's because the ota is just an update, not a full zip?
PopCaps1996 said:
the payload bin that you extracted? can you zip up the extractred imgs from payload . bin. an send them to me?
Click to expand...
Click to collapse
I can get you the boot.img, not every img files. Check the attached.
lentm said:
I can get you the boot.img, not every img files. Check the attached.
Click to expand...
Click to collapse
When trying to patch the boot.img file with Magisk Stable version 23.0 (23000) (21) and Canary version f822ca5b (23001) (21), I get "Unsupported/Unknown image format. Installation failed".
dragonnightx said:
When trying to patch the boot.img file with Magisk Stable version 23.0 (23000) (21) and Canary version f822ca5b (23001) (21), I get "Unsupported/Unknown image format. Installation failed".
Click to expand...
Click to collapse
Yea, that's what I get too.
How long does OnePlus usually take in processing the bootloader unlock request?
TheLoonyRebel said:
How long does OnePlus usually take in processing the bootloader unlock request?
Click to expand...
Click to collapse
7 days
PopCaps1996 said:
you will not be able to modify anything anyways once you get the bootloader unlocked because oneplus has not released stock rom for the N200 on their website yet. so there for we do not have stock boot.img to be able to patch an root but i heard they will be uploading the rom soon. unless we can figure out how to back up boot img through fastboot but don't think that's possible
Click to expand...
Click to collapse
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
jilebi said:
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
Click to expand...
Click to collapse
I tried it and even I set it manually to N200, but no full ROM available
PopCaps1996 said:
you do NOT need to carrier unlocked for bootloader unlock use this...... debloat script oneplus through ADB an once finished OEM UNLOCK will be ungrayed. then you can request a unlock token from oneplus then wait 7 days then flash an unlock bootloader.
im still carrier locked
Click to expand...
Click to collapse
Do you know which specific app to uninstall removes the OEM unlock restriction? I want to unlock the bootloader, but would rather keep the other preinstalled software.
I've done a good bit of scouring here but cannot seem to get a definitive reason or fix to my current issue.
Here's the order of events:
Bought a new N200 unlocked version.
Unlocked bootloader - no issues.
Put TWRP on it - still a WIP so the issues with it were expected. It's minimal and is not fully working. I was aware of this and succeeded at this step as well.
Put Magisk on it. Once again, minimal issues.
Decided to return to stock because it's difficult to update the device.
Removed root. Complete uninstall of magisk.
Used payload dumper to extract the factory boot image. Used the same method to reinstall this to the device.
Booted back to stock recovery. Completely wiped device keeping system intact. Then booted up.
Booted back to fastboot to relock bootloader. ERROR - DEVICE CORRUPT.
Hardware booted back to fastboot and unlocked bootloader. Device works.
New partial update rolls out. Cannot update.
So here's the issue. I cannot relock the bootloader or the device will read as corrupt and not boot up. I also cannot update the device because it states the device is either "busy" or has an "installation problem". I also cannot sideload from recovery because it states the device is unauthorized (weird since the bootloader is still unlocked) and sideload doesn't really seem to work via fastboot either.
Any tips or help that can get me completely back to stock on this unlocked variant would be greatly appreciated.
You'll have to just redo everything msm your device back to factory. Then update to the partial patch. Afterwards you can do the root process.
Winnower Amber said:
You'll have to just redo everything msm your device back to factory. Then update to the partial patch. Afterwards you can do the root process.
Click to expand...
Click to collapse
The problem lies in the MSM part of your reply Winnower. I have the unlocked variant. The tool for that is not available. Not yet, anyways. But I am hopeful I will be getting my hands on that today for the community.
You could use Android studio to piggy back on the update file.
When you relock the bootloader, you have to have correct vbmetas. (Verified boot metadata). When you unlocked, OnePlus automatically disabled them. They may have been cleared (This is the usual way to disable verified boot, by blanking the hashes from the vbmetas.) or they may just not match the current version installed.
You restored to the "full" OTA version from the website, but if you previously took a "patch" OTA update over the network, your existing vbmetas would not match the full OTA version.
Also, keep in mind there are two slots to deal with. The sideload update mechanism checks both copies for modification, and you probably only reverted one.
I've read comments by others that relocking the bootloader is not a requirement for the sideloader to update, but reverting the software is.