Database Info

[Q] Root issues after 4.4.2 update

I manually sideloaded 4.4.2 onto my nexus 5 all was good and root appeared to be working as nova,lightflow,adblock all asked for permission upon reauthentication. However when i went into supersu it prompted for a updated. Which I continued as normal but it fails. Even after reboot.
I've even tried using cf-autoroot again to no luck.
Whats the best solution for me.
Nexus 5 - 4.4.2 KOT49H from 4.4 KRT16M
Root : Supersu by chainfire using cf-autoroot.
Nova launcher seems to be able to use root as does lightflow and root explorer.
Adblock asks but cannot change the files it needs.
Any extra information needed I will gladly produce

Try flashing su zip? - https://mega.co.nz/#!xk92nAZI!t2-Mhj_BbBMlYVj6OLC6xT2ycAMixnETqnUdqFXkr9w
Sent from my Nexus 5 using Tapatalk

Ben36 said:
Try flashing su zip?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't have a custom recovery and sideloading this fails.

brichardson1991 said:
I don't have a custom recovery and sideloading this fails.
Click to expand...
Click to collapse
use fastboot to flash a custom recovery?
basic stuff man.

Zepius said:
use fastboot to flash a custom recovery?
basic stuff man.
Click to expand...
Click to collapse
I thought not having a custom recovery was the way to ensure OTA updates?
But if I'm not going to be getting OTA then I'll go for it.
Whats the best one for Nexus 5, as i used to use Clockworkmod on Galaxy S2 but i've read TWRP is better ?

brichardson1991 said:
I thought not having a custom recovery was the way to ensure OTA updates?
But if I'm not going to be getting OTA then I'll go for it.
Whats the best one for Nexus 5, as i used to use Clockworkmod on Galaxy S2 but i've read TWRP is better ?
Click to expand...
Click to collapse
custom recoveries in themselves do not stop a OTA. what stops a OTA is the fact that people do system mods and that breaks the OTA.
as for which is best, that falls under best rom/kernel type stuff. pick one.

brichardson1991 said:
I thought not having a custom recovery was the way to ensure OTA updates?
But if I'm not going to be getting OTA then I'll go for it.
Whats the best one for Nexus 5, as i used to use Clockworkmod on Galaxy S2 but i've read TWRP is better ?
Click to expand...
Click to collapse
OTA only check the system partiiton, custom recovery won't spoil OTA.
and stock recovery = no recovery

I prefer TWRP.
If you currently have root access, download teh TWRP app from the Play Store and it'll install itself

brichardson1991 said:
I thought not having a custom recovery was the way to ensure OTA updates?
But if I'm not going to be getting OTA then I'll go for it.
Whats the best one for Nexus 5, as i used to use Clockworkmod on Galaxy S2 but i've read TWRP is better ?
Click to expand...
Click to collapse
You can't have ANY modification. Recovery, Kernel, Binaries(Xposed), factory apps all have to be in tact for the official OTA to work. You'll need to find to flashable version, or flash clean back to absolute stock.

Decimation said:
You can't have ANY modification. Recovery, Kernel, Binaries(Xposed), factory apps all have to be in tact for the official OTA to work. You'll need to find to flashable version, or flash clean back to absolute stock.
Click to expand...
Click to collapse
So I flashed TWRP using the app.
and now supersu is up to date.
So in future all OTA updates won't work and i will just have to sideload them like i did with these 2 ?
If that's the case I'm fine with that.

For future OTA you can flash the OTA after the download is provided here, then flash SuperSU immediately after. Also just double check if SuperSU is updated so you have the most recent version.
Thats what I did for the 4.4.1 and 4.4.2 OTAs and I never lost root. All done via TWRP

Thanks all. I've sorted it out. Can close this topic now.
Sent from my Nexus 5 using XDA Premium 4 mobile app

[Q] Restoring my recovery, but not wiping

Hi all,
I have searched the web, but haven't found an exact answer to my question.
I have a Nexus 5, currently on 4.4.2 (KOT49H). I am unlocked, rooted + Xposed and have TWRP. I want to update to 4.4.4 preferably OTA, officially. I would like to be able to use OTA updates from now on if possible.
Currently, if I disable Xposed, and use Suvival Mode in SuperSU and try to install the OTA update, TWRP intervenes and doesn't let me.
I would like to replace TWRP with the stock recovery so I can update OTA in the future. I don't want to wipe the phone to achieve this if possible. If this isn't possible, could someone step through how to update to 4.4.4 with TWRP installed — I'm on a mac also.

Flash the stock recovery image in fastboot
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Flash the stock recovery image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Where can I find the stock recovery? Is that this: *w*w*w*.developers.google.com/android/nexus/images

providedbike said:
Where can I find the stock recovery? Is that this: *w*w*w*.developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes, extract the image and then the zip file
Sent from my Nexus 5 using XDA Free mobile app

OTA is the least compatible and hardest way to update. Why do you want to use this method? It's the worst option available to you.

rootSU said:
OTA is the least compatible and hardest way to update. Why do you want to use this method? It's the worst option available to you.
Click to expand...
Click to collapse
Because it would seem easier for me—AFAIK. Although this didn't work, this workflow sounds appealing to me every time an update comes out:
- Disable Xposed
- Enable Survival Mode in SuperSU
- Install OTA update
- Re-enable Xposed, done.
No USB, no computer, no terminal.
Is there another way to achieve this?

providedbike said:
Because it would seem easier for me—AFAIK. Although this didn't work, this workflow sounds appealing to me every time an update comes out:
- Disable Xposed
- Enable Survival Mode in SuperSU
- Install OTA update
- Re-enable Xposed, done.
No USB, no computer, no terminal.
Is there another way to achieve this?
Click to expand...
Click to collapse
Running a rooting rom without a custom recovery is dangerous IMHO.
Without having to lose custom recovery
1) Download latest rooted stock ROM
2) Flash
3) Enable Xposed

rootSU said:
Running a rooting rom without a custom recovery is dangerous IMHO.
Without having to lose custom recovery
1) Download latest rooted stock ROM
2) Flash
3) Enable Xposed
Click to expand...
Click to collapse
Does this apply for the stock rom? I'm rooted, but still stock...

providedbike said:
Does this apply for the stock rom? I'm rooted, but still stock...
Click to expand...
Click to collapse
Yes, whenever there is a new stock ROM, someone makes a rooted stock flashable zip of it. Also if you make any small changes to system, sometimes like adblocking, OTA will fail but flashable zip of rom will just override all that bs.
latest 4.4.4 rooted stock rom is in a thread which you can find i the resources section of the sticky-roll-up thread. You can get there via my signature.
That way, you can take a nandroid backup so if anything goes wrong after the update, you can do a full restore, where as with OTA you will not be able to with stock recovery.

rootSU said:
Yes, whenever there is a new stock ROM, someone makes a rooted stock flashable zip of it. Also if you make any small changes to system, sometimes like adblocking, OTA will fail but flashable zip of rom will just override all that bs.
latest 4.4.4 rooted stock rom is in a thread which you can find i the resources section of the sticky-roll-up thread. You can get there via my signature.
That way, you can take a nandroid backup so if anything goes wrong after the update, you can do a full restore, where as with OTA you will not be able to with stock recovery.
Click to expand...
Click to collapse
Ok great that's very helpful, thanks!

providedbike said:
Ok great that's very helpful, thanks!
Click to expand...
Click to collapse
No problem.
I just think that way is easier....I wouldn't want you putting extra work in, if you dont have to. It also gives you more freedom to work with mods in the future too, or kernels etc

rootSU said:
No problem.
I just think that way is easier....I wouldn't want you putting extra work in, if you dont have to. It also gives you more freedom to work with mods in the future too, or kernels etc
Click to expand...
Click to collapse
Yep it's all good. For some reason, I had this little fear of the fact it's an official stock rom, that's been "toyed" with. But of course that makes no sense really, considering I'm willing to install many third party apps and processes that could easily alter/mess my phone up.
Do the rooted stock roms get released fairly rapidly after the official one is released?

providedbike said:
Yep it's all good. For some reason, I had this little fear of the fact it's an official stock rom, that's been "toyed" with. But of course that makes no sense really, considering I'm willing to install many third party apps and processes that could easily alter/mess my phone up.
Do the rooted stock roms get released fairly rapidly after the official one is released?
Click to expand...
Click to collapse
Yeah. as soon as the factory image is released. Maybe a day or two. Which is before 99% of people even receive the OTA notification

rootSU said:
Yeah. as soon as the factory image is released. Maybe a day or two. Which is before 99% of people even receive the OTA notification
Click to expand...
Click to collapse
Perfect, thanks for clearing things up for me.
Just checking, I'll make a backup before I flash, but technically, will all my data still be there if all goes to plan?

providedbike said:
Perfect, thanks for clearing things up for me.
Just checking, I'll make a backup before I flash, but technically, will all my data still be there if all goes to plan?
Click to expand...
Click to collapse
Yep. the /data partition is not touched. Just /system and /boot (ROM and Kernel)

rootSU said:
Yep. the /data partition is not touched. Just /system and /boot (ROM and Kernel)
Click to expand...
Click to collapse
Great I'll do it tonight

Semi-bricked OPO, need help restoring

Hi everyone, I have a big problem. Recently I got the phone and decided to root it. I used this guide: http://forum.xda-developers.com/showthread.php?t=2788632
I successfully rooted 4.4.2. using TWRP method, no problem but I when I decide it to update to OTA XNPH30O - 4.4.4. after clicking install, it sends me back to TWRP recovery page and I never able to install the update. What I did next was probably what got me in this situation. I went to recovery page, I did both format data and advance wipe but turns out it didn't clean everything on the SD DIR. So now when I restart the system, it just hangs on the OPO page.
Please how do I restore to the original factory ROM so I can re-root it again. Currently I have only access to fastboot and TWRP recovery page. I'm very noob at this and the last thing I want is to messed up the bootloader so I need someone to guide me through it step by step.
Thank You

Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon

timmaaa said:
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?

You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first

Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
The OTA updates are bugged.
You might want to consider using a custom ROM.

Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
Like I said just go to my index thread, there are full versions of every release of CM11S in the Stock Images thread. Just flash whichever version you wavy to be on.
Transmitted via Bacon

EddyOS said:
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Click to expand...
Click to collapse
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Gamm86 said:
The OTA updates are bugged.
You might want to consider using a custom ROM.
Click to expand...
Click to collapse
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.

Majestic_12 said:
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Click to expand...
Click to collapse
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)

Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon

timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed.zip (taken from the images thread)

Thank you all for helping me with this, I know all this noob asking is lame but I need to ask in order for me to learn.
EddyOS said:
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
link (taken from the images thread)
Click to expand...
Click to collapse
I did just that using fastboot, I flashed ROM XNPH33R which is supposedly 4.4.4 and I again rooted it afterward with TWRP/SuperSU method. But now I think I need to go through a checklist on why my battery still isn't doing good as many would say. I wouldn't consider it draining but it does go down quite fast when I put it to use. Evening idling for 8 hours the phone still drains about 20% when I woke up.
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
I did just that on using the XNPH33R fastboot img but now that I think about it, should I use the zip method instead but that's putting the files onto DIR and flash it from TWRP right?
EddyOS said:
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Click to expand...
Click to collapse
Well I did all that, now I'm on 33R and is rooted, is there anything I can do to help improve the battery life? I';m still experiencing a drain.

OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?

Majestic_12 said:
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Click to expand...
Click to collapse
Getting rid of bloat isn't really going to increase the duration of your battery. Finding which apps are driving your battery the most or causing wakelocks and then dealing with them by using something like Greenify will have a positive effect though.
Transmitted via Bacon

About Root in 05Q

Hello guys!!!, Today I get the new OTA with the firmware 05Q and I install it. I see in the forum a version of 05Q rooted LINK HERE
I only want to ask if anyone know another way of get root actually or if I should wait until our amazing toolkits for 1+1 get updated.
Thanks i nadvance!!! :cyclops:

You can gain root following, This thread. If you already have a custom recovery install, might be easier to install the pre-rooted 05QA. I went the second route.
P.S. That toolkit will root 05QA, just does not have the new firmware to go back to stock.

I have a custom recovery installed ofc, if I install the pre-rooted 05Q I lost all my data and apps? Should I do a factory reset? Thanks for your fast answer mate!!

Istvan_86 said:
I have a custom recovery installed ofc, if I install the pre-rooted 05Q I lost all my data and apps? Should I do a factory reset? Thanks for your fast answer mate!!
Click to expand...
Click to collapse
If you have custom recovery installed. Do a back up first. You should not have to wipe or lose anything.

rraquib said:
If you have custom recovery installed. Do a back up first. You should not have to wipe or lose anything.
Click to expand...
Click to collapse
Really thanks again mate!! I do it, like you, as soon as possible.

Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??

timmaaa said:
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
Click to expand...
Click to collapse
@timmaaa Read carefully I mentioned both option and he was wondering about the pre-rooted version.

rraquib said:
@timmaaa Read carefully I mentioned both option and he was wondering about the pre-rooted version.
Click to expand...
Click to collapse
You said that flashing entire ROM would be easier, it isn't. All that's need to get root is to flash the SuperSU zip. He's already on 05Q so flashing the ROM zip is completely and utterly pointless. It's like telling someone who's run out of petrol to install a entirely new petrol tank that's full of petrol (when all that's actually needed is the fuel).
It doesn't matter what someone thinks might be the solution, if you're going to answer in the q&a section you need to give the best and easiest solution.

The thing is flashing update-supersu is not working... for me at least. I updated OTA.. After installation finished, rebooted to TWRP and tried to install update-supersuv2.37.zip...
It doesn't show any error, but when I reboot my phone there is no supersu installed ( actually there is one but it's greyed out with android icon and not showing up on application list )

timmaaa said:
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
Click to expand...
Click to collapse
+1
only SU from TWRP

plato79 said:
The thing is flashing update-supersu is not working... for me at least. I updated OTA.. After installation finished, rebooted to TWRP and tried to install update-supersuv2.37.zip...
It doesn't show any error, but when I reboot my phone there is no supersu installed ( actually there is one but it's greyed out with android icon and not showing up on application list )
Click to expand...
Click to collapse
Install a newer version
#stayparanoid

Sorry guys for don´t answer your comments, I have been working out of my country for a couple of weeks.
I get root on 05Q with just flashing SuperSU 2.46 from recovery. Easy and fast, just that.
Anyway you have my thanks in your respective buttons.
EDIT: If moe people with doubts read this. I use the info on this post. http://forum.xda-developers.com/showthread.php?t=2788632

OTA update with unlocked bootloader

I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?

geicogecko said:
I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?
Click to expand...
Click to collapse
I think you should be able to
Sent from my Pixel 2 XL using Tapatalk

You cannot take OTA updates normally with an unlocked bootloader. The phone will download the update, but the update will fail.
You CAN update manually using either OTA or factory images from here and following my guide here.
To sideload OTA images using either stock recovery or TWRP, follow the instructions here.

Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.

geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.

geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.

socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?

k.s.deviate said:
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?
Click to expand...
Click to collapse
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...

socal87 said:
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...
Click to expand...
Click to collapse
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.

k.s.deviate said:
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.
Click to expand...
Click to collapse
I downloaded the OTA directly from https://developers.google.com/android/ota, then rebooted into TWRP and flashed the zip.
I'm on stock software with the exception of Magisk and Flash kernel, so OTAs always fail. Thus, I have Automatic System Updates turned off in Developer Options.
Regardless of how you do it, the OTA will always overwrite /boot, so you'll lose custom kernel and recovery.

bobby janow said:
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.
Click to expand...
Click to collapse
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.

socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.

geicogecko said:
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.
Click to expand...
Click to collapse
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
socal87 said:
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.
Click to expand...
Click to collapse
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Yes. If you're otherwise stock aside from an unlocked bootloader, you can sideload the OTA zip...or, copy it to internal storage, reboot to recovery, and install it that way.
If you want to keep TWRP, you'll have to boot the TWRP image after installing and rebooting, then flash TWRP. The OTA does not wipe data (obviously); it just returns everything in /boot and /system to stock.

The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Click to expand...
Click to collapse
So I actually took the advice and relocked the bootloader. No issues. I think there was one app that I would've needed root for, but I can't remember what it was. I didn't use Xposed. I don't even know if it works on the Pixel. Like I said in the opening post, I only needed it to enable wifi hotspot, so others may notice it more.

Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.

ychongy13 said:
Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.
Click to expand...
Click to collapse
You should be able to install the latest OTA image using stock recovery:
https://developers.google.com/android/ota