Database Users

Stock rooted Lollipop with TWRP - Is this the best method to upgrade to MM?

There are a few threads that deal with upgrading lollipop to marshmallow, but they seem to raise as many questions as they answer - mainly since they were usually written before rooted images were distributed.
Basically, I am on an unlocked, rooted stock XT1575 with TWRP 2.8.7.0. It sounds like it's less efficient and has lots of potential problems to go back to stock, unroot, install OTA, do new system root, and re-add TWRP.
Instead, it sounds like the simplest method to get to stock rooted MM, with least steps and potential problems, should be this:
Update TWRP to 2.8.7.1 using IMG file here from within TWRP Recovery (TWRP Manager did not install it when I tried via Android proper - I was still at 2.8.7.0)
Do a full TWRP backup of my current Lollipop stock rooted installation (I assume this means I can restore without problems if the MM install goes awry)
*Optional: Use Titanium Backup to backup settings of important apps, and text messages/MMS.
In TWRP, Wipe->Swipe to Factory Reset
Transfer to phone and Flash via TWRP the stock rooted odexed ROM from this thread (not sure if there is a good argument for deodexed? I've never gotten a clear answer why one should be better, but would stick with odexed just because I believe it is "stock" so maybe less problems?)
Install SuperSU 2.62 from this thread by simply flashing it as normal in TWRP 2.8.7.1.
Reinstall all programs on initial setup. [*Optional: Reinstall via Titanium backup]
I assume if I do this I will: have marshmallow; have root; have working TWRP.
Does anyone see any obvious problems with this method? Thanks, I really appreciate any comments.
EDIT: Yes, I tried this method. It all worked, except I've added SuperSU installation steps that worked for me, since the "Stock Rooted" ROM is NOT actually rooted when I flash it. Also, used Titanium Backup successfully for some programs, so added that as an option.

Sorry to bump, but any response from someone with experience would be very helpful. I just want to make sure I don't have to go through the whole unroot/OTA/reinstall TWRP/reinstall root procedure that every thread says seems to cause problems...

Answered my own question - edited the main post to show the method used successfully.

Thank you for this answer thread. I was looking for the simplest answer for upgrading to MM without having to unroot and reflash everything. Looks like this is the easiest for now (I have having to reinstall everything, since some games I play to NOT react nicely to data being restored via titanium).

Have a brand new XT1575 with 5.1.1, Does the MM Update break root ability. I primarily want it for xposed, adaway. No ROMing
Should I update and then root? or root and then update?

I personally have found that following this method breaks root possibilities. MM is rooted, but when I got to the point of installing SuperSU via these steps, it broke EVERYTHING (settings stopped working, Motorola Services stopped working, etc).
I have to start from scratch again now.

Upgrading Rooted (TWRP+SU) PE 1575 from 5.1 to M. Need Advice + I have a guide

Hello,
Now before you ask, I've been doing a lot of research though searching threads and post. I'm actually going to post everything I found so far. On my first attempt of getting Marshmallow a few weeks ago, I downloaded the OTA and installed it. BIG mistake as I had TWRP and stock update didn't know what to do. I had to use CLARK to go back to stock then restore my phone back to Lolipop. Then I had to fix my Wifi Issue. After that I started doing a lot of research.
Here's all of my research links:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
Already Rooted Moto X Pure 2015 (KitKat) - Upgrade to Marshmallow, How?
Marshmallow and root -pg 2
MXPE on the way. Root after getting M update? (POST #18)
I need some input on people who have already went though this. So, this is what I'm getting:
1) Flash/Update to TWRP twrp-2.8.7.1-clark.img
2) Download "XT1575 stock unrooted TWRP backup" (from the first link). UNZIP THE FILE and place it in the TWRP folder on your phones internal storage.
3) Reboot into Recovery. Backup, then Restore the "XT1575 stock unrooted TWRP backup" image
4) If TWRP ask to install SuperSU, DON'T INSTALL
5) Let the phone boot back up and setup Marshmallow.
NOW, in order to Restore your apps+data with Titanium Backup, your phone has to be rooted. Currently, your phone is not rooted so you have to do the following:
6) Download 2.62 supersu and move it to internal/external SD.
7) Reboot into Twerp.
8) Install 2.62 supersu
9) Reboot
10) Test Titanium Backup and you should be OK.
Now, has anybody used this method or a similar method? I think this is possibly a correct method. Also reading that there's no need to use the seamless root since you can use supersu 2.62.

Personally I would flash the full stock mm firmware in fastboot. Then flash twrp and root. I don't believe your method will update modem.

lafester said:
Personally I would flash the full stock mm firmware in fastboot. Then flash twrp and root. I don't believe your method will update modem.
Click to expand...
Click to collapse
But if it doesn't update the modem, I could just flash that on there though TWRP right? NON-HLOS.bin?

If I can get some more feetback, it would be great. I'm going to attempt in one more day. If everything goes good, I want to make a quick guide since it's hard to find concrete guides for this situation.

Unable to Update to 6.0.1 (MTC20F)

I decided to catch up on security patches today and, with any luck, obtain the OTA update for Android N. I performed a full unroot (SuperSU) and blew away TWRP by flashing stock recovery for my current build of 6.0.1 (MTC19X). I have also flashed everything back to stock except user data. My boot loader remains unlocked. Every time I try to get the update to 6.0.1 (MTC20F) OTA, the phone will reboot normally and try to install the update. The little android's antennae wiggle for a minute or two and then it just falls over with the familiar red exclamation mark showing up.
Anyone have any ideas?
Thanks!

Cryptomap said:
I decided to catch up on security patches today and, with any luck, obtain the OTA update for Android N. I performed a full unroot (SuperSU) and blew away TWRP by flashing stock recovery for my current build of 6.0.1 (MTC19X). I have also flashed everything back to stock except user data. My boot loader remains unlocked. Every time I try to get the update to 6.0.1 (MTC20F) OTA, the phone will reboot normally and try to install the update. The little android's antennae wiggle for a minute or two and then it just falls over with the familiar red exclamation mark showing up.
Anyone have any ideas?
Thanks!
Click to expand...
Click to collapse
When you did have root, did you make any system changes? Perhaps installing a mod or something that's still there? OTA will fail if it detects any system changes. If you truly are back to stock, then you can also grab a zip of the OTA and install it via ADB sideload. That's what I did and it worked fine.

ultyrunner said:
When you did have root, did you make any system changes? Perhaps installing a mod or something that's still there? OTA will fail if it detects any system changes. If you truly are back to stock, then you can also grab a zip of the OTA and install it via ADB sideload. That's what I did and it worked fine.
Click to expand...
Click to collapse
When I had root I ran AdAway, Helium and the XPosed framework. Do you think any of those would cause my hiccup?
EDIT: I also had SELinuxModeChanger installed.
Would my best bet be to re-root and uninstall some of those programs that could edit system files?

Cryptomap said:
When I had root I ran AdAway, Helium and the XPosed framework. Do you think any of those would cause my hiccup?
EDIT: I also had SELinuxModeChanger installed.
Would my best bet be to re-root and uninstall some of those programs that could edit system files?
Click to expand...
Click to collapse
You won't be able to take an OTA with Xposed for sure as it changes the system big-time. If you want to test out Nougat before they post the factory image (if ever, ugh), then follow section 14 of this guide to the letter. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You can still flash TWRP and re-root it, but only systemless, and you can also flash a systemless Adaway. Xposed isn't available for Nougat yet, so if you must have that, you're better to wait.

ultyrunner said:
You won't be able to take an OTA with Xposed for sure as it changes the system big-time. If you want to test out Nougat before they post the factory image (if ever, ugh), then follow section 14 of this guide to the letter. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You can still flash TWRP and re-root it, but only systemless, and you can also flash a systemless Adaway. Xposed isn't available for Nougat yet, so if you must have that, you're better to wait.
Click to expand...
Click to collapse
Heisenberg's guides have been incredibly helpful so I'll try that route.
Thanks for the input!

Cryptomap said:
Heisenberg's guides have been incredibly helpful so I'll try that route.
Thanks for the input!
Click to expand...
Click to collapse
No problem. The thanks button does that too ... Seriously though, you have to be 'completely' stock to take an OTA, thus why I await the factory images with baited breath.

Can't update to B29

My phone is prompting me to update to B29, but when it reboots, it brings me to the TWRP recovery, and I can't seem to find an update.zip or anything. Is it not there, or am I just looking in the wrong places? Will it even successfully update with the bootloader unlock (not the official unlock) and TWRP installed, or do I need to restore the stock recovery?
My phone was originally on B20_boot, but I've since restored using Draken's TWRP files to get to B27 (I'm assuming still B20_boot).

You won't be able to OTA update with your system modifications. DrakenFX has flashable zips posted in another thread, but beware there seems to be quite a few bugs in b29 (I have no in-call audio personally).

You can use my updated post to B29 (bootstack and boot/system) flashable files are there.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

So why am I getting the notification, then? Will it just keep popping up, or is there a way to block it (even though I'm not rooted)?
As for the bugs, I've seen plenty who have upgraded to B29 without issues. How did you update? Could it be something with updating via TWRP?

Have you personally heard of anyone having problems with your update file? Will it wipe my phone (ie: will I have to reinstall everything)?

Bootloader unlocked, normal twrp flash as per DrakenFX's instructions. And yeah but a lot of people are in both boats so your milage may vary.

Thanks. Do you think I'll be able to keep my data partition intact? I really don't want to set everything else up again. It's getting old... lol.

I wiped everything, so I'm not sure. Maybe that's why my stuff is broken lol

You can't do system updates with custom bootloader's. You are getting the message because you still have the update program on your phone. Look for some sort of update.apk and disable or uninstall it.

I didn't think you could do that without root.
Oh well, I plan on putting root back on soon anyway.

That would be interesting, if true. You would think a "dirty flash" would cause more problems than a clean one.
What about the whole "can't root B29" thing. I've seen a comment where someone said they could not root B29 since they didn't root before the upgrade. I'm not rooted now, but I am bootloader unlocked with the latest TWRP. Should I be ok to flash without rooting first? I was hoping to root afterwards, and try to figure out a way to make Magisk work.

You can't root locked bootloader B29 afaik at the moment. You'd either have to unlock your bootloader or stay on B27 to get root.

I am bootloader unlocked.
I'm not rooted now, but I am bootloader unlocked with the latest TWRP.
Click to expand...
Click to collapse

EngineerMode unroot?

back when engineermode exploit backdoor 'thing' whatever you want to call it, was still a thing i seized to opportunity to gain root access, however since then magisk hide has begun failing me and i would like to either find a way to update magisk from v14.0 safely, or to unroot completely (preferably without wiping) as this has started being problematic. I am on the latest oxygenOS update and i used this guide to root (i originaly linked it here but apparently i cant do that, it was on github, called OneplusRoot by a fella named aldur.)
If anyone can help id really appreciate it.
Thanks in advance

Since One Plus removed engineering mode I'm surprised you were able to update OOS and maintain the exploit. Why don't you just unlock your bootloader and root the proper way? Your phone won't melt if you do.

I would like to avoid wiping if possible. I too am surprised at the persistence of root after at least 3 OTAs. At this point I no longer really need root and would rather my phone run smoothly without some applications crashing or not running due to root.

bump?

gbesh said:
bump?
Click to expand...
Click to collapse
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you

manor7777 said:
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you
Click to expand...
Click to collapse
Well my system doesn't boot with root. I have to manually mount something and start the magisk service.
Which is why I'm not sure how to update as I've been told the updated version has a different file structure that the one I'm on.

were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how

yohouse2 said:
were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how
Click to expand...
Click to collapse
no unfortunately i am still waiting for a solution.

gbesh said:
no unfortunately i am still waiting for a solution.
Click to expand...
Click to collapse
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install

yohouse2 said:
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install
Click to expand...
Click to collapse
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.

gbesh said:
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.
Click to expand...
Click to collapse
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.

yohouse2 said:
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.
Click to expand...
Click to collapse
After one of the recent updates, magisk hide started working again and my apps are no longer crashing. It is strange but i guess this situation has turned out favourably after all.