Database Info

Root method yet for VS987?

Hey guys, I just received a complimentary LG G5 (VS987) last week from Verizon as a means of making up for the Marshmallow update continually destroying my LG G3 and its replacements Anyway, it's a great phone, but I've been disappointed so far to find that there's no root method at the moment. At least not one I can find easily. Do you guys know if there's a method hidden away out there or if a particular developer is working on it right now?

I really hope one comes out soon and this doesn't become another crap phone but so far no. I just upgraded to this phone assuming a root would come soon but marshmallow phones on Verizon are death! Can't wait for CyanogenModbut right now you'll have to wait.

I just got the LG G5 Verizon variant as well on Friday. Was a little reluctant because of possibly not being able to root and unlock boot loader. Subscribing to this thread because I hope there will be support for this soon. Kinda hoping there would be a solution like Safestrap was for the galaxy s5, and then installing an LG version of the Samsung_bootloader_unlocker.

Abramelin said:
I just got the LG G5 Verizon variant as well on Friday. Was a little reluctant because of possibly not being able to root and unlock boot loader. Subscribing to this thread because I hope there will be support for this soon. Kinda hoping there would be a solution like Safestrap was for the galaxy s5, and then installing an LG version of the Samsung_bootloader_unlocker.
Click to expand...
Click to collapse
There is hope! With the quadrooter exploits being discovered we may have root soon :3

Nathamio said:
There is hope! With the quadrooter exploits being discovered we may have root soon :3
Click to expand...
Click to collapse
I don't see that at all, since the issue of a locked bootloader remains an obstacle on the G5.

Temp rooting is the solution for that, once we can get temp rooted we can find workarounds to enable unlocking.

Temp rooting has been possible for a many a moon on the G5, but that hasn't enabled anyone to unlock the bootloader

Maybe not yet. But it is plausible that a temp root would grant access to boot loader. If the G5 becomes popular enough LG might do it for us. I heard they've done it for Europe variants but said they don't plan for any other. It might be 3-5 years from now but who knows really. I'm sure someone clever enough will figure out a work around eventually. I work with Arch Linux so I'm not used to being controlled like this. If it weren't for me getting this phone for free, I would definitely have gotten one I *could* root and all.

jpradley said:
Temp rooting has been possible for a many a moon on the G5, but that hasn't enabled anyone to unlock the bootloader
Click to expand...
Click to collapse
Can you post that link?

What about this option?
I'm a new user, so I can't post the link, but did a Google search for VS987 custom rom and came up with this: search4roots.com/how-to-easily-root-lg-g5-vs987-marshmallow-6-0-1/

Barook said:
I'm a new user, so I can't post the link, but did a Google search for VS987 custom rom and came up with this: search4roots.com/how-to-easily-root-lg-g5-vs987-marshmallow-6-0-1/
Click to expand...
Click to collapse
Spam site

andyroidking said:
Spam site
Click to expand...
Click to collapse
This is how you get the viruses.

Hi. My Nexus dumped, I got a G5. Where's the temp root? I will see what I can do for your boot loader. Few questions about the G series I need answered:
Flashing tools used on other variants
Leaked signing tools?
LG G series boot loader format
Encryption on this boot loader
Get me temp root and answer these questions and ill push the locked image here to work on.

LupineDream said:
Hi. My Nexus dumped, I got a G5. Where's the temp root? I will see what I can do for your boot loader. Few questions about the G series I need answered:
Flashing tools used on other variants
Leaked signing tools?
LG G series boot loader format
Encryption on this boot loader
Get me temp root and answer these questions and ill push the locked image here to work on.
Click to expand...
Click to collapse
You ever get the info you needed? I've heard of people gaining temp root with the 987 but I've never seen the published method or any real evidence of it.

So I'm assuming this is not legit?
http://www.androidinfotech.com/2016/06/root-lg-g5-verizon-vs987-601-marshmallow.html?m=1

LupineDream said:
Hi. My Nexus dumped, I got a G5. Where's the temp root? I will see what I can do for your boot loader. Few questions about the G series I need answered:
Flashing tools used on other variants
Leaked signing tools?
LG G series boot loader format
Encryption on this boot loader
Get me temp root and answer these questions and ill push the locked image here to work on.
Click to expand...
Click to collapse
Artimis said:
So I'm assuming this is not legit?
http://www.androidinfotech.com/2016/06/root-lg-g5-verizon-vs987-601-marshmallow.html?m=1
Click to expand...
Click to collapse
Have you tried it? I assume if there is root, it'd be placed on XDA dev for sure.

donjo19 said:
Have you tried it? I assume if there is root, it'd be placed on XDA dev for sure.
Click to expand...
Click to collapse
No, I don't have a G5 yet. I plan on ordering one in 8 days when my contract is eligible for renewal but I've never owned a phone I couldn't root and don't know how I feel about it. Unfortunately, that seems to be the case with pretty much all VZW phones now.
The ones that can be rooted, I'll need to make other sacrifices on like non-removable storage, non-replaceable battery, no IR blaster, etc. Makes me really appreciate my G3

Artimis said:
No, I don't have a G5 yet. I plan on ordering one in 8 days when my contract is eligible for renewal but I've never owned a phone I couldn't root and don't know how I feel about it. Unfortunately, that seems to be the case with pretty much all VZW phones now.
The ones that can be rooted, I'll need to make other sacrifices on like non-removable storage, non-replaceable battery, no IR blaster, etc. Makes me really appreciate my G3
Click to expand...
Click to collapse
The G3 is still by far my favorite Android phone. If I could go back to it, I would in a heartbeat. I eventually had mine brick. But this phone has been nothing but a disappointment...mainly for lack of root.

None of the files from that site seem to be infested with a virus, however their instructions are not very clear on how to use it all. Unless I am just not reading it correctly.

Wow, this is sad news indeed. I too have loved my G3, but this is due in large part to me having root. I was considering upgrading to the G5 simply because I expect to see deep discounts on Black Friday, but no root means no thank you. I will have to find another "root" to the future.

Tmobile 7 Pro Battery Sucks

Hi everyone, long oneplus user here came from OP6 to OP 7 PRO that I purchased from Tmobile 2 weeks ago. Everything was going great until I upgraded the software to the latest version 9.5.11.GM31CB and my battery sucks really bad.
I have never had issues with battery with Oneplus devices, I have very little apps installed and it drains at least 10% overnight while not being used and also drains excessivley while using Google maps or practically any app while the screen is on. I've seen several others post the same issue on Oneplus community but no one replies back. To make things worse, I can't unlock bootloader since I also need the unlock code and the phone needs to be paid off and my device is on the Tmobile payment plan.... so now im stuck with a new device that has to be charged 2 sometimes 3 times daily. Im debating whether selling it on ebay and just buying an older OP Device.
Can anyone advice me on what to do? I really appreciate any help.

SystemErrorOne said:
Hi everyone, long oneplus user here came from OP6 to OP 7 PRO that I purchased from Tmobile 2 weeks ago. Everything was going great until I upgraded the software to the latest version 9.5.11.GM31CB and my battery sucks really bad.
I have never had issues with battery with Oneplus devices, I have very little apps installed and it drains at least 10% overnight while not being used and also drains excessivley while using Google maps or practically any app while the screen is on. I've seen several others post the same issue on Oneplus community but no one replies back. To make things worse, I can't unlock bootloader since I also need the unlock code and the phone needs to be paid off and my device is on the Tmobile payment plan.... so now im stuck with a new device that has to be charged 2 sometimes 3 times daily. Im debating whether selling it on ebay and just buying an older OP Device.
Can anyone advice me on what to do? I really appreciate any help.
Click to expand...
Click to collapse
Convert to international version and try Q stock with arter97 kernel. Leaving TMobile firmware has been a blessing. Read through the posts to learn how to oem unlock without unlocking through TMobile.
Hint: get the msm tool with appropriate firmware, flash international, flash ob3/4 (one of those two), unlock oem without having to talk to TMobile. Then install the latest custom twrp and flash away. I strongly recommend going decrypted, because you have to do it all over again if you get soft bricked.
Edit: flashing roms and whatnot is a lot harder than on older phones. I always keep the msm tool ready it I need to start over the process.

Definitely go international...

preference said:
Convert to international version and try Q stock with arter97 kernel. Leaving TMobile firmware has been a blessing. Read through the posts to learn how to oem unlock without unlocking through TMobile.
Hint: get the msm tool with appropriate firmware, flash international, flash ob3/4 (one of those two), unlock oem without having to talk to TMobile. Then install the latest custom twrp and flash away. I strongly recommend going decrypted, because you have to do it all over again if you get soft bricked.
Edit: flashing roms and whatnot is a lot harder than on older phones. I always keep the msm tool ready it I need to start over the process.
Click to expand...
Click to collapse
you need the developer preview 3 13x3 to bootloader unlock now

preference said:
Convert to international version and try Q stock with arter97 kernel. Leaving TMobile firmware has been a blessing. Read through the posts to learn how to oem unlock without unlocking through TMobile.
Hint: get the msm tool with appropriate firmware, flash international, flash ob3/4 (one of those two), unlock oem without having to talk to TMobile. Then install the latest custom twrp and flash away. I strongly recommend going decrypted, because you have to do it all over again if you get soft bricked.
Edit: flashing roms and whatnot is a lot harder than on older phones. I always keep the msm tool ready it I need to start over the process.
Click to expand...
Click to collapse
Thank you soooo much. I kinda had a hint that I had to convert to the international version but just wasn't sure. I found the MSM tool online but when I click to run it, it gives me an error code. Do you by any chance have the link to the one you are using? Will update everyone on how the conversion goes, heck might even make a video for others to follow.

SystemErrorOne said:
Thank you soooo much. I kinda had a hint that I had to convert to the international version but just wasn't sure. I found the MSM tool online but when I click to run it, it gives me an error code. Do you by any chance have the link to the one you are using? Will update everyone on how the conversion goes, heck might even make a video for others to follow.
Click to expand...
Click to collapse
I'll try to help after work. I just use the one posted in the T-Mobile conversion thread. Google 'T-Mobile to international xda OnePlus 7 pro' and you should find the msm package I use whenever I get softbricked. Hold power, volume up, and volume down at the same time to enter bootloader mode. Basically turn off the phone, hold down all the buttons while connected to a PC with msm, hit start on the msm tool when the phone shows up. Make sure auto-reboot is off. Don't know why but lots of users say keep that option off

How To Guide Rooting the SM-F711B (on Version F711BXXU2AUI4) working

First of all:
I'm no Dev...just someone who likes to play lego.
From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk.
I've read a good startup here.
Hopefully this makes this thread clear enough so that i dont need to describe the whole procedure step by step.
(https://www.naldotech.com/root-samsung-galaxy-z-flip-3-5g-magisk/)
(1.OEM-Unlock,2.BL-Unlock,3.extract boot.img,4.patch boot.img via magisk on the unrooted mobile,5.patch boot.img.tar to AP&BL via Odin, 6.pray)
Anyways...here are maybe small hints to avoid a few traps.
a) Just do the oem-unlock in the dev-options (enabled by tapping buildnumber 5 times) is just half of the rent.
Afterwards i had to go in Download-mode (switch of mobile, press volUp+volDown and connect PC-cable.)
There appears a possibility of choice.
Press VolUp short: get the mobile on standby to flash the rom via odin.
Press VolUp LOONG: get the mobile to the menu where the bootloader can finally get unlocked. (Otherwhise every try to patch a rooted img will be blocked by bootloader-protection.)
Of course this can possibly be done via adb/fastboot commands.
Funny side note: OEM-Unlock-option will completely disappear from Dev-options and waranty is lost. Also the mobile stops to get Updates OTA which means that you have to update manually whenever a new version will appear in the net.
b) patching boot.img via magisk should work as described in many other magisk-rooting-manuals.
Flashing the tar back to the mobile via odin was little bit tricky.
It doesnt reach out just to provide the magisk_patched.tar to Odin just on the AB-line.
I had to patch it to BL too.
Cheers
MikGx

When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.

@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2

MikGx said:
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
Click to expand...
Click to collapse
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.

naldotech.com, the link you provide is pretty clear about the process. What it doesnt say is what to do at the end. When you untick "reboot" in odin, and you finish flashing, your phone will stay in download mode. Then what to do?. Press power and volume down to leave and restart the phone? or, power and volume down, screen goes black imediately power and volume up, enter recovery and restart from there.? please someone ?

Press the power and volume down buttons for about 7 seconds and it will reboot

beanbean50 said:
Press the power and volume down buttons for about 7 seconds and it will reboot
Click to expand...
Click to collapse
I did as you mention but it didnt work. It made me reset the system. But I Fallowed the naldotech.com guide. At the end, being in dawnload mode, I pressed power and volume down, when the screen got black I pressed power and volumen up, I entered recovery mod, cleared cache and re- started the system: Voila my phone is rooted

Hello.
Can someone pleas provide a working link for frija download? The one referring from naldotech seems to be broken (https://www.naldotech.com/download-samsung-galaxy-stock-firmware-frija-tool/)
Update: Found a link via google -> https://technastic.com/odin-download-samsung-latest-all-versions/

twistedumbrella said:
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
Click to expand...
Click to collapse
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.

d0x360 said:
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
Click to expand...
Click to collapse
twistedumbrella said:
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
Click to expand...
Click to collapse
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.

twistedumbrella said:
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
Click to expand...
Click to collapse
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.

d0x360 said:
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
Click to expand...
Click to collapse
You got where I said "I guess the disclaimer is misleading" right?

twistedumbrella said:
You got where I said "I guess the disclaimer is misleading" right?
Click to expand...
Click to collapse
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons

d0x360 said:
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
Click to expand...
Click to collapse
Lucky? I dunno. Had I known it would cause this much trolling, I wouldn't have bothered to mention it.

I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?

david.siebauer said:
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
Click to expand...
Click to collapse
Partially. I just did that: I have AfWall running on my old phone, tried to unlock the Flip with this manual here in order to use the firewall there, did something wrong - and stumbled upon Netguard while searching what might have happened and decided to give it a try first. (Unless there is a custom ROM for the phone available, I have no other need for root or an unlocked bootloader.)
From what I could find on my Flip 3, you can unlock and relock the bootloader as you like - but as soon as you install a non-genuine bootloader (i.e. one chnaged by Magisk) you will trip Knox - and this cannot be reverted.
In such a case you can still re-lock your bootloader and unlock it later (on my phone, that "7-day-no-switch-indeveloper-options" routine kicked in, but you can circumvent that) - but Knox will stay in its state. From what I read this means some things will not work such as Samsung Pay, but I do not know the details (yet) apart from that it does not bother me ;-), and the nag screen during boot is gone.

Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now

david.siebauer said:
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
Click to expand...
Click to collapse
Well, it's better than my Sony - there it is "once unlocked, always unlocked" with no way back at all
But I have to admit I understand the logic why the manufacturers do that, at least to the degree that they trip a fuse as Samsung does.
By rooting the phone, you shift the responsibility for the software state of the phone from the manufacturer to the user, so I think it is okay to implement something to make it clear to possible future buyers that it is or has been in that state.
(This does not include however all the other stones they put in the way of people wanting to develop or use custom ROMs!)

I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features. Guess u shouldn't have bought a Samsung lol.

david.siebauer said:
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features.
Click to expand...
Click to collapse
Oh, trust me - as soon as I hear there is a custom ROM that works as a daily driver I will root mine as well. I really hope that there will be one for this phone
david.siebauer said:
Guess u shouldn't have bought a Samsung lol.
Click to expand...
Click to collapse
Sadly there is no Fairphone mini or Fairphone Flip - or would it be Fairfliphone? ... Flipfairphone?... - yet (if ever), so the only current alternative would be Motorola. And the price tag for the Razr is simply too much, even if I personally think it looks better than the Samsung. Additionally, I do not know if they are in any way better when it comes to rooting or loading custom ROMs.

Flashing LineageOS for MicroG on 8T (T-Mobile Variant) purchased from OnePlus

Hello all!
Thanks for taking the time to click into this.
About me: I mostly see myself as a somewhat tech-savvy noob - I have rooted several devices in the past, flashed ROMs, etc.
New Device: OnePlus 8T T-Mobile Variant purchased from OnePlus.com
Condition: Brand New - never started the device
I would like to essentially imitate Calyx as described here.
=> install TWRP/Magisk + flash 'LineageOS for MicroG'
Questions:
1) Will I be able to unlock the bootloader given that this is the T-Mobile variant purchased from OnePlus?
2) Do I need to take additional steps because this phone is the T-Mobile variant?
3) basic question: I have never started the phone so it has no personal data - should I back up the current setup in case I need to return to OOS for any reason or can I track down the default OOS installation making that all unnecessary?
(I remember in the past default Samsung installations were easily tracked down and flashed using Odin).
4) Would you recommend any detailed instructions to go through the process of backup, installing custom recovery, accessing root privileges, flashing LineageOS for MicroG, etc?
(I feel like I am piecing parts together from different places and it's all not fitting together)
Thank you so much for reading this.... I feel like I'm going down several rabbit holes currently so any perspective or support is welcome!
It would be helpful to hear any thoughts from some more experienced peeps before I move ahead.
Thank you!

Currently, I am trying to get the SIM unlocked, then unlock the bootloader, and proceed with the plan above.
I am considering returning the phone and getting a different one that has more users on XDA to avoid having bizarre issues arise with the steps involved with the T-Mobile version of the 8T and being totally on my own.

doctadocta said:
Currently, I am trying to get the SIM unlocked, then unlock the bootloader, and proceed with the plan above.
I am considering returning the phone and getting a different one that has more users on XDA to avoid having bizarre issues arise with the steps involved with the T-Mobile version of the 8T and being totally on my own.
Click to expand...
Click to collapse
yeah I dont see much help for Tmo version and I faced lots of issues just trying to get a brand new one recognized by my computer.

Ejvyas said:
yeah I dont see much help for Tmo version and I faced lots of issues just trying to get a brand new one recognized by my computer.
Click to expand...
Click to collapse
whoa! that's helpful feedback. Thank you for posting!
Based on your comment, I am leaning towards returning the phone.
I think I learn best through examples and may need a little support.
I am now wondering how I can figure out which phones have the largest 'community' on XDA.

I have the T-Mobile variant. There's more support and options available so don't be discouraged.
Normally, you have to be SIM unlocked before you can do anything else, like bootloader unlocking. If the phone is being paid for or financed and you haven't been a long time customer you may or may not get it SIM unlocked.
That said, I got mine SIM unlocked after contacting the T-Mobile Tforce people on Facebook. Then I saw this thread on Rebranding the T-Mobile variant.
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
Following it I changed the T-Mobile firmware to the European firmware. If nothing else you get more recent updates and a local update feature (full OTA updates can be downloaded and installed locally). As a result of the conversion I was able to simply fastboot unlock the bootloader without need for waiting for a code from OnePlus. The phone is now bootloader unlocked and rooted with Magisk.
Note that according to the OP, SIM unlock is not necessary for the conversion but you'll still need to be SIM unlocked to be able to unlock the bootloader.
Now that I'm "free" I now have the itch for a custom ROM. Over the years all of my devices run either with microG or just UnifiedNlp but no Google. I feel the need to do the same here. Currently I just have most Google apps disabled and using FOSS apps in their place but still...
Besides LineageOS for microG, the 8T also has Carbon ROM and crDroid. They historically have always had signature spoofing support so I assume they still do with Android 11. That means microG can be used.
Check the guides and ROM/Kernel threads for more info.
I don't know if I can get to trying anything this week but I hope to. I work at a drive-in movie theater and with Spider-Man coming out this week I'll be quite busy.

marcdw said:
I have the T-Mobile variant. There's more support and options available so don't be discouraged.
Normally, you have to be SIM unlocked before you can do anything else, like bootloader unlocking. If the phone is being paid for or financed and you haven't been a long time customer you may or may not get it SIM unlocked.
That said, I got mine SIM unlocked after contacting the T-Mobile Tforce people on Facebook. Then I saw this thread on Rebranding the T-Mobile variant.
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
Following it I changed the T-Mobile firmware to the European firmware. If nothing else you get more recent updates and a local update feature (full OTA updates can be downloaded and installed locally). As a result of the conversion I was able to simply fastboot unlock the bootloader without need for waiting for a code from OnePlus. The phone is now bootloader unlocked and rooted with Magisk.
Note that according to the OP, SIM unlock is not necessary for the conversion but you'll still need to be SIM unlocked to be able to unlock the bootloader.
Now that I'm "free" I now have the itch for a custom ROM. Over the years all of my devices run either with microG or just UnifiedNlp but no Google. I feel the need to do the same here. Currently I just have most Google apps disabled and using FOSS apps in their place but still...
Besides LineageOS for microG, the 8T also has Carbon ROM and crDroid. They historically have always had signature spoofing support so I assume they still do with Android 11. That means microG can be used.
Check the guides and ROM/Kernel threads for more info.
I don't know if I can get to trying anything this week but I hope to. I work at a drive-in movie theater and with Spider-Man coming out this week I'll be quite busy.
Click to expand...
Click to collapse
Do you know how to fix this ?
"Automatic Detection of DDR failed"

Ejvyas said:
Do you know how to fix this ?
"Automatic Detection of DDR failed"
Click to expand...
Click to collapse
Excuse the late reply.
No, not too versed on this device really. I searched for that error and got a lot of hits but didn't have the time to read up. Sorry.

[SOLVED] "FAIL" trying to fastboot Unlock Code to Moto One 5G Ace

I got the Unlock Code from Moto with no problem, but can't get the phone to take it. FAIL, over and over again. I've tried several times, rebooted the phone, powered off, even tried an FDR. I keep getting a 'FAIL" message trying to push the code to the phone.
Just got the phone (used) today and I do have Unlock enabled in Dev Options. CID is 0x0032, obviously unlockabled since I did get the code from Moto. Twice. I redidthe Unlock request with a new string and got the same code again. Nothing is working. I've unlocked 15 or more Moto phones and never had anything like this happen before.
Using "fastboot oem unlock UNIQUE_KEY [20-character unlock code string]". Copied it, typed it manually, etc etc. FAIL FAIL FAIL.
Frustrating. Any clues/suggestions?
- - - - -
Edit to add: This phone has (I presume) the newest firmware on it, QZKS30.Q4-40-95-9 (RETUS), which has not been uploaded to lolinet yet.
Could this newest update be the problem? If so, can I safely roll back to 95-6 or even something older?
= = = = = = = = =
SOLVED. There was apparently an issue with the first phone I tried. Bought a second XT2113-2 relatively cheap (64GB) which came with the same 40-95-9 firmware, and it took the unlock code without a hitch.

I recall that I experienced something similar to this as well. A little bit of searching lead me to believe my issue was an older stock firmware bug. My stock firmware was initially from Jan 2021 and I did ota updates until it got to about Aug 2021 and then the phone unlocked. Can't say for sure that the deviced just needed time to "phone home" before allowing unlocking tho (I've read rumors).
If there is a ota update available, try that. I do know that I am able to relock/unlock on the 40-95-6 (Feb 2022) RETUS stock firmware.

notmyrealhandle said:
I recall that I experienced something similar to this as well. A little bit of searching lead me to believe my issue was an older stock firmware bug. My stock firmware was initially from Jan 2021 and I did ota updates until it got to about Aug 2021 and then the phone unlocked. Can't say for sure that the deviced just needed time to "phone home" before allowing unlocking tho (I've read rumors).
If there is a ota update available, try that. I do know that I am able to relock/unlock on the 40-95-6 (Feb 2022) RETUS stock firmware.
Click to expand...
Click to collapse
Thanks for replying. This phone has 40-95-9 firmware (March 1, 2022) which looks to be the latest OTA.
I have wondered if I'm stuck in another one of the newer Moto's (or Android's) mysterious holding patterns. Maybe it'll work in a few days. I will certainly post here if that's the case. . . . But why give me the Unlock button plus the Unlock Code, but then hold me back from actually pushing it to the phone? That wouldn't make a lot of sense.
This is the exact message returned by the bootloader every time:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
I believe I'll try reflashing the 40-95-9 firmware, downloaded this morning via Rescue and Smart Assistant.

Reflashing firmware didn't help.
Edit to add:
I should probably stress, I flashed the entire firmware with no problems at all.
Should that suggest that this bootloader unlocking failure is not a hardware problem? . . . because if broke hardware is a possibility, I would definitely want to return this phone to the seller.

Moondroid said:
Reflashing firmware didn't help.
Edit to add:
I should probably stress, I flashed the entire firmware with no problems at all.
Should that suggest that this bootloader unlocking failure is not a hardware problem? . . . because if broke hardware is a possibility, I would definitely want to return this phone to the seller.
Click to expand...
Click to collapse
Two other things you can try:
1. make sure you are using an up to date fastboot exe (I'm using fastboot version 33.0.1-8253317 on ubuntu linux).
2. Try from both the bootloader mode and fastbootd mode on the device - I forget how to get to fastbootd from stock `adb reboot fastboot` might do it.
EDIT I'm pretty sure you want to be in the bootloader mode. Just thought I'd mention it as fastbootd was new to me and some fastboot commands seem to like the device to be in one mode or the other.
HTH

notmyrealhandle said:
Two other things you can try . . .
Click to expand...
Click to collapse
Still nothing.
I found some newer adb & fastboot utils (2021 vs 2018) and tried those. That just changed the error message a teensy bit (replaced "remote failure" with a couple of bare quote marks).
I also uninstalled & reinstalled my Motorola drivers before trying the newer adb & fastboot. That didn't help either.
Trying to boot twrp gives me a "permission denied" error.
So all I can think to try now is to run another firmware reinstall via LMSA (Rescue and Smart Assistant), just to see if that hiccups anywhere as much as anything. (I manually flashed all the files the first time.)
I think it's past time for me to say something like "this doesn't just suck, it SUPER-sucks." Moto gave me the phreaking Unlock code, but the phone won't let me use it.

Moondroid said:
Moto gave me the phreaking Unlock code, but the phone won't let me use it.
Click to expand...
Click to collapse
It will only work 48 hours after the unlock email is sent, as per this thread <https://forum.xda-developers.com/t/oem-unlocking-grayed-out-on-moto-g-play-2021.4259833/page-2>
I recently went through this myself. It was really baffling because the customer service / tech support would not tell me anything about it. Maybe it's some kind of hyper secret security measure?
Just keep the phone online and wait it out.

slipchicken said:
It will only work 48 hours after the unlock email is sent, as per this thread <https://forum.xda-developers.com/t/oem-unlocking-grayed-out-on-moto-g-play-2021.4259833/page-2>
I recently went through this myself. It was really baffling because the customer service / tech support would not tell me anything about it. Maybe it's some kind of hyper secret security measure?
Just keep the phone online and wait it out.
Click to expand...
Click to collapse
I tried the unlock code 5 minutes after I got it. Why would I wait 48 hours? Lol . . .
If this is another "time-delay" thing it doesn't make any sense at all. OEM Unlock was already enabled, the phone gave me an unlock string to send Moto, and I got the unlock key from Moto with no delays at all. Within an hour after unboxing the phone I was trying to push an unlock code to the phone.
I also tried getting another code from Moto, generated a new string and all, but the second code Moto sent me was exactly the same as the first. I did try it (again) on the phone but got the same "FAILED" message as before.
This is just nuts. Unless the latest OTA 95-9 is in fact the culprit. Moto's unlock-code process might still send unlock codes that possibly will no longer work after a certain point? Hopefully I'll get a definitive answer on this aspect soon.

Moondroid said:
Moto's unlock-code process might still send unlock codes that possibly will no longer work after a certain point? Hopefully I'll get a definitive answer on this aspect soon.
Click to expand...
Click to collapse
I meant that it will only start working once 48 hours have passed. Leaving internet active may be a requirement, and a restart may be a requirement too.
For instance if you get the first code email at 8:00am on June 7th, the code will only work after 8:00am on June 9th.
EDIT: Also I have tried manually changing the time in the phone's settings and it didn't work. I had to wait the full 48 hours for it to start working.
I do agree however that it is absolutely nuts of Motorola to do this without any sort of explanation. That's why I assume it's some kind of secretive or misguided anti-theft measure.

slipchicken said:
I meant that it will only start working once 48 hours have passed. Leaving internet active may be a requirement, and a restart may be a requirement too.
For instance if you get the first code email at 8:00am on June 7th, the code will only work after 8:00am on June 9th.
EDIT: Also I have tried manually changing the time in the phone's settings and it didn't work. I had to wait the full 48 hours for it to start working.
I do agree however that it is absolutely nuts of Motorola to do this without any sort of explanation. That's why I assume it's some kind of secretive or misguided anti-theft measure.
Click to expand...
Click to collapse
I was in that thread you quoted and I don't remember anything about having to wait AFTER getting the unlock code. Wait for OEM Unlock to show as enabled in Dev Options, yes, I'm thoroughly familiar with that. But I have never-never-never had to wait for an unlock code to work after receiving it from Moto. If that's in there somewhere please point more specifically? because I've unlocked a whole bunch of Moto phones and as I said, I've never heard of being able to enable OEM Unlock, getting the unlock code from Moto and then having to wait to use it.

See bottom of top post. The phone had some kind of problem that wouldn't allow it to accept the unlock key.