Hello, as you all can see I have the T-Mobile version of this phone. I have tried everything and I cant get the device rooted. I bought this phone unlocked from Amazon and I use it on Mint Mobile. I have no idea how or even if it effects the rooting process but, I cant think of any reason why none of the methods I've used dont work. I have tried using the "All In One Tool" and the same thing happens with that tool, that happens with every method I've tried; I can use a cmd window to boot into fastboot but, once I am there none of the commands I enter seem to have any effect. I can explain more but, has anyone experienced this or knows what the problem is?
All the info you need is right here:
[GUIDE] ROOT OnePlus 7T Pro McLaren 5G (T-Mobile version HD1925)
Hi. So I wanted to put together a little write-up on how to root the T-Mobile McLaren 5G variant, at least how I rooted mine, as there doesn't seem to be anything about this yet. I was actually able to root my device last night successfully, so I...
forum.xda-developers.com
Assuming your phone has been SIM/carrier unlocked by T-Mobile, you then need to request an unlock token from OnePlus. All info in above thread
But I highly highly highly recommend making a backup of your persist partition using the MSM tool before even unlocking the bootloader
Related
I have a Zenfone 3 ZC520TL US model phone (apparently there are multiple versions of the ZC520TL).
First question: Is there a LineageOS available for this phone? Or any plans for it? I don't see it listed on LineageOS's website. But there was a thread here a few months ago about it, although I'm not sure if that was specifically for the ZC520TL or the US specific ZC520TL.
Second question: Is it possible to root this phone? From the best I can tell, the only way to do this is with Magisk Manager, creating a patched boot image. Although, I'm not sure what the probability of bricking the phone is by doing this. I would assume you could always manually install the stock firmware, but I'm not sure if that would work.
Third: Is root even needed? The only reason I think I'd really need root is to enabling tethering on the phone. I'm currently with an MVNO that doesn't specifically allow tethering. I'm not sure how providers go about detecting tethering these days, I'm sure they probably could detect it regardless of whether the phone is rooted or not. But I rarely tether, in fact I rarely use over 1GB of data a month period. But the last thing I really want is to be stuck out some where when I have to be away from home for a few days and not being able to tether to my laptop for work. Or when I'm sitting outside an arm's length away from my home's wifi signal.
Do you still need to add the net.tethering.noprovisioning=true line to the build.prop file in order to tether?
Fourth: I used Asus's UnlockTool from their website. But I don't know if it truely unlocked the phone. When entering fastboot mode, I no longer see the message about CSC, I see a message that says FASTBOOT mode... But fastboot getvar unlocked still shows no. Although, I'm not sure if there is a TWRP for this phone or a LineageOS or alternative that would really necessitate any of this anyway.
Hi
So I've unlocked my bootloader and installed the latest lineageOS onto it. Before I could get LineageOS on it, I had to flash an universal bootloader on to it.
androidfilehost'com/?fid=673368273298930589.
I have an few questions
I 've brought my device in Australia so my phone model is A2017G however now when i check about phone it states its an A2017U. Should I be using A2017U softwares now instead of A2017G? Like looking up forums that target A2017U specifically since my model is no longer A2017G.
- The unlocked bootloader screen that disappear after 5 seconds. Does it do anything else apart from being an little annoying? If so, what does it also do? Also I checked the forums on the removal but I am stuck on deciding which is my device model (A2017G or A2017U)
- My fire emblem heroes is no longer working as it just crashes in the opening loading screen. I am certain that LineageOS does not root your device so I don't have root. Anyone knows an fix?
Thank you
When you flash the Universal Bootloader that's when the model changes, i think (but you're still a2017g). The screen lets you know that you have a different bootloader from stock, if you want to remove it, go here, you can restore it by flashing the universal bootloader (remember to remove pin/password or finger before flashing the file also when restoring the screen, remove it as well). Not sure about the fire emblem heroes and no LOS doesn't come pre-rooted.
Hello everyone. I'm just getting my new device situated and, knowing that unlocking the bootloader often requires a factory reset, I thought to make that one of my first tasks with my T-Mobile McLaren 5G. I was able to successfully activate the Developer menu but when I went there, I found that the OEM Unlock setting was not only off, but greyed out and unable to be enabled! If I'm correct, enabling OEM Unlocking in the Dev menu is the first step to unlocking the bootloader, before connecting via ADB or using some sort of toolkit.
I called T-Mobile to ensure this was not their doing and according to their rep (after getting transferred from CS, to a tech, to a senior tech) apparently this is not something they have control over ; they can unlock the phone to use other SIMs but don't have anything to do with the bootloader, the ROMs etc. They suggested contacting OnePlus and gave me an 800 number, but I thought I'd check with the community first just in case.
Should this OEM Unlocking option be capable of being enabled? Is there a way to unlock the bootloader without this step? I'm a bit out of date on the current state of unlocking / custom ROMs and the like - is there any sort of open source GUI (or for that matter, CLI) based toolkit for easily flashing/unlocking bootloader and other tasks? There used to be some tools available for older Nexus, Pixel, and OnePlus devices a few years back but the older ones I recall don't seem to be updated since then. If not and it all needs to be done manually, do we still use the Android SDK Platform Tools (I assume you don't need the whole Android Studio or even Android Studio CLI)?
Regarding T-Mobile, there seems to be some discussion about certain OnePlus devices requiring a code from OnePlus itself via ( https://www.oneplus.com/unlock_token ) in order to unlock the bootloader? I don't remember it being this much trouble with past earlier devices (including Nexus and OnePlus)! Is this step required or is there a workaround? Regardless, even that page describes being able to toggle the OEM Unlocking setting before anything else, so something seems to be of concern. Ideas? Thanks!
The device sim unlock for the OnePlus 7T Pro 5G McLaren is hidden in Settings-->SIM & network-->ADVANCED Network Unlock; it doesn't have a separate magenta colored unlock app icon like some older T-Mobile phones do. But, the rest should be similar to the T-Mobile OnePlus 7 Pro process https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
After the permanent device sim unlock is completed, the OEM unlocking option should no longer be greyed out.
OK so I need some help...
When I originally purchased my LG G6 in June of 2019, I made sure it was a US997 model, but I ended up getting a BRIGHTPOINT version during my purchase. I went through the website to check the imei and the device ID and it gave me the not unlockable status.
After that, I went and decided to update the software manually to US99721e since it wouldn't OTA it and have been on that ever since. Now, I just recently tried while on the 21e software and I was given an unlock.bin code!
So if someone could help me out:
IF you're on a US997 BRIGHTPOINT G6:
-Download LG UP and UpperCut
-Download US997_21e_01_0211-UCL.kdz at lg-firmwares.com (this is the one I'm on, try this one first!)
-Once it's done, enable developer mode, adb debugging, and OEM unlock
-Go through the unlocking process
Please let me know what you find out!!
Is that only for us cellular?
Sent from my V60 ThinQ using XDA Labs
I have a brightpoint LG G6, which I bought as the seller claimed it was an unlocked US997, failing to share it was a OEM phone. I don't understand how this works please can you clarify? I tried the unlocking process and I have to supply my phone information to LG. Their database says it is a brightwell phone and so they won't release the unlock. Are you saying that after installing this ROM I don't need the key from LG to unlock the bootloader?
I have installed Uppercut and LGUP (1.14 as newer versions don't seem to work). I downloaded the ROM and I have the LGUP loaded. It shows the phone using US99721a. I have 4 process options, Refurbish, Upgrade, FOTA upgrade or Phonesettings which is the one to use?
It works! At least I obtained an unlock.bin file from LG. I need to work out which is the best LG G6 US997 ROM and how to load it when my SD card doesn't work. Any help or pointers to useful information much appreciated. For anyone else trying this here is what I found. I downloaded the LG windows drivers and LGUP 1.14 (There are newer versions but these don't work with uppercut. I downloaded Uppercut from XDA website and then you run Uppercut not LGUP. This immediately caused my virus checked to block it as it contains a trojan. I didn't like that but googled to find others had the same issue. There seems to be a way to load the correct file to get LGUP to work directly and I would recommend researching that but I disabled the virus software and proceeded. I used the UPGRADE option in LGUP - you need to reboot your phone into download mode. To do so, disconnect USB cable then Power off the phone completely. Now hold Volume Up then plug in USB cable at the same time. Make sure that LGUP is NOT running when you connect the USB cable and start it once you are in download mode. It loads the ROM very quickly and takes a bit longer to reboot and then it needs time to upgrade android as you have a 6 months newer version of Android 8. Then follow direction on the LG unlock site https://developer.lge.com/resource/mobile/RetrieveBootloader.dev. You will need to install ADK https://developer.android.com/studio/releases/platform-tools unzip after you download. LG emailed my unlock code immediately.
Yes, I can confirm that it works with the US997 model now. I already was at version US99721e so I didn't have to jump through the hoops to load this version. I went through the steps to unlock the bootloader via the LG developer website and voila, got sent the unlock.bin file, too.
Now I am pretty sure that I tried that in past perhaps 1-2 years ago and it didn't work, so perhaps LG has secretly flipped a few bits in their database to allow unlocking for these not quite brand new devices.
I just applied the unlock.bin and got the "cannot check for corruption" warning on the boot screen. So this is working - fantastic!
Now have to restore my device from the LG Backup I made before and put on the SD card.
I had tried the unlock last year but I didn't retry before I updated so it may have worked anyway and the update of the ROM wasn't needed. I unlocked the phone and installed Sky Hawk recovery but when that starts it asks for a deception password and nothing I have tried works. I'm not sure if that is a real issue or I can continue safely with flashing a new ROM. Has anyone worked through this issue?
challenger07 said:
I had tried the unlock last year but I didn't retry before I updated so it may have worked anyway and the update of the ROM wasn't needed. I unlocked the phone and installed Sky Hawk recovery but when that starts it asks for a deception password and nothing I have tried works. I'm not sure if that is a real issue or I can continue safely with flashing a new ROM. Has anyone worked through this issue?
Click to expand...
Click to collapse
First, when you're in Adroid remove all screen lock mechanisms, you can re-enable it later.
Enable USB debugging, do adb reboot bootloader and fastboot flash recovery with this recovery instead (rel_o2):
https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-2-1-unofficial-fixes-t3722199
Do the button combo to launch recovery. If you're in recovery, first reformat /data (you have to enter "yes") to get rid of encrption and after that flash the anti-root removal tool mentioned in the post. Then reboot into recovery and then flash Magisk and/or your ROM of choice. Note that I have only used this with stock ROM and Magisk and not tried any custom ROMs, but the thread has plenty of people having also tried other ROMs.
How do you even know if you have a Brightpoint device?
I found out when I tried to unlock. http://mobile.developer.lge.com/
Thanks for the info. I'll dig into this once I know for sure that a version of Android 10 is available to load into the phone.
What I've been dealing with so far keeps asking for a 15 digit IMEI number. My phone only has a 14 digit value.
I pulled box (yes I kept it) and discovered that the IMEI is 15 digits. No idea why the value is the phone truncates the last digit. The site that checks IMEI numbers says that it is the platinum edition: US997PL. Gee, the box says that.
Hello everyone. it's been a week that I work on this problem but I can't solve it myself despite having made numerous attempts. the situation is this: installing lineage os when the system restarted the 6t got stuck in the bootlader. I installed qualcom drivers from here
https://androidfilehost.com/?fid=11410963190603879743
and downloaded msm https://androidfilehost.com/?fid=17248734326145733776
I disabled windows secure boot and installed optional qualcomm drivers on windows... the 6t is correctly recognized as Qualcomm 9008 in the device manager in port 9 but I also tried in the 7 and it is always correct.
I tried other divers (after removing the previous ones) and other versions of msm but I always give the same error : param preload... device not match images.
I have read many discussions and tried many things but I can not solve. someone is willing to help me. Thanks guys.
I also tried uninstalling the drivers and reinstalling these:
QUD.WIN.1.1 Installer-10037.3 Setup.zip | by Dark Nightmare for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
using this version of msm:
6T_MsmDownloadTool_v4.0.58_OOS_v9.0.12.rar | Tool by iaTa for OnePlus 6T
[TOOL] 6T MsmDownloadTool v4.0.58 (OOS v9.0.12) https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
androidfilehost.com
the problem is not solved but changed to: (recording dawnload time in red) images do no match with teh phone!
i can't figure out if it's a msm or driver version problem or maybe something else ...
I don't know what the exact problem. If you have installed magisk or modify something to your phone, sometime msm will fail to recognized or flash..
rom
But if your phone can boot into fastboot mode, try to flash fastboot ROM it might help
Fastboot rom.
[ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if...
forum.xda-developers.com
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
sun-k said:
hello, thanks for the answer. yes I had installed magisk and yes I can enter the fastboot but from there only to turn it off. now I will read the discussion that linked me. Thank you
Click to expand...
Click to collapse
if you get a warning in MSM tool: 'images do not match the phone', you are flashing the wrong image. That could happen to a branded phone. So, if you have a T-Mobile branded phone, either convert it to Global first (that tool has 'device check' disabled), or use T-Mobile MSM tool.
Your other option is to contact OnePlus support and they can help you remotely. I got into a similar bind with my 6t a year and ½ ago and nothing I was attempting worked. It was very frustrating. Ultimately I contacted OnePlus and they got me back up and running in no time. I was a little upset that I had to resort to relying on the manufacturer but also relieved to have a working device again and also thankful that it was an option, even if I would've preferred to have fixed it myself. Good luck.
PS - something to be aware of, I'm not 100% sure that it was a result of OnePlus' involvement/remotely flashing the device but somehow I ended up with a new/different IMEI. This created a world of difficulty with my cellular carrier (VZW) - I had finagled a OnePlus 8 out of them by citing manufacturers defect (I had coverage through VZW despite purchasing the phone directly from OnePlus) but they said the OnePlus 6t they received had a different IMEI than what they expected to receive, which makes absolutely no sense and this is the only possible explanation I could come up with. It ultimately saved me from having to pay for retail for the OnePlus 8 but not without a lot of headaches in between. Oh and lemme just say that having a VZW OnePlus with a locker bootloader sucks, I can't wait to get away from this thing and back to something I can root (I only pulled this maneuver in order to buy myself some time as I wasn't thrilled with the 1+9)