Related
Hi,
I got an update on my LG G2 D802 and i have ROOT, i downloaded SuperSU because someone told me that i can update my device with it, but i dont know how.
Can someone explain me how to use it? what should i do in the SuperSU to update my device?
Thank you.
Uh...i don't think supersu can update your device. All it does is handle root.
Gesendet von meinem LG-d802 mit Tapatalk
ckyy said:
Uh...i don't think supersu can update your device. All it does is handle root.
Gesendet von meinem LG-d802 mit Tapatalk
Click to expand...
Click to collapse
But i saw that it have OTA Survival in the Settings.
Are you sure that i cant to update with it?
On my previous theard i asked if i can update, and someone told me that he updated his G2 with the SuperSU, but i dont know how to do this too..
itaylubo2 said:
But i saw that it have OTA Survival in the Settings.
Are you sure that i cant to update with it?
On my previous theard i asked if i can update, and someone told me that he updated his G2 with the SuperSU, but i dont know how to do this too..
Click to expand...
Click to collapse
OTA survival means that when your carrier sends out an OTA update for your device, you should still have root afterwards. Normally without OTA survival you will lose root after updating. SuperSU has nothing to do with updates, it is simply a firewall between apps and the root of your device. :good:
If you have OTA survival turned on in SuperSU, AND you have stock recovery, then theoretically, you can do the OTA update and still have root when it's finished. But it isn't 100% successful.
Also OP...
http://forum.xda-developers.com/showthread.php?t=2443934
souleman said:
If you have OTA survival turned on in SuperSU, AND you have stock recovery, then theoretically, you can do the OTA update and still have root when it's finished. But it isn't 100% successful.
Click to expand...
Click to collapse
I have stock recovery, so i should turn on the OTA Survival in the SuperSU and to start to update?
I saw in the settings of the SuperUser that it have also OTA Survival, should i turn it on too?
Thank you.
DO NOT DO OTA'S IF YOU ROOTED. Period.
khaytsus said:
DO NOT DO OTA'S IF YOU ROOTED. Period.
Click to expand...
Click to collapse
I received an ota last night (whilst very drunk) . I have a rooted but otherwise completely stock rom with stock recovery and the ota installed without a problem and I remained rooted even though I hadn't set my superSU to maintain root. My system updated from 10a to 10f.
It would appear that an ota will install with root as long as you have stock recovery and have not made changes to the system partition. (apart from the su binary of course.)
bobsie41 said:
I received an ota last night (whilst very drunk) . I have a rooted but otherwise completely stock rom with stock recovery and the ota installed without a problem and I remained rooted even though I hadn't set my superSU to maintain root. My system updated from 10a to 10f.
It would appear that an ota will install with root as long as you have stock recovery and have not made changes to the system partition. (apart from the su binary of course.)
Click to expand...
Click to collapse
Yes, but I like to keep things simple for people.
Recovery is what will get you, or a modified ROM. But.. Ah, it doesn't matter, people will do it anyway.
itaylubo2 said:
I have stock recovery, so i should turn on the OTA Survival in the SuperSU and to start to update?
I saw in the settings of the SuperUser that it have also OTA Survival, should i turn it on too?
Thank you.
Click to expand...
Click to collapse
You shouldn't have SuperSU and SuperUser both on the phone. Remove one of them (probably SuperUser as it doesn't play well with some things).
It is recommended not to do an OTA if you are rooted. If you wait a few days, someone will have a flashable version of the OTA on here.
Having a modified stock rom very rarely causes any issues. It can, but it doesn't very often. 99% of the time, it's because someone is running a different recovery, and still blames it on the ROM. But unless your ready to flash it back to how it was when you opened the box, just wait a couple days.
souleman said:
You shouldn't have SuperSU and SuperUser both on the phone. Remove one of them (probably SuperUser as it doesn't play well with some things).
It is recommended not to do an OTA if you are rooted. If you wait a few days, someone will have a flashable version of the OTA on here.
Having a modified stock rom very rarely causes any issues. It can, but it doesn't very often. 99% of the time, it's because someone is running a different recovery, and still blames it on the ROM. But unless your ready to flash it back to how it was when you opened the box, just wait a couple days.
Click to expand...
Click to collapse
But i have stock recovery and stock ROM, it is matter?
I realy dont know what to do when the Kitkat 4.4 will comes...
itaylubo2 said:
But i have stock recovery and stock ROM, it is matter?
I realy dont know what to do when the Kitkat 4.4 will comes...
Click to expand...
Click to collapse
To be safe you could always unroot your phone before updating since everything is stock you won't be losing much and you won't be taking any unnecessary chances. Plus the root might not stick with such a big update even with root survival so you might have to reroot it again after the update anyways.
This is pretty much the same thing everyone had already said, I don't think anyone here would tell you it's worth taking the risk -even if it's just a slight risk since you don't have a custom recovery installed- that will only be saving you the few minutes it'll take to reroot your phone.
Sent from Sprint LG G2
kcerica said:
To be safe you could always unroot your phone before updating since everything is stock you won't be losing much and you won't be taking any unnecessary chances. Plus the root might not stick with such a big update even with root survival so you might have to reroot it again after the update anyways.
This is pretty much the same thing everyone had already said, I don't think anyone here would tell you it's worth taking the risk -even if it's just a slight risk since you don't have a custom recovery installed- that will only be saving you the few minutes it'll take to reroot your phone.
Sent from Sprint LG G2
Click to expand...
Click to collapse
How i Unroot my phone? just doing Factory Reset?
There should be an unroot option in the supersu settings
Sent from Sprint LG G2
itaylubo2 said:
How i Unroot my phone? just doing Factory Reset?
Click to expand...
Click to collapse
Uninstall SuperUser, then in SuperSu there is an option to unroot the phone.
souleman said:
Uninstall SuperUser, then in SuperSu there is an option to unroot the phone.
Click to expand...
Click to collapse
I downloaded SuperSU, and after i delete it.
and i did Reboot, and the Superuser dissapeard, but i still have ROOT, i can use Freedom, Market Unlocker and Auto Hide Soft Keys.
Now i downloaded SuperSU again, and i saw in the "Description" that the SuperUser should be removed when i download the SuperSU.
If i'll do Full Unroot from the SuperSU, it will work on LG G2 D802 with stock ROM&Recovery?
Thank you very much !!!
itaylubo2 said:
I downloaded SuperSU, and after i delete it.
and i did Reboot, and the Superuser dissapeard, but i still have ROOT, i can use Freedom, Market Unlocker and Auto Hide Soft Keys.
Now i downloaded SuperSU again, and i saw in the "Description" that the SuperUser should be removed when i download the SuperSU.
If i'll do Full Unroot from the SuperSU, it will work on LG G2 D802 with stock ROM&Recovery?
Thank you very much !!!
Click to expand...
Click to collapse
Yup. Full Unroot in SuperSu will delete the files from the /system partition that give you access to root.
souleman said:
Yup. Full Unroot in SuperSu will delete the files from the /system partition that give you access to root.
Click to expand...
Click to collapse
It will work for 100%? In the Root Exporer, i search in the /system/bin for the "su" and i didnt found it, also i didnt found the SuperUser.apk in the /system/app, i can find only in the /system/xbin the "su" file.
It should be like this? because i saw some videos on Glalaxy Note 2 that he have all except the su file in the /system/xbin..
itaylubo2 said:
It will work for 100%? In the Root Exporer, i search in the /system/bin for the "su" and i didnt found it, also i didnt found the SuperUser.apk in the /system/app, i can find only in the /system/xbin the "su" file.
It should be like this? because i saw some videos on Glalaxy Note 2 that he have all except the su file in the /system/xbin..
Click to expand...
Click to collapse
There shouldn't be an su files after unroot. Is either superuser.apk or supersu.apk in either /system/app or /data/app?
Who knew it would be that simple? Towelroot has rooted my Note 3, I'm finally back with Titaniuam Backup Pro and Knox is 0x0!
Amazing.
However I've installed CF's SuperSU and it fails to update the binaries.
I've frozen KNOX in Titanium and rebooted but they still won't update.
Do I even need to update them?
Also, if I try to install CWM will that trip KNOX?
jonboyuk said:
Who knew it would be that simple? Towelroot has rooted my Note 3, I'm finally back with Titaniuam Backup Pro and Knox is 0x0!
Amazing.
However I've installed CF's SuperSU and it fails to update the binaries.
I've frozen KNOX in Titanium and rebooted but they still won't update.
Do I even need to update them?
Also, if I try to install CWM will that trip KNOX?
Click to expand...
Click to collapse
Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip . Don't flash it. Unzip it. Then go to /common folder and install superuser.apk. Run SuperSU from App Drawer, and let binary to update. Now you have it working. And don't worry about disabling KNOX. Just disable it.
By flashing CWM you will trip knox.
alexpowermetal said:
Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip . Don't flash it. Unzip it. Then go to /common folder and install superuser.apk. Run SuperSU from App Drawer, and let binary to update. Now you have it working. And don't worry about disabling KNOX. Just disable it.
By flashing CWM you will trip knox.
Click to expand...
Click to collapse
Fantastic. thank you Alex. That worked perfectly. As you're in the know I'll ask you another question (or two)!
Because I don't want to trip knox I won't install CWM. As such I can't make a nandroid backup. I want to install the xposed framework and Wanam modules...but it strongly recommends a backup. Is it risky for me to do this?
Any idea what happens when an OTA update is release by Samsung?
jonboyuk said:
Fantastic. thank you Alex. That worked perfectly. As you're in the know I'll ask you another question (or two)!
Because I don't want to trip knox I won't install CWM. As such I can't make a nandroid backup. I want to install the xposed framework and Wanam modules...but it strongly recommends a backup. Is it risky for me to do this?
Any idea what happens when an OTA update is release by Samsung?
Click to expand...
Click to collapse
I took the yolo approach and installed xposed and wanam with no problems. As you say don't want to risk loosing warranty but knox is still fine and now I have a customisable phone.
No idea about ota samsung update sorry.
pjtb said:
I took the yolo approach and installed xposed and wanam with no problems. As you say don't want to risk loosing warranty but knox is still fine and now I have a customisable phone.
No idea about ota samsung update sorry.
Click to expand...
Click to collapse
Hahaha, I too have just taken the YOLO approach (as much as I hate that phrase!). Thanks mate!
jonboyuk said:
Hahaha, I too have just taken the YOLO approach (as much as I hate that phrase!). Thanks mate!
Click to expand...
Click to collapse
Actually you can make nandroid backup without costume recovery. Just use Online Nandroid Backup. It makes nandroid backup in CWM or TWRP formats.
And then you can use Nandroid Manager to restore your backup. Although I still can't figure it out on how to restore a backup if you soft brick you phone.
alexpowermetal said:
Actually you can make nandroid backup without costume recovery. Just use Online Nandroid Backup. It makes nandroid backup in CWM or TWRP formats.
And then you can use Nandroid Manager to restore your backup. Although I still can't figure it out on how to restore a backup if you soft brick you phone.
Click to expand...
Click to collapse
Cheers, not heard of that before. I'll have to look into it!
alexpowermetal said:
Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip . Don't flash it. Unzip it. Then go to /common folder and install superuser.apk. Run SuperSU from App Drawer, and let binary to update. Now you have it working. And don't worry about disabling KNOX. Just disable it.
By flashing CWM you will trip knox.
Click to expand...
Click to collapse
Not quite sure what to do here. I've ODINed twice and just tried this approach, but I cannot get the binaries to update successfully. I keep getting the failure. Any ideas?
danjng said:
Not quite sure what to do here. I've ODINed twice and just tried this approach, but I cannot get the binaries to update successfully. I keep getting the failure. Any ideas?
Click to expand...
Click to collapse
Now you can install SuperSU from play store as it was updated and now it should update binaries without a problem. Install SuperSU, open it, press "update binaries", use "normal" method (not CWM/TWRP), when it will ask you to disable knox, press "disabled knox" and then reboot.
I'm having a similar issue that's pretty frustrating. I root my phone and install supersu, asks to disable knox and everything works great until about a day after, I try to open Supersu and it says I need to update binaries but it will not update. So I have to uninstall supersu, root again then install Supersu again! Right now it's working fine but I'm scared to open Supersu in fear that it will happen all over again. It's been a pain! I even tried flashing the supersu zip through Safestrap to see if it helps but it did the same thing. Is anyone having a similar issue or can anyone help with this?
alexpowermetal said:
Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip . Don't flash it. Unzip it. Then go to /common folder and install superuser.apk. Run SuperSU from App Drawer, and let binary to update. Now you have it working. And don't worry about disabling KNOX. Just disable it.
By flashing CWM you will trip knox.
Click to expand...
Click to collapse
Isn't the point of using towelroot to prevent tripping KNOX? When trying to update my SuperSU binaries it asks me to disable KNOX, won't this trip it?
toews said:
Isn't the point of using towelroot to prevent tripping KNOX? When trying to update my SuperSU binaries it asks me to disable KNOX, won't this trip it?
Click to expand...
Click to collapse
As far as I understand, it disables software part of knox, so it (knox) wont prevent you to update binaries. Anyway it won't trip knox.
Binary issue
fsolares said:
I'm having a similar issue that's pretty frustrating. I root my phone and install supersu, asks to disable knox and everything works great until about a day after, I try to open Supersu and it says I need to update binaries but it will not update. So I have to uninstall supersu, root again then install Supersu again! Right now it's working fine but I'm scared to open Supersu in fear that it will happen all over again. It's been a pain! I even tried flashing the supersu zip through Safestrap to see if it helps but it did the same thing. Is anyone having a similar issue or can anyone help with this?
Click to expand...
Click to collapse
I have the same problem with binary issues on the towelroot method. It works at first but after a reboot it says "Update binary files" So i do that and then it says "Failed" I have the verizon Note 3 on 4.4.2. I found a temp fix for this when having issues with binary update. You don't have to re-root your phone.
1. Save the apk super su to your phone.
2. After having problems with binary then uninstall the supersu app from your phone
3. Install the supersu apk using "ES File Explorer" Then load the app it'll still say failed.
4. Reboot the phone and open up Supersu and you won't get the binary issue
I know its annoying work around but its what i have figured out and it works.
Guys, can you help with 2 questions please?
I have a I9505 with 4.4.2 branded rom (ZTO) with towel root (know still 0x0) and disable OTA updates, I can't find a perfect custom rom (always a feature not working, missing or the interface it's a mess/colorfull), now I just want the stock unbranded rom.
1 - What is the safest way to flash the stock rom without trip knox?
2- After that, can I enable back OTA updates with root?
Thanks!
fsolares said:
I'm having a similar issue that's pretty frustrating. I root my phone and install supersu, asks to disable knox and everything works great until about a day after, I try to open Supersu and it says I need to update binaries but it will not update. So I have to uninstall supersu, root again then install Supersu again! Right now it's working fine but I'm scared to open Supersu in fear that it will happen all over again. It's been a pain! I even tried flashing the supersu zip through Safestrap to see if it helps but it did the same thing. Is anyone having a similar issue or can anyone help with this?
Click to expand...
Click to collapse
Why are you re-rooting?
---------- Post added at 03:01 PM ---------- Previous post was at 02:57 PM ----------
jashton23 said:
I have the same problem with binary issues on the towelroot method. It works at first but after a reboot it says "Update binary files" So i do that and then it says "Failed" I have the verizon Note 3 on 4.4.2. I found a temp fix for this when having issues with binary update. You don't have to re-root your phone.
1. Save the apk super su to your phone.
2. After having problems with binary then uninstall the supersu app from your phone
3. Install the supersu apk using "ES File Explorer" Then load the app it'll still say failed.
4. Reboot the phone and open up Supersu and you won't get the binary issue
I know its annoying work around but its what i have figured out and it works.
Click to expand...
Click to collapse
Same phone and carrier. Thanks for this. :good:
alexpowermetal said:
Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip . Don't flash it. Unzip it. Then go to /common folder and install superuser.apk. Run SuperSU from App Drawer, and let binary to update. Now you have it working. And don't worry about disabling KNOX. Just disable it.
By flashing CWM you will trip knox.
Click to expand...
Click to collapse
I downloaded SuperSU from the link your provided, copied just the superuser.apk from /common folder to my Note 3 and then install.
Run SuperUser, which asked to disable KNOX (I clicked OK). KNOX disabled.
However, there is no prompt for the binary update. Am I doing anything wrong?
you could also flash the zip with mobile odin pro (available in play store)
*flies away*
Sent from my SM-N9005 using XDA Premium 4 mobile app
Killberty said:
you could also flash the zip with mobile odin pro (available in play store)
*flies away*
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wouldn't this require TWRP? I don't have that, since installing TWRP will trip KNOX.
Mod Edit quote removed
and i just told u another method man...
i am not tired of it, i enjoy helping people, giving back support i once recieved myself when i was a noob
but if i post something, you should read it, and maybe you are even smart enough to type in "mobile odin pro" in that play store instead of just commenting - if you had done that, you'd have seen that no custom recovery is required for flashing
Sent from my SM-N9005 using XDA Premium 4 mobile app
Mod Edit
Thread cleaned
If you want to help users , great.
If you do not want to help users , that is also fine.
But there is no need to insult each other.
Please respect the XDA RULES
Thank you
malybru
Forum Moderator
My device is D6503. I had stock .314 rooted rom with locked bootloader. I updated via OTA to .167 and root remained except system partition write.
For this SuperSu was moved to system partition before update and also Survival mode was swithced on!
Another useful information is that if you do the SD Card fix on .314 it will remain after the update, so still all apps will be able to write on SD.
I was on Hungarian T-mobil .314 fw, unbranded phone.
UPDATE:
If you run the RIC killer from below, you will be able to mount system rw:
RIC killer
You lose no data during the update, even Xposed moduls works like before.
I thought this can be an useful information for everyone, if not moderators can delete the thread.
Which stock 314 firmware did you have before? Canada / USA stock 314 doesn't let you do ota, it forces you to use pcc for the update and you lose root.
bdithug said:
Which stock 314 firmware did you have before? Canada / USA stock 314 doesn't let you do ota, it forces you to use pcc for the update and you lose root.
Click to expand...
Click to collapse
Hungarian T-mobil, but the phone is unbranded. Also it is important to not have custom recovery installed, because then OTA won't install. You can only root if you want to be able to update via OTA in the future.
bojan1986819 said:
Hungarian T-mobil, but the phone is unbranded. Also it is important to not have custom recovery installed, because then OTA won't install. You can only root if you want to be able to update via OTA in the future.
Click to expand...
Click to collapse
Hmm.. So flash a stock 314 fw (Hungarian tmobile confirmed) , root but don't install custom recovery, then do ota and it will preserve root? Can you install a custom recovery afterwards?
bdithug said:
Hmm.. So flash a stock 314 fw (Hungarian tmobile confirmed) , root but don't install custom recovery, then do ota and it will preserve root? Can you install a custom recovery afterwards?
Click to expand...
Click to collapse
I'm not fully sure because you lose system partition write access after the OTA, so this have to be checked by someone. I don't install custom recovery because SD card fix and Xposed is all I need and I want to keep the possibility to use OTA updates in the future. I don't like when I have to reinstall everything and set my preferences again if I want to have a new fw with root, without exploit.
If someone checks this I will add the result to the first post.
Did anyone else duplicate this method?
bojan1986819 said:
I'm not fully sure because you lose system partition write access after the OTA, so this have to be checked by someone. I don't install custom recovery because SD card fix and Xposed is all I need and I want to keep the possibility to use OTA updates in the future. I don't like when I have to reinstall everything and set my preferences again if I want to have a new fw with root, without exploit.
If someone checks this I will add the result to the first post.
Click to expand...
Click to collapse
I did another similar way: created my own personal rooted zip file and flashed. I loosed access to mount system..
Hope someone can fix it.
MichaelWT said:
Did anyone else duplicate this method?
Click to expand...
Click to collapse
Yes someone in the thinktank thread did the same. So it seems like if you can do OTA and switch on Survival mode it works.
Yes you can, but you won't be able to mount r/w system untill devs find a kernel xploit to make it adbd insecure.
hi mates
more information would be of much more help, please :good:
ota marashmellow
I have rooted android 5.1.1, now I got 6.0 ota, can I update, is root preserved or I will lost my root after updating.
do not. two things can do, wait out root 6 and continue with 5.1.1 (root) or OTA update and lose root
I used towel root to root my S4, and I somehow allowed an auto update, which downloaded the updated, tried to install but failed. But I lost my root.
I am running 4.4.2 - Kitkat right?
So I don't have root, and I cannot update my phone - Is it possible for me to root it again? If so is there a link to instructions?
Thanks in advance, the DoridForums people sent me here -
Randy72560 said:
I used towel root to root my S4, and I somehow allowed an auto update, which downloaded the updated, tried to install but failed. But I lost my root.
I am running 4.4.2 - Kitkat right?
So I don't have root, and I cannot update my phone - Is it possible for me to root it again? If so is there a link to instructions?
Thanks in advance, the DoridForums people sent me here -
Click to expand...
Click to collapse
I dunno what you are running.
1. You can take a look in your Settings - About device (Pic attached).
2. Try again Towel Root if you still running android 4.4.2 for root again your device.
3. Tell us how it works.
* You can download OTA udpates but you can't install them when you are rooted. Root your device modify system. It changes of OFFICIAL to CUSTOM. OTA detects it and give you a error when you try to install the update.
Ok attached is my about phone info -
I just tried towel root again, and it says this phone is not currently supported. So again, thought I would see what my easy options might be.
I can't post an image or links, Android version says 4.4.2 - If that's what you need? If not let me know which number you need
Use CF-Autoroot to root instead of Towelroot. While CF-Autoroot requires the Odin software to use, it's far more consistent in its results since it temporarily replaces the existing recovery with a recovery that will install SuperSU into the /system partition. Unlike Towelroot, CF-Autoroot is version agnostic, meaning it will work regardless of the version of Android installed.
There is an entire thread on CF-Autoroot. Hit the search bar at the top of the page and I'm sure you'll find it.
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.