Database Develop

need help on a vzn dev edition and root

hope someone can help.i have a vzn dev ed thats bootloader unlock and rooted on 4.4.2 but every time i turn off the phone and turn it back on root is gone and i would have to root again. if anyone can help me out it would be great. thanks in advance for any help

Did you use PIE root method?
Sent from my XT1060 using Tapatalk

i flash recovery twrp with moto toolkit the first time and it work but when i reboot i would lose root.then i try towelroot it would give me root again but if i reboot i would lose root. anyway to solve this would be great. thanks in advance

If you can boot into recovery (twrp) just flash the su zip, if you search the forums or Google you will find a link

You used a toolkit to flash recovery and root the phone? In the time it took to download and get the toolkit ready, you probably could have downloaded mfastboot, recovery, and a superuser zip and had all of them flashed and no issues.

i8rice said:
hope someone can help.i have a vzn dev ed thats bootloader unlock and rooted on 4.4.2 but every time i turn off the phone and turn it back on root is gone and i would have to root again. if anyone can help me out it would be great. thanks in advance for any help
Click to expand...
Click to collapse
If you are using a tool kit, I have to ask.. Have you visited Moto's web site, requested the unlock code for your phone, and actually used it (mfastboot oem unlock uniquecode)?
If you have a developer edtion, consider this... Don't use the tool kit, instead...
Install Android Platform Tools, ADB, mFastboot and the Moto drivers by following -> http://mark.cdmaforums.com/ADB.htm
Root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738 however, since it was written some time ago, get and use the newest TWRP from -> http://techerrata.com/browse/twrp2/ghost and get the newest SuperSU from -> http://download.chainfire.eu/supersu and copy it to the /SDCard in your phone (or just download it from the browser on your phone so its in /sdcard/download folder before you start)... Use these versions when following that process.
If you already got your unlock code from Moto's web site and used it, then you can skip step 1.
And step 5 should be started with the phone UNPLUGGED.

thanks for all the reply. i have it unlock by Moto's web site with the code.i have twrp 2711 and everything flash fine. i flash with the new su 2.0 in twrp2.7.1.1 it said flash successful but when it boots up i still have no root. i use rsd lite and flash Google Play Edition 4.4.2, by Q9Nap where the rom is already rooted. root work fine until i reboot i would lose root again.thanks in advance for any and all the help

i8rice said:
thanks for all the reply. i have it unlock by Moto's web site with the code.i have twrp 2711 and everything flash fine. i flash with the new su 2.0 in twrp2.7.1.1 it said flash successful but when it boots up i still have no root. i use rsd lite and flash Google Play Edition 4.4.2, by Q9Nap where the rom is already rooted. root work fine until i reboot i would lose root again.thanks in advance for any and all the help
Click to expand...
Click to collapse
Did you ever try to downgrade to 4.4 and use something like slapmymoto or MotoWpNoMo or something before?
Either way, based on the past seeing similar symptoms.. I would consider downloading the stock verizon 4.4.2 SBF and then follow Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html to get back to stock, then try TWRP and SuperSU again. (and yes there are a few lines/commands repeated there, that is intentional)

Heard of this another time....but can't find the thread. All signs for that person was bootloader unlocked and write protection still enabled.

[Q] Questions about root and OTA

Hello everyone, I'm new here, my nexus 6 is on stock 5.0.1 and waiting for update to 5.1, here are my concerns.
1. How can I root my phone without unlock boot loader or flash a twrp recovery( I Know if I got a twrp recovery, I can not get OTA).
2. If I need unlock boot loader in order to root, could this affect ota?
3. If I rooted my phone, can I get ota in the future?
Thanks.

Dennypalace said:
Hello everyone, I'm new here, my nexus 6 is on stock 5.0.1 and waiting for update to 5.1, here are my concerns.
1. How can I root my phone without unlock boot loader or flash a twrp recovery( I Know if I got a twrp recovery, I can not get OTA).
2. If I need unlock boot loader in order to root, could this affect ota?
3. If I rooted my phone, can I get ota in the future?
Thanks.
Click to expand...
Click to collapse
1. You can't 2. No can be unlocked and still do the ota 3. YES!

nms247 said:
1. You can't 2. No can be unlocked and still do the ota 3. YES!
Click to expand...
Click to collapse
Thanks. So this means if I want to root my phone, I will have to unlock boot loader. And is there anything I can do if I want to update through OTA after I rooted and unlocked my phone?

Dennypalace said:
Thanks. So this means if I want to root my phone, I will have to unlock boot loader. And is there anything I can do if I want to update through OTA after I rooted and unlocked my phone?
Click to expand...
Click to collapse
As long as you flash the stock recovery before an ota you'll be fine

Actually any system modification including root on Lollipop will prevent an OTA so in answer to question 3, no.

Basically need to flash stock system.img, recovery.img and stock boot (if you changed the kernel).
At least thats what I'm about to do.

y2whisper said:
Basically need to flash stock system.img, recovery.img and stock boot (if you changed the kernel).
At least thats what I'm about to do.
Click to expand...
Click to collapse
Correct. That's exactly what I did, and it worked.

rootSU said:
Actually any system modification including root on Lollipop will prevent an OTA so in answer to question 3, no.
Click to expand...
Click to collapse
Weird as I took the OTA while rooted.

Still working on it on my end. Drivers aren't installed for add sideboard trying to figure it out

[HELP] Moto X XT1058 AT&T fully bricked! I can't do anything!

So, as the title says, I had a Moto X XT1058 from AT&T.
I updated a long time ago to Lollipop and the phone worked perfectly fine until yesterday, when suddenly shutted down and when I restarted, got stuck on M logo.
I restarted to bootloader(?) pressing power off and vol down buttons.
The version that shows me is 30.BE
The device wasn't unlocked or rooted, because I was happy with the stock ROM, so it says Device is LOCKED ans Status Code 0.
I tried every option on this menu and everyone says (in red):
"No valid PIV block in SP for system
piv validation failed (system)
Boot up failed"
I tryed with abd, fastboot, mfastboot and RSDLite to flash gpt.bin and motoboot.img and every time I do it I get a error, and the operation fails.
For what I've read in tooooooo many posts, it's probably death, but I resist to this idea, so I came here to ask for advice.
THE PHONE IS NOT IN WARRANTY ANY MORE.
Thanks in advance and sorry for my english (not my native language).

why dont you try twrp recovery ?
just flash it

fadyrox said:
why dont you try twrp recovery ?
just flash it
Click to expand...
Click to collapse
Can I do it if my phone isn't rooted? The bootloader it's locked!

Flash full stock att 5.1 rom, it will be fine.

Salik Iqbal said:
Flash full stock att 5.1 rom, it will be fine.
Click to expand...
Click to collapse
Flashing via fastboot mode will be okay !
do search here you will get details !

fadyrox said:
Flashing via fastboot mode will be okay !
do search here you will get details !
Click to expand...
Click to collapse
But I never flashed any ROM on this phone. I got Lollipop from a OTA update. My phone was stock. Never rooted, never unlock bootloader. I didn't find any tutorial to do it with this characteristics.
And it's an AT&T xt1058

MatiCepe said:
But I never flashed any ROM on this phone. I got Lollipop from a OTA update. My phone was stock. Never rooted, never unlock bootloader. I didn't find any tutorial to do it with this characteristics.
And it's an AT&T xt1058
Click to expand...
Click to collapse
first you need to unlock your bootloader .. otherwise you wont be able to recover your device
Please do a search regarding unlocking bootloader !

fadyrox said:
first you need to unlock your bootloader .. otherwise you wont be able to recover your device
Please do a search regarding unlocking bootloader !
Click to expand...
Click to collapse
The bootloader of the XT1058 from AT&T is'nt unlockable.... That's the big trouble. I've read that it can be done if it's no 4.2.2, but not if the version is newer.

MatiCepe said:
The bootloader of the XT1058 from AT&T is'nt unlockable.... That's the big trouble. I've read that it can be done if it's no 4.2.2, but not if the version is newer.
Click to expand...
Click to collapse
Download rsd lite for windows, get latest stock rom for att, reboot your phone into fastboot, flash stock rom and you are done.

Salik Iqbal said:
Download rsd lite for windows, get latest stock rom for att, reboot your phone into fastboot, flash stock rom and you are done.
Click to expand...
Click to collapse
I searched and the lastone is ATT_XT1058_5.1.0_LPA23.12-21.7_cid1_CFC.xml.zip. I try to flash it on my phone via RSD and the process showsme this error:
Failed flashing process. 4/18 flash motoboot "motoboot.img" -> Phone returned FAIL.

MatiCepe said:
I searched and the lastone is ATT_XT1058_5.1.0_LPA23.12-21.7_cid1_CFC.xml.zip. I try to flash it on my phone via RSD and the process showsme this error:
Failed flashing process. 4/18 flash motoboot "motoboot.img" -> Phone returned FAIL.
Click to expand...
Click to collapse
Is your phone is charge enough? Search 5.1.1 att xml zip

can anybody give a solution for this problem because i am also with a xt1058 at&t, The device wasn't unlocked or rooted and the version that shows me is 30.BE too
sorry my english

What's up with your device any screen shot?

Hi, i have the same problem, my device is locked by AT&T and i cant flash the firmware< i have a unlock code from the AT&T company, how I can introdce that code manually? Thanks!

Thank you
H3c4rtr1 said:
Hi, i have the same problem, my device is locked by AT&T and i cant flash the firmware< i have a unlock code from the AT&T company, how I can introdce that code manually? Thanks!
Click to expand...
Click to collapse
You can help how you got the code, give details.
Thank you

Android pay no longer works after MM upgrade [unlocked bootloader, but not rooted]

Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/

phraxen said:
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Click to expand...
Click to collapse
Some of the CM-based ROMs floating around address this issue, but there is no way to use stock marshmallow with an unlocked bootloader and pass safetynet. So if you want android pay, your options are to stay on SU4TL-49 or install one of the CM-based ROMs that have implemented a workaround.
I got around this issue by using my credit card company's app instead of Android Pay. It allows me to do wireless payments everywhere Android Pay is accepted, but it only checks for root. It does not use safetynet.

Too late for you now, but recently someone in this forum updated to Marshmallow radio, but did NOT flash the Marshmallow bootloader. They were already using custom ROM. Others using that ROM who flashed Marshmallow bootloader no longer pass safetynet, but that person does. The conclusions is an unlocked Marshmallow bootloader or newer is what Safetynet looks for?
And yes, I've flashed both Marshmallow bootloader and radios over both my daily XT1225. I could only test the theory by breaking out my new-in-box third Quark, which have for emergency back-up -- and is which still probably on Kitkat.
While I previously had the older Google Wallet, Android Pay for me is not as important as controlling my own phone as I please. My phones will always be rooted. And in the Moto Quark, unlocking the bootloader is necessary for permanent root, whereas it's not necessary in some other phones -- like LG. But whatever needs to be done to root my phones, I will. And if Android Pay is not possible, so be it. I always carry my wallet when I go out somewhere. Pulling out my phone, pulling out my wallet, what's the difference?

phraxen said:
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Click to expand...
Click to collapse
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
fastboot erase cache
EDIT: Here is a flashable zip that will flash the bootloader for you for those who are so inclined. Make sure to wipe cache and dalvik/art cache in TWRP afterwards: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
EDIT 2: And here is the bootloader.img taken from the SU4TL-49 package if fastboot is your weapon of choice: https://mega.nz/#!iogRGIrQ!ixpZGw1cR90jLxe9r8EAt76SGNoSqVqSv1iu0v14QCc

TheSt33v said:
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
Remember to wipe cache afterwards.
Click to expand...
Click to collapse
I'm confused... isn't that downgrading the bootloader?

ChazzMatt said:
I'm confused... isn't that downgrading the bootloader?
Click to expand...
Click to collapse
Yes it is. And as long as your bootloader is unlocked, no harm no foul. I thought that downgrading the bootloader was the one thing that you couldn't do even if it was unlocked, but I just did it and I'm passing safetynet now, so I guess I was wrong.
If anyone wants proof I'm on the SU4TL-49 bootloader, I can take a picture when I get home. I don't know of a way to get a picture of the bootloader screen using only my phone.

TheSt33v said:
Yes it is. And as long as your bootloader is unlocked, no harm no foul. I thought that downgrading the bootloader was the one thing that you couldn't do even if it was unlocked, but I just did it and I'm passing safetynet now, so I guess I was wrong.
Click to expand...
Click to collapse
Learn something new everyday. Wow.
You just can't downgrade a locked bootloader, eh?
Thank you!
When I get home will try Lollipop bootloader on my XT1225.
The custom ROM guys will love this, then.

ChazzMatt said:
Learn something new everyday. Wow.
You just can't downgrade a locked bootloader, eh?
Thank you!
When I get home will try Lollipop bootloader on my XT1225.
The custom ROM guys will love this, then.
Click to expand...
Click to collapse
I seem to remember trying this a long time ago using TWRP, and TWRP was unable to flash the older bootloader. It works fine through fastboot though. I'm going to do some more investigation when I'm not at work to see if I can get TWRP to do this. That would be easier for most people.
Also, I thought the latest iSu already got around this issue. That's what BHB's command line patch thing is for. But it will certainly make things easier!

TheSt33v said:
I seem to remember trying this a long time ago using TWRP, and TWRP was unable to flash the older bootloader. It works fine through fastboot though. I'm going to do some more investigation when I'm not at work to see if I can get TWRP to do this. That would be easier for most people.
Also, I thought the latest iSu already got around this issue. That's what BHB's command line patch thing is for. But it will certainly make things easier!
Click to expand...
Click to collapse
I was on the latest bootloader and just flashed the .47 bootloader because of major radio issues. I flashed from TWRP and have been doing it since the .49 update.

gumbi2647 said:
I was on the latest bootloader and just flashed the .47 bootloader because of major radio issues. I flashed from TWRP and have been doing it since the .49 update.
Click to expand...
Click to collapse
Interesting. I've noticed that TWRP randomly has issues with flashing things on my phone for some reason, and a reboot often fixes the issue. Maybe I just got unlucky that one time, but if that's the case, I'll have a flashable SU4TL-49 bootloader up a few minutes after I get home.

TheSt33v said:
Interesting. I've noticed that TWRP randomly has issues with flashing things on my phone for some reason, and a reboot often fixes the issue. Maybe I just got unlucky that one time, but if that's the case, I'll have a flashable SU4TL-49 bootloader up a few minutes after I get home.
Click to expand...
Click to collapse
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?

ChazzMatt said:
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
Click to expand...
Click to collapse
ADB is not involved. Only fastboot.
The way I did it on my phone (XT1254 unrooted, unlocked, 100% stock MM) exactly was this:
1. Make note of BL version on bootloader screen.
2. fastboot flash motoboot bootloader.img using the SU4TL-49 bootloader.
3. Reboot bootloader
4. Confirm that the BL version has changed (it did)
5. Reboot to system.
6. Tried safetynet (failed)
7. Reboot to stock MM recovery menu
8. Wipe cache, reboot to system
9. Tried safetynet (passed), added a bunch of cards in Android Pay without issue
I'm assuming that wiping cache using other methods will be just as effective, but I don't know that for sure.

TheSt33v said:
ADB is not involved. Only fastboot.
The way I did it on my phone (unrooted, unlocked, 100% stock MM) exactly was this:
1. Make note of BL version on bootloader screen.
2. fastboot flash motoboot bootloader.img using the SU4TL-49 bootloader.
3. Reboot bootloader
4. Confirm that that BL version has changed (it did)
5. Reboot to system.
6. Tried safetynet (failed)
7. Reboot to stock MM recovery menu
8. Wipe cache, reboot to system
9. Test safetynet (passed)
I'm assuming that wiping cache using other methods will be just as effective, but I don't know that for sure.
Click to expand...
Click to collapse
Which version of TWRP are you using? I heard the 04 update has some issues. I have been on 03 forever.

gumbi2647 said:
Which version of TWRP are you using? I heard the 04 update has some issues. I have been on 03 forever.
Click to expand...
Click to collapse
04, so that could be it.

I post this around XDA, new bootloader add a new prop line
it add
[ro.boot.flash.locked]: [0]
And I patch that with this
https://www.androidfilehost.com/?fid=745425885120696423
with will change that to
[ro.boot.flash.locked]: [1]
Just use adb command
Code:
getprop | grep ro.boot.flash.locked
to check.
and then cts will not fail so is not really need to downgrade for now, There is the chance that Moto will change the boot.img so it can't boot on old bootloader, that did not happens yet on quark but others Moto device is need latest bootloader with latest ROM.
But then again may never be a update from Moto to this device.
So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
https://www.androidfilehost.com/?fid=745425885120696423
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.

TheSt33v said:
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
fastboot erase cache
Click to expand...
Click to collapse
Thanks for this. I'll give it a shot and let you know how it turns out.

bhb27;70506510So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
[url said:
https://www.androidfilehost.com/?fid=745425885120696423[/url]
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
Click to expand...
Click to collapse
Thanks! Flashing that works just fine. So now we have 2 options.

bhb27 said:
I post this around XDA, new bootloader add a new prop line
it add
[ro.boot.flash.locked]: [0]
And I patch that with this
https://www.androidfilehost.com/?fid=745425885120696423
with will change that to
[ro.boot.flash.locked]: [1]
Just use adb command
Code:
getprop | grep ro.boot.flash.locked
to check.
and then cts will not fail so is not really need to downgrade for now, There is the chance that Moto will change the boot.img so it can't boot on old bootloader, that did not happens yet on quark but others Moto device is need latest bootloader with latest ROM.
But then again may never be a update from Moto to this device.
So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
https://www.androidfilehost.com/?fid=745425885120696423
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
Click to expand...
Click to collapse
That worked for me. I was able to add a debit card without getting the error.
Thanks to you and TheSt33v.

ChazzMatt said:
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
Click to expand...
Click to collapse
Have you tried this using TWRP and if so did everything go well
Sent from my XT1254 using Tapatalk

joekitch said:
Have you tried this using TWRP and if so did everything go well
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I have not personally tried it yet. Someone else can answer if they have?

How to Root LG G6 H872 on Android Oreo

Hi everyone! I recently bought a LG G6 H872, which still has 10e installed. After crawling the forums for a bit, here's the sequence of things I wanted to do to it:
1.) Update to 8.0 Oreo via OTA.
2.) Unlock bootloader
3.) Root and TWRP using this: https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
4.) Magisk
Is the latest Oreo update the 20a version that is mentioned in the thread or should I manually update it to something older. I saw that there was anti-rollback so I don't want to update too far. Also, if there is ever another OTA, how does one update the rooted phone?
Edit: I wrote up some steps if it helps you on this post: https://forum.xda-developers.com/showpost.php?p=77513501&postcount=4

I do not believe there is currently a way to root the T-Mobile versions.

patruns said:
I do not believe there is currently a way to root the T-Mobile versions.
Click to expand...
Click to collapse
That is not correct, see: https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518

For future people who come across this thread, here are the steps I took to root this phone:
1.) Factory reset and then update device via OTA incrementally until 20a (which is Android Oreo 8.0)
2.) unlock bootloader: https://www.youtube.com/watch?v=EpaW0-8-QKY
3.) root device: https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
Note: there is a video tutorial here: https://www.youtube.com/watch?v=-z4CWLikPcI&t=821s. The first steps of flashing the laf partition are very useful to watch before attempting
4.) Factory reset in TWRP
5.) Reset after encryption error, then wipe with TWRP. May give mount error.
6.) Boot into Android Oreo. Device is not yet rooted at this point.
6.) Flash MAGISK via TWRP (SD card or ADB push) ]. Ignore the mount error. Reboot.
7.) Device is rooted! :good:

That's interesting
Without getting into an issue those steps look slightly different in order than the original process.
Or I'm a dumbass and somehow got it out of order. Seems ok now though.

Hello there!
I want to ask if it's the same to do the steps with 20e ?

Curious as well if this works with the latest update.

thendless said:
Curious as well if this works with the latest update.
Click to expand...
Click to collapse
This is an already rooted version of the latest update. I've downloaded but haven't flashed it yet, but the op is good and I've never had an issue with his work.
https://r.tapatalk.com/shareLink?ur...share_tid=3875515&share_fid=3793&share_type=t
Sent from my LG-H872 using Tapatalk

I succeeded in completing the process.
Permanent unlock from Tom via app.
Unlocked bootloader.
Twrp installed to recovery, can boot to recovery via low volume/power button combo.
Magisk installed.
20a working nicely.
I'm getting requests from Tmo to update from 20a to 20d. Is this recommended? Will twrp, root, unlock, etc. be lost?

I am glad to see that the bootloader gets unlocked easily. @alliance1975 how did you go from Unlocked bootloader step to Twrp installed step? That is the big one I think.
There is a good TWRP available, but we can't install it because the phone lacks fastboot commands. Is there a way to install TWRP? Or is it really that the only method is the rather risky runningnak3d method?

interestor said:
I am glad to see that the bootloader gets unlocked easily. @alliance1975 how did you go from Unlocked bootloader step to Twrp installed step? That is the big one I think.
There is a good TWRP available, but we can't install it because the phone lacks fastboot commands. Is there a way to install TWRP? Or is it really that the only method is the rather risky runningnak3d method?
Click to expand...
Click to collapse
I used the procedure summarized in step 3. I agree it is risky, well, the riskiest root & twrp I've ever tried. I neglected to say I only read instructions, the dev who actually came up with the plan deserves all the credit.

When I try to oem unlock nothing happens. What can I do? I have followed all other instructions.

Follow steps from this https://forum.xda-developers.com/tmobile-g6/how-to/unlock-bootloader-tmo-t3578099

Yeah I got my bootloader unlocked

alliance1975 said:
I succeeded in completing the process.
Permanent unlock from Tom via app.
Unlocked bootloader.
Twrp installed to recovery, can boot to recovery via low volume/power button combo.
Magisk installed.
20a working nicely.
I'm getting requests from Tmo to update from 20a to 20d. Is this recommended? Will twrp, root, unlock, etc. be lost?
Click to expand...
Click to collapse
Any info on this? Will updating from 20a mess up the phone (root, etc...)?