Database Info

Still get OTAs while having ROOT?

If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.

KuGeL94 said:
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
Click to expand...
Click to collapse
Yes!

SWTR said:
Yes!
Click to expand...
Click to collapse
Indeed.

KuGeL94 said:
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
Click to expand...
Click to collapse
The OTA will download but not install. You need stock recovery AND any system file that is updated by the OTA needs to be stock as well otherwise OTA install will fail.
Plenty of threads on XDA speak of this.
If you look at the OTA updater file you will see if uses MD5 (or similar) to check each system file it updates to make sure its as it was originally.
When you root it alters some system files.
Best thing is to install custom recovery and take a backup before rooted. Then root. When you get an OTA just restore backup and flash stock recovery. Then OTA will re-download. Let it install, then flash custom recovery and re-root.

Thanks, well I'll just stay unrooted and make the best out of it, the Moto G is just as amazing as Motorola developed it to be.

No stock recovery it's no need. I updated last ota with Philz recovery without problems.

denzel09 said:
No stock recovery it's no need. I updated last ota with Philz recovery without problems.
Click to expand...
Click to collapse
Do you mean you downloaded OTA and flashed manually via recovery. You can do that I agree, but what you can't do is let OTA install naturally the way Motorola intended.

No. I had Philz recovery. System stock partition. Downloaded ota normally, reboot like ota update ask, phone reboots in philz recovery and this last flash ota automatically without any problem. There is not need to reflash stock recovery or flash ota update manually with custom rec, only need a non root stock system partition. I dont know if stock cwm or other rec like twrp work in same way but i doubt, always used only philz recovery.

You do not need stock recovery, I don't know who made this stupid rumour up. I use twrp and it flashes fine.
Sent from my Google Nexus G -

[Q] Droid Maxx 4.2.2 sunshine unlock, how to get to 4.4.4?

So i held out taking the otas for a while to avoid losing root and am still on 4.2.2 post camera update. I know, it's sad, but I have root so i haven't been dying to update.
However, i just saw that sunshine will unlock my bootloader, which I'm going to do. What I'm confused about though is once i unlock my bootloader, how do I get to 4.4.4? Can I just revert everything to stock and take all of the otas (and then flash twrp to get root)? I heard that something in one of the otas changed something with the bootloader, so i don't know if taking that would cause problems with an unlocked bootloader or make me lose my unlocked status. Either way, could i just flash a 4.4.4 image directly from 4.2.2? If so where do i get a stock image to flash? Thanks for any help!

Once you have successfully unlocked, make sure you are status 3 unlocked in fastboot.
Once confirmed, you can use the rsd lite, and use the stock firmware from:
http://sbf.droid-developers.org/
Next, flash twrp for the ghost from their website.
Lastly if you want root flash supersu.

So can I flash a different OS version from the site that you linked? Or is that just to return to stock in anticipation of flashing TWRP and using that to flash a later android version?

rule of thumb is you cannot downgrade, only upgrade or revert to the same version you are already on

This seemed like the easiest route to a rooted 4.4.4... Unlock bootloader via Sunshine, and proceed as instructed here: http://forum.xda-developers.com/droid-ultra/general/unlocked-boot-xt-1080-restore-4-4-4-pre-t2883131
Data remains intact, unlocked bootloader warning on boot logo fixed, and TWRP (or Philz) flashed as recovery. Super easy. Good times.

Deleted. Redundant post.
Sent from my DROID Maxx

I'm in the same situation. I'm currently rooted on the post camera update and held off on the new ota's for a while. I want to do the sunshine unlock. My question is should I do the sunshine unlock, upgrade to the newest 4.4.4 then install twrp to root? This youtube.com/watch?v=_xVyJMtLDPgvideo gives pretty good instructions but I also want to take future OTA's. I understand you won't be able to unless you put the recovery back to stock.
Thanks in advanced

rcji said:
I'm in the same situation. I'm currently rooted on the post camera update and held off on the new ota's for a while. I want to do the sunshine unlock. My question is should I do the sunshine unlock, upgrade to the newest 4.4.4 then install twrp to root? This youtube.com/watch?v=_xVyJMtLDPgvideo gives pretty good instructions but I also want to take future OTA's. I understand you won't be able to unless you put the recovery back to stock.
Thanks in advanced
Click to expand...
Click to collapse
Yep true. Can't take OTAs with out stock recovery. But it is easy to flash Stock Recovery then back to TWRP after the OTA. Of course safest option is to flash stock fxz without wiping data before taking OTAs.
Personally have my own recovery and logo.bin script I keep for just this reason. Run RSDlite with the stock software take OTA (if no fxz yet for the OTA) then full bit and setup and finally flash the recovery and logo.bin I use.
Many ways of doing it just find its easier for me this way probably cause this is how I learned from trial and error is all. Probably an easier way though.

[Q] Help with installing lollipop on unlocked phone

Hello !
I recently bought a used Z3 6603, and wanted to update it to lollipop.
But it seems it has a unlocked bootloader (according to service menu) and when i recieved it, it was factory reset, but some 3rd party apps were still installed.
One of them Super SU, so it was rooted.
I was told that i could update the firmware if i just used the Full Uninstall feature in Super Su, so i did that.
I still can't update using sony companion, becouse it knows the software is not the original one.
And i cant reinstall super su, its saying that there is no SU binary installed and the program cant install it.
I have flashed phones before, but it was really a long time ago, so im asking for some help to fix this.
Its running 4.4.4 build 23.0.1.A.5.77 and stock rom i think.
Please tell me what to do, and what info you might need !
I want to have the phone in lollipop, but everything stock, no root, no bootloader etc.
And somewhere I read something about DRM keys. Please help me with fixing that aswell thank you.
Regards ImmoralCore

ImmoralCore said:
Hello !
I recently bought a used Z3 6603, and wanted to update it to lollipop.
But it seems it has a unlocked bootloader (according to service menu) and when i recieved it, it was factory reset, but some 3rd party apps were still installed.
One of them Super SU, so it was rooted.
I was told that i could update the firmware if i just used the Full Uninstall feature in Super Su, so i did that.
I still can't update using sony companion, becouse it knows the software is not the original one.
And i cant reinstall super su, its saying that there is no SU binary installed and the program cant install it.
I have flashed phones before, but it was really a long time ago, so im asking for some help to fix this.
Its running 4.4.4 build 23.0.1.A.5.77 and stock rom i think.
Please tell me what to do, and what info you might need !
I want to have the phone in lollipop, but everything stock, no root, no bootloader etc.
And somewhere I read something about DRM keys. Please help me with fixing that aswell thank you.
Regards ImmoralCore
Click to expand...
Click to collapse
Your DRM keys are lost forever.

TheTeslaCoil said:
Your DRM keys are lost forever.
Click to expand...
Click to collapse
Ok, so they are lost even if I use the first backup that was made by the person I bought it from ?
DRM=Hardcoded=Once unlocked, always DRM free, even if you use the recovery image ?
And the rest of the questions, what am I supposed to do to get stock lollipop?
In the matter of fact it does not matter if its unlocked or locked, I just want legit lollipop, with the possibility to update regularly. (But if root is possible at the same, it can still be rooted)
Thanks for your reply !

You need the TA backup. Not system backup.
And careful not to restore some other TA.
If the previous owner backed up TA, good. If not, no chance to recover them.
Download your specific firmware in ftf format and flash it with Flashtool.
Make a clean install.
You cannot recieve OTA with an unlocked bootloader, only if you relock, but there is no point in doing that if the DRM keys are lost.
So, from where you stand, keep it rooted and unlocked, because you can do much more with it : Custom ROM' s [at the moment stock is best]...custom kernels with recovery...mods...etc.
After you flash the ftf, flash via adb a custom kernel with recovery and from recovery flash SuperSU update, as a flashable zip, that will root the phone and install SuperSU.Search also for busybox flashable zip.

TheTeslaCoil said:
You need the TA backup. Not system backup.
And careful not to restore some other TA.
If the previous owner backed up TA, good. If not, no chance to recover them.
Download your specific firmware in ftf format and flash it with Flashtool.
Make a clean install.
You cannot recieve OTA with an unlocked bootloader, only if you relock, but there is no point in doing that if the DRM keys are lost.
So, from where you stand, keep it rooted and unlocked, because you can do much more with it : Custom ROM' s [at the moment stock is best]...custom kernels with recovery...mods...etc.
After you flash the ftf, flash via adb a custom kernel with recovery and from recovery flash SuperSU update, as a flashable zip, that will root the phone and install SuperSU.Search also for busybox flashable zip.
Click to expand...
Click to collapse
Ok, I will try that then, but if I use flashtool to update to lollipop, will I still be able to root easy, or should I reinstall 4.4.4 clean, then root, fix recovery kernel and everything, and then lollipop or what goes first?
Does flash/kernel etc affect the fact that it has an unlocked bootloader ? do i need to do anything with that, or do it stay unlocked?

ImmoralCore said:
Ok, I will try that then, but if I use flashtool to update to lollipop, will I still be able to root easy, or should I reinstall 4.4.4 clean, then root, fix recovery kernel and everything, and then lollipop or what goes first?
Does flash/kernel etc affect the fact that it has an unlocked bootloader ? do i need to do anything with that, or do it stay unlocked?
Click to expand...
Click to collapse
If you have unlocked the bootloader it is always a trivial matter to root.
Just flash an insecure kernel.
If one does not exist use [NUT]'s online kernel builder to make one with recovery incorporated in it. Its very straightforward and an automated process.
So, update using flashtool, flash your custom kernel, and you have root and recovery.

gregbradley said:
If you have unlocked the bootloader it is always a trivial matter to root.
Just flash an insecure kernel.
If one does not exist use [NUT]'s online kernel builder to make one with recovery incorporated in it. Its very straightforward and an automated process.
So, update using flashtool, flash your custom kernel, and you have root and recovery.
Click to expand...
Click to collapse
1. Sorry for my noobish question, but define insecure kernel?
2. Did I get it right? I read about ppl downgrading their phones to 4.4.4 and then installing stuff. And for me it does not matter wich version it is, becouse the unlocked bootloader makes it easy to flash, even what version you are running?

ImmoralCore said:
1. Sorry for my noobish question, but define insecure kernel?
2. Did I get it right? I read about ppl downgrading their phones to 4.4.4 and then installing stuff. And for me it does not matter wich version it is, becouse the unlocked bootloader makes it easy to flash, even what version you are running?
Click to expand...
Click to collapse
1) a rooted kernel.
2) If you have unlocked there is no need to follow any of the locked bootloader guides, they are a waste of your time. One of the points point of unlocking the phone is to easily get root. You just flash a custom kernel to gain root.
If you have a locked bootloader then you have to go through all the fuss of downgrading etc etc.... but with an unlocked bootloader its so easy and straightforward

gregbradley said:
1) a rooted kernel.
2) If you have unlocked there is no need to follow any of the locked bootloader guides, they are a waste of your time. One of the points point of unlocking the phone is to easily get root. You just flash a custom kernel to gain root.
If you have a locked bootloader then you have to go through all the fuss of downgrading etc etc.... but with an unlocked bootloader its so easy and straightforward
Click to expand...
Click to collapse
Ok, thank you very much for your answers both of you!
I understand everything much better, now its just some flashing to do, c ya ! :good:

ImmoralCore said:
Ok, thank you very much for your answers both of you!
I understand everything much better, now its just some flashing to do, c ya ! :good:
Click to expand...
Click to collapse
Good luck.

[Q] Just want to use the "Titanium Backup" app

I am using Stock Kernel and CM 12.1 on my Oneplus One. I just want to use the "Titanium Backup" app (that running on Root device only). What exactly I need to do with my phone: ???
Just Unlock my Bootloader and run SuperSU ?
Can I still be able to use Rom OTA with the Unlock Bootloader ?
Thanks!

Too late for Titanium backup now!
Please read this guide very carefully. It covers everything you need to know: [GUIDE] Unlock/Root/Flash for OnePlus One
To answer your question briefly, in order to use Titanium Backup, you need a rooted device.
To root your device you need:
unlocked bootloader
custom recovery (i.e. TWRP )
When you unlock your bootloader, you will lose all your data - your phone will be wiped!
Long story short, it is now too late for you to use Titanium backup to backup your apps & data.
Please note that there are methods to backup your apps which do not require root access, but you will have to use adb & the command line - not for everyone, and not what you had in mind I imagine.
You might just want to make a list of your favourite apps, backup their data & settings as much as you can, and then once you've got some sort of backup done, proceed to unlock your bootloader (and wipe your device), install TWRP, gain root, and profit.
Once again: Please read this guide very carefully. It covers everything you need to know: [GUIDE] Unlock/Root/Flash for OnePlus One

ohussain said:
Please read this guide very carefully. It covers everything you need to know: [GUIDE] Unlock/Root/Flash for OnePlus One
To answer your question briefly, in order to use Titanium Backup, you need a rooted device.
To root your device you need:
unlocked bootloader
custom recovery (i.e. TWRP )
When you unlock your bootloader, you will lose all your data - your phone will be wiped!
Long story short, it is now too late for you to use Titanium backup to backup your apps & data.
Please note that there are methods to backup your apps which do not require root access, but you will have to use adb & the command line - not for everyone, and not what you had in mind I imagine.
You might just want to make a list of your favourite apps, backup their data & settings as much as you can, and then once you've got some sort of backup done, proceed to unlock your bootloader (and wipe your device), install TWRP, gain root, and profit.
Once again: Please read this guide very carefully. It covers everything you need to know: [GUIDE] Unlock/Root/Flash for OnePlus One
Click to expand...
Click to collapse
First thanks for your answer! Do I lose the rom OTA Update after unlock my bootloader and install TWRP ? Do I must change to the TWRP recover or I can use the stock one?
Sent from my A0001 using xda premium

You're welcome. You cannot use the stock recovery, and you will not receive OTAs once you've unlocked your bootloader, installed TWRP, and rooted.
Trust me, you are not missing out on anything - OTAs will be rare, and the quality of the OS provided by Cyanogen is low.
Once you have TWRP installed, you can choose to install other ROMs. I highly recommend XenonHD. Light, stable, AOSP-based (not a CM clone), with full layers support, and a balanced feature-set.
There are many ROMs available for the OnePlus One for you to choose from, and you could also run CM or OxygenOS - it's up to you.
Just make sure you read & follow Heisenberg's guide, and you'll be fine. :good:
Since you're coming from Cyanogen's lollipop build, you should pay special attention to the note at the end of section 2 of Heisenberg's guide ('How To Install A Custom Recovery On Your Device').

xperia_88 said:
First thanks for your answer! Do I lose the rom OTA Update after unlock my bootloader and install TWRP ? Do I must change to the TWRP recover or I can use the stock one?
Sent from my A0001 using xda premium
Click to expand...
Click to collapse
Unlocking your bootloader has no effect on the ability to take OTA updates. However, having a custom recovery and root do. If you want to take an OTA in future you just need to flash the stock recovery and the stock system.img and OTA's will work perfectly.

ohussain said:
You're welcome. You cannot use the stock recovery, and you will not receive OTAs once you've unlocked your bootloader, installed TWRP, and rooted.
Click to expand...
Click to collapse
This isn't entirely true, the unlocked bootloader doesn't matter.

Heisenberg said:
This isn't entirely true, the unlocked bootloader doesn't matter.
Click to expand...
Click to collapse
You're God damn right.
That's what I meant, but thank you for clearing up precisely what precludes one from receiving OTA updates. :good:

Heisenberg said:
Unlocking your bootloader has no effect on the ability to take OTA updates. However, having a custom recovery and root do. If you want to take an OTA in future you just need to flash the stock recovery and the stock system.img and OTA's will work perfectly.
Click to expand...
Click to collapse
Thanks for your clear answer!!!
Since I just want to use my favorite Titanium Backup but still using OTA update I would appreciate if you'LL guide me what is the easier way to do that.
I know now that to Unlocking my bootloader has no effect on the ability to take OTA but the custom recovery and root do so where I can find link to the stock recovery and the stock system.img and do I must to flash them after the Unlocking my bootloader ?
10X

xperia_88 said:
Thanks for your clear answer!!!
Since I just want to use my favorite Titanium Backup but still using OTA update I would appreciate if you'LL guide me what is the easier way to do that.
I know now that to Unlocking my bootloader has no effect on the ability to take OTA but the custom recovery and root do so where I can find link to the stock recovery and the stock system.img and do I must to flash them after the Unlocking my bootloader ?
10X
Click to expand...
Click to collapse
In order to use Titanium you need to unlock your bootloader, then flash TWRP recovery, then use TWRP recovery to flash SuperSU. You'll have root now and Titanium will work. Once you get to the point where you want to take an OTA you can extract the system.img and the recovery.img from the fastboot zip which you'll find here:
http://forum.xda-developers.com/showthread.php?t=2906746
Flash them and then OTA updates will work. There are detailed instructions in my guide:
http://forum.xda-developers.com/showthread.php?t=2839471

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8

Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!

Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.

Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?

Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.

annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?

hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?

Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:

Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.

How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol

Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)

Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?

GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...

annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse

I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing

Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?