I have a Turbo with UDP and still have stock 4.4.4. I have the Sim card from my old RAZR Maxx in it that I trimmed down to the correct size (not sure if that makes a difference). I want to root for 3 main reasons - 1. WiFi hotspot. 2. Do away with some bloat. 3. Stop Ota screen that pops up every day.
I know the first thing I need to do is mofo root. I just want someone's suggestions who has already rooted. I still want a reliable phone without any weird glitches or something I constantly have to fool with. If I can stick with the 4.4.4 and just make those changes that would be OK with me. Or if someone knows a good smooth operating ROM to use please point me in the right direction. Thanks
Mofo is not the current root method... Sunshine is, and it's a better option overall. Also, if you're still on 4.4.4 you need to update to Lollipop to run Sunshine. I see no reason to stick to 4.4.4, either. I recommend catching up on the various threads about this, as they probably answer your questions, for the most part.
My personal choice is to stay with the stock ROM because I have heard of too many issues with Bluetooth and VoLTE on the CM-based ones. You could consider CF's ROM which is based on stock, if you want to move away from "stock".
EDIT: A few links to get you started:
http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
http://forum.xda-developers.com/droid-turbo/development/roms-t3347701
Forwarning - the latest OTA for SU4TL-49 will permalock (for now, at least) the bootloader, so DON'T apply that update - the first thread details that info as well.
Mofo Root/Kitkat 4.4.4 went out over 7 months ago (November 2015), when Sunshine team found an exploit for Snapdragon 805 devices and 5.1 Lollipop to unlock the bootloader.
With 5.1 and Sunshine you can have REAL root and TWRP custom recovery.
Just be very careful and do NOT update to SU4TL-49. That's the most recent update (pushed out in May 2016) where Verizon finally closed the Sunshine exploit.
There's a link in Development to flash SU4TL-44, which works with Sunshine.
Once your bootloader is unlocked, then you can update to SU4TL-49. It can't lock it back. It just prevents it from being unlocked.
Additonal Droid Turbo Root Info - XT1254 - QuarkSecurity Patch level 2016-04-01
Requirements; Unlocked Bootloader, Sunshine(Latest) SuperSU, TWRP Manager. Additional Suggested; Rom Manager(Helpful) Titanium Backup(Helpful) If you have updated to 23.21.49.quark_verizon.verizon.en.US vzw, (Tested only on this stock rom) and you do not have root, as long as you unlocked your bootloader, there is an EASY rooting method. I always reset first for testing, but you probably do not have to.......1: download and install Sunshine. Run Sunshine. When it gives you "temp root", minimize the app, (remember not to have any options set to kill when out of focus) download and install SuperSU, Set the following options in SuperSU, Enable Superuser, Default Access GRANTED, Enable SU DURING BOOT, Make sure Mount namespace seperation is checked, Turn OFF tapjacking protection, )can be re-enabled after process is finished, INSTALL SuperSU into /system, Trust System User, Enable PRO(Pseudo). Shut the phone Down. Restart. You have root. Now install TWRP manager, install the recovery suite, setup as you see fit. Optional, but useful, if you use a terminal as I do, install Sudo installer using the recovery install. Optional/ Titanium Backup is nice for people who play with roms, and root, etc....Rom manager is also very useful. Remember in most cases, if you have an option that does not specifically say DROID TURBO, or has the turbo hardware id, the DROID MAXX options usually work. Hope someone other than me has fun with this....:0) Remember, UNLOCK THE BOOTLOADER FIRST. This whole thing is mainly directed at the people who already unlocked the bootloader, and then upgraded somehow, and lost root.
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
this DOES work with SU4TL-49!
SXRXNRR said:
Requirements; Unlocked Bootloader, Sunshine(Latest) SuperSU, TWRP Manager. Additional Suggested; Rom Manager(Helpful) Titanium Backup(Helpful) If you have updated to 23.21.49.quark_verizon.verizon.en.US vzw, (Tested only on this stock rom) and you do not have root, as long as you unlocked your bootloader, there is an EASY rooting method. I always reset first for testing, but you probably do not have to.......1: download and install Sunshine. Run Sunshine. When it gives you "temp root",
This whole thing is mainly directed at the people who already unlocked the bootloader, and then upgraded somehow, and lost root.
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
this DOES work with SU4TL-49!
Click to expand...
Click to collapse
Uhmm... it does NOT work with SU4TL-49.
Lots of people have said even with unlocked bootloader, Sunshine no longer gives temp root with SU4TL-49 installed.
Read this thread:
Help Needed From XT 1254 Developers Please
http://forum.xda-developers.com/moto-maxx/help/help-xt-1254-developers-please-t3390557
It's specifically from an XT1254 user with an unlocked bootloader, who installed the OTA SU4TL-49 and no longer could get TEMP ROOT. Luckily, once we figured out he had an unlocked bootloader, he just had to install TWRP to get permanent root!
If you already have an unlocked bootloader, the best way is to get root is to go ahead and install TWRP and then root,
I don't understand the people who unlocked their bootloader prior to SU4TL-49 and did not then go ahead and permanently root their phones... But apparently they are out there. They were constantly using Sunshine temp root and now with SU4TL-49 that no longer works.
Worked on mine. Want pics?
It worked on mine. Want pics of it????
ChazzMatt said:
Uhmm... it does NOT work with SU4TL-49.
Lots of people have said even with unlocked bootloader, Sunshine no longer gives temp root with SU4TL-49 installed.
Read this thread:
Help Needed From XT 1254 Developers Please
http://forum.xda-developers.com/moto-maxx/help/help-xt-1254-developers-please-t3390557
It's specifically from an XT1254 user with an unlocked bootloader, who installed the OTA SU4TL-49 and no longer could get TEMP ROOT. Luckily, once we figured out he had an unlocked bootloader, he just had to install TWRP to get permanent root!
If you already have an unlocked bootloader, the best way is to get root is to go ahead and install TWRP and then root,
I don't understand the people who unlocked their bootloader prior to SU4TL-49 and did not then go ahead and permanently root their phones... But apparently they are out there. They were constantly using Sunshine temp root and now with SU4TL-49 that no longer works.
Click to expand...
Click to collapse
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
I did exactly as stated, it is perm root. I dont know why you would challenge that? Im sitting here with it? With sudo terminal, twrp, titanium root, etc....im not delusional dude.
ChazzMatt said:
Uhmm... it does NOT work with SU4TL-49.
Lots of people have said even with unlocked bootloader, Sunshine no longer gives temp root with SU4TL-49 installed.
Read this thread:
Help Needed From XT 1254 Developers Please
http://forum.xda-developers.com/moto-maxx/help/help-xt-1254-developers-please-t3390557
It's specifically from an XT1254 user with an unlocked bootloader, who installed the OTA SU4TL-49 and no longer could get TEMP ROOT. Luckily, once we figured out he had an unlocked bootloader, he just had to install TWRP to get permanent root!
If you already have an unlocked bootloader, the best way is to get root is to go ahead and install TWRP and then root,
I don't understand the people who unlocked their bootloader prior to SU4TL-49 and did not then go ahead and permanently root their phones... But apparently they are out there. They were constantly using Sunshine temp root and now with SU4TL-49 that no longer works.
Click to expand...
Click to collapse
---------- Post added at 03:54 PM ---------- Previous post was at 03:49 PM ----------
Seriously, I read these posts, and tried anyway. It worked. Isnt that what we are supposed to do? share our finds?
SXRXNRR said:
It worked on mine. Want pics of it????
Click to expand...
Click to collapse
Yes, I would like to see pics, considering that the developer of Sunshine (who is a professional security researcher) said himself that it would not work on SU4TL-49. That, along with the many, many reports of people saying that it does not work on SU4TL-49, cause reason for suspicion.
And yes, XDA is for sharing findings, but only if those findings are valid and do not lead to other people doing things that they will regret based on bad advice.
SXRXNRR said:
It worked on mine. Want pics of it????
I did exactly as stated, it is perm root. I dont know why you would challenge that? Im sitting here with it? With sudo terminal, twrp, titanium root, etc....im not delusional dude.
Seriously, I read these posts, and tried anyway. It worked. Isnt that what we are supposed to do? share our finds?
Click to expand...
Click to collapse
OF course you have TWRP, because you installed TWRP with an unlocked bootloader. But you probably didn't get temp root with SU4TL-49 first. You got root from TWRP.
All I'm questioning is getting temp root first with SU4TL-49 installed -- on an XT1254 with unocked bootloader which had previously never had TWRP or other permanent root before that.
If you got managed to get temp root first with SU4TL-49 first (and had never installed TWRP or rooted before), you must have a magical phone. @jcase would be very interested.
What would you show me pics of? You've already installed TWRP and rooted -- which can be easily be done with an unlocked bootloader and TWRP. Showing us pictures of that doesn't show us anything.
If you have an XT1254 with an unlocked bootloader and no root, the best way is to go ahead and install TWRP custom recovery and root. (You can only unlock your bootloader with Sunshine prior to instaling SU4TL-49.)
I dont need kudos from anybody. I shared because I did it. On a factory reset turbo, that was updated. I dont care if you dont believe either. makes no difference to me. Obviously posting here is grounds for attack. I was simply sharing, It worked. Consider the conversation closed. I wont be sharing anything here. TWRP was installed AFTER the temp root. Running sunshine and seeing TEMP root achieved, I installed SuperSU as stated, then TWRP manager, etc...Im a 45 year old security geek. I take offense with your attitude. I wouldnt post it if the steps didnt work. Thanks for the friendly atmosphere. Really. Maybe I do have a magical phone. WTFK?
ChazzMatt said:
OF course you have TWRP, because you installed TWRP with an unlocked bootloader. But you probably didn't get temp root with SU4TL-49 first. You got root from TWRP.
If you got temp root from SU4TL-49 first, you must have a magical phone. @jcase would be very interested.
What would you show me pics of? You've already rooted your phone and installed TWRP, which can be easily be done with an unlocked bootloader and TWRP. Showing us pictures of that doesn't show us anything.
All I'm questioning is getting temp root first with SU4TL-49 installed -- with no TWRP or other permanent root before that. If you have an unlocked bootloader, the best way is to go ahead and install TWRP and root. At that point, you had already unlocked your bootloader prior to SU4TL-49.
Click to expand...
Click to collapse
He probably has the su44 bootloaders
SXRXNRR said:
I dont need kudos from anybody. I shared because I did it. On a factory reset turbo, that was updated. I dont care if you dont believe either. makes no difference to me. Obviously posting here is grounds for attack. I was simply sharing, It worked. Consider the conversation closed. I wont be sharing anything here. TWRP was installed AFTER the temp root. Running sunshine and seeing TEMP root achieved, I installed SuperSU as stated, then TWRP manager, etc...Im a 45 year old security geek. I take offense with your attitude. I wouldnt post it if the steps didnt work. Thanks for the friendly atmosphere. Really. Maybe I do have a magical phone. WTFK?
Click to expand...
Click to collapse
See the previous post above from Sunshine dev. The "magical" part is you are somehow the exception if you had an unlocked bootloader, no permanent root, and installed the OTA. It won't work for most other people. Somehow you installed SU4TL-49 update but not the bootloader that goes with it. You must still have the SU4TL-44 bootloader.
Now that you are telling more details "On a factory reset turbo,", it's becoming clear you had root, TWRP installed before. What you are doing has been described in detail before in the thread (from May) I'm quoting below. It's nothing new, nothing fantastic.
But what you seemed to be describing at first was using Sunshine to get temp root when you never had permanent root before (and I wasn't the only one who thought so) . That scenario is impossible.
Posting here is not grounds for attack. We just don't believe you did something no one else has been able to do, without explaining why you were able to do it. Especially when there's no proof at each step, but an easy alternative explanation (TWRP, then root) if you really installed the complete SU4TL-49 update. There's been many, many people including myself who have done stuff, then said, "I'm not sure the exact steps I did to get here." With only 1 post prior to this, we have to question your seeming amazing story.
Now that you have added more details, all you did was re-flash TWRP on an unlocked bootloader phone that already had root and TWRP previously. That's been described since May, see thread quote below. It's for people who previously had root, re-set their phone to install the update. Then afterwards, yes, you can get temp root back with Sunshine. But the important part is at some point you already have permanent root prior to installing the OTA. See steps 11-16, as well as the trouble shooting.
New OTA Available for Droid Turbo
http://forum.xda-developers.com/droid-turbo/general/ota-available-droid-turbo-t3378576
TheSt33v said:
DO NOT UPDATE IF YOUR BOOTLOADER IS LOCKED AND YOU WANT TO UNLOCK IT AT SOME POINT
DO NOT UPDATE IF YOUR BOOTLOADER IS LOCKED AND YOU WANT TO UNLOCK IT AT SOME POINT
DO NOT UPDATE IF YOUR BOOTLOADER IS LOCKED AND YOU WANT TO UNLOCK IT AT SOME POINT
Small update to build SU4TL-49. Not Marshmallow. Claims "security patches and improved network performance."
How to Update with an Unlocked Bootloader
The update will only work if you have a 100% unmodified stock rom and recovery menu. If you're on CF's rom and you want to update to the latest version of that, see his page for details on how to do that.
1. Backup all data. Just in case. Definitely do this if you're coming from CM13 or RR. I don't remember if the OTA wipes your data or not.
2. Download this SU4TL-44 100% stock flashable zip here: http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
3. Download the SU4TL-44 stock recovery menu here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8
4. Boot into TWRP.
5. Flash the file you downloaded in step 2 by selecting Install and browsing to the file.
6. In TWRP, select Install, followed by install image, and select the recovery image that you downloaded in step 3. Tell it to flash it to recovery, and flash it.
7. If you're coming from CM13 or RR, do a factory reset in TWRP. If you're coming from a modified stock rom, I still recommend this, but it's not mandatory.
8. Reboot to recovery to confirm that you see the stock recovery menu (a dead android with the words "no command").
9. Boot the phone normally. If TWRP offers to install SuperSU, say no.
10. The OTA update should appear. Take it and let it do its thing.
You now have a 100% stock, bootloader still unlocked, SU4TL-49 phone. If you want TWRP back so you can start flashing stuff again, keep reading.
11. Download and install Sunshine from here: http://theroot.ninja/
12. Download your preferred version of TWRP. The current stable version is here: https://dl.twrp.me/quark/. If you want baybutcher27's modded version that includes lots of handy additional features, you can get that here: http://forum.xda-developers.com/showpost.php?p=66877208&postcount=116
13. Download Flashify from the play store.
14. Open Sunshine and follow the instructions until it gains temp root. Disregard the message that says it isn't compatible with SU4TL-49.
15. Open Flashify, select Recovery Image, then browse to the version of TWRP that you downloaded in step 11. Flash it.
16. Reboot to recovery. You should see TWRP's lovely smiling face staring back at you.
How to Install the SU4TL-49 Modem Only
1. [HIGHLY RECOMMENDED] Flash the modded TWRP I mentioned earlier, select backup, backup only your modem.
2. Flash Computerfreek274's modem package that you can get here: https://www.androidfilehost.com/?fid=24545070682210570
3. If you have GPS or other modem-related issues, try flashing this to fix them: https://www.androidfilehost.com/?fid=24531035584725320
4. If you decide you don't like the new modem, restore the backup you made in step 1.
Troubleshooting
Issue: You followed all of the steps, but you still get an error when you try to take the OTA.
Solution: Backup your data and perform a factory reset using the stock recovery menu. You can do this by rebooting to recovery like you do when you want to boot TWRP, and when you see the "no command" screen, hold the power button and press volume up. Then select factory reset and do it.
Click to expand...
Click to collapse
TheSt33v said:
Yes, I would like to see pics, considering that the developer of Sunshine (who is a professional security researcher) said himself that it would not work on SU4TL-49. That, along with the many, many reports of people saying that it does not work on SU4TL-49, cause reason for suspicion.
And yes, XDA is for sharing findings, but only if those findings are valid and do not lead to other people doing things that they will regret based on bad advice.
Click to expand...
Click to collapse
Just like in your thread I quoted, it's clear now he had root, TWRP installed prior to a factory re-set to install SU4TL-49. He didn't initially disclose it was a factory re-set, and that he had previous permanent root and TWRP.
Perhaps unintentionally, he made it seem he only had unlocked bootloader and had been using Sunshine to get temp root. At least that's how I read it. Now with SU4TL-49, temp root will no longer works in that scenario. But if you've already gotten permanent root, TWRP and install the update -- even with a factory re-set -- you've made enough changes that Sunshine will still work to give you temp root.
At that point, yes Sunshine will still give you temp root -- just like you posted in your thread. To me, and it's my opinion only it seems your steps, downloading TWRP from Quark thread, using Flashify would seem simpler. You have TWRP and then can use TWRP to get root.
Once we know all the facts, his experience is not fantastic and if he had just read your thread we could have skipped the drama.
ChazzMatt said:
Just like in your thread I quoted, it's clear now he had root, TWRP installed prior to a factory re-set to install SU4TL-49. He didn't initially disclose it was a factory re-set, and that he had previous permanent root and TWRP.
Perhaps unintentionally, he made it seem he only had unlocked bootloader and had been using Sunshine to get temp root. At least that's how I read it. Now with SU4TL-49, temp root will no longer works in that scenario. But if you've already gotten permanent root, TWRP and install the update -- even with a factory re-set -- you've made enough changes that Sunshine will still work to give you temp root.
At that point, yes Sunshine will still give you temp root -- just like you posted in your thread. To me, and it's my opinion only it seems your steps, downloading TWRP from Quark thread, using Flashify would seem simpler. You have TWRP and then can use TWRP to get root.
Once we know all the facts, his experience is not fantastic and if he had just read your thread we could have skipped the drama.
Click to expand...
Click to collapse
Oops
Related
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
vespadaddy said:
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
Click to expand...
Click to collapse
use fastboot to flash stock recovery on your phone, undo the tethering hack, and take the OTA.
Since you have a Dev Edition with unlocked bootloader, Root and Write Protection Disable survive. You can leave stock recovery on there, unless you really need the features of TWRP like backup, etc. Then you just have to do any NEW hacks for tethering (for 4.4.2 its different than 4.4). Or you can use wifi tether for root app instead of hacks.
There was talk about repackaging the OTA to be installed via TWRP or CWM, but I don't recall the thread containing an actual zip, and think they were mostly talking about what needs to be done. Since its easy enough with the Dev Edition to update, its likely not worth the work repacking it, since it wont work for those with LOCKED bootloaders.
vespadaddy said:
Hello,
I searched for the answer and didn't find it so... I need to upgrade OS on my phone to the latest OTA.
I have a VZW Dev. ed. MotoX, unlocked, rooted, running TWRP. It is stock, aside from the tethering hack.
Given that I managed to unlock, root and install TWRP, I'm sure I could manage it again, if I have to install a stock recovery again (yuck), but I;m hoping there may be an easier way, perhaps one that involves simply clicking a link on my phone or some such similar. I recall with the GNex, these usually popped up shortly after the OTA became available. Is something similar for the MotoX likely to show up, or is our community just too small?
Is there a 1 click upgrade yet? Is there likely to be one, or do I need to roll up my sleeves with this device and revert to stock, apply OTA, then re-install TWRP and root? What a PITA. What's the easiest way?
Thanks!
Click to expand...
Click to collapse
I pretty much did what was described below and maintained TWRP and root. Note: you must enter TWRP and exit after the update to reinstall SU.
http://forum.xda-developers.com/showpost.php?p=50639372&postcount=25
except I chose not to flash the following...
fastboot flash logo logo.bin
fastboot erase customize
fastboot erase clogo
Whether it makes sense or not my goal is to not "upgrade" my bootloader or GPT until absolutely necessary as they can't be downgraded. The risks associated with doing this are hotly debated so understand what you are getting into if you choose to do this to your phone.
Reverted thether hack.
Recovery tool worked for me on moto x dev. flashed stock recovery. Took ota 442. Flashed twrp. kept root and stuff. no need for a computer.
http://forum.xda-developers.com/showthread.php?t=2334554
Title pretty much sums it all. I've an XT1058 with unlocked bootloader running stock rooted Kitkat 4.4. I want to update to stock 4.4.2 to try and use the new screen mirroring feature with my Chromecast (AFAIK, I need to be at least on 4.4.1, right?). Is there a way not to lose the unlocked bootloader and/or the root when I flash the update?
Similar question: Do I have to go back to stock (i.e., unrooted, locked) before I flash 4.4.2, or can I flash it over my current stock ROM?
Thank you all in advance.
Deivid85 said:
Title pretty much sums it all. I've an XT1058 with unlocked bootloader running stock rooted Kitkat 4.4. I want to update to stock 4.4.2 to try and use the new screen mirroring feature with my Chromecast (AFAIK, I need to be at least on 4.4.1, right?). Is there a way not to lose the unlocked bootloader and/or the root when I flash the update?
Similar question: Do I have to go back to stock (i.e., unrooted, locked) before I flash 4.4.2, or can I flash it over my current stock ROM?
Thank you all in advance.
Click to expand...
Click to collapse
If you have unlocked the bootloader, there is no fear of "losing" it. Bootloader unlocking is permanent, so even if root is lost, you can simply re-flash TWRP and re-root. Disclaimer: I'm sure you do know the difference between unlocking the bootloader (permanent), and using one of the write-protect-disable exploits (like MotoWpNoMo - which is NOT permanent and would be lost if upgraded to 4.4.2), but I wanted to point this out just in case. If you are indeed bootloader-unlocked, you will have a "WARNING BOOTLOADER UNLOCKED" screen appear upon boot. Again, I apologize if this is redundant...
If you want to take the OTA to 4.4.2, you would need to flash back stock recovery, un-do any mods you have made to /system, and disable Xposed (if installed). This could be complicated if you aren't sure what mods you may or may not have made...
There is no 4.4.1 for the Moto X - we skipped straight from 4.4 to 4.4.2. I'm not sure which version was the first to support Chromecast, however.
It would be easiest to "go back to stock" rather than trying to figure out how to un-do any modifications you may or may not have made. Additionally, it is preferable to flash the entire stock 4.4.2 SBF (which will erase ALL of your data - backup anything you need first), rather than trying to retain the userdata and just flash /system. Issues can arise if you try to retain your userdata.
My advice (for what its worth) is to follow the instructions in the Return to Stock thread to flash the ENTIRE STOCK 4.4.2 SBF for YOUR carrier. This will return you to 100% stock with no root. You WILL retain your unlocked bootloader so afterwards, you can simply flash TWRP, and re-root your phone.
By going this route, you minimize any potential problems that might arise by trying to take the OTA, or by flashing the SBF without erasing userdata.
If you have any questions or need clarification, let me know.
Good Luck
samwathegreat said:
If you have unlocked the bootloader, there is no fear of "losing" it. Bootloader unlocking is permanent, so even if root is lost, you can simply re-flash TWRP and re-root. Disclaimer: I'm sure you do know the difference between unlocking the bootloader (permanent), and using one of the write-protect-disable exploits (like MotoWpNoMo - which is NOT permanent and would be lost if upgraded to 4.4.2), but I wanted to point this out just in case. If you are indeed bootloader-unlocked, you will have a "WARNING BOOTLOADER UNLOCKED" screen appear upon boot. Again, I apologize if this is redundant...
If you want to take the OTA to 4.4.2, you would need to flash back stock recovery, un-do any mods you have made to /system, and disable Xposed (if installed). This could be complicated if you aren't sure what mods you may or may not have made...
There is no 4.4.1 for the Moto X - we skipped straight from 4.4 to 4.4.2. I'm not sure which version was the first to support Chromecast, however.
It would be easiest to "go back to stock" rather than trying to figure out how to un-do any modifications you may or may not have made. Additionally, it is preferable to flash the entire stock 4.4.2 SBF (which will erase ALL of your data - backup anything you need first), rather than trying to retain the userdata and just flash /system. Issues can arise if you try to retain your userdata.
My advice (for what its worth) is to follow the instructions in the Return to Stock thread to flash the ENTIRE STOCK 4.4.2 SBF for YOUR carrier. This will return you to 100% stock with no root. You WILL retain your unlocked bootloader so afterwards, you can simply flash TWRP, and re-root your phone.
By going this route, you minimize any potential problems that might arise by trying to take the OTA, or by flashing the SBF without erasing userdata.
If you have any questions or need clarification, let me know.
Good Luck
Click to expand...
Click to collapse
Thank you very much for the thorough and detalied reply! I'll follow your advice and report back.
Also, as a follow up question (actually, more like checking I got your reply right): Given that I do have the bootloader permanently unlocked, all I need to root 4.4.2 is flashing back TWRP and hit the root option? (I know you said exactly that, but I got lost after reading al the PIE tethered root threads, so just wanted to make sure that is for locked bootloaders, and not my case).
Thanks again!
Deivid85 said:
Thank you very much for the thorough and detalied reply! I'll follow your advice and report back.
Also, as a follow up question (actually, more like checking I got your reply right): Given that I do have the bootloader permanently unlocked, all I need to root 4.4.2 is flashing back TWRP and hit the root option? (I know you said exactly that, but I got lost after reading al the PIE tethered root threads, so just wanted to make sure that is for locked bootloaders, and not my case).
Thanks again!
Click to expand...
Click to collapse
You are correct. Nothing in the PIE thread is relevant to us with unlocked bootloaders.
Worked like a charm!
I actually in the same situations as the OP, EXCEPT my bootloader is locked and I used a couple of jcase's methods to get my root, so no TWRP. Would the same instructions still apply? What would be the best way to backup things?
NameLessThugZero said:
I actually in the same situations as the OP, EXCEPT my bootloader is locked and I used a couple of jcase's methods to get my root, so no TWRP. Would the same instructions still apply? What would be the best way to backup things?
Click to expand...
Click to collapse
Actually, nothing about your situation is similar to the OPs since you don't have unlocked bootloader....or do you mean the situation is similar in that you want to be able to use chromecast?
Regardless, nothing in this thread is relevant to you. The 4.4.2 bootloader is impervious to any known write-protect-disable exploits, so if you DO update to 4.4.2 you will PERMANENTLY lose write-protect. The only option once on 4.4.2+ is to use tethered root such as PIE, which does not disable write protect, does not allow writing to /system, and any and all changes are lost upon reboot. You must then re-connect to PC, and re-run the exploit to gain root again.....not very pretty....
The ONLY option for you (besides bootloader unlock) if you want to retain write-protect-disable and persistent Root, is to follow the advice in this thread: http://forum.xda-developers.com/moto-x/moto-x-qa/upgrade-4-4-root-t2822191
And heed the warnings!!! One simple / innocent mistake will result in either a brick, or PERMANENT loss of write-protect-disable. Take extreme caution.
Good Luck
samwathegreat said:
Actually, nothing about your situation is similar to the OPs since you don't have unlocked bootloader....or do you mean the situation is similar in that you want to be able to use chromecast?
Regardless, nothing in this thread is relevant to you. The 4.4.2 bootloader is impervious to any known write-protect-disable exploits, so if you DO update to 4.4.2 you will PERMANENTLY lose write-protect. The only option once on 4.4.2+ is to use tethered root such as PIE, which does not disable write protect, does not allow writing to /system, and any and all changes are lost upon reboot. You must then re-connect to PC, and re-run the exploit to gain root again.....not very pretty....
The ONLY option for you (besides bootloader unlock) if you want to retain write-protect-disable and persistent Root, is to follow the advice in this thread: http://forum.xda-developers.com/moto-x/moto-x-qa/upgrade-4-4-root-t2822191
And heed the warnings!!! One simple / innocent mistake will result in either a brick, or PERMANENT loss of write-protect-disable. Take extreme caution.
Good Luck
Click to expand...
Click to collapse
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
NameLessThugZero said:
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
Click to expand...
Click to collapse
Sure! If you don't mind losing write-protect-disable forever, and having to re-root each time you reboot, go for it! I highly suggest you follow the instructions in the "Return to Stock" thread (in general sub-forum) to flash the entire 4.4.2 SBF for YOUR carrier. This will give you bone-stock 4.4.2, and will erase everything. Back up anything important first. Then you can follow the instructions in the PIE thread.
The suggested method is highlighted in red in your post above. You CANNOT use the method listed in THIS thread, because you cannot flash custom recovery unless you have unlocked bootloader.
I -think- PIE will work with Titanium Backup (confirm that first), so you can probably back-up anything that you can't just re-install from the play store and restore it afterwards. Copy everything you want to keep from the internal storage (pictures, etc.), because they will be erased as well.
That's pretty much it. I don't think you've missed anything, but keep in mind that bootloader unlock (and the 4.4 exploits) are both far superior to PIE as far as usability and persistence. You'll have to try and reboot as seldom as possible.
Good Luck!!! :good:
EDIT: Keep in mind also that once you update to 4.4.4, PIE will NOT WORK, and you will LOSE ROOT FOREVER (unless another exploit is released, which is unlikely at best).
samwathegreat said:
Sure! If you don't mind losing write-protect-disable forever, and having to re-root each time you reboot, go for it! I highly suggest you follow the instructions in the "Return to Stock" thread (in general sub-forum) to flash the entire 4.4.2 SBF for YOUR carrier. This will give you bone-stock 4.4.2, and will erase everything. Back up anything important first. Then you can follow the instructions in the PIE thread.
The suggested method is highlighted in red in your post above. You CANNOT use the method listed in THIS thread, because you cannot flash custom recovery unless you have unlocked bootloader.
I -think- PIE will work with Titanium Backup (confirm that first), so you can probably back-up anything that you can't just re-install from the play store and restore it afterwards. Copy everything you want to keep from the internal storage (pictures, etc.), because they will be erased as well.
That's pretty much it. I don't think you've missed anything, but keep in mind that bootloader unlock (and the 4.4 exploits) are both far superior to PIE as far as usability and persistence. You'll have to try and reboot as seldom as possible.
Good Luck!!! :good:
EDIT: Keep in mind also that once you update to 4.4.4, PIE will NOT WORK, and you will LOSE ROOT FOREVER (unless another exploit is released, which is unlikely at best).
Click to expand...
Click to collapse
Sweet, thanks for your help. Ill check on the TB thing. Ill update if I need any other help.
NameLessThugZero said:
I guess I was trying to be too concise, sorry. I know I dont want to go the safestrap route because of time and complexity, nor do I want to do anything with chromecast(which I forgot was mentioned, my bad). I did however plan to use PIE as soon as I heard about it. The route I was simply going to take was just to flash stock 4.4.2 SBF, then apply PIE( which I know isnt permanent after a hard reboot) since I knew that would be to safest way to get root without screwing up stuff. That said, cant this method work just as well? And sure I have to worry about getting SuperUser Xposed up and running again, which I believe has been posted about already, in the comments. But i think that would be all unless Im missing something else.
Click to expand...
Click to collapse
Keep in mind, that PIE itself isn't as good of root as using SlapMyMoto & MotoWpNoMo together.
On the X there are two parts needed for effective Root. 1. Root Exploit, and 2. Write Protection Dis-abler.
PIE is a root Exploit. It exploits a vulnerability to grant root access. It does not address Write Protection.
Write Protection on the X prevents proper access to /system or the like. Some apps wont be able to create new files in the protected folders, and any changes made to existing files (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on. This is also why PIE root is lost at power off/on.
In the past (4.4 and below days) SlapMyMoto was the Root Exploit, and MotoWpNoMo was the write protection dis-abler. Once thought to be permanent, the exploit used by MotoWpNoMo was plugged in 4.4.2 making it not work. Write protection becomes re-enabled, and there is no new exploit to disable it.
Why do I mention this? In reading the various threads, especially the Pie thread, there appear to be special instructions to install XPosed when write protection is enabled that you'll need to keep in mind, as well as info on how to re-root and get Xposed working again if you do power off/on. Because write protection is enabled, there are some apps and hacks that may not work. Some of the Tethering tricks for example.
Unlocking the bootloader gets around this. Once you unlock the bootloader, you can always install a custom recovery (like TWRP) and root from there. In the process, write protection becomes disabled. There is no need to wait on a vulnerability in the code to be exploited to gain root and disable write protection.
Hi there, I have a UK moto x model xt1052. I am looking to root and flash custom ROMs onto my device, but am concerned that I will brick the device by using a method intended for a different model of moto x.
The UK moto x was shipped with android 4.4.2, later updated to 4.4.4 so there are no earlier builds of android to downgrade to.
Any help will be appreciated.
Timsteels
Figure out if you can, and want to unlock your bootloader.... Then go to the One Stop Shop root thread sticky at the top of the general section. It has all your options.
---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------
And root methods have nothing to do with your model. It mostly has to do with locked or unlocked bootloader state.
timsteels said:
Hi there, I have a UK moto x model xt1052. I am looking to root and flash custom ROMs onto my device, but am concerned that I will brick the device by using a method intended for a different model of moto x.
Click to expand...
Click to collapse
Process to root the X is the same whether you have an XT1052, XT1053, XT1056, XT1060, etc. As KJ said, with 4.4.4 its all about can you unlock your bootloader or not. (and do you mind voiding your warranty doing so since you don't have a Developer Edition X).
See the One Stop Shop thread, in particular this post -> http://forum.xda-developers.com/mot...-confusion-t2826159/post54671918#post54671918
timsteels said:
The UK moto x was shipped with android 4.4.2, later updated to 4.4.4 so there are no earlier builds of android to downgrade to.
Click to expand...
Click to collapse
And you do NOT WANT TO DOWNGRADE!!!!! Doing so you will risk bricking your phone now, or when you later take an OTA. There are many warnings posted in the forums to not downgrade, and many threads started by those who have ignored the warnings and tried to downgrade and have bricked their phones!!!
Besides that, two key parts, GPT.Bin (partition table), and Motoboot.img (contains bootloader, TZ and a few other parts) will NOT downgrade successfully once on 4.4.2, 4.4.3 or 4.4.4. so any past exploits requiring the older roms wont work anyway.
So unlocking the boot loader is the same process as the us variants of the moto x? I just don't want to turn my phone into a paperweight! I'm not too worried about the warranty, as I am usually careful with my phones.
Unlocking and recovery and ROOT is all the same on any X. What matters is Android version (cause locked 4.4.4 guys can't root in any way), locked or unlocked bootloader and that's about it.
An unlocked X is the same no matter a Dev Edition or any other. All the same.
As far as bricking... The only time that's a giant threat is trying to downgrade. Not saying an X has never been bricked another way, cause everything we do has some risk to it. But most issues are curable.
Ok thanks for the info! And in terms of custom roms, do I need to install one built for the xt1052, or will other ones also work?
That is not something I know about. Never flashed one. Just stock and gravity box.
Read the opening post of rom threads, should have what devices it's for. ?
Ok thanks again! Is there much point in installing the exposed framework or anything similar?
I think many rooted X members here use Gravity Box while on stock rom... So they can customize some things. ?
Ok cool. I will have a look and decide if I want to go ahead. Thanks for all the assistance
timsteels said:
Ok thanks again! Is there much point in installing the exposed framework or anything similar?
Click to expand...
Click to collapse
Many root, install Xposed and some modules to customize their phone rather than running any Custom Roms because the custom roms often lose the Moto features like the notifications and such.
Ok and if I root, unlock bootloader and install xposed, will my phone still receive the ota updates? Or is it a case of reversing the procedure to get the ota updates?
timsteels said:
Ok and if I root, unlock bootloader and install xposed, will my phone still receive the ota updates? Or is it a case of reversing the procedure to get the ota updates?
Click to expand...
Click to collapse
First you can't install an OTA with a custom recovery (like TWRP, CWM, Philz) on the phone. You'll get stuck in a boot loop.
Next, in every OTA there is a "pre-validation check" (a manifest file which contains a list of items to be checked and a SHA type hash code for a type of check sum verification of each part/file its looking at.)
Anything that alters your phone from what the Pre-Validation check is looking for will cause the OTA to fail. So if you modify or remove and system files, have the wrong recovery, etc., those parts would not pass the pre-validation check so the OTA would fail.
Xposed also needs to be disabled, or it will cause the OTA's pre-validation checks to fail.
So it really comes down to what you do after you root.
If you flash TWRP, Root, install Xposed and a few modules, and nothing else, then to take an OTA, you'll need to disable Xposed (there is a flashable zip on your /SDcard to do this), then flash stock recovery.img back on your phone, then you can take the OTA. Once the OTA is successfully installed, you can re-flash custom recovery, re-root if necessary, and re-enable Xposed.
If you rename/delete/modify files from /system (like some do to get rid of bloat), you'll need to un-do that.
If you're like me, I just unlocked, rooted, and installed apps that use root (like Root Explorer, Greenify, Wifi Tether for root), so all I do is flash stock recovery on, take the OTA, and if I lost root, flash TWRP and re-root.
For more see -> http://mark.cdmaforums.com/MotoX-OTA.html
Ok that's good to know. I'll have a think about it. I may wait until lollipop comes out for the moto x.
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
You'll have to unlock the bootloader. No way around it.
Should I be nervous about unlocking the bootloader?
Didn't my Samsung phone come with it already unlocked?
Should you be nervous? Google the pros and cons then decide for yourself.
No phone nor tablet comes with an unlocked bootloader.
I have an XT1053 and just recently unlocked the bootloader through the Motorola site. I waited until now because my original warranty just expired and knew that unlocking the bootloader would void my warranty. I wanted to unlock the bootloader under 4.4.4 because I didn't know if there would be any problems once Lollipop was offered as an update. The unlock process went very smoothly and took only a few minutes. You probably already know that unlocking wipes your phone, so be prepared to reinstall apps and other files. I have not rooted yet because I'll probably wait to do that after the Lollipop OTA comes around. Even then, I may not root because I'm really pretty happy with the phone as it is. For me, unlocking the bootloader was just of way of preserving the future option to root.
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
mac1996 said:
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
Do you have fastboot?
if yes, go to your phone bootloader.
Connect to your computer by USB.
Type the following in cmd. (place your recovery img file in fastboot directory)
fastboot flash recovery (your recovery name).img
Sent from my XT1053 using XDA Free mobile app
Check the sticky threads. There's only a year and halfs worth of information available to you here and all over the rest of the internet.
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
At any point after unlocking the bootloader... To flash recovery, did you do the following...
Start the phone in Fastboot/Bootloader mode.. then from the PC type...
mfastboot flash recovery YourRecovery.img
mfastboot reboot-bootloader
Follow onscreen directions to use vol down key and highlight recovery, then use vol up to select/enter recovery. Once in recovery you can reboot the phone and proceed with whatever you want.
Failure to reboot-bootloader and entering recovery immediately after flashing recovery (i.e. doing something else first) can result in the recovery not sticking.
4.4.4
a year old post by dray_jr says the following:
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
can someone explain this to me? I got my phone around august 2014, it came with 4.4.3 and right now I'm on 4.4.4.
If I use the motorola website and follow their bootloader unlock steps am I fine? will I have any brick issues stated from the quote above?
Thread
Nevermind guys, found the perfect thread for 4.4.4 root!
Thread: http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Final question: I don't have to install supersu root if i install CM12 once i get into TWRP recovery am i correct? (since cms come rooted)
Would flashing a JB kernel (and only the kernel) work to root it as described here?: http://forum.xda-developers.com/crossdevice-dev/sony/guide-xperia-kitkat-4-4-4-rooting-t3003520
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
nhizzat said:
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
Click to expand...
Click to collapse
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
dagoban said:
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
Click to expand...
Click to collapse
I don't proclaim to know the ins and outs of all things android, but I do know this.. Just because a phone has android 4.4.4 doesn't mean its the same 4.4.4 with the same exact flaws and vulnerabilities, susceptible to the same exact root processes. Its why an exploit to root one phone, often doesn't work to root another.
In the case of the Moto X with a locked bootloader, JCASE has come out with many processes exploiting vulnerabilities for Android and the Apps on the Moto X to not only root it, but disable its write protection. As new OTA's have patched an exploit, he came out with other ways.
Starting wth 4.4.2, the vulnerability in the bootoader to disable write protection has been patched.
Jcase's Sunshine tool works on the X with 4.4.3 and lower, and only SOME with 4.4.4. It needs temp root first, etc. For whatever reason, we don't have a way to even temp root the 2013 X on 4.4.4 enough to allow Sunshine to do its work. And despite being asked many times, Jcase pretty much said in the Sunshine discussion threads that v3.0 wont have Moto X 4.4.4 support (unless he changed his mind and I missed it). Yet sunshine and its root processes, etc work on other phones (HTC) with 4.4.4.
But back to the thread you link...
On the X, due to its security measures, with a locked bootloader, you can only flash the Moto signed ROM for your phone. Nothing else. Because of this, you can't flash a custom recovery. To flash items, we use mFastboot and RSDLite. They need the img files, or bin files. If we make our own, they wont be signed, so they wont flash to a phone with a locked bootloader. And you can't package them into a flashable ZIP because stock recovery looks for the Moto digital signature (which we don't have and can't fake), and you can't install TWRP/CWM/Philz/etc to flash that way. So if you manage to pull the JB kernel out of the Moto SBF file, you wont be able to flash it.
Due to write protection on the 2013 X, any changes made to /System and a few other places, will be lost at power off/on. In other words, if you do manage to flash it (or push via adb), it wont stick due to write protection.
We've seen people try and manipulate their phone by trying to DOWNGRADE their ROM. Well, this doesn't work either. GPT.BIN (partition table), and Motoboot.img (bootloader, TZ, and a few other things) get in the way. Even on an X with an Unlocked bootloader, you can't downgrade these parts. Enough who attempted this have ended up bricking their phone immediately, or with later taking an OTA. Sure you can try to flash just system.img, and while that has less risk for bricking, people who have tried this were still not able to use the older Root Exploits (that worked if you hadn't upgraded already). People have tried flashing everything but GPT.BIN and MotoBoot.img. Again, it didn't help with rooting. Not to mention with a missmatched system.img or other parts, features on the phone may not always work properly (going Settings -> Security comes to mind), and you are at risk of bricking should you take an OTA update.
Since that process exploits a vulnerability, and its out there (so the vulnerability is in the public), I'm sure if it worked or was possible, JCASE, Beaups, or others would have put something together.
Now, back on topic of the XT1053... it has an Unlockable bootloader. Unlocking the bootloader disables write protection, and allows you to flash non-moto stuff. So unlocking the bootloader, flashing TWRP, reboot bootloader, enter TWRP and root, is quick, easy, effective, and doesn't rely on vulnerabilities on the phone to be exploited so patches/updates haven't got in the way. Plus you don't have to wait for someone to find them and create a repeatable process.
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...)?