Develop Bugs

AT&T Update Help

I received the notification to update this morning to 4.4, however the update started to apply, it kicked it out with a suspected root error. Before applying the update, I had already uninstalled Xposed and unrooted my phone, so I am not sure what set off the root checker. I was wondering what my options were at this point. I know I can flash back to stock, but I would like to avoid this if at all possible. Are there any alternatives, or will I be forced to flash back to stock?
Thanks in advance for your help.
Sent from my LG-E980 using XDA Free mobile app

marksman81 said:
I received the notification to update this morning to 4.4, however the update started to apply, it kicked it out with a suspected root error. Before applying the update, I had already uninstalled Xposed and unrooted my phone, so I am not sure what set off the root checker. I was wondering what my options were at this point. I know I can flash back to stock, but I would like to avoid this if at all possible. Are there any alternatives, or will I be forced to flash back to stock?
Thanks in advance for your help.
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
I'm having exactly the same issue. I used the one click root method and have unrooted using full unroot in SuperSu.
But it appears full unroot per SuperSu is not enough? I tried root checker in Play Store and it says I am not rooted.
When I run the install it takes a long time to download and gave 0x13e error after the reboot while upgrading.
I also tried the LG PC Suite but it says my phone has the most current version, that is weird...
This OTA seems to be very picky as I was able to update in January 2014 fully rooted....
I wonder if I need to flash the IOT and go through the hassle of reinstalling all apps and config....that's a lot of hassle...

View92612 said:
I'm having exactly the same issue. I used the one click root method and have unrooted using full unroot in SuperSu.
But it appears full unroot per SuperSu is not enough? I tried root checker in Play Store and it says I am not rooted.
When I run the install it takes a long time to download and gave 0x13e error after the reboot while upgrading.
I also tried the LG PC Suite but it says my phone has the most current version, that is weird...
This OTA seems to be very picky as I was able to update in January 2014 fully rooted....
I wonder if I need to flash the IOT and go through the hassle of reinstalling all apps and config....that's a lot of hassle...
Click to expand...
Click to collapse
It is very strange but if I try update recovery it says my battery does not have enough charge. (but battery is at 100%).
I even bought a new battery. I did disable carrier iq spying service before I unroot.
Do I have to enable carrier iq spy in order to upgrade?

View92612 said:
It is very strange but if I try update recovery it says my battery does not have enough charge. (but battery is at 100%).
I even bought a new battery. I did disable carrier iq spying service before I unroot.
Do I have to enable carrier iq spy in order to upgrade?
Click to expand...
Click to collapse
Your phone needs to be 100% stock in order for OTA updates to work. This means:
no custom recovery (CWM, TWRP, etc)
all bloatware must be present
you can't be rooted
all system services must be like stock (this includes carrier IQ, so yes, it needs to be reenabled).
If you can't get the OTA to update after fixing everything, try flashing this:
http://forum.xda-developers.com/showthread.php?t=2760895
This IS the ATT stock ROM, but mildly debloated. The creator only debloated things that could be installed via the Play Store though (like Google Music, Newstand, Books, etc), so there isn't anything like the remote app or something missing.
I flashed this version because I'm too lazy to try and return my phone to pure stock just to get the OTA and then have to reflash root and a custom recovery. Too much work for me.
EDIT: I'm not too sure what's going on with your recovery... I hope someone else can answer that for you.

The easiest thing to do is just flash the 4.4.2 Rom found here: http://forum.xda-developers.com/showthread.php?t=2760895
This route saves allot of time having to flash back to pure stock, wait for your phone to receive the update again, and your phone taking forever to download said update.

spexwood said:
If you can't get the OTA to update after fixing everything, try flashing this:
http://forum.xda-developers.com/showthread.php?t=2760895
This IS the ATT stock ROM, but mildly debloated. The creator only debloated things that could be installed via the Play Store though (like Google Music, Newstand, Books, etc), so there isn't anything like the remote app or something missing.
I flashed this version because I'm too lazy to try and return my phone to pure stock just to get the OTA and then have to reflash root and a custom recovery. Too much work for me.
EDIT: I'm not too sure what's going on with your recovery... I hope someone else can answer that for you.
Click to expand...
Click to collapse
Thanks a lot. This is my wife's phone so she'd rather not to update if a data wipe is required. She's actually quite happy with 4.1.
Anything extra would only be a "good to have". I think I'll keep it on 4.1 until she switches to another phone.
I did download the slightly customized stock rom so that it could be updated in the future.
In fact, I still have stock recovery and the only reason I rooted was to disable carrier iq because it was doing funny things with the GPS, very annoying.
There is no other way to disable carrier iq without rooting...unfortunately...

View92612 said:
Thanks a lot. This is my wife's phone so she'd rather not to update if a data wipe is required. She's actually quite happy with 4.1.
Anything extra would only be a "good to have". I think I'll keep it on 4.1 until she switches to another phone.
I did download the slightly customized stock rom so that it could be updated in the future.
In fact, I still have stock recovery and the only reason I rooted was to disable carrier iq because it was doing funny things with the GPS, very annoying.
There is no other way to disable carrier iq without rooting...unfortunately...
Click to expand...
Click to collapse
If you flash that ROM over her current stock ROM, it should act just like an OTA update and replace the JB OS with the KK OS. It should also replace JB version Google apps with KK ones too.
If you decide to do this, you will need to do 3 things:
1) Make a backup just in case, but then copy the backup to your PC
2) Backup the internal SD to a PC and then format the internal storage. (see *2 below as to why)
3) After the flash, you will need to install the apk from the following thread and use it to install a Kitkat compatible CWM. If you don't while in recovery at any time, you may get stuck in what's called the Recovery Bootloop. Basically, every time you try to reboot the phone into the system (whether from a powered off state or from recovery), you will always go back to recovery.
The only bad thing about this recovery is that it can't read external SD cards, so anything you want to flash/backup will need to be stored on internal storage.
*2) Kitkat uses a different directory system for internal storage. If you were to not wipe the internal SD and managed to get the OTA working, it would wipe the drive for you automatically (which means all your data would be gone!).
However, with this flashable stock ROM, what will happen instead, is that all your data will remain, but will be hidden from view/access. If you have root, you can get it and move it, but it's a pain. Otherwise, your files are hidden from you, yet the system reads X amount of your internal storage as being occupied by "Miscellaneous" files, yet shows that nothing is there.
So just backup the files, then format the internal storage (which will leave her apps alone) before updating. Then flash that ROM and then copy the files back over.
All this is up to you and your wife as to whether or not you deem it to be worth the effort.

[Q] How allow update of ATT S3 4.1.2

I have an ATT S3 with 4.1.2 currently. It is rooted and has CWM recovery but still running stock OS.
I keep getting notifications of an OS OTA update to be installed, but it always fails. Can I get that to install by simply deleting the superuser app and selecting update option? Does the custom recovery also interfere?
Maybe the best way to ask is...
what would be the process I should use to get the update to install and get back to rooted/CWM?
I am no longer a "power user" and could easily live with the 4.1.2 OS, but the frequent 'demands' from ATT to install the update are bothersome.

Ota updates will only work with no root and a custom recovery.
Since you are on 4.1.2, you could flash stock 4.1.1, sim unlock, and run ota updates to 4.4.2. It's no the fastest but I feel it is the safest route.

movrshakr said:
I keep getting notifications of an OS OTA update to be installed, but it always fails. Can I get that to install by simply deleting the superuser app and selecting update option? Does the custom recovery also interfere?
Maybe the best way to ask is...
what would be the process I should use to get the update to install and get back to rooted/CWM?
I am no longer a "power user" and could easily live with the 4.1.2 OS, but the frequent 'demands' from ATT to install the update are bothersome.
Click to expand...
Click to collapse
audit13 said:
Ota updates will only work with no root and a custom recovery.
Since you are on 4.1.2, you could flash stock 4.1.1, sim unlock, and run ota updates to 4.4.2. It's no the fastest but I feel it is the safest route.
Click to expand...
Click to collapse
OTA is typically the safest way to update (as with any update, official or otherwise, you proceed at your own risk and no one here is responsible should anything negative happen to your phone and its software). If you do not want to take the time to do so, or feel the process is too tedious, you should be able to freeze the AT&T software update with an app like Titanium Backup. This should stop the nagging to install an OTA update. I have utilized this method before and it has worked quite well for me in the past.

aybarrap1 said:
...If you do not want to take the time to do so, or feel the process is too tedious, you should be able to freeze the AT&T software update with an app like Titanium Backup. This should stop the nagging to install an OTA update. I have utilized this method before and it has worked quite well for me in the past.
Click to expand...
Click to collapse
I have TitaniumBackup. What is the app that needs to be frozen to stop the update nags?
I am kind of surprised that uninstalling the superuser app is not enough to allow the update.
"Ota updates will only work with no root and a custom recovery."
"Ota updates will only work with ... a custom recovery."
Really? Did you mean,
Ota updates will only work with no root and NO custom recovery?

movrshakr said:
I have TitaniumBackup. What is the app that needs to be frozen to stop the update nags?
I am kind of surprised that uninstalling the superuser app is not enough to allow the update.
"Ota updates will only work with no root and a custom recovery."
"Ota updates will only work with ... a custom recovery."
Really? Did you mean,
Ota updates will only work with no root and NO custom recovery?
Click to expand...
Click to collapse
No root and no custom recovery is required for OTA updates.

movrshakr said:
I have TitaniumBackup. What is the app that needs to be frozen to stop the update nags?
Click to expand...
Click to collapse
If I remember correctly it is called "software update" but it will definitely consist of those words. I know it can be done because I did it when I was on rooted stock 4.1.1 and 4.1.2. Once I froze it, I never got notified.
Sent from my SAMSUNG-SGH-I747

aybarrap1 said:
If I remember correctly it is called "software update" but it will definitely consist of those words. I know it can be done because I did it when I was on rooted stock 4.1.1 and 4.1.2. Once I froze it, I never got notified.
Click to expand...
Click to collapse
Gosh, I have looked repeatedly through the (long) list of installed things in TitaniumBackup "Overview of app storage use..." list (the screen from which you freeze things...
and I simply cannot find the OTA update app. Indeed I did not see anything with the word 'update' in it.
Hoping someone can help me specifically identify the app that needs to be frozen in an S1 to stop the auto updates.
They are driving me crazy. Even though they fail, they often happen at night and leave the phone screen ON, on a screen waiting for an input, and the battery is hot. Happened once when not plugged in and drained to autoshutoff, so I woke to a dead battery.

movrshakr said:
Gosh, I have looked repeatedly through the (long) list of installed things in TitaniumBackup "Overview of app storage use..." list (the screen from which you freeze things...
and I simply cannot find the OTA update app. Indeed I did not see anything with the word 'update' in it.
Hoping someone can help me specifically identify the app that needs to be frozen in an S1 to stop the auto updates.
They are driving me crazy. Even though they fail, they often happen at night and leave the phone screen ON, on a screen waiting for an input, and the battery is hot. Happened once when not plugged in and drained to autoshutoff, so I woke to a dead battery.
Click to expand...
Click to collapse
It is there, I froze mine with Titanium Backup for about 18 months. It could be that the name is more like ATTUpdater. I also don't recall exactly because I have since installed a custom rom.

dawgdoc said:
It is there, I froze mine with Titanium Backup for about 18 months. It could be that the name is more like ATTUpdater. I also don't recall exactly because I have since installed a custom rom.
Click to expand...
Click to collapse
You're right! Found it.
It was AT&T Software Update. I had missed it before because, in portrait mode, the 'pdate' part of the name was not visible, and it just had not registered as I looked through them. Thanks heaps.

movrshakr said:
You're right! Found it.
It was AT&T Software Update. I had missed it before because, in portrait mode, the 'pdate' part of the name was not visible, and it just had not registered as I looked through them. Thanks heaps.
Click to expand...
Click to collapse
Glad to have been of service.

[Q] Recent SuperSU Updates - Issues

Figured I would start here in my device thread before trying the SuperSU thread.
Anybody have issues with SuperSU since the last few updates ago?
SuperSU does not even open. Root-dependent apps do not open. Titanium sits there at the initial screen "asking for root rights" until I kill the app. AdAway does not open... just goes right to a black screen until I kill the app. AdAway seems to work though, as my web surfing does not have ads.
I've also tried manually going in and applying the latest update via (philz) recovery.
Would I be safe to roll back to an older version of SuperSU?
Mods... if you're going to gun the thread, please at least point me in the right direction as I did search, but did not find anything related to recent issues on the Note 2 for SuperSU.
TIA for help and suggestions.

Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.

ceabbott2 said:
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
Click to expand...
Click to collapse
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.

lennykravitz2004 said:
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
Click to expand...
Click to collapse
For me, I just reflashed the ROM I was running at the time and that resolved it. Of course seeing that the update was " fixed" I attempted it and lost root again. I then did the same as before, wiped and relashed. I didn't do clean installs either time. Just wiped caches and reflashed. That sucks if you have to re-root. I mean, it's easy and all but it shouldn't have to be done.
D

Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.

DJ_Barcode said:
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
Click to expand...
Click to collapse
Thanks for the try. Did not work though.
Looks like I just need to re-flash the ROM.

My problem was odd. Before I discovered the aforementioned trick, I'd re-root with Chainfire or Kingo. I'd reboot, and my device would be rooted. But those two methods have an additional payload - they flash the stock recovery. So I'd ODIN the Philz Touch recovery back to the device, reboot, and root would be gone. Never figured out what was going on.

Yup. Issues with new version. Only last 2 or three updates.
They seemed to be perfectly fine with cm12 though.
Sent from my SPH-L900 using XDA Free mobile app

Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!

lennykravitz2004 said:
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
Click to expand...
Click to collapse
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app

jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
As always, thanks for your response. Your recommendation is what I've been doing, just wanted to follow-up on this and see if there was anything else I needed to consider or change as well.
My main concern was to make sure I was not going to run into any "big" issues (especially security) by staying on current version. Thanks for explaining where the issue really lies on this too. I'm obviously not a dev, however I do want to understand what is exactly going on and responses like yours always provide that type of info. :good: Thank you.
And, FWIW, using "fool proof" to describe a process only makes me more curious (and no, not in that way) about your suggestion. :laugh:
Now I HAVE to find out more about that option... (only after some of the best BBQ in all of the land - Sugarfire BBQ in STL )

jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
How do you disable auto update of binary on SuperSU? I keep seeing it in the notification bar, very annoying.

Stock Lollipoop rooted with SuperSU - but it keeps resetting everything I do

see #5 for problem
Hi guys,
so after quite some time with custom Roms I decided to go stock again as somehow I don't need root at all. Well, that's not true. I miss AdAway.
As there is no possibility to root the stock rom, is there ANY AdBlocker that works on Lollipop? AdBlock Plus doesn't (yet).

Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.

ckpv5 said:
Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.
Click to expand...
Click to collapse
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?

fBx said:
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?
Click to expand...
Click to collapse
Flash twrp recovery and root through the recovery. It'll ask you when you reboot the system if you want to root it
Sent from my HTC One_M8 using XDA Free mobile app

Huh. Didn't know it was THAT straightforward and I've been flashing my phones for years.
Well. I flashed TWRP and SuperSU 2.46, succeeded. But Adaway and Adfree don't work correctly. They block the ads but only until you reboot, then it's reverted, kinda like with a tethered jailbreak on iPhones.
What am I doing wrong here? Also the block is not like on KitKat - there it was really blocked, really removed, here only the images of the ads are removed but you still see the space they were supposed to be.
I also used a system app removal tool that also didn't work although it shows success. It just removes the installed data like updates.
When I delete apps manually via ES Explorer, they just reappear at the next reboot.
Root Checker says root is fine but it isn't supposed to behave like that and undo my changes.
What's wrong? Do I need another kernel maybe? As I said I went back to stock completely and updatet through to L.

I believe I got whats causing the issue.
After deleting a system app and rebooting, I got a message saying that the phone was restored from an "unnormal behaviour". Does Lollipop bring some kind of system restore point that just automatically restores itself when "weird" things like host file alteration happens? If yes, how do I get rid of that?

This phone has always had system files protected since KitKat. You need a kernel mod to delete system apps.
Don't know why the ad blockers aren't working. Adaway is working fine for me on stock US Dev Edition rooted. You said you are using Adaway and AdFree? Are you actually using both at the same time? maybe they are interfering with each other?

No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Maybe I should try installing xposed and see if it's gone after a reboot.

fBx said:
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?t=2701816
But unfortunately, flar2 hasn't had the time to update for LP. A user posted the kernel module in Post #210, but a subsequent user said it doesn't work. Custom ROMs have write protection disabled, as does Dev Edition stock ROM.
fBx said:
No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Click to expand...
Click to collapse
Odd, as mentioned, I've used AdAway for quite some time now, and don't have these issues.

Yes, very odd indeed. Well, if I don't get it sorted out somehow I might as well switch to Viper or some other close to stock custom Rom again, or make it Dev like you.

Things are getting worse, in 1 of 2 cases AdAway spits an error at me when trying to apply the fixes and the phone just reboots and undos everything. It's like some protection from rooting or changing anything although I am rooted. I don't understand it. I can't possibly be the only one having problems with root on Stock Lollipop
This is really annoying me. I think I'm better of just installing a custom rom and setting the phone up again, will cost me an hour but at least I'm done with the bugs.

Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.

fBx said:
Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.
Click to expand...
Click to collapse
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.

redpoint73 said:
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.
Click to expand...
Click to collapse
I also assume that's the reason. I've never been on a stock rom since I don't know when, but figured that actually I only wanted AdAway which would normally not require a custom rom per se... but as it didn't really work in the end (and also other root-requiring stuff), I went back to custom again. Well, it's not that it's that difficult to wipe the phone occasionally and set up a clean custom rom to get it back to perfect performance. Gonna go with it.

Security update with root

So, I'm new to rooting and this is my first Nexus device.
I'm loving it and all the options but now I'm getting a notification to update.
I see all the forums about hooking it up to a computer and using commands to do it all and then rerooting.
I was looking for an easier way.
I bought a Nexus 5 to play with because I liked this one so much and when OTAs came up, it would let me download them and reboot into CWM recovery and ask if I want to flash the ZIP.
This one just boots into TWRP (No CWM for 5x) and does nothing.
I found the update as a zip here:
<https://gist.github.com/jduck/744a6c8a9042e9c792b7>
My question is: can I just download it and use TWRP to flash it or is the sequence of commands on a computer the only way to do it?
Thank you in advance for your help and I apologize for my ignorance.
Gotta start somewhere though, right?

Hi !
I personnaly use NRT from Wugfresh for my Nexus 5x and my Nexus 7 2013, both rooted.
In "model type", select Nexus 5x and your build.
In "Restore/upgrade/downgrade", select "device is on/normal", then click "Flash stock+ unroot".
Select the build you want to install, it can dl and extract it for you, and select "No Wipe Mode" in order to keep your data and apps. (don't try to put your ota file here)
Go through the steps, and in the end, hit "Root" to root again.
I know there are others methods to apply just the OTA with command lines, but I never did it cause I never took the time to learn. I should do it, maybe it's faster with command lines.
Anyway this works, even if it takes a little time, and it is kind of automatic. But I strongly recommend you try both method to find what suits you most. Or wait for someone else to reply so you'll have more points of view !
Have fun with your N5x !

I like the idea of that.
Does it reinstall the superuser app automatically?
If so, which one?
And does it redo custom recovery?
And which one for that?
Sorry for all the questions but I purchased SuperSU and I don't want it to automatically download a different one and have to go through the steps to change a superuser app.

erichjelm said:
I like the idea of that.
Does it reinstall the superuser app automatically?
If so, which one?
And does it redo custom recovery?
And which one for that?
Sorry for all the questions but I purchased SuperSU and I don't want it to automatically download a different one and have to go through the steps to change a superuser app.
Click to expand...
Click to collapse
Use chainfires "flashfire" for this process
http://www.xda-developers.com/flashfire-updated-with-android-6-0-and-ota-support/

Darke5tShad0w said:
Use chainfires "flashfire" for this process
http://www.xda-developers.com/flashfire-updated-with-android-6-0-and-ota-support/
Click to expand...
Click to collapse
It's not working.

I have Xposed installed.
I unmarked all modules, rebooted, and tried again but to no avail.
Other than Xposed, no mods to the kernel.

erichjelm said:
I have Xposed installed.
I unmarked all modules, rebooted, and tried again but to no avail.
Other than Xposed, no mods to the kernel.
Click to expand...
Click to collapse
Are you using flashfire v0.28?
Xposed modifies the system so while you maybe able to get the ota it can prevent you from installing them even with flashfire.
Go to the flashfire thread and see if this is a problem with the app or because or xposed (most likely answer).
Otherwise find the ota threads and see if you can flash it through recovery (not the N version)

Yeah, it's that version of Flashfire.
I have the update zip but I'm afraid to just flash it.
I was hoping that I'd get some more help here.
Not that I don't appreciate your help.
Thank you, by the way.

erichjelm said:
Yeah, it's that version of Flashfire.
I have the update zip but I'm afraid to just flash it.
I was hoping that I'd get some more help here.
Not that I don't appreciate your help.
Thank you, by the way.
Click to expand...
Click to collapse
Thats at the end of my ability to help you with this particular problem, I have only owned a Nexus for 2 months and they are completely diff to Samsung plus I run pure nexus rom, you may just have to use a computer.

And I really appreciate it.
I'll just use a computer and do it.
Don't want to risk trying to flash the zip and bricking but I'm still curious.
Just not curious enough.
Haha.

Got it.
In case anyone needs to know for themselves, I wanted to post it here.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
I used that and it worked.
I didn't flash the Xposed zip and had to later on.
Worth it just to add it to the queue to save the time.
Everything else seems to be working fine thus far.
A few settings are changed (TinyCore was turned off and hidden apps in Smart Launcher 3 were unhidden) but that's nothing big.

erichjelm said:
Got it.
In case anyone needs to know for themselves, I wanted to post it here.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
I used that and it worked.
I didn't flash the Xposed zip and had to later on.
Worth it just to add it to the queue to save the time.
Everything else seems to be working fine thus far.
A few settings are changed (TinyCore was turned off and hidden apps in Smart Launcher 3 were unhidden) but that's nothing big.
Click to expand...
Click to collapse
That is the same manipulation I explained in post 2, but with Flashfire, without using a computer. And full automated, where with nrt you have to factory reset and root later. I'll try it next time ! And yeah, the version of SuperSu is always the latest, and if it is not, it will update via play store (I bought it as well ^^)

Greedybro said:
That is the same manipulation I explained in post 2, but with Flashfire, without using a computer. And full automated, where with nrt you have to factory reset and root later. I'll try it next time ! And yeah, the version of SuperSu is always the latest, and if it is not, it will update via play store (I bought it as well ^^)
Click to expand...
Click to collapse
This one didn't unroot. Just uninstalled Xposed. Kept all my data and stuff. Apps stayed signed in even. I was afraid because I heard "factory reset" in yours. Or something to that nature. The only thing I'm having problems with now is Tapatalk told me to check my adblock settings and won't load anything. I'll have to look up what's wrong with it. Other than that, it's doing all right.

You are right and wrong, it unroots but reroots in the process. Same I did when I used nrt. And as i didn't wipe data, apps stayed sign in as Well.
But i tried flashfire on my nexus 7 and I it is way more useful and faster than nrt. I am adopting it !