Database Develop

[Q] Verizon DE Software Upgrade Q

If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike

Mike7143 said:
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Click to expand...
Click to collapse
You need stock /system partition and stock recovery. It doesn't matter whether the bootloader is locked or unlocked.

Mike7143 said:
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Click to expand...
Click to collapse
To install? or to be notified and receive the update?
To receive the update you'll need to be running the "stock" Verizon firmware, rooted/unrooted and bootloader locked/unlocked doesn't matter.
For it to install successfully, to expand on what kbluhm posted...
Keep in mind that usually OTA updates will look for certain files to be present on your phone and verify their size and check sums (MD5 or the like) before the OTA update will install. If files are missing or changed, the ota update will fail. That is why "stock /system" is required.
And "stock recovery" is needed because when the phone reboots to install the update, it tries to boot to stock recovery and run the install script. The 3rd party recoveries don't seem to work, or have errors, when installing the OTA update zips.
If you've rooted with SlapMyMoto, RockMyMoto, or thel like, you may have other issues to deal with in order to take any OTA updates since those processes can touch other files/partitions on the phone which will cause problems with the OTA Updates.

So in order to install the update I need to re-flash the stock recovery over TWRP, correct? How do I go about doing this?

Ah okay, thanks guys. What a hassle. I'm unlocked and using TWRP, flashed a new boot logo, and am rooted. Probably just easiest to just SBF back to stock and re-do everything.
Thanks!

You could grab the factory image from Motorola and flash only system and recovery using fastboot. That is my plan. You can find the zip file on Motorola's site or there is a topic here on XDA.
Sent from my XT1060 using Tapatalk

guitarbedlam said:
So in order to install the update I need to re-flash the stock recovery over TWRP, correct? How do I go about doing this?
Click to expand...
Click to collapse
Mike7143 said:
Ah okay, thanks guys. What a hassle. I'm unlocked and using TWRP, flashed a new boot logo, and am rooted. Probably just easiest to just SBF back to stock and re-do everything.
Thanks!
Click to expand...
Click to collapse
There are several threads about using Fastboot to flash recovery or parts of the rom rather than having to use RSDLite and flash the SBF of everything..
Example: see option 2 in -> http://forum.xda-developers.com/showthread.php?t=2536735

KidJoe said:
There are several threads about using Fastboot to flash recovery or parts of the rom rather than having to use RSDLite and flash the SBF of everything..
Example: see option 2 in -> http://forum.xda-developers.com/showthread.php?t=2536735
Click to expand...
Click to collapse
Thus, all I'd have to flash (I'm stock unlocked rooted) is the recovery and I'd be good to install the update. Then install the custom recovery and install the superuser zip. and BAM. But first I need the whole 4.4.2 update thing...

guitarbedlam said:
Thus, all I'd have to flash (I'm stock unlocked rooted) is the recovery and I'd be good to install the update. Then install the custom recovery and install the superuser zip. and BAM. But first I need the whole 4.4.2 update thing...
Click to expand...
Click to collapse
Sure, we need the 4.4.2 update.
And as long as you didn't delete any stock apps/apk's, freeze them with Titanium Backup or something similar, or rename them manually (and forgot to rename them back)... then yes.. just flash stock recovery, take update, flash TWRP and use SuperSU to re-root.

KidJoe said:
Sure, we need the 4.4.2 update.
And as long as you didn't delete any stock apps/apk's, freeze them with Titanium Backup or something similar, or rename them manually (and forgot to rename them back)... then yes.. just flash stock recovery, take update, flash TWRP and use SuperSU to re-root.
Click to expand...
Click to collapse
You can freeze them all you want and leave them frozen. They are still there, untouched, waiting to be checked/verified against and patched/updated. Once you obtain root again and grant it to Titanium Backup it will be re-frozen.
You just can't delete, rename or swap out.....frozen apps are still right there as normal.

tcrews said:
You can freeze them all you want and leave them frozen. They are still there, untouched, waiting to be checked/verified against and patched/updated. Once you obtain root again and grant it to Titanium Backup it will be re-frozen.
You just can't delete, rename or swap out.....frozen apps are still right there as normal.
Click to expand...
Click to collapse
Interesting. One of the issues reported with the Kit Kat update was the OTA failing due to apps frozen with Titanium Backup. I only "disable" via the stock app manager, so I haven't had a problem.

Most likely those with failures had modified/deleted/renamed something else that was causing the issues and blaming it on the frozen apps. I have updated every device I've had with frozen apps. Freezing, at least in Titanium Backup, tells the OS the app is not available. In recovery, the OS is not loaded and knows nothing about frozen apps. Titanium doesn't touch the actual files so they are still present to be patched by the OTA.
Sent from my Nexus 10

[Q] Upgrading to Lollipop from locked bootloader, rooted, Kitkat.

Hello all,
With news that the Z3 and Z3 compact are starting to get Lollipop today I am sure a lot of people are going to be coming to the boards asking this exact question. So I wanted to start a thread that can help people find the answer quickly. (I'll update the OP as useful info comes in.)
I am currently on a D5803 running 4.4.4, with a locked bootloader and am rooted. I used This how-to to get where I am.
What is the best way to upgrade to Lollipop for me?
Is there a way to keep root? A pre-rooted FTF file?
Will all DRM features remain?
Will I need to reinstall anything? Recovery? Busy Box? SU?
Does this upgrade require a full wipe?
Thanks for any help
If anyone wants to check if their bootloader is locked:
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked

just wonder...
i definitly want to root my Z3C.
Should i root with KK 4.4 or wait for Lollipop(and root later) !?

TheTomcraft said:
just wonder...
i definitly want to root my Z3C.
Should i root with KK 4.4 or wait for Lollipop(and root later) !?
Click to expand...
Click to collapse
You root on KK then you can update to Lollipop and keep root.

The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?

Sean09 said:
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Click to expand...
Click to collapse
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.

frason said:
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
Click to expand...
Click to collapse
could you please write what exactly you did to achieve this. Step by step guide would be awesome. Thanks!

gruev said:
could you please write what exactly you did to achieve this. Step by step guide would be awesome. Thanks!
Click to expand...
Click to collapse
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.

q.
frason said:
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
Click to expand...
Click to collapse
Did you wipe? or flash over?

newbie2006 said:
Did you wipe? or flash over?
Click to expand...
Click to collapse
I wiped it (had too much crap on the phone anyway, so worth it), restored what I wanted with Titanium Backup when done.
---------- Post added at 10:24 PM ---------- Previous post was at 10:19 PM ----------
I also tried with flashing lockeddualrecovery but recovery doesn't work. So need to wait for an update on that one I guess.

Any ideas about what could go bad if I don't wipe data?
Also, do you still have drm?

I succesfully flashed lolipop with this method without data wipe. I still have root and DRM keys. The only thing I lost was data of some app's with external data linked to SD card with Link2SD. And some root app's started to claim about busybox not installed properly. Besides that everything works like a charm

frason said:
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
Click to expand...
Click to collapse
When you flash those do you have system read and write as well? Do we need to worry about the RICDefeat in doing all this for the upgrade? Is RICDefeat integrated into that?

1.Flash the tft of lollipop
2.Get the zip of XZDualRecovery 2.8.3 Advanced Stock Kernel from http://nut.xperia-files.com/ and supersu from http://forum.xda-developers.com/showthread.php?t=1538053
3.Flash the boot.img in AndroPlusKernel with cable on flashtool
4.Reboot in recovery
5.Flash XZDualRecovery 2.8.3 Advanced Stock and supersu
6.Enjoy
Sorry，it should be with UB

about not working recovery
Dont know it thats issue, but I have same clue.
On KitKat after applying all steps to root 4.4.4 rom recovery was working until I changed busybox.
Oryginaly busybox was in version 1.20.2-jb - with that recovery was working.
I need some other tools and updated busbox to version 1.22.1 and recovery wasnt working (starting recovery end up with bootloop, but could start to system).
Returning back to recovery 1.20.2-jb fixed problem.

frason said:
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
Click to expand...
Click to collapse
Sean09 said:
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Click to expand...
Click to collapse
I was hoping by adding step 4, it would be possible the encrypt device. Sadly it still creates a bootloop.

in my case I received the notification update via OTA, have Kit Kat with root if I update, will i lose root?

skaarax said:
in my case I received the notification update via OTA, have Kit Kat with root if I update, will i lose root?
Click to expand...
Click to collapse
I want to know about this too.
And what is a safe process for us (locked bootloader, rooted 4.4) to upgrade to 5.02 or 5.1 in the future.
I heard that unlocking bootloader will causes the camera not working properly (at least the auto mode would be messed up)
Does TWRP requiring unlocking bootloader?
Thanks guys.

I'm resurrecting this thread as I've got the same question as previous posters and I've not been able to find an answer elsewhere on the forum.
Basically, I've got a phone with a Bootloader which can't be unlocked. I upgraded/rooted it last year. It's still on KitKat. Is there any way I can upgrade it to Lollipop or Marshmallow without going through the downgrade/flash pre-rooted ROM procedure, without losing root? In other words, can I make use of TWRP which I installed in order to flash the rooted ROM last time? If so, how? (I'm not keen on using KingRoot unless somebody can convince me that handing over my IMEI info is safe.)
Thanks in advance.

Just flash a pre-rooted 5.1 zip made with prf creator whilst still on root+recovery KK. That's how I updated my M2 from rooted 4.4.4 KK to rooted 5.1 lollipop whilst retaining my locked bootloader. No sure if it's working for mm yet though this way

Suggestions for root & ROM

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

Stock Recovery To Replace Twrp!!!!!Extracted from Official Rom:)

This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me

Brick
abhigamez said:
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Click to expand...
Click to collapse
This could end up in hard brick also if OTA detects other system modifications. You should just edit the OP with a warning.

abhigamez said:
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Click to expand...
Click to collapse
Couldn't one just install it from this link?
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
This is basically all of the stock firmware (Including the recovery), correct?

CasinovaRoyale said:
This could end up in hard brick also if OTA detects other system modifications. You should just edit the OP with a warning.
Click to expand...
Click to collapse
i don't think so abt hard brick
as when i was updating i simply came with error while updating that can't update
and i also tried updating after flashing custom rom [which is available online] and i was successfully updated

smokinjoe2122 said:
Couldn't one just install it from this link?
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
This is basically all of the stock firmware (Including the recovery), correct?
Click to expand...
Click to collapse
I don't think it's a useful thread as there is a specific thread to give information about installing Official firmware and relocking the bootloader.!
Please moderator check this once.
This might damage the devices if anyone tries to update the ROM through OTA, by just changing the recovery being the variety ,oem and bootloader status changed.

thippu46 said:
I don't think it's a useful thread as there is a specific thread to give information about installing Official firmware and relocking the bootloader.!
Please moderator check this once.
This might damage the devices if anyone tries to update the ROM through OTA, by just changing the recovery being the variety ,oem and bootloader status changed.
Click to expand...
Click to collapse
i hv checkd it, but my device didn't hard broke, but i want to make my device dead to get new motherboard in warranty

yograjfire18 said:
i hv checkd it, but my device didn't hard broke, but i want to make my device dead to get new motherboard in warranty
Click to expand...
Click to collapse
:angel:lol

Does someone has tried this successfully?

mabvmet said:
Does someone has tried this successfully?
Click to expand...
Click to collapse
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.

Could always just do "fastboot boot" instead of "fastboot flash". It will allow you to then boot twrp, install what you want, and not touch the stock recovery.

pratham.kamath said:
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Click to expand...
Click to collapse
What are the steps I need to follow to install this file? (SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
---------
Edit: Solved
---------
I followed the code section steps on this post:
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018

pratham.kamath said:
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Click to expand...
Click to collapse
Hey! I Finally did this, I removed the twrp and the root, I Just installed this stock (?) rom through the "adb fastboot". Now when I look for OTA updates it appears a message that indicates that the latest security update is installed, it's the one of December 2017...
Why doesn't it appear the last one (april's or so)?
What I have to do in order to have or reactivate the OTA updates?
Thanks in advance!

Make sure the correct stock rom is installed. (Cross check the name word to word) I too tried a few different stock ROMs and only the above version worked and updated till April security patch. Rest versions didn't update for some reason.

pratham.kamath said:
Make sure the correct stock rom is installed. (Cross check the name word to word) I too tried a few different stock ROMs and only the above version worked and updated till April security patch. Rest versions didn't update for some reason.
Click to expand...
Click to collapse
How can I know what is the correct stock rom?

SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/
This one worked for me.

pratham.kamath said:
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/
This one worked for me.
Click to expand...
Click to collapse
My current file >>
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml_1
This rom left me with the December security patch and no OTA updates available
This time I will download the same one, but the most recent (February, according with the web)
Next download >>
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip 03/02/2018 06:35
I followed this steps in code section to flash it... any suggest?
Steps >> https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018

Don't go by date go by exact name and number of rom as I mentioned. I tried almost all the firmwares listed and only the one that I mentioned updated to latest april security patch. Matter of fact i just restored phone to stock yesterday and it worked again. Also copy all the commands to a notepad and save the same as .bat file so that way you can just run the file and it will automatically install stock rom and reboot phone.
---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
Check software channel name in settings. Mine is listed as retin. I read that there are other software channels too for which updates security patch has not been released yet. I may be wrong though.

pratham.kamath said:
Don't go by date go by exact name and number of rom as I mentioned. I tried almost all the firmwares listed and only the one that I mentioned updated to latest april security patch. Matter of fact i just restored phone to stock yesterday and it worked again. Also copy all the commands to a notepad and save the same as .bat file so that way you can just run the file and it will automatically install stock rom and reboot phone.
---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
Check software channel name in settings. Mine is listed as retin. I read that there are other software channels too for which updates security patch has not been released yet. I may be wrong though.
Click to expand...
Click to collapse
Sorry, how do I run the bat file? The last time I entered the commands one by one.
My software chanel is "openmx" the sameone that I had when the phone was rooted (and with the updates available).

I need help
I need the recovery.img for the device moto g5s plus xt1806:llorando:

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...)?